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

New ERROR (after unit has been restarted?): Fan mode is not valid. Valid fan modes are: quiet, low, powerful, auto #150

Open
joergbattermann opened this issue Jun 24, 2024 · 2 comments

Comments

@joergbattermann
Copy link

I was just doing something else on my HA system when I got a notification in the lower left corner saying "Fan mode is not valid. Valid fan modes are: quiet, low, powerful, auto". I had never seen that before so I checked the Settings > System > Logs and saw this:

image

I know what happened to cause the communication timeout (I restarted the AP the Kumo Cloud unit connects to) but I have never seen that particular error before (when wifi went away for a minute or two).

Maybe one related question: is there any way to configure the amount of retries / time waited etc? The restarts of the Kumo Cloud unit also temporarily stop the heatpump as far as I know and I'd probably be a bit more lenient for my particular environemnt if I could configure these values.

Thanks!

@dlarrick
Copy link
Owner

I'm not surprised. The integration fetches the supported fan modes from the unit itself. So if it can't talk to the unit, it can't figure out what the modes are.

@joergbattermann
Copy link
Author

Yeah makes sense that it would complain about that but for some reason I assumed once fetched (initially during setup), that info would be stored/cached.. the units' modes rarely (if ever) change and that's why I was surprised by the ERROR side of things vs just WARNINGs.

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

No branches or pull requests

2 participants