-
Notifications
You must be signed in to change notification settings - Fork 6
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
Fan Speed Discrepancies for i max series #82
Comments
Looks like the i max series speed runs from 0-91 instead of 0-100. I only have classic and protect series and they all run from 0-100. I'll leave this ticket for somebody with an i max to tackle. |
OK - thank you. I do know have the knowledge to fix the problem, but if someone is willing I would be happy to help test. |
Ok so it seems like when talking just to the raw api and looking at the app the minimum is 11 (anything less is 'standby' mode) and the max is 88. It is super weird I have no idea why they did that. |
I feel like adding different model handling might be a good idea due to the variance between them @dahlb? Not sure how you'd want to implement it if at all but that can be in a separate discussion I feel |
these are some great insights to the i max api. I am not inclined to add model specific handling of the raw values to try and normalize the blueair api for them, that seems likely to reduce overall reliability of the integration. I've found my two protects each have a clear change in volume based on the % set in the api. I'd guess the same is true for most of the models, and while these insights can be helpful to others I don't think we should codify them. |
Hello! Thanks for your work on this! I noticed with the 411i Max and 311i Max there is a discrepancy between the fan speed reported in the Blueair app and the attribute reported in HA. For example, when the fan is running at full speed, it is shown as only 91% in HA.
Here is what I found:
App -> HA
0 -> 0
12 -> 11
16 -> 15
21 -> 19
25 -> 23
30 -> 27
34 -> 31
38 -> 35
43 -> 39
47 -> 43
52 -> 47
56 -> 51
60 -> 55
65 -> 59
69 -> 63
74 -> 67
78 -> 71
82 -> 75
87 -> 79
91 -> 83
96 -> 87
100 -> 91
Any idea what is causing this and how it can be fixed?
The text was updated successfully, but these errors were encountered: