-
-
Notifications
You must be signed in to change notification settings - Fork 86
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
Incorrect fan speed values for Roborock S5 #253
Comments
Please supply correct details based on these specs: https://home.miot-spec.com/spec/roborock.vacuum.s5 It's currently implemented lik this: 1: 101: Quiet I wont change the names, because they keep changing them on every new model and I cant create a custom capability for each model. |
Those specs are outdated or incomplete as it misses the Gentle value. I think it would be the best to have fan speeds related to a model. For example:
|
Feel free to submit a PR where you create a custom capability to match each model. It wont be added by me as I have beter things to do with my life.
That would be the best solution for you. I have to consider about 12000 other users that also only think from their own perspective. I'll keep this request open to see if more users are missing this. |
I can see your point. However, I am curious. You think it is fine/better how it is behaving right now? |
For now it's better for most users yes as I'm unsure other models have this gentle option. Changing it will affect a lot of users. I understand you only look at your own use case but I have to support 12000+ users. And I need to do all that in my free time without getting much appreciation for it anyway. So yes, I cut corners. Just create your flows to use the right option even though the text doesn't match. |
Hi,
The fan speed values for Roborock S5 (roborock.vacuum.s5) are actually incorrectly set to different values.
In fact, Gentle should be something like 0. It can be used for mopping without vacuuming (fan is off).
Otherwise, it is working fine. Just the list of values is incorrect/incorrectly mapped.
The text was updated successfully, but these errors were encountered: