Aqara FP400: Three Weeks of Real-World Use with M3 and Home Assistant

Hi everyone

after about three weeks of daily use, I can say that I am extremely satisfied with the Aqara FP400, especially with its presence detection, people counting, and the ability to create precise detection zones.

Initially, I connected the FP400 directly to Home Assistant using Thread/Matter. However, I eventually decided to switch it to Zigbee, mainly because all my Aqara child devices are already connected to my Aqara Hub M3, which is then integrated into Home Assistant.

For my particular setup, this turned out to be the right choice.

What impressed me the most is the ability to configure specific zones directly in Aqara Home and then have those zones available in Home Assistant. This means that the FP400 isn’t simply being used as a presence sensor for the entire room — I can actually determine which specific area of the room is occupied.

The automations I’m currently using

I’ve created a few fairly simple automations, but they have turned out to be extremely useful in everyday life.

The first one is dedicated to the sofa area.

During the night, when my two-month-old son wakes up for a feeding, my wife sits down on the sofa in the living room and the FP400 immediately detects her presence in the dedicated sofa zone.

Home Assistant then automatically turns on the floor lamp:

  • warm white, around 2710 K
  • brightness set to 25%
  • automatically turns off after 2 minutes of absence

This means there is no need to manually turn on a light in the middle of the night and, more importantly, the main living-room lighting doesn’t suddenly turn on at full brightness.

I’ve also created a second automation for my daughter’s play area.

When my daughter enters her dedicated play area, the FP400 detects her presence and Home Assistant automatically turns on the LED strip installed inside her toy cabinet.

The light is then automatically switched off after she leaves the zone.

These are small automations, but they are exactly the kind of automations that make a real difference in everyday life.

AI and people counting

One of the features I particularly appreciate is the combination of the FP400’s AI capabilities and people counting.

Knowing not only whether someone is present, but also how many people are in the room, opens up the possibility of creating much more detailed and intelligent automations.

Instead of simply having:

«If someone is present → do something»

you can build much more specific logic based on the number of people detected.

For example, an automation can behave differently when there is one person in the room compared with several people. This adds another layer of context to presence detection and makes it possible to create automations that are much more precise and better suited to the actual situation in the room.

Combined with the different detection zones, this makes the FP400 much more than a simple presence sensor.

A winning team with the FP300

I am also already familiar with Aqara’s FP series because I own three FP300 sensors.

Adding the FP400 to the setup has been a great experience. The FP300s were already giving me excellent presence detection, but having the FP400 working alongside them gives me an even more powerful combination.

Three FP300s + the FP400 is, for me, a winning team.

Having multiple presence sensors covering different areas of the home, together with the more advanced capabilities of the FP400, allows Home Assistant to build a much better picture of what is actually happening in the house.

It also makes it possible to create automations based on the presence in specific rooms or zones instead of relying only on simple motion detection.

Presence detection

Another feature that has really impressed me is the way the FP400 can detect and count people in the room.

Compared with a conventional PIR motion sensor, the difference in everyday use is significant. A person doesn’t need to keep moving in order to continue being detected as present.

For my particular use case, where someone can remain seated on the sofa for quite a long time, this is extremely important.

The ability to work with specific zones makes it even more useful. I can have presence in the sofa zone control one light, while presence in the play area controls a completely different light.

Placement is critical

In my opinion, this is one of the most important things to consider when installing the FP400.

The sensor can be extremely accurate, but proper placement and correct room boundary configuration are essential.

I spent some time getting the detection area and individual zones properly configured before creating my automations. Once the room perimeter and zones were set up correctly, the sensor became extremely reliable in everyday use.

I would strongly recommend taking some time to properly position the sensor and define the room boundaries before judging its performance.

Aqara + Zigbee + M3 + Home Assistant

My current setup is:

FP400 → Zigbee → Aqara Hub M3 → Matter → Home Assistant

For me, this setup works particularly well because I can keep all my Aqara devices connected to the Aqara Zigbee ecosystem while using the M3 as a bridge to Home Assistant.

What I particularly appreciate is being able to configure the FP400’s zones in Aqara Home and then use those zones in my Home Assistant automations.

Initially I was using the FP400 directly over Thread/Matter with Home Assistant, but moving it to Zigbee through the M3 turned out to be a better solution for my particular ecosystem and use case.

If you only want to use the FP400 as a general presence sensor, there are obviously several ways to integrate it.

But if your goal is to monitor and automate specific areas within a room, I have found this setup to be particularly effective.

Final thoughts

After around three weeks of daily use, the FP400 has become one of those devices that you notice precisely because you don’t have to interact with it.

The nighttime scenario is probably the best example.

My wife has to get up to feed our baby, sits down on the sofa, and the floor lamp automatically turns on at exactly the brightness and color temperature we configured.

No switch to find in the dark. No need to reach for a phone. And, most importantly, no bright ceiling light suddenly illuminating the entire living room.

