-
-
Notifications
You must be signed in to change notification settings - Fork 32.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Xiaomi_miio: Error on device update (Vacuum) #43836
Comments
Hey there @rytilahti, @syssi, @starkillerOG, mind taking a look at this issue as its been labeled with an integration ( |
Could you please try
|
|
same issue on my side |
My Xiaomi Vacuum Mop v2 is "unavailable" |
I have same problem. |
Same issue. On first attempt, I got After that, I pinged that IP, it only responded after a few seconds. On my second attempt, I got the same log as faaafo. |
@faaafo for the timezone problem, please create an upstream issue at https://github.com/rytilahti/python-miio/ . For some reason the device is not reporting the timezone information correctly, which is required for the timer functionality. However, the missing timer information should not cause a verbose exception since #41330 (merged already in October) so you should simply try to update to a newer homeassistant version to see if it fixes it, with the caveat of not having timer information available for homeassistant. |
I Have :)
|
@rytilahti Thank you for chiming in. Updated the underlying host and homeassistant (2020.12.1) as well. Alas to no avail. Will gladly follow your suggestion, open an issue on python-miio and keep you/this issue posted |
@faaafo thanks for chiming in back, too! Okay, that's a bit odd. Does the stacktrace in the logs still look similar, i.e., crashing inside timezone request handling? |
i use - platform: miio2 and it's work but / - platform: xiaomi_miio it's not work. error miio2 but it's work Got exception while fetching the state: Unable to discover the device 192.168.2.129 |
miio2 it work pic |
Current log
|
@ShifuEst What is miio2? |
@faaafo ah, indeed, the PR I linked fixes only the cases where a miio2 is a custom fork of the integration for some non-rockrobo (viomi) devices. Issues with that should be reported to its developer and not in this repository. |
https://github.com/nqkdev/home-assistant-vacuum-styj02ym this is miio2 and it's work |
if I use vacuum:
|
Update of vacuum.robottolmuimeja is taking over 10 seconds |
if I use miio2 then is ok :) |
vacuum:
|
look miio2 platform work. :) |
Moi. |
Same error for the no roborock S7:
|
@vukisz that looks like a completely different problem (protocol incompatibility) than the ones mentioned earlier. Could you please activate debug logger for @ShifuEst moi moi :-) |
The timezone issue should have been fixed for a long time ago already (0.5.5, rytilahti/python-miio#949), and a fix to the s7 issue got fixed in 0.5.6 which is used by 2021.5.1, so I'm closing this now. |
The problem
I can’t tell since when I got this error. Updating the raspi host nor hassio(docker) didn’t help.
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
Running
mirobo
on the raspi or docker instance works as well:The text was updated successfully, but these errors were encountered: