Xiaomi Aqara, RTCGQ11LM, Zigbee Motion Sensor not triggering

🛎️ Get Help
1

Hi,
I got a few Xiaomi Aqara, RTCGQ11LM, Zigbee Motion Sensors and I am trying to set them up to turn some hue lights on. Howeverm it doesn't seem to trigger.

The devices paired with HE, but it is seen as "Device", not as a motion sensor:

Data	
endpointId: 01
application:
softwareBuild: 3000-0001
inClusters: 0000,FFFF,0406,0400,0500,0001,0003
outClusters: 0000,0019
model: lumi.sensor_motion.aq2
manufacturer: LUMI

I can see the device logs and they look like this:

dev:1002020-01-17 09:08:33.936 am infoZigbee parsed:[raw:A7800100004201FF421D0121350C0328130421A81305214F00062401000000000A210000641001, dni:A780, endpoint:01, cluster:0000, size:42, attrId:FF01, encoding:42, command:0A, value:!5 (!¨!O$
!d, clusterInt:0, attrInt:65281]
dev:1072020-01-17 08:54:06.893 am infoZigbee parsed:[raw:20CA0100004A01FF42210121B30B03281D0421A81305213A00062401000000000A2100006410000B210300, dni:20CA, endpoint:01, cluster:0000, size:4A, attrId:FF01, encoding:42, command:0A, value:!³ (!¨!:$
!d !, clusterInt:0, attrInt:65281]
dev:1002020-01-17 08:18:26.522 am infoZigbee parsed:[raw:A7800100004201FF421D0121350C0328140421A81305214F00062401000000000A210000641001, dni:A780, endpoint:01, cluster:0000, size:42, attrId:FF01, encoding:42, command:0A, value:!5 (!¨!O$
!d, clusterInt:0, attrInt:65281]

Since it is not seen as Motion Sensor, it is also not visible in the Rule Machine and Zone Motion Controllers. I tried to make them visible by setting the device type to Generic Zigbee Motion Sensor, which works, but I get an error in the logs after this, whenever the device triggers, so this doesn't work either.

dev:1002020-01-17 09:08:33.936 am infoZigbee parsed:[raw:A7800100004201FF421D0121350C0328130421A81305214F00062401000000000A210000641001, dni:A780, endpoint:01, cluster:0000, size:42, attrId:FF01, encoding:42, command:0A, value:!5(!¨!O$
!d, clusterInt:0, attrInt:65281]
dev:1072020-01-17 08:54:06.893 am infoZigbee parsed:[raw:20CA0100004A01FF42210121B30B03281D0421A81305213A00062401000000000A2100006410000B210300, dni:20CA, endpoint:01, cluster:0000, size:4A, attrId:FF01, encoding:42, command:0A, value:!³(!¨!:$
!d!, clusterInt:0, attrInt:65281]
dev:1002020-01-17 08:18:26.522 am infoZigbee parsed:[raw:A7800100004201FF421D0121350C0328140421A81305214F00062401000000000A210000641001, dni:A780, endpoint:01, cluster:0000, size:42, attrId:FF01, encoding:42, command:0A, value:!5(!¨!O$
!d, clusterInt:0, attrInt:65281]

However, I did set up the Rule Machine and triggers and then changed the device type back to Device, but that does not work either.

In the Rule Machine I set up the trigger on "Motion Sensor" "changed" to be the event.

Any ideas if and how I could make this work?

Thanks.

2

Have you added the. Xiaomi drivers for the devices? These aren’t stock drivers and require installing manually.

You’ll find them here.

Then change the driver assigned for each device, to the new driver.

3 Likes
3

Ah, this could be it. I will check this later. Thanks.

1 Like
4

While you should definitely read/use the device driver thread linked to by @Royski, I want to point out that very few zigbee repeaters work with Xiaomi Mijia/Aqara sensors and you want to be sure you only have compatible repeaters or Xiaomi devices fall offline.

Here's a thread about pairing Xiaomi sensors and keeping them connected:

3 Likes
5

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.