Robrock Saros 10R RoborockMopIntensity always off with new firmeware version

[Pizzaschachtel]

The problem

The new firmware version (02.45.86) of the Saros 10R causes issues within HA. The MopIntensity entity always show the State "off". If I change the value in the frontend, then the value is set in the Roborock app (set a value works as expected), but after a short time, the entity state resets to off (the value in the Roborock App keeps like previous set). So my guess is, that the mapping from the "get" function does not work like expected.

What version of Home Assistant Core has the issue?

core-2025.6.1

What was the last working version of Home Assistant Core?

core-2025.6.1

What type of installation are you running?

Home Assistant Container

Integration causing the issue

roborock

Link to integration documentation on our website

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

Diagnostics information

config_entry-roborock-01JTXRB85XYCVY41K5RFWHWGQZ (1).json

Example YAML snippet

Anything in the logs that might be useful for us?

2025-06-19 22:04:05.532 WARNING (MainThread) [roborock.code_mappings] Missing RoborockMopIntensityS7 code: 235 - defaulting to 200

Additional information

No response

[home-assistant[bot]]

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)}}

[issue-triage-workflows[bot]]

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]

not stale

This issue is likely due to incorrect mappings, we previous have depended on users providing the data but that has proven to be a bad method as firmwares can change the values.

We have a new method of being dynamic with the modes, but that likely wont be in HA until 2025.11

[issue-triage-workflows[bot]]

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.

[sroebert]

This is not solved and still an issue