Struggling with FP2 initial lag

Aqara Products
,
1

Hello,

I’m having issues with my FP2 being very delayed on initial sensing. I’ve tried 3 different rooms, resetting the FP2 multiple times, and I have 3 hubs in the house. Currently, it’s attached to the wall that my router node is on the other side of, and about 6 feet from an M3 hub.

No matter where I’ve placed this sensor in the house, there is a massive delay on when it first senses. My son had me take it out of his bathroom because it was always taking forever to turn on the lights.

Is my unit defective? I’ve even tried looking up YouTube video’s with similar issues but none have the kind of delay that mine has. It can sometimes take 5-7 seconds to finally recognize and trigger an automation. I have tried turning off the AI features.

1 Like
2

@timmay2t Hi there! Thanks for sharing the details of your setup and the troubleshooting steps you’ve already taken. Let’s dive in and see if we can improve that initial detection lag with your FP2.

A few factors can impact sensing speed, and the FP2’s initial delay may stem from installation environment, device settings, or network communication:

  1. Network and Server Communication Delay: Some delay is normal due to device-server communication, but 5-7 seconds is definitely on the higher side. Ensure your device’s firmware is up to date for the best compatibility and performance.
  2. Installation Height and Position: The sensor should be mounted at 1.4-1.8 meters high in a regular home setting. For larger spaces or offices, a higher installation is okay, but the sensor should be angled slightly downward. Also, make sure it’s not directly facing metal obstacles or sources of interference like mirrors, glass, air conditioners, or fans, as these can slow down detection or cause false triggers.
  3. Sensitivity Settings: Try increasing the detection sensitivity, especially if the sensor is in a static area like a bathroom or bedroom. Higher sensitivity can help the FP2 respond faster, though too high may cause false alarms.
  4. Edge and Interference Configuration: Make sure the “edge” zones are properly set up and that interfering sources (like the router, thick walls, or moving curtains) are marked as “interference” in the app. This helps the FP2 focus on the right areas for presence detection.
  5. AI Space Learning: Use the “AI learning function” when the room is empty to help the FP2 better understand the environment. This can sometimes improve detection speed and accuracy.

If you’ve already tried all of the above and still experience significant lag, it might be worth trying the following:

  • Move the FP2 to a location with minimal Wi-Fi interference, away from metal objects or thick walls.
  • Temporarily test the sensor in a different room with minimal furniture and electronics to see if response time improves.
  • Double-check that your hub’s firmware is also up to date and supports Wi-Fi local automation (version 3.5.0 or above is required for best performance).

If none of these steps help and the delay persists in all locations, it might indicate a hardware issue. In that case, I’d recommend reaching out to Aqara’s customer support for further diagnostics or a possible replacement.

Let us know how it goes or if you discover any improvements after tweaking these settings! The community is here to help, and your feedback could help others facing similar issues.

1 Like
3

If anybody else runs into this, in my case the doorway was causing massive interference, I had to extend the entrance/exit well into the room and then it would properly pick up.

The nature of the sensor has a bit of wifi delay but once it’s detecting it’s great.

1 Like
4

@timmay2t That’s a really helpful insight—thank you for sharing your experience! Extending the entrance/exit zone into the room is a clever way to address interference issues at the doorway. The FP2 uses millimeter-wave technology and relies heavily on accurate configuration of entrance/exit, edge, and interference source areas for optimal detection. Properly marking these zones can significantly accelerate target recognition and minimize delays, just as you observed.

And yes, a slight Wi-Fi delay is normal due to device-server communication, but once the sensor locks onto presence, it maintains responsiveness quite well. Your feedback will definitely help others in the community who might be troubleshooting similar lag issues.

Thanks again for sharing—keep the tips coming! If you find other tweaks or setups that improve performance, we’d love to hear about them.