-
-
Notifications
You must be signed in to change notification settings - Fork 41
Does not load the map #511
Comments
I am also having map display issues with X2 Omni and am happy to assist with pulling logs and testing with some guidance. Entity logbook shows successful map updates every second, however accessing the entity image via the hass/api/image_proxy url within the entity results in 500: internal server error This perhaps may belong in a new ticket - but I'm seeing parsing errors in the log - sample log attached while cleaning in progress |
I am having the same problem with the X1 |
Same here for the N8 - vacuum is configured via the app and over there the map is available and working as expected. |
Newer bots use different commands for the map than older ones. DeebotUniverse/client.py#372 tried to implement the new command but it takes time. |
|
I can confirm that the map is working with the 950 as I have that model. |
I just removed the integration and then removed it from hacs, reboot HA and installed the core integration. Hope this is of some help... I have root access to my X1 so if @edenhaus need anything from me, feel free to ask. |
You can see the map with the hassio build-in integration and what the Deebot is doing at moment on in? |
Not sure I understand the question... The core integration is working and I can see a map. |
Checks
The problem
Good morning, I just installed the integration. I have a Deebot x2 omni, it has already mapped my house from its original app, and made several trips even after configuring the robot on HA. Despite this, the map still doesn't load and I can't figure out how to do it. Without that I don't know how to do automations for cleaning certain rooms
On which deebot vacuum you have the issue?
Deebot x2 omni
Which version of the Deebot component are you using?
3.1.1
Which version of Home Assistant are you using?
2024.1.5
What type of installation are you running?
Home Assistant Core
Country
it
Continent
eu
Instance type
Cloud
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: