This driver does not work with real thermostats.
It works with temperature sensors and creates a virtual Thermostat.
Stelpro KI Zigbee Thermostat using Zigbee Thermostat Edge Driver can’t set temperature to 65F or 67F
@Mariano_Colmenarejo Can the Edge Driver Zigbee TempSensor and Thermostat Mc be used for a standalone thermostat or do you need a Temp sensor? If it can can you add the fingerprints of the device below. The problem with the stock driver is that you cant set the temperature to 65 or 67 F. I think because the driver tries to use a decimal point like 65.2 and the thermostat uses whole numbers. I also posted the logs that Smartthings had me send them that shows the issue.
2023-01-03T13:09:37.847150867+00:00 TRACE Zigbee Thermostat Received event with handler zigbee
2023-01-03T13:09:37.856050534+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x94B8, src_endpoint: 0x19, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCC, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x04, ZCLCommandId: 0x0A >, < ReportAttribute || < AttributeRecord || AttributeId: 0x0000, DataType: Int16, LocalTemperature: 1800 > > > >
2023-01-03T13:09:37.875961867+00:00 TRACE Zigbee Thermostat Found ZigbeeMessageDispatcher handler in zigbee-thermostat → stelpro ki zigbee thermostat
2023-01-03T13:09:37.881298867+00:00 INFO Zigbee Thermostat Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: LocalTemperature
2023-01-03T13:09:37.888074867+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> emitting event: {“attribute_id”:“temperature”,“capability_id”:“temperatureMeasurement”,“component_id”:“main”,“state”:{“unit”:“C”,“value”:18.0}}
2023-01-03T13:09:37.907295201+00:00 DEBUG Zigbee Thermostat Master Bath Thermostat device thread event handled
2023-01-03T13:09:38.733711201+00:00 DEBUG Zigbee Thermostat driver device thread event handled
2023-01-03T13:09:54.790762869+00:00 TRACE Zigbee Thermostat Received event with handler capability
2023-01-03T13:09:54.801658536+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> received command: {“args”:{“setpoint”:65},“capability”:“thermostatHeatingSetpoint”,“command”:“setHeatingSetpoint”,“component”:“main”,“positional_args”:[65]}
2023-01-03T13:09:54.810152536+00:00 TRACE Zigbee Thermostat Found CapabilityCommandDispatcher handler in zigbee-thermostat → stelpro ki zigbee thermostat
2023-01-03T13:09:54.865669536+00:00 ERROR Zigbee Thermostat Master Bath Thermostat thread encountered error: [string “st/dispatcher.lua”]:233: Error encountered while processing event for <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)>:
arg1: table: 0xc17030
[string “st/dispatcher.lua”]:233: Error encountered while processing event for <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)>:
arg1: table: 0xc17030
[string “st/zigbee/generated/zcl_clusters/Thermostat/s…”]:101: Error creating Int16: Int16 value must be an integer
2023-01-03T13:10:07.116202204+00:00 TRACE Zigbee Thermostat Received event with handler capability
2023-01-03T13:10:07.125311537+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> received command: {“args”:{“setpoint”:64.2},“capability”:“thermostatHeatingSetpoint”,“command”:“setHeatingSetpoint”,“component”:“main”,“positional_args”:[64.2]}
2023-01-03T13:10:07.137787204+00:00 TRACE Zigbee Thermostat Found CapabilityCommandDispatcher handler in zigbee-thermostat → stelpro ki zigbee thermostat
2023-01-03T13:10:07.147800871+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x94B8, dest_endpoint: 0x19, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x02 >, < WriteAttribute || < AttributeRecord || attr_id: 0x0012, DataType: Int16, data: 1789 > > > >
2023-01-03T13:10:07.185477204+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x94B8, dest_endpoint: 0x19, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0012 > > >
2023-01-03T13:10:07.199213537+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0x94B8, dest_endpoint: 0x19, profile: 0x0104, cluster: Thermostat >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x00 >, < ReadAttribute || AttributeId: 0x0008 > > >
2023-01-03T13:10:07.237576871+00:00 DEBUG Zigbee Thermostat Master Bath Thermostat device thread event handled
2023-01-03T13:10:07.706954871+00:00 TRACE Zigbee Thermostat Received event with handler zigbee
2023-01-03T13:10:07.736405204+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x94B8, src_endpoint: 0x19, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCC, rssi: -71, body_length: 0x0004, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3E, ZCLCommandId: 0x04 >, < WriteAttributeReponse || ZclStatus: SUCCESS > > >
2023-01-03T13:10:07.803270537+00:00 TRACE Zigbee Thermostat Received event with handler zigbee
2023-01-03T13:10:07.825208538+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x94B8, src_endpoint: 0x19, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCA, rssi: -70, body_length: 0x0009, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x3F, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0012, ZclStatus: SUCCESS, DataType: Int16, OccupiedHeatingSetpoint: 1789 > > > >
2023-01-03T13:10:07.924547871+00:00 DEBUG Zigbee Thermostat Master Bath Thermostat device thread event handled
2023-01-03T13:10:07.948999871+00:00 TRACE Zigbee Thermostat Found ZigbeeMessageDispatcher handler in zigbee-thermostat → stelpro ki zigbee thermostat
2023-01-03T13:10:08.026208204+00:00 INFO Zigbee Thermostat Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: OccupiedHeatingSetpoint
2023-01-03T13:10:08.068438204+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> emitting event: {“attribute_id”:“heatingSetpoint”,“capability_id”:“thermostatHeatingSetpoint”,“component_id”:“main”,“state”:{“unit”:“C”,“value”:17.89}}
2023-01-03T13:10:08.260834871+00:00 DEBUG Zigbee Thermostat Master Bath Thermostat device thread event handled
2023-01-03T13:10:08.875376204+00:00 DEBUG Zigbee Thermostat driver device thread event handled
2023-01-03T13:10:09.120873538+00:00 TRACE Zigbee Thermostat Received event with handler zigbee
2023-01-03T13:10:09.130068538+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> received Zigbee message: < ZigbeeMessageRx || type: 0x00, < AddressHeader || src_addr: 0x94B8, src_endpoint: 0x19, dest_addr: 0x0000, dest_endpoint: 0x01, profile: 0x0104, cluster: Thermostat >, lqi: 0xCC, rssi: -70, body_length: 0x0008, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x18, seqno: 0x40, ZCLCommandId: 0x01 >, < ReadAttributeResponse || < AttributeRecord || AttributeId: 0x0008, ZclStatus: SUCCESS, DataType: Uint8, PIHeatingDemand: 0x00 > > > >
2023-01-03T13:10:09.353498871+00:00 TRACE Zigbee Thermostat Found ZigbeeMessageDispatcher handler in zigbee-thermostat → stelpro ki zigbee thermostat
2023-01-03T13:10:09.372849871+00:00 INFO Zigbee Thermostat Executing ZclClusterAttributeValueHandler: cluster: Thermostat, attribute: PIHeatingDemand
2023-01-03T13:10:09.404263538+00:00 INFO Zigbee Thermostat <ZigbeeDevice: 202da3e5-75eb-4884-a4d8-3511e1c3568f [0x94B8] (Master Bath Thermostat)> emitting event: {“attribute_id”:“thermostatOperatingState”,“capability_id”:“thermostatOperatingState”,“component_id”:“main”,“state”:{“value”:“idle”}}
Thank you, thats what I thought
@nayelyz any update on this, it seems the Zwave Stelpro’s were having the same issue and I see someone was working on it. How about the Zigbee version, ST is auto migrating them now and more people are having the same issue now.
Hi @mlchelp
Could you try this driver version for your thermostat?
───────────────────────────────────────────────────
Name Zigbee Thermostat Mc
Version 2023-02-18T15:54:51.831614748
───────────────────────────────────────────────────
1 Like
Mariano, yes and thank you. I will try it when I get home tonight.
Mariano, thank you. It works perfectly. No more decimal point when changing the temperature and It works for the 2 temperatures that didn’t work 65 and 67. Much appreciated.
1 Like
Yes thank you @Mariano_Colmenarejo I am now using your zigbee driver 
Turns out only one of my 8 thermostats were zigbee, the other 7 are the stelpro zwave
I wonder if I could use the ZWave Thermostat Mc edge driver ?
The exact same issue happens to these as to the zigbee?
I have seen that for Z-wave they made a change in the production code for these thermostats in the adjustment of the heat set point
I wasn’t getting the same error for zwave as zigbee. I have updated to use your drivers across the board. Thank you again
1 Like