My Review: Aqara Spatial Multi-Sensor FP400

As the successor to the popular FP2, the new Aqara FP400 promises exciting advancements in mmWave presence detection. Here are the initial test results and practical impressions.

Design & Scope of Delivery

  • Appearance: Visually, the FP400 looks largely identical to its predecessor, the FP2—with one small detail difference: while the FP2 only had “Aqara” printed on the front, the FP400 features both “Aqara” and the model designation “FP400” on the front panel.
  • Scope of Delivery: In addition to the sensor itself, the package includes an adhesive pad, a magnetic metal plate, wall plugs, screws, and a USB-C to USB-C cable (the predecessor came with a USB-C to USB-A cable).




Initial Setup & Configuration

  • Default Connection: Out of the box, the sensor is set to Thread by default.
  • Setup Process: Initial setup should be done via the official Aqara App, as all fundamental configurations must be performed there. The FP400 is the first Aqara product that does not require an Aqara border router for setup (see YouTube Video https://youtu.be/6cvEowFILCQ?si=hTj4MWbkrhsBK5fj )
  • Since I own the M3 Hub, I unfortunately wasn’t able to test this aspect, even though an Apple HomePod mini is also present in my setup. I also cannot rule out that I might have done something wrong here.
  • Matter Integration: Because the printed Matter code is already used when integrating it into the Aqara system, a new pairing code must be generated within the Aqara App to pass the sensor over to the Apple ecosystem or the Ecosystem of your choice. Integration using this generated code works immediately afterward.
  • Zone Transfer: Zones created in the Aqara App are transferred to the target ecosystem, but the assigned names are not carried over.
  • Light Sensor: Just like with the FP2, the illuminance (light) sensor is exposed to Apple Home.

New Features & Improvements

  • Live Detection: A new addition is live detection during direct room walk-throughs and mapping.
  • Detection Cycle: The detection cycle can now be flexibly adjusted from 10 seconds up to 5 minutes.
  • Mounting Height: The exact mounting height must/can now be specified during setup (minimum height: 150 cm).
  • Monitoring & Zones: Monitoring and zone settings are structured similarly to the FP2, but according to PR information, they are supposed to work with higher fidelity and precision.
  • Personal Impression: More accurate and significantly less ghosting.

As you can see here, I was able to set up and test the two devices right next to each other.


Protocols & Protocol Switching

  • Zigbee / Thread: Switching between Zigbee and Thread is done via Bluetooth as usual. I personally prefer Zigbee, hence the final switch to Zigbee mode.
  • Limitations in Zigbee Mode: In pure Zigbee mode, no new settings or extended options could be observed up to this point.

Reset Instructions

  • Resetting: If a reset of the sensor becomes necessary, this is done by pressing the button 10 times consecutively.

Conclusion

The FP400 is a worthy successor to the FP2. Personally, it feels substantially more accurate than the FP2 and exhibits noticeably less ghosting. Initially, I had both positioned side-by-side to maintain as identical a setup as possible.

However, as with all radar sensors: position is everything! Test your position over several days and states before final installation.

Things that no radar sensor likes, based on my personal experience:

  • Opposing mirrors (bathrooms, hallways)
  • Smart blinds when opening or closing
  • Large tiled surfaces
  • Large window areas

Try to avoid positioning the sensor facing such surfaces. I achieved the best results at head/chest height. I also achieved good results mounted above a door, angled slightly downward. Furthermore, I strongly recommend marking entry and exit points in the Aqara App; this helps immensely in defining absence more quickly.

Would I recommend replacing an FP2 with an FP400? It depends on the use case: if you have a room where the FP2 doesn’t perform as expected and you have already changed the device’s position multiple times (don’t forget to let it relearn), it is definitely worth giving the FP400 a try. For anyone who doesn’t own a presence sensor yet and doesn’t mind a cable, the FP400 comes with a very clear purchase recommendation.

In comparison to FP2, the following differences arise:

FP 2: WIFI - FP400 Zigbee or Thread
FP 2: 60GHz mmWave - FP400: 60GHz mmWave (up to 5 times more accurate)
FP 2: up to 5 targets - FP 400: up to 10 targets
FP 2: 8x6m Distance - FP 400: 10x8m Distance
(according to Aqara Infos)

Amazon DE: FP 400 Amazon DE

Attached are a few more screenshots of the setup, setup process, and integrations.

Aqara:















Live detection during setup










Apple Home:

Homeassistant:


MyLatestAqara
Spatial-Multi-Sensor-FP400
FP400
@AqaraOfficial @Caroline_Zzz

27 Likes

Nice! I was going to put off the upgrade to the FP400, but if it’s that better than FP2 then I’m going to upgrade it.

What about people sitting on a sofa? Or under a blanket? My FP2 sometimes things there’s no one in the room in those case

7 Likes

My bad ignore the message as I just see that it is already on sale.nice review

5 Likes

No Problems with blankets or Sofa. I had the same issue with my FP 2 for the bedroom. I changed three times the location and finally fixed the issue with blankets.
Location is everythig

5 Likes

Nice review!

4 Likes

Thank U :slightly_smiling_face:

3 Likes

That’s great to hear actually, I’ll definitely upgrade

2 Likes

Hey, did you get a chance to test it while sleeping? Does it detect your presence the whole time, or does it lose track of you at some point?

1 Like

I haven’t had a chance to do that yet, as that feature doesn’t interest me. However, I can say that the FP 400 hasn’t fallen out while I’m sitting at my home office desk or lying down/sleeping on the couch (taking a nap). Then again, I don’t take eight-hour naps.:face_with_hand_over_mouth::wink:

2 Likes

Any experience on how it operates over thread?

1 Like

From the user manual:

“The device also supports direct addition to third-party Matter platforms by scanning the Matter code on the device itself without going through configuration in the Aqara Home app. However, in this way, it can only be used as one general presence sensor and one light sensor. It is recommended that users configure the device through the Aqara Home app before synchronizing it to third-party platforms to use the device’s full functionality.”

Is there a technical reason that the “pure” thread protocol without an Aqara hub is so severely limited? Or is the text just saying that the Aqara app is required but not an Aqara hub?

That depends on WICH border router you use. If you use an Aqara M3 Hub and set it up in the Aqara app—configuring zones and so on—you need to generate an additional Matter code within the Aqara app and then provide that to your preferred ecosystem. That way, the zones you configured are available in your system.

If you pair the device directly without using the Aqara app, you won’t get any of those settings; you’ll only get a single zone, including the brightness sensor.