Aqara FP1 and P1 motion sensors

Hi @kahn-hubitat ,

Unfortunately, in HE drivers it is not possible to dynamically enable/disable device capabilities. If this was possible (like in the SmartThings new Edge drivers) then the Battery capability could be disabled for the DC powered sensors and would not confuse the HomeKit integration displaying 'low battery' warnings.

Supporting different drivers for each different device is very time-consuming and practically impossible, so exposing additional attributes that are not used by a particular device is the compromise that we have to live with.

The bug in the "approachDistance" preference was that the codes were misplaced by 1:

old versions (wrong)   :  version 1.2.3 
-----------               -------------
not available             far     (correct)
far                       medium  (correct)
medium                    near    (correct)
near ( didn't work)       -

On the temperature reporting - it is definitely not a bug in the driver, but most probably a bug in Aqara firmware, as exactly the same problem is reported when using Home Assistant Z2M - one link is here, but the same problem was mentioned in other posts in Github.

Nevermind, figured it out.
Note to anyone, make sure and have significant space between your fan and your FP1 sensor else it'll think you're present still.

1 Like

I didn't mean get rid of the capability.
Homekit is probably a small subset of the users of this device. Don't break the hubitat battery
Reporting for that. If needed put an option to change the way you report it but otherwise leave it normal.

1 Like

@kkossev,
Thank for your support as always.
I have the following Aqara motion sensors:
Aqara P1 Motion Sensor - RTCGQ14LM – recently purchased and working well, no issues encountered

Aqara FP1 Human Presence Detector RTCZCGQ11LM - working well and no issues since first install

And 2no older Aqara RTCGQ11LM motion sensors; I've recently started testing the P1 drivers and found that one is working well and one stops responding after a day or so.

This sensor using P1 driver had no issue so far:

And, the sensor below stopped responding on the P1 sensor twice, so reverted to Xiaomi Aqara Mijia Sensors and Switches driver.
Note: battery was reporting 0% and stopped responding so I reverted to using the Xiaomi driver again.

Any suggestions or further tests I can do?
Thanks
EDIT: I have now replaced the battery, will monitor and see if there are any further issues.

1 Like

Hi @iEnam ,
Thank you for the feedback!

I will be monitoring this week how the older Aqara model "lumi.sensor_motion.aq2" (RTCGQ11LM) performs with this driver. But have in mind, that on a driver level it is not possible to influence whether a Zigbee device stays connected to the Zigbee network or not. Almost all drivers for Zigbee battery-powered 'sleepy' devices are passive, i.e. the drivers do not send any commands to the device during the normal day-to-day operation. The only exception is during the initial pairing and configuration. So I'm my opinion whether a Zigbee device falls off the network or not, does not depend on the driver used.

I find it strange that the sensor which is working OK with this driver is missing the LUMI 'manufacturer' data record in the Data section. Usually, this is a sign of incomplete pairing procedure,

1 Like

All,

As this thread became too big and it is now probably difficult to find information related to a particular Aqara motion or presence sensor model, I was thinking if it will be a good idea to start a new thread in the custom drivers section.

As this driver supports at least 4 different Aqara sensors, I am not sure what would be the better approach - to continue discussing all the sensors here, in one new common thread, or to create separate threads for each of the different FP1, P1, Precision, and other models Aqara sensors?

How to continue with the "Aqara P1 Motion Sensor" updates and discussions?

  • Continue in this thread.
  • Create a new thread in the 'custom drivers' category, common for all P1, FP1, Precision, and other Aqara sensors that use the same driver.
  • Create new individual threads in the 'custom drivers' category, separately for each different type of Aqara sensor.

0 voters

Thanks for the tip. I was able to get full data only after removing the device and pairing again.

Both the RTCGQ11LM sensors are now using the P1 driver, will monitor for any issues.
Also, I note that these sensors do not report the voltage (you probably omitted it due to incorrect reporting?).

Thanks again

Interestingly, some of my RTCGQ11LM are reporting the battery regularly, but some of them - not!
Thank you for the report, will check it.

1 Like

Please see below.

  1. Aqara shower sensor (RTCGQ11LM) is working fine and battery source and percentage also available.
Summary


Summary

dev:15422022-12-06 10:58:50.089 AMinfoAqara shower sensor Battery level is 78% (2.89 Volts)

dev:15422022-12-06 10:58:50.083 AMdebugAqara shower sensor parse: Desc Map: [raw:CF2D0100004A01FF42210121E50B0328190421A8130521F700062430000000000A211F356410000B211600, dni:CF2D, endpoint:01, cluster:0000, size:4A, attrId:FF01, encoding:42, command:0A, value:!å
(!¨!÷$0
!­5d
!, clusterInt:0, attrInt:65281]

dev:15422022-12-06 10:58:50.076 AMdebugAqara shower sensor parse: description is read attr - raw: CF2D0100004A01FF42210121E50B0328190421A8130521F700062430000000000A211F356410000B211600, dni: CF2D, endpoint: 01, cluster: 0000, size: 4A, attrId: FF01, encoding: 42, command: 0A, value: 210121E50B0328190421A8130521F700062430000000000A211F356410000B211600

dev:15422022-12-06 10:53:14.243 AMinfoAqara shower sensor Motion reset to inactive after 30 s.

dev:15422022-12-06 10:52:44.244 AMinfoAqara shower sensor Detected motion

dev:15422022-12-06 10:52:44.220 AMdebugAqara shower sensor parse: Desc Map: [raw:CF2D0104060800001801, dni:CF2D, endpoint:01, cluster:0406, size:08, attrId:0000, encoding:18, command:0A, value:01, clusterInt:1030, attrInt:0]

dev:15422022-12-06 10:52:44.151 AMdebugAqara shower sensor parse: description is read attr - raw: CF2D0104060800001801, dni: CF2D, endpoint: 01, cluster: 0406, size: 08, attrId: 0000, encoding: 18, command: 0A, value: 01

dev:15422022-12-06 10:52:44.143 AMinfoAqara shower sensor illuminance is 21 Lux

dev:15422022-12-06 10:52:44.139 AMdebugAqara shower sensor parse: Desc Map: [raw:CF2D0104000A0000211500, dni:CF2D, endpoint:01, cluster:0400, size:0A, attrId:0000, encoding:21, command:0A, value:0015, clusterInt:1024, attrInt:0]

dev:15422022-12-06 10:52:44.134 AMdebugAqara shower sensor parse: description is read attr - raw: CF2D0104000A0000211500, dni: CF2D, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 1500

dev:15422022-12-06 10:51:32.400 AMinfoAqara shower sensor Motion reset to inactive after 30 s.

dev:15422022-12-06 10:51:02.401 AMinfoAqara shower sensor Detected motion

dev:15422022-12-06 10:51:02.376 AMdebugAqara shower sensor parse: Desc Map: [raw:CF2D0104060800001801, dni:CF2D, endpoint:01, cluster:0406, size:08, attrId:0000, encoding:18, command:0A, value:01, clusterInt:1030, attrInt:0]

dev:15422022-12-06 10:51:02.370 AMdebugAqara shower sensor parse: description is read attr - raw: CF2D0104060800001801, dni: CF2D, endpoint: 01, cluster: 0406, size: 08, attrId: 0000, encoding: 18, command: 0A, value: 01

dev:15422022-12-06 10:51:02.362 AMinfoAqara shower sensor illuminance is 20 Lux

dev:15422022-12-06 10:51:02.359 AMdebugAqara shower sensor parse: Desc Map: [raw:CF2D0104000A0000211400, dni:CF2D, endpoint:01, cluster:0400, size:0A, attrId:0000, encoding:21, command:0A, value:0014, clusterInt:1024, attrInt:0]

dev:15422022-12-06 10:51:02.353 AMdebugAqara shower sensor parse: description is read attr - raw: CF2D0104000A0000211400, dni: CF2D, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 1400

dev:15422022-12-06 10:49:52.946 AMinfoAqara shower sensor Motion reset to inactive after 30 s.

dev:15422022-12-06 10:49:22.953 AMinfoAqara shower sensor Detected motion

dev:15422022-12-06 10:49:22.917 AMdebugAqara shower sensor parse: Desc Map: [raw:CF2D0104060800001801, dni:CF2D, endpoint:01, cluster:0406, size:08, attrId:0000, encoding:18, command:0A, value:01, clusterInt:1030, attrInt:0]

dev:15422022-12-06 10:49:22.910 AMdebugAqara shower sensor parse: description is read attr - raw: CF2D0104060800001801, dni: CF2D, endpoint: 01, cluster: 0406, size: 08, attrId: 0000, encoding: 18, command: 0A, value: 01

dev:15422022-12-06 10:49:22.899 AMinfoAqara shower sensor illuminance is 26 Lux

dev:15422022-12-06 10:49:22.894 AMdebugAqara shower sensor parse: Desc Map: [raw:CF2D0104000A0000211A00, dni:CF2D, endpoint:01, cluster:0400, size:0A, attrId:0000, encoding:21, command:0A, value:001A, clusterInt:1024, attrInt:0]

dev:15422022-12-06 10:49:22.886 AMdebugAqara shower sensor parse: description is read attr - raw: CF2D0104000A0000211A00, dni: CF2D, endpoint: 01, cluster: 0400, size: 0A, attrId: 0000, encoding: 21, command: 0A, value: 1A00

dev:15422022-12-06 10:48:51.487 AMinfoAqara shower sensor Motion reset to inactive after 30 s.

dev:15422022-12-06 10:48:21.486 AMinfoAqara shower sensor Detected motion

dev:15422022-12-06 10:48:21.459 AMdebugAqara shower sensor parse: Desc Map: [raw:CF2D0104060800001801, dni:CF2D, endpoint:01, cluster:0406, size:08, attrId:0000, encoding:18, command:0A, value:01, clusterInt:1030, attrInt:0]

dev:15422022-12-06 10:48:21.454 AMdebugAqara shower sensor parse: description is read attr - raw: CF2D0104060800001801, dni: CF2D, endpoint: 01, cluster: 0406, size: 08, attrId: 0000, encoding: 18, command: 0A, value: 01

dev:15422022-12-06 10:48:21.446 AMinfoAqara shower sensor illuminance is 26 Lux

  1. Aqara kitchen sensor (RTCGQ11LM) seems to have stopped working last night; powerSource reading unknown (was reading battery previously), and battery percentage not available since pairing.
  1. Aqara kitchen sensor (RTCGQ11LM) seems to have stopped working last night; powerSource reading unknown (was reading battery previously), and battery percentage not available since pairing.
Summary



Thanks

I think that the issue with the Aqara/ kitchen sensor is a typical scenario where an old-generation Aqara (Xiaomi) sensor falls off the Zigbee network and does not automatically reconnect.

Pair it again to HE, but do it on-place, where the motion sensor final position will be. Then check the ZIgbee routing table 10 minutes later - does it communicate directly to the hub or via repeater?

1 Like

Thanks, I had actually paired it again yesterday afternoon.
It took several attempts to pair it with all data fields populated.
And, when it finally did, it was picked as a "device" driver and not the P1 drivers for some reason.
Note: the battery level did not show initially after successful pairing, but is showing now at 78% although a new battery was recently fitted.

Data


Logs

Also, I've just remotely viewed the child and route info, but the kitchen sensor route table entry is not available, not sure if it needs to be in use or something?

Routing table

But the good news is that the sensor seems to be working well now, thanks.

1 Like

Thank you all who gave your vote on the poll.

I will start creating new threads individually for each different type of Aqara motion/presence sensor, probably starting with the old models. Once done and the new threads are linked to this one, I can ask for closing it.

New forum thread for the older models Xiaomi/Aqara motion sensors : - [RELEASE] Aqara / Xiaomi Motion Sensors driver

New forum thread for the High Precision motion sensor : [RELEASE] Aqara High Precision Motion Sensor (RTCGQ13LM)

2 Likes

Both of my FP1s went offline this weekend (about 13 hours apart). They were working just fine until this happened.


and

I'm trying to reset and re-pair them, but holding down the button for 5s (or even 10s) doesn't seem to get it back into pairing mode. When I plug them in the blue LED blinks for an instant, but it never blinks when I hold the button down to reset them no matter how long I hold it.

I'm going to leave them off power for 10 minutes then try this:

Is there something else I should try?

One of my units wouldn't even pair - I would get a brief led flash and that was it. I think the trick may be to hold down for 10 secs then for 5 and timing is important.

I hope you have better luck, I eventually ended up throwing my unit away :rage:. My other FP1 in our powder room is still working fine though. :crossed_fingers:

Just to be clear - that's press and hold for 10s, release and then press and hold for 5s, correct? How long to have it released in the middle?

I'm trying this, and still not getting any response from either of my previously working FP1s. The LED doesn't light and they aren't re-pairing. The LED only briefly flashes when I first plug them in.

I can't tell you how long I futzed with it - other FP1 (I have 4) seemed to pair with little or no issues. In my case I am now almost certain it was a manufacturing defect. The FP1s appear to be well built so not sure what was going on :man_shrugging:

are they all on the same hub and what model of hubs?

I have 2 in operation now - C7 with updated firmware.

edit: also have tested on an rpi with UZB-7 and an install of HA. Both platforms work well..

edit2: ARGHHHHHH!!!!

Apologies @NoWon, have C7 / Z-Wave on the brain apparently it's a C5 on CH 13. With HA it was using a Sonoff ZB3 stick (the older one) CH 20.

I recently received 3 of them. All of them paired easily with my C-7 on channel 20. However, one of them will not reset to motion/presence inactive/not present no matter what I have tried so far (re-pairing, resetting, adjusting settings, moving the sensor, etc). Any ideas?

Happened to me as well in one of my 3 units.
Took it off the network rejoined and it worked again.
I did read that people are complaining about this in other forums as well