current Temp not adjusting

[wesmannmsu]

System Health details

For some reason (that I cant determine) the Main Zone's temp seem to be stuck at 69, but its not.

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

The Main Zone, temp remains mostly constant, and its not anywhere near what the wall mount says.

config_entry-ha_carrier-01JNFJJ1DJPNN1RCA5QWNPHCKM (2).json

Reproduction steps

1. I am not sure why.

...

Debug logs

attached

Diagnostics dump

No response

[LSR19]

I am having the same issue. Room temperature in my 3 zones remains constant irrespective of the actual room temperature seen by the wall controller and by the Carrier iPhone app.

[dahlb]

looks like the websocket updates send the current temperature over with the wrong zone id, my system only have zone 1 setup but I see this in my debug logs

2025-03-09 11:49:39.403 DEBUG (MainThread) [carrier_api.api_websocket_data_updater] InfinityStatus received: {"messageType":"InfinityStatus","deviceId":"serialxxx","zones":[{"id":2,"rt":78}],"timestamp":"2025-03-09T15:49:39.334Z"}

@wesmannmsu can you check for debug message like mine? I was able to confirm in your diagnostic log that your zone 1 has the heat and cool set points your thermostat, and your zone 2 has the current temperature that is within one degree of what is on your thermostat so I'm guess it was just a delay in data captures.

@LSR19 your multi zone setup I think could be really helpful in understanding how the websocket is mismatching the current temperature (rt).

1. Please can you attempt to enable debug logging
2. pick a zone to adjust the temperature enough to cause a current temperature change.
3. find a message in your debug logs like above note the zone id vs the zone id you expected
   I'm hoping if you can do that for each of your zones we will see the pattern of how they are mapped to the zones and can adjust to handle the api's inconsistency.

[dahlb]

fyi: looks like the same thing happens at https://my.carrier.com/home/, I saw the correct temperature in the mobile app but I'm guessing when you change apps back to the carrier app it reloads all the data from graphql so it masks the error in mobile

[dahlb]

v2.7.6 adjusts the zone id based on my debug logs and assumes the issue stems from a conflict between 0 index array and 1 index array for zone counts. a more complex fix might be needed once we see more data

[dahlb]

@wesmannmsu please write up a separate issue about your target temperatures shifting

[wesmannmsu]

One of the things I have noticed on my system is that the System has issues connecting to its Bryant. Has anyone else seen this?

I image this would affect Websocks and all kinds of stuff, especially if a time out is involved.

For me, this sort of comes and goes, does anyone else see this?

[wesmannmsu]

Something is clearly still wrong, caught all this in Debugging and Video.

https://youtu.be/DVJbxn0Ym90

config_entry-ha_carrier-01JNFJJ1DJPNN1RCA5QWNPHCKM.json
home-assistant_ha_carrier_2025-03-10T20-16-58.412Z.log

[dahlb]

@wesmannmsu please keep comments on this ticket related to this ticket which is focused on the zone current temperature being wrong. If you have a question like the two above you can open discussions to field feedback

[wesmannmsu]

Yep, Sorry, thought they might be related