Ah sorry. I was talking about adding support for Valetudo to the map extractor, as an alternative to ICantBelieveItsNotValetudo that doesn’t require a separate docker container, supports calibration and allows rendering the map of a Valetudo robot as a home assistant camera.
Have you uploaded it somewhere?
Not yet, I’ll probably get to it in the next few days and will share the repo so you can take a look at it.
Great addon - love it!
Two questions:
-
Missunderstood the scale completely causing my HA to restart when I eneter 15 or higher as scale parameter
How much computer power is needed with scale at maybe 3 or 4 compared to 1? -
Any way of changing the color of the grey boxes below?
I haven’t benchmarked it, but map area grows at a square rate in respect to the scale. Most of mechanism do not depend on map size, but processing bigger maps needs more CPU and memory (I assume that at least memory usage grows in a square rate as well)
Tiles use tertiary color
Thank you! But what do you mean with “tetriary color”? 
Everything is described in the link above in the “Basic” section
Ah, when I spelled it correctly it worked 
Never heard that word before
Whoops, fixed my comment
1 Like
Is the dreame.vacuum.p2140p model supported? Getting errors with the extractor. I’m getting this:
File "/config/custom_components/xiaomi_cloud_map_extractor/dreame/map_data_parser.py", line 51, in decode_map
unzipped = zlib.decompress(base64.decodebytes(raw_map_string.encode("utf8")))
zlib.error: Error -3 while decompressing data: incorrect header check
It’s hard to say, you can try to follow steps described here:
If it still doesn’t work please create a dedicated issue on GitHub and send me a raw map file
This is awesome!
Just a question, is there a way to enlarge a map? The one that is downloaded from my xiaomi account is teeny-tiny and it’s not very readable.
Sure, you just have to configure map trimming (example, documentation). To increase map resolution after trimming you can add scale as well
2 Likes
My config worked. But after a few days of working, I recently got this error when I click a room to clean.
It runs, but returns when leaving dock. Also after a few secs, the household is visible again from the lovelace card. It appears on every run. Room selection doesn’t work therefor not anymore. Only running from the Xiaomi mi home app. How is this possible? Running on a RPI4B and followed the steps from the lovelace card.
I am googling currently, but couldn’t find a proper solution… Already tried to re run a full calibration of the house. But still having the same issue.
Is it possible that your room IDs have changed? You can try to retrieve them using map extractor
Are you aware of some memory leaks, in your module or maybe somewhere in libs you are using? Our homeassistant started to restart every hour or so and when we checked it was because it run out of memory - python3 process was using it all gradually.
It looks way more stable when we turned off map transformation
This problem is caused by too big scale. Image processing takes too much time and its results seem to be cumulating in the memory.
1 Like
I’ve got the same problem as @Joojo.
It’s been quite a few months since it started…
I follow all the ideas there were in the github’s issues: using a device with the same network and trying new access, but the error keeps happening:
Logger: custom_components.xiaomi_cloud_map_extractor.common.xiaomi_cloud_connector
Source: custom_components/xiaomi_cloud_map_extractor/common/xiaomi_cloud_connector.py:122
Integration: xiaomi_cloud_map_extractor (documentation, issues)
First occurred: 06:46:02 (1 occurrences)
Last logged: 06:46:02
Additional authentication required. Open following URL using device that has the same public IP, as your Home Assistant instance: https://account.xiaomi.com/identity/authStart?…
Any news on it?