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 have the same issue where its not being recognized by HA Homekit. Checked to see if it was disabled/ignored, but nothing is there.
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?
I’ve tried that but nothing appears.
Have you tried a full factory reset of the FP2? You can backup its current room configuration/ zones within the Aqara app. That way, after you factory reset it, you can at least restore the configuration. Perhaps it will then show up?
Yup done all that, but still nothing in HA.
Hello all,
hope someone can help me out here.
Been reading trough the thread but i cant get the FP2 into HA in anyway.
first im using an android phone (dont have an Iphone).
I can get the sensor into the aqara app, but only got it to show in HA 1 time orso, and when it did it couldnt connect (blue circle kept spinning) and never asked me for a pairing code.
is there a detailed howto to be found somewhere on how to set it up using an android phone.
also i see everyone talking about homekit controller, but they mean homekit device right, and this doesnt find any devices in HA…
please help as i want to get this to work.
thanks
Hi there, I managed to make this work:
-Leave the FP2 unplugged for a few min
- Plug back in and directly go in HA, it detected FP2 for me.
It seems that FP2 enters discovery only after a power cycle for a limited time. Keep this in mind if you’re going to need to do another hard reset (press button 10 times)
2 Likes
hi thanks for the response,
HA seems to see the device but when i click configure now it just keeps loading and in the end i get error message “error : config flow couldnt be loaded”
same when i try to add it using homekit device…
any ideas…thanks
1 Like
ok so i got it working…
i unplugged all my Deco TP link WIFI extenders so i had only my original router (WIFI Point) working.
In my modem settings i disabled the 5 Ghz wifi and just enabled the 2.4 Ghz wifi.
Went trough the Aqara App setup and completed it, than i pulled the plug on the FP2 sensor and reinserted it again after wich it was found in home assistant and was able to configure it correctly.
After that i could enable the 5 Ghz wifi from my modem again and fired up all my TP Link WIFI extenders.
Works like a charm now
1 Like
as of the date of my posting I successfully installed the Aqara FP2 into my HA. I was having problems installing Aqara presence sensor into my HA because I am using an iPhone - which downloads the aqara home from the app store.
What I think worked is that I factory reset (10 seconds button pressed) my FP2, I then deleted the accessory from the apple home AND the aqara home app on my iphone.
I used an older samsung android phone to download the Aqara app from the playstore. I then logged in and connect the FP2 to the internet using the android phone. Apple is not involved at all this point.
After restarting both the HA and FP2, it does appear in the notification of my HA after a few minutes. Hope this helps someone.
2 Likes
So I had quite a fight with this on my setup, this guide applies to setups that are running HAOS on virtual machine. I found out that if you have HAOS in QEMU/KVM then the mDNS packages that are broadcasted get dropped because by default the virtual machine uses hardware offloading for those packages and that feature has some kind of bug that gives checksum fails. I had to disable hardware offloading inside the virtual machine, not the host, and after that FP2 was found like everybody told it should be found.
So if you have Home Assistant running inside virtual machine you can try the following steps:
- Log for incoming traffic, check if there are bad checksum packages. For this you need tcpdump program and the name of your network interface (in this example the interface is called enp0s2).
apk add --no-cache tcpdump
sudo tcpdump -i enp0s2 -s0 -vv net 224.0.0.0/4
Wait for a while for broadcasting messages to appear and if you can see there are bad checksum lines then continue to step 2.
- Disable “hardware” offloading in the virtual machine, again replace enp0s2 with your interface name
apk add --no-cache ethtool
ethtool --offload enp0s2 rx off tx off
That was enough for me but I found another command on a forum, you can add it if you want:
ethtool -K enp0s2 gso off
- Run tcpdump again and see if the errors went away.
sudo tcpdump -i enp0s2 -s0 -vv net 224.0.0.0/4
At this point you should be able to connect to FP2 (and perhaps other HomeKit devices), but you need to run these commands every time the virtual machine reboots, I did the following.
In configuration.yaml:
shell_command:
hardware_offloading: apk add --no-cache ethtool && ethtool --offload enp0s2 rx off tx off && ethtool -K enp0s2 gso off
Then added automation:
alias: Disable hardware offloading
triggers:
- trigger: homeassistant
event: start
actions:
- action: shell_command.hardware_offloading
data: {}
Hopefully this helps somebody struggling with HomeKit devices not being found.
2 Likes
Is this applicable when running HAOS under Proxmox?
I don’t know if Proxmox has fixed this, but you can check if the packets get dropped with
apk add --no-cache tcpdump
sudo tcpdump -i enp0s2 -s0 -vv net 224.0.0.0/4
This is done inside HomeAssistant, I use Advanced SSH & Web Terminal add-on
Hi everyone,
I’m using an Aqara FP2 Presence Sensor, and it works perfectly when a zone or room is empty. However, it fails to trigger automations for entries or exits when someone is already present in the zone or room.
Example:
- Person A is in the living room.
- Person B enters or leaves → No automation is triggered.
What I’ve Tried:
- Triggers:
- Someone enters/leaves.
- Someone enters/leaves from the left/right.
- Event detected (zone).
- Adjusting sensitivity settings.
- Testing in different zones/rooms.
The Problem:
It seems FP2 only detects overall presence state (empty ↔ occupied) but not individual entries/exits in multi-person scenarios.
Question:
Is this a sensor limitation, or is there a workaround? Any advice would be greatly appreciated!
Aqara unfortunatelly doesn’t expose person count, so no chance to get that value directly. However, there is a workaround: Room Multi People Detection in HA, with Aqara FP2 sensor
1 Like
Thank you for your response! What I’m trying to achieve feels like such a simple thing to implement. I’m honestly surprised that something this basic doesn’t work as expected. Do you think this is really a complex feature to implement, or am I overestimating how straightforward it should be?
The feature is super easy to implement. But it has to be done on Aqara’s side. Until they expose this value via Zigbee/WiFi, there is nothing HA could do.