huh, not looking good, the device seems to be refusing to respond to our request for information...
Without that we won't be able to identify the device.
I will try with another piece and see and let you know how it goes. Unfortunately, I had bought 4 of them ! Once again, thanks for your support.
You can always send me one, can't promise anything, but I might be able to see what's going on with it.
1 Like
Blockquote
dev:2212021-11-12 03:27:24.788 pm infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0003,0001,0500", outClusters:"0000,0003,0001,0500", model:"TS0203", manufacturer:"_TYZB01_xph99wvr"
dev:2212021-11-12 03:27:21.739 pm traceZCL version:03
dev:2212021-11-12 03:27:21.733 pm traceSoftware Build Id:unknown
dev:2212021-11-12 03:27:21.732 pm traceModel:TS0203
dev:2212021-11-12 03:27:21.730 pm traceManufacturer:_TYZB01_xph99wvr
sys:12021-11-12 03:27:21.133 pm Zigbee Discovery Stopped
dev:2212021-11-12 03:27:19.048 pm debuggetting info for unknown Zigbee device...
dev:2212021-11-12 03:27:17.890 pm infoZigbee parsed:[raw:5B6E01000108210020C8, dni:5B6E, endpoint:01, cluster:0001, size:08, attrId:0021, encoding:20, command:0A, value:C8, clusterInt:1, attrInt:33]
dev:2212021-11-12 03:27:17.887 pm infoZigbee parsed:[raw:5B6E010001082000201E, dni:5B6E, endpoint:01, cluster:0001, size:08, attrId:0020, encoding:20, command:0A, value:1E, clusterInt:1, attrInt:32]
dev:2212021-11-12 03:27:17.871 pm infoZigbee parsed:[raw:5B6E01000108210020C8, dni:5B6E, endpoint:01, cluster:0001, size:08, attrId:0021, encoding:20, command:0A, value:C8, clusterInt:1, attrInt:33]
dev:2212021-11-12 03:27:17.863 pm infoZigbee parsed:[raw:5B6E010001082000201E, dni:5B6E, endpoint:01, cluster:0001, size:08, attrId:0020, encoding:20, command:0A, value:1E, clusterInt:1, attrInt:32]
dev:2212021-11-12 03:27:17.669 pm infoZigbee parsed:[raw:catchall: 0000 0013 00 00 0040 00 5B6E 00 00 0000 00 00 006E5B5C21D90F004B120080, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:5B6E, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 6E, 5B, 5C, 21, D9, 0F, 00, 4B, 12, 00, 80]]
sys:12021-11-12 03:27:17.051 pm Found Previously Joined Zigbee Device Device
dev:2212021-11-12 03:27:17.032 pm debugconfigure() called...
Hey mate, how can I send you one for trouble shooting?
Sure
I just got couple of these sensors yesterday, so I wrote driver for it: https://raw.githubusercontent.com/surfingbytes/hubitat/master/drivers/tuya-zigbee-contact-sensor.groovy
It's my first hubitat driver, so it may have been written better, but it works. It also has motion capability, because I'm using it (soldered together with another part) in motion zone, so when you sit on chair, it reports motion and lights don't go off:
4 Likes
Can you share a link for pressure? sensor that you wired to the Tuya contact sensor?
Thanks!
This part for chair: DWCX Universal 40cm Car Seat Pressure Sensor Safety Belt Accessory Warning Reminder Pad Occupied Seated Alarm Plastic|Sensors & Switches| - AliExpress
This one for bed: https://www.amazon.de/-/en/Pressure-alarm-detects-intruders-burglars/dp/B084YWTBLG
1 Like
Wow..you are the man..It worked like a charm ! Thanks a ton...
Ive just bought a few of these Tuya Smart Wifi/zigbee Door Sensor Door Open / Closed Detectors Wifi Home Alarm Compatible With Alexa Google Home Smart Life App - Window Door Sensor - AliExpress
Doesn't seem to work with the generic driver and after having a search ive come across this thread.
@TOMAS1 Is your driver for this sensor or is yours a different model?
Mines called a zigbee door detector which takes 2 x AAA batteries with a red contact light
Thanks
Mine has button battery so it's different one. Set it to "device" driver and send me screenshot of Device page (Device Details - Data part), and screenshot of logs when the sensor sends open and close events. Can't promise it will work, but I'll try to add it to this driver.
3 Likes
Ok thank you
Is this what you mean @tomas1 ?
- endpointId: 01
- application: 45
- softwareBuild:
- inClusters: 0001,0003,0500,0000
- outClusters: 0003,0004,0005,0006,0008,1000,0019,000A
- model: TS0203
- manufacturer: _TZ3000_2mbfxlzr
dev:22842022-04-22 19:25:06.524 debuggetting info for unknown Zigbee device...
dev:22842022-04-22 19:24:41.636 infofingerprint profileId:"0104", endpointId:"01", inClusters:"0001,0003,0500,0000", outClusters:"0003,0004,0005,0006,0008,1000,0019,000A", model:"TS0203", manufacturer:"_TZ3000_2mbfxlzr"
dev:22842022-04-22 19:24:41.444 traceZCL version:03
dev:22842022-04-22 19:24:41.439 traceSoftware Build Id:unknown
dev:22842022-04-22 19:24:41.438 traceModel:TS0203
dev:22842022-04-22 19:24:41.437 traceManufacturer:_TZ3000_2mbfxlzr
dev:22842022-04-22 19:24:41.233 debuggetting info for unknown Zigbee device...
1 Like
The first part, yes. But I those logs are from device init, not from open/close events.
Ok where do I find the open close event logs? Thanks
settings, logs
ok, After deleting the device and re joining it closer to the hub i have some info in the logs
2022-04-24 16:37:29.007 infoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
dev:23162022-04-24 16:37:27.460 infoZigbee description:zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
dev:23162022-04-24 16:37:25.836 infoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
dev:23162022-04-24 16:37:18.383 infoZigbee description:zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
dev:23162022-04-24 16:37:17.070 infoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
dev:23162022-04-24 16:37:16.627 infoZigbee description:zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
dev:23162022-04-24 16:37:09.899 infoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000
Now ive re-added it closer to the hub ive used the generic zigbee contact sensor (no temp) driver and it seems to be working
3 Likes
Using Generic Zigbee Contact Sensor driver (no temp) driver (added close to hub) worked for me for Model:TS0203, so thanks!
2 Likes
