I’m on HA 0.98.5 and have OZW (generic linux install), I presume with the OZW command class updates mentioned further up in the thread.
I just went through the same process as @bachya did a few posts above, but Heat and Auto modes just aren’t working. It doesn’t accept the heating setpoint from HA, and HA doesn’t reflect the heating setpoint when the mode is changed on the unit itself. In your first picture above you actually see this same behavior, where you say you set the mode to Auto and the setpoint to 72F, but the temperature
field in the state still reads 75. Later in the “Unit Testing” section, you set it to Auto on the unit itself and a setpoint of 65, but the temperature
state still says 79.
I’m not convinced these things work entirely out-of-the-box without their ADC service. There’s something missing still where the heat mode isn’t working; I can hear the relay click when I switch it to Heat or Auto, through HA or from the unit, but the setpoint reported in HA (and send from HA to the unit) is always the cool
setpoint and never the heat
one. Heat is also never applied based on the setpoint even if it’s well into the region where you’d expect heating to happen.
I tailed OZW_Log.txt
for a bit and saw that even if I changed the mode to Heat through HA (HA state and unit agree on the mode), setpoint changes still go out to the cooling setpoint only:
2019-09-19 04:45:26.111 Info, Node003, Received thermostat mode: Off
2019-09-19 04:45:26.111 Detail, Node003, Expected reply and command class was received
2019-09-19 04:45:26.111 Detail, Node003, Message transaction complete
2019-09-19 04:45:26.111 Detail,
2019-09-19 04:45:26.111 Detail, Node003, Removing current message
2019-09-19 04:45:26.112 Detail, Node003, Notification: ValueChanged
2019-09-19 04:45:29.449 Info, Node003, Value::Set - COMMAND_CLASS_THERMOSTAT_MODE - Mode - 0 - 1 - Heat
2019-09-19 04:45:29.449 Detail, Node003, Queuing (Send) ThermostatModeCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x40, 0x01, 0x01, 0x25, 0x47, 0xc4
2019-09-19 04:45:29.449 Detail, Node003, Queuing (Send) ThermostatModeCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x40, 0x02, 0x25, 0x48, 0xcb 2019-09-19 04:45:29.449 Detail,
2019-09-19 04:45:29.449 Info, Node003, Sending (Send) message (Callback ID=0x47, Expected Reply=0x13) - ThermostatModeCmd_Set (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x40, 0x01, 0x01, 0x25, 0x47, 0xc4
2019-09-19 04:45:29.463 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-09-19 04:45:29.463 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2019-09-19 04:45:29.477 Detail, Node003, Received: 0x01, 0x05, 0x00, 0x13, 0x47, 0x00, 0xae
2019-09-19 04:45:29.478 Detail, Node003, ZW_SEND_DATA Request with callback ID 0x47 received (expected 0x47)
2019-09-19 04:45:29.478 Info, Node003, Request RTT 28 Average Request RTT 44
2019-09-19 04:45:29.478 Detail, Expected callbackId was received
2019-09-19 04:45:29.478 Detail, Expected reply was received
2019-09-19 04:45:29.478 Detail, Message transaction complete
2019-09-19 04:45:29.478 Detail,
2019-09-19 04:45:29.478 Detail, Node003, Removing current message
2019-09-19 04:45:29.478 Detail,
2019-09-19 04:45:29.478 Info, Node003, Sending (Send) message (Callback ID=0x48, Expected Reply=0x04) - ThermostatModeCmd_Get (Node=3): 0x01, 0x09, 0x00, 0x13, 0x03, 0x02, 0x40, 0x02, 0x25, 0x48, 0xcb
2019-09-19 04:45:29.542 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-09-19 04:45:29.542 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2019-09-19 04:45:29.557 Detail, Node003, Received: 0x01, 0x05, 0x00, 0x13, 0x48, 0x00, 0xa1
2019-09-19 04:45:29.557 Detail, Node003, ZW_SEND_DATA Request with callback ID 0x48 received (expected 0x48)
2019-09-19 04:45:29.557 Info, Node003, Request RTT 78 Average Request RTT 61
2019-09-19 04:45:29.557 Detail, Expected callbackId was received
2019-09-19 04:45:29.767 Detail, Node003, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x03, 0x03, 0x40, 0x03, 0x01, 0xb0
2019-09-19 04:45:29.767 Detail,
2019-09-19 04:45:29.767 Info, Node003, Response RTT 288 Average Response RTT 265
2019-09-19 04:45:29.767 Detail, Node003, Refreshed Value: old value=0, new value=1, type=list
2019-09-19 04:45:29.767 Detail, Node003, Changes to this value are not verified
2019-09-19 04:45:29.767 Info, Node003, Received thermostat mode: Heat
2019-09-19 04:45:29.767 Detail, Node003, Expected reply and command class was received
2019-09-19 04:45:29.767 Detail, Node003, Message transaction complete
2019-09-19 04:45:29.767 Detail,
2019-09-19 04:45:29.767 Detail, Node003, Removing current message
2019-09-19 04:45:29.767 Detail, Node003, Notification: ValueChanged
2019-09-19 04:45:35.136 Info, Node003, Value::Set - COMMAND_CLASS_THERMOSTAT_SETPOINT - Cooling 1 - 2 - 1 - 76
2019-09-19 04:45:35.136 Detail, Node003, Queuing (Send) ThermostatSetpointCmd_Set (Node=3): 0x01, 0x0c, 0x00, 0x13, 0x03, 0x05, 0x43, 0x01, 0x02, 0x09, 0x4c, 0x25, 0x49, 0x8f
2019-09-19 04:45:35.137 Detail, Node003, Queuing (Send) ThermostatSetpointCmd_Get (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x43, 0x02, 0x02, 0x25, 0x4a, 0xca
2019-09-19 04:45:35.137 Detail,
2019-09-19 04:45:35.137 Info, Node003, Sending (Send) message (Callback ID=0x49, Expected Reply=0x13) - ThermostatSetpointCmd_Set (Node=3): 0x01, 0x0c, 0x00, 0x13, 0x03, 0x05, 0x43, 0x01, 0x02, 0x09, 0x4c, 0x25, 0x49, 0x8f
2019-09-19 04:45:35.151 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-09-19 04:45:35.151 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2019-09-19 04:45:35.165 Detail, Node003, Received: 0x01, 0x05, 0x00, 0x13, 0x49, 0x00, 0xa0
2019-09-19 04:45:35.166 Detail, Node003, ZW_SEND_DATA Request with callback ID 0x49 received (expected 0x49)
2019-09-19 04:45:35.166 Info, Node003, Request RTT 28 Average Request RTT 44
2019-09-19 04:45:35.166 Detail, Expected callbackId was received
2019-09-19 04:45:35.166 Detail, Expected reply was received
2019-09-19 04:45:35.166 Detail, Message transaction complete
2019-09-19 04:45:35.166 Detail,
2019-09-19 04:45:35.166 Detail, Node003, Removing current message
2019-09-19 04:45:35.166 Detail,
2019-09-19 04:45:35.166 Info, Node003, Sending (Send) message (Callback ID=0x4a, Expected Reply=0x04) - ThermostatSetpointCmd_Get (Node=3): 0x01, 0x0a, 0x00, 0x13, 0x03, 0x03, 0x43, 0x02, 0x02, 0x25, 0x4a, 0xca
2019-09-19 04:45:35.224 Detail, Node003, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-09-19 04:45:35.224 Detail, Node003, ZW_SEND_DATA delivered to Z-Wave stack
2019-09-19 04:45:35.238 Detail, Node003, Received: 0x01, 0x05, 0x00, 0x13, 0x4a, 0x00, 0xa3
2019-09-19 04:45:35.238 Detail, Node003, ZW_SEND_DATA Request with callback ID 0x4a received (expected 0x4a)
2019-09-19 04:45:35.238 Info, Node003, Request RTT 71 Average Request RTT 57
2019-09-19 04:45:35.238 Detail, Expected callbackId was received
2019-09-19 04:45:35.297 Detail, Node003, Received: 0x01, 0x0c, 0x00, 0x04, 0x00, 0x03, 0x06, 0x43, 0x03, 0x02, 0x2a, 0x02, 0xf8, 0x60
2019-09-19 04:45:35.297 Detail,
2019-09-19 04:45:35.297 Info, Node003, Response RTT 131 Average Response RTT 198
2019-09-19 04:45:35.297 Detail, Node003, Refreshed Value: old value=75.0, new value=76.0, type=decimal
2019-09-19 04:45:35.297 Detail, Node003, Changes to this value are not verified
2019-09-19 04:45:35.297 Info, Node003, Received thermostat setpoint report: Setpoint Cooling 1 = 76.0F
2019-09-19 04:45:35.297 Detail, Node003, Expected reply and command class was received
2019-09-19 04:45:35.297 Detail, Node003, Message transaction complete
2019-09-19 04:45:35.298 Detail,
2019-09-19 04:45:35.298 Detail, Node003, Removing current message
2019-09-19 04:45:35.298 Detail, Node003, Notification: ValueChanged
All of the mode changes and setpoint changes were done within HA. The unit reflects the mode changes and the relay makes an audible click when entering Heat mode, but the setpoint is only for cooling. It’s probably obvious given that the endpoint/node given to us by default is one that’s literally labeled “cooling” whereas the other is “unused.” I’m at a loss as to how to get the “heating” bits enabled or visible though. Their manual mentions extra modes and configurations being available via their application but they offer no further detail.