viomi.vacuum.v18 stopped working with checksum error
See original GitHub issueThe vacuum was working yesterday just fine with 2 discovered entities (vacuum and battery) but today I get this error:
Got MiioException while fetching the state for Viomi S9 Robot Cleaner: Got checksum error which indicates use of an invalid token. Please check your token!
Token was correct extracted with the Miot Auto component or xiaomi_token_extractor.exe
I tried reconnecting to wifi and refresh the token but the error is the same with the new token. I tried v0.3.4, v0.3.5 and latest
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Xiaomi integration for miio devices issue - Configuration
I have raised it with rytilahti/python-miio but not sure how it ... Same problem: viomi.vacuum.v18 stopped working with checksum error ...
Read more >Xiaomi Robot Vacuum Binding - #1934 by marcel_verpaalen
My Mijia Vacuum Robot (viomi.vacuum.v7) has worked. I can get all of its parameters (and set some others), as also control it to...
Read more >Rooting the Xiaomi STYJ02YM (viomi-v7) Vacuum Robot
My motivation to get root access is to have a talking and blinking robot that can move through my flat and is independent...
Read more >How to Force Reset Viomi SE Robot Vacuum Cleaner by Xiaomi
In just a few seconds you will be able to restore settings and bring back normal Xiaomi Viomi Vacuum working mode. If you...
Read more >python-mirobo - Bountysource
Python library & console tool for controlling Xiaomi Vacuum cleaner robot ... miiocli viomivacuum status not working for STYJ02YM (viomi.vacuum.v8, ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That bug seems resolved. Vacuum gets discovered with many status attributes populated.
Is this bug solved ?