-
-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to retrieve map from vacuum #422
Comments
Does the map work in Xiaomi Home? |
Hmm, indeed, no... Didn't check it as I assumed it would be HA-related... Any idea how that might happen? (and how to fix it) |
I have the same problem, I have no idea what happened. It might be a problem on the Xiaomi Cloud side - vacuum doesn't return map id because it can't upload it to the cloud. I hope it's not a ban... Do your vacuums have the latest firmware versions? Has any new update become available in the last days? |
The S5 hasn't been updated in a while as it's the one upstairs that doesn't get used that much. edit |
Ok, I have rebooted my vacuum and it started to work. Maybe it will work with your vacuums as well. |
Thanks! I'll try it with the one downstairs, and tomorrow with the other one. edit |
You have to hold the power button for a few seconds |
Great! It worked for the S7. I'll try the S5 tomorrow. I assume it'll work as well... |
I seem to have the same problem periodically as well. It seemed to start when i customized the whole image with different colors. Don't know if these modifications are done after the retrieval from Xiaomi, or before. When it's not working i don't see an image of my room in the Xiaomi app as well. It will try to load the map indefinitely in the Xiaomi app. After several days or something sometimes it is working all of a sudden again. Will investigate if this still breaks occasionally without all the custom color things. |
@MathijsG it must've been a coincidence. Map coloring is done completely on the integration side. |
By the way Roborock S50 / S5 Non-max edition All the other cloud features still work, can even start it, etc, just without visuals. |
Weird over here. Restart fixed the s7 on Friday but when I checked again on Saturday, the s5 was available and the s7 wasn’t. |
I have closed this issue because it doesn't seem to be connected to the code of the integration itself. You might try to increase |
Also noticed this over the last few days, rebooting the vacuum hasn't helped. I did notice that the map would randomly come back and then disappear into a broken state again. Both in Home Assistant and the Xiaomi Home app. Certainly seems like something on their side |
Just here to report that I am experiencing issues since a few days too. But it looks like there could be something wrong on the Xiaomi (cloud) side. Yesterday I had "Failed to retrieve a map", on the other hand today I see "Failed to login" message on the lovelace. Also randomly I see it works fine. |
The same thing has been happening to me for about a week, I don't know if this log has anything to do with it:
|
Having the same, also seeing Failed to login now, instead of the earlier error. |
Now I also see "Two factor auth required (see logs)" message... |
Yeah me too. I relogged in (in the logs you see the link you need to open), and now the map works again. Hope it will stay that way. |
Rebooting the robot worked but today it happened again |
Same here. What I find interesting is that my neighbour with the exact same S50 has zero problems, and another friend with his S7 no problems as well. So somehow I think this still is related to having this integration. Maybe we flooded the API? |
@MathijsG yeah, that's something I'm afraid of. You can try to reduce polling intensity by adding following config: scan_interval: 30 |
Today for me it's working again normally... |
moved to : Reboot worked yesterday, but map is once again unavaible this morning. |
I think a reboot is not really useful, as it's the cloud api connection that rejects us, not something wrong in the vacuum itself. I moved to 30 with that setting. It seems to work for now, lets see how long it will continue to work. |
ok i will test if |
Well, 60 of course would be better as it is even less often relying on the API. |
Yes. This integration doesn't work with Roborock app. Use https://github.com/humbertogontijo/homeassistant-roborock |
I removed the integration. Hopefully, the map comes back in MiApp. What do you mean with "blueprint to update it"? And where can I set auto-update: false? In configurations.yaml? Where should I integrate it. Just at the end? |
Oh my. I should read documentation more thoroughly. Thank you! |
I was able to install MapExtractor again and I add the code in configuration file camera:
- platform: xiaomi_cloud_map_extractor
host: XXXXX
token: XXXXX
username: XXXXX
password: XXXX
draw: ["all"]
attributes:
- calibration_points Then I integrated Blueprint and this is saved under: /config/blueprints/automation/PiotrMachowski/disable_vacuum_camera_update_when_docked.yaml Please can someone tell what I have to change here manually that scan interval auto update is correct that I not get the map error again? In the code I also get the error by I am not an real expert. So maybe someone can help me. |
You have to use this config camera:
- platform: xiaomi_cloud_map_extractor
host: XXXXX
token: XXXXX
username: XXXXX
password: XXXX
draw: ["all"]
attributes:
- calibration_points
auto_update: false Do not modify blueprint, just create an automation using it. |
@PiotrMachowski same thing, I import the blueprint, I modify my configuration yaml for add auto update false and I have the " failed to retrieve device " message on my dashboard... My map appear on mi home app |
@PiotrMachowski Same for me. I did the same steps like you. The map info is "failed to retrieve device". |
Same, the control work but not the map |
Are we the only one with this problem? |
Did you find any solution? |
Hi, I still have this issue, any solution? |
@Loeana Can you please invite me to your node-red project? Would love to check it out! Thanks |
I'm having as well issues with the vacuum map on the xiaomi app and on HA. I've applied @PiotrMachowski's blueprint / automation suggestions and will report back if it gets working again. |
Would be great when @PiotrMachowski has some time to check it. 2023-11-14 21:37:43.149 WARNING (SyncWorker_5) [custom_components.xiaomi_cloud_map_extractor.camera] Got exception while fetching the state: No response from the device |
Still being worked on? |
@BeardElk that's not related to this discussion. Your card configuration doesn't match your vacuum integration. |
Sorry! |
So I added the suggestionst that @PiotrMachowski made, the map came back on the iOS app but in HA there is no map anymore. |
This works great. Thanks a lot for the fix/workaround @PiotrMachowski |
It works. I got another Token as before. Maybe it helps someone else. |
Hi @PiotrMachowski, this solution by the moment works fine. The only issue is that when the vacuum is cleaning it do not update the map. Just only when is docked. Many thanks! UPDATE: after first docking it fails again.... I tryed another option of the blueprint and it seems the same... after first docking doesn't work any more |
Hi @PiotrMachowski, I was doing some tests with map update... The point is the following: I delete the integration and set up again. In my camera configuration I set up " scan_interval: 900" in order to not overload the Xiaomi API. I do not set any blueprint. When I load everything it seems everything works correctly. I turn on the vacuum and the map is updated correctly. BUT when the vacuum is docked it seems something start go wrong... Right now, when I load the card I figured it out that the first thing I can see is the following picture This screenshot is presented during less than a second. Afterwords it loads the map again but the map it's not updated (I guess it's loaded from cached map). So, the map is not updated Finaly, if I reboot HA, the map update doesn't work anymore. In the same way before, it appears the "disconnected" screenshot before for less than 1sec and afterwords the following image (I understand the cached map is not available anymore) So, I said before in my last comment, it seems that when the vacuum is docked the first time the integration crashes somewhere and stop working Hope this helps! |
Not only integration crashes, map won't load anymore when using this Home Assistant extension on your vacuum. Xiaomi app just shows "Map Loading" after using this extension, and you must unpair and change device to different region and back to restore map functionality. |
is this now seriously an only option?
Thanks |
My suggestion is still the same, but it is buried deep in this thread. In the meantime I am working on a rewritten version of the integration, but I don't have as much free time as I used to.
They will just tell you to remove vacuum from HA |
Unfortunately I think that I got blocked even while using the blueprint. And that happened quickly even while not docked. 👎 |
You have to add camera:
- platform: xiaomi_cloud_map_extractor
host: !secret xiaomi_vacuum_host
token: !secret xiaomi_vacuum_token
username: !secret xiaomi_cloud_username
password: !secret xiaomi_cloud_password
draw: ['all']
attributes:
- calibration_points Then you can use the blueprint in "two intervals mode" with "docked" interval set to a few hours. It should be fixed after 2-3 days after this change. You can also reboot the vacuum to help it recover. I will now lock this conversation to prevent my comment from disappearing again. |
Checklist
The problem
First of all thanks for this great integration! I've been using it for more than a year now without any issues.
However for the last couple of days I don't receive any maps anymore.
I only see "Failed to retrieve map from vacuum" for both my vacuums (S5 &S7).
I've checked the logs but nothing's showing. I only have the custom integration error about that it's not tested by Home Assistant. But after that, nothing at all.
Always difficult when something breaks when you didn't change anything...
Any idea's?
What version of an integration has described problem?
v2.2.0
What was the last working version of an integration?
v2.2.0
What vacuum model do you have problems with?
S5 and S7
What version of Home Assistant do you use?
2023.3.6
What type of installation are you running?
Home Assistant Core
Camera's configuration
Errors shown in the HA logs (if applicable)
Additional information
No response
The text was updated successfully, but these errors were encountered: