They work fine, meet all my needs, and have never failed me (touch wood). That is why I bought them. They are exceptional thermostats for controlling HVAC systems. When I lose connectivity to them, I know they will work.
Remote access and HA integration are nice to have - there is no reason for me to upgrade my thermostats for this.
I still need to fiddle with this - nearly every day.
Mine has been stable since upgrading to 2023.4.4. I still get warnings in the error log but my thermostats do not go unavailable in HA and I do not have to reload the integration.
I just had another instance of my thermostats going off line. Error log shows:
2023-04-17 08:36:11.409 ERROR (MainThread) [somecomfort] API returned 200 from /portal/Device/CheckDataSession/2577885 request
2023-04-17 08:36:11.460 ERROR (MainThread) [somecomfort] API returned 200 from /portal/Device/CheckDataSession/1088545 request
2023-04-17 08:36:11.814 ERROR (MainThread) [somecomfort] API returned 200 from /portal/Device/CheckDataSession/1946190 request
2023-04-17 09:02:12.521 ERROR (MainThread) [somecomfort] API returned 200 from /portal/Device/CheckDataSession/1946190 request
2023-04-17 09:02:12.655 ERROR (MainThread) [somecomfort] API returned 200 from /portal/Device/CheckDataSession/2577885 request
2023-04-17 09:02:13.048 ERROR (MainThread) [somecomfort] Login as [email protected] failed
Edit: It looks like the fix did not make it into 2023.4.4 but has been addressed and will hopefully make it into the next release.:
Reload integration fixes the problem here. Is there a way to reload an integration from an automation?
Service homeassistant.reload_config_entry
The entry_id can be found: Home Assistant UI > Settings > Devices & Services > honeywell > click on devices
The URL of your browser should be something like
http://192.168.10.5:8123/config/devices/dashboard?historyBack=1&config_entry=1c693dfaeeb8c757439047d348f272bf
the 1c693dfaeeb8c757439047d348f272bf would be the entry_id
And then?? I would like to have an automation to reload the integration daily.
Since it is a service, you would create an automation that triggers on the device being unavailable then call this service.
Call what service?
There is no service in developer tools, services that reloads the climate integration.
Try
HOMEASSISTANT.RELOAD_CONFIG_ENTRY
Should help you out
The service I provided above in my post - click on the link homeassistant.reload_config_entry for details. It’s the same link @checking12 provided.
Of course, the problem hasn’t gone away.
Is there any way to trigger an automation on this?
The integration is still working, the thermostats can be controlled from Home Assistant, but I keep getting this annoying error- and reconfiguration is simply entering the password again.
I’m still getting the error where the thermostats go “unavailable” occasionally. I’m running HA 2023.4.5.
I’ve learned that the fix is not to “reconfigure” from the error dialog above, which only prompts for the password, but to scroll down the list of integrations to the original Honeywell entry.
From there it’s possible to hit the three dots menu and select “reload.” That brings all my thermostats back in HA immediately.
Unfortunately that error dialog remains. I’m just ignoring it for now, hoping for a fix in future versions.
Is anyone still seeing this issue? It seems to be happening more and more lately. Up to twice a day.
I’m still at 2023.4.5. I don’t see anything about this being fixed in 2023.5.x. If the fix is still pending I’ll wait for it. Has anyone had any luck updating?
I did see that this issue is marked as fixed by this pull request, and it shows it’s been merged to dev 2 weeks ago.
But I’m not sure this is the same issue. That one talks about requiring re-authentication every two weeks. As I said, mine is doing it daily, sometimes twice a day.
The workaround for me has been to reload the integration, as I mentioned in my earlier post. If this is going to go on much longer, I’m thinking of creating an automation to detect the unavailable status and issue the reload after a suitable delay.
I’m also seeing this multiple time per day.
Supposedly fixed in 2023.5.x but I have not upgraded to that version yet.
I’ve been running 2023.5.x a few days now and so far I have not had to reload the integration (whereas before I had to reload it about every day). I still get lots of log messages about the API returning 401, 403 and 500.
Upgraded to 2023.5.3 a few hours ago. I am also seeing the log messages but don’t have to reload the integration.
Thanks! I’ll try to work an update to 2023.5.x into my schedule sometime in the next few days.
I just wanted to circle back and report that my Honeywell integration has not gone “unavailable” since I installed 2023.6.1. That was 10 days ago. Before this, it had been happening almost daily, often several times a day.
Thank you!!
