I've been taking my time with this and getting the zones right. Last night I decided it was stable enough to start adding FP2 zones into automations. Using HADB, I have brought the zones into HE and they appear as highly responsive motion sensors. Perfect!
Once they are in, I'm using the Home Assistant HomeKit Controller integration's sensor view to know when a zone is activated or not. Probably works the same with the Apple Home app, but I'm not using that, so I cannot comment. This is far better than trying to use the detected person icon on the Aqara FP2 Zone map. It would be great if the app worked perfectly, but it often doesn't show you as present, even though you are detected (which I'm determining by looking at the HomeKit Controller sensor view as previously mentioned). This allows quick and accurate adjustment of the FP2 zones. I simply open the Aqara app and make a Zone adjustment, save it and then flip to Chrome on my iPhone to see exactly when I'm detected in Home Assistant or not as I move in and out of the zones.
It's early, but I suspect that what some people are seeing as ghosts in the Aqara Zone map, are merely in the Aqara app alone. A bug in the app, and not a problem with the actual FP2 1.15 firmware I'm running. I'm finding no actual person detected in that zone when the app shows that a ghost exists in that zone. Again, I may be incorrect here, but the evidence I'm finding of actual detection when viewing the HomeKit Controller sensor status indicates otherwise. However, if you have upgraded to 1.17, this may not be the case. I'm sorry if you're plagued with poor performance due bugs in 1.17, and I empathize with you. As I mentioned in my previous post, circumstances both within, and beyond my control gave me a second chance to avoid the allegedly faulty 1.17 firmware the second time around, and I can now safely wait for the next release and see how it shakes out before making the non-revertable choice to upgrade.
Hope this information is helpful and I'm interested to hear if anyone with FP2 firmware version 1.17 can either corroborate, or confute my findings using the same methodology.
I am running the 1.17 firmware on my FP2 and it is working fine. While the Aqara app on my iPhone is a little wonky, my home automations are working just fine. I am also using HA to HADB to bring my FP2 zones into HE.
I have had some luck in the iOS Aqara app by opening the FP2 sensor page, then clicking the 3 dot menu (top right), wait until it says updated, then going back to the main sensor page. Afterwards, it at least shows something on the screen. Rebooting the FP2 sensor also sometimes helps.
Hopefully Aqara will work through these bugs soon.
Unfortunately I upgraded my two FP2 to latest FW V1.17
My integration is also done via HA HomeKit Controller + HADB.
Unfortunately all ghosts are very real because near all of them generated a correspondent event.
The one in a bathroom does not have any zones defined. Over night when it suppose to be quiet
it did generated many (10+) events. I guess, I have to wait until next firmware release hopping
it will fix things.
Do you have any window coverings or shower curtains that might be moving slightly when your HVAC system turns on? How about any plants? What about handing towels? These sensors are very sensitive to any motion in the room.
Also on latest firmware v1.1.7_0002.0028.
Working well apart from the annoying ghosts...
From a quick glance, I can see that the app and integration in HA show the same thing, i.e. ghosts are reported in both cases.
Just received my wall mount Tuya mmW sensor today. It's every bit as good as the reviews state. I don't see why you would still order an Aqara FP1 with these available. For that matter, I wouldn't personally spend the money on an FP2 for an application that only needs a single zone.
I'm pretty happy with the FP2 features and performance, but for $28 CAD (After discount, I only paid $20 CAD shipped), you would be much better off with four of these in many cases.
Yes, I love the Tuya ZY-M100, they are great!
They are working fine in two bedrooms.
Unfortunately, I failed to get it to work in the living room, hallway, and bathroom as the radar sees through walls!
Will test further.
I have access to Zigbee2MQTT but do not use it... the options are the same as provided by @kkossev excellent drivers.
From my limited testing the main option to get right is the placement of sensor and max_range (I normally use a tape measurer to measure distance). However, the problem is adjacent rooms, for example, sensor placed in the bathroom easily detects the adjacent room as the space is too small in the bathroom.
First odd (more so than what I've already read about here ) behavior from the FP2 this morning. Blue light suddenly started flashing (Forgot to check if it was still active in HA ), as if it was in pairing mode. Unblocked its internet and opened the Aqara app, but it couldn't be found. Tried to pair it again, but nothing found. I power cycled it for 30 sec and it came back online like nothing had changed. Blocked its internet again and it's working in HA just as before.
Is this typical behavior? Does it just suddenly drop off and I'm going to need to reboot every so often? I'm on firmware 1.15 still, so maybe this is a unique experience. Has anyone else experienced the same thing?
I have not observed this behavior, however I am no longer running 1.15. So, possibly something that was fixed in 1.16 or 1.17? I do know that my FP2 was upgraded within the first day or two of my ownership. Thus, it is possibly a bug in older firmware. NOT that I am recommending you upgrade - it is just a hypothesis...
Thanks Dan. I'll keep watch for the update and see how things shakeout with those that are already on 1.17_0028 to see if I should be joining the party.
Got mine in yesterday and I'm evaluating in parallel for now... I think I have the three ghosts pretty well trapped for now, but we'll see how it goes. (Still on fw 1.1.5_0001.0015)
I read a comment somewhere (the HA community I think) that said it will stop working if the Internet is blocked. Is anyone else here successfully using it with the Internet blocked?
There was a report from Lewis Barclay, which may have been due to an even earlier firmware on press devices Aqara sent out. Don't know, as he didn't specify the firmware version he was testing with in the article.
However, I can tell you that on v1.15 and later, it does indeed continue to report the occupancy state in the zones when the internet is blocked. You simply cannot adjust the zones without temporarily unblocking its internet access.
[Edit] Hmm, I do notice that the screenshot from his article shows version 1.16, so it's possible he was just incorrect.
I feel like I have to say "successfully" with a huge asterix. I have my FP2s on HA, and they definitely work sending status to HA even with the internet blocked for the FP2s. The huge asterix is that the Aqara app won't talk to the FP2s at all in that state. The app just says there was a connection error anytime you try and interact with one of the FP2s. As long as you only need the status reported to HA, you're fine. But if you want to do any troubleshooting or update the zones with the Aqara app, the FP2s have to have internet connectivity.
Just a separate piece of anecdotal observation, in my experience it has been very accurate. Certainly not that the meter level. It’s accurately placing me into a zone while I sit at a desk or sit on the couch.
Yeah, more of an exaggerated comment on my part, but I watched the icon move the equivalent of about two meters while my daughter laid motionless in her bed...
Doesn't happen all the time, but it's hard to create automations based on that if it happens at all.
) behavior from the FP2 this morning. Blue light suddenly started flashing (Forgot to check if it was still active in HA 
), as if it was in pairing mode. Unblocked its internet and opened the Aqara app, but it couldn't be found. Tried to pair it again, but nothing found. I power cycled it for 30 sec and it came back online like nothing had changed. Blocked its internet again and it's working in HA just as before.
