[RELEASE] Tuya Zigbee Multi-Sensor 4 In 1 (PIR motion sensors and mmWave presence radars) w/ healthStatus

[kkossev]

This driver can be installed from Hubitat Community Package Manager (HPM). Search for "Tuya Zigbee Multi-Sensor 4 In 1" or tag "Zigbee"

If you have already installed the driver manually, please do a Match search in HPM and then check for any updates.

The driver can be installed manually from: https://raw.githubusercontent.com/kkossev/Hubitat/main/Drivers/Tuya%20Multi%20Sensor%204%20In%201/Tuya%20Multi%20Sensor%204%20In%201.groovy

Most of Tuya Motion sensors should work out of the box using HE inbuilt "Generic Zigbee Motion Sensor (no temp)" driver. However, there are some non-standard Tuya motion sensors which never send 'Motion Inactive' events to HE, or have additional capabilities, or allow specific parameters configuration, or simply do not follow Zigbee ZHA 1.2 standards.

If your Tuya device did not work with the HE inbuilt drivers, simply changing to this driver is usually not enough. You need to pair the device again to HE hub, at a close distance (less than 1-2 meters). This driver should be selected automatically during the Zigbee pairing procedure. If not, most probably you have a new device model or manufacturer - please post the device details in this thread. The model and the manufacturer can be found on the Device Details - "Data' section. Please try to select. copy and paste these values as a text, not as a picture.

Supported Passive InfraRed (PIR) sensors :

Device	Links
Tuya ZigBee Multi-Sensor 4 in 1	Zigbee ID: _TZ3210_zmy9hjay, _TYST11_i5j6ifxj, _TYST11_7hfcudw5 AliExpress: link Price Range: Mid Reports: Motion, Illuminance, Temperature, Humidity Configuration: sensitivity, Keep Time, LED
Tuya ZigBee Multi-Sensor 3 in 1	AliExpress: link Amazon.de: link Price range: Mid Reports: Motion, Temperature, Humidity Configuration:Sensitivity, Keep Time
Tuya ZigBee Multi-Sensor 2 in 1	model: TS0601 Manufactuer: TZE200_3towulqd Battery: 2450 AliExpress: link1 AliExpress: link2 AliExpress: link3 Reports: motion and illuminance Configuration: sensitivity and rettrigger time (10/30/60/120)
TUYATEC RH3040 Motion Sensor	Reports: Motion, Battery AliExpress: link AliExpress: link Review:(link)
PIR Motion Sensor	Reports: Motion, Battery AliExpress: link1 AliExpress: link2 AliExpress: link3
Tuya ZigBee PIR Motion Sensor	Reports: Motion, Battery Zigbee ID: TS0202 _TZ3000_bsvqrxru AliExpress: link
PIR sensor TS0202	Reports: Motion, Battery AliExpress: link
Tuya Ceiling-mounted Human Presence Sensor AIR	Zigbee ID: "TS0601"; "__TZE200_auin8mzr" Price range: mid AliExpress: (link) Driver status: fully operational
Tuya Smart ZigBee Human Presence Detector	AliExpress: link Price range: mid/High Driver status: fully operational

Supported mmWave radars :

Device	Links
Tuya Smart ZigBee Smart Ceiling-mounted Human Presence Sensor 5.8 GHz mmWave radar w/ distance measurement	Zigbee ID: "TS0601"; "__TZE200_ztc6ggyl", "__TZE200_ikvncluo" , "__TZE200_lyetpprm" Price range: Mid/High Combined Radar and PIR and illuminance sensor, detects movement pretty fast! AliExpress: (link) MOES: (link) Amazon .com: (link) Driver status: fully operational
Tuya Smart ZigBee Smart Ceiling-mounted Human Presence Sensor 24 GHz mmWave radar w/ 'Scenes'	Zigbee ID: "TS0601"; "__TZE200_vrfecyku" Price range: High AliExpress: (link) Driver status: basic functionalities only, need testers
Tuya Smart ZigBee Smart Ceiling-mounted Human Presence Sensor 24 GHz mmWave radar w/ 'Fall Alarm'	Zigbee ID: "TS0601"; "__TZE200_lu01t0zl" Price range: High AliExpress: (link) Driver status: basic functionalities only, need testers
Tuya Square Black 24GHz radar w/ LED	Caution: chatty device! NOT RECOMMENDED to buy! Review: link AliExpress: (link)) Driver status: fully functional (LED enable/disable, presence detection timers)
NEW! OWON ZigBee Occupancy Sensor OPS305	10GHz mmWave radar from OWON OWON site: (link) Occupancy only, no configurable settings!

