-
-
Notifications
You must be signed in to change notification settings - Fork 569
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
Can't reach my mirobo #145
Comments
Hi, |
Downgrade to |
Thanks fanthos, yes I found solution few minutes ago in #142 as well. Pawel |
Ok so I updated protocol.py and device.py with your correction but it did nothing. I downgraded construct and seems ok :
ERROR:mirobo.vaccum is normal ? I unchanged the modification and I get no error now |
Yes, that error is normal if there is no such file / you have not run mirobo after the reboot of the device. That Did you try it out already with the recent master from git? There has been no release with the fix yet. |
Nop I used protocol.py and device.py you pushed here #142 But I am not good at all in Python so maybe I forgot something. I will try again when master will be updated to see if issue still happens |
@fanthos I Downgrade to construct==2.8.16 fix timeout error. but I had new error.. |
Hi,
I tried everything but I can't join my mirobo. Discover seems to work as I get the right IP but mirobo return this :
Can you help me ?
Regards
Infos :
System : Debian 9
Token extracted with aSQLiteManager from miio2.db
python-miio v0.3.2
Mirobo firmware : 3.3.9_003077
The text was updated successfully, but these errors were encountered: