When the Lennox system uses schedules, a change to the setpoint causes a temporary hold until the hold is cleared or the next scheduled event occurs. I'd like an OH Channel for ZoneHoldExists and a mechanism to cancel the zone hold. This keeps things simple and allows the use of built-in Lennox features.
Another approach that makes this a bit more complicated is to stop using Lennox schedules. Use openhab rules and calendar to manage the schedule to change the OperationMode, SetPoint, and FanMode directly. When the schedules are not used, there is no hold placed on setpoint changes.
Future feature request ...
When the Lennox system uses schedules, a change to the setpoint causes a temporary hold until the hold is cleared or the next scheduled event occurs. I'd like an OH Channel for ZoneHoldExists and a mechanism to cancel the zone hold. This keeps things simple and allows the use of built-in Lennox features.
Another approach that makes this a bit more complicated is to stop using Lennox schedules. Use openhab rules and calendar to manage the schedule to change the OperationMode, SetPoint, and FanMode directly. When the schedules are not used, there is no hold placed on setpoint changes.