---

Compatibility

• Tuya specific cluster 0xEF00 PIR sensors
  Note: currently, the driver is tested only with :
  • model:"TS0202" PIR sensors
  • model:"TS0601" PIR sensors
  • model: "TS0601" Microwave Radars
• IAS cluster 0x0500 sensors
  • model:"TS0202" - various manufacturers
  • model:"RH3040" - various manufacturers
• Tuya new millimeter wave radards Human Presence sensor support

---

Features

• Motion detection
• Temperature
• Humidity
• Illuminance (4in1 models )
• Battery reporting (for most of the models)
• Tamper Alert (4in1 and 3in1 only)
• Reset Motion to Inactive software timer
• PIR sensor sensitivity configuration (for some models)
• Keep Time configuration (for some models)
• New Tuya radars 'Human Presence' support and specific configurations

---

[kkossev]

REVISIONS HISTORY:

• ver. 1.0.0 2022-04-16 - Inital test version
• ver. 1.0.1 2022-04-18 - IAS cluster multiple TS0202, TS0210 and RH3040 Motion Sensors fingerprints; ignore repeated motion inactive events
• ver. 1.0.2 2022-04-19 - setMotion command; state.HashStringPars; advancedOptions: ledEnable
• ver. 1.0.3 2022-05-05 - added '_TZE200_ztc6ggyl' 'Tuya ZigBee Breath Presence Sensor' ; Illuminance unit changed to 'lx'
• ver. 1.0.4 2022-05-06 - added isHumanPresenceSensorAIR(); isHumanPresenceSensorScene(); isHumanPresenceSensorFall(); convertTemperatureIfNeeded
• ver. 1.0.5 2022-06-11 - _TZE200_3towulqd +battery; 'Reset Motion to Inactive' made explicit option; sensitivity and keepTime for IAS sensors (TS0202-tested OK) and TS0601(not tested); capability "PowerSource" used as presence
• ver. 1.0.6 2022-07-10 - battery set to 0% and motion inactive when the device goes OFFLINE;
• ver. 1.0.7 2022-07-16 - _TZE200_ikvncluo (MOES) and _TZE200_lyetpprm radars; scale fadingTime and detectionDelay by 10; initialize() will resets to defaults; radar parameters update bug fix; removed unused states and attributes for radars
• ver. 1.0.8 2022-07-24 _TZE200_auin8mzr (HumanPresenceSensorAIR) unacknowledgedTime; setLEDMode; setDetectionMode commands and vSensitivity; oSensitivity, vacancyDelay preferences; _TZE200_9qayzqa8 (black sensor) Attributes: motionType; preferences: inductionTime; targetDistance.
• ver. 1.0.9 2022-08-11 kkossev - degrees Celsius symbol bug fix; added square black radar _TZE200_0u3bj3rc support, temperatureOffset bug fix; decimal/number type prferences bug fix
• ver 1.0.10 2022-08-15 - (dev. branch) - added Lux threshold parameter; square black radar LED configuration is resent back when device is powered on; round black PIR sensor powerSource is set to DC; added OWNON OCP305 Presence Sensor
• ver. 1.0.11 2022-08-22 - IAS devices initialization improvements; presence threshold increased to 4 hours; 3in1 exceptions bug fixes; 3in1 and 4in1 exceptions bug fixes;
• ver. 1.0.12 2022-09-05 - added _TZE200_wukb7rhc MOES radar
• ver. 1.0.13 2022-09-14 - added _TZE200_jva8ink8 AUBESS radar; 2-in-1 Sensitivity setting bug fix
• ver. 1.0.14 2022-10-31 - added Bond motion sensor ZX-BS-J11W fingerprint for tests
• ver. 1.0.15 2022-12-03 - OWON 0x0406 cluster binding; added _TZE204_ztc6ggyl _TZE200_ar0slwnd _TZE200_sfiy5tfs _TZE200_mrf6vtua (was wrongly 3in1) mmWave radards;
• ver. 1.1.0 2022-12-25 - SetPar() command; added 'Send Event when parameters change' option; code cleanup; added _TZE200_holel4dk; added 4-in-1 _TZ3210_rxqls8v0, _TZ3000_6ygjfyll, _TZ3210_wuhzzfqg
• ver. 1.1.1 2023-01-07 - illuminance event bug fix; fadingTime minimum value 0.5; SetPar command shows in the UI the list of all possible parameters; _TZ3000_6ygjfyll bug fix;
• ver. 1.2.0 2023-02-06- healthStatus; supressed repetative Radar detection delay and Radar fading time Info messages in the logs; logsOff missed when hub is restarted bug fix; capability 'Health Check'; _TZE200_3towulqd (2in1) new firmware versions fix for motion and battery %;
• ver. 1.2.1 2023-02-10 - reverted the unsuccessful changes made in the latest 1.2.0 version for _TZE200_3towulqd (2in1); added _TZE200_v6ossqfy as BlackSquareRadar; removed the wrongly added TUYATEC T/H sensor...
• ver. 1.2.2 2023-03-18 - typo in a log transaction fixed; added TS0202 _TZ3000_kmh5qpmb as a 3-in-1 type device'; added _TZE200_xpq2rzhq radar; bug fix in setMotion()
• ver. 1.3.0 2023-03-22 kkossev -'_TYST11_7hfcudw5' moved to 3-in-1 group; added deviceProfiles; fixed initializaiton missing on the first pairing; added batteryVoltage; added tuyaVersion; added delayed battery event; removed state.lastBattery; caught sensitivity par exception; fixed forcedProfile was not set automatically on Initialize;

The development branch version that contains the latest additions and bug fixes can be manually downloaded from here: https://raw.githubusercontent.com/kkossev/Hubitat/development/Drivers/Tuya%20Multi%20Sensor%204%20In%201/Tuya%20Multi%20Sensor%204%20In%201.groovy

An archive containing older driver versions is available here .

TODO :

• add TS0202 _TZ3210_cwamkvua [Motion Sensor and Scene Switch]
  (Tuya Motion Sensor and Scene Switch LKMSZ001 Zigbee compatibility)
• rename the state 'motionStarted' to 'lastMotion' and present it in a human-readable form.
• add to state 'last battery' the time when the battery was last reported.

[joaomf]

Hi @kkossev,

The 4 sensors are updating. I'll check at different times and compare it with other sensors I have here.

Thanks.

[rlithgow1]

hmmm.. Maybe I'll buy one of these and help out... I like the recessed cup

[Angus_M]

How is the 4-in-1 device for presence sensing? Reliable? If human is stationary? Retrigger time?

[jimhim]

Ordered the 4 in 1. Can't wait to try it. Now it just has to get here from China.....

[nclark]

Thanks @kkossev for this driver, I had bought this one with the Tuya hub hoping to get a driver out but I am just to swamped with work, getting our home ready to be sold and everything. I will be testing it out and everything seems to work after installing the driver. I'll try to get you feedback and features I would like to have with this one after a few days of testing.

[kkossev]

@Angus_M

If human is stationary?

I think that only the rather expensive 'radar' type motion sensors (or combined microwave + PIR sensors) are able to detect stationary live objects... like this one : Tuya Wifi / Zigbee Motion Pir 110v -240v Light Luminosity Sensor Radar Human Presence Detector - Infrared Alarm Detector - AliExpress

Or this one by Moes: Moes Tuya Smart ZigBee Human Presence Detector Radar Detection Sensor Photometric 2 in 1 Function Smart Life Ceiling PIR Hub| | - AliExpress

Or even cheaper: Tuya Smart ZigBee Smart Ceiling mounted Human Presence Sensor EU/US/UK Tuya Human Body Motion Detection Sensor APP key Control| | - AliExpress

[joaomf]

@Angus_M

Retrigger time?

45 seconds after stopping the movement.

[kkossev]

The different types of sensors have different retrigger times and different behavior:

