I had one of my FP1's that refused to pair.. and had to give up. Incredibly frustrating but I think it was a hardware issue, the LED wasn't turning on etc. It could also be that the timing for pairing/reset whatever is far too tight meaning you have to hit it exactly at the right time..
Nope. I never got it paired other than to the aqara camera hub unfortunately. Wondering if it's a location restriction issue. I'm from the Caribbean.
Tried this too. Doesn't work lol. But I'm happy you got it added.
1 Like
Unfortunately I never did.. 
Providing the sensors are not defective and you are Apple products user : ) , there is an easy way to bring the FP1 occupancy status now in Hubitat.
FP1 -> Aqara E1 hub -> HomeKit -> virtual switch + 2 rules -> Hubitat
1 Like
I generally try not to use any 3rd party hubs if I can help it - would probably go with Home Assistant if I had to. Your drivers are working great for my other FP1s (many thanks!!) so the problem is likely a faulty device.
2 Likes
Update. So it now worked. I shut down the hub for about 8 hours and restarted just now. It paired immediately. Can't say directly what the issue is or was nor did I try to pair another Fp1 sensor. The one that wasn't working for hours now worked immediately though. No factory reset or anything done differently.
3 Likes
I am glad to hear that it worked for you!
Was the FP1 sensor powered on in the last 8 hours?
Both were left off.
I need to do some read up on the configurations and how to utilize in automations though since both are reading as a motion sensor although one determines presence. I cant select the presence sensor option.
Just use the motion attribute in your automations, like all other motion sensors (PIR).
I don't see any particular benefits of using the 'presence' attribute, it just represents some internal FP1 logic and is slower to fire up if compared to the digital motion attribute logic.
4 Likes
What, in particular, are you wanting to change?
@martin.machacek.cz thank you for the report, this and some other minor bugs should be fixed in the dev. branch version 1.2.3 timeSTamp 2022/12/04 9:59 AM. You can download it from the link in this post :
or even faster, by clicking on the "Import" button inside the HE driver editor.
I had to add a hardcoded '"100% battery level" for FP1 to get rid of the HomeKit's low battery warning. If the sensor goes offline for more than 3 hours by any reason, the battery level is forced to 0 (zero) and the batterySource attribute is forced to 'unknown'. These can be used to trigger notifications/alarms, although my FP1 has never left the Zigbee network since installed before several months.
In HomeKit Integration (beta) make sure the temperature and the illuminance are not exported, use just the Motion sensor capability :
The temperature sensor readings are now made configurable and disabled by default.
1 Like
how about not hardcoding or updating battery if power source is dc?
also when i updated the driver the distance reset from far to medium?\
last question is it reqally get a temp report from the device or just re-reporting the startup value because it never seems to change.. appears to me it is not really getting a temp report from the device
1 Like
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