As my wife pointed out, this is one of those situations where home automation isn’t just technology for the sake of technology — it’s a small convenience that genuinely makes everyday life easier.

The combination of accurate presence detection, configurable zones, people counting and AI-based features has made the FP400 one of the most useful presence sensors in my setup.

And together with my three FP300 sensors, it has become a really powerful team for presence-based automations throughout the home.

After three weeks, I am extremely happy with the FP400.

Finally, I would like to thank the Aqara Team once again for giving me the opportunity to test this fantastic device.

It has been a pleasure putting the FP400 through its paces in a real home environment and, most importantly, seeing how its features can translate into useful automations that genuinely improve everyday life.

Thank you Aqara for the opportunity!

Here my automation:


and

FP400

13 Likes

@gtxteo What a fantastic real-world breakdown! Your setup perfectly illustrates why zone-based presence detection is such a game-changer compared to simple motion sensing. The nighttime feeding scenario especially resonates — that’s exactly the kind of “invisible” automation that actually improves daily life rather than just adding tech complexity.

Your approach of running FP400 → Zigbee → M3 → Matter → Home Assistant is really smart for mixed ecosystems. It mirrors what we’ve seen with the FP300’s dual-protocol flexibility — Thread/Matter for direct platform integration, but Zigbee for unlocking deeper customization through Aqara Home.[“content_id”:7"]

A couple of thoughts your post sparks:

On the FP300 + FP400 combo — you’re absolutely right that this is a winning team. The FP300s handle solid room-level presence while the FP400 adds that granular zone and people-counting layer. For anyone else considering this, the FP300 in Zigbee mode does offer detection range adjustment and independent sensor toggling through Aqara Home, which can help tune coverage overlap when you’re running multiple sensors.

On placement — your emphasis on this can’t be overstated. With mmWave sensors, a few centimeters or degrees of angle shift can meaningfully change detection patterns. The time spent on boundary configuration pays dividends.

On people counting — this is where the FP400 really diverges from the rest of the FP lineup. The FP2 does multi-person tracking across zones, but the FP400’s AI-driven count adds that explicit numeric dimension for automation logic. Your example of different behaviors for one person vs. several is spot-on.

Curious: have you experimented with any automations that combine the people count with specific zone occupancy? Like, “if sofa zone = occupied AND count = 1 → night light, but if count ≥ 2 → brighter scene”? That seems like the next logical layer of complexity.

Also appreciate the honest note about Thread vs. Zigbee tradeoffs. For readers with similar M3-centered setups, your path is a solid reference.

Thanks for sharing such a detailed, lived-in perspective — posts like this are incredibly valuable for the community. Would love to hear how the automations evolve as your family grows into the system

5 Likes

Great write-up, and congrats on the new baby!!! Trust me, the grandkids will be here before you know it. :wink:

Am I right that you cannot use Thread and have zones??? If so, I don’t understand why. Is it just because not enough info is exposed over Thread? Hopefully I just don’t understand. Still, I love that it’s not WiFi.

5 Likes

Thank you so much. Yes, zones are exposed only with ZigBee. I think that’s a limit of Matter/Thread “software”. Trust me, zone implementation in your own Smart Home is a game changer.

4 Likes

I completely agree! I have the FP2 and will likely order the FP400 today.

5 Likes

Do it. I’m thinking honestly to buy one more FP400 for my studio.

4 Likes

I agree with your assessment of the FP400’s capabilities and how it can be used to create precise automations in Home Assistant. The ability to configure specific zones and use people counting features really opens up the possibilities for creating more intelligent and context-dependent automations.

5 Likes

So, does the FP400 expose the people count to Home Assistant? Because if not, I don’t really see any advantage over my FP2 tbh. Also, because I’d need an Aqara Hub, which I haven’t needed for my FP2s and FP300s so far

1 Like

Honestly, I’m surprised you’re so excited about this sensor. I tried both wall and ceiling mounts, but both were inaccurate. After many hours of testing, the sensor constantly loses track of the person, which is very annoying. I even bought the Aqara hub for this, even though it should work with other Thread routers, but still without success.

I have both of my sensors mounted in a corner. I had major problems with my FP400 that is installed in my kitchen and a relatively small space. The people detected would bounce around irraticly if i for example sit down on the kitchen table and wave my hands. I found this to be caused by an improper installation angle of the corner mount of the device. After moving the device to a better position and fixing the angle and recalibrating the device i’m getting consistent detection. AI Spatial detection is also on.

My second sensor also with a corner mount worked straight out of the box and is very accurate detecting persons in selected zones (couch + rocking chair)

I actually found out how to do this. You need to utilize Signals in the Aqara App and then create an automation and a helper in Home Assistant that keeps a count of the persons in a specific zone. Because the Signals are “blips”, which means that they go to “Detected” but instantly go back to “Clear” after the action has been detected you cant do this with a single entity, you need at least two, and then you need a helper that keeps a count of the persons from 0-10.

Your automations are a dream, thank you for sharing!

1 Like