I have purchased and set up an Aqara FP1E presence sensor. I have at least eight Aqara temperature/humidity sensors paired with me C7 hub. They work because I have multiple Ikea Zigbee repeaters that keep my Aqara temperature sensors from falling off the network.
I added the FP1E driver via HPM. I paired the device successfully. The problem is that it has never detected anything and the health goes to offline within a minute of pairing.
You are trying the wrong driver, the one is from Jonathan Bradshaw works only with old Aqaraa FP1 sensor.
You need to use the "Aqara P1 Motion Sensor" driver :
Keep in mind that pairing the Aqara FP1 and Aqara FP1E sensors to Hubitat is not easy. You must pair the device at least twice from a close distance from the hub.
Not absolutely neccesery, but when paired directly to HE we will be missing the “AI spatial learning ” feature, whatever it is.
Ok, so I did originally reference the link you provided. In that link it suggests the HPM install. Per your advice, I uninstalled the HPM driver and manually installed the other in the link. Not the question is, "What does it mean to pair the device at least twice?" When I un-pair and pair the device again isn't that like starting over? Why would that make a difference?
In using the manually installed driver, the device now looks like below. The health is still "unknown" and I see no "zone" setting which is the point of this device. At first glance this appears to be just like a standard PIR motion detector except that those seem to work better. I still feel like I am missing something.
In reading everything on the web, I see no one that has one of these apparently working except through Aqara's proprietary hub and app. Looks like the majority of those who have had success end up using it in the Amazon eco-system. Maybe I should send this back and get one of the FP1 devices instead? Your thoughts?
I will try to answer as detailed as I can, so I will be quoting your questions.
Uninstalling the same driver to install it from HPM works, but you can achieve the same result using HPM 'Match Up' function.
Note, that there are two similarly named drivers in HPM - Jonathans 'Aqara Human Presence Sensor FP1'`and mine 'Aqara P1 Motion Sensor'. The screenshot in your first post shows Jonathan's driver, which is for Aqara FP1 and will not work with Aqara FP1E.
Pair the device, then pair it again without removing it from the hub. The hub will recognize it and initialize it correctly on the second attempt.
I have edited the pairing hint in the Preferences section a bit :
If you can suggest better wording, please help - English is not my primary language.
It makes a difference, but I am not sure why this is needed with HE hubs. When writing the old FP1 driver before one year, I was able to make it pair easy and correctly to SmartThings V2 hub, to Home Assistant Z2M, but not to Hubitat hubs. There is something in the HE pairing procedure that Aqara doesn't like... So I had to implement heavy workarounds in the initial pairing exchange of Zigbee messages (mimicking the Aqara hub responses / pretending to be an Aqara hub....) - no other platforms need this.
Anyway, for a successful initialization, two consecutive pairing attempts without deleting/removing the device in between are needed.
When pairing for a second or third time (very close to the hub!), observe the live logs, If there are just a few lines of debug logs, you must try pairing once again. An indication of a successful initialization is the number of the received Zigbee messages - this is the 'rxCounter' state variable :
Aqara FP1E does not have zone settings!
The old FP1 has zones, although I never made them work successfully enough, even with Jonathans driver.
Every device marketed as a 'presence sensor' is actually a very sensitive motion sensor, but the motion detection principle is different. Sensors based on sophisticated analysis of the reflected mmWaves can detect micro-motions, such as the movement of a human chest while breathing.
This is a very new device by Aqara, the folks from Z2M, ZHA, Deconz are still working on it!
I would suggest to get a cheap Aqara E1 Matter Bridge hub instead - it pairs instantly, and will benefit from the 'Enhanced Precision with AI', whatever this means..
Connecting the Aqara FP1E via the custom Matter Bridge package works just fine :
Aqara FP1E has the same difficult Zigbee direct pairing procedure as the Aqara P1 and Aqara FP1 sensors.
I hold the device reset button for about ten seconds and the light is flashing. I start the Zigbee pairing and it is detected right away, but now is never completing the pairing operation.
Also, in regards to your Pair twice without deleting comment, once a device is added to the HE, it would not be detected to pair again. How are you accomplishing the "pair twice"?
Any Zigbee coordinator (Hubitat hubs included) can pair one and the same device again.. if the DNI (Device Network Id) is already in the hub database, then it is recognized as an existing device and HE preserves the internal dB ID. Its always been like this.... It is shown on Hubitat Zigbee pairing web pages as 'found an existing device XXXXX'
Are you pairing the FP1E close to the hub?
You can also reboot the hub prior the second pairing attempt. Your hub is C-7, right? (because C-8 is known to have some Zigbee pairing problems at the moment with some Tuya and Aqara and other brands Zigbee 3.0 devices).
Something worth noting is that I finally stopped trying to pair the FP1E close to the HE. That was just never working at all. I ended up pairing it successfully in the location which is where I wanted to use it and near an IKEA Zigbee plug/repeater. My success was almost immediate with that approach and I am not sure why. I did have to go back and "pair again" as you say. For the years that I have been running HE I was completely unaware that it was possible to pair again without having to delete the device and start over. Very interesting! As your documentation states, when I paired the second time the device started working and has worked flawlessly for the two days since that time.
One question I have is I noticed that the driver in HPM does not have zones whereas the driver linked in your notes does not. I am using the driver that does not have zones. Is there a reason why I might not be able to use the driver with zones?
You have done amazing work. Thanks for that. I have to say that this device is like crash landed alien technology and my two cats never trigger occupancy as desired. However, the device always "sees" me and so I never have any false positives which is completely amazing.
@kkossev great work on the driver. This was one of the easiest devices I've paired. Instantaneous to pair, then I immediately paired again, and the second time everything was populated.
I particularly like the small movements and large movements. Using C7.
Aqara FP1E does not have zones. No zones are defined from Aqara hub / Aqara Home app.
This device reports periodically something that could be the distance to the detected moving object, but these seems inconsistent. There is no indication of a distance in Aqara Home app as well.
What could be added in the driver next week when I get back home is a configuration of the maximum detection distance. By default, it is the maximum 6 meters, but can be restricted to lesser.
It is also yet unknown whether the ‘AI learning’ feature (calibration) can be triggered without Aqara cloud servers in the play.
Anyway, the default settings after the factory reset seems to be working very well. I have zero false detections when I am not home.
I find the ads for the FP1E sensor on Amazon and on Aqara website to be interesting in that they say the device is a MATTER device. Am I missing something?
These ads are misleading ...
The comma in the ".... FP1E with Matter , Requires Aqara Zigbee 3.0 HUB"
means this is a Zigbee device exposed to other platforms via Aqara Matter Bridge hubs. Most of the Aqara Zigbee hubs are also Matter bridges.
Trying to add the device. I added the driver through hpm but I can't even add the device.
It says ZigBee device found, initializing please wait but then nothing happens.
I've tried close to the hub, further away and still nothing.
