-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
Roborock Qrevo S causes warnings and log spam #120148
Comments
Hey there @humbertogontijo, @Lash-L, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) roborock documentation |
can you send me a screenshot of all of your fan speed options in the app |
@Lash-L Here you go: The options are named Quiet, Balanced, Turbo, Max and Max+. |
How is it in the latest release? |
I always upgrade my production system to a new HA version at the end of the month, I will let you know. |
@Lash-L Now only missing the dock type:
|
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
@Lash-L With Home Asssistant 2024.10.2 I still see the missing dock type warning. |
The problem
There are many warnings logged by the Roborock integration for our Qrevo S. I guess it is not fully supported.
Showing these warnings once per startup is enough by the way.
What version of Home Assistant Core has the issue?
core-2024.6.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Roborock
Link to integration documentation on our website
https://www.home-assistant.io/integrations/roborock
Diagnostics information
config_entry-roborock-929a94b1fb394c7091eda13d77ac5291.json
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: