[RELEASE] Tuya Temperature Humidity Illuminance LCD Display with a Clock (w/ healthStatus)

[kkossev]

I still need the device's fingerprint.

Change the driver temporarily to the HE inbuilt driver named 'Device', click on the 'Get Info' button,
The fingerprint should be in the live logs.

If nothing is found there, try again, but press the physical button on the top of the sensor at the same time when you click on GetInfo button.

P.S. seems like this is a problematic device, there are issues reported even with Zigbee2MQTT here.

But I should have started with the device fingerprint first. Try to obtain the fingerprint as in my previous post.
Next, update the driver again - time stamp 2023/05/21 11:06 PM. I have moved this device to TS0601_Tuya group now. My previous assumption for the device group seems to have been wrong. After updating the driver, clock the Initialize button , then F5 to refresh the page,

[mcchey]

I swap the driver from to "device" and click the "get info" and these appears in the live log...

H w Clock

dev:522023-05-23 12:51:24.172 PMtraceZCL version:03

dev:522023-05-23 12:51:24.150 PMtraceSoftware Build Id:unknown

dev:522023-05-23 12:51:24.144 PMtraceModel:TS0601

dev:522023-05-23 12:51:24.139 PMtraceManufacturer:_TZE200_cirvgep4

dev:522023-05-23 12:51:23.983 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 A034 01 00 0000 11 01 000340, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:A034, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:11, direction:01, data:[00, 03, 40]]

dev:522023-05-23 12:51:22.927 PMinfoZigbee parsed:[raw:A0340100001801002048E2FF2038E4FF2001, dni:A034, endpoint:01, cluster:0000, size:18, attrId:0001, encoding:20, command:0A, value:48, clusterInt:0, attrInt:1, additionalAttrs:[[value:38, encoding:20, attrId:FFE2, consumedBytes:4, attrInt:65506], [value:01, encoding:20, attrId:FFE4, consumedBytes:4, attrInt:65508]]]

dev:522023-05-23 12:51:17.894 PMinfoZigbee parsed:[raw:catchall: 0000 0013 00 00 0040 00 A034 00 00 0000 00 00 0034A043975BA24F38C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A034, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 34, A0, 43, 97, 5B, A2, 4F, 38, C1, A4, 80]]

dev:522023-05-23 12:51:04.719 PMdebuggetting info for unknown Zigbee device..

[kkossev]

Isn't there anything after the last trace log "ZCL version:03" ?
I need the fingerprint log that usually follows this trance log ...

Should look like this:

Try several times, pressing the device button before or after you click on the GetInfo button.

[mcchey]

These???

ev:522023-05-23 01:03:26.220 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 A034 01 00 0000 11 01 000340, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:A034, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:11, direction:01, data:[00, 03, 40]]

dev:522023-05-23 01:03:25.168 PMinfoZigbee parsed:[raw:A0340100001801002048E2FF2038E4FF2001, dni:A034, endpoint:01, cluster:0000, size:18, attrId:0001, encoding:20, command:0A, value:48, clusterInt:0, attrInt:1, additionalAttrs:[[value:38, encoding:20, attrId:FFE2, consumedBytes:4, attrInt:65506], [value:01, encoding:20, attrId:FFE4, consumedBytes:4, attrInt:65508]]]

dev:522023-05-23 01:03:20.139 PMinfoZigbee parsed:[raw:catchall: 0000 0013 00 00 0040 00 A034 00 00 0000 00 00 0034A043975BA24F38C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A034, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 34, A0, 43, 97, 5B, A2, 4F, 38, C1, A4, 80]]

dev:522023-05-23 01:03:17.645 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 A034 01 00 0000 11 01 000340, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:A034, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:11, direction:01, data:[00, 03, 40]]

dev:522023-05-23 01:03:16.588 PMinfoZigbee parsed:[raw:A0340100001801002048E2FF2038E4FF2001, dni:A034, endpoint:01, cluster:0000, size:18, attrId:0001, encoding:20, command:0A, value:48, clusterInt:0, attrInt:1, additionalAttrs:[[value:38, encoding:20, attrId:FFE2, consumedBytes:4, attrInt:65506], [value:01, encoding:20, attrId:FFE4, consumedBytes:4, attrInt:65508]]]

dev:522023-05-23 01:03:11.568 PMinfoZigbee parsed:[raw:catchall: 0000 0013 00 00 0040 00 A034 00 00 0000 00 00 0034A043975BA24F38C1A480, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:A034, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 34, A0, 43, 97, 5B, A2, 4F, 38, C1, A4, 80]]

dev:522023-05-23 01:02:49.639 PMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0004,0005,EF00,0000", outClusters:"0019,000A", model:"TS0601", manufacturer:"_TZE200_cirvgep4"

dev:522023-05-23 01:02:49.523 PMtraceZCL version:03

dev:522023-05-23 01:02:49.520 PMtraceSoftware Build Id:unknown

dev:522023-05-23 01:02:49.517 PMtraceModel:TS0601

[kkossev]

Yes, thanks!

[mcchey]

This one just arrived on Post, seen that it's one of the compatible ones, but no backlight... Worked first pairing, report Temp and Humidity. Yeah, we are having hot days here at the moment.

[kkossev]

So this is a different device than the previous _TZE200_cirvgep4 ?
Can you obtain the fingerprint (same way, as for the other device) ?

[mcchey]

This is a different one (No Backlight) ... just received it.. here are the logs.

Snsr T & H No Backlight

dev:532023-05-23 01:25:02.294 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 24 01 BD00, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[BD, 00]]

dev:532023-05-23 01:25:01.255 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 24 01 BA00, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[BA, 00]]

