Honeywell integration no longer reporting current thermostat status or setting temperatures #56034

mat1583 · 2021-09-10T03:19:58Z

The problem

The integration is no longer reporting current temperature, humidity, or operation status. Both thermostats are behind a RedLink gateway.

Edit: After further testing, it's no longer setting the temperatures of the thermostats, either. It's dead in the water. All I see are the warnings posted from the logs.

What is version of Home Assistant Core has the issue?

2021.9.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Supervised

Integration causing the issue

Honeywell

Link to integration documentation on our website

https://www.home-assistant.io/integrations/honeywell/

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.helpers.entity
Source: helpers/entity.py:644
First occurred: 1:10:27 PM (108 occurrences)
Last logged: 10:06:28 PM

Update of climate.downstairs is taking over 10 seconds
Update of climate.upper_level is taking over 10 seconds

Additional information

probot-home-assistant · 2021-09-10T03:20:04Z

honeywell documentation
honeywell source
_{^{(message by IssueLinks)}}

probot-home-assistant · 2021-09-10T03:20:07Z

Hey there @rdfurman, mind taking a look at this issue as it has been labeled with an integration (honeywell) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

meyerrj · 2021-09-10T03:57:28Z

Check to see if you ended up with another thermostat entity,

I had something happen with mine with one of the recent upgrades where it created a new entity as climate.thermostat_2

mat1583 · 2021-09-10T10:38:02Z

Check to see if you ended up with another thermostat entity,

I had something happen with mine with one of the recent upgrades where it created a new entity as climate.thermostat_2

I completely deleted the integration, restarted, then reinstalled to start fresh.

frederuco · 2021-09-10T12:55:57Z

I had this issue too with 2021.9.5.

This is the past 48 hours of my downstairs. There is about 23 hours that I was using the 2021.9.5 code, about 12 hours ago I rolled to the 2021.6.0 code using the yaml login.

Note - the living room temp is an ESP8266 with temp/humidity and is about 15 feet from the thermostat and my house has a very open floor plan. It runs a few degrees higher due to the sun shining in my living room. But, the fact that my thermostat goes to 73 in the morning, and the temp in there was 73 but this kept reporting 70. And my humidity did not change for 23 hours when the other one did? I checked, no duplicate entities for these with a _2 on them.

I did not remember to grab logs prior to swapping over. I was more thinking of just getting it back working properly with code that I know works fine.

dnikles · 2021-09-10T13:22:56Z

I am having this issue and only have one thermostat (and one thermostat entity.)

greg520820 · 2021-09-10T15:52:35Z

Same issue since updating to 2021.9.5. Getting persistent update warnings, 13 in one hour. Two thermostats.

edit: Went back to 9.4 over 10 hours ago. Every thing is working on the honeywell integration with no update or api limit errors.

Logger: homeassistant.helpers.entity
Source: helpers/entity.py:644
First occurred: 10:38:28 AM (13 occurrences)
Last logged: 11:38:29 AM

Update of climate.back_bedroom is taking over 10 seconds

mat1583 · 2021-09-10T19:38:12Z

I restored to 2021.9.4 to get it working for the time being.

middleagedman · 2021-09-10T19:43:52Z

I'm on 2021.9.3 and I am seeing this as well

2021-09-10 02:01:27 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.1st_floor is taking over 10 seconds
urllib3.exceptions.ReadTimeoutError: HTTPSConnectionPool(host='www.mytotalconnectcomfort.com', port=443): Read timed out. (read timeout=30)

tommyjlong · 2021-09-10T22:47:54Z

2019.9.5 - When I tried this out yesterday, I could see the thermostat's indoor temperature status being updated on the 5 minute polling intervals. But today, it has not updated the indoor temperature status (nor indoor humidity).

mat1583 · 2021-09-12T01:18:06Z

Yeah, now seeing no updates again.

frederuco · 2021-09-12T03:20:46Z

After updating to 2021.9.6 today, it only took about an hour and my honeywell stopped updating.

Logger: homeassistant.components.honeywell.const
Source: components/honeywell/init.py:135
Integration: Honeywell Total Connect Comfort (US) (documentation, issues)
First occurred: 10:18:06 PM (1 occurrences)
Last logged: 10:18:06 PM

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

