Make sure you are using version 1.7.0 (or later) of the ‘Aqara P1 Motion Sensor’ driver.
As already mentioned, pairing Aqara FP1 to Hubitat is not easy… Try pairing it several times in a close proximity to your C-7 hub. Pairing after the HE hub was rebooted seems to make it easier.
Once the pairings is successful, the FP1 stays connected to the hub without problems. The new generation Aqara devices do not suffer from dropping off the Zigbee network, that was a problem with the older devices. But the initial pairing is difficult.
Reboot the C-7 hub before pairing. If it still doesn't work, leave it for tomorrow, I will try to make some more detailed description of how the pairing works.
I always click on the pairing button on the HE web page first, then hold the device button for 5 seconds, until it flashes 3 or 4 times blue.
FWIW,
I was never able to get my FP1E to pair to a C-7 hub. Tried over and over for days, and finally gave up. However, I was happy to find out that I could make it work through the Matter Advanced Bridge after pairing it back to an Aqara E1 hub.
It will be interesting interesting if someone can compare the performance of two FP1E sensors, brought to Hubitat in the two different ways - one via direct Zigbee pairing and the second via the Matter Bridge, when processed natively by the Aqara hub.
For C-7 direct pairing what helped me is to reboot the hub, and pair the sensor (two times, without deleting the device) immediately after the hub reboot.
Thanks, I have tried your suggestions as well, no luck. The only thing I haven't tried is a different zigbee channel. Currently I am using channel 16 and I have several aqara devices paired including 3 FP1s. I am hesitant to change the channel in fear of messing up all the other aqara devices, but it may be worth a shot. This particular hub is dedicated to nothing but aqara devices
I am using Zigbee channel 25. After the device finally paired, it has been rock solid and very accurate. I wish only that the FP1E driver would do zones.
So I have 1 FP1 and 1 FP1E, the FP1E paired not so easily but it only took a couple of tries using the methods described above. Hold button 5 sec and then keep alive and hold button 5 sec again. However the FP1 will not pair in the same manner. It is found by my C-7 hub when initially paired but then tells me that I need to build a stronger zigbee network. I only have the one device on the zigbee as I was trying to avoid using it and stick with z wave only. But I really want a presence sensor so here I am. The devices will both be within 2-4 meters of the hub in two different rooms. 1 device about 1 meter away from the hub. Any ideas why the FP1 won't pair or what I am misssing so that I can get it paired. Just to point out my matter coms is disabled as I do not use it at this moment so I keep it off.
OK, rebooting made it work. maybe I had the 2 mixed up but it seems like the 2 different sensors report different values.
The FP1 was the first one that paired and I was having the issue with the FP1E. The FP1 allows you to set approach distance, motion sensitivity and monitoring mode and the return values of activity tell me if something is approaching.
The FP1E does not allow me to set the approach distance, motion sensitivity or the monitoring mode and the roomActivity returns large movement, I haven't seen anything else as it just got installed. IS there a document to tell you what values are supposed to be able to be set, which ones we are supposed to get back as returns? And should these 2 devices report differently like they are.
To the question of did the pairing timeout, yes on all instances for both devices. During the pairing process it would say it found a device but if I did not keep it alive it would not install at the end and I would have to repeat the process. And the times it did install correctly it did the exact same thing but if I kept it alive for some amount of time and then held down again and made sure it was alive until the timer ran out then it would install properly. Attached is the logs of install for the FP1 if you wanted to see it
I also attached a device view. I would think that the FP1E would give more data as its a newer device but maybe I am wrong or I still need to install it more than 2 times, maybe it didn't install the second time, I can not be sure
The Aqara FP1E is a different device with different configuration parameters and attributes compared to the old Aqara FP1. Thats why the 'Çurrent States' look differently.
Not all of the FP1E configuration parameters are currently implemented in the custom driver, and I can't say when I will have the time to do it.
An alternative way to bring FP1E to Hubitat is via the HE's built-in Generic Matter Bridge, with the sensor paired directly to an Aqara hub.
I appreciate your work on this, these things work so much better than trying to come up with silly rules with multiple motion sensors to automate lights. I work in commercial AV systems as a programmer and I fully get the wheres the time to do this situation. I would love to start developing some hubitat apps and drivers but there is so much new stuff to deal with at work all the time that I never have time myself. As in I still haven't had the chance to get maker-api to work so that my Crestron system can interface with Hubitat yet
I am having a hard time getting the FP1E to work in HE.
I tried using the built-in HE driver and it does report any motion
I also used the Aquara FP1 Motion Sensor by Kossev and that too does not work what could I be doing wrong?
what model of hubitat hub are you using and what zigbee channel are you connected to?
The C-8 Pro has some issues with zigbee channel 20 (maybe others)
I would recomend using an Aqara M3 hub (G3 I had some issues) to connect the FP1E and network that hub to Hubitat.
you might
They should rejoin on the new channel over 24 hours depending on the devices they are not all built the same.
If you try another channel (I use 15 others use 25) and doesn't work you can just change back to channel 20 and everything should return to normal.
But even though channel 20 was my go to channel for all other hubs with the C-8 Pro I will not be using it.
