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

Xiaomi Mi Robot (viomivacuum), command stability #800

Closed
fs79 opened this issue Aug 15, 2020 · 3 comments
Closed

Xiaomi Mi Robot (viomivacuum), command stability #800

fs79 opened this issue Aug 15, 2020 · 3 comments

Comments

@fs79
Copy link
Contributor

fs79 commented Aug 15, 2020

Describe the bug
When you send commands it takes a while and sometimes you get a timeout. I solved this by sending the command up to 20 times. (/usr/local/lib/python3.7/dist-packages/miio/device.py retry_count=20)
When I send the move forward command with a duration of 15 seconds it seems the 15 secs start when the command is sent the 1st time to the vacuum cleaner. So if the command needs a while the bot won't move forward 15 secs.
Possible to start the timer when the robot accepts the command?

Version information (please complete the following information):

  • OS: Linux, Python 2.7.16
  • python-miio: miiocli, version 0.5.3

Device information:

  • Model: Xiaomi Mi Robot Vacuum Mop Pro
    Model: viomi.vacuum.v8
    Hardware version: Linux
    Firmware version: 3.5.3_0017

To Reproduce
miiocli viomivacuum --ip 10.0.. --token 1234 move forward --duration 15

Expected behavior
Device should start and move forward for the seconds give, p.e. 15 secondes

@fs79 fs79 changed the title Xiaomi Mi Robot Xiaomi Mi Robot (viomivacuum), command stability Aug 15, 2020
@rytilahti
Copy link
Owner

The miiocli doesn't keep a record of the recently used sequence ids which is the likely cause for this. I have had plans to consolidate the solution used by mirobo to miiocli, but I haven't found time to do that nor will I have in the near future.

So if anyone is interested on working on adding support for a device database/cache of sorts to the miiocli to fix this, all help is welcome!

@fs79
Copy link
Contributor Author

fs79 commented Sep 13, 2020

Maybe related to this issue.
#813

@rytilahti
Copy link
Owner

Yes, that's related. Only mirobo tool (which works only with rockrobo vacuums) does keep track of used sequence ids.

@fs79 fs79 closed this as completed Jul 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants