[ALPHA] Tuya Zigbee Multi-Sensor 4 In 1

Good idea...

Thanks for the tips @kkossev & @danabw, I finally found the problem or at least part of it, I was testing this sensor with some 16340 batteries, same as the CR123A but rechargeable and with these it was giving me constant motion detected events. So I changed the power source to a Mini-USB cable and all was working as it should!!! :grin:, so then I found some good CR123A Amazon Basics batteries and tried those to see if it's just a batterie issue, but still working as intended. :grinning:

So I'm guessing that either the rechargeable batteries are just somewhat depleted and need to be charged even though the sensor reports them as being 100%, or there is just some incompatibility with those cells. So I'll through them in the charger and test them again next week (going to the cabin for the weekend) and I'll report back with the results.

2 Likes

Excellent...great mystery, and great sleuthing to solve it! :slight_smile: I think we have a movie here, or at least a limited series. :smiley:

Using rechargeables is tough, because they can report at or near 100 up until the last minute, and then they die. I use rechargeables in small flashlights around the house and one will work fine and a few seconds later be dead...

2 Likes

Anyone have one of these 3-1 sensor long enough to evaluate battery life? I want to replace the battery hog MultiSenor6 's that I have.

my 4-in-1 should be here any day so I can throw my hat into the ring for testing

Just want to give a big shout out to the OP for developing such a versatile driver.

I had a couple of Neo Coolcam Motion Sensors (NAS-PD07 model: TS0601, manufacturer: _TZE200_7hfcudw5 ) which had been stuffed in drawer for about 6 months after unsuccessful and frustrated attempts to get them working with a number of other device handlers.

I have limited experience with the Zigbee payload so I had limited success in hacking together another driver based on the Zigbee - Tuya Alarm as it was limited to motion detection but the temperature values were way off.

Needless to say, finding this driver has made me one happy chappy! Cheers!

1 Like

My 4 in 1 finally got here, and seems to be working with your driver. Thanks! Is it possible to get the temp reports in °F instead of °C?

Sure, I am planning to get back to this driver development in the next days.

2 Likes

Tested this version of the TS0202:
image
I can not get active events less than a minute. The inactive event is random.

I also have these motion sensors:

Ugly and creepy. Like there is a Cylon watching you.
Interestingly the foot print is the same and it acts the same as the round one.

1 Like

FYI I also have these Tuya contact sensors. The are Huge. They have been rock solid using the Hubitat generic driver. None have ever dropped off the mesh. I have been using them on my refrigerator which historically has given me trouble using Xiaomi/Aqara and Sonoff sensors.
image

1 Like

It seems these simple sensors ( a.k.a. ZM-RT20) are capable of configuring the sensitivity and the 'keep time''' parameters. I have added a task in my TODO list to research more and implement it if possible.

The C/F conversion depending on the HE hub setting was added in ver 1.0.4.
Can you update the driver from the dev. branch (in post #2) and let me know if it works for you?
There were a lot of changes in the code related to the Radar sensors, if nothing is broken I will publish the release version tomorrow and will add the driver in HPM.

Mine is now saying it's due on the 29th of may (ordered a few weeks ago)...

Thanks, I really wasn't trying to add anything to your work. I thought I'd post other Tuya devices that I found were compatible with HE so that others can have more choice in devices.

1 Like

No worries, the idea for configuring the 'keep time' and the sensitivity for some TS0202 sensors was already in my plans.

Thank you. I updated and the driver automatically started to follow my Hubitat setting of °F

1 Like

@kkossev Got mine in today, using driver 1.04

and some not parsed stuff

dev:16382022-05-16 08:11:51.911 pm debugtuya 4-in-1 NOT PARSED : descMap = [raw:catchall: 0000 8021 00 00 0040 00 6D8A 00 00 0000 00 00 4C00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:6D8A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[4C, 00]]

dev:16382022-05-16 08:11:51.907 pm debugtuya 4-in-1 parse() descMap = [raw:catchall: 0000 8021 00 00 0040 00 6D8A 00 00 0000 00 00 4C00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:6D8A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[4C, 00]]

dev:16382022-05-16 08:11:50.911 pm debugtuya 4-in-1 NOT PARSED : descMap = [raw:catchall: 0000 8021 00 00 0040 00 6D8A 00 00 0000 00 00 4D00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:6D8A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[4D, 00]]

dev:16382022-05-16 08:11:50.908 pm debugtuya 4-in-1 parse() descMap = [raw:catchall: 0000 8021 00 00 0040 00 6D8A 00 00 0000 00 00 4D00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:6D8A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[4D, 00]]

dev:16382022-05-16 08:11:49.902 pm debugtuya 4-in-1 NOT PARSED : descMap = [raw:catchall: 0104 0000 01 01 0040 00 6D8A 00 00 0000 04 01 00, profileId:0104, clusterId:0000, clusterInt:0, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:6D8A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]

dev:16382022-05-16 08:11:49.899 pm debugtuya 4-in-1 parse() descMap = [raw:catchall: 0104 0000 01 01 0040 00 6D8A 00 00 0000 04 01 00, profileId:0104, clusterId:0000, clusterInt:0, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:6D8A, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]

dev:16382022-05-16 08:09:52.185 pm infoZigbee description:enroll request endpoint 0x01 : data 0x0015

dev:16382022-05-16 08:09:51.886 pm infoZigbee description:zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000

dev:16382022-05-16 08:09:19.863 pm infofingerprint profileId:"0104", endpointId:"01", inClusters:"0000,0001,0500,EF00", outClusters:"0019,000A", model:"TS0202", manufacturer:"_TZ3210_zmy9hjay"

dev:16382022-05-16 08:09:19.765 pm infoZigbee description:enroll request endpoint 0x01 : data 0x0015

dev:16382022-05-16 08:09:19.507 pm traceZCL version:03

dev:16382022-05-16 08:09:19.498 pm traceSoftware Build Id:unknown

dev:16382022-05-16 08:09:19.496 pm traceModel:TS0202

dev:16382022-05-16 08:09:19.495 pm traceManufacturer:_TZ3210_zmy9hjay

dev:16382022-05-16 08:09:19.365 pm infoZigbee description:zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:FF, delay:0000

dev:16382022-05-16 08:09:18.783 pm debuggetting info for unknown Zigbee device...

dev:16382022-05-16 08:09:16.768 pm debugconfigure() called...

First of all thanks to OP for this thread. I was looking everywhere for motion&lux zigbee detector compatible with HE. I've just ordered 4in1 from the above link, one unit to start with but if working as advertised I'll be buying many more to kit out whole house.
Also found these from the same seller on Aliexpress, similar to TS0202 but with light sensor.

Ordered 1 for testing, I'll let you know if it works.

1 Like

It will be interesting to know for the 2 in 1 model whether the illuminance is reported when the light changes, no matter whether there is a motion or not. The 4 in 1 sensor works this way (independent illuminance reporting).

However, some cheaper motion sensors use to send illuminance reports only at the time when there is a motion detected, which makes the useability a bit questionable, except there is a 100% guarantee that the illuminance is reported (and processed in HE) well ahead of the motion event.

I'll update here as soon as I test it. Might be a nice(cheap) alternative to the 4in1.

Download the Hubitat app