Changing target Temp unexpectedly

[wesmannmsu]

System Health details

System Information

version	core-2025.3.1
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.13.2
os_name	Linux
os_version	6.6.73-haos
arch	x86_64
timezone	America/Chicago
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	4993
Installed Version	2.0.5
Stage	running
Available Repositories	1576
Downloaded Repositories	8

Home Assistant Cloud

logged_in	true
subscription_expiration	January 1, 2026 at 6:00 PM
relayer_connected	true
relayer_region	us-east-1
remote_enabled	true
remote_connected	true
alexa_enabled	false
google_enabled	false
cloud_ice_servers_enabled	true
remote_server	us-east-1-14.ui.nabu.casa
certificate_status	ready
instance_id	9d3afd8201b548c2bec40881c5cac1b1
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 14.2
update_channel	stable
supervisor_version	supervisor-2025.03.2
agent_version	1.6.0
docker_version	27.2.0
disk_total	457.7 GB
disk_used	19.1 GB
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	generic-x86-64
supervisor_api	ok
version_api	ok
installed_addons	Z-Wave JS UI (3.22.0), Z-Wave JS (0.10.0), Mosquitto broker (6.5.0), Advanced SSH & Web Terminal (20.0.2), Studio Code Server (5.18.3), Samba share (12.5.0), Music Assistant Server (2.4.4)

Dashboards

dashboards	4
resources	2
views	3
mode	storage

Network Configuration

adapters	lo (disabled), eno1 (enabled, default, auto), hassio (disabled), docker0 (disabled), vethc4a5abf (disabled), veth1d9b915 (disabled), veth2226d41 (disabled), vethb25a9c4 (disabled), vethb817459 (disabled), veth6361a76 (disabled), veth742fee9 (disabled), veth27a9357 (disabled), veth4ea4c81 (disabled)
ipv4_addresses	lo (127.0.0.1/8), eno1 (192.168.29.46/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), vethc4a5abf (), veth1d9b915 (), veth2226d41 (), vethb25a9c4 (), vethb817459 (), veth6361a76 (), veth742fee9 (), veth27a9357 (), veth4ea4c81 ()
ipv6_addresses	lo (::1/128), eno1 (fd4a:3f8e:85ca:f44a:f596:cf0d:284d:2a14/64, fe80::bcec:9488:2da1:4291/64), hassio (fe80::42:48ff:fe14:a2dd/64), docker0 (fe80::42:55ff:fe05:8aa7/64), vethc4a5abf (fe80::e472:eff:fe8d:d75c/64), veth1d9b915 (fe80::4c91:8ff:fe9d:421d/64), veth2226d41 (fe80::3862:60ff:feda:8880/64), vethb25a9c4 (fe80::9853:4cff:fe4b:3bc/64), vethb817459 (fe80::b0d8:3ff:fe29:d391/64), veth6361a76 (fe80::1818:96ff:febd:6c3f/64), veth742fee9 (fe80::2471:daff:feae:fd0/64), veth27a9357 (fe80::ecf0:d6ff:fef5:a8e6/64), veth4ea4c81 (fe80::583f:96ff:fe40:cd4f/64)
announce_addresses	192.168.29.46, fd4a:3f8e:85ca:f44a:f596:cf0d:284d:2a14, fe80::bcec:9488:2da1:4291

Recorder

oldest_recorder_run	February 27, 2025 at 6:09 PM
current_recorder_run	March 10, 2025 at 7:14 AM
estimated_db_size	891.34 MiB
database_engine	sqlite
database_version	3.48.0

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

For reasons I can identify it wants to change the temp to 60/80 Heating/Cooling.

I set it to a preset 70/75, but when I look back later, its at 60/80 again.

I know that I 'once' tested the system when websockets were having issues pre 2.4.3. just to see if it would update on the wall thermostat.

I turned logging on this morning, when it was at 60/80, set the termastat to "Preset Resume" and it adjusted, seemed to stay that way, but about an hour later, it was back to 60/80.

Stopped logging and got a fresh diagnostic.

Reproduction steps

1. Don't know

...

Debug logs

attached

Diagnostics dump

config_entry-ha_carrier-01JNFJJ1DJPNN1RCA5QWNPHCKM (1).json
home-assistant_ha_carrier_2025-03-10T12-10-07.559Z.log

[dahlb]

at 2025-03-10 06:16:14.853 from logs
zone 1 is configured to manual mode at 60/80
all zones are configured to away and vacation modes set to 60/80

zones

1. Main
2. Upstairs
3. Basement

looks like another websocket message with incorrectly assigned zone ids

2025-03-10 06:56:02.518 DEBUG (MainThread) [custom_components.ha_carrier] set_temperature; kwargs:{'temperature': 65.0, 'target_temp_high': 80.0, 'target_temp_low': 60.0, 'entity_id': ['climate.varela_hvac_main']}
2025-03-10 06:56:02.518 DEBUG (MainThread) [custom_components.ha_carrier] set_temperature; heat_set_point:60.0, cool_set_point:80.0, fan_mode:FanModes.OFF
2025-03-10 06:56:02.519 DEBUG (MainThread) [custom_components.ha_carrier] infinite_hold:True; holding until:'10:00'
2025-03-10 06:56:03.362 DEBUG (MainThread) [carrier_api.api_websocket] ws: reconciled
2025-03-10 06:56:03.961 DEBUG (MainThread) [carrier_api.api_websocket] ws: reconciled
2025-03-10 06:56:06.319 DEBUG (MainThread) [carrier_api.api_websocket_data_updater] InfinityStatus received: {"messageType":"InfinityStatus","deviceId":"4620W201259","zones":[{"id":2,"htsp":60,"clsp":80}],"timestamp":"2025-03-10T11:56:06.218Z"}
2025-03-10 06:56:06.320 DEBUG (MainThread) [carrier_api.api_websocket_data_updater] InfinityStatus received: {"messageType":"InfinityStatus","deviceId":"4620W201259","zones":[{"id":2,"htsp":60,"clsp":80}],"timestamp":"2025-03-10T11:56:06.218Z"}

from the logs it looks like you set the main climate through ha to a custom temperature of 60/80 but it updated the upstairs thermostat instead.

Did you trigger the set_temperature call through a home assistant service call? I've never seen the ha ui pass three temperature values at once like what I see in your calls.

[wesmannmsu]

True, but like I said, I adjusted it in HA to 60/80 about 10 days ago, manually, not through an automation or anything.

But it keeps shooting back to that value without me doing it. I set it to resume, and it pops back to 60/80 when next I look.

The debug log should show it going to 60/80 but I didnt set it.

[wesmannmsu]

Although, I updated this morning to you current version, and it hasn’t gone back to 60/80 since (but its just been a couple hours)

[dahlb]

Sorry to be clear what I see in your logs is at 2025-03-10 06:56:02.518 something in your home assistant server intentionally set the climate for zone 1 to 60/80. If you don't know what did it I would suggest looking through all your automations that interact with zone 1

[wesmannmsu]

OMG, you are so right! I have a stupid test automation. So sorry about that!!!

[wesmannmsu]

I'm so dumb! Sorry!