Aqara new people presence sensor FP2

Im finding it terrible to use lights that blink when you ask it to turn them on if motion is detected, Think they should of called this device The Blinking Aqara Sensor that needs truly hanging up for good! :slight_smile: I’ve only ever tested a day and turned them off ready for them blinking! They seem more trouble than what they are and as for like these videos I see I have no chance of them set up doing that they cant even find my seat position let alone turn lights on in different areas my rooms is very small you can’t swing a cat in it not that I want too but you get the point :muscle: :rofl:

If motion, or more correctly for this device, presence has been detected when someone enters a detection zone, then it’s working okay. It’s what you do with that detection afterwards that can affect how a light responds. I tend to include a “for” time of 1minute when absence, or no presence is detected. That way, lights don’t immediately go off if there’s a brief period of absence.

Yes mine was set to 1 minute which is why I think it might be blinking on and off due to not having enough time to sense Im still there. But making this device useless as I cannot have a light keep goign off an d then back on again a normal motion sensor does not do this though Id still prefer if I know how to change it to be on longer then a 1 min

The same light works fine with sensors to turn on and off by sunset but not with a time period.

Do you know how I change it on the the yaml file to keep on longer so i can test it again tonight as again hard to test in the day when its light.

1 minute should be long enough. The issue may be the set up in the Aqara app. These sensors are very sensitive to being setup correctly. You really need to just mount it some where, turn it on and watch what happens as people move in, out and around the area. If you see ghost presence then look for something that might be causing interference or turn down the sensitivity. The other thing to check is how quickly absence is detected. If that’s happening too quickly then perhaps the sensitivity is too low or the sensor is not mounted in the optimal position. I have mine in the corner of the room to optimise the 120 degree detection angle. I know it sounds like a real pain to do all this watching and tweaking, but it will be worth it in the end. Once you are happy with the detection and absence, then you can start putting in edges and interference zones. First thing I do is stand in the corners of the area and mark them. Then walk around and mark the edges. Do that a couple of times to check how accurately it’s detecting, then you can start putting in furniture and detection zones. This is our living room. My son is sitting on the floor in front of the sofa watching tv.

If you want to tweak the wait time in the automation, adjust the “for” in your “no presence” trigger,or whatever you’ve called it. That can be done in the automation UI editor.


Any way of knowing how many people in the room with this device on HA ?

Nope. That information is not exposed via HomeKit.

I don’t want to alarm anyone, but the latest iOS Aqara app update appears to have finally fixed my FP2s.

Actual map tracking without being forced.
No network connection errors, time outs, bullshit.
Region edits save. Period. The first time!
Ghosts delete no problem

F!cking finally :smiley:

Did someone test firmware version 1.2.0 ?
Is it safe ?

I’ve been running it since it came out. For me it’s no worse than any of the other firmware versions. Not particularly better for me, but no worse. I guess it depends on your definition of “safe.” If you’re not having any issues, I wouldn’t upgrade the firmware.

Well, after the 1.1.7 debacle, I’m not keen to blindly try a new version.
My definition of “safe” is “at least as good as 1.1.9”

My only issue with 1.1.9 is some occasional difficulty to cope with more than one person in the room and a crash now and then where the FP2 loose the wifi connection definitely so a power cycle is necessary.

All of my FP2s are running 1.2.0 with no issues at all.

So, I updated to 1.2.0 and…back to ghost land…
1.1.9 was almost perfect and now 1.2.0 is a disaster again, close to 1.1.7
Ghosts everywhere, including outside of the perimeter, no live update in the iOS app anymore, and so on.

So far it seems that every even version are to be skipped and the odd ones are more or less OK.

Same here regarding the return of the ghosts in 1.2.0. In my case, the ghosts are always in an interference zone. It’s really bad, I’d say at least 50% of the time I leave the room there will be a ghost in a random interference zone.

So I just deleted all interference zones to see if that improves things.

Since I removed my FP2 since it stopped working. I added it again to the Aqara app then to HomeKit and it showed up. I then deleted it from the HomeKit, and it never shows up in Home Assistant. Any ideas on how to get HA to see it?

Same here. Most of my ghosts seem to be in interference zones.

I just keep resetting to absence in the hope that it’ll improve things.

1 Like

After removing it from Apple Homekit, it needs to be power cycled while HA is looking for it with its Homekit integration. It seems its ability to be discovered is a windows right after power cycle. At least that matches many observations incl mine.


I setup my fp2 in aqara app on Android. How do I get it to show up in HA? It’s not coming up under home kit at all.

Edit. Unplugging and plugging it back in fixed it. How to work out why these zone names are not coming through

Zones names are not populated from the App, you will have to name them manually In HA.

1 Like

Should I have enter exit zones in my main areas ? The boxes would take you too much room tho. Not sure how others are doing this.

I’m an Android user. Registering an FP2 on both the Aqara app (for setup) and HA HomeKit integration used to work fine, but version 4.0.5 of the Android app wouldn’t bind a new device to the app. Aqara fixed that with 4.0.6, but prevented the device showing up under HA HomeKit. I’ve informed Aqara. If you want something that works, use 4.0.3 and install it as an .apk. I’m not sure I’ve posted this in the right place, so let me know if it fits better elsewhere in the forum.