FP300 delay in bathroom,normal or misconfigured?

Hey all,

I just purchased and added an Aqara FP300 in a small bathroom and I’m noticing a consistent ~1-3 second delay before it detects presence. Detection works fine, it’s only the initial trigger that feels slow.

For comparison, in my kitchen I have an Aqara FP1E, and it feels noticeably faster in detecting movement/presence.

Bathroom Setup

Sensor mounted on the wall, facing the bathroom area at 1.8m high.

Small space, typical bathroom (tiles, mirror, etc.)

What I’ve already tried:

Ran the AI spatial learning feature

Reduced the detection range to match the small size of the bathroom

Even when I’m right at the entrance of the bathroom and clearly within its field of view, it still has a delay or does not detect me until I go closer to the sensor.

Trying to understand if I’ve misconfigured something or if this is simply how the FP300 behaves. Any help is welcome!

3 Likes

I’m not sure I can help much but I can confirm I have the same experience as you with the FP300.

I set the FP300 a few inches away from the FP1E essentially covering the exact same space and the FP1E beats the FP300 100% of the time and it’s more accurate.

The FP300 has unique uses and quirks associated with it and you kind of have to play around with it in different locations.

If you have a tiny bit of OCD you may not like the FP300 (I don’t)

1 Like

I have the same experience, but with an FP300 in the kitchen. Firmware v. 5841. Sensitivity is set to low.

I thought it was because the update fixed the false positives of the PIR (for example when I’m cooking or the oven is on) and as a side effect, it needs more time. But I have a 1-5s lag no matter if anyone’s cooking or not.

1 Like

It’s actually quite surprising, because the distance from where I installed it in my bathroom to the door is less than 3 meters. I also don’t think battery operation is a factor here, since my Philips PIR sensor triggers almost instantly. In my case it’s not about OCD, it’s just that the bathroom has no window, so those 2–3 seconds actually matter.

That’s interesting.

I also compared it directly with an FP1E in another room, and the difference in initial trigger speed is quite noticeable.

Have you noticed if changing sensitivity or placement makes any real difference, or is the delay always there regardless?

Do you think this is something that could improve with future firmware updates, or does it feel like a hardware limitation of the FP300?

I’m trying to decide whether it’s worth keeping it or returning it.

I actually don’t mind the delay in the kitchen as I have a T1M in the hallway acting as a “pilot light”. I think it’s better than when I left the oven on and it detected presence for 2 hours. So I didn’t tinker with the settings.

I put one on the ceiling in my living room, as my wife doesn’t understand that she can turn the lights off via a switch. I am working on the best location and angle at this time. I currently have it set via honey to turn on two lights. One via motion and another via presence. The motion is always first and a second or two is presence. Would be nice if they went hand in hand.

Hi there, as this issue has already been resolved with our support team via email, we’ll be closing this topic on the forum as well. If you have any further questions or run into any other issues, please feel free to reply directly to our support email. Thanks for your support and understanding!