Initial support for Vacuum 1C STYTJ01ZHM (dreame.vacuum.mc1808)

[legacycode]

I own a Vacuum 1C STYTJ01ZHM and added support for it. This PR is based on the branch https://github.com/rytilahti/python-miio/tree/dreame_miot_mc1808

I tested every method with my own device and they all are working.

Usage: miiocli dreamevacuummiot [OPTIONS] COMMAND [ARGS]...

Options:
  --ip TEXT     [required]
  --token TEXT  [required]
  --help        Show this message and exit.

Commands:
  home                  Return to home.
  identify              Locate the device (i am here).
  info                  Get miIO protocol information from the device.
  raw_command           Send a raw command to the device.
  reset_filter_life     Reset filter life.
  reset_mainbrush_life  Reset main brush life.
  reset_sidebrush_life  Reset side brush life.
  start                 Start cleaning.
  status                State of the vacuum.
  stop                  Stop cleaning.

miiocli dreamevacuummiot --ip xxx --token xxx status

Battery level: 86
Brush life level: 100
Brush left time: 300
Charging state: not_charging
Cleaning mode: default
Device fault: no_faults
Device status: idle
Filter left level: 150
Filter life level: 100
Life brush main: 18000-18000
Life brush side: 12000-12000
Life sieve: 9000-9000
Map view: tmp
Operating mode: fixme14
Side cleaning brush left time: 200
Side cleaning brush life level: 100
Timer enabled: False
Timer start time: 22:00
Timer stop time: 8:00
Voice package: DE
Volume: 14

BTW: Where can i find the technical json file? I have seen that the previous file was generated?

Thanks for your suggestions and best regards.

[legacycode]

@rytilahti i dont know why this build fails. Can you give me a hint?

[rytilahti]

Hey, it's coming from using model in SUPPORTED_MODELS.keys(): https://dev.azure.com/python-miio/python-miio/_build/results?buildId=901&view=logs&jobId=13848698-6df7-53ab-f6ce-57fb993c05be&j=13848698-6df7-53ab-f6ce-57fb993c05be&t=4316697d-697e-5b3b-d95b-644457d92942 - where model in SUPPORTED_MODELS is expected.

If you have installed pre-commit hooks, it will run automatically pre-commit, but you can also always run the tests run by the CI using pre-commit run -a in the source directory.

For the JSON file, check out devtools directory and its README :-)

[rytilahti]

Thanks for the PR, some comments from a very brief initial review.

This will make #683 obsolete, right?

[legacycode]

Thanks for the PR, some comments from a very brief initial review.

This will make #683 obsolete, right?

Correct #683 can be closed and the branch can be deleted.

[legacycode]

Hey, it's coming from using model in SUPPORTED_MODELS.keys(): https://dev.azure.com/python-miio/python-miio/_build/results?buildId=901&view=logs&jobId=13848698-6df7-53ab-f6ce-57fb993c05be&j=13848698-6df7-53ab-f6ce-57fb993c05be&t=4316697d-697e-5b3b-d95b-644457d92942 - where model in SUPPORTED_MODELS is expected.

If you have installed pre-commit hooks, it will run automatically pre-commit, but you can also always run the tests run by the CI using pre-commit run -a in the source directory.

For the JSON file, check out devtools directory and its README :-)

Thanks, but i did not change the heater.py file. On my machine there are no errors when running the pre-commit scripts:

docformatter.............................................................Passed
flake8...................................................................Passed
bandit...................................................................Passed

[rytilahti]

@legacycode the precommit output looks odd, considering that there are more checks since #915 and the current master was checked clean... Anyway, that's not your problem, but please add an entry to the README.md for this new supported device, then this is ready to be merged!

Note, that the API (including status enums) may be adapted in the future to allow common interface among different vacuum types to simplify using the library for downstream users (like homeassistant).

[legacycode]

@rytilahti I added the device to the readme file.

[rytilahti]

Thanks again for the PR, @legacycode! 🥇