Aqara FP 300 First Review (Pics&Vid)

Hello everyone,

I received my FP300 and unpacked and started using it the same day.

First of all, the size: the device is really small compared to the FP2. The feel is excellent, typical of Aqara, and the package includes the device and the user manual, as well as a small metal plate with mounting hardware. The Matter Code is printed on both the user manual and the device itself.


My requirements for integrating the device:

  • Aqara M3 Hub
  • HomePod Mini
  • Google Nest
  • IKEA Dirigera

The device is in Thread mode by default and can be integrated into the known ecosystems via Matter.

However, if you integrate the device via Matter, you miss out on some really great and useful features, which I’ll discuss later.
Since I was aware of this and personally prefer Zigbee, it was clear from the start that I would switch protocols and go directly to Zigbee.

I had no problems switching protocols


.
![Screenshot_20250916_114606_Aqara Home|239x500]

After programming, a suitable spot in the hallway had to be found, which, as with the FP2, was a bit of a challenge. I strongly recommend testing the device over several days and at different times before finally installing it.

Advantages of Zigbee Mode:

  • Light intensity sensor
  • Temperature sensor
  • Humidity sensor
  • 3 different detection modes available

The detection modes are:

  • mmWave+PIR (recommended)
  • mmWave only
  • PIR only

The light intensity, temperature, and humidity sensors can be configured or disabled! This is, of course, a really great feature, as you can extend the battery life by disabling, for example, temperature and humidity!

I noticed a few translation errors here. The word “Schließen” should be “Aus.”
I haven’t figured out exactly what the term “adjust (german Anpassen” means yet. Perhaps Aqara can give us a clue.

The range can also be adjusted in Zigbee mode:

However, I should mention at this point that the range doesn’t seem to reach that of an FP2. Furthermore, I’ve found that the height at which the sensor is mounted influences the range. The sensor responds best to head and/or upper body height.

The sensitivity of the presence detection is also adjustable:

You can also adjust the switch-off delay from 10 seconds to 5 minutes. This will later affect any automations that are supposed to turn off the lights, for example. This is where you set the delay.

My hallway has a lot of corners and edges, which can be distracting. Unfortunately, the first attempt shown in the following picture didn’t produce the desired results because the walls and the sensor’s range interfered.

To test the sensor, I created corresponding automations in the Aqara app and was able to directly test the new Automations 2.0 function with its conditions.

First, I created three scenes:

  • Hallway On Day
  • Hallway On Night
  • Hallway Off

Then, three automations:

Hallway on Day (occupancy, 7:01 AM - 10:29 PM, below 100 lux)
Hallway at Night (occupancy, 10:30 PM - 7:00 PM)
Hallway Off (no occupancy)

When creating the automations, I noticed the following errors:

Maybe @AqaraOfficial can fix this with an Software update.

There’s a small quirk with the sensor’s lux value if you want to use it in your automations within the Aqara app.

The lux levels aren’t selectable down to the exact lux level, as you might be used to from other systems, but rather in the following increments:

1-10 lux (individually)
10-100 lux (increments of 10)
200-1000 (increments of 100)
2000-10000 (increments of 1000)
20000-80000 (increments of 10000)

About HomeKit:

All sensors such as presence, brightness, temperature, and humidity are exported here and can be used for automation:

Google Home:

No sensor is displayed for me. I’d probably have to switch to Thread mode for that. However, since that’s not currently an option for me, it will take a while.

Conclusion: The FP300 is ideal for medium to small rooms if you don’t want or can’t use a cable for the FP2. For larger and longer rooms, I would personally switch to the FP2.

Furthermore, the FP300 doesn’t support zones like the FP2! This is logical, however, as this would simply consume too much power and would require a different wireless protocol, as the data exchange would be much larger and more intensive. That’s why the FP2 uses Wi-Fi and not Zigbee or Thread!

If Aqara markets the new FP300 in the right price segment, it will be a game changer for many households!

I’d like a maximum price of €45! With a discount, it would be €35.

To conclude my short review, a short video of the current test scenario. Please note that the sensor status will be updated later. Therefore, in the video, I briefly exit the sensor view and then return to it. I hope you enjoyed it and were able to draw some conclusions. If anything changes, I’ll update this post accordingly. Thanks

11 Likes

What a great sharing! Thank you for letting everyone see the real FP300!

3 Likes

This in English will be “Custom”
Not quite sure how to say it in German. Maybe you could give me some suggestions!

4 Likes

Thank you :v: Just testing :face_with_hand_over_mouth::wink:

I ment that i do not know what this feature does. The Translation is ok :wink:

custom means you could set the specific report frequency and so on

1 Like

Hi @MakerMing for custom the right translation is benutzerdefiniert
But when it will be too long I would use custom there too . I´m sure 99% of the Germans will unterstand that as well

4 Likes

Thank you for this sharing. I now understand why I don’t get any configuration informations: I will not have with Thread / Matter integration.

I have to setup the device in the Aqara app to do so. I wonder if it is possible to add it into the Aqara App without Hub ?
If someone has the answer.

My sharing is there with different requirement: HA with Thread USB key (Sonoff z-dongle), OTBR and matter integration.

You can integrate the sensor into your desired ecosystem via the Thread wireless protocol using Matter.

However, if you don’t have an Aqara hub that supports Thread or Matter, you’ll need to connect the sensor DIRECTLY to, for example, a HomePod Mini.

Then you’ll only have the sensor in HomeKit and probably won’t be able to configure any of the things I mentioned above.

To configure the settings, you’ll need at least a Thread-enabled Aqara hub.

That’s my current understanding. If there’s anything wrong here, please correct me!

1 Like

Have you tested it with pet ? Or have you seen option for pet ? (detect it, don’t detect it, etc…)

Unfortunately, since I don’t have any pets, I can’t test this. However, you can adjust the sensitivity as described above, and AI learning is also included. Since the sensor works best for me at chest/head height (probably because the area to be detected is larger), it’s quite possible that animals near the ground might not be detected.