As of 5 minutes ago, it was back on the US site (before it was "currently unavailable, not sure when it will be back). Hoping you see this in time to check the amazon ca site.
You're good luck 
Checked again after this post, for fun, and they were actually in stock so I grabbed 4.
They are from Amazon.com so hopefully I don't have to return them if I get the 35-100% daily variable tariff. 
1 Like
I have been checking every morning, lunch, and evening for a few months. It finally showed available so I grabbed some. Glad you got the message in time
PS - I heard that SCOTUS just shot this down.........
1 Like
Added four more FP300s today using this driver. (Previous four joined via Aqara/Matter to HE.) As others already note, the driver works great.
At some point, momentarily forgetting about the Temp/Humidity child, I attempted Swap Device to replace a Virtual Motion Sensor with a new FP300 ... and HE allowed it. (I didn't think Swap Device supported devices with children.) It swapped the devices, but kept the child device on its original parent device ID, so the FP300 Temp/Humidity device was now a child of the Virtual Motion Sensor. After noticing, I swapped them back and then manually replaced them in the apps.
No big deal. Just a fun observation to share.
I have an interesting use case.
-- Presence Detection Mode = both
-- roomState is unoccupied
-- pirDetection is active
-- yet motion is inactive ... even with the pirDetection=active, so not a classic OR of the two
For some reason, the pirDetection rarely leaves active. It blips to inactive and right back to active. The mmWave detection is accurate though with respect to actual motion/presence in the room. I've enabled the AI spatial detection and interference detection to no avail.
Mine finally arrives on Thursday! But, of course, I have surgery scheduled for Wednesday, so I won't be able to install it for about three weeks... GRRRRR!!!!!!
It is interesting that you bring this observation up today. 
I recently received my second FP300 sensor and decided to try pairing it directly to one of my Hubitat hubs via Zigbee. My original FP300 is paired directly to an Aqara M3 hub via Zigbee, and then to Home Assistant via the M3’s Matter Bridge functionality, and finally to Hubitat via HADB.
So, during some testing today I believe I may have found the same issue you mentioned above, but I am not 100% certain. From my quick testing, it appears that the pirDetection sensor is not being used by the driver to trigger the standard “motion” attribute. Only the roomState (mmWave) sensor seems to be controlling the Hubitat standard “motion” attribute. Again, this is my hypothesis, as I do not know if the FP300 is sending three unique events (PIR motion, mmWave Occupancy, and combined “Motion”) OR just two unique events (PIR Motion and mmWave Occupancy.) If the latter, then the driver would have to perform the proper logic to combine PIR and mmWave to properly report Hubitat’s “motion” capability.
@kkossev - any thoughts on the above?
2 Likes
Hi Dan,
You are correct. In the latest version of this driver (2.1.1, released on 2025/12/30), the pirDetection sensor is not used to trigger the standard “motion” attribute. As a result, the 'motion active' event is delayed by nearly one second.... 
I will review the code as soon as I have time this week and will update the driver.
4 Likes
Tonight I attempted to migrate an FP300 from an Aqara M3 bridged device to a direct HE device. I removed the accessory from the Aqara hub and made 10+ attempts to join the "freed" FP300 to HE. Each time, HE detected the Zigbee device but did not finish initialization. I tried Double Luck Voodoo, rebooting the hub, etc ... no luck. Anyone else have this issue, transitioning a full join to an Aqara hub to a reset join to HE?
Have you tried taking out the batteries for a few minutes and then putting them back in ?
Ah, I forgot that. I'll try that tonight. Thanks!
Just got mine in and have them temporarily mounted until I can verify they work as expected.
Also, 3D printing some corner mounts I found on Makerworld so that I can better aim them (even though they appear to be working fine as they are so far)
So, from the previous posts, I see that the PIR isn't really being used to determine motion. What about occupancy?
My automations are simple for right now. I just want them in places where lights are not being turned off. So, trigger is light(s) turn(s) on OR room state reports occupied (the second is to force a retrigger in case I get false "unnocupied" during the wait for expression - but I am thinking I am going to remove this as it is built into the wait for expression)
The actions are: Wait for expression - roomstate = unoccupied -Duration 20, then lights off.
Should I be using motion inactive instead of occupancy?
Also, anyone using these in a room with a ceiling fan? Any issues/tricks with that? (I have one in a room with a fan that will be getting used shortly)
These are back in stock on amazon i just ordered 4 - this guy has a discount code on his youtube channel
3 Likes
Wish I had seen this code earlier. Oh well.
BTW - the amazon ones apparently do not come with the metal disc. That appears to only be available in the Aqara physical stores and not in the US. Does anyone use fender washers?
The combination of hub reboot, battery removal, and avoiding repeaters worked. Thanks.
2 Likes
What is a reasonable expecation of range for this little sensor.
I was hoping it would replace a ringe Gen 2 motion sensor. Mainly to use the MMwave sensor part to help prevent inactivity when Motion is lower but presense is still occuring. I was also hoping to use the Temp/Humidity sensors to let me remove a Aeotec Multi Sensor. Mainly the Humidity is used to control a dumb humidifier.
It seems to work fairly well, but the range isn't the greatest from my experience. It is proabbly fine for a smallish room, but for a room that is over 20" in some directions it may struggle from a corner. It is currently placed right above the ring sensor and while the Ring sensor seems to detect well over 20ft away and activates while we are on the way into the room with the FP300 we have to take a few steps into the room for it to trigger and activate lights. This shouldn't be to much of a suprise as it looks like the settings max at 6 meeters.
I think i may try to reposition the sensor from the corner to the center of the wall in the room which should take care of the range issue. I just need to find a good removeable option to position it. Magnet sounds like the way to go. since it's base supports it. Is a metal washer all that is really needed as suggested by @tray_e above
Manufacturer states 6 m or ~20 feet. So your experience seems to match that.
I gave up on whether fender washers would work or not and just printed some stands and corner mounts.
If you have access to a 3D Printer, there are a few models on makerworld that might suit your needs. (If you don't, many libraries have 3 D Printers and will print for you at the cost of their materials - Most filament is ~$20 USD / kg - My prints were all less than 20 g). Some of the models require magnets, some do not. I printed these two:
https://makerworld.com/en/models/1997012-aqara-fp300-magnetic-corner-mount#profileId-2149776 (Magnets required - this one is a corner mount. He has a link to his flat one on the same page)
https://makerworld.com/en/models/1995961-aqara-fp300-corner-mount-no-magnet-needed?from=search#profileId-2148526 (No Magnets - printed in separate pieces - had to reduce the size of the main pieces by as they made the clearance too tight)
https://makerworld.com/en/search/models?keyword=FP300 (others available)
1 Like
Finally able to order a couple of sensors. Good to see a variety of mounts to choose from. Thanks for pointing them out. Its the (mm)Wave of the Future 
1 Like
Have you noticed any significant performance differences when paired directly to Hubitat vs Aqara M3 hub? I have one paired directly to Hubitat, and it is working 'ok'. Was planning to pair another to the Aqara hub to see if there are any significant performance differences. Thanks
So, I had my FP300 paired to an M3 Hub, then to Home Assistant via Matter, and then to Hubitat via HADB. I initially paired my second FP300 to the M3 Hub and then to my test/dev HE hub via Matter. Not sure if that made much of a difference or not performance wise. I currently have one FP300 directly paired to my Production HE hub via Zigbee, and my second FP300 directly paired to my Dev/Test HE hub via Zigbee. I have been messing around with some driver tweaks to try and optimize performance and battery life. Thus far, I am getting close to the performance of my old Lowe’s Iris v2 Zigbee PIR motion sensor in the same room. The old Iris v2 sensor is still about 200ms quicker to respond. So not exactly the data you asked for, but it’s all I have at this time.
1 Like
