@chris The latest snapshot has the updates
I then tested by sending mode updates thru the Menu UI
I tested changing Thermostat mode by cycling through
- Auto to Heat
- Heat to Cool
- Cool to Auto
The Thermostat showed exactly what I expected with the setpoint and mode updating on the Thermostat display set point, mode, and “Auto Change On” for Auto mode
I then tried to set the Mode to Away
There was no change. Here is the debug log.
events.log (214.4 KB)
In the log I see this
2021-12-21 09:40:41.223 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Command received zwave:device:a9db510670:node9:thermostat_mode --> 13 [DecimalType]
2021-12-21 09:40:41.224 [DEBUG] [lass.ZWaveThermostatModeCommandClass] - NODE 9: setValueMessage 13, modeType empty false
2021-12-21 09:40:41.224 [ERROR] [lass.ZWaveThermostatModeCommandClass] - NODE 9: Unsupported mode type 13
2021-12-21 09:40:41.224 [WARN ] [nverter.ZWaveThermostatModeConverter] - NODE 9: Generating message failed for command class = COMMAND_CLASS_THERMOSTAT_MODE, endpoint = 0
2021-12-21 09:40:41.225 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: No messages returned from converter
The Honeywell install guide says that “Away mode” is triggered by the z-wave controller.
What are your thoughts?
Edit:
The Thing config
Schedule Type is “1” (Single schedule)
Auto Changeover is “1” (manual states this is On/Off. I presume “1” is On)