Presence Multi-sensor FP300 Tips: Boost Detection Accuracy šŸŽÆ

Millimeter-wave radar is what makes the Aqara FP300 a standout presence sensor – it detects even subtle movements like breathing, keeping your smart home automations on point. But nailing the setup and understanding its quirks is key. If you’re dealing with ā€œghost detections,ā€ missed presence alerts, or the sensor refusing to switch to ā€œabsenceā€, we’ve got you covered. These targeted fixes will help your FP300 perform like a pro!

Let’s dive into the most common issues and how to solve them – step by step, no tech jargon required! :blush:

1. Issue: ā€œSomeone is present, but the sensor says ā€˜no oneā€™ā€ / Can’t detect static people

If the FP300 fails to recognize you when you’re sitting still (e.g., working at a desk or resting) or incorrectly reports an empty room, try these fixes:

  • Let the device learn its environment :brain:: New devices or sensors moved to a new spot need ~10 minutes of ā€œquiet timeā€ (no one in the area) to finish spatial learning. Want to speed it up? Go to Zigbee mode’s ā€œOn-site configurationā€ and run ā€œAI Spatial Background Learning.ā€
  • Optimize installation position :pushpin:: Ensure the sensor has a clear line of sight – no obstacles in front. Aim it directly at the main activity area (e.g., sofa, bed, desk) for the best coverage.
  • Adjust the absence delay timer :hourglass_flowing_sand:: Lengthen the ā€œAbsence Delay Timerā€ (cool-down period) in settings. This gives the sensor more time to confirm the room is empty before switching to ā€œno one.ā€
  • Match sensitivity to your scene :gear:: Higher sensitivity = better at detecting static people. Choose based on how long you stay in the area:
    • Low: Bathrooms, hallways (stay <20 mins)
    • Medium: Studies, living rooms (daily use)
    • High: Bedrooms (stay >8 hours, e.g., sleeping)

2. Issue: ā€œNo one is here, but the sensor still says ā€˜someoneā€™ā€ (False alerts)

False ā€œsomeone presentā€ alerts are usually caused by interference or misconfigured settings – here’s how to fix them:

  • If it’s ā€œInfrared Motion Detectedā€ false alerts :fire:: PIR sensors are sensitive to temperature changes. Use the ā€œPresence/No Presenceā€ status (not ā€œInfrared Motion Detectedā€) as your automation trigger – it’s far more reliable.
  • If it’s radar false alerts (dual presence mode) :satellite::
    1. Customize detection range: In Zigbee mode’s ā€œOn-side Configuration,ā€ set a specific detection distance to exclude non-target areas (e.g., avoid triggering from a curtain or a fan).
    2. Lower sensitivity: Less sensitivity = stronger anti-interference. Follow the same scene-based guide above (low for short stays, high for long stays).

3. Issue: ā€œI left the room, but the sensor won’t switch to ā€˜no oneā€™ā€

Stuck on ā€œsomeone presentā€ even after you’ve left? Try these troubleshooting steps:

  • Update firmware first :rocket:: Outdated firmware can cause glitches. Make sure your FP300 is running the latest version – check in the Aqara app.
  • Refine detection range :dart:: Use Zigbee mode’s ā€œOn-side Configurationā€ to narrow the detection distance. This prevents the sensor from picking up movement outside your target area.
  • Re-run spatial learning :arrows_counterclockwise:: Go to ā€œOn-side Configurationā€ and execute "AI Spatial Background Learning again. Ensure the room is empty during this process so the sensor re-learns the ā€œemptyā€ environment.
  • Adjust sensitivity :gear:: Refer to the scene-based sensitivity guide above – lowering it can reduce interference from non-human movement.
  • Be patient with interference sources :window:: Moving curtains, swaying ceiling lights, or air flow can mimic subtle human movement. Give the sensor a few minutes to adapt – it will learn to distinguish interference over time.

Pro Tip for All Issues: Test After Adjustments! :white_check_mark:

After tweaking settings or repositioning the sensor, do a quick test: Walk in, sit still, then leave the room. Check if the sensor switches between ā€œsomeoneā€ and ā€œno oneā€ correctly. Small adjustments (like minor angle changes or sensitivity tweaks) can make a big difference!

With these fixes, your Aqara FP300 will deliver the precise, reliable detection it’s known for. If you still have questions, drop a comment below - the community are always here to help! :raised_hands:

#AqaraFP300 #DetectionTips #SmartHomeHacks #TroubleshootingGuide

16 Likes

FP300 and Thread is still not working so this post is kind of pointless.

2 Likes

Sensor is still completely useless in Thread mode on Home Assistant, Homekit, and Aqara app. Just always gets stuck on presence.

1 Like

Could small animals affect it, such as mosquitoes? Because when it was running in a clean environment, it worked fine in Zigbee mode with Z2M. But when it was installed in a room where mosquitoes may be present, this issue started to appear.