It’s rather “not supported yet”, but I don’t know when it will be (probably not soon). You can follow this issue to check any progress
hi, is it still not supported? what is their difference with the others?
Hi, yes, it’s still not supported. The difference is that it uses a different API that returns a map in a different format.
You can follow a status of the implementation here
Hi, i noticed an high CPU use after installing Xiaomi Cloud Vacuum Map Extractor.
I tried to set auto update to 15 sec or 20 sec but CPU use suddenly increased to 6-8% average…
I set auto update to false in config.yaml and now CPU is ok as before (average 3-4%).
It’s a known behaviour of this integration?
I tried to set auto update to 15 sec or 20 sec but CPU use suddenly increased to 6-8% average…
Thanks for your awesome integration
Hi, do you have configured scale
in your config?
Hi Piotr,
no,i haven’t scale in my config, here it is:
- platform: xiaomi_cloud_map_extractor
host: xxx.xxx.x.xxx
token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
username: [email protected]
password: xxxxxxxxxxxxx
draw: ['all']
attributes:
- calibration_points
auto_update: false
store_map: false
It’s the recommended config with some adjustement.
Your integration works pretty well except for CPU use with auto update active
Hassio updated on Raspberry3B+,Roborock S5
Well, this integration requires some computing power, as it downloads, processes and draws the whole image every 5s. You can reduce CPU usage by increasing scan_interval
and trimming the map.
Ok. Thanks. I’ll try.
Hi and thank you for developing this great component! I wanted to change the font type as some other users that are running the HA inside a container already tried, but I still didn’t manage to do it. Is there any new method to do it? I saw this issue but didn’t reach to any conclusion. Thanks!
It depends on your type of installation. Currently it seems to be possible only on pure HA core (in python virtual environment)
Strange thing. I have auto_update set to false and run update_entity service when cleaning. But with the latest version I suddenly get the image of my camera disappearing after a while when not cleaning. I have to run update_enity service manually again to restore it but after a while it disappears again. Any ideas?
I have set store_map to true. But I can’t see the file showing up anywhere. Has anyone got this working? Is there somethings else I need to do as well? Any way to troubleshoot this?
The file should be in homeassistant
container:
docker exec --it homeassistant bash
cd /tmp
I’m using the Home Assistant OS and accessing my files through the Samba share addon. Does that change anything?
Hello i keep getting log warnings
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:561
First occurred: 13:29:17 (6 occurrences)
Last logged: 14:45:53
Update of camera.xiaomi_cloud_map_extractor is taking over 10 seconds
Update of switch.dryer is taking over 10 seconds
Update of switch.washer_one is taking over 10 seconds
AND
Source: helpers/entity_platform.py:693
Integration: Camera (documentation, issues)
First occurred: 13:30:52 (3 occurrences)
Last logged: 14:12:17```
Updating xiaomi_cloud_map_extractor camera took longer than the scheduled update interval 0:00:05
Any idea on how to fix issue?
You can increase scan_interval, to get rid of the second error, but the first one will stay with you, unless you disable this logger
HI Piotr
Thank you for quick reply, please can you tell me where do i edit or add this?
vacuum:
- platform: xiaomi_miio
host: !secret xiaomi_ip
token: !secret xiaomi_token
camera:
- platform: xiaomi_cloud_map_extractor
host: !secret xiaomi_ip
token: !secret xiaomi_token
username: !secret mihome_user
password: !secret mihome_pass
draw: ['all']
attributes:
- calibration_points
scan_interval:
seconds: 20```
Like this
Just added this tried 10 ,20,30 seconds but get same error
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:561
First occurred: 22:06:10 (1 occurrences)
Last logged: 22:06:10
Update of camera.xiaomi_cloud_map_extractor is taking over 10 seconds
Plus the other
Logger: homeassistant.components.xiaomi_miio.vacuum
Source: components/xiaomi_miio/vacuum.py:124
Integration: Xiaomi Miio (documentation, issues)
First occurred: 22:06:02 (1 occurrences)
Last logged: 22:06:02
Loading Xiaomi Miio Vacuum via platform setup is deprecated; Please remove it from your configuration