core: Honeywell integration no longer reporting current thermostat status or setting temperatures

ly happening is that TCC is invalidating the session token for whatever reason (server rebooting or poor session handling on their end), so this integration’s code needs to be restructured so that if there’s an error accessing TCC, it automatically dumps the current session and tries to aquire a new one? …

You are exactly right. This is not a rate limiting issue any longer, the “somecomfort” library this integration is using throws the rate-limit error as a default. The real issue is “Remote end closed connection without response”. The really weird thing is that I haven’t really changed the logic for fetching data that much so it’s hard to know where this started. The old and current code has a retry system that should address connections being canned by TCC. Could be the sleep time is holding the connections open maybe? I will try poking around that device update loop and see if I can uncover anything.

I just got back from my camping trip so I will take some time too look into this again.

@rdfurman I believe I found the issue - the connection error is not being caught in the exception to trigger a retry. Adding the below line should resolve the issue. (I think!)

__init__.py

    async def async_update(self) -> None:
        """Update the state."""
        retries = 3
        while retries > 0:
            try:
                await self._refresh_devices()
                break                
            except (
                somecomfort.client.APIRateLimited,
                OSError,
                somecomfort.client.ConnectionTimeout,
                somecomfort.client.ConnectionError,  <--------- insert at line 125

Looks like we’re getting closer here, seems like folks are no longer seeing frequent API rate limiting which is awesome. Next up: I am able to reproduce this error now:

SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

Going to look into it today after I’m done work.

@schreyack Good find. I suspected something like this was the case as well. I’m currently using the custom integration (original), and every once in a while I still see connection issues. It looks like the original integration retries a few times and eventually gets rate limited. That makes sense. It goes like this:

1. ERROR: Update for climate [thermostat] fails (due to a read timeout)
2. WARNING: Update of [thermostat] is taking over 10 seconds.
3. ERROR: Failed to initialize honeywell client.
4. ERROR: Update for climate [thermostat] fails: You are being rate limited.
5. ERROR: SomeComfort update failed, Retrying - Error: You are being rate-limited. Try waiting a bit.

It looks like what’s happening is that the connection to TCC starts timing out, and the original integration is retrying in quick succession which eventually leads to getting rate limited. I think the fix to the new integration should include an exponential backoff for retries to avoid being rate limited.

@rdfurman - reading through the somecomfort client, i see that it is attempting to keep the connection to the TCC portal alive by sending periodic keep alives. could it be that since you migrated the initialization of the client in HA to the async method, that this is somehow messing with the keepalives? i’m not super familiar with how the async method in HA works, but just thought it might be an area to investigate.

Since it seems like rdfurman is busy with life (which I completely understand), I’ve made some modifications to increase the logging of the latest released integration so I can hopefully uncover what the issue is. Made the updates yesterday and am currently waiting for the failure to occur. No promises, but I will try to find a fix.

I wish I was able to help code and fix this. It seems quite odd that the integration was working for years prior to this “upgrade” and now seems that most / all users are having issue(s) with it. Is there not a chance just to revert to or at least leverage the old working code?

Certainly appreciate all the efforts going to maintain and work on this, would simply love it to work as it did a few months ago…

There’s another report of this over on the HA community forum: https://community.home-assistant.io/t/honeywell-total-connect-comfort-constantly-loses-contact/349773

I was hoping I’d be able to update to 10.x from 7.4 this week, but I have the WiFi thermostats. If this is still an issue I may have to hold off even longer. I hate to do that, there are already so many breaking changes I’ll have to deal with.

Would it make sense for me to update HA but back-level just the Honeywell integration? My version 7.4 has been working flawlessly.

I’ve just been running the old Honeywell integration as a custom component for the last couple of releases so I don’t get behind. I’ll switch over again to the new one when it is a bit more stable. I’d recommend that if you want to upgrade but not use the current honeywell integration.

Do you see an error about “Unique IDs” in the logs? If so, there is a separate issue for that: https://github.com/home-assistant/core/issues/57217

I updated again last night, but it looks like it stopped worked again before that update (will keep an eye on it going forward and update either way). Also, it became unavailable for like 30 seconds periodically (about every 12 hours).

Thank you! What version was not working correctly? I’m looking forward to hearing back after you’ve given it some time to soak. When you do, please let us know what version you’re on.

I have a ton of work to do when I update from 7.4 (the last time this integration worked) to 10.x. I’m going to have to block out some time to make the update, and I want to know what I’m getting into. Thank you again!!!

Oops, I forgot that bit, here you go. Seems to be going fine this morning so far.

Version | core-2021.10.3 Installation Type | Home Assistant Container Development | false Supervisor | false Docker | true User | root Virtual Environment | false Python Version | 3.9.7 Operating System Family | Linux Operating System Version | 5.14.9-2-ARCH CPU Architecture | aarch64

Thank you! I did a search in my browser but I guess I had to expand that section before it could be found. Now that I know what to look for I will be checking “All changes” with each update.

There have been a ton of changes since 7.4. I think I’ve got a LOT of work ahead of me, but at least I know I can get started now with some hope of success. The Honeywell integration was my first and is still one of my most important integrations. Thanks to all who contributed!

FYI, running 2021.10.0. The 'Connection aborted.', RemoteDisconnected error hit last night (around 3 times), and this morning I checked for thermostat updates and it is updating properly.

@rdfurman

i’ve been working to improve the error handling in the somecomfort client and along the way, i discovered that if the client returns any type of exception to the honeywell integration, the retry process is executed, including the async_reload; however, the data in HA will become stale/stuck from that point forward. in other words, the async_reload call has not resolved the issue of stale data once an exception is triggered. (i am testing with the most recent code that you submitted to HA.)

that said, the somecomfort client does have it’s own retry process that will solve most issues, other than rate limiting and to that end, i’m updating the client to never send an exception and instead just log errors. i’ve been running it this way for several days now and it seems to work well. assuming all continues well, i will release 0.7.0 for the client with these updates.

also - if you’re willing, do you mind sending me your email address? would be easier for us to communicate vs leaving messages here. 😃 mine is [my github username] @ yahoo.com

@rdfurman i bumped somecomfort libary to 0.6.0 last night if you want to change the integration to use it. just minor update to support Aux heat feature. but this also means we can now easily make updates to the client if we need.

So are we ever going to be able to get rid of the “taking longer than 10 seconds” messages? I appreciate all the work that’s gone into this.

Whenever I get around to implementing DataUpdateCoordinator I would think these messages will go away.

@rdfurman + all, I submitted a pull to somecomfort to patch an issue with “Aux Heat” control not functioning and the code owner @kk7ds indicated he no longer has the hardware to test. He is wondering if there is someone in our community that might want to take over the somecomfort repo? #kk7ds/somecomfort/pull/35. It would be great to have a community member owning this… I will offer to take over if no one else can, but I am only just starting to learn python.

@jad889nb I’m willing to take if you don’t feel up to it.

HA polls TCC every 5 minutes, so that makes sense… any change you make outside of HA can take up to 5 minutes to be reflected, depending on where you fall in the polling cycle.

Ah success 😃

2021-09-28 13:36:11 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

Then a few minutes later I did a UI reload (which hit my added log statement I mentioned above):

2021-09-28 13:45:40 WARNING (MainThread) [homeassistant.components.honeywell.const] Unloading entry. UnloadStatus: True

And was able to change my thermostat both from the UI and locally from the thermostat itself and I did get a status update. So looks like the UI reload works after a somecomfort error.

@bkr1969 when was the last time you restarted HA?

@rdfurman totally agree, it is odd. also odd is that i haven’t seen a remote connection error in days now… no idea why.

while you’re doing updates, what do you think about adding the following unload_entry code so then people can restart the integration from UI rather than needing to do a full HA restart when they have an issue? i’ve tested on mine and it seems to work.

__init__.py

async def async_unload_entry(hass, config) -> bool:
    """Unload a config entry."""
    unload_ok = await hass.config_entries.async_unload_platforms(config, PLATFORMS)
    hass_data: dict[str, Any] = hass.data[DOMAIN]
    if unload_ok:
        hass_data.clear()

    return unload_ok

I got a bit curious and started going through the code some. I may be off base as my Python proficiency could use some improvements, but I hope the following may be helpful or at least provide food for thought:

It looks like HA mainly is working on the climate/thermostat data which is represented by the HoneywellUSThermostat class. The class contains device data which will become important later on. When HA gets data for a thermostat, I believe it is getting the data for each instance of the HoneywellUSThermostat, which in turn gets it from its own device data instance.

The old yaml based code seems to pretty much operate on a per thermostat basis (HoneywellUSThermostat instance) , so each HoneywellUSThermostat instance would call somecomfort (which is making the API calls to the cloud) to get an update, and if somecomfort failed, HoneywellUSThermostat would create a new somecomfort client (each thermostat contains a client, which may be the same client as other thermostats), and retry somecomfort again. Upon success it would in turn create a new device instance. The HoneywellUSThermostat instance then simply updated itself for the new device instance.

The newer honeywell UI based code still uses the HoneywellUSThermostat class but it has added a HoneywellData class that contains the somecomfort client and all the thermostats and the thermostat’s data which are contained in devices which also contains device instances used by HoneywellUSThermostat. HA does call the HoneywellData class at poll time, which in turn will call somecomfort to get all the thermostats’ data (it appears that _refresh_devices() is actually calling somecomfort each time per thermostat), and once it gets the data, it in turn iterates through all the HoneywellUSThermostat instances updating their device instance data. However if a failure occurs with somecomfort, the HoneywellData creates a new client and a new devices list instance (which also contains new device instances) and sets itself to the new devices list instance. However it doesn’t appear to iterate through the HoneywellUSThermostat instances so that they can update themselves with the new device instance. So I think what is happening is that after a somecomfort connection failure, when HA queries the HoneywellUSThermostat instance, it returns stale data because the HoneywellUSThermostat device instance didn’t get updated.

@rdfurman I believe I now understand what the issue is, but I don’t know how to fix it.

I added logging within the async_update and _refresh_devices functions, and from that was able to confirm that the somecomfort client does get recreated as it should in _retry. (assuming the change I added above is implemented)

However, once this event is triggered (ie, there is some kind of failure from the somecomfort client) the HA side (I guess the state machine in HA?) never gets updated again. It seems like once we recreate the somecomfort client the link back to HA is broken or HA just stops updating. I don’t know enough about HA to know how to fix this… I believe we need to add some code in _retry after the new somecomfort client is created to force HA to sync again. Thoughts?

So my update still did not catch the error and trigger the retry. I still got this error last night:

  File "/config/custom_components/honeywell/climate.py", line 329, in set_hvac_mode
  File "/config/custom_components/honeywell/somecomfort.py", line 170, in system_mode
  File "/config/custom_components/honeywell/somecomfort.py", line 482, in _set_thermostat_settings
  File "/config/custom_components/honeywell/somecomfort.py", line 447, in _post_json
  File "/config/custom_components/honeywell/somecomfort.py", line 436, in _request_json
custom_components.honeywell.somecomfort.APIRateLimited: You are being rate-limited. Try waiting a bit.

I had added some logging in the exception clause which did not show up in the logs, so I’m sure that’s the issue, but I don’t quite understand why my update from yesterday didn’t work. To that end, I just modified the code to just catch everything and log what we find:

            except Exception as e:
                retries -= 1
                if retries == 0:
                    raise e

                result = await self._retry()
                _LOGGER.info("** Update Error")

                if not result:
                    raise e

                _LOGGER.info("SomeComfort update failed, Retrying - Error: %s", e)

Will let you know what I find.

Fired up a new branch for your idea: https://github.com/rdfurman/core/tree/fix_honeywell_connection_error

Awesome find you guys! I can try this out now, and think on how to add some kind of sleep/backoff algo to the retry system.

Welcome back @rdforman, and family and life absolutely take precedence! Is it possible the old integration was re-authenticating with every call to somecomfort, rather than holding on to a session between calls? I know even with the old integration, that I would sometimes get a random error and my thermostats wouldn’t push a thermostat change to TC, but usually trying again a minute or two later would work. My polling was set to 180 seconds. Another note, whenever I did have problems, I wouldn’t ever need to restart home assistant – it would just fix itself after a couple minutes, where now it looks like a restart is required to fix things, which really really sounds like a session/token is being held on to that’s gone “bad” where previously that wasn’t the case, it was either being replaced once bad, or it was just simply getting a whole new session every time.

Now I don’t know if it’s a session token from TCC, or some kind of local session/connection handling in somecomfort, or what. Hopefully the brainstorming from everyone here leads to some clues.

On Mon, Sep 20, 2021 at 1:57 PM CaptTom9 @.***> wrote:

Thank you @rdfurman https://github.com/rdfurman! We all understand life takes priority. Hope you had a good time.

Glad to see progress, and that it’s in capable hands. All the effort IS appreciated!

And thanks to @mcortez https://github.com/mcortez, @bkr1969 https://github.com/bkr1969, @schreyack https://github.com/schreyack for all the testing and input!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/56034#issuecomment-923298494, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA3HF2R2MZJNRCJMB4QWBDUC6N3FANCNFSM5DYOJWPA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thank you @rdfurman! We all understand life takes priority. Hope you had a good time.

Glad to see progress, and that it’s in capable hands. All the effort IS appreciated!

And thanks to @mcortez, @bkr1969, @schreyack for all the testing and input!

I haven’t dug into the code, but I’m wondering if the service signs into TCC and gets some kind of session token that is used for subsequent calls to the service? If it does, I believe TCC’s system is $@&# at maintaining sessions – even when I’m using the official App directly or Google Home’s integration with TCC, it seems to regularly loose its session and forces me to login again. So perhaps the whole “rate limit” errors were a red herring, and what is really happening is that TCC is invalidating the session token for whatever reason (server rebooting or poor session handling on their end), so this integration’s code needs to be restructured so that if there’s an error accessing TCC, it automatically dumps the current session and tries to aquire a new one?

I like how you’re thinking, but why would that have just become an issue with TCC since there were no issues earlier?

I haven’t dug into the code, but I’m wondering if the service signs into TCC and gets some kind of session token that is used for subsequent calls to the service? If it does, I believe TCC’s system is $@&# at maintaining sessions – even when I’m using the official App directly or Google Home’s integration with TCC, it seems to regularly loose its session and forces me to login again. So perhaps the whole “rate limit” errors were a red herring, and what is really happening is that TCC is invalidating the session token for whatever reason (server rebooting or poor session handling on their end), so this integration’s code needs to be restructured so that if there’s an error accessing TCC, it automatically dumps the current session and tries to aquire a new one?

On Mon, Sep 20, 2021, 11:35 AM schreyack @.***> wrote:

Since it seems like rdfurman is busy with life (which I completely understand), I’ve made some modifications to increase the logging of the latest released integration so I can hopefully uncover what the issue is. Made the updates yesterday and am currently waiting for the failure to occur. No promises, but I will try to find a fix.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/56034#issuecomment-923178702, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA3HF4BR2KMRVDAYMYTSMTUC55HZANCNFSM5DYOJWPA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I rebooted 2021.9.x and the status began updating again, but it only lasted less than a day before it went stale. I’m now also finding that I am unable to set the temperature. I increment the temperature in the UI by 1 degree, the UI changes the value one degree (and the value turns red), but after a couple of seconds, the value in the UI goes back to what it was prior. It clearly is failing to set the temperature, but there are no logs whatsoever showing up.

I wish I was able to help code and fix this. It seems quite odd that the integration was working for years prior to this “upgrade” and now seems that most / all users are having issue(s) with it. Is there not a chance just to revert to or at least leverage the old working code?

Good point. I like the idea of reverting back to the working version until the bugs can be worked out, if that’s possible.

I also agree with @markus99 that all the efforts toward a fix are appreciated. It’s just that maybe we should consider a different approach after three major, unanticipated bugs in the two months since the upgrade.

I updated to 2021.9.7 and let it run for a few hours while I slept. Same result, after a little over an hour of uptime(1 hour and 18 minutes to be exact) the honeywell integration stopped updating the sensors (After the SomeComfort Update Failed). Easiest to see in the humidity sensors.

HA came up at 9:53 PM for reference.

Upstairs and Kira Office about 10 feet from each other and have an open door between them.

Downstairs and Living Room are about 12 feet from each other and an open floor plan

Logs showing honeywell errors since updating. 2021-09-18 22:02:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 22:07:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 22:12:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 22:17:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 22:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 22:27:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 22:32:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 22:37:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 22:42:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 22:47:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 22:52:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 22:57:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:02:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:07:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:11:52 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: (‘Connection aborted.’, RemoteDisconnected(‘Remote end closed connection without response’)) 2021-09-18 23:12:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:17:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:27:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:32:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:37:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:42:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:47:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:52:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-18 23:57:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:02:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:07:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:12:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:17:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:21:52 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: (‘Connection aborted.’, RemoteDisconnected(‘Remote end closed connection without response’)) 2021-09-19 00:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:27:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:32:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:37:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:42:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:47:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:52:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 00:57:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:02:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:07:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:12:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:17:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:27:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:32:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:37:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:42:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:47:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:52:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 01:57:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:02:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:07:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:12:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:17:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:27:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:32:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:37:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:42:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:47:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:52:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 02:57:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:02:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:07:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:12:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:17:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:27:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:32:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:37:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:42:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:47:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:52:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 03:57:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:02:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:07:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:12:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:17:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:27:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:32:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:37:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:42:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:47:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:52:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 04:57:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 05:02:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 05:04:06 WARNING (SyncWorker_6) [urllib3.connectionpool] Retrying (Retry(total=5, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘ReadTimeoutError(“HTTPConnectionPool(host=‘192.168.0.61’, port=49153): Read timed out.”)’: /setup.xml 2021-09-19 05:07:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 05:12:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 05:17:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 05:21:52 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: (‘Connection aborted.’, RemoteDisconnected(‘Remote end closed connection without response’)) 2021-09-19 05:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 05:27:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 05:32:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 05:37:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 05:41:52 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: (‘Connection aborted.’, RemoteDisconnected(‘Remote end closed connection without response’)) 2021-09-19 05:47:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 05:51:52 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: (‘Connection aborted.’, RemoteDisconnected(‘Remote end closed connection without response’)) 2021-09-19 05:52:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 05:57:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 06:02:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 06:07:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 06:12:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 06:17:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 06:22:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 06:27:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 06:32:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds 2021-09-19 06:37:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.downstairs is taking over 10 seconds

EDIT: @rdfurman thanks so much for your work on this integration. I really appreciate it!

@rdfurman just wondering if you’ve had any success troubleshooting this? also wanted to say thank you for all the effort you’ve put into this integration!