I got it working. It’s billiant! Thank you so much for your work.
Do I need to keep the sensor’s driver as ‘Sensor and Child Thermostat Mc’ or I can switch it back to the original driver?
I don’t know what you mean
If you want to use the virtual thermostat, you have to keep it paired to this controller.
If you don’t want to use the virtual thermostat, you can delete the virtual thermostat with the app, like any other device and keep using the normal sensor with this driver or change the driver you want and that works
1 Like
Perfect thank you.
1 Like
Hi! I think it would be better to have both capabilities. I agree that the design might be weird, but that was Samsung’s design for some reason. In my case, I have been using it as a thermostat for years and I have never noticed that the temperature gets affected. I press the button around once or twice a day.
I’ll try to do it, but it will take longer.
I have to create specific profiles, subdriver and presentations.
I’ll let you know when it’s there, but it will be in the driver without child device, which has various types of devices
1 Like
It has been using the standard Zigbee Thermostat Device Handler no a custom one. It does not show the State, Power Source or Battery.
Then do i remove battery a powerSource?
Yes please
Moved to base-thermostat profile, without battery and power Source
───────────────────────────────────────────────────
Name Zigbee Thermostat Mc
Version 2023-01-16T09:39:28.552087089
───────────────────────────────────────────────────
This device exist in stock Zigbee Thermostat driver.
In production is not active now, but in beta drivers activated
# - id: "Danfoss/eTRV0100"
# deviceLabel: Danfoss Thermostat
# manufacturer: Danfoss
# model: eTRV0100
# deviceProfileName: thermostat-popp-danfoss
1 Like
Thanks. Do you know why its not showing stats. Is it possible to let it only change 0.5 degrees instead of 1 degrees. Perhaps as a possibility in settings.
I guess i will need to accumulate data to show statistics, but I don’t know.
I guess you will need to accumulate data to show statistics, but I don’t know.
Hi
I also got two new temp/hum sensors. Zigbee Thing MC is unable to fetch data.
Using your driver “Zigbee Temp Sensor and Child Thermostat Mc” it just doesnt work (no temp, hum, bat; error fetching data).
Usign CLI logcat i’we got this data (read below). Is there anything obvious?
Zigbee Device: d8c051a1-b28b-4f40-bfb7-2a658de7e606
Manufacturer: _TZ3000_xr3htd96
Model: TS0201
2023-01-17T17:01:35.691971952+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc Zigbee Device: d8c051a1-b28b-4f40-bfb7-2a658de7e606
Manufacturer: _TZ3000_xr3htd96 Model: TS0201
[1]: PowerConfiguration, Identify, TemperatureMeasurement, RelativeHumidity, Basic
2023-01-17T17:01:35.796566557+00:00 DEBUG Zigbee Temp Sensor and Child Thermostat Mc driver device thread event handled
2023-01-17T17:01:35.807771490+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc Received event with handler _resync
2023-01-17T17:01:35.813424648+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc Received event with handler environment_info
2023-01-17T17:01:35.859686101+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc Found DeviceLifecycleDispatcher handler in st-zigbee-temp
2023-01-17T17:01:35.865458319+00:00 WARN Zigbee Temp Sensor and Child Thermostat Mc Attempted to generate event for d8c051a1-b28b-4f40-bfb7-2a658de7e606.main but it does not support capability Illumin Condition
2023-01-17T17:01:35.873901538+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> emitting event: {“attribute_id”:“humidityCondition”,“capability_id”:“legendabsolute60149.humidityCondition”,“component_id”:“main”,“state”:{“value”:0}}
2023-01-17T17:01:35.909903864+00:00 PRINT Zigbee Temp Sensor and Child Thermostat Mc device:get_latest_state 0 table: 0x1f82f30
2023-01-17T17:01:35.930993403+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> emitting event: {“attribute_id”:“tempCondition”,“capability_id”:“legendabsolute60149.tempCondition2”,“component_id”:“main”,“state”:{“unit”:“C”,“value”:0}}
2023-01-17T17:01:35.989504311+00:00 WARN Zigbee Temp Sensor and Child Thermostat Mc Attempted to generate event for d8c051a1-b28b-4f40-bfb7-2a658de7e606.main but it does not support capability Illumin Target
2023-01-17T17:01:36.008952363+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> emitting event: {“attribute_id”:“humidityTarget”,“capability_id”:“legendabsolute60149.humidityTarget”,“component_id”:“main”,“state”:{“value”:" “}}
2023-01-17T17:01:36.038694894+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> emitting event: {“attribute_id”:“tempTarget”,“capability_id”:“legendabsolute60149.tempTarget”,“component_id”:“main”,“state”:{“value”:” "}}
2023-01-17T17:01:36.064734240+00:00 DEBUG Zigbee Temp Sensor and Child Thermostat Mc Tuya TS0201 device thread event handled
2023-01-17T17:01:36.075531970+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc Received event with handler environment_info
2023-01-17T17:01:36.085076406+00:00 DEBUG Zigbee Temp Sensor and Child Thermostat Mc Z-Wave hub node ID environment changed.
2023-01-17T17:01:36.121719719+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc Received event with handler device_lifecycle
2023-01-17T17:01:36.127507278+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> received lifecycle event: added
2023-01-17T17:01:36.140635505+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> received unhandled lifecycle event: added
2023-01-17T17:01:36.147680693+00:00 DEBUG Zigbee Temp Sensor and Child Thermostat Mc Tuya TS0201 device thread event handled
2023-01-17T17:01:36.157764732+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc Received event with handler device_lifecycle
2023-01-17T17:01:36.166838934+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> received lifecycle event: driverSwitched
2023-01-17T17:01:36.184953320+00:00 TRACE Zigbee Temp Sensor and Child Thermostat Mc Found DeviceLifecycleDispatcher handler in st-zigbee-temp
2023-01-17T17:01:36.196411713+00:00 DEBUG Zigbee Temp Sensor and Child Thermostat Mc Tuya TS0201 device thread event handled
2023-01-17T17:01:36.202934306+00:00 DEBUG Zigbee Temp Sensor and Child Thermostat Mc Tuya TS0201 device thread event handled
2023-01-17T17:01:41.210009261+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381129B577A3, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D970002076928, dest_endpoint: 0x01 > > >
2023-01-17T17:01:41.300905686+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0021, DataType: Uint8, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x5460, reportable_change: 0x01 > > > >
2023-01-17T17:01:41.344825302+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381129B577A3, src_endpoint: 0x01, cluster: TemperatureMeasurement, dest_addr_mode: 0x03, dest_address: 286D970002076928, dest_endpoint: 0x01 > > >
2023-01-17T17:01:41.362041239+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Int16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x012C, reportable_change: 16 > > > >
2023-01-17T17:01:41.450786589+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381129B577A3, src_endpoint: 0x01, cluster: RelativeHumidity, dest_addr_mode: 0x03, dest_address: 286D970002076928, dest_endpoint: 0x01 > > >
2023-01-17T17:01:41.501446240+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Uint16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x0E10, reportable_change: 0x0064 > > > >
2023-01-17T17:01:41.541424886+00:00 PRINT Zigbee Temp Sensor and Child Thermostat Mc maxTime y changeRep: 300 10.0
2023-01-17T17:01:41.561790063+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381129B577A3, src_endpoint: 0x01, cluster: TemperatureMeasurement, dest_addr_mode: 0x03, dest_address: 286D970002076928, dest_endpoint: 0x01 > > >
2023-01-17T17:01:41.607338493+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Int16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x012C, reportable_change: 10 > > > >
2023-01-17T17:01:41.662790538+00:00 PRINT Zigbee Temp Sensor and Child Thermostat Mc Humidity maxTime & changeRep: 600 100
2023-01-17T17:01:41.699120361+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381129B577A3, src_endpoint: 0x01, cluster: RelativeHumidity, dest_addr_mode: 0x03, dest_address: 286D970002076928, dest_endpoint: 0x01 > > >
2023-01-17T17:01:41.763188045+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Uint16, minimum_reporting_interval: 0x003C, maximum_reporting_interval: 0x0258, reportable_change: 0x0064 > > > >
2023-01-17T17:01:41.807145013+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381129B577A3, src_endpoint: 0x01, cluster: PowerConfiguration, dest_addr_mode: 0x03, dest_address: 286D970002076928, dest_endpoint: 0x01 > > >
2023-01-17T17:01:41.820859533+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0104, cluster: PowerConfiguration >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0021, DataType: Uint8, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x5460, reportable_change: 0x01 > > > >
2023-01-17T17:01:41.972700416+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381129B577A3, src_endpoint: 0x01, cluster: TemperatureMeasurement, dest_addr_mode: 0x03, dest_address: 286D970002076928, dest_endpoint: 0x01 > > >
2023-01-17T17:01:42.048771432+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0104, cluster: TemperatureMeasurement >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Int16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x012C, reportable_change: 16 > > > >
2023-01-17T17:01:42.177543119+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0000, cluster: 0x0021 >, < ZDOMessageBody || < ZDOHeader || seqno: 0x00 >, < BindRequest || src_address: A4C1381129B577A3, src_endpoint: 0x01, cluster: RelativeHumidity, dest_addr_mode: 0x03, dest_address: 286D970002076928, dest_endpoint: 0x01 > > >
2023-01-17T17:01:42.238561613+00:00 INFO Zigbee Temp Sensor and Child Thermostat Mc <ZigbeeDevice: d8c051a1-b28b-4f40-bfb7-2a658de7e606 [0xAE67] (Tuya TS0201)> sending Zigbee message: < ZigbeeMessageTx || Uint16: 0x0000, < AddressHeader || src_addr: 0x0000, src_endpoint: 0x01, dest_addr: 0xAE67, dest_endpoint: 0x01, profile: 0x0104, cluster: RelativeHumidity >, < ZCLMessageBody || < ZCLHeader || frame_ctrl: 0x00, seqno: 0x00, ZCLCommandId: 0x06 >, < ConfigureReporting || < AttributeReportingConfiguration || direction: 0x00, attr_id: 0x0000, DataType: Uint16, minimum_reporting_interval: 0x001E, maximum_reporting_interval: 0x0E10, reportable_change: 0x0064 > > > >
2023-01-17T17:01:42.351237256+00:00 DEBUG Zigbee Temp Sensor and Child Thermostat Mc Tuya TS0201 device thread event handled
2023-01-17T17:02:05.195044794+00:00 DEBUG Zigbee Temp Sensor and Child Thermostat Mc driver device thread event handled
Hi @dusanhauko
What I see in this log is that the configuration has been sent to the device but there are no responses from the device.
If you have not sent any more messages, it means that the configuration has not reached the device or the device has answered and has not reached the hub.
Try pairing it another time, as close to the hub as possible.
Also try to reboot the hub or turn it off and on if it is a v3
@Mariano_Colmenarejo I have the"LCD Temperature & Humidity Sensor" - Model ZG-227ZL manufactured by Tuya (Zigbee ID:_TZE200_znbl8dj5/TS0601) and, unfortunately, I have the same problems described by @RafaelAntonio2022 :
Using the “Edge Driver Zigbee Temp Humidity Sensor Mc Version-5” i can add the device to smartthings, but the values (temperature, humidity and battery) stays in 0, even after several hours/days…
I even deleted the device and did a new search (several times)… but, with the same results…
Could you help? A big thanks!
Hi @Cesar_Novo
Nornally midel TS0601 uses tuya cluster EF00 and not works with this driver
1 Like
OK… Thanks!
@Cesar_Novo
This is a specific thread for devices using tuya cluster EF00
1 Like
@Mariano_Colmenarejo First of all, thanks for your answer! But, acccordingly to the author of the “generic EF00 device”, the _TZE200_znbl8dj5/TS0601, doesn’t use EF00 cluster…
So, right now ,i’m a bit “lost”…
Do you have any suggestion, please? Thanks!