• 4 in 1 motion sensor :
  • 10 seconds retrigger time,
  • sends motion active event every 10 seconds (if movement)
  • sends motion inactive 30, 60, 120 or 240 seconds after movement stops
• 3 in 1 motion sensor :
  • sends motion active event just once when the movement started
  • sends motion inactive 30, 60 or, 120 seconds after movement stops
• TUYATEC motion sensor :
  • sends motion active event just once when the movement started
  • sends motion inactive 60 seconds after movement stops
• TS0202 motion sensor (the small round one) :
  • 5 seconds (!!!) retrigger time,
  • sends motion active event every 5 seconds (if movement)
  • sends motion inactive 60 seconds after movement stops

In combination with the software 'Motion Reset' timer, it is possible to have two different configurations when there is frequent movement:

• single motion active, single motion inactive events - when the 'Motion Reset' timer is 0. The 'motion inactive' event may come several minutes later, when the motion stops.
• multiple motion active/inactive events - when the 'Motion Reset' timer value is a little higher than the device retrigger period. Active/Inactive events will come every 10 seconds from the '4 in 1' device or event faster from the small round sensor!

The above may not be 100% accurate, I will correct if I find any mistakes.

[nclark]

Finally got around to testing this and seems like my sensor might be defective or something, I'm always detecting motion, as soon as it resets, it will detect motion right away even when the house is completely empty.

My model on the sticker in the back is ZB003-X but is labeled as TS0202, it is a 4-1 multi sensor and all other functions seems to work perfectly (would like to have ±offset settings for temp, humidity and lux).

I have tried reseting the sensor, remove and re-include it, hit configure, etc. Still no change?

I am on the latest 1.0.2 driver, here is a copy of the logs if you might find something...

Motion logs

dev:7522022-04-28 10:08:33.058 infoMulti sensor ZB003-X Detected motion

dev:7522022-04-28 10:08:33.055 tracezs = [sourceEndpoint:01, alarm1Set:true, alarm2Set:false, tamperSet:false, batterySet:false, supervisionReportsSet:false, restoreReportsSet:false, troubleSet:false, acSet:false, testSet:false, batteryDefectSet:false, extendedStatus:00, zoneId:00, delay:0000]

dev:7522022-04-28 10:08:33.053 debugZone status: zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000

dev:7522022-04-28 10:08:33.051 debugMulti sensor ZB003-X parse() descMap = [:]

