Skip to content
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

0.5.0 / 0.5.0.1 breaks viomivacuum status #694

Closed
Bene2103 opened this issue May 8, 2020 · 1 comment · Fixed by #695
Closed

0.5.0 / 0.5.0.1 breaks viomivacuum status #694

Bene2103 opened this issue May 8, 2020 · 1 comment · Fixed by #695
Labels

Comments

@Bene2103
Copy link

Bene2103 commented May 8, 2020

First of all, thank you guys very much for this awesome piece of software!

I'm using miio with my Xiaomi STYJ02YM which should be the same as some vacuum from Viomi.

I've used python-miio 0.4.8 for quite some time and now decided to upgrade to the actual version because of the improvements which were made to the viomivacuum.

Python-miio 0.4.8 works really well, every command i've done works like a charm.
info:
Bildschirmfoto 2020-05-08 um 15 43 34
status:
Bildschirmfoto 2020-05-08 um 15 45 19

Upgraded to 0.5.0.1 i i've seen me confronted with the following output:
info (which works as it should):
Bildschirmfoto 2020-05-08 um 15 46 13
status:
Bildschirmfoto 2020-05-08 um 15 46 58

Is there anything i've done wrong? Or anything i can fix myself?

The next thing is the following.
The robot works fine for some time until it gets unresponsive to python-miio. This was discussed before in some other threads. The only way to communicate with the robot is a power-cycle.
Some quick fix witch doesn't work for me
#550 (comment)
Here is some explanation for the problem
#597 (comment)

I've also tried the installed firmware on the vacuum and updated the vacuum to the newest firmware. The problem still persists.

Is there any fix for this? I'd like to contribute as much as i can! (despite my very low programming skills)

Thank you!

@rytilahti
Copy link
Owner

Thanks for the report, that broke as the naming got changed during improving the presentation. Please check out the linked PR to see if it works!

Unfortunately I have no fix for the connectivity issues, but that should be a separate issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants