My Roborock S8 still goes unavailable every day

[hmorkemo]

The problem

The issue I reported in #152567 is still there in 2025.10.2. I've added a few comments to it.
Actually it has gotten a bit worse.
Now, when my S8 is docked and I delete and re-add the integration, it doesn't discover it at all. It discovers only my S6.
But when I start the S8 with the Roborock app and return it to the docking station, I can delete and re-add again. Now it will be discovered.
The S8 firmware is up-to-date (V02.17.42).
Is there anything I can do to help?

What version of Home Assistant Core has the issue?

2025.10.2

What was the last working version of Home Assistant Core?

No response

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

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

[artur90226]

Same

[Lash-L]

Hi! Please share your logs during setup of the Roborock integration

[EyalRotem]

I have a q revo curv, it also goes unavailable after a while. sometimes reloading the integration helps. but i guess it's a matter of timing.

re adding works fine, but it never stays available for a full clean cycle, after an hour and a half or so it becomes unavailable.

this is a log where it suddenly fails to connect (failure at : 2025-10-15 10:29:32.998) log
this is the log after re-adding the integration: log

[GeeEmm88]

Same here for Q Revo and Q8+ Max….

[ctsdad]

Hey to add to the list of devices I am having the same issue where my S7+ and dock become unavailable at least once every 24 hours. The only fix for me is to delete them and reinstall.

[paulc-us]

Same issue. qrevo s5v.

[namecaps3k]

Same on qrevo curv

[Lash-L]

@EyalRotem thanks for sharing your logs. Everyone else, I ask that whenever you are on a issue on github you share your logs. variations of 'same on X' blow up my messages and make it very difficult for me to parse out helpful information.

Please always provide your device model and your logs so I can do my best to help you.

Eyal, looking at your logs:

2025-10-15 10:59:26.322 DEBUG (MainThread) [roborock.version_1_apis.roborock_local_client_v1] [Jim Curvy] Disconnecting from 192.168.1.20
2025-10-15 10:59:26.322 INFO (MainThread) [roborock.version_1_apis.roborock_local_client_v1] [Jim Curvy] Roborock client disconnected

Do you not get any logs later this about it attempting to reconnect? Does it just stop right here in regards to the local client?

It is interesting in your other logs it fails during the hello. I can't quite make sense of that, but I'll try to think on it.

Do you get more of the Failed to connect in your logs over a longer period of time? If so - how many before it stops reconnecting?

[ctsdad]

I apologize. I started to but then realized that I had already deleted the devices and added them back. I also am trying as a temporary fix to use a separate email for the Home Assistant and the app and just share the vacuum. I noticed I always get a warning about being signed in on two devices. I know it would be just a band-aid situation but it would keep me from pulling my hair out for a bit.

…

