Try to add these lines to your configuration.yaml (after calibration_points)
scan_interval:
seconds: 30
auto_update: true
It worked for me.
Unfortunately, that did not work.
Thanks!
How can I chance the installation type?
If I install a new VM and restore HA?
The vacuum is Roborock S5 Max
@CommittotheIndian Do you have anything in logs? Eg just after HA start
@Mabaelst You would have to ditch HassOS, I donāt think itās worth itā¦
Initially after restart all I get is the warning it took longer than 10 seconds.
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:476
First occurred: March 30, 2021, 7:05:05 PM (48 occurrences)
Last logged: 3:42:37 AM
Update of camera.xiaomi_cloud_map_extractor is taking over 10 seconds
Update of vacuum.webette is taking over 10 seconds
After a few hours I got a couple of these:
Logger: custom_components.xiaomi_cloud_map_extractor.camera
Source: custom_components/xiaomi_cloud_map_extractor/camera.py:194
Integration: xiaomi_cloud_map_extractor (documentation)
First occurred: 3:40:39 AM (1 occurrences)
Last logged: 3:40:39 AM
Got exception while fetching the state: Unable to discover the device 10.10.*.*
Logger: homeassistant.components.camera
Source: helpers/entity_platform.py:605
Integration: Camera (documentation, issues)
First occurred: 3:40:57 AM (1 occurrences)
Last logged: 3:40:57 AM
Updating xiaomi_cloud_map_extractor camera took longer than the scheduled update interval 0:00:30
Which is weird because again I can control it, see sensor, etc. That last one just started after adding the scan_interval part to my config mentioned a couple posts up.
I am using the Xiaomi Mio integration instead of the YAML for control ever since I moved my HA Instance to a blue. I could still control it with YAML before though.
1 Like
Thank you!
If I understand correctly, if I start a new VM and I re-integrate the Vacuum Cleaners should this work?
This is a new installation. I could add text to the previous one. What have I done differently now than last time?
Suppose I reinstall everything, do I need to install another package from HA?
Thank you for your response.
@CommittotheIndian please check if token token is still valid. You can do it using tokens extractor
@Mabaelst the problem is that (as far as I know) HassOS doesnāt have any preinstalled font. I will try make it possible to provide your own font file
OK thank you.
But then I donāt understand that I could use text (freesans.ttf) in a previous installation of HA and not with this new installation!
I can not get any of the token extractor apps to work. Iām still trying to figure out another way.
Could I still control the vacuum if the token had changed?
@Mabaelst what type of installation was it?
@CommittotheIndian probably notā¦ Maybe IP address is invalid? You can check current configuration of integration in .storage directory
Pulled my token, itās the same. The file from my phone with the token also showed the correct IP.
@CommittotheIndian maybe something blocks traffic to Xiaomi cloud? (adguard/pihole/ā¦)
@Mabaelst previous one, not current 
Sorry, but I donāt remember that correctly.
I think I did exactly the same with this new installation as with the previous one and then I was able to add text. Thatās why I wonder why it doesnāt work with this new one?
Okay so I saw that earlier you said that the token has to be in single or double quotes. Does this go for the other login info as well?
camera:
- platform: xiaomi_cloud_map_extractor
name: xiaomi_vacuum_map < no quotes here?
host: "192.168.1.2"
token: "1a2b3c4d5e6g7h7i8j"
username: "johndoe"
password: "password"
draw: ['all']
attributes:
- calibration_points
I have the same issue as @CommittotheIndian and I actually do run pihole.
After a quick look at your code, I identified three domains for whitelisting:
Letās see if that helps. Did I forget anything?
Unfortunately doesnāt look like that works either. I added those sites to my whitelist and disabled pihole for good measure. Still sits idle.
This is the only error Iām getting right now.
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:476
First occurred: 8:06:08 PM (1 occurrences)
Last logged: 8:06:08 PM
Update of camera.xiaomi_cloud_map_extractor is taking over 10 seconds
Not sure if others will pop up later.
@Mabaelst I have no ideaā¦
@combative-american you can use quotes in every text parameter
@kongo09 @CommittotheIndian vacuum also has to have access to Xiaomi servers + probably it has to be in the same subnet as HA
Subnet is the same. I wouldnāt know why there wouldnāt be any access to Xiaomi servers. If I remember correctly, I didnāt have any errors before 2021.3 version of HA. Actually, at the same time, I also started to get a lot of errors concerning cast devices.
Are you aware of any changes in the inner workings of HA that could be at the root here?
Same as @kongo09,
My subnet is the same. My HA can ping and control the vacuum so it is clearly communicating with it. Iām on 2021.3.4. After a few hours of running, checked the logs again and now Iām showing these errors.
Logger: homeassistant.components.xiaomi_miio.vacuum
Source: components/xiaomi_miio/vacuum.py:506
Integration: Xiaomi Miio (documentation, issues)
First occurred: 3:40:29 AM (2 occurrences)
Last logged: 10:16:31 AM
Got exception while fetching the state: Unable to discover the device 10.10.*.*
Logger: custom_components.xiaomi_cloud_map_extractor.camera
Source: custom_components/xiaomi_cloud_map_extractor/camera.py:194
Integration: xiaomi_cloud_map_extractor (documentation)
First occurred: 3:40:41 AM (1 occurrences)
Last logged: 3:40:41 AM
Got exception while fetching the state: Unable to discover the device 10.10.*.*