Randomly Responding and/or Updating.

[wesmannmsu]

System Health details

With the new thermostat installed, it appears to work just fine. Until it just sort of stops.

Checklist

• I have enabled debug logging for my installation.
• I have filled out the issue template to the best of my ability.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of currently previous issues..

Describe the issue

When changing the Upper and Lower limits on the control, it either:

• Ignore it (goes back to what it was before)
• Changes it (but take a while)

When selecting a Preset from the control.

• It just pops back to what it was before.

However, changing it on the Thermastat, changes it (eventually) on the HA control

I created a Automation to Test with, and in the Trace, it seems to take 10 minutes to complete. but, still did not update the control or the thermstat

Included the dianostics, and can create a video of what is happening if you like

config_entry-ha_carrier-01JNFJJ1DJPNN1RCA5QWNPHCKM.json

Reproduction steps

config_entry-ha_carrier-01JNFJJ1DJPNN1RCA5QWNPHCKM.json

home-assistant_ha_carrier_2025-03-05T17-33-41.144Z.log
config_entry-ha_carrier-01JNFJJ1DJPNN1RCA5QWNPHCKM.json

...

Debug logs

See attached logs and diagnostics.

Diagnostics dump

No response

[dahlb]

have you checked you are using the newest firmware on your new thermostats?

[dahlb]

I can see in your diagnostic dump that you are on the latest firmware, please see if you can reproduce using the latest release of this integration (v2.6.0)

[wesmannmsu]

I did update the thermostat to the latest firmware when I installed it.

I was at the older release of this integration you wanted me to try for the "A" version of the thermostat. but updated to 2.5.X (the latest at the time) once the "B" was installed.

Just updated to 2.6, and yeah, it's smooth and responsive now.

[wesmannmsu]

I do not know what you did, but now it's super responsive!

…

On Thu, Mar 6, 2025 at 6:18 AM Bren Dahl ***@***.***> wrote: I can see in your diagnostic dump that you are on the latest firmware, please see if you can reproduce using the latest release of this integration (v2.6.0) — Reply to this email directly, view it on GitHub <#210 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANFT64TIMNKDINJVFSCDYJD2TA4H3AVCNFSM6AAAAABYMVONVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBTGY4DMOJVGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: dahlb]*dahlb* left a comment (dahlb/ha_carrier#210) <#210 (comment)> I can see in your diagnostic dump that you are on the latest firmware, please see if you can reproduce using the latest release of this integration (v2.6.0) — Reply to this email directly, view it on GitHub <#210 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANFT64TIMNKDINJVFSCDYJD2TA4H3AVCNFSM6AAAAABYMVONVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBTGY4DMOJVGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dahlb]

The websocket provides near real-time updates, it still has a few edge cases I'm working on handling more gracefully, if you need more stability in the mean time use v2.3.0.

Subscribe to #212 to track this remaining issue