On Wed, Oct 15, 2025 at 8:25 PM Luke Lashley ***@***.***> wrote: *Lash-L* left a comment (home-assistant/core#154476) <#154476 (comment)> @EyalRotem <https://github.com/EyalRotem> thanks for sharing your logs. Everyone else, I ask that whenever you are on a issue on github you share your logs. variations of 'same on X' blow up my messages and make it very difficult for me to parse out helpful information. Please always provide your device model and your logs so I can do my best to help you. Eyal, looking at your logs: 2025-10-15 10:59:26.322 DEBUG (MainThread) [roborock.version_1_apis.roborock_local_client_v1] [Jim Curvy] Disconnecting from 192.168.1.20 2025-10-15 10:59:26.322 INFO (MainThread) [roborock.version_1_apis.roborock_local_client_v1] [Jim Curvy] Roborock client disconnected Do you not get any logs later this about it attempting to reconnect? Does it just stop right here in regards to the local client? It is interesting in your other logs it fails during the hello. I can't quite make sense of that, but I'll try to think on it. Do you get more of the Failed to connect in your logs over a longer period of time? — Reply to this email directly, view it on GitHub <#154476 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AK6QM4EJT6INAZQP46Q52VL3X3QWXAVCNFSM6AAAAACJFQ6E5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMBYG4YTOMJWGA> . You are receiving this because you commented.Message ID: ***@***.***>

-- Chris Thompson, , CSAC-A,CPSS, AP Mobile: (252) 245-2855

[GeeEmm88]

Roborock Q Revo: 02.20.60
Roborock Q8 Max+: 02.07.60

Still losing connection daily, it auto-recovers after some time before it gets lost again

2025-10-16 01:22:06.854 WARNING (MainThread) [roborock.version_1_apis.roborock_mqtt_client_v1] [Roborock Q Revo] Attempting to create a future with an existing id 1 (0)... New id is 14596. Code may not function properly. 2025-10-16 01:22:06.857 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback RoborockFuture._set_result() (None) Traceback (most recent call last): File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run self._context.run(self._callback, *self._args) ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/roborock/roborock_future.py", line 19, in _set_result self.fut.set_result(item) ~~~~~~~~~~~~~~~~~~~^^^^^^ asyncio.exceptions.InvalidStateError: invalid state 2025-10-16 01:22:36.321 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None) Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/roborock/util.py", line 62, in _run_task response = await self.callback() ^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/roborock/version_1_apis/roborock_client_v1.py", line 102, in _async_value self._value = await self._send_command(self.attribute.get_command, None) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/roborock/version_1_apis/roborock_mqtt_client_v1.py", line 54, in _send_command await self._validate_connection() File "/usr/local/lib/python3.13/site-packages/roborock/cloud_api.py", line 259, in _validate_connection await self.async_connect() File "/usr/local/lib/python3.13/site-packages/roborock/cloud_api.py", line 188, in async_connect if connected_future := self._sync_connect(): ~~~~~~~~~~~~~~~~~~^^ File "/usr/local/lib/python3.13/site-packages/roborock/cloud_api.py", line 174, in _sync_connect self._mqtt_client.connect(host=self._mqtt_host, port=self._mqtt_port, keepalive=KEEPALIVE) ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/paho/mqtt/client.py", line 1435, in connect return self.reconnect() ~~~~~~~~~~~~~~^^ File "/usr/local/lib/python3.13/site-packages/paho/mqtt/client.py", line 1598, in reconnect self._sock = self._create_socket() ~~~~~~~~~~~~~~~~~~~^^ File "/usr/local/lib/python3.13/site-packages/paho/mqtt/client.py", line 4609, in _create_socket sock = self._create_socket_connection() File "/usr/local/lib/python3.13/site-packages/paho/mqtt/client.py", line 4640, in _create_socket_connection return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source) ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/socket.py", line 840, in create_connection for res in getaddrinfo(host, port, 0, SOCK_STREAM): ~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/socket.py", line 977, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ socket.gaierror: [Errno -3] Try again 2025-10-16 01:22:39.658 WARNING (MainThread) [roborock.version_1_apis.roborock_mqtt_client_v1] [Roborock Q Revo] Attempting to create a future with an existing id 0 (0)... New id is 14601. Code may not function properly.

2025-10-16 01:27:20.797 ERROR (paho-mqtt-client-) [roborock.version_1_apis.roborock_mqtt_client_v1] [Roborock Q Revo] Failed to connect (Client identifier not valid) 2025-10-16 01:27:20.799 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback RoborockFuture._set_result() (None) Traceback (most recent call last): File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run self._context.run(self._callback, *self._args) ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/roborock/roborock_future.py", line 19, in _set_result self.fut.set_result(item) ~~~~~~~~~~~~~~~~~~~^^^^^^ asyncio.exceptions.InvalidStateError: invalid state 2025-10-16 01:27:22.864 ERROR (paho-mqtt-client-) [roborock.version_1_apis.roborock_mqtt_client_v1] [Roborock Q Revo] Failed to connect (Client identifier not valid) 2025-10-16 01:27:22.865 ERROR (MainThread) [homeassistant] Error doing job: Exception in callback RoborockFuture._set_result() (None) Traceback (most recent call last): File "/usr/local/lib/python3.13/asyncio/events.py", line 89, in _run self._context.run(self._callback, *self._args) ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/roborock/roborock_future.py", line 19, in _set_result self.fut.set_result(item) ~~~~~~~~~~~~~~~~~~~^^^^^^ asyncio.exceptions.InvalidStateError: invalid state

[EyalRotem]

@Lash-L
Thanks for looking into this.
I trimmed the log because it repeats the same disconnect/reconnect lines over and over—essentially the same as:

2025-10-15 10:58:40.316 DEBUG (MainThread) [roborock.version_1_apis.roborock_local_client_v1] [Jim Curvy] Disconnecting from 192.168.1.20
2025-10-15 10:58:40.316 INFO (MainThread) [roborock.version_1_apis.roborock_local_client_v1] [Jim Curvy] Roborock client disconnected

It loops with every attempt, without additional details.

Notice though that the first log is where the device goes unavailable where the ERROR messages are.

Some additional info:

• After re-adding the integration, things work as expected for a while.
• The device seems to go unavailable mainly during or after a long cleaning session (usually after ~1.5 hours).
• When the issue happens, simply reloading the integration doesn’t help, but disabling it for a while and then enabling again does restore connection.

If it’s helpful, here’s a typical sequence:

1. Integration enabled (was disabled for a few days before)
2. Robot starts cleaning via Home Assistant
3. After ~1.5 hours, it goes unavailable (no response, repeated disconnects)
4. Reloading the integration does not fix it
5. Disabling the integration for several hours, then re-enabling, does

Let me know if you’d like a raw/full log segment showing the repeating disconnects, or any other specific details.

Device model:
Roborock Q Revo Curv
roborock.vacuum.a135
Firmware: 02.27.38

EDIT: here's another log, what happend in real time is: robot cleaned, got unavailable, i restarted HA because other reasons - integration worked for a bit - then robot went unavailable again.

ha.log

[maciek226]

Same here
Device model: roborock qv 35a
Firmware: 02.27.90

WARNING (MainThread) [homeassistant.components.roborock] Not setting up Roborock QV 35A because we could not get the network information of the device. Please confirm it is online and the Roborock servers can communicate with it