Woke up to a broken Roborock integration—anybody else?

Configuration
1

Morning! I woke up to an updated Roborock app, and a broken integration—so I assume something there was a breaking change.

Anybody else? Or is this isolated to just me?

Already tried deleting and reconnecting the integration, but no luck.

2

Yes, same problem here.
No errors in logs either. You?

3

Same here. Roborock Integration does not connect to the vacuum anymore.

4

Got mine working again finally, kinda.
I found if I disable HACS, then Roborock works. So there must be a conflict.
Haven’t figured out what yet.

5

Do you have this problem with the core or only with hacs version of Roborock?

6

Core version. I switched to it from HACS when it became part of core.

7

So when you said you disabled HACS, do you mean you disabled all of your hacs integrations? In that case, I would update all of your integrations and see if that makes a difference. If it doesn’t, then I need you to post logs.

8

Yes disabled HACS integration and then all the integration associated with it, then restarted HA.
They are all up to date.

9

Still testing but it seems to be the Govee HACS integration which breaks Roborock.

1 Like
10

Update it - This has been an error i’ve been working with for months now. Nothing I can do about it because the custom component pulls a version of a dependency that Roborock needs down. Updating Govee hacs or switching to the core integration should fix it.

11

There is no newer update for Govee HACS unfortunately and the model i have does not support local api control so i cannot use the core integration. However I did find another option, which is the Govee MQTT Addon, so have moved to that.

12

Here is the issue on the Govee side for anyone wanting to track it.
Please update Dacite · Issue #159 · LaggAt/hacs-govee (github.com)

13

I am experiencing the same issue with S8 MaxV Ultra on 2024.12.4. Not entirely sure when the connection broke, but I’m pretty sure I first set it up via the core integration (not HACS) after the 2024.12 release. Have only used it on the core integration, never with HACS, and I don’t have any Govee devices. Deleting the integration and re-adding does not solve the issue. Below are the logs:

Logger: roborock.containers
Source: /usr/local/lib/python3.13/site-packages/roborock/containers.py:128
First occurred: 4:23:07 PM (4 occurrences)
Last logged: 4:26:43 PM

HomeDataDevice.__init__() got an unexpected keyword argument 'cid'
Traceback (most recent call last):
  File "/usr/local/lib/python3.13/site-packages/roborock/containers.py", line 112, in convert_to_class_obj
    return_list.append(cls_type.from_dict(obj))
                       ~~~~~~~~~~~~~~~~~~^^^^^
  File "/usr/local/lib/python3.13/site-packages/roborock/containers.py", line 166, in from_dict
    return cls(**data)
TypeError: HomeDataDevice.__init__() got an unexpected keyword argument 'cid'

Logger: homeassistant.config_entries
Source: config_entries.py:640
First occurred: 4:23:07 PM (4 occurrences)
Last logged: 4:26:43 PM

Error setting up entry [email protected] for roborock
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 640, in __async_setup_with_context
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/roborock/__init__.py", line 72, in async_setup_entry
    device.duid: device for device in all_devices
    ^^^^^^^^^^^
AttributeError: 'dict' object has no attribute 'duid'
14

Hi @msl2424 you are experiencing a different issue

copying context from another thread:
Hi everyone! Codeowner for the Roborock integration here. I have a fix for this already included in 2024.12.5 as of this morning. Once 2024.12.5 gets pushed out, update to that.

Basically, Roborock changed their api yesterday a tiny bit and that is causing the issues. I added a solution that will help prevent a similar error from happening again, but api changes of any form can cause major problems.

MANY previous versions of the roborock integration will be permanently broken! So I’m sorry to force anyone to 2024.12.5 that wasn’t planning on it, but you will need to. I encourage everyone to go here: #133533 where I will leave the issue open for any further questions. I do not frequently check the forums.

Sorry for the inconvenience everyone! I fixed it as soon as I was aware of it, but of course I have no real affiliation with Roborock, so I did not know beforehand. Hopefully 2024.12.5 will be released shortly.

5 Likes
15

Hi @Lash-L, I upgraded today to v2024.12.5 but I still have the issue, tried to remove roborock integration multiple times. I get this errors with status on the integration, failed to configure, initializing endless loop.

Logger: roborock.api
Source: runner.py:154
First occurred: 2:10:54 PM (1 occurrences)
Last logged: 2:10:54 PM
[Roby] id=1 Timeout after 4 seconds

Logger: roborock.api
Source: components/roborock/coordinator.py:80
First occurred: 2:10:56 PM (44 occurrences)
Last logged: 2:13:48 PM
[Roby] id=1 Timeout after 4 seconds

16

2024.12.5 fixed the issue with mine.

17

(post deleted by author)

18

2024.12.5 didn’t resolve for Qrevo Master for me. I posted the issue to this 133533 Github ticket. If you folks read the ticket, there is a manual workaround that you could to resolve for Qrevo Master, but I haven’t tried it.