AGSHome Motion Detectors

thomas.keaney.sr · January 20, 2021, 8:52pm

I just purchased three of these. They are listed as compatible as of 2.2.3 in December 2020. They are detecting movement but I cannot get it to trip the lights. The log seems to indicate that it is not parsing correctly.

Help??

Device Details

Create Time	2021-01-18 2:40:29 PM PST
Last Update Time	2021-01-20 12:43:01 PM PST
Last Activity At
Data	* endpointId: 01

application: 45
manufacturer: TUYATEC-zn9wyqtr
model: RH3040
softwareBuild:
inClusters: 0000,0001,0500
outClusters: 0019,000A|
|In Use By|* Family Room Motion Zone Controller (Motion Zone)
Master (Dashboard)
Turn On & Set Level Bar Light when Family Room Active (Simple Automation Rule 1.1)|

Log file:
dev:2002021-01-20 12:46:16.830 pm warnparse(String description) not implemented

dev:2002021-01-20 12:46:16.718 pm warnparse(String description) not implemented

dev:2002021-01-20 12:45:14.485 pm warnparse(String description) not implemented

dev:2002021-01-20 12:45:14.378 pm warnparse(String description) not implemented

mike.maxwell · January 20, 2021, 9:06pm

what driver are you using?

thomas.keaney.sr · January 20, 2021, 9:07pm

When I set it up, I used generic dome motion sensor. Then I read the release notes and switched to:

AGSHome Motion using Generic Zigbee Motion Sensor (no temp)

thomas.keaney.sr · January 20, 2021, 9:10pm

I had the wrong set up, now I'm getting:

dev:2002021-01-20 01:08:41.006 pm debugdescMap: [raw:catchall: 0104 0500 01 01 0040 00 3877 00 00 0000 0B 01 0000, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3877, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2002021-01-20 01:08:40.240 pm debugdescMap: [raw:catchall: 0104 0500 01 01 0040 00 3877 00 00 0000 0B 01 0000, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3877, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2002021-01-20 01:08:39.623 pm debugdescMap: [raw:catchall: 0104 0500 01 01 0040 00 3877 00 00 0000 0B 01 0000, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3877, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

dev:2002021-01-20 01:08:39.276 pm debugdescMap: [raw:catchall: 0104 0500 01 01 0040 00 3877 00 00 0000 04 01 00, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:3877, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]

mike.maxwell · January 20, 2021, 9:14pm

yeah, i was going to say that message you posted it only contained within component drivers.

click configure, see if the device starts working.

If it doesn't you're going to have to wait until 2.2.5 releases as the specific device you have has a slightly different fingerprint than the one we tested with.
Some motion detectors will configure correctly after the fact, some wont.

If this one doesn't than after 2.2.5 comes out you will have to remove and re-include the device.

mr.murraybrandon · June 21, 2021, 12:36am

Anyone had success with this device? I have three of them, but they all send an inactive/active every minute, no matter which driver is being used. I have tried three different drivers, including the Generic Zigbee Motion Sensor (no temp). I think they need some special configuration. Given the RH3040 is so commonly available online and uses convenient AAA batteries, can anyone understand what's going on and patch an existing driver to make it work? Happy to provide low level transmission data.