Has anyone seen the new Tuya XZ-WSD01 Smart Brightness Thermometer Link I've ordered a couple to see how they go.
Tony
Nope. Short battery life (6-8 months), and (apparently) Celsius only.
Looks nice though!
Celsius only? Shoot. I was looking to pick one of these up to test myself.
I have them - branded Moes. Worked for a while, but now all flashing screens on/off.
I had a mad moment and may have been slightly drunk as I have 4 Moes Smart Brightness Thermometer doodads heading my way from China 
@snell would the item you have been working on be able to port over? I ask because if memory serves yours is working on lux, temp, humidity etc?
Just thought to check Zigbee2MQTT and
So it is doable, I just with there was such a thing where it would convert the MQTT to Groovey 
If you have zigbee2mqtt running somewhere, it is very simple to create a custom virtual device to bring any device paired to z2m into Hubitat. I do that for ~65 sensors.
I am a bit rubbish at all this, however, I have nearly finished my Zigbee2MQTT set up. I have loads of phones so have repurposed an old Samsung Galaxy Note 8 into Home Assistant Core. Just trying to figure out how to run my CC2531 for it as server (broker). Probably going to get a USB c hub to have it plugged in as well as ethernet, memory card etc
For now mine are back in the drawer. They EAT batteries when connected, all drained new batteries in 2-3 weeks, so I’m not going to replace until someone has better luck!
If they are a load of shite then I'll return them. I say that about a lot of things but yeah really mean it this time 
1 Like
Happy to have someone reuse the code or help get something working. But I do not have the temperature or humidity working yet. Mine still ONLY sends lux. Very frustrating after I got the 5-in-1 air Sensor working pretty readily.
A few days ago I've got a used Tuya XZ-WSD01 gadget for almost no money, together with a Tuya gateway. Works fine when paired to its gateway, using the Tuya V2 local integration shows in Home Assistant, respectively is available in Node-RED.
The most interesting fact is that this thing seems to work fine with SmartThings hub also!
I can't say for the battery life, but I think should be OK because when paired to ST there are no resets/reboots еffect every 2 minutes or so, no false zero readings of the lux value, Shows up in Hubitat using HubConnect (Omnipurpose driver).
...but - no luck porting the ST driver into HE... 
Hopefully will have more free time in the next days to experiment with the ST driver porting into HE. If anyone else wants to try, the ST driver link is this
Seems like the modified driver is now working in HE! 
I have just put a fresh battery cell and if the battery level is still 100% on Sunday I will publish the driver for tests.
This device behaves rather inconsistently, it was working just fine for 2 days, but today it started self-resetting again... after a lot of trials this is the code that seems to be working (at least for me) at the moment:
@andrew.j.habgood @lusciouslukey @tony4mikki @snell if you have a chance to test it, please let me know your results.
thanks @kkossev, ive got two of the zss-zk-thl units setup on my desk here and have them connected with a hubitat c6, ive just set them to use your drive and ill see how they go.
Previously 1 of the units was connected using the Xiaomi Aqara Mijia Sensors and Switches by wayoftheweb. The unit just stopped reporting using that driver and appeared to lock up showing 0 for temp and 0 for humidity.
Sitting on my desk this morning ive seen that same uni reset a number of times .
Not really sure about the quality of these devices.
Ill see how both go with your driver and give feedback here
Thanks again
Thank you @benwiseman for the feedback!
Digging further, I read a lot of similar complaints about Moes ZSS-TK-THL device resetting itself when paired to zigbee hubs different than Tuya. There is a long discussion on this topic in github, where some much more clever guys are trying to reverse-engineer the communication protocol between the sensor and the original Tuya hub, where this device is working without any problems!. Seems like there is some kind of specific configuration or specific replies from the hub to the device, that are implemented in the Tuya hubs only. When this sensor is paired to anything else, after a certain period of time not receiving the expected responses from the zigbee coordinator - the unit resets itself. The visual effect is that the illuminance shown on the E0ink display is 0, but the device sends once also zero values for the temperature and the humidity.
So, Moes ZSS-TK-THL is 'semi-working' with Hubitat at the moment... The only workaround that I am able to implement is to filter the zero readings after the reboots (that's the 'Filter zero readings' option in the driver). But visually the device will show 0 brightness, unit the emvironment illuminance is changed and the device refreshes the E-ink display... which is rather unpleasant.
ahh good to know smarter people than i are working on it. Thanks for your labour and smarts
1 Like
Hey, I have been otherwise occupied, however, just installed one now to test for you:
dev:3902021-09-07 12:49:56.826 infoT,H Plus L illuminance changed to 110
dev:3902021-09-07 12:49:56.821 debugdescription: read attr - raw: 34120104000A000021BF4F, dni: 3412, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: BF4F
dev:3902021-09-07 12:41:50.308 infoT,H Plus L illuminance changed to 131
dev:3902021-09-07 12:41:50.304 debugdescription: read attr - raw: 34120104000A000021B652, dni: 3412, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: B652
dev:3902021-09-07 12:40:58.272 infoT,H Plus L illuminance changed to 165
dev:3902021-09-07 12:40:58.262 debugdescription: read attr - raw: 34120104000A000021A056, dni: 3412, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: A056
dev:3902021-09-07 12:33:51.713 infoT,H Plus L temperature changed to 25.7°C
dev:3902021-09-07 12:33:51.662 debugdescription: read attr - raw: 34120204020A0000290D0A, dni: 3412, endpoint: 02, cluster: 0402, size: 0A, attrId: 0000, encoding: 29, command: 0A, value: 0D0A
dev:3902021-09-07 12:32:46.234 infoT,H Plus L illuminance changed to 145
dev:3902021-09-07 12:32:46.231 debugdescription: read attr - raw: 34120104000A0000216F54, dni: 3412, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 6F54
dev:3902021-09-07 12:32:44.679 infoT,H Plus L illuminance changed to 121
dev:3902021-09-07 12:32:44.669 debugdescription: read attr - raw: 34120104000A0000215D51, dni: 3412, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 5D51
dev:3902021-09-07 12:25:19.132 infoT,H Plus L illuminance changed to 145
dev:3902021-09-07 12:25:19.128 debugdescription: read attr - raw: 34120104000A0000216F54, dni: 3412, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 6F54
dev:3902021-09-07 12:25:11.243 infoT,H Plus L illuminance changed to 113
dev:3902021-09-07 12:25:11.239 debugdescription: read attr - raw: 34120104000A0000213450, dni: 3412, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 3450
dev:3902021-09-07 12:24:17.097 infoT,H Plus L temperature changed to 26.0°C
dev:3902021-09-07 12:24:17.013 debugdescription: read attr - raw: 34120204020A0000292C0A, dni: 3412, endpoint: 02, cluster: 0402, size: 0A, attrId: 0000, encoding: 29, command: 0A, value: 2C0A
dev:3902021-09-07 12:20:28.116 debugrefreshing Moes ZSS-ZK-THL battery status
dev:3902021-09-07 12:20:17.918 infoT,H Plus L illuminance changed to 139
dev:3902021-09-07 12:20:17.914 debugdescription: read attr - raw: 34120104000A000021B753, dni: 3412, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: B753
dev:3902021-09-07 12:20:16.339 infoT,H Plus L illuminance changed to 107
dev:3902021-09-07 12:20:16.336 debugdescription: read attr - raw: 34120104000A000021474F, dni: 3412, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 474F
dev:3902021-09-07 12:20:13.187 infoT,H Plus L illuminance changed to 146
dev:3902021-09-07 12:20:13.183 debugdescription: read attr - raw: 34120104000A0000218D54, dni: 3412, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 8D54
dev:3902021-09-07 12:20:04.521 infoT,H Plus L illuminance changed to 119
dev:3902021-09-07 12:20:04.508 debugdescription: read attr - raw: 34120104000A0000211451, dni: 3412, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 1451
dev:3902021-09-07 12:18:48.109 debugrefreshing Moes ZSS-ZK-THL battery status
dev:3902021-09-07 12:18:06.853 debugrefreshing Moes ZSS-ZK-THL battery status
dev:3902021-09-07 12:18:03.841 debugrefreshing Moes ZSS-ZK-THL battery status
dev:3902021-09-07 12:18:03.835 debugsendZigbeeCommands(cmd=[zdo bind 3412 0x01 0x01 0x0400 {0C4314FFFE58A259} {}, delay 1186, zdo bind 3412 0x01 0x01 0x0402 {0C4314FFFE58A259} {}, delay 1187, zdo bind 3412 0x01 0x01 0x0405 {0C4314FFFE58A259} {}, delay 1189, zdo bind 3412 0x02 0x01 0x0400 {0C4314FFFE58A259} {}, delay 1186, zdo bind 3412 0x02 0x01 0x0402 {0C4314FFFE58A259} {}, delay 1187, zdo bind 3412 0x02 0x01 0x0405 {0C4314FFFE58A259} {}, delay 1189, he raw 0x3412 1 0x01 0x0400 {10 00 00 00 00}, delay 2000, he raw 0x3412 1 0x01 0x0402 {10 00 00 00 00}, delay 2000, he raw 0x3412 1 0x01 0x0405 {10 00 00 00 00}, delay 2000])
dev:3902021-09-07 12:18:03.828 debugConfiguring Moes ZSS-ZK-THL Reporting and Bindings
dev:3902021-09-07 12:18:03.827 debugupdated
dev:3902021-09-07 12:18:00.504 debugrefreshing Moes ZSS-ZK-THL battery status
dev:3902021-09-07 12:18:00.498 debugsendZigbeeCommands(cmd=[zdo bind 3412 0x01 0x01 0x0400 {0C4314FFFE58A259} {}, delay 1186, zdo bind 3412 0x01 0x01 0x0402 {0C4314FFFE58A259} {}, delay 1187, zdo bind 3412 0x01 0x01 0x0405 {0C4314FFFE58A259} {}, delay 1189, zdo bind 3412 0x02 0x01 0x0400 {0C4314FFFE58A259} {}, delay 1186, zdo bind 3412 0x02 0x01 0x0402 {0C4314FFFE58A259} {}, delay 1187, zdo bind 3412 0x02 0x01 0x0405 {0C4314FFFE58A259} {}, delay 1189, he raw 0x3412 1 0x01 0x0400 {10 00 00 00 00}, delay 2000, he raw 0x3412 1 0x01 0x0402 {10 00 00 00 00}, delay 2000, he raw 0x3412 1 0x01 0x0405 {10 00 00 00 00}, delay 2000])
dev:3902021-09-07 12:18:00.492 debugConfiguring Moes ZSS-ZK-THL Reporting and Bindings
dev:3902021-09-07 12:17:51.472 debugrefreshing Moes ZSS-ZK-THL battery status
dev:3902021-09-07 12:17:51.457 debugsendZigbeeCommands(cmd=[zdo bind 3412 0x01 0x01 0x0400 {0C4314FFFE58A259} {}, delay 1186, zdo bind 3412 0x01 0x01 0x0402 {0C4314FFFE58A259} {}, delay 1187, zdo bind 3412 0x01 0x01 0x0405 {0C4314FFFE58A259} {}, delay 1189, zdo bind 3412 0x02 0x01 0x0400 {0C4314FFFE58A259} {}, delay 1186, zdo bind 3412 0x02 0x01 0x0402 {0C4314FFFE58A259} {}, delay 1187, zdo bind 3412 0x02 0x01 0x0405 {0C4314FFFE58A259} {}, delay 1189, he raw 0x3412 1 0x01 0x0400 {10 00 00 00 00}, delay 2000, he raw 0x3412 1 0x01 0x0402 {10 00 00 00 00}, delay 2000, he raw 0x3412 1 0x01 0x0405 {10 00 00 00 00}, delay 2000])
dev:3902021-09-07 12:17:51.443 debugConfiguring Moes ZSS-ZK-THL Reporting and Bindings
dev:3902021-09-07 12:17:51.441 debugupdated
dev:3902021-09-07 12:17:04.735 infoZigbee parsed:[raw:34120204020A0000290D0A, dni:3412, endpoint:02, cluster:0402, size:0A, attrId:0000, encoding:29, command:0A, value:0A0D, clusterInt:1026, attrInt:0]
dev:3902021-09-07 12:10:23.285 infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0400", outClusters:"0019,000A", model:"TS0222", manufacturer:"_TYZB01_kvwjujy9"
dev:3902021-09-07 12:10:23.270 infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0400", outClusters:"0019,000A", model:"TS0222", manufacturer:"_TYZB01_kvwjujy9"
dev:3902021-09-07 12:10:23.267 infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0400", outClusters:"0019,000A", model:"TS0222", manufacturer:"_TYZB01_kvwjujy9"
dev:3902021-09-07 12:10:23.182 traceZCL version:03
dev:3902021-09-07 12:10:23.174 traceSoftware Build Id:unknown
dev:3902021-09-07 12:10:23.173 traceModel:TS0222
dev:3902021-09-07 12:10:23.171 traceManufacturer:_TYZB01_kvwjujy9
dev:3902021-09-07 12:10:23.148 traceZCL version:03
dev:3902021-09-07 12:10:23.142 traceSoftware Build Id:unknown
dev:3902021-09-07 12:10:23.141 traceModel:TS0222
dev:3902021-09-07 12:10:23.139 traceManufacturer:_TYZB01_kvwjujy9
dev:3902021-09-07 12:10:23.137 traceZCL version:03
dev:3902021-09-07 12:10:23.131 traceSoftware Build Id:unknown
dev:3902021-09-07 12:10:23.130 traceModel:TS0222
dev:3902021-09-07 12:10:23.128 traceManufacturer:_TYZB01_kvwjujy9
dev:3902021-09-07 12:10:22.988 infoZigbee parsed:[raw:34120204050A0000213418, dni:3412, endpoint:02, cluster:0405, size:0A, attrId:0000, encoding:21, command:0A, value:1834, clusterInt:1029, attrInt:0]
dev:3902021-09-07 12:10:21.054 debuggetting info for unknown Zigbee device...
dev:3902021-09-07 12:10:07.912 debuggetting info for unknown Zigbee device...
dev:3902021-09-07 12:10:07.199 debuggetting info for unknown Zigbee device...
dev:3902021-09-07 12:10:05.185 debugconfigure() called...
dev:3902021-09-07 12:09:37.212 infoZigbee parsed:[raw:34120204050A000021931A, dni:3412, endpoint:02, cluster:0405, size:0A, attrId:0000, encoding:21, command:0A, value:1A93, clusterInt:1029, attrInt:0]
dev:3902021-09-07 12:09:27.146 infoZigbee parsed:[raw:34120204050A000021181D, dni:3412, endpoint:02, cluster:0405, size:0A, attrId:0000, encoding:21, command:0A, value:1D18, clusterInt:1029, attrInt:0]
dev:3902021-09-07 12:09:27.028 infoZigbee parsed:[raw:34120204020A0000292E0A, dni:3412, endpoint:02, cluster:0402, size:0A, attrId:0000, encoding:29, command:0A, value:0A2E, clusterInt:1026, attrInt:0]
dev:3902021-09-07 12:09:20.961 infoZigbee parsed:[raw:34120104000A0000213254, dni:3412, endpoint:01, cluster:0400, size:0A, attrId:0000, encoding:21, command:0A, value:5432, clusterInt:1024, attrInt:0]
dev:3902021-09-07 12:09:18.222 infoZigbee parsed:[raw:34120104000A0000217134, dni:3412, endpoint:01, cluster:0400, size:0A, attrId:0000, encoding:21, command:0A, value:3471, clusterInt:1024, attrInt:0]
dev:3902021-09-07 12:09:15.980 infoZigbee parsed:[raw:catchall: 0000 8005 00 00 0040 00 3412 00 00 0000 00 00 D9001234020102, profileId:0000, clusterId:8005, clusterInt:32773, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:3412, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[D9, 00, 12, 34, 02, 01, 02]]
dev:3902021-09-07 12:09:15.859 infoZigbee parsed:[raw:34120104000A0000213B55, dni:3412, endpoint:01, cluster:0400, size:0A, attrId:0000, encoding:21, command:0A, value:553B, clusterInt:1024, attrInt:0]
dev:3902021-09-07 12:09:13.390 infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0400", outClusters:"0019,000A", model:"TS0222", manufacturer:"_TYZB01_kvwjujy9"
dev:3902021-09-07 12:09:13.276 traceZCL version:03
dev:3902021-09-07 12:09:13.268 traceSoftware Build Id:unknown
dev:3902021-09-07 12:09:13.266 traceModel:TS0222
dev:3902021-09-07 12:09:13.265 traceManufacturer:_TYZB01_kvwjujy9
dev:3902021-09-07 12:09:12.852 debuggetting info for unknown Zigbee device...
dev:3902021-09-07 12:09:11.762 infoZigbee parsed:[raw:34120204020A0000290D0A, dni:3412, endpoint:02, cluster:0402, size:0A, attrId:0000, encoding:29, command:0A, value:0A0D, clusterInt:1026, attrInt:0]
dev:3902021-09-07 12:09:10.952 infoZigbee parsed:[raw:34120104000A0000218657, dni:3412, endpoint:01, cluster:0400, size:0A, attrId:0000, encoding:21, command:0A, value:5786, `Preformatted text`clusterInt:1024, attrInt:0]
dev:3902021-09-07 12:09:10.837 debugconfigure() called...
dev:3902021-09-07 12:09:10.829 infoZigbee parsed:[raw:34120204050A000021C121, dni:3412, endpoint:02, cluster:0405, size:0A, attrId:0000, encoding:21, command:0A, value:21C1, clusterInt:1029, attrInt:0]
As I have 4 of the buggers currently one is on MQTT in home assistant and another in Smart Life Official to check for any disparity between data and performance.
1 Like
Thanks, @lusciouslukey !
What did you use for logging the communication between the device and the zigbee coordinator?
Meanwhile, I connected the ZSS-ZK-THL sensor to zigbee2mqtt and it working without visible problems for 2 hours!
I noticed the following in the logs:
Line 31064: debug 2021-09-08 20:21:48: Received Zigbee message from 'Moes TS0222 Z2M', type 'read', cluster 'genTime', data '["localTime"]' from endpoint 1 with groupID 0
Added a "zdo bind..." command for cluster 000A ,,,,, and now it has passed more than one hour without self-resting !!
Fingers crossed! 
ive had two connected since my last post, one keeps resetting quite often, the other appears stable. happy to log data if you tell me how.