So, something isn't right.

Edit - changing temps in HA did not connect up again, sensors (humidity, current and target temps) not updating with real data.

stk21 · 2021-09-12T15:11:20Z

Running code version core-2021.9.5 and still receiving rate limiting. Also experiencing the no update for temp sensor back to HA.

File "/usr/local/lib/python3.9/site-packages/somecomfort/client.py", line 482, in _set_thermostat_settings
result = self._post_json(url, data=data)
File "/usr/local/lib/python3.9/site-packages/somecomfort/client.py", line 447, in _post_json
return self._request_json('post', *args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/somecomfort/client.py", line 436, in _request_json
raise APIRateLimited()
somecomfort.client.APIRateLimited: You are being rate-limited. Try waiting a bit.
2021-09-12 09:06:49 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139656766614784] You are being rate-limited. Try waiting a bit.
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 185, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1492, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1527, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 213, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 658, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 843, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 695, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/climate/init.py", line 470, in async_set_hvac_mode
await self.hass.async_add_executor_job(self.set_hvac_mode, hvac_mode)
File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 52, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/honeywell/climate.py", line 328, in set_hvac_mode
self._device.system_mode = self._hvac_mode_map[hvac_mode]
File "/usr/local/lib/python3.9/site-packages/somecomfort/client.py", line 170, in system_mode
self._client._set_thermostat_settings(
File "/usr/local/lib/python3.9/site-packages/somecomfort/client.py", line 482, in _set_thermostat_settings
result = self._post_json(url, data=data)
File "/usr/local/lib/python3.9/site-packages/somecomfort/client.py", line 447, in _post_json
return self._request_json('post', *args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/somecomfort/client.py", line 436, in _request_json
raise APIRateLimited()
somecomfort.client.APIRateLimited: You are being rate-limited. Try waiting a bit.
2021-09-12 09:06:53 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139656766614784] You are being rate-limited. Try waiting a bit.
Traceback (most recent call last):

stk21 · 2021-09-12T15:34:14Z

and, five minutes after upgrading to the .6 code, I get these messages

2021-09-12 09:20:15 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1_2 is taking over 10 seconds
2021-09-12 09:25:15 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1_2 is taking over 10 seconds
2021-09-12 09:30:15 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1_2 is taking over 10 seconds

stk21 · 2021-09-13T16:16:31Z

More logs and no updated from back into HA

2021-09-13 03:40:25 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1_2 is taking over 10 seconds
2021-09-13 03:45:16 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2021-09-13 03:45:25 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1_2 is taking over 10 seconds
2021-09-13 03:50:25 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1_2 is taking over 10 seconds
...
... (trimmed logs every 5 minutes)
...
2021-09-13 07:15:25 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1_2 is taking over 10 seconds
2021-09-13 07:19:00 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [139732137847584] Client unable to keep up with pending messages. Stayed over 512 for 5 seconds
2021-09-13 07:20:25 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1_2 is taking over 10 seconds
2021-09-13 07:25:25 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1_2 is taking over 10 seconds

mat1583 · 2021-09-13T18:03:19Z

@rdfurman have you been able to perform any troubleshooting for this issue? Please let me know if there's anyway I can help since I have two devices.

rdfurman · 2021-09-13T18:30:48Z

@rdfurman have you been able to perform any troubleshooting for this issue? Please let me know if there's anyway I can help since I have two devices.

Hard for me to troubleshoot when I'm not seeing this issue in my production setup. Is there anything that looks related in your logs aside from the "taking over 10 seconds" message?

Also my indoor thermostat doesn't show humidity. Which one do you have that does that?

schreyack · 2021-09-13T18:38:44Z

@rdfurman there are quite a few of us seeing this (just fyi). we never see status updates or temperature changes being reflected in HA. my setup does not include the redlink gateway. i ended up rolling back to 2021.7.4, but can roll forward again to assist in pulling log info for you.

frederuco · 2021-09-13T19:19:35Z

@rdfurman I already added the logs from my server after upgrading to 2021.9.6. The honeywell integration works for about 2 hours, then stops reporting updates and any changes made in HA will not be sent to TCC.
I am using 2021.6.0 honeywell version, but I can jump back to the 2021.9.6 version if you need more details/logs with the current one.

mat1583 · 2021-09-14T03:29:46Z

I'll try to get better logs tomorrow when I'm on my laptop, but here's a screenshot of the reported temperatures for one thermostat.

You can see that it shows 2 degree swings in a very short period when in fact the temperature was a steady 75 during that entire period. The set temperature reported was also similarly incorrect.

Tomorrow I'll try resetting my RedLink gateway and possibly resetting the thermostat and re-adding it to see if that fixes the inaccurate reported numbers.

schreyack · 2021-09-14T14:49:12Z

so this is interesting - after re-upgrading to 2021.9.6 the integration is working just fine now. the only difference i can think of is that i went from 2021.7.4 directly to 2021.9.6 instead of going through the step upgrades of 2021.9.4 and 2021.9.5 like i did the first time.

mat1583 · 2021-09-14T15:03:22Z

@rdfurman This morning I reset my redlink gateway and everything seems to be reporting correctly at the moment. If this continues to remain stable over the next 2-3 days, I'll leave it up to you whether you want to close it. Something funky was definitely going on with the temperature reporting as seen above and by other users, but it may not be a code issue. It could just be the thermostat, the reporting on honewell's side, etc.

As for humidity and such, those are attributes of my thermostat entity:

My downstairs thermostat is a Prestige IAQ, and the upstairs is a VisionPro8000

Valdorama · 2021-09-14T15:07:27Z

FYI I'm also seeing this behaviour. Running HA Container v2021.9.6, with two thermostats. Will work OK for a period after a restart but then eventually the logs will contain the message below, and after that it doesn't work:

Logger: homeassistant.helpers.entity
Source: helpers/entity.py:644
First occurred: September 13, 2021, 10:57:03 AM (278 occurrences)
Last logged: 10:04:09 AM

Update of climate.downstairs is taking over 10 seconds
Update of climate.upstairs is taking over 10 seconds

stk21 · 2021-09-14T15:11:57Z

I removed my integration yesterday, upgraded to the latest code, then re-added my integration. My three thermostats after 18 hours are no longer reporting current status/temp/settings, etc.

Lots really show nothing. Included logs specific to integration since reboot of host yesterday. Not sure specifically when the HA reporting stopped.

[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.

[ removed logs that are not specific to climate]

2021-09-13 13:25:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
2021-09-13 13:30:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
2021-09-13 13:35:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds

[the above logs show every 5 minutes]

2021-09-13 14:05:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
2021-09-13 14:10:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
...
2021-09-13 19:30:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
2021-09-13 19:35:11 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2021-09-13 19:35:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
...
2021-09-13 20:15:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
2021-09-13 20:20:11 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2021-09-13 20:20:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
...
2021-09-13 21:30:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
2021-09-13 21:33:25 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140197862538160] Client unable to keep up with pending messages. Stayed over 512 for 5 seconds
2021-09-13 21:35:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds

2021-09-13 23:40:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
2021-09-13 23:45:11 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2021-09-13 23:45:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds

2021-09-13 23:55:11 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2021-09-13 23:55:19 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
...
2021-09-14 07:40:51 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
2021-09-14 07:45:51 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds
2021-09-14 07:50:51 WARNING (MainThread) [homeassistant.helpers.entity] Update of climate.zone_1 is taking over 10 seconds

rdfurman · 2021-09-14T15:14:28Z

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.

tommyjlong · 2021-09-14T18:10:14Z

I'm not getting any log warnings or errors (other than "climate.blah taking over 10 seconds"), yet the indoor temperature and humidity have been flat-lined for several days now (last change was approximately 6 hours after last reboot) and the humidity showing on HA is not the same value showing on the thermostat itself.

CaptTom9 · 2021-10-04T15:35:56Z

Great news @schrekyack! I'm anxious to try out the updated version. Thanks to all for the great work!

Taking some of this off-line is a great idea, but don't forget to post updates here for us mere mortals who aren't involved in the coding. Thank you!

shmick · 2021-10-04T16:12:55Z

Seeing some new errors. Things were running fine for a few days.

To add some additional info, this thermostat is located at a seasonal trailer park that does experience brief internet outages, but all the other integrations keep working after things normalize.

2021-10-04 11:15:56 WARNING (MainThread) [homeassistant.config_entries] Config entry 'honeywell' for honeywell integration not ready yet: Failed to initialize the Honeywell client: Check your configuration (username, password), or maybe you have exceeded the API rate limit?; Retrying in background

2021-10-04 11:15:56 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

2021-10-04 11:16:07 ERROR (MainThread) [homeassistant.components.climate] Platform honeywell does not generate unique IDs. ID 6753017 already exists - ignoring climate.thermostat

rdfurman · 2021-10-05T00:03:52Z

@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

Huh that is super weird. I ran the new code with async_reload for nearly a week and it did trigger the reload a couple times. The history graph on my setup seems to indicate the data is being updated.

That being said, I am all for improving the somecomfort library (and integrating it into HA honeywell). I will fire off an email for us to discuss further. 👍

rdfurman · 2021-10-05T00:06:15Z

Seeing some new errors. Things were running fine for a few days.

To add some additional info, this thermostat is located at a seasonal trailer park that does experience brief internet outages, but all the other integrations keep working after things normalize.

2021-10-04 11:15:56 WARNING (MainThread) [homeassistant.config_entries] Config entry 'honeywell' for honeywell integration not ready yet: Failed to initialize the Honeywell client: Check your configuration (username, password), or maybe you have exceeded the API rate limit?; Retrying in background

2021-10-04 11:15:56 ERROR (MainThread) [homeassistant.components.honeywell.const] SomeComfort update failed, Retrying - Error: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

2021-10-04 11:16:07 ERROR (MainThread) [homeassistant.components.climate] Platform honeywell does not generate unique IDs. ID 6753017 already exists - ignoring climate.thermostat

Interesting, that last error about the unique_id is a little concerning. We had a bug about that a while back when I first introduced the config flow. Do you mind me asking how what version you're on now, and the version you came from?

Might be worth taking it out of this thread by creating a new bug for it.

shmick · 2021-10-05T00:12:51Z

Interesting, that last error about the unique_id is a little concerning. We had a bug about that a while back when I first introduced the config flow. Do you mind me asking how what version you're on now, and the version you came from?

Might be worth taking it out of this thread by creating a new bug for it.

Running HA 2021.9.7 via official docker image and manually over-wrote the Honeywell __init__.py from #56757

tommyjlong · 2021-10-08T15:08:06Z

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.

CaptTom9 · 2021-10-08T21:49:25Z

Wait, does this mean the Honeywell integration was updated in 10.0? I didn't see anything in the release notes.

tommyjlong · 2021-10-08T22:23:39Z

In the blog on release 2010.10, click on the "All changes" and you'll see a very loooooong list of all the merged commits. You'll see:

Fix honeywell connection error (rdfurman - #56757) (honeywell docs)

CaptTom9 · 2021-10-09T01:18:21Z

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!

markus99 · 2021-10-12T12:18:47Z

So just 2x confirming, the issue(s) w/ Honeywell / HA are now all fixed and upgrading to 10.x is working well? Thanks for ALL who contributed / worked thru the issue(s)!

JSkier21 · 2021-10-12T12:46:03Z

So just 2x confirming, the issue(s) w/ Honeywell / HA are now all fixed and upgrading to 10.x is working well? Thanks for ALL who contributed / worked thru the issue(s)!

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).

CaptTom9 · 2021-10-12T13:47:59Z

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!!!

JSkier21 · 2021-10-12T13:56:12Z

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.

JSkier21 · 2021-10-13T01:07:32Z

Okay, so looks like it went 8 hours without an update. Some errors about rate limiting. Going to remove, restart service, and add it again. Will check to see how it looks in the morning.

EDIT:
Seems to be okay after a few nights. Still has blips of becoming unavailable for 30 seconds every 10 - 12 hours so.

dnikles · 2021-10-21T11:27:06Z

Yesterday evening mine stopped updating after functioning for a week or so. I couldn't turn it on/off, set temp, etc. It worked through the honeywell app. Started working again after a restart of HA.

JSkier21 · 2021-10-22T13:53:20Z

Yeah, looks like it stops after a long period of time again, bummer. This should be re-opened.

Same here, web app / android app work fine, HA, integration pretty much dead.

rdfurman · 2021-10-22T13:55:27Z

Do you see an error about "Unique IDs" in the logs? If so, there is a separate issue for that: #57217

JSkier21 · 2021-10-22T14:00:32Z

Do you see an error about "Unique IDs" in the logs? If so, there is a separate issue for that: #57217

Yes, I'll head over to that one, thank you.

the-gray-ghost · 2021-10-25T15:57:40Z

I have had this issue persist since the 10.0 update. I am running 10.6. Just restarted my system yesterday and everything is still working, however, did have this show up in the log last night:

Logger: homeassistant.components.honeywell.const
Source: components/honeywell/init.py:153
Integration: Honeywell Total Connect Comfort (US) (documentation, issues)
First occurred: October 24, 2021, 7:12:13 PM (2 occurrences)
Last logged: October 24, 2021, 10:27:21 PM

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

When/If the thermostat fails, I will add the log for that.

On a side note, I see people here are able to get the humidity reporting from their thermostat in HA, I have not seen a way to do so, am I missing something? I'm running through RedLink.

rdfurman · 2021-10-25T16:13:34Z

I have had this issue persist since the 10.0 update. I am running 10.6. Just restarted my system yesterday and everything is still working, however, did have this show up in the log last night:

Logger: homeassistant.components.honeywell.const
Source: components/honeywell/init.py:153
Integration: Honeywell Total Connect Comfort (US) (documentation, issues)
First occurred: October 24, 2021, 7:12:13 PM (2 occurrences)
Last logged: October 24, 2021, 10:27:21 PM

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

When/If the thermostat fails, I will add the log for that.

On a side note, I see people here are able to get the humidity reporting from their thermostat in HA, I have not seen a way to do so, am I missing something? I'm running through RedLink.

Please note that error does not mean your Thermostat will stop working in HA. We've built it to retry when the Honeywell API throws this error. Please check your history graph to see if data has actually stopped updating. Usually folks see their data stop updating only after the unique IDs error. These seem to be happening mostly in the Honeywell wifi units. My RedLINK throws the connection error sometimes as well, but data still updates.

CaptTom9 · 2021-10-25T20:04:25Z

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.

newlinux · 2021-10-25T20:15:24Z

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.

bkr1969 · 2021-10-25T20:59:03Z

@rdfurman, if you'd like me to run anything for you, I am happy to do so. My 2 WIFI thermostats have not had any issues since this was originally closed.

Trebacz · 2021-10-26T01:02:28Z

I also have had no issues w/ my 2 wifi thermostats going offline....

…

On Mon, Oct 25, 2021, 1:59 PM Brian ***@***.***> wrote: @rdfurman <https://github.com/rdfurman>, if you'd like me to run anything for you, I am happy to do so. My 2 WIFI thermostats have not had any issues since this was originally closed. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#56034 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AETXMEYWZTFVK7CYKP2PVNLUIXAKHANCNFSM5DYOJWPA> . 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>.

the-gray-ghost · 2021-10-26T01:06:05Z

Please note that error does not mean your Thermostat will stop working in HA. We've built it to retry when the Honeywell API throws this error. Please check your history graph to see if data has actually stopped updating. Usually folks see their data stop updating only after the unique IDs error. These seem to be happening mostly in the Honeywell wifi units. My RedLINK throws the connection error sometimes as well, but data still updates.

Understood, the integration is still working, just posted log entry in case it was relevant. The integration has completely failed with every release this month, I keep updating in the hopes it will get fixed. Let me know what I can do to help.

CaptTom9 · 2021-10-26T11:58:54Z

The integration has completely failed with every release this month, I keep updating in the hopes it will get fixed. Let me know what I can do to help.

If anyone is interested, I created this Feature Request over on the Community forum:
https://community.home-assistant.io/t/feature-request-allow-update-and-back-level-integrations-individually/348905

Basically, if we could choose to update (or not) integrations individually from within the GUI, it would give more flexibility to developers and less pressure while working on bugs like these. I know it's possible to manually back-level just this integration, but it's something I've never done. I hope to set aside some time to do this but I know it's going to be a lot of trial and error, plus I've got a ton of breaking changes built up now that I'll have to address when I update HA.

I encourage up-votes if you agree. Thank you!

rdfurman · 2021-10-26T23:38:46Z

Since this is a closed issue, can we please continue discussion about the unique ID error over at #57217. Thanks.

probot-home-assistant bot added the integration: honeywell label Sep 10, 2021

mat1583 mentioned this issue Sep 10, 2021

Rate limiting in Honeywell TCC #55095

Closed

mat1583 changed the title ~~Honeywell integration no longer reporting current temp, humidity, or operation status~~ Honeywell integration no longer reporting current thermostat status or setting temperatures Sep 10, 2021

mat1583 mentioned this issue Sep 13, 2021

Honeywell TCC 2021.9.5 #56133

Closed

rdfurman mentioned this issue Oct 6, 2021

Update somecomfort library to 0.7.0 #57214

Merged

22 tasks

shmick mentioned this issue Oct 7, 2021

Platform honeywell does not generate unique IDs. ID 6753017 already exists - ignoring climate.thermostat #57217

Closed

github-actions bot locked and limited conversation to collaborators Nov 26, 2021

Honeywell integration no longer reporting current thermostat status or setting temperatures #56034

Honeywell integration no longer reporting current thermostat status or setting temperatures #56034

Comments

mat1583 commented Sep 10, 2021 • edited

The problem

What is version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Integration causing the issue

Link to integration documentation on our website

Example YAML snippet

Anything in the logs that might be useful for us?

Additional information

probot-home-assistant bot commented Sep 10, 2021

probot-home-assistant bot commented Sep 10, 2021

meyerrj commented Sep 10, 2021

mat1583 commented Sep 10, 2021

frederuco commented Sep 10, 2021

dnikles commented Sep 10, 2021

greg520820 commented Sep 10, 2021 • edited

mat1583 commented Sep 10, 2021

middleagedman commented Sep 10, 2021

tommyjlong commented Sep 10, 2021

mat1583 commented Sep 12, 2021

frederuco commented Sep 12, 2021 • edited

stk21 commented Sep 12, 2021

stk21 commented Sep 12, 2021

stk21 commented Sep 13, 2021

mat1583 commented Sep 13, 2021

rdfurman commented Sep 13, 2021

schreyack commented Sep 13, 2021

frederuco commented Sep 13, 2021

mat1583 commented Sep 14, 2021

schreyack commented Sep 14, 2021

mat1583 commented Sep 14, 2021

Valdorama commented Sep 14, 2021

stk21 commented Sep 14, 2021

rdfurman commented Sep 14, 2021

tommyjlong commented Sep 14, 2021

CaptTom9 commented Oct 4, 2021

shmick commented Oct 4, 2021

rdfurman commented Oct 5, 2021

rdfurman commented Oct 5, 2021

shmick commented Oct 5, 2021

tommyjlong commented Oct 8, 2021

CaptTom9 commented Oct 8, 2021

tommyjlong commented Oct 8, 2021

CaptTom9 commented Oct 9, 2021

markus99 commented Oct 12, 2021

JSkier21 commented Oct 12, 2021

CaptTom9 commented Oct 12, 2021

JSkier21 commented Oct 12, 2021

JSkier21 commented Oct 13, 2021 • edited

dnikles commented Oct 21, 2021

JSkier21 commented Oct 22, 2021 • edited

rdfurman commented Oct 22, 2021 • edited

JSkier21 commented Oct 22, 2021

the-gray-ghost commented Oct 25, 2021

rdfurman commented Oct 25, 2021

CaptTom9 commented Oct 25, 2021

newlinux commented Oct 25, 2021

bkr1969 commented Oct 25, 2021

Trebacz commented Oct 26, 2021 via email

the-gray-ghost commented Oct 26, 2021

CaptTom9 commented Oct 26, 2021

rdfurman commented Oct 26, 2021

mat1583 commented Sep 10, 2021 •

edited

greg520820 commented Sep 10, 2021 •

edited

frederuco commented Sep 12, 2021 •

edited

JSkier21 commented Oct 13, 2021 •

edited

JSkier21 commented Oct 22, 2021 •

edited

rdfurman commented Oct 22, 2021 •

edited