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

Support Roborock Q Revo(roborock.vacuum.a75) #1796

Closed
bchen290 opened this issue Jul 15, 2023 · 7 comments · Fixed by #1841
Closed

Support Roborock Q Revo(roborock.vacuum.a75) #1796

bchen290 opened this issue Jul 15, 2023 · 7 comments · Fixed by #1841

Comments

@bchen290
Copy link

If you are receiving a warning indicating an unsupported model (Found an unsupported model '<model>' for class '<class>'.),
this means that the implementation does not list your model as supported.

If it is working fine for you nevertheless, feel free to open an issue or create a PR to add the model to the _supported_models (example) for that class.

Before submitting, use the search to see if there is an existing issue for the device model, thanks!

Device information:

Use miiocli device --ip <ip address> --token <token>.

  • Model: roborock.vacuum.a75
  • Hardware version:
  • Firmware version:
@DennYoDeluxe
Copy link

same Issue:
Found an unsupported model 'roborock.vacuum.a75' for class 'RoborockVacuum'. If this is working for you, please open an issue at https://github.com/rytilahti/python-miio/

Running the very new Roborock Q Revo

@mindgam3s
Copy link

+1

@Darkside138
Copy link

Bump, have this vacuum and it's working great with the integration

@littlesteve01
Copy link

Hallo, ist this Model working/supported?

@rytilahti
Copy link
Owner

rytilahti commented Oct 10, 2023

So what exactly is not working? Most (if not all) roborock vacuums should be supported but there may be some missing features depending on the model.

If the device is working as expected, we can suppress the warning (see the linked PR).

@lmuser22
Copy link

getting this Report für my A75

Output:

WARNING:miio.device:Found an unsupported model 'roborock.vacuum.a75' for class 'ViomiVacuum'. If this is working for you, please open an issue at https://github.com/rytilahti/python-miio/
WARNING:miio.integrations.vacuum.viomi.viomivacuum:Unknown vacuum state: None
Traceback (most recent call last):
File "/usr/local/bin/miiocli", line 8, in
sys.exit(create_cli())
File "/usr/local/lib/python3.9/dist-packages/miio/cli.py", line 66, in create_cli
return cli(auto_envvar_prefix="MIIO")
File "/usr/local/lib/python3.9/dist-packages/miio/click_common.py", line 51, in call
return self.main(*args, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1078, in main
rv = self.invoke(ctx)
File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/miio/click_common.py", line 310, in wrap
result_msg = result_msg_fmt.format(**kwargs)
File "/usr/local/lib/python3.9/dist-packages/miio/integrations/vacuum/viomi/viomivacuum.py", line 325, in bin_type
return ViomiBinType(self.data["box_type"])
File "/usr/lib/python3.9/enum.py", line 360, in call
return cls.new(cls, value)
File "/usr/lib/python3.9/enum.py", line 677, in new
raise ve_exc
ValueError: None is not a valid ViomiBinType

@rytilahti
Copy link
Owner

@lmuser22 you need to use miiocli roborockvacuum to control roborocks, you are somehow trying to control yours as a viomi vacuum which isn't obviously working.

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

Successfully merging a pull request may close this issue.

7 participants