Piotr Machowski

@saschabrockel just turn it off and on again. You can do it by holding power button on the vacuum

@saschabrockel what is exact model code of your vacuum?

@saschabrockel I meant one in this format: roborock.vacuum.a11

Something must be blocked somewhere. Vacuum must be in the same network as HA, vacuum and HA must be able to access Xiaomi cloud for map extractor to work properly

@saschabrockel have you checked token with tokens extractor?

@saschabrockel Ok, that's great 👍 I will mark this conversation as off-topic, as original problem is different

It seems that this vacuum has a problematic data from a last cleaning. Full cleaning should fix this issue. One more thing: your config puts unnecessary stress on your HA...

Let's keep this open as this error should have been handled by the integration. I will close this issue when a proper solution will be merged in code

Yup, I prefer to keep code changes on `dev` branch until a release. Shouldn't `unique_id` be generated automatically instead of being provided in yaml? Imports would probably benefit form a...

> Not for yaml as they need to be persistent between reboots (or it would create a new entity every time) hence why someone needs to manually type something unique....