Stelpro stzw402+ setpoint issue
Posted: Wednesday 31 January 2018 2:39
Hello,
I believe I've run across an issue that has to do with behind the scenes temperature unit conversions. I have recently installed a Stelpro STZW402+ thermostat and included it in my network without issue. Unfortunately, I have been unable to set the setpoint on the device when it is set to F units. Setting both Domoticz and the thermostat to C enables me to set the setpoint without issue. Setting Domoticz to C and leaving the thermostat on F also works, but only for certain temps. Digging through the debug logs, this seems to be related to the length of the value being sent to the thermostat by Domoticz and, in turn, OZW.
An unsuccessful attempt (setting F value) looks like this in the logs (here I set 68 F in the UI)
A successful attempt (setting F value) looks like this (here I set 16.1 C in the UI)
A successful attempt (setting a C value) looks like this (here I set 18 C in the UI)
I have attempted to update the ozq config file for the device by adding
to the device xml (excluded the device, stopped Domoticz, altered XML, started Domoticz, included device) but this does not resolve the issue.
Is Domoticz doing some sort of conversion on the back end that causes 68 F in the UI to turn into 68.002884 by the time it gets to OZW?
I've posted this issue on the OZW group, but have not heard anything for a few days, so I'm hoping someone over here may have some insight.
I believe I've run across an issue that has to do with behind the scenes temperature unit conversions. I have recently installed a Stelpro STZW402+ thermostat and included it in my network without issue. Unfortunately, I have been unable to set the setpoint on the device when it is set to F units. Setting both Domoticz and the thermostat to C enables me to set the setpoint without issue. Setting Domoticz to C and leaving the thermostat on F also works, but only for certain temps. Digging through the debug logs, this seems to be related to the length of the value being sent to the thermostat by Domoticz and, in turn, OZW.
An unsuccessful attempt (setting F value) looks like this in the logs (here I set 68 F in the UI)
Code: Select all
2018-01-28 11:35:38.205 Info, Node044, Value::Set - COMMAND_CLASS_THERMOSTAT_SETPOINT - Heating 1 - 1 - 1 - 68.002884
2018-01-28 11:35:38.205 Detail, Node044, Queuing (Send) ThermostatSetpointCmd_Set (Node=44): 0x01, 0x0f, 0x00, 0x13, 0x2c, 0x08, 0x43, 0x01, 0x01, 0xcc, 0x04, 0x0d, 0xa4, 0x44, 0x25, 0x94, 0x10Code: Select all
2018-01-26 21:38:52.373 Info, Node042, Value::Set - COMMAND_CLASS_THERMOSTAT_SETPOINT - Heating 1 - 1 - 1 - 60.98
2018-01-26 21:38:52.374 Detail, Node042, Queuing (Send) ThermostatSetpointCmd_Set (Node=42): 0x01, 0x0d, 0x00, 0x13, 0x2a, 0x06, 0x43, 0x01, 0x01, 0x4a, 0x17, 0xd2, 0x25, 0x7c, 0x58Code: Select all
2018-01-26 21:40:40.366 Info, Node042, Value::Set - COMMAND_CLASS_THERMOSTAT_SETPOINT - Heating 1 - 1 - 1 - 18
2018-01-26 21:40:40.366 Detail, Node042, Queuing (Send) ThermostatSetpointCmd_Set (Node=42): 0x01, 0x0c, 0x00, 0x13, 0x2a, 0x05, 0x43, 0x01, 0x01, 0x01, 0x12, 0x25, 0xd3, 0x69I have attempted to update the ozq config file for the device by adding
Code: Select all
override_precision="2"Is Domoticz doing some sort of conversion on the back end that causes 68 F in the UI to turn into 68.002884 by the time it gets to OZW?
I've posted this issue on the OZW group, but have not heard anything for a few days, so I'm hoping someone over here may have some insight.