core icon indicating copy to clipboard operation
core copied to clipboard

Roborock S7 - Got error when receiving: timed out

Open moulder6 opened this issue 1 year ago • 14 comments

The problem

Since yesterday I get:


Logger: miio.miioprotocol
Source: components/xiaomi_miio/__init__.py:239
First occurred: 13:09:57 (8 occurrences)
Last logged: 13:16:22

Got error when receiving: timed out

And the vacuum related stuff never loads.

Trying to setup the integration again doesn't go trough as it claims "Could not login to Xiaomi Miio Cloud, check the credentials.", although i can log in with the same credentials in the mi home app and Xiaomi Cloud.

What version of Home Assistant Core has the issue?

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

Xiaomi Miio

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

It doesn't seem to be related to home asistant version, as i tried rolling back and the issue persisted. The firmware version of the robbot is from a few days ago: 4.1.5_1536

moulder6 avatar Aug 08 '22 10:08 moulder6

Hey there @rytilahti, @syssi, @starkillerog, @bieniu, mind taking a look at this issue as it has been labeled with an integration (xiaomi_miio) you are listed as a code owner for? Thanks! (message by CodeOwnersMention)


xiaomi_miio documentation xiaomi_miio source (message by IssueLinks)

When I upgraded to 2022.8 from 2022.7.latest my vacuum entities were no longer valid. I switched back to 2022.7.latest and it worked again.

I have a roborock S7 using the Xiaomi Miio integration with the API key setup. I also have the custom:xiaomi-vacuum-card and I am using the custom xiaomi_cloud_map_extractor component. Both were no longer working because the vacuum entity was invalid.

bigbangus avatar Aug 08 '22 13:08 bigbangus

Here it was working fine with 2022.8 and 2022.8.1, but then the day 8.2 released it stopped working, and i wasn't able to setup it again, as the integration fails to login.

moulder6 avatar Aug 09 '22 09:08 moulder6

@moulder6 Could you provide a listing of all custom components of your setup?

ls -l config/custom_components

syssi avatar Aug 09 '22 09:08 syssi

I have these: image image

Even after disabling all of them, restart, and trying to setup xiaomi_miio again it claims that the credentials are incorrect.

moulder6 avatar Aug 09 '22 22:08 moulder6

Hey, I was wondering if there's additional information that i could provide to help sort this ou? Again, I am able to login in to the Xiaomi Mi Home App with the same details that the HA Integration claim are incorrect.

moulder6 avatar Aug 16 '22 06:08 moulder6

I try to set up the integration the manual route, but It seems the problem is due to Xiaomi adding 2 factor authentication to their accounts in the beginning of this year. Here's a related thread with people experiencing similar issues with the token extractors: Map Extractor quit working (Two factor authentication required)

Unfortunately I tried the proposed solution, and although i successfully go trough the process of verification in the browser, the token extractor still can't get trough.

moulder6 avatar Aug 17 '22 07:08 moulder6

Removing and re-adding the integration just fixed it for me.

bigbangus avatar Aug 17 '22 13:08 bigbangus

Got the same problem.

Re-adding is not working for me unfortunately

schol478 avatar Aug 18 '22 14:08 schol478

Same issue here, re-adding does not work. My S5 works, not the S7.

mariusjellum avatar Aug 19 '22 15:08 mariusjellum

So... After being stuck for a few days and running out of sms-es for verification a few times, after adding and removing the robot from the mi account, and adding it back, which led nowhere... I ended up deleting my old mi account, then creating another one, and added the robot to it... After doing that, i was able to use the new account to add the xiaomi miio integration again, without any problems. Let's see how long this lasts...

moulder6 avatar Aug 23 '22 14:08 moulder6

Hey guys I am having issues with integrating my Xiaomi Roborock S7 to HA. It used to work all well until the recent update to 2022.9.

It is not available on HA and I get this error message:

Logger: homeassistant.config_entries
Source: config_entries.py:388
First occurred: 13:26:21 (1 occurrences)
Last logged: 13:26:21

Config entry 'Roborock S7' for xiaomi_miio integration not ready yet; Retrying in background

Is there any work around this or any solutions? I tried removing and readding the component but it doesnt work for me.

Thanks.

bachoo786 avatar Sep 16 '22 12:09 bachoo786

Same here on HA 2022.10.4 with S7.

Source: helpers/update_coordinator.py:151 
Integration: Xiaomi Miio ([documentation], [issues]) 
First occurred: 04:09:03 (19 occurrences) 
Last logged: 04:35:48

Timeout fetching Roborock S7 data

mrwogu avatar Oct 16 '22 02:10 mrwogu

Check that your S7 is on the same VLAN as Home Assistant, that fixed it for me.

mariusjell avatar Nov 06 '22 11:11 mariusjell

Check that your S7 is on the same VLAN as Home Assistant, that fixed it for me.

Same problem for me. The S7 is on a different VLAN but I have a firewall rules which is OK for IP communication between my LAN and the S7. I can ping it from HA.

Is there another workaround to the Config entry 'Roborock S7' for xiaomi_miio integration not ready yet; Retrying in background

Loic691 avatar Nov 10 '22 09:11 Loic691

Same problem for me. The S7 is on a different VLAN but I have a firewall rules which is OK for IP communication between my LAN and the S7. I can ping it from HA.

Is there another workaround to the Config entry 'Roborock S7' for xiaomi_miio integration not ready yet; Retrying in background

I also had the communication between VLANs working, but even so what fixed it for me was moving it to the same VLAN as HA. I would try that.

mariusjell avatar Nov 16 '22 18:11 mariusjell

Some devices have a security feature that blocks communications from other subnets, and there is nothing the integration can do. See https://python-miio.readthedocs.io/en/latest/troubleshooting.html#discover-devices-across-subnets for details on that. If the device is not responding to requests while working for many other users, there is not much we as developers can do, so I'm closing this. If you have some more insights that this is caused by the integration or the backing library, please feel free to reopen this.

rytilahti avatar Jan 05 '23 01:01 rytilahti