dev:7522022-04-28 10:08:33.044 debugMulti sensor ZB003-X NOT PARSED : descMap = [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

dev:7522022-04-28 10:08:33.041 debugMulti sensor ZB003-X parse() descMap = [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

dev:7522022-04-28 10:08:32.717 infoMulti sensor ZB003-X Motion reset to inactive after 42s

dev:7522022-04-28 10:08:32.715 tracezs = [sourceEndpoint:01, alarm1Set:false, alarm2Set:false, tamperSet:false, batterySet:false, supervisionReportsSet:false, restoreReportsSet:false, troubleSet:false, acSet:false, testSet:false, batteryDefectSet:false, extendedStatus:00, zoneId:00, delay:0000]

dev:7522022-04-28 10:08:32.713 debugZone status: zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000

dev:7522022-04-28 10:08:32.710 debugMulti sensor ZB003-X parse() descMap = [:]

dev:7522022-04-28 10:08:32.703 debugMulti sensor ZB003-X NOT PARSED : descMap = [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

dev:7522022-04-28 10:08:32.700 debugMulti sensor ZB003-X parse() descMap = [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

dev:7522022-04-28 10:07:50.577 infoMulti sensor ZB003-X Detected motion

dev:7522022-04-28 10:07:50.575 tracezs = [sourceEndpoint:01, alarm1Set:true, alarm2Set:false, tamperSet:false, batterySet:false, supervisionReportsSet:false, restoreReportsSet:false, troubleSet:false, acSet:false, testSet:false, batteryDefectSet:false, extendedStatus:00, zoneId:00, delay:0000]

dev:7522022-04-28 10:07:50.573 debugZone status: zone status 0x0001 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000

dev:7522022-04-28 10:07:50.570 debugMulti sensor ZB003-X parse() descMap = [:]

dev:7522022-04-28 10:07:50.563 debugMulti sensor ZB003-X NOT PARSED : descMap = [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

dev:7522022-04-28 10:07:50.560 debugMulti sensor ZB003-X parse() descMap = [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

dev:7522022-04-28 10:07:50.105 infoMulti sensor ZB003-X Motion reset to inactive after 42s

dev:7522022-04-28 10:07:50.103 tracezs = [sourceEndpoint:01, alarm1Set:false, alarm2Set:false, tamperSet:false, batterySet:false, supervisionReportsSet:false, restoreReportsSet:false, troubleSet:false, acSet:false, testSet:false, batteryDefectSet:false, extendedStatus:00, zoneId:00, delay:0000]

dev:7522022-04-28 10:07:50.101 debugZone status: zone status 0x0000 -- extended status 0x00 - sourceEndpoint:01, zoneId:00, delay:0000

dev:7522022-04-28 10:07:50.098 debugMulti sensor ZB003-X parse() descMap = [:]

dev:7522022-04-28 10:07:50.091 debugMulti sensor ZB003-X NOT PARSED : descMap = [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

dev:7522022-04-28 10:07:50.088 debugMulti sensor ZB003-X parse() descMap = [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

dev:7522022-04-28 10:07:07.950 infoMulti sensor ZB003-X Detected motion

[danabw]

@nclark

it will detect motion right away even when the house is completely empty.

Is it near any heat sources that might be triggering it? Have you tried moving it around to different locations to see if the behavior changes?

[kkossev]

Please post the device Manufacturer value from the web page 'Data' section.
Until now, this driver has been tested with manufacturer:"_TZ3210_zmy9hjay" only.

Tuya devices are identified by the manufacturer ID rather than the 'Model'.
What I see from the logs is an unexpected event coming from the On/Off Zigbee cluster, which is usually used in switches, not in motion sensors.

[nclark]

@kkossev

Please post the device Manufacturer value from the web page 'Data' section.
Until now, this driver has been tested with manufacturer:"_TZ3210_zmy9hjay" only.

• endpointId: 01
• model: TS0202
• application: A1
• manufacturer: _TZ3210_zmy9hjay

[nclark]

@danabw

Is it near any heat sources that might be triggering it? Have you tried moving it around to different locations to see if the behavior changes?

Did change it around and not heat source at all a part from my computer but it's not visible from the 3 placements I used in that room.

[nclark]

@kkossev

What I see from the logs is an unexpected event coming from the On/Off Zigbee cluster, which is usually used in switches, not in motion sensors.

Could it be the tamper function that might be defective, did not check your code at all to see if implemented or started to implement but who knows, it does say it has a tamper alarm.

Next step is that I might pair it to the tuya hub I have here and see what it does there, if I had more time I would sniff the packets on the tuya hub.

[kkossev]

@kkossev

_TZ3210_zmy9hjay

That's the one we have tested with...

Please change the driver to the inbuilt HE ''Generic Zigbee Motion Sensor''.
The motion detection should work with the standard driver too.

These are my logs:

Generic Zigbee Motion Sensor logs:

dev:19982022-04-28 18:20:04.746 debugskipped:[raw:catchall: 0104 EF00 01 01 0040 00 002B 01 00 0000 06 01 00006C0200040000002C, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:002B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6C, 02, 00, 04, 00, 00, 00, 2C]]

dev:19982022-04-28 18:20:04.741 debugdescMap: [raw:catchall: 0104 EF00 01 01 0040 00 002B 01 00 0000 06 01 00006C0200040000002C, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:002B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6C, 02, 00, 04, 00, 00, 00, 2C]]

dev:19982022-04-28 18:20:03.543 debugskipped:[raw:catchall: 0104 EF00 01 01 0040 00 002B 01 00 0000 06 01 00006B0200040000011A, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:002B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6B, 02, 00, 04, 00, 00, 01, 1A]]

dev:19982022-04-28 18:20:03.538 debugdescMap: [raw:catchall: 0104 EF00 01 01 0040 00 002B 01 00 0000 06 01 00006B0200040000011A, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:002B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6B, 02, 00, 04, 00, 00, 01, 1A]]

dev:19982022-04-28 18:20:02.335 debugdescMap: [raw:002B0304000A000021ED5C, dni:002B, endpoint:03, cluster:0400, size:0A, attrId:0000, encoding:21, command:0A, value:5CED, clusterInt:1024, attrInt:0]

dev:19982022-04-28 18:20:01.208 debugskipped:[raw:catchall: 0104 EF00 01 01 0040 00 002B 01 00 0000 06 01 00006E02000400000064, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:002B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6E, 02, 00, 04, 00, 00, 00, 64]]

dev:19982022-04-28 18:20:01.143 debugdescMap: [raw:catchall: 0104 EF00 01 01 0040 00 002B 01 00 0000 06 01 00006E02000400000064, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:002B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6E, 02, 00, 04, 00, 00, 00, 64]]

dev:19982022-04-28 18:19:59.936 debugdescMap: [raw:002B01000110210020C82000201C, dni:002B, endpoint:01, cluster:0001, size:10, attrId:0021, encoding:20, command:0A, value:C8, clusterInt:1, attrInt:33, additionalAttrs:[[value:1C, encoding:20, attrId:0020, consumedBytes:4, attrInt:32]]]

dev:19982022-04-28 18:19:29.598 info4 in 1 is inactive

dev:19982022-04-28 18:19:29.592 debugskipped:[raw:catchall: 0104 0006 02 01 0040 00 002B 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:002B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

dev:19982022-04-28 18:19:29.587 debugdescMap: [raw:catchall: 0104 0006 02 01 0040 00 002B 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:002B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

dev:19982022-04-28 18:18:47.524 info4 in 1 is active

dev:19982022-04-28 18:18:47.518 debugskipped:[raw:catchall: 0104 0006 02 01 0040 00 002B 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:002B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

dev:19982022-04-28 18:18:47.513 debugdescMap: [raw:catchall: 0104 0006 02 01 0040 00 002B 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:002B, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

[kkossev]

@nclark

Next step is that I might pair it to the tuya hub I have here and see what it does there, if I had more time I would sniff the packets on the tuya hub

Please hold on pairing it to Tuya hub if possible, let's keep this possibility as a last choice.

[nclark]

@kkossev

Please change the driver to the inbuilt HE ''Generic Zigbee Motion Sensor''.
The motion detection should work with the standard driver too.

ok just changed the driver, hit configure and still the same, motion detected every ~45 seconds

Logs with generic Zigbee Motion Sensor

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:26:29.637 [info](http://hubitat.local/device/edit/752)Multi sensor ZB003-X is active

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:26:29.635 [debug](http://hubitat.local/device/edit/752)skipped:[raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:26:29.632 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:26:29.171 [info](http://hubitat.local/device/edit/752)Multi sensor ZB003-X is inactive

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:26:29.169 [debug](http://hubitat.local/device/edit/752)skipped:[raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:26:29.166 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:46.871 [info](http://hubitat.local/device/edit/752)Multi sensor ZB003-X is active

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:46.869 [debug](http://hubitat.local/device/edit/752)skipped:[raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:46.866 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:46.471 [info](http://hubitat.local/device/edit/752)Multi sensor ZB003-X is inactive

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:46.469 [debug](http://hubitat.local/device/edit/752)skipped:[raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:46.466 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:08.790 [debug](http://hubitat.local/device/edit/752)skipped:[raw:catchall: 0104 EF00 01 01 0040 00 9E85 01 00 0000 06 01 00006C02000400000034, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6C, 02, 00, 04, 00, 00, 00, 34]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:08.787 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 EF00 01 01 0040 00 9E85 01 00 0000 06 01 00006C02000400000034, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6C, 02, 00, 04, 00, 00, 00, 34]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:07.587 [debug](http://hubitat.local/device/edit/752)skipped:[raw:catchall: 0104 EF00 01 01 0040 00 9E85 01 00 0000 06 01 00006B020004000000CE, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6B, 02, 00, 04, 00, 00, 00, CE]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:07.584 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 EF00 01 01 0040 00 9E85 01 00 0000 06 01 00006B020004000000CE, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6B, 02, 00, 04, 00, 00, 00, CE]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:06.382 [debug](http://hubitat.local/device/edit/752)descMap: [raw:9E850304000A0000212140, dni:9E85, endpoint:03, cluster:0400, size:0A, attrId:0000, encoding:21, command:0A, value:4021, clusterInt:1024, attrInt:0]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:05.185 [debug](http://hubitat.local/device/edit/752)skipped:[raw:catchall: 0104 EF00 01 01 0040 00 9E85 01 00 0000 06 01 00006E02000400000064, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6E, 02, 00, 04, 00, 00, 00, 64]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:05.182 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 EF00 01 01 0040 00 9E85 01 00 0000 06 01 00006E02000400000064, profileId:0104, clusterId:EF00, clusterInt:61184, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:06, direction:01, data:[00, 00, 6E, 02, 00, 04, 00, 00, 00, 64]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:25:03.983 [debug](http://hubitat.local/device/edit/752)descMap: [raw:9E8501000110210020C820002025, dni:9E85, endpoint:01, cluster:0001, size:10, attrId:0021, encoding:20, command:0A, value:C8, clusterInt:1, attrInt:33, additionalAttrs:[[value:25, encoding:20, attrId:0020, consumedBytes:4, attrInt:32]]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:24:34.541 [info](http://hubitat.local/device/edit/752)Multi sensor ZB003-X is active

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:24:34.539 [debug](http://hubitat.local/device/edit/752)skipped:[raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:24:34.536 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 01 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:24:34.086 [info](http://hubitat.local/device/edit/752)Multi sensor ZB003-X is inactive

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:24:34.079 [debug](http://hubitat.local/device/edit/752)skipped:[raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:24:34.076 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0006 02 01 0040 00 9E85 01 00 0000 00 00 , profileId:0104, clusterId:0006, clusterInt:6, sourceEndpoint:02, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:true, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:58.942 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0500 01 01 0040 00 9E85 00 00 0000 0B 01 0000, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:58.934 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0500 01 01 0040 00 9E85 00 00 0000 04 01 00, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:48.952 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0402 01 01 0040 00 9E85 00 00 0000 0B 01 0682, profileId:0104, clusterId:0402, clusterInt:1026, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[06, 82]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:48.944 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0000 8021 00 00 0040 00 9E85 00 00 0000 00 00 6F00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:9E85, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[6F, 00]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:48.940 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0001 01 01 0040 00 9E85 00 00 0000 0B 01 0682, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[06, 82]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:48.927 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0000 8021 00 00 0040 00 9E85 00 00 0000 00 00 6D00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:9E85, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[6D, 00]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:48.890 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0001 01 01 0040 00 9E85 00 00 0000 0B 01 0682, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[06, 82]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:48.887 [info](http://hubitat.local/device/edit/752)Multi sensor ZB003-X battery is 100%

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:48.874 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0000 8021 00 00 0040 00 9E85 00 00 0000 00 00 6B00, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:9E85, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[6B, 00]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:48.870 [debug](http://hubitat.local/device/edit/752)skipped:[raw:catchall: 0104 0402 01 01 0040 00 9E85 00 00 0000 01 01 000086, profileId:0104, clusterId:0402, clusterInt:1026, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 00, 86]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:48.867 [debug](http://hubitat.local/device/edit/752)descMap: [raw:catchall: 0104 0402 01 01 0040 00 9E85 00 00 0000 01 01 000086, profileId:0104, clusterId:0402, clusterInt:1026, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:9E85, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:01, direction:01, data:[00, 00, 86]]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:48.857 [debug](http://hubitat.local/device/edit/752)descMap: [raw:9E850100010A20002025, dni:9E85, endpoint:01, cluster:0001, size:0A, attrId:0020, encoding:20, command:01, value:25, clusterInt:1, attrInt:32]

[dev:752](http://hubitat.local/logs#dev752)2022-04-28 11:23:34.472 [warn](http://hubitat.local/device/edit/752)configure...

Got to run, will touch back when I'll be back in a couple hours.

[kkossev]

Seems like something is activating the motion sensor all the time... you can try putting it in a black box for a test?
Also, check or even better change the power supply. Do you have 2xCR123A batteries to test with? My past experience in the field of electronics is that 90% of the malfunctions are caused by a faulty power supply... so I always started with checking the PS.

Coincedally I just received my 4in1 sensor today, now it will be much easier to troubleshoot when I have the device!