The HA climate entity doesn’t seem to mesh well with Honeywell’s hold modes.
The entity supports a hold_mode, but it seems to be looking at something different. The only options there are “hold,” “swing,” and “away.” Here’s the documentation:
My Honeywell thermostat has “permanent hold” and “temporary hold” modes. Nothing which seems like it could map to “swing” or “away.”
When I change the set temperature from HA, if the thermostat was previously running the normal schedule, it changes to temporary hold. If it was already in a hold, it stays in that hold, and just changes the temperature setting for the duration of that hold.
I haven’t found a way to cancel the hold and return to running the schedule, nor does it show when a temporary hold will revert back (at the next scheduled change) the way the thermostat and the Honeywell app do. Those things don’t appear to be supported in HA.
Beyond this basic difference, I’m convinced there are other problems with the Honeywell integration. For example, one of my thermostats appears to correctly shade the area under the line in the history_graph when the heat is on, but two do not. The one that works has heating and cooling capability, the others have heating only. The only apparent difference is the working one has “fan_mode” and “fan_modes” attributes. Obviously the fan doesn’t reflect whether it’s heating or cooling. Again, this points to some sort of issue mapping the Honeywell’s capabilities to the climate entity.