The one that paired with a C8P, that i have in my living room, is preforming incredably well.
A follow up.
Looks like the Aqara FP300 is back in stock at Amazon in the USA.
https://www.amazon.com/gp/product/B0FG2MD3YP
Update: Sold out again.
Just snagged one (I was too slow when they were first released and quickly sold out), thanks!
I´ve been trying to get one of this FP300 for WEEKS, with no luck.
Bought one from Ali Express but then I realized it was NOT a FP300, but a RTCGQ13LM that they sell when you search for a FP300.
My error not to verify before.
Anyone know a place where I can get one? or when they are going to be available again?
I keep checking Amazon. Especially around the 9pm time frame. I will catch them in stock and order them in a few minutes they are out again. I got 4 more coming. Sometimes it is limited to like two on the order.
I just got my FP300 too. So excited to test it out!
However, it seems like the "Motion" state continues to report active when no-one is around for more than a minute. The PIR detection looks more accurate.
Currently, detection sensor type is "Both mmWave+PIR". How can I reduce the clear time of the "Motion" state?
Edit: Found out the "forever" active motion state was due to a nearby fan... goes to show that its mmWave sensor is working perfectly...
Edit2: Changing detection sensor type seems to be unresponsive. Took a long while to change to PIR only, and now stuck and unable to change to other selections.
Make sure you press the sensor button before changing the configuration settings.
okk. will try it out. thank you!
Just received a FP300 today. Surprised how small it is. I plan on installing it tomorrow, it will replace a Zooz ZSE11 which sometimes turns the toilet light off before we're done doing our business (and no amount of flailing arms and hands 
seems to get it to detect motion once that happens).
This is my first Aqara device. Are firmware updates usually available on HE for these things? I'd rather not have to buy an Aqara hub if it isn't necessary, but I don't see any "update firmware" button in the driver. Given that this is a fairly new device, I'd expect that there would be FW updates now and then.
It appears that once the device is paired to HE, it no longer is detected in the Aqara app. I suppose pairing turns off Bluetooth.
It's also my first mmWave device. I'll probably buy some more if this one proves itself to be worthy.
No
You don’t. Folks have figured out that using the Aqara app on your phone, you can change from Zigbee back to Matter, and then back to Zigbee. Doing so installs the latest firmware. You then can re-pair the device with Hubitat and it’ll pop back into its original slot.
Note: I have no firsthand experience with the above procedure. I have an Aqara M3 hub that my FP300 is paired with, so firmware updates are straightforward. 
Did you already have the hub prior to the FP300? Any benefit to using it vs pairing directly to HE?
I'm not crazy about the idea of introducing another hub or Zigbee network into my setup, but if there's a benefit I'm not aware of, I'd consider it.
I'll probably get a few more of these FP300's as they become available, but I don't see any other Aqara devices in my immediate future.
Hi,
May I check if you used both PIR+mmWave detection in your device setting?
For your automation, is “motion” the trigger?
I wonder if the Rule Machine triggers can be further split into PIR and mmWave separately. I have several false positives every hour (happening as I am typing this).
You can find these tips useful : (posted by Aqara Support team here ) . I have copied/pasted the oriiginal text with some addtions related to Hubitat and the driver specifics :
I. Troubleshooting for Device Stuck in Presence State (HE: 'motion active')
Check for Dynamic Environmental Interferences
Please verify if the following conditions exist in the detection area: whether devices such as air conditioners, fans, or range hoods are turned on after a person enters the area, and whether items like curtains or chandeliers experience shaking or movement. Such dynamic interferences may cause the sensor to get stuck in the presence state.
Principle Explanation
The sensor’s dual PIR (Passive Infrared) and MMW (Millimeter Wave) mode will automatically learn and save the interference-free environmental scenario by default. If a person enters the area and triggers a new scenario or introduces additional interference sources, the sensor will struggle to switch back to the absence state quickly. The characteristics of interferences such as slight chandelier shaking or curtain swaying are similar to weak human movements (e.g., breathing), and the device requires more time to identify and eliminate such interferences. We recommend waiting patiently for the state to recover.
Scenario Testing and Problem Verification
If the sensor gets stuck in the presence state (HE: 'motion active'), you can execute AI Space Background Learning (HE: 'Start Spatial Learning' command) in the Real-time Debugging section of the device '(HE: device Commands tab)' for it to re-learn the current environment. After completion, observe if the sensor can switch back to the absence state (HE: 'motion inactive') quickly in subsequent use: if yes, it can be determined that the issue is caused by new interference sources generated by relevant devices turned on after a person enters the area.
HE: Start Spartial Learning button on the Commands tab:
Configuration Optimization Suggestions
Adjust the sensor to the low-sensitivity mode, and set the appropriate detection distance and angle to avoid interference sources as much as possible, which helps the device determine the absence state quickly. If the issue persists after the adjustment, try switching to the MMW-only mode for use.
HE: Preferences tab, click on the Save button after changing the settings!
II. Troubleshooting for MMW Radar Failure to Detect Human Presence
Based on your device usage, this issue is most likely caused by the following two reasons, with corresponding verification methods and solutions attached:
- Insufficient Power Supply Impairing Radar Performance Two of your devices were previously left with only about 10% battery power. If the device battery is critically low (e.g., near 0%), insufficient power supply capability will directly degrade the detection performance of the millimeter wave radar, or even prevent it from detecting human presence. If the battery is confirmed to be nearly exhausted, replace it with a new one and try again.
- Abnormal Trigger Caused by MMW Radar Learning an Incorrect Environment If a person remains in the detection area for an extended period, the device may mistakenly identify human characteristics as environmental interference sources and complete the learning process, which in turn affects the subsequent normal detection and triggering of human presence.
- Verification Method: Ask all people to leave the detection area for about 5 to 6 minutes to allow the device to re-learn and restore the normal interference-free environment. Then have a person re-enter the area and observe if the radar can detect and trigger the presence state normally.
- Solution: If the issue is verified to be caused by this reason, appropriately increase the sensor’s sensitivity.
Note: We confirm that the log reporting function operates correctly. When the millimeter wave radar detects human presence, the device will also register the PIR as detecting presence continuously.
Thank you for sharing. The false positives occurred in a setting where there shouldnt be any physical movements and heat changes when room is unoccupied. Potentially could be due to light from outside window hitting and reflecting off some surfaces in the room. This is very tricky…
However, my device setting is set at using both PIR and mmwave. In the absence of heat changes, I am confused as to why the device reports activity.
Yes, I already had it. I would not recommend buying it just for using the FP300 sensors since @kkossev has already developed a working HE Zigbee driver for it.
So I just unboxed and it looks like this FP300 is looking for Matter, not Zigbee!!
I also found that using the Aqara app is the only way to change to Zigbee. But that seems to need an Aqara hub or connecting to a third party Matter hub. I have not done anything with Matter on my Hubitat, don't have an Aqara hub, and I'm not sure where to go from here.
So am I stuck?
No hub needed. Just the Aqara App on your favourite mobile device. 
Sorry, but I need more help, please. How does the Aqara app talk to the FP300 sensor? When I try to add it, I'm told to make sure I have an Aqara hub on the same LAN as the mobile phone. I can also get to a place where it asks if the device has been added to a third-party Matter ecosystem, which I don't have. Can I enable Matter in my Hubitat and get it to talk directly to the FP300?
I just followed the directions in this Video Tutorial (starts at 1:15).
Maybe something has changed? 
@Ranchitat Thanks for the help! The bad news is that something changed and it's not so easy now, but the good news is, with a bit of digging, I finally found I could manually add it and then it used Bluetooth to my Andoid phone to update the firmware, after which it gave me the option to stay with Matter or switch to Zigbee. So now I'm in business!
ChatGPT incorrectly insisted I required a Matter Edge Router for the FP300 to talk to the Hubitat or phone.