Hey, do I have to use the Xiaomi app to use this integration? I need e.g. xiaomi_token etc.
I use the Roborock app for my Q8 Max+
When I added the robot to Xiaomi Home and in HA I used Xiaomi then I have twice less entities (HA) than on Roborock.
First of all what a nice integration you build for HASS!
I’m working on the integration, and everything seems to works instead of the map, it’s not consistent. one time it’s loads the other time i got the error: “Failed to retrieve map from vaccuum” I have an (Xiaomi) roborock.vacuum.m1s it’s an oldy and only supported from the chinese servers. Is this supported with your integration?
This also explains the warning in the logs:
Logger: homeassistant.helpers.entity
Source: helpers/entity.py:1263
First occurred: 13:20:46 (12 occurrences)
Last logged: 13:55:47
Update of camera.vacuum_map is taking over 10 seconds
The integration stop showing the map now completley, the ip adres in the error is correct, and in Unifi the device is connected. And i can control it through the xiaomi integration.
This error originated from a custom integration.
Logger: custom_components.xiaomi_cloud_map_extractor.camera
Source: custom_components/xiaomi_cloud_map_extractor/camera.py:326
integration: xiaomi_cloud_map_extractor (documentation, issues)
First occurred: 13:20:44 (9 occurrences)
Last logged: 14:04:48
Got exception while fetching the state: Unable to discover the device 192.168.2.75
I added the debug logging Aswell but that shows nothing extra’s
Thank for you for the response made a typo in the ip adres…
But the the camera integration looks not that stable for my usecase, after a while i get the screen as shown below, is it possible to save the map if the robot isn’t available? When i load the yaml configuration the map is shown.
As you can see rooms is empty, I thought these id’s where the same is I used to define the rooms in the Lovelace config. But that’s not how it works?. Where are the room numbers coming from?
Thanks in advance!
(I already made rooms in de xiaomi app)
No, these room IDs must match with ones that are generated by the vacuum. Attributes calibration_points and rooms should not be null though, is the map still visible? Is there anything in logs?
First of all, @3_14, thank you for you work, Great job!
Guys,
I have the Robock S5, and I’m facing the issue “Failed to retrieve map from vacuum” in the default card:
But the Mi Home application shows the map correctly, the vacuum settings is set to save the map (Map saved mode (Beta) = on), and default card with Xiaomi Miio integration works fine too.
I’m using Home Assistant OS on a Raspberry PI 4 8Gb with the last version (Core 2024.5.5).
In the Home Assistant log, I got this error message:
Registrador: custom_components.xiaomi_cloud_map_extractor.camera
Fonte: custom_components/xiaomi_cloud_map_extractor/camera.py:323
integração: xiaomi_cloud_map_extractor (documentação, problemas)
Ocorreu pela primeira vez: 10:12:21 (1280 ocorrências)
Último registro: 10:24:43
Got OSError while fetching the state: [Errno -5] Name has no usable address
Could someone help-me to make this integration works?
One small suggestion:
I do not recommend configuring attributes you don’t need - it will make everything slower and will unnecessarily take up DB space