Aqara FP400 Presence Sensor: mmWave Radar Detection

The Aqara FP400 Presence Sensor is a major step forward in smart home sensing. It uses mmWave radar with AI to track many people at once, detect their posture, and spot falls. Unlike basic infrared sensors that miss still people, the FP400 keeps detecting presence even when no one moves.

Aqara rates it to separate standing, sitting and lying poses, to follow up to 10 people at once, and to publish a live headcount. That opens the door to routines built on how a room is actually used rather than on whether something moved in the last minute. This is not a unit I own. What I do run is a set of ceiling-mounted mmWave motion sensors plus a 24G presence sensor, all Zigbee, all joined straight to Home Assistant, and that setup is the yardstick I hold the FP400 against.

Product Overview and First Impressions

Overview

The Aqara FP400 goes far beyond basic motion sensing as a next-generation presence sensor. It tracks multi-person presence, noting each person's position and posture (standing, sitting, or lying). The 60 GHz mmWave radar covers rooms up to 10 meters wide. It can track up to 10 people at the same time.

Two of the listed capabilities are the interesting ones. A live headcount gives climate routines something better than a binary occupied flag, and dwell time per zone lets you separate a room someone walks through from a room someone sits in. Aqara also lists a fall-detection mode for horizontal mounting. This review doesn't cover it and you shouldn't buy the sensor for it, because a safety function is exactly the kind of claim nobody should repeat without evidence.

The sensor slots into an existing setup without adding cameras, which is the whole reason radar presence sensing took off. The compact 120mm x 80mm x 40mm body sits flush on a wall. It runs on permanent AC power, so there are no batteries to maintain and no battery to go flat in the middle of a winter evening.

Technical Specifications and Performance

The FP400 is built for steady, round-the-clock use in homes and light business spaces. The core sensor uses 60 GHz mmWave radar for non-intrusive presence tracking. Onboard AI handles the processing. This local setup keeps response time under one second. Data stays on the device, not in the cloud, which helps protect privacy.

Detection Capabilities:

• Coverage area: 10m x 10m maximum, divisible into 20-30 customizable detection zones
• Simultaneous tracking: Up to 10 individual occupants with distinct positioning
• Posture recognition: Standing, sitting, lying orientations with transition detection
• Analytics: Real-time headcount, dwell time per zone, walking distance metrics

Hardware Specifications:

• Radar module: 60 GHz mmWave sensor with AI processing chip
• Power supply: AC adapter providing 5V DC, continuous operation without battery dependency
• Physical dimensions: 120 mm x 80 mm x 40 mm, weight 150 grams
• Construction: Durable ABS plastic housing with integrated wall-mount bracket
• Operating temperature: Rated for 0C to 40C ambient conditions

Connectivity and Standards: The device supports Thread and Zigbee 3.0, with Matter certification for cross-platform use. It carries FCC and CE marks alongside its Matter certification. Aqara doesn't publish an average power figure, so plan for a device that draws its few watts around the clock rather than one you can forget about on a battery.

Works With

The FP400 shines in its ability to connect across many smart home platforms. It supports Zigbee 3.0, Thread, and Matter at the same time. This lets it link to Aqara gateways, SmartThings hubs, Home Assistant, Apple HomeKit (via Thread), Google Home (via Matter), and Amazon Alexa devices.

Pairing runs through the Aqara Home app, and SmartThings or Home Assistant can then consume the device. Matter matters here because it lets a presence signal cross into routines you build on someone else's controller instead of locking the data into one app. Once the zones exist, they can drive Philips Hue lighting, thermostats, or smart locks, depending on what your controller already speaks.

The Aqara Home app lets you draw custom zones on a room floor plan and set sensitivity per zone, from fine movement down to basic motion only. Voice controllers such as Alexa or Google Assistant can report status, though voice commands need exact phrases wired into your routines first.

The route I'd actually take is Zigbee. Every presence and motion sensor in my house joins a Home Assistant Connect ZBT-1 coordinator directly, with no manufacturer cloud in the path and no vendor app holding the zone configuration hostage. There's a durability argument for that too: my Aqara and other Zigbee devices have survived two coordinator swaps without being re-paired one by one, while the WiFi devices I once ran through a vendor app didn't survive a single migration. If you run Home Assistant on a Raspberry Pi, Zigbee mode plus your own automations gives you presence logic that outlives whatever happens to the app store listing, and puts that data to work for energy saving, security, and daily routines.

Practical Use Cases and Real-World Applications

Where does a sensor like this earn its price over a plain motion sensor? These are the scenarios the zone and posture data actually unlock:

Security zoning: Zone alerts let you watch specific areas rather than a whole room. A hallway zone can separate a short trip to the bathroom from someone moving the length of the corridor, which is the pattern that generates most PIR false alarms.

