-
-
Notifications
You must be signed in to change notification settings - Fork 563
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
miiocli viomivacuum status not working for STYJ02YM (viomi.vacuum.v8, fw: 3.5.3_0017) #1003
Comments
@bkupidura you may want to check out #1014 which should make it a bit easier to find out which properties are not working for your device :-) |
@bkupidura do you have any progress with that? |
@ontaptom Unfortunately no. Didnt had time to look at that. :( |
@bkupidura I do have the same device running on the same firmware version. I’m running Home Assistant OS on a Raspberry Pi. If you could explain how I can execute the |
@Didel command mentioned by @rytilahti will require manually patching python-miio package (or installing package manualy), as afaik HA is still using older version. If you dont feel comfortable with that, i would suggest not modyfiying anything in HA container - as i will not be able to help with reverting any changes. Steps bellow will not do any harm to yours HA installation - but probably step 4) will fail because of missing #1014 You can check that with:
Im not using HA OS, so this is based on https://developers.home-assistant.io/docs/operating-system/debugging/ and not on my experience. |
@bkupidura I had some success today with adding my viomi.vacuum.v8 to HA. However, on the bottom side of my vacuum the model is listed as: STYTJ02YM. Can you verify with yours? I read that .v7 is STYJ.. and .v8 is STYTJ..
Hope that helps :) |
To improve the support in this library (and in turn help to get out-of-the-box support for homeassistant at some point), it would be useful if anyone with v8 and v9 could use the test properties and report back here:
This needs to be run with the current git version until there will be a new release:
poetry installs the git version on its own virtual environment, and shouldn't thus cause any problems to any system-wide installations with the caveat of requiring to run |
@rytilahti hope this helps:
Run against:
|
@ontaptom great, thanks! From the looks of it, the logic behind testing how many properties to request at once is a bit broken.. Could you rerun the command with After that, you could re-try the command without the property which should now report with more max properties than 2 :-) edit: feel free to try the linked PR which makes the command more verbose for easier testing. |
@rytilahti I had to remove quite few of them to have that command run successfully. Removed properties:
Each of them gave me an error The full command and output once those were eliminated:
|
Hi, i have same device as @ontaptom, output from #1024 is:
|
@ontaptom the last commit on the PR considers empty lists (which seem to be those that cause problems) as invalid properties, maybe it works now? @Skelly82 thanks! We need now someone with v9 to perform the same test so that we can adjust the list of usable properties depending on the device :-) Ping @titilambert Could you please test if other commands on |
@rytilahti running the full command with last commit on the PR:
Definitely handles better the empty lists :) As of miiocli viomivacuum commands, I tried:
Unfortunately the most interesting one (I suppose) get_rooms didn't work :/
|
Thanks again for testing! So these are the extra properties that are supported by v9 and not on v8 (from the currently enabled ones, some of those I gave earlier were commented out): {'map_num', 'cur_mapid', 'mop_route'} Skipping these for v8 should make Alas, I don't have any idea about the map/room functionality :-( |
.. EDIT: and "status" is not working for me although : {'map_num', 'cur_mapid', 'mop_route'} are commented out ResultsModel: |
As far as I understand, the issue is that the device skips None values in the For instance, if you're requesting For my Home Assistant integration, I've made a patch for ViomiVacuum class with an override of |
Describe the bug
miiocli viomivacuum status is broken for STYJ02YM with firmware 3.5.3_0017.
Looks like vacuum is returning less properties than expected.
List of available properties can be found https://github.com/nqkdev/home-assistant-vacuum-styj02ym/blob/master/vacuum.py#L122, i see that nqkdev is not using all available - but this can be start point for further investigation.
Version information (please complete the following information):
Device information:
Model: viomi.vacuum.v8
Hardware version: Linux
Firmware version: 3.5.3_0017
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Status command working
Console output
The text was updated successfully, but these errors were encountered: