Aqara has released five mmWave presence sensors that come up for Home Assistant, and they do not share a connection type. Two are Zigbee and USB-powered, one is Wi-Fi and reaches Home Assistant through HomeKit Controller, and two are battery units that ship in Thread/Matter mode and need a one-time app step before Zigbee2MQTT can see them. Which one you hold decides your integration path, so that is how this page is organised.
Everything here is research synthesis. It draws on the Zigbee2MQTT device pages, the Home Assistant integration docs, retailer spec listings and our own published device guides. No sensor was bench-tested for this page, and where a claim rests only on one of our own guides, the text says so.
This page covers the FP1, FP1E, FP2, FP300 and FP310. Pricing is left out on purpose, since it moves too fast and varies by region. Vendor range figures are also treated as the least useful axis, because the integration path and power source constrain a purchase far more.
The short answer: five sensors, three integration paths
The useful split is not “old versus new”. It is how the sensor reaches Home Assistant and what it asks of you before it works locally.
| Sensor | Link to Home Assistant | Power | Detection area | Aqara app needed for |
|---|---|---|---|---|
| FP1 | Zigbee via Zigbee2MQTT | USB (per our guide) | Regions, Z2M only | Nothing. Avoid Zigbee channels 21-24 |
| FP1E | Zigbee via Zigbee2MQTT | USB (per our guide) | Single area | Nothing |
| FP2 | 2.4 GHz Wi-Fi, via HomeKit Controller | USB-C, constant power | Up to 30 zones, up to 5 people | Wi-Fi setup, zone layout and later zone edits, firmware |
| FP300 | Ships Thread/Matter, Zigbee after an app switch | Battery | Radar plus PIR | One-time mode switch |
| FP310 | Ships Thread/Matter, Zigbee after an app switch | Battery | Radar, no PIR | One-time mode switch |
Per our device guides, all five run locally once paired. The FP1 and FP1E never need the Aqara app. The FP300 and FP310 need it once, for the mode switch. The FP2 is the one with ongoing app contact: our FP2 guide says zone layout needs an Aqara account login, later zone edits need internet access restored, and firmware updates go through the app. Those are statements from our own guides, not something we tested.
Which one do you have?
Start with how it is powered and how it connects, because those two facts separate the lineup cleanly.
- A unit on USB-C with no Zigbee pairing at all is the FP2. It is the only Wi-Fi unit.
- A USB-powered unit that pairs to a Zigbee coordinator is an FP1 or an FP1E.
- A battery unit is an FP300 or an FP310.
We are deliberately not describing physical differences between these, because we have no verified source for appearance. Check the model label on the unit, or the device page in the Aqara app. For the FP1 versus FP1E split, the Zigbee2MQTT device description is a second check, since the FP1 page is titled “Presence sensor FP1” and the FP1E page “Presence sensor”. If the naming scheme itself confuses you, our guide to Aqara model codes covers how they map to marketing names.
The USB Zigbee pair: FP1 and FP1E
Both pair straight to a Zigbee coordinator with no Aqara hub. On both Zigbee2MQTT pages, pairing is a press-and-hold of the reset button for about five seconds until the blue light blinks.
The FP1 is the older, richer one. Its Z2M device page exposes presence, approach distance, motion sensitivity, a monitoring mode and the region controls (configured_regions, region_upsert, region_delete). Our FP1 guide describes up to 10 named regions mapped onto a 7×4 grid, requiring Z2M 1.30.0 or later, and says region features exist only in Zigbee2MQTT, not ZHA. Zigbee2MQTT’s own docs flag regions as experimental, per that guide. Our guide also calls the first-generation unit discontinued and secondhand-only. The Z2M device page states neither the version requirement nor the discontinued status, so treat both as our guide’s claims and check current availability yourself.
The FP1 comes with two practical catches. The Z2M page says it does not work on Zigbee channels 21 to 24, which matters if you moved your network to dodge Wi-Fi interference. Our guide to changing the Zigbee channel covers choosing one. The page also says a unit can get stuck and need a 12-second press after power is connected, and lists adapter firmware requirements for CC2530/CC2531, CC1352/CC2652, CC2538 and ConBee II.
The FP1E is the plainer one. Its Z2M device page exposes presence, movement, target distance, detection range and spatial learning, plus the AI interference-source and adaptive-sensitivity settings. It has no region exposes, which matches our FP1E guide describing a single detection area with no zones and no multi-person tracking. That guide gives roughly 6 m at 120 degrees, about a 30-second hold-off before reporting clear, and says it acts as a Zigbee router. Those last two details come only from our guide, not the Z2M page. If router behaviour matters to your mesh, see our router versus end-device planning guide.
Full setup for each lives in the FP1 Zigbee2MQTT guide and the FP1E Zigbee2MQTT guide.
The Wi-Fi unit: FP2
The FP2 is the odd one out, and the one most often described wrongly. It is not a Zigbee device, so there is no Zigbee2MQTT page for it at all. Retailer spec listings and Samsung’s SmartThings product page agree on 2.4 GHz Wi-Fi (802.11 b/g/n) plus Bluetooth 4.2, and none we found lists Thread or Zigbee. Aqara’s own product page, as retrieved for this article, confirms USB-C and constant power but does not state the radio, so the band comes from those listings rather than an Aqara spec sheet.
Do not plan an FP2 around a Thread border router or a Zigbee coordinator. It joins your Wi-Fi network and reaches Home Assistant over the HomeKit protocol. HomeKit Controller supports Thread accessories in general, which is probably where the mix-up comes from, but that is a property of the integration, not of this sensor.
In Home Assistant the path is the HomeKit Controller integration. HA’s docs say the HomeKit protocol is local and offline and does not require an Apple online account. They add that some Wi-Fi accessories need an Apple device just to join the network the first time. That does not bite here: per our FP2 local setup guide, the FP2 gets onto Wi-Fi through the Aqara Home app, which works on Android as well as iOS, so no Apple hardware is needed. That guide walks through the setup order.
The same guide is clear about where Aqara stays in the loop. Zones are drawn in the Aqara Home app with an account login and then stored on the device, so daily operation is local. Changing the zone layout later means giving the sensor internet access again, and firmware updates run through the app. If you plan to block the FP2’s internet access on an IoT VLAN, finish the zone layout first.
What you get for that is the most capable sensing in the lineup. Aqara’s page describes rooms up to 40 m2, up to 30 zones across 320 cells, up to 5 people tracked at once (best at 3 or fewer), a built-in light sensor exposed to third-party ecosystems, fall detection when ceiling-mounted, and an IPX5 rating. It also states that local automations work without internet.
The FP2 has a documented firmware regression. We cover it in the FP2 1.3.6 interference-zone bug, and it is the main reason to read current release notes before updating.
The battery pair: FP300 and FP310
These two are the confusing ones, because of how they ship. Per our comparison and device guides, both ship in Thread/Matter mode, and Zigbee2MQTT only sees them after you pick Zigbee mode in the Aqara Home app during setup. The FP300’s Z2M page confirms the switch direction matters. A unit previously set to Thread/Matter needs a full factory reset (reset button pressed 10 times) to move to Zigbee, and the standard 5-second reset only restores network settings. Our Thread-to-Zigbee switch explainer covers the mechanism so it does not need repeating here.
Choose Zigbee mode in the Aqara Home app before you try to pair with Zigbee2MQTT. Going back after a Thread/Matter setup takes the 10-press factory reset, not the usual 5-second one.
On the sensing side, per our three-way comparison, both use a 120-degree, 6 m coverage figure. The FP300 adds a PIR layer to a 60 GHz radar and runs on 2x CR2450, with roughly three years in Zigbee mode and two in Thread mode per that article. The FP310 uses 24 GHz radar and has no PIR, which fits its Z2M device page, where there is no pir_detection expose. After the switch, Zigbee2MQTT lists the FP300 as model PS-S04D and the FP310 under its own FP310 page. The FP300’s Z2M page doesn’t name the cell type, so the CR2450 detail is ours.
The FP310 page adds two practical details. Battery status can take up to 24 hours to be reported, and changed settings only refresh after pressing the on-device button to wake it. Also, our comparison noted that FP310 availability outside China-oriented listings was uncertain when it was written. We did not re-check that.
The full setups are in the FP300 Zigbee2MQTT guide and the FP310 Zigbee2MQTT guide, and the three-way deep dive is our FP2 vs FP300 vs FP310 comparison.
Firmware and updates
The Zigbee2MQTT device pages for the FP1, FP1E, FP300 and FP310 each state that the device supports OTA updates. The FP2 has no Z2M page, and per our FP2 guide its firmware updates go through the Aqara Home app.
Our earlier three-way comparison said Zigbee2MQTT does not support OTA for the FP300 and treated that as a buying differentiator. The current Z2M PS-S04D page says otherwise. An independent Home Assistant write-up updated in May 2026 still described FP300 updates as app-only, so the device-page listing appears to be recent. Whether Zigbee2MQTT actually offers your unit an FP300 image depends on Aqara publishing one, which we did not verify. Check the live device page and the OTA tab rather than relying on older advice, ours included.
That changes the FP300-versus-FP310 decision. If you were choosing between them mainly on OTA, the difference may not exist.
Known friction
Two GitHub reports are worth knowing about, and neither should be read as a settled verdict.
One concerns the FP310 under native Zigbee2MQTT support. The reporter describes presence freezing until intervention, suspects the manufacturer-specific detection_range attribute (0x019a) of getting stuck when read or written, and says mesh metrics looked normal. Issue #32189 was opened on 2026-06-03 and is closed now, but we could not see how it was closed or when. Closed is not proof of a fix, so check the current issue before relying on that behaviour in an automation.
The other is a 2024 report of an FP1 failing the interview with a ConBee III coordinator (“can not get active endpoints”). Issue #23526 was closed as not planned and marked stale, with no later activity. It is one adapter and one user, so it is historical colour at most. Still, if you are on a ConBee III, search for newer reports before buying a secondhand FP1.
Which to buy or keep
These are our synthesis from the sources above, not test results.
| If you want | Look at | Why |
|---|---|---|
| Zones or several people tracked | FP2 | Only unit with up to 30 zones and 5 people. Wi-Fi, and zone edits need the app and internet |
| Zones on Zigbee | FP1 | Regions in Z2M, with the channel limit and secondhand availability |
| Whole-room presence, minimal setup | FP1E | Single area, USB, no app at any point |
| Battery placement, PIR layer | FP300 | Radar plus PIR, needs the app mode switch |
| Battery placement, radar only | FP310 | No PIR, same mode switch, availability uncertain |
I think most people running Zigbee2MQTT should start with the FP1E if a USB outlet is available, since it asks for nothing beyond pairing. The battery pair earns its place where there is no outlet, and then the app step is the price. The FP2 is the pick when zones or multi-person tracking are the point, as long as you accept a Wi-Fi device and the occasional trip back to the Aqara app.
Common questions
Which Aqara presence sensor is best for Home Assistant?
It depends on your path. For Zigbee2MQTT with no app step, the FP1E. For zones and multiple people, the FP2 via HomeKit Controller. For battery placement, the FP300 or FP310 after the Zigbee switch.
Is the Aqara FP2 Zigbee or Wi-Fi?
Wi-Fi. Retailer listings and Samsung’s SmartThings product page give 2.4 GHz Wi-Fi with Bluetooth 4.2, and none lists Zigbee or Thread. It reaches Home Assistant through HomeKit Controller.
What is the difference between the Aqara FP1 and FP1E?
The FP1 exposes region controls in Zigbee2MQTT. The FP1E has a single detection area and adds spatial learning and AI sensitivity settings.
Do I need an Aqara hub for an Aqara presence sensor?
No. Our FP1E guide says a hub is never needed for that sensor, and the Z2M device pages cover pairing the Zigbee models directly to a coordinator. The FP2 joins your Wi-Fi directly. The FP300 and FP310 need the Aqara app for the mode switch, not a hub.
Which Aqara presence sensor works with Zigbee2MQTT?
The FP1, FP1E, FP300 and FP310 have Z2M device pages. The FP2 does not, because it is not a Zigbee device.
What this page verified
Verified against the Zigbee2MQTT device pages and Home Assistant’s HomeKit Controller docs on 2026-10-08: the expose lists, OTA listings, FP1 channel limit and the FP300 mode-switch reset behaviour. Checked again on 2026-10-10: the FP2’s 2.4 GHz Wi-Fi radio across several retailer listings and Samsung’s SmartThings page, and the FP310’s 24 GHz radar in a third-party listing.
Carried from our own guides, not independently confirmed, are the FP1’s region limits and discontinued status, the FP1E’s router role and 30-second hold-off, the CR2450 battery type and runtime figures, the FP300’s 60 GHz radar, and the FP2’s cloud-gated zone editing.
What still depends on Aqara: the one-time mode switch on the FP300 and FP310, and on the FP2, zone layout, later zone changes and firmware updates. Everything else in the table runs on your own coordinator or your own LAN.
Still unconfirmed are the FP2’s radio from an Aqara-published spec, whether FP300 and FP310 units actually receive OTA images through Zigbee2MQTT in practice, and how the FP310 issue #32189 was closed. After pairing any of these, check the live device page for your sensor and your Zigbee2MQTT version, since expose lists change. For the FP300, the OTA tab on a real unit is the test that settles the update question, and until someone runs it, trust the device page over any older comparison, ours included.