Websocket stability issues

[dahlb]

System Health details

Na

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

2.6.0 and later releases use websocket interface that leaves unavailable entities from some updates.

This ticket is to track when the websocket is more reliable, if you want reliable use v2.3.0 until this ticket is resolved.

Reproduction steps

...

Debug logs

Na

Diagnostics dump

No response

[wesmannmsu]

I updated to the latest 2.7 then 2.71 and it's back to not responding. Moved back to 2.6

Selecting Presets->Resume or Presets->Sleep (or anything) is ignored and return back to Present->Manual

home-assistant_ha_carrier_2025-03-07T03-40-33.171Z.log
config_entry-ha_carrier-01JNFJJ1DJPNN1RCA5QWNPHCKM (1).json

Presets.mp4

[dahlb]

the description suggests using 2.3.0, 2.6 is the websocket version that is known to currently have stability issues.

when you post your logs please enable debug logging or they likely are empty like the one you've posted.

[dfludwig]

Let me know if there is anything you'd like me to test, or data you'd like me to try to gather to help resolve this issue.

[dahlb]

v2.7.5 has been running for me for the past two days with no problems and handles all the updates I've tried.

The graphql servers return 500 at least once a day but the integration gracefully handles it now.

if you are still experiencing issues after updating to v2.7.5 please open a new ticket with a description, debug logs, and diagnostic file.

[jerryj001]

updated to v2.7.5 this morning temperature has not changed for the last 8 hours, Also I am using the latest Home assistant on docker. suspect the temperature problem persists.

[wesmannmsu]

One other thing I have noticed is that its (main zone) sometimes jump to 60/80 Heat/Cool without any clear reason. I have not be able to catch it doing it, otherwise I would have written a report

[dahlb]

@jerryj001 #214 is an open issue about current temperature not updating on v2.7.5

[dahlb]

@wesmannmsu be sure to turn on debug logging which will log all websocket messages, for the heat/cool changing the message would include something like

"htsp":56,"clsp":74

htsp is heating set point
if you find the set points changing incorrectly be sure to open a new ticket as this one is closed