I’ve just starting to use the Total Connect Comfort integration, and having a strange issue with the “hold” modes. My theromostat is a Honeywell RTH9580WF1005, and works fine using the TCC app.
This termostat has three modes: normal (follow schedule), temporary hold (until next scheduled change), and permanent hold. HA shows I have three preset_modes: “none”, “away”, and “hold”.
Setting “none” causes the thermostat to follow the schedule, as I anticipated.
Setting “away” and “hold” are both behaving unexpectedly. If I move from “none” to “away”, every other time it sets the thermostat to “temporary” or “permanent” hold. For example:
- “none” → “away” yields temporary hold
- “away” → “none” yields following schedule
- “none” → “away” yields permanent mode
- “away” → “none” yields following schedule
- “none” → “away” yields temporary hold
- …
The same thing happens with “hold” as “away”. I had expected one of these two modes to be the temporary hold and the other the permanent hold. The documentation says “away” is the permanent hold, and doesn’t mention the “hold” mode.
I’ve printed the HA device state, and the “permanent hold” attribute is reflecting the same as what I’m seeing. ie: half the time set to true and the other half false.
It takes a while for the settings to take effect, so I’m waiting for both the thermostat and my HA dashboard to show each new state before trying the next step. ie: Assuming looking at the thermostat control and the HA console is a good representation of steady state, I’m not causing a race condition.
For completeness, here is my code snippet (device_id truncated):
sequence:
- device_id: f4...
domain: climate
entity_id: climate.house
type: set_preset_mode
preset_mode: away
- action: climate.set_temperature
metadata: {}
data:
target_temp_high: 84
target_temp_low: 55
target:
device_id: f4...
Am I doing something wrong? Are successfully setting each of the 3 modes?
1 post - 1 participant
