home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.31k stars 30.62k forks source link

Roborock map not showing docked robot #110588

Open mvdwetering opened 8 months ago

mvdwetering commented 8 months ago

The problem

My robot has been docked for several hours now, but the map still shows the robot in the kitchen area (yellow/orange part on th eleft) while it is actually at the dock (on the right side of the central blue area). The Roborock app does show the correct map

Home Assistant map: image

Roborock map: image

Looking at the timestamps when the image and vacuum entity were last updated it looks like the map image was not updated after it docked. I assume that map updates are only done while it is cleaning, but maybe an additional last update could/should be done after it docked?

Image entity state according to entity state history: image

Vacuum entity state change to docked according to the entity state history image

What version of Home Assistant Core has the issue?

core-2024.2.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Roborock

Link to integration documentation on our website

https://www.home-assistant.io/integrations/roborock/

Diagnostics information

config_entry-roborock-47dd5a0c17ed868596ee8771370bbe3b.json

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 8 months ago

Hey there @humbertogontijo, @lash-l, mind taking a look at this issue as it has been labeled with an integration (roborock) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `roborock` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign roborock` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


roborock documentation roborock source (message by IssueLinks)

Lash-L commented 8 months ago

You are correct - map updates are only done while they are cleaning. It probably would be sane if it updated one more time. I'll think about this problem a bit more.

nicoodeimos commented 6 months ago

I can confirm I have the same issue with Roborock s7 maxV.

jc4thirty commented 5 months ago

Confirming the same issue with both s4 and s4 Max here.

issue-triage-workflows[bot] commented 2 months ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

Lash-L commented 2 months ago

Not stale

Oleg-Sob commented 1 week ago

The problem remains.