Occupancy-based energy management: Lights, climate and media shut off when a zone has been empty for a set time. The gain over PIR isn't the shutdown, it's the absence of the opposite failure: radar keeps reporting a still person, so the lights don't drop out on someone reading in a chair. That single behaviour is why I put mmWave sensors on the ceilings instead of the cheaper alternative.

Adaptive routines: Posture data lets a rule react to sitting versus standing. Overhead light dims when someone settles into the living room; a desk light stays at full while someone stands at the desk.

Room analytics without a camera: Dwell time per zone tells you how a space is used across a week. Radar gets you that number without putting a lens in the room, which is the trade-off that makes it acceptable in places a camera never would be.

Multi-person routines: Tracking up to 10 people at once means a routine can key off a headcount rather than a single occupied flag, so a kitchen with four people in it can behave differently from a kitchen with one.

Setup Process and Configuration Guidance

Aqara puts setup at roughly 10-15 minutes from box to working automation. Here's the order the steps come in, and where the time actually goes:

Physical Installation: Mount the sensor on a wall at 1.2-1.5 meters, facing the area you want covered. The bracket takes screws or adhesive. Use the screws. A radar sensor's whole value depends on it pointing where you decided it points, and adhesive on a painted wall is a slow way to lose that. Keep a clear line to the floor and avoid mounting above furniture that shadows part of the room.

Power Connection: Plug the included AC adapter into a standard outlet. The device needs constant power and has no battery backup. Plan your placement near an outlet. Run the cable through the bracket to hide it for a clean look.

Network Pairing: Get the Aqara Home app (iOS or Android) and create an account. Add the FP400 over Zigbee or Thread depending on your hub, then scan the QR code on the device. Worth deciding this consciously rather than accepting the default: the protocol you join on determines who owns the zone data later.

Zone Customization: The app lets you draw zones on a floor plan with touch gestures. Split the room into areas that match how it's used, such as seating, walkways and desks. Start with fewer zones than you think you need and add them when a rule misfires.

Automation Configuration: Set up presence-based actions through the Aqara app or your smart home hub. For example: "When someone is in the kitchen, turn on the lights at full." Or: "When no one is in the living room for 10 minutes, switch to eco mode."

Calibration and Testing: Walk each zone and watch the live presence display in the app. Try standing, sitting and lying down to see where the boundaries really are. Adjust sensitivity if pets or moving curtains trip a zone.

Troubleshooting Notes: Keep a clear line between the sensor and the floor, since furniture in the path creates blind spots. Metal surfaces within 50cm affect radar. Firmware updates arrive through the app and are worth applying, because radar tuning is exactly the sort of thing vendors improve after launch. The printed guide is brief; the detailed documentation lives online.

Honest Assessment and Practical Limitations

Let me be exact about what this section is. I don't own an FP400, so there's no six-week log to quote. What follows is the set of limits I'd expect from the technology, drawn from running ceiling mmWave sensors and a 24G presence sensor on my own Zigbee network, plus the constraints Aqara states outright.

Pets and radar: mmWave sensors respond to a moving mass, and a large dog is a moving mass. Sensitivity tuning helps and rarely solves it completely. Anyone with animals should budget for a few rounds of adjustment rather than expecting pet immunity out of the box.

Power placement: The AC requirement decides where the sensor can go. Rooms without an outlet near the ideal spot need an extension or new wiring, and that's a real constraint in a finished house. The mounting bracket takes adhesive at 150 grams, but a sensor whose aim defines its coverage deserves screws.

Zone accuracy: Zone borders depend on room shape and furniture. Open plans with few landmarks make precise boundaries hard to draw in the app, and awkward rooms take several passes. Add setup time for anything that isn't a rectangle.

Privacy and data path: Radar avoids the camera problem, but presence, posture and movement data still travels to whatever hub and cloud you join it to. There's no local-only mode that cuts cloud access while keeping hub automations alive, and that's the reason my own sensors go straight to a local coordinator instead. Read Aqara's privacy policy before deciding this doesn't matter to you.

Matter limitations: Certification does not mean feature parity. Zone-level data and posture detection live in the Aqara Home app, while Matter exposes a much simpler present or not-present state. For the detailed data you're paying for, plan on a Zigbee or Thread link to a hub that speaks it properly.

Best fit: The FP400 suits homes that have outgrown basic motion sensing and want multi-person tracking, posture awareness or zone-level detail, and that are comfortable running the Aqara app alongside their main controller.

When to look elsewhere: If you need battery power, this isn't it. If pets rule your floor plan, a plain PIR may frustrate you less despite missing still people. If you want everything local, weigh a sensor that reports fully into your own hub without a vendor account in the middle.

The device carries a 4.7-star average from over 1,200 buyers, which tells you the feature set lands for people who need it. It's a strong pick if your requirements match, and an expensive one if a simple occupancy flag would have done.