Aqara Xiaomi RTCGQ11LM pairs and then never reconnects

[Ltek]

What happened?

Pairs fine, reads all attributes then never connects again. Looks like it break the link to the coordinator and never reconnects.. no matter where I place the motion sensor. I have 8 of these these same sensors connected to Conbee and working for 2+ years all over my house. The radios are in the same location.

What did you expect to happen?

communicate and update status of all parameters

How to reproduce it (minimal and precise)

Pair the device.

Zigbee2MQTT version

1.33.0

Adapter firmware version

EZSP v8 6.10.3.0 build 297

Adapter

Sonoff

Debug log

Debug log is empty.

[Rujith]

Have the same issue. Pairs fine, but then status is never updated. The same Aqara motion sensor works fine in ZHA

[therealpeterduke]

Hey,

I had the same problem with the motion detector and the MCCGQ11LM. The solution was for me (it has been running for a few days without any problems): Disconnect the device, start pairing mode and keep pressing the small button during this until the interview is completed. I did this several times in a row on different days until the connection remained stable.

The strange thing is that the devices do not connect to the coordinator that is closer, but to routers that are in the network.

I have two other MCCGQ11LMs that worked from the start without any problems.

Zigbee2MQTT version 1.33.2 Coordinator-Type EZSP v8

Good luck!

[Rujith]

Hey,

I had the same problem with the motion detector and the MCCGQ11LM. The solution was for me (it has been running for a few days without any problems): Disconnect the device, start pairing mode and keep pressing the small button during this until the interview is completed. I did this several times in a row on different days until the connection remained stable.

The strange thing is that the devices do not connect to the coordinator that is closer, but to routers that are in the network.

I have two other MCCGQ11LMs that worked from the start without any problems.

Zigbee2MQTT version 1.33.2 Coordinator-Type EZSP v8

Good luck!

Still didn't work, I will keep trying. Thanks for your help

[Ltek]

@Koenkk would love to have this fixed... its holding me back from migrating away from Conbee. Looks like this is a pervasive problem

[Koenkk]

This is probably related to the EZSP firmware you are running, I suggest to try a different fw.

[Ltek]

This is probably related to the EZSP firmware you are running, I suggest to try a different fw.

I'm running the stock Sonoff dongle, did know there was an alternative... please suggest something specific with a link... I'd have no idea what works/doesnt.

[essegi65]

This is probably related to the EZSP firmware you are running, I suggest to try a different fw.

I'm running the stock Sonoff dongle, did know there was an alternative... please suggest something specific with a link... I'd have no idea what works/doesnt.

I have the same problem with coordinator SLZB-06 FW: 2.0.8, Z2M ver: 1.33.2.1, HAASSOS: 2023.11.6 Always with xiaomi device: RTCGQ01LM. once the paring is done the status is not updated and the detection does not work

[Geoffrey54]

Same here, paring MCCGQ11LM is fine but losing connexion after. The sonoff coordinator is near the device. I will try to disconnect and reconnect it several time…

[Rujith]

Hey, I had the same problem with the motion detector and the MCCGQ11LM. The solution was for me (it has been running for a few days without any problems): Disconnect the device, start pairing mode and keep pressing the small button during this until the interview is completed. I did this several times in a row on different days until the connection remained stable. The strange thing is that the devices do not connect to the coordinator that is closer, but to routers that are in the network. I have two other MCCGQ11LMs that worked from the start without any problems. Zigbee2MQTT version 1.33.2 Coordinator-Type EZSP v8 Good luck!

Still didn't work, I will keep trying. Thanks for your help

Worked finally after several retries, reboots of HA, Z2M and battery removals etc. Not sure what helped, but finally it paired again.

[github-actions[bot]]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days

[Ltek]

This is a problem with Z2M... i'm on the latest FW and Z2M and it simply doesnt like these devices. I have 6 of them. They all pair fine, and quickly, with Conbee/Deconz... even v1 of Conbee device. I recently updated to Conbee III and it works with them also.