I followed exactly the same route, though not without glitches:
one of sensors did not received yet update, forcing check shows that it is up to date As this is recently added to my setup, I assume this is because of newer HW build and update should come soon. One strange observation for this particular one; router hsows different MAC address of sensor than Aqara app
I have one sensor from China distribution (unlike others from European one), so need to switch regions in App to get FW update… otherwise, for HA works the same. Just additional tasks to remember…
Hmm, I don’t allow unknown MACs on my network, I usually have to add a device twice to get it on the correct SSID, once to an SSID with nothing on it so I can get the MAC, and again to where it’ll live. So if the 1.2.5 to 1.2.6 update changed it’s MAC during the update process, that would probably explain why the only one of these I had that tried to do that update, bricked itself.
UPDATE: OK so not bricked apparently, had to reset the FP2, reboot my phone, reboot my access points, clear the ARP table on the router to get it to rejoin, but it did rejoin. Very bad form, MACs are the identifier of the device, you can’t just change them on a whim. LIFX has done this too, but usually only by adding 1 to the old MAC.
Hey @skorpioskorpio, I experienced the same just now, I couldn’t understand what’s happening for a rough 30 minutes, kept reregging the device and failed at it .
Not only the MAC changed from dc:ed:83:xx:xx:xx to 54:ef:44:xx:xx:xx, but the device string has changed too. Originally it announced itself as “Presence-Sensor-FP2-XXXX”, and after the fw upgrade this became empty (“”).
Yea, I had had only one update, a couple days after I posted that all the rest updated at once (I have 21 of them). What a mess, hopefully they won’t do that on the next update.
Back in the days i had ~10x FP1 and they where just crap.
The issues i had:
ghosting (sometimes it just triggered, and nobody was in the room)
stuck in “presence detected” (sometimes a cold power reset helped, sometimes re-pairing). At the end a few of them i had to swap the PCB for 180 degeres or remove it to get it working again.
After all the issues (also after several fw updates) i decided to replace all of them with esphome DIY sensors with DFrobot SEN395. They work better, but sometimes, when i am sitting still for while the are clearing the presence.
So i am looking for an upgrade to these.
Now, that the FP2 is out in the wild for a while i want to know your thoughts, issues, …
Also read wome reddit, amazon, … posts, that also ghosting is an issue on these.
The last changelog of 1.2.6 also states some improvements on ghosting.
Can you please share your experience with these FP2 sensors on different Firmware Versions (maybe also the new 1.2.6).
I’ve read through this thread and Googled it, but maybe I missed the answer…
Is it at all possible to get the FP2 to link up to HA if they are on different subnets? When I go to add the FP2 to HA via the Setting > Integrations > Apple Homekit > it says there are no unpaired devices available to add… Probably because it on a different VLAN, but I’d like to keep it that way if possible… Can I? Or are we forced to have them on the same VLAN / subnet?
I still have some ghosting issues, but not often and not that bad. The FP2 is still not great at detecting me when I sit still, which was suppose to be one of the great selling points of this sensor. I think performance really depends on your environment, so you might just have to buy one and test it.
It is possible to setup your VLAN communications to allow HomeKit discovery across VLANs, but exactly how you do it depends on your network equipment. Here’s a blog post I found that talks about doing it using UniFi equipment (the part about HomeKit is down the page a ways). If you aren’t using Unifi equipment, it might get you pointed in the right direction.
I think you need LAN Local as the type. It’s not in any of the screenshots in the article, but when you get to the HomeKit section, there is one line in the text that says the author is looking at LAN Local setting. You could be forgiven for not noticing that.
“Home” app? Which app are you referring to exactly? I setup the device in the Aqara app and then tried to get Home Assistant to discover it on my wifi… which it didn’t due to VLAN’s. I tried to create the appropriate network rules for it to be seen across VLAN’s but they didn’t seem to wok.
In the end I reset the wifi credentials on the FP2 and just put it on the same VLAN as HA instead of my iot VLAN.
I’m just doing a full house renovation and I’m considering using an FP2 in every room - is it mature enough, has it improved? Am I setting myself up for a world of pain and should I be considering going back to regular motion sensors?
My goal is mostly to detect lack of presence to turn off lights and also to create various presence zones in each room (e.g. sofa vs chair).
I have 5 of those currently and I’m very pleased. In some circumstances these might not be 100% accurate to precisely position person within zone, but with a bit of experimeting and ‘tolerance’ build into created zones works perfectly for me. I’ve never had issues, that others faced, with initerferences, ghosting and false detections, perhaps setup of my rooms is simple enough not to create issues.
I have six of them. They are mostly fine. I think the placement and the environment are big factors in success, and it’s hard to say in advance how happy you’ll be. Mine show false positives sometimes, but if I restart the sensor, the ghosts go away (I restart it because I block the FP2s from internet access, so I can’t use their app to delete the ghosts). And I gave up on it ever detecting me or my spouse while we’re sleeping. I had to go to a different kind of sensor to figure out if the bedroom is occupied.
Same issue on my side now. If you remove the FP2 from HA HomeKit, it then becomes undetectable by HA HomKit! How come no one mentions/discusses this, it’s a huge problem!
If anyone managed to solve it, PLEASE post an answer. I’ve seen this issue raised in a lot of places.
Have you tried to check if it is in disabled/ignored state by chance? Go to Settings>Devices & Services and in filter boz check show ignored/disabled. Perhaps it will reappear…
I know that after removing the FP2 from an actual Apple Home/HomeKit system, you must power off the FP2 for a few seconds, and then power it back on. Only after doing so will HA detect the device being available to be integrated as a “HomeKit Device”.
Perhaps the same is true when removing the FP2 from HA?
As this is recently added to my setup, I assume this is because of newer HW build and update should come soon. One strange observation for this particular one; router hsows different MAC address of sensor than Aqara app 
.
