https://forum.aqara.com/tag/FP400

I love the new sensor of our favorite brand. The packaging is as always great and everything in place. My only complain is the lack of a power supply. The set up was easy as always and connection was made with Zigbee with the M3. I was struck by the fact that the cameras did not appear when selecting an hub. Since I always use my products in HomeKit mode, I can only share my impressions based on that—aside from the fact that the “ghost phenomenon” reappeared during setup. So, the response is much faster and clearer compared to the FP2 I’ve been using for a long time—and even the recent FP300. There aren’t any other significant differences regarding HomeKit, though that’s not Aqara’s fault but Apple’s; I hope Apple gives us more automation options in the future, because we’re really missing out on a lot!

@ikariapower Great to hear your hands-on impressions! It’s awesome that the FP400 is delivering noticeably snappier response times compared to both the FP2 and FP300—sounds like the mmWave tuning has come a long way.

A couple of thoughts on your points:

  • Power supply: Totally get the frustration. The FP300 went with dual CR2450s for its compact form factor (42 × 42 × 50 mm), so if the FP400 follows a similar design philosophy, a built-in PSU would definitely bulk things up. Trade-offs, right?

  • Zigbee + M3 setup: Solid choice. The M3’s hub clustering and edge automation capabilities should keep things running smooth and local even with multiple hubs in play.

  • Cameras not showing during hub selection: That’s an odd one—usually camera hubs or G-series devices should populate. Might be worth flagging with support if it persists.

  • HomeKit limitations: Preaching to the choir here. Apple’s automation framework is… let’s say conservative. The FP2’s zone positioning and multi-person detection are basically locked behind Aqara’s native app because HomeKit can’t handle that granularity yet. Here’s hoping WWDC delivers something.

The “ghost phenomenon” during setup—classic mmWave quirk. Usually settles once environmental calibration finishes.

Keep the impressions coming, especially if you dive deeper into zone configs or multi-target tracking