dlarrick

I am going to reword this a bit and take the basic idea.

I cribbed some of your text to improve this section. Thanks!

OK, I finally had some time to research this issue. Here's what I found: https://developers.home-assistant.io/blog/2024/01/24/climate-climateentityfeatures-expanded/ TL;DR: If an integration supports climate.turn_on / climate.turn_off it needs to set the proper ClimateEntityFeature...

The change in this PR: https://github.com/dlarrick/hass-kumo/pull/163/files is what you tried? And it's not working for you? That user reported success. Just for a sanity check, is your main HomeAssistant version...

Your earlier one was more correct I think. The 2nd attempt is missing TURN_ON (and has FAN_MODE twice but that should not matter). So let me ask again, what version...

Hmm that's odd. It should not contact Kumo Cloud at all, ever, once initially set up, if "prefer cache" is turned on. If that's no longer true, we should definitely...

If you're willing, follow the procedure on the pykumo README, supplying it with your kumo_cache.py rather than having it prompt you. `account = pykumo.KumoCloudAccount(username, password, kumo_dict=cached_json)` Then see if you...

I'm glad it's working for you now, and I hope your Internet comes back w/o issue. The behavior here is the result of evolution of control, and also choosing strategy...

This is pretty common. The integration gets the units' local IP address from the KumoCloud service. If you chose "prefer cache" at setup, this is done only once, at setup....

I think that log is unrelated. See https://github.com/dlarrick/hass-kumo/issues/137 which will get fixed at some point. This should not prevent Kumo from functioning. Going Unknown is likely something else. One of...