dev:532023-05-23 01:25:00.216 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 24 01 B700, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[B7, 00]]

dev:532023-05-23 01:24:59.184 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 24 01 B400, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[B4, 00]]

dev:532023-05-23 01:24:58.135 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 24 01 B100, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[B1, 00]]

dev:532023-05-23 01:24:57.094 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 24 01 AE00, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[AE, 00]]

dev:532023-05-23 01:24:56.055 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 24 01 AB00, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[AB, 00]]

dev:532023-05-23 01:24:55.013 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 24 01 A800, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[A8, 00]]

dev:532023-05-23 01:24:53.976 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 24 01 A500, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[A5, 00]]

dev:532023-05-23 01:24:53.305 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 24 01 A200, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[A2, 00]]

dev:532023-05-23 01:24:53.194 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 24 01 A000, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:24, direction:01, data:[A0, 00]]

dev:532023-05-23 01:24:53.056 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 02 01 009F1402000400000005, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 9F, 14, 02, 00, 04, 00, 00, 00, 05]]

dev:532023-05-23 01:24:52.936 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 02 01 009E130200040000000A, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 9E, 13, 02, 00, 04, 00, 00, 00, 0A]]

dev:532023-05-23 01:24:52.804 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 02 01 009D1202000400000096, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 9D, 12, 02, 00, 04, 00, 00, 00, 96]]

dev:532023-05-23 01:24:52.685 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 02 01 009C1102000400000096, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 9C, 11, 02, 00, 04, 00, 00, 00, 96]]

dev:532023-05-23 01:24:52.556 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 02 01 009B0D02000400000014, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 9B, 0D, 02, 00, 04, 00, 00, 00, 14]]

dev:532023-05-23 01:24:52.436 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 02 01 009A0C0200040000003C, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 9A, 0C, 02, 00, 04, 00, 00, 00, 3C]]

dev:532023-05-23 01:24:52.307 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 02 01 00990B02000400000000, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 99, 0B, 02, 00, 04, 00, 00, 00, 00]]

dev:532023-05-23 01:24:52.192 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 02 01 00980A02000400000186, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 98, 0A, 02, 00, 04, 00, 00, 01, 86]]

dev:532023-05-23 01:24:52.054 PMinfoZigbee parsed:[raw:catchall: 0104 EF00 01 01 0040 00 227B 01 00 0000 02 01 00970904000100, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:227B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:02, direction:01, data:[00, 97, 09, 04, 00, 01, 00]]

dev:532023-05-23 01:24:48.101 PMinfofingerprint profileId:"0104", endpointId:"01", inClusters:"0004,0005,EF00,0000", outClusters:"0019,000A", model:"TS0601", manufacturer:"_TZE200_locansqn"

dev:532023-05-23 01:24:47.976 PMtraceZCL version:03

dev:532023-05-23 01:24:47.969 PMtraceSoftware Build Id:unknown

dev:532023-05-23 01:24:47.966 PMtraceModel:TS0601

dev:532023-05-23 01:24:47.962 PMtraceManufacturer:_TZE200_locansqn

dev:532023-05-23 01:24:44.133 PMdebuggetting info for unknown Zigbee device..

[kkossev]

This is the same that I have. It's a bit chatty, but it works.

The other one (w/ backlight) is problematic. Currently, it doesn't work well even with Zigbee2MQTT . We will have to wait until a solution is found.

[mcchey]

Understand...bought it when I saw its on your list of working ones... Thank you so much for your help... I wish I am as knowledgeable and smart like you

[kahn-hubitat]

just got these from alliexpress.

it paired right up.. i already had your driver installed and it found it.
put the 3 aaa batteries in and long hold the button for 5 secs till wifi indicator starts flashing.

good job on the driver.. it actually go tthe date and time and set to fahrenheit..

here are some logs..

couple of questions..
i assume the config parameters dont work as it shows unconfig in the driver panel and has a warning that the params dont match.. if so it will reporting only once an hour or 5%.. no way to override?

second, in the logs it shows one device type but then another on the same line.. is there a mismatch.. see below..

thanks

finally a device with multiple aa or aaa batteries .. here is hoping it has great battery life in my wine fridges.. wonder about a freezer.. what is the temp range? ( looks like not speced for a freezer.. -10C = 14F) bummer

[kahn-hubitat]

put in wine fridge and even without changing settings.. not sure what that doesnt work as documentatoin says it supports it.. reporting is not unreasoneable and not flooding my zigbee mesh.. i think we have a keeper

[arnb]

@kahn-hubitat

here is hoping it has great battery life in my wine fridges.

In a room setting the supplied batteries for this exact device lasted from Aug 14, 2022 to May 3, 2023, YMMV.

[kahn-hubitat]

@arnb

In a room setting the supplied batteries for this exact device lasted from Aug 14, 2022 to May 3, 2023, YMMV.

you actrually had one that long ago.. where did you get it.. i couldnt find a zigbee model with aaa batteries until now.

[kahn-hubitat]

one other issue.. no battery percentage.. showing.. does it take a day or so before it comes up?

[arnb]

@kahn-hubitat

where did you get it

Purchased 3 on July 22, 2022 for ~ US $33.

https://www.aliexpress.us/item/3256803448038428.html

[arnb]

@kahn-hubitat

no battery percentage.. showing.. does it take a day or so before it comes up?

My devices report around every 2.5 hours.

[kahn-hubitat]

Checked still no battery reports. Maybe needs to go below 100?

[kkossev]

No, the battery percentage remaining should be reported automatically every few hours even when there is no charge.

I will look at this in the next days.

[kahn-hubitat]

Should i.leave it auto detect or set as 601 tuya?