Nightly error line in the log

[vturekhanov]

The problem

Every night approximately in the same time I find an error line in the HA log (see attached). Not sure if it's normal.

What version of Home Assistant Core has the issue?

core-2023.7.3

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

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2023-08-06 03:21:24.477 ERROR (MainThread) [homeassistant.components.roborock.coordinator] Error fetching roborock data: Failed connecting to 192.168.1.15
2023-08-07 03:21:33.448 ERROR (MainThread) [homeassistant.components.roborock.coordinator] Error fetching roborock data: Failed connecting to 192.168.1.15
2023-08-08 03:21:37.448 ERROR (MainThread) [homeassistant.components.roborock.coordinator] Error fetching roborock data: Failed connecting to 192.168.1.15

Additional information

No response

[home-assistant[bot]]

Hey there @humbertogontijo, @lash-l, 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.

_{^{(message by CodeOwnersMention)}}

---

roborock documentation roborock source _{^{(message by IssueLinks)}}

[BlastyCZ]

Same issue here, just different time, every day at 3:42:XX. WiFi logs show nothing except it reconnects immediately. I was thinking it's only my issue because Shelly behave kind of similar so I was about catching pcap for that time to dig deeper - there are only these two devices on that WiFi. But it's at least for me minor issue so I haven't done the pcap thing. And to be clear - it isn't related to DHCP, I have 1h lease time.

[Lash-L]

If it is dropping off your network and reconnecting, that is the devices fault and there isn't anything we can really do about it unfortunately. Does that appear to be the case?

The Roborock vacuums do some weird things with their wireless connection.

[vturekhanov]

My vacuum cleaner also seems to be disconnecting from WiFi. Other WiFi devices work fine.

03:21:29 12.08.2023 Left
03:21:54 12.08.2023 Connected

2023-08-12 03:21:26.541 ERROR (MainThread) [homeassistant.components.roborock.coordinator] Error fetching roborock data: Failed connecting to 192.168.1.15

[BlastyCZ]

I would really apreciate if there is some kind of (optional?) timeout before device is marked as unavailable. I don't know what the options are in the integration.

[lanfill]

I am seeing the same thing:

[lanfill]

I get this in the logs:

2023-08-18 13:09:37.369 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry XXXXXXX@XXXX.XXXX for roborock
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 388, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/roborock/__init__.py", line 45, in async_setup_entry
    network_results = await asyncio.gather(
                      ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/roborock/api.py", line 489, in get_networking
    return await self.send_command(RoborockCommand.GET_NETWORK_INFO, return_type=NetworkInfo)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/roborock/api.py", line 389, in send_command
    response = await self._send_command(method, params)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/roborock/cloud_api.py", line 195, in _send_command
    return await self.send_message(roborock_message)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/roborock/cloud_api.py", line 173, in send_message
    (response, err) = await async_response
                      ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/roborock/api.py", line 321, in _wait_response
    raise RoborockTimeout(f"id={request_id} Timeout after {QUEUE_TIMEOUT} seconds") from None
roborock.exceptions.RoborockTimeout: id=15464 Timeout after 4 seconds

if I delete and re-authenticate it works fine until 3:42AM the next day.

[vargylet]

I have the same issue. I also used to have this issue before when I used the Xiaomi app and integration instead of the Roborock app and integration. Probably caused by the device.

[IetIesAai]

Since the disconnection seems to be quite short (about 30 seconds in my case) - wouldn't a longer timeout be sufficient? In some integrations you can configure this on the integrations page....

I don't mind the error as much as that it makes all the (monitored, in ly case) sensors go unavailable for a very short time.... Of course one can work around the notification, but would be better if that's not needed ;-)

[lukas-kraus]

Same problem here

[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.

[BlastyCZ]

No change over the time. There is still log record every day at the same time. The timeout setting is not possible?

[JacquesRodrigues]

I've got the same issue, every night there is an error in the log.

"Error fetching roborock data: Failed connecting to 192.168.1.230 Error fetching roborock data: id=19727 Timeout after 4 seconds Error fetching roborock data: id=15407 Timeout after 4 seconds"

My device has a static IP.

[sven-debug]

I have this issue as well. Would be nice to fix that one. Basically the leaning robot works fine. But there might be an exeption that is not properly caught yet.

Logger: homeassistant.components.roborock.coordinator
Quelle: helpers/update_coordinator.py:347
Integration: Roborock (Dokumentation, Probleme)
Erstmals aufgetreten: 19. Mai 2024 um 03:34:37 (7 Vorkommnisse)
Zuletzt protokolliert: 03:34:47

Error fetching roborock data: Failed connecting to 192.168.178.26
Error fetching roborock data: id=18044 Timeout after 4 seconds
Error fetching roborock data: id=23977 Timeout after 4 seconds
Error fetching roborock data: id=26477 Timeout after 4 seconds

[realjax]

same issue here at 3:42 at night.

[pauldcomanici]

Similar issue here, a lot of errors in logs like:

2024-08-19 10:15:30.754 ERROR (MainThread) [homeassistant.components.roborock.coordinator] Error fetching roborock data: id=31503 Timeout after 4 seconds

[Florian-Schmidt]

Subscribing to this issue as my Roborock gets unavailable in irregular periods and integrations needs to be restarted. In my case I guess it's because of WiFi roaming between mesh routers.

Error fetching roborock data: Failed connecting to 192.168.x.x

[Otiel]

Same error, but each time it happens, it matches with the Roborock entity becoming unavailable for a short time:

It's not limited to one time per night, neither at 3:42 like some others though.