I just tried it. The edit allowed me to change the value in the preference pane to 5 seconds, but it still says 10 seconds on the main (commands) pane, and it still takes about 15 seconds to turn off.
-Tom
I have the FP300 paired to an Aqara M3 hub. The minimum absence delay time is 10s. I doubt the device supports anything less than 10s.
2 Likes
Rebooted, and nothing changed. 15 seconds off time is still pretty good, though, since the standard for PIR sensors is measured in minutes. And the "stay on" behavior of this sensor is great. I've never had it turn off while I'm still in the room.
-Tom
1 Like
Thanks Krassimir - this is excellent. Finally got my hands on an FP300 and installed in on my landing. Used Aqara app to set to Zigbee, added device on Hubitat (C8 Pro) immediately after - no shenanigans, no double-luck pairing, it just worked. Used the spatial learning, and left everything pretty much default.
FINALLY room lighting works how it should - instantly comes on, stays on when I am on the landing, and pretty much instantly turns off as soon as I leave the area (using unoccupied status as the turn off trigger). My only worry is the battery life, but we will see about that over time!
In my other rooms where I can supply power I have the TS0225_2AAELWXK or HL0SS9OA sensors - they don't work as well as this! I wonder, is there a similar powered alternative to the FP300 I should look to swap them out with?
1 Like
Maybe the Aqara FP1E could be seen as a wired alternative to the battery-powered FP300, but the FP300 was released more than a year later, so I expect it includes improvements not present in the earlier Zigbee models. And, of course, the FP2 remains Aqara's most advanced presence sensor.
I have pushed a new version 2.1.1 for update via HPM, where the temperature attribute rounding bug is fixed. Thanks to @jonathan.lorber and @hubitrep .
3 Likes
Of the sensors avalaible which would you recommend. The FP300 has not been avaliable on amazon for some time now. If the FP2 is a more advanced sensor should that be the way to go?
Aqara FP2 is better in my opinion, but it is more expensive, it is wired, and it is WiFi ( HomeKit protocol over WiFi). You need to enable the HomeKit controller app on your hub, which in the case of non-PRO hub consumes additional memory. All my Zigbee and Z-Wave devices are connected to a C-8 non-Pro hub, but I'm running into memory issues with the hub. That's why I paired my Matter and HomeKit devices to my older C-7 hub and then used hub mesh to connect it to the main C-8 hub.
3 Likes
I have found the Aqara FP2 to be a very good mmWave sensor. As mentioned by @kkossev, it is a WiFi based sensor. The only standards-based protocol that it supports is HomeKit. I have my two FP2 sensors paired with Home Assistant using that platform's "HomeKit Device" integration. I then use the Hubitat Community's "Home Assistant Device Bridge" (HADB) to bring in just the sensor data I want to my Hubitat hub. I had this working before Hubitat released their "HomeKit Controller" integration. It has worked so well that I have not even bothered trying to directly connect the FP2 sensors to my HE C8-Pro hub.
Also, it should be noted that Hubitat has now restricted their "HomeKit Controller" integration to only the C8-Pro and future hub models due to the CPU/Memory constraints as mentioned above by @kkossev.
Setting up and maintaining (e.g. firmware upgrades) the FP2 sensor requires the use of the Aqara app on your phone. This allows the creation of multiple zones, each of which are then presented as distinct motion/occupancy sensors. While the FP2 is pretty quick, it is probably a little bit slower at initial motion detection than a Zigbee PIR motion sensor. YMMV, of course. 
1 Like
How do you do this? Is it restricted to C8-Pro?
Sorry, my mistake. Matter is enabled on my C-7 hub, while the HomeKit Controller is enabled only on my developer C-8 Pro hub.
1 Like
@kkossev and @ogiewon
Okay, so the F2 is a very good sensor, is there a reason i would wait i get the FP300.
The only thing i am coming up with is if i wanted the ability for those extra sensors I guess. Is the FP2 just mm or does it to PIR as well. Then if i a users use case could use the Light, Temp or Humidity, the FP300 is a good option.
I am just trying to figure out the pro/con of each. I certainly have potential use case for the other sensors as well. The room i would put this in would allow it to replace a Ring G2 Motion sensor and a old Aeotech Multi Sensor.
I already have plenty of temperature, humidity, and light sensors, so the extra sensors in the FP300 don’t really add much value for me.
The key difference between the FP300 and the FP2 is that the FP300 is battery-powered, giving you greater flexibility in where to install it in a room. No power outlet limitations, no visible cables — and that greatly improves the WAF!
4 Likes
The FP2 is mmWave only. I have use a Zigbee PIR motion sensor + FP2 mmWave sensor together in a Room Lighting automation for one specific room. This provides near instant light activation (PIR) and no false light deactivations (mmWave) which has vastly improved the WAF for that space.
If I was starting fresh today, I think I'd try a FP300 as it basically combines the best of the PIR and mmWave sensors in a single, small, battery powered package. It can be direct-connected to any generation of Hubitat hub via Zigbee.
If one needs multiple motion zones, the FP2 is hard to beat. It is just a little more difficult to install (needs wired power) and needs to use HomeKit for integration.
4 Likes
I recently experimented with FP1E, FP2, and FP300. My thoughts ... The zones in the FP2 are interesting, but it struggled mightily with reflective surfaces. I had to return them. Thankfully the others handle those surfaces much better. The FP1E and FP300 are pretty similar (I have an earlier post about their comparison), but I "feel" that the FP1E has better coverage (e.g. horizontal angle). That being said, I snatch up all FP300s that I can find: battery-powered and really good performance.
1 Like
Darn it leave some for me 
. I have been looking for them. If one was avaliable i would of already bought on myself.
2 Likes
Happy New year guys..
Need some help. I got myself 1 FP300 a couple of days ago. Setting up wasn't a problem. Used the Aqara app to change to Zigbee and paired to a C-7 hub without any hitch.
Everything was in default. When I move into the landing zone, motion was detected. Room state = occupied. But after a few seconds, while still in the landing zone, motion and room state went to inactive and unoccupied. Even when typing this message, the FP300 cannot detect my movement and presence.
Any clues for me? @kkossev
Edit : did a few more scenario test. when moving into the landing zone about 5-6 meters from sensor, motion detected. Sat on couch about 3m away from sensor, motion and room state both turns inactive and unoccupied after a few seconds. However, if I bring the sensor nearer to me sitting on my couch(about 0.3m), everything worked as it should.
Edit 2 :Things seems to be working. Keeping this post for others who may face the same issue, I didn't know and didn't see a child device added, I changed some preferences and clicked save, after briefly pressing the device button, a child device appeared and all was good from there, for now.
Edit 3 : Not working after an hour... I'm at my wit's end..
Hi Teohwk,
Have you considered increasing the sensitivity? I'm unsure if this parameter applies only to the PIR sensor or to both the PIR and mmWave sensors.
Did you also calibrate the sensor using the 'Spatial Learning' command?
Hi kkossev,
Yeah I did all you mentioned above. But it wasn't working then. I then left the room for a while. I came back and it is working now, without doing anything. I am also confused but let's see how long it will continue to work.
Thanks for responding to my call for help.
1 Like
I've had mine in my office to test for a few weeks. It will work fine for a day then just seemingly go to sleep. Hubitat still shows it as online with a fairly recent 'last activity' time but no motion is detected. The only way I can fix it is to press the button on the unit.
Mine seems more stable after running the spatial learning
1 Like
