Improve Viomi support (status reporting, maps)

[titilambert]

This PR refactors viomi vacuum (like STYJ02YM)

I tested all the attributes with STYJ02YM.
I re-organised the commands to stick with the android UI.
I added also some commands:

• maps management
• list rooms
• cleaning specific room

[coveralls]

Coverage decreased (-0.1%) to 73.831% when pulling dd83750 on titilambert:viomi_status into 93b7a77 on rytilahti:master.

[titilambert]

@rytilahti ping

[rytilahti]

Thanks for the PR! I did a quick initial review, do you have plans to figure out the unknown variables and are you sure requesting so many variables is not breaking some limits?

edit: some of the consumables are duplicates and already available thanks to #805?

[rytilahti]

@titilambert Ping? Could you also update the description for the PR?

[titilambert]

@titilambert Ping? Could you also update the description for the PR?

done

[titilambert]

@rytilahti I made a refactoring to have something structured like the android app.
I added a big module docstring to explain what is missing or not.
I still need to test some properties.
After that, I guess, we could merge this PR.
Then, the thing missing will be the management of the scheduled cleanup !

[syssi]

@titilambert Take a look at your inbox. I've sent you an e-mail (subject: "Some material to support your viomi PR").

[titilambert]

@titilambert Take a look at your inbox. I've sent you an e-mail (subject: "Some material to support your viomi PR").

Thanks ! I already had this file but only for viomi.v7
I think I got everything I can (for now)

[titilambert]

@rytilahti I found a way to create a map in live using Pillow.
Once this PR is merged, I will create a new one just for this feature
Are you open to add Pillow as dependency in the project ?

[titilambert]

@rytilahti I think this PR is now ready !

[titilambert]

@rytilahti The PR is now rebased

[titilambert]

@rytilahti need to get PR #884 merged, then I rebase this one and It will be ready for review

[jeremysherriff]

There is a lot of comments in this PR, and it's very hard to see what is now resolved and what still needs work.
I would like to help, please ignore if the following is not useful;

edge_state is a toggle setting in the Mi Home app (so probably a boolean). The wording in English in the app is
Vacuum along the edges with description This setting is valid once. It will cause the vacuum to only vacuum the edges of the room/zone/map. The setting reverts to off/0/false once the clean-up completes or is cancelled.

repeat_state is also a toggle setting in the app. The wording in English in the app is
Secondary cleanup with description After enabling the cleanup will be repeated, only takes effect once. It makes the vacuum repeat the cleanup room/zone/map twice over (for extra clean!). The setting reverts to off/0/false once the clean-up completes or is cancelled.

Screenshot of these settings in app:

[jeremysherriff]

The voice volume is set using integers ranging from 1 to 10, represented in the app as 10% to 100%. I assume this is the same as other Xiaomi models?

Here's logs from the Mi Home app with me setting the volume to 90% and then back to 100%:

2021-02-03 19:50:31 -> {"id":1115,"method":"set_voice","params":[1,9]}
2021-02-03 19:50:31 <- {"code":0,"id":1115,"otlocalts":1612335031389261,"result":["ok"]}

2021-02-03 19:50:35 -> {"id":1117,"method":"set_voice","params":[1,10]}
2021-02-03 19:50:35 <- {"code":0,"id":1117,"otlocalts":1612335035817524,"result":["ok"]}

When disabling the voice, the parameters become [0,5] (presumably, "off" and "50%") and the app hides the volume setting. When re-enabling, the app sets the voice volume to 50% regardless of what volume it was originally. The following is the result of me disabling the voice when it is was 100% volume, and then re-enabling, and manually setting the volume back to 100%:

2021-02-03 19:57:40 -> {"id":4146,"method":"set_voice","params":[0,5]}
2021-02-03 19:57:40 <- {"code":0,"id":4146,"otlocalts":1612335461613965,"result":["ok"]}

2021-02-03 19:57:45 -> {"id":4148,"method":"set_voice","params":[1,5]}
2021-02-03 19:57:45 <- {"code":0,"id":4148,"otlocalts":1612335466505960,"result":["ok"]}

2021-02-03 19:58:48 -> {"id":4157,"method":"set_voice","params":[1,10]}
2021-02-03 19:58:48 <- {"code":0,"id":4157,"otlocalts":1612335528958184,"result":["ok"]}

[titilambert]

@rytilahti I just fixed all your comments and the tests are green :)

[rytilahti]

Okay, let's get it merged, thanks for the PR and for your patience! 🎉 For further improvements, let's try to do it more gradually (i.e., with smaller, self-contained changes) to make it easier & faster to review!

[k-0]

I've been experimenting with getting specific rooms cleaned, and realised that my Russian hacked Mi Home app is logging the vacuum calls. Here's a successful call to vacuum the Hallway with a single pass:

2021-01-29 15:53:50 -> {"id":163,"method":"set_mode_withroom","params":[0,1,1,15]}
2021-01-29 15:53:50 <- {"code":0,"id":163,"otlocalts":1611888830803511,"result":["ok"]}

As per previous, my rooms are:

jeremy@tvbox:~$ miiocli viomivacuum --ip=192.168.220.115 --token=3a5a32786e57457653576662xxxxxxxx get_rooms
Running command get_rooms
{'10': 'Bathroom', '12': 'Kitchen', '15': 'Hallway', '13': 'Living Room'}

I use this App too. Where can I find this log? Maybe there is a easy way to get the coordinates for zoned-cleaning.

[rezmus]

create /vevs/logs/ and kill app. you will find everything (also zone clean coords) in /vevs/logs/miio/did.txt where did is your device id.