Unable to add Roborock and invalid status error message format.

[honeydripper]

The problem

After updating to 2026.1.1 Roborock integration stopped working.
The integration reports: "Failed setup, will retry: No devices were able to successfully setup"

Removing readding integration does not resolve the problem.
From the logs it looks like it fails on pulling maps:
Command RoborockCommand.LOAD_MULTI_MAP failed on mqtt channel: Invalid V1 message format: missing 'result' in data point for b'{"t":1768419740,"dps":{"102":"{\\"id\\":20062,\\"error\\":{\\"code\\":-10007,\\"message\\":\\"invalid status\\"}}"}}'

Attaching the full debug logs for reference.

home-assistant_roborock_2026-01-14T19-45-51.242Z.log

What version of Home Assistant Core has the issue?

2026.1.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

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

No response

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

[Lash-L]

So I think two things are happening here:

1. The error message is different than what our system is used to and causes issues there
2. Your map is in a state where the Roborock api does not allow pulling the map. Were you cleaning when you tried to set up the vacuum? Or potentially is your map unsaved?

[milousparks]

I solved this issue by going into the Roborock mobile app and accepting the new user agreements. Then I clicked “Enter” under the Devices tab and accepted the agreements again. After that, the integration started working again after a refresh.

[honeydripper]

Thanks both, the map was saved (at least I did not have any unsaved notification) and I did not get any new user agreements. I fiddled with the Roborock app again (as I did before filing this issue) and it worked in some magic way. Not sure if my fiddling had any effect or this was completely external.

This issue can be closed. Thanks heaps for jumping on it!

[allenporter]

We'll keep this open to track the error message parsing at least, and then see if we need to show something better in the user interface.

[allenporter]

Lash-L fixed this in Python-roborock/python-roborock#744 and can be considered resolved now.