Aqara FP300 is now released for sale on Amazon :
( limited-time discount codes for the US/CA - FP300NA11 or EU/UK - FP300EU11 )
It is now confirmed that the Aqara FP300 pairs and stays connected to Hubitat C-7 and C-8 hubs in Zigbee mode without any issues.
Switching the FP300 from Thread/Matter to Zigbee requires only a one-time firmware update using the Aqara Home mobile app (Android / iOS).
No Aqara Hub is required for the protocol switch or for ongoing Zigbee operation in HE!
Although the Aqara FP300 is not yet available for sale, information about this new battery-powered mmWave sensor is already on GitHub. Here comes an update for the community Aqara device driver:
added Aqara FP300 Presence Sensor support (experimental, not tested); credits: Dan Gibson (@absent42 on GitHub)
ver. 1.9.1 2025-11-12
Bug fix: decoding Aqara RTCGQ11LM (lumi.sensor_motion.aq2) battery voltage
ver. 1.9.2 2025-11-13
FP300 temperature and humidity parsing;
decoding most of the FP300 reports;
added restartDevice() command for FP1E/FP300
ver. 1.9.3 2025-11-14
fixed FP300 illuminance handling and the calculation formula;
enabled motionSensitivity for FP300;
FP300 fingerprint update;
bugfix : no response on ping() command was switching FP300 healthStatus to offline
added battery voltage and percentage events for FP300;
enabled advanced options for FP300 illuminance sensor
version 2.0.0 2025/11/15 11:58 PM (dev. branch) :
BREAKING CHANGE: Added child device support for FP300 temperature & humidity; FP300 T/H readings now appear in a separate child device using Generic Component Temperature Humidity Sensor;
BREAKING CHANGE: removed TemperatureMeasurement and relativeHumidityMeasurement capabilities from the parent driver;
BREAKING CHANGE: added deviceTemperature attribute for non-FP300 devices internal temperature;
added advancedOptions preference toggle;
added separate tempOffset and humidityOffset for FP300;
added experimental trackTargetDistance() command for FP300
MAJOR CHANGE: Intelligent Parameter Change Detection :
implemented for FP300 and illuminance reporting
store parameters in the state.params [n:name, t:type, v:value, l:local]
only sends changed values to prevent Zigbee flooding and potential device instability
'Spatial Learning' starts a process for calibrating the FP1E/FP300 sensitivity, and it appears to be effective! This feature was recently added to the driver.
@kkossev I have an FP2 in my bedroom how does this sensor compare to the FP2?
I am getting frustrated by a Linptech sensor in my office and was considering another FP2 to replace it. Would you recommend the FP300 over the Linptech?
There are high hopes that the Aqara FP300 will be the best battery-powered mmWave sensor released so far. The early feedback from beta testers has been quite promising. However, it’s still unclear how well it will connect — and stay connected — to Hubitat hubs. I just placed my order today, so I’ll find out soon enough!
It should be able to communicate natively via Zigbee to Hubitat.
You don’t need an Aqara hub, but you will need to install and use initially the Aqara Home mobile app to switch the FP300 in Zigbee mode (the device comes with a Thread firmware by default). Once it pairs to HE via Zigbee protocol, the Aqara mobile app should not be needed anymore.
First off, thanks so much for the clear info and the driver details — really helpful!
I’m almost there, but just need a little clarification. I understand we don’t need an Aqara hub, but we do need to use the Aqara Home mobile app to switch the FP300 into Zigbee mode. What I’m a bit fuzzy on is what exactly the FP300 connects to initially — is it via Thread so we can use the app to flip it over to Zigbee? In other words, do we really not need any hub at all to make this initial switch, or am I missing a secret handshake?
Currently, there are only a few mentions in other forums that an Aqara hub is not required for the one-time initial protocol switching, but none of these posts can be fully trusted. Initial communication without a hub is possible via mobile phone Bluetooth, although this is not mentioned in Aqara's documentation. They consistently promote their Zigbee hubs....
This is a legitimate concern; hopefully, we will know the answer soon. Until then, it may be wise to hold off on any purchases while we are still unsure.
Which makes sense, as I believe the Matter specification uses Bluetooth for pretty much all initial commissioning of devices. Matter over WiFi devices are configured via Bluetooth to set the WiFi credentials, for example. Matter over Thread devices use Bluetooth initially to add them to a Matter Thread mesh network. At least that is how I believe it works!
I have ordered one as well. I have an M2 hub so I was pondering if I should go ahead and bind it to my M2 hub via zigbee and see if it will come over via matter bridge like my other Aqara devices or go ahead and use @kkossev driver and connect it directly to HE.
I have the Linptech (I am one of the few that have no issues with them, knock on wood) but going through a remodel so the WAF would greatly increase if I can eliminate the wires in these locations.
since being advertised from yesterday evening!
