Roborock QRevo Master fails to set up, timing out in GET_STATUS

[rccoleman]

The problem

In the new 2025.12.0b0, my three Roborock QRevo Master no longer complete integration setup. In the debug logs, it looks like they all fail due to timeouts when the GET_STATUS command is issued.

2025-11-26 10:04:57.525 DEBUG (MainThread) [roborock.devices.v1_rpc_channel] Sending command (local, request_id=20043): RoborockCommand.GET_STATUS, params=None
2025-11-26 10:04:57.527 DEBUG (MainThread) [roborock.devices.v1_rpc_channel] Sending command (local, request_id=20044): RoborockCommand.GET_STATUS, params=None
2025-11-26 10:04:57.529 DEBUG (MainThread) [roborock.devices.v1_rpc_channel] Sending command (local, request_id=20045): RoborockCommand.GET_STATUS, params=None
2025-11-26 10:05:07.317 DEBUG (MainThread) [roborock.mqtt.roborock_session.aiomqtt] Sending PINGREQ
2025-11-26 10:05:07.395 DEBUG (MainThread) [roborock.mqtt.roborock_session.aiomqtt] Received PINGRESP
2025-11-26 10:05:07.527 DEBUG (MainThread) [homeassistant.components.roborock.coordinator] Failed to update data during setup: Command timed out after 10.0s
2025-11-26 10:05:07.530 DEBUG (MainThread) [homeassistant.components.roborock.coordinator] Failed to update data during setup: Command timed out after 10.0s
2025-11-26 10:05:07.530 DEBUG (MainThread) [homeassistant.components.roborock.coordinator] Failed to update data during setup: Command timed out after 10.0s
2025-11-26 10:05:07.531 DEBUG (MainThread) [roborock.devices.v1_channel] Unsubscribed from device XrQn1jySYJQLoJOLo660d
2025-11-26 10:05:07.532 DEBUG (MainThread) [roborock.devices.v1_channel] Unsubscribed from device 6aG6Gke2SLXndVF9kk4ShJ
2025-11-26 10:05:07.532 DEBUG (MainThread) [roborock.devices.v1_channel] Unsubscribed from device 63z8ayoLM4TMbwfOowNX3e
2025-11-26 10:05:07.532 DEBUG (MainThread) [roborock.devices.v1_channel] Background reconnect task cancelled
2025-11-26 10:05:07.532 DEBUG (MainThread) [roborock.devices.v1_channel] Background reconnect task cancelled
2025-11-26 10:05:07.532 DEBUG (MainThread) [roborock.devices.v1_channel] Background reconnect task cancelled
2025-11-26 10:05:07.532 WARNING (MainThread) [roborock.devices.local_channel] Connection lost to 192.168.1.118
2025-11-26 10:05:07.533 WARNING (MainThread) [roborock.devices.local_channel] Connection lost to 192.168.1.153
2025-11-26 10:05:07.533 WARNING (MainThread) [roborock.devices.local_channel] Connection lost to 192.168.1.150

These vacuums use the new L01 protocol.

What version of Home Assistant Core has the issue?

core-2025.12.0b0

What was the last working version of Home Assistant Core?

core-2025.11.3

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

home-assistant_roborock_2025-11-26T18-05-41.060Z.log

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

[rccoleman]

I had been testing with @Lash-L with python-roborock==3.7.2 and I notice that the HA beta is stil using 3.7.1. On a whim, I tried to update to 3.8.0 (latest on pypi) and two of my three robots came up in HA, but now they're all unavailable. Here's the debug log from a few cycles with 3.8.0.

home-assistant_roborock_2025-11-26T18-43-41.200Z.log

[Lash-L]

I had been testing with @Lash-L with python-roborock==3.7.2 and I notice that the HA beta is stil using 3.7.1. On a whim, I tried to update to 3.8.0 (latest on pypi) and two of my three robots came up in HA, but now they're all unavailable. Here's the debug log from a few cycles with 3.8.0.

home-assistant_roborock_2025-11-26T18-43-41.200Z.log

should be fixed with Python-roborock/python-roborock#593

And a version bump on core

[allenporter]

Tagging with b0 for now, but should probably be b1

[rccoleman]

Running with 3.8.1 looks good. Thanks for the quick turnaround!

[dynasticorpheus]

@Lash-L Despite manually upgrading to python-roborock==3.8.1 on 2025.12.0b0 my Q8 Max fails to setup most likely due to below error. Shall I raise a separate issue?

Logger: homeassistant.util.json
Source: util/json.py:72
First occurred: 10:02:13 (1 occurrence)
Last logged: 10:02:13

JSON file reading failed: /config/.storage/roborock/01JFAXEN5Q41V4K9PEP6M3JEZY
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/util/json.py", line 72, in load_json
    with open(filename, mode="rb") as fdesc:
         ~~~~^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/util/loop.py", line 201, in protected_loop_func
    return func(*args, **kwargs)
IsADirectoryError: [Errno 21] Is a directory: '/config/.storage/roborock/01JFAXEN5Q41V4K9PEP6M3JEZY'

edit: already addressed in #157379 hence removed folder manually and setup is successful now

[allenporter]

I have confirmed the folder error is fixed in b1. Thank you, we can open a new issue if there are further problems.