-
-
Notifications
You must be signed in to change notification settings - Fork 163
Time out on device initialization #725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is a nice found I will investigate that, thanks. Miio protocol has limit of maximum 15 properties at a time for all the devices that are using it but I don't think it is a size issue because vacuum can return raw map data over local protocol when it is mapping and it can grow very huge. |
I can confirm that this issue also occurred with my |
For my c102gl I also had to set the props down to 5 on the latest beta release v2.0.0816 |
same here, adjusting the value down to 5 fixed the issue for me |
I have decided not to modify this value on the release because there are too many people having no issues with it. |
Could you explain how this could be related to network or ISP settings? |
+1 local connection was not working at all (no response from device), cloud connection was ok. |
Just chipping in as this happened to me today. I want to mention that changing the lines suggested above worked for me too:
I also don't see how this could be related to my network nor my ISP. To further shed light into this:
Probably the major release of HA broke it. The thing is that I now have custom code in the Attaching some DEBUG logs, just in case it helps:
Thanks for the help. |
Describe the bug
Initialization of the vacuum does not work (Time out). Configuration of the device works, but the integration can not load the device.
To Reproduce
Use an L10s Ultra with firmware 4.3.9_3204 like in #482 or #342
Expected behavior
The integration should load the device correctly and not time out.
Additional Information (please complete the following information)
I have analysed the problem. The log points to line 262 in device.py, where the properties are requested from the device. The timeout occured in the fourth request inside the loop, so properties 45-60. I tried to get the exact property that causes the timeout, but when I requested less properties, no time out occured. I have changed the code to only request 10 properties at a time and now it initializes the device correctly. I don't really know why this works perhaps the request or response is too big for the exact combination.
So a fix that worked for me is to change lines 262 and 265 inside device.py from the value 15 to 10.
The text was updated successfully, but these errors were encountered: