#Honeywell Timeouts

1 messages · Page 1 of 1 (latest)

misty cypress
#

I get a lot of these messages related to my Honeywell thermostats timing out or taking a long time to query. It has been happening for months. Over 1500 occurrences as of this morning.

Logger: homeassistant.helpers.entity
Source: helpers/entity.py:1284
First occurred: November 16, 2025 at 4:59:47 PM (1517 occurrences)
Last logged: 8:19:55 AM

Update of climate.upper_level_thermostat is taking over 10 seconds
Update of climate.lower_level is taking over 10 seconds

Anyone else get these? Any ideas for solving it? Any suggestions for non-cloud based (local control) thermostats to replace these? I would prefer Z-Wave devices.

tawny garden
#

Honeywell is tightly rate limited. The fact that you have 1500 in a morning tells me you should not talk to it so often
I doubt there are 1500 calls allowed in a week...

misty cypress
# tawny garden Honeywell is tightly rate limited. The fact that you have 1500 in a morning tell...

Thanks for the link. The Honeywell integration's IoT class is "Cloud Polling" which is the heart of the problem. I can't seem tȯ change the polling interval for the Honeywell integration. Perhaps, I'll try turning off polling and setting up an automation as the article suggests. BTW, I don't think it had been 1,500 calls that morning. I think it's cumulative since the last restart. It's up to almost 9,000 timed out API calls now. I'd really like to find new thermostats that are Local Push or Local Polling types. Z-Wave would be best for me. Any suggestions?