Roborock vacuum status updates very slowly after start

[christer-svg]

The problem

After starting my Roborock vacuum (via Home Assistant), the state/status takes a very long time to update. This makes automations and UI feedback unreliable, since Home Assistant still reports the old state for a significant amount of time after the robot has actually started cleaning.

The robot starts cleaning immediately, but the state in Home Assistant updates only after a long delay 20-40 seconds.

It worked before updating to 2025.12

Model: Roborock Saros 10

What version of Home Assistant Core has the issue?

2025.12.5

What was the last working version of Home Assistant Core?

2025.11

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Roborock

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

roborock_2026-01-03T09-13-56.838Z.log

config_entry-roborock-01KDG7S09PA4DC8P6EQPZBTTVJ.json

[home-assistant]

Hey there @Lash-L, @allenporter, 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)}}

[dontobi]

Ich hab das selbe Problem. Viele Entitäten werden erst nach mehreren Sekunden geändert.

[johnmph]

Same here with a Roborock S8 MaxV Ultra, there is a delay of about 20 seconds.

I temporary "fixed" it by using a bool passing to true when a command is sent to the robot and passing to false with an automation when the status of the robot changed, and I use this bool for showing a message "Command sent, please wait" instead of showing the buttons.

But it is far from ideal...

[christer-svg]

Another fix is to get the status from Matter. It doesn't have nearly as much functionality as choosing which rooms etc. but you can combine them, use the status which is updated instantly from Matter and the rest from the Roborock integration. Saros 10 supports Matter but don't know if S8 MaxV does?

[johnmph]

Yes I think S8 MaxV supports Matter, thanks, I will try that

[MSL-DA]

I’m experiencing the same thing … about a 30-second delay. It’s all something that started after that infamous update (MRGA) that was supposed to be so great, but has given me nothing but headaches.

[MSL-DA]

Funny enough, @Lash-L and @allenporter bury their heads in the bushes and pretend that integration is worth a silver medal!

[Lash-L]

@MSL-DA Contributions welcome! Allen and I both have families. We do this as a hobby. Take your disrespect elsewhere.

The integration is tagged as a polling integration - meaning it updates on a set interval.

I'm working on getting more automatic updates working here: Python-roborock/python-roborock#731

automatic updates existed in an older version of the api, but were removed during our large refactor. There are significant stability reasons for this, this is not something we can just pop back in and be happy with. It requires the cloud connection, which can lead to a bunch of problems.

I do not have unlimited time. I prioritize other functionality that helps improve performance, reliability and device support. I work a full time job, I have a kid under 1, I am getting my masters. I do this is a hobby, I am not paid and I am not affiliated with Roborock. All the work we do - we have to determine ourself, Roborock does not communicate with us at all, there is not a manual, no documentation. Every feature takes a significant amount of time to make sure we do right.

Lastly, I encourage you to read what the quality scale means. We hit a set of feature requirements and code quality requirements to get the silver quality status, it does not mean we have 100% feature parity with the app.

TLDR: Just don't be rude and please never tag us again to be disrespectful.

[MSL-DA]

@MSL-DA Contributions welcome! Allen and I both have families. We do this as a hobby. Take your disrespect elsewhere.

The integration is tagged as a polling integration - meaning it updates on a set interval.

I'm working on getting more automatic updates working here: Python-roborock/python-roborock#731

automatic updates existed in an older version of the api, but were removed during our large refactor. There are significant stability reasons for this, this is not something we can just pop back in and be happy with. It requires the cloud connection, which can lead to a bunch of problems.

I do not have unlimited time. I prioritize other functionality that helps improve performance, reliability and device support. I work a full time job, I have a kid under 1, I am getting my masters. I do this is a hobby, I am not paid and I am not affiliated with Roborock. All the work we do - we have to determine ourself, Roborock does not communicate with us at all, there is not a manual, no documentation. Every feature takes a significant amount of time to make sure we do right.

Lastly, I encourage you to read what the quality scale means. We hit a set of feature requirements and code quality requirements to get the silver quality status, it does not mean we have 100% feature parity with the app.

TLDR: Just don't be rude and please never tag us again to be disrespectful.

Do you think it lives up to “Provides a stable user experience under various conditions” when a user has to wait 30–60 seconds before the status updates in Home Assistant - that is, before I can cancel or stop the current run.

And by the way, you don’t need to tell me who I shouldn’t tag. If you’re unhappy, you’re welcome to use GitHub’s feature for unwanted contact. Freedom of speech 🤜🏾

[strutings]

And by the way, you don’t need to tell me who I shouldn’t tag. If you’re unhappy, you’re welcome to use GitHub’s feature for unwanted contact. Freedom of speech 🤜🏾

This has nothing to with FOS. As a general guideline It’s considered rude to tag the owner of the code on github, that’s it.

[MSL-DA]

As a general guideline It’s considered rude to tag the owner of the code on github, that’s it.

You should read the Code of Conduct … it would suit you better than coming up with your own rules.