It looks like the FP2 is being detected by Home Assistant for some people after it has been removed from HomeKit but not others. Unfortunately I’m in the camp where it isn’t recognised by Home Assistant.
I’m wondering whether the issue for me is that my IoT devices are in a different subnet from my HA server. It’s not been a problem for other HomeKit devices but maybe there is something quirky about the FP2. If I get chance this weekend I’ll temporarily shift HA to be on the same subnet to see if that helps.
I don’t have different subnets but i am getting stuck at step 1: “Add the FP2 to HomeKit through the Aqara App”
How can i do that when not having an iphone? When installing " Homekit" in Home Assistant, it says the following:
But how to proceed? How/where can i utilize the Home App when running on Android?
I got it working. It’s kinda weird but the following helped:
-my device was already connected to wifi by setting it up before in the Aqara app
-add Homekit Controller Integration, choose the FP2
-Homekit Controller spinning wheel running indefinitely
-while spinning Homekit Controller setup, reset the FP2 by 10 second long press on the device button
-while spinning Homekit Controller setup, open the aqara app and re-add the device
-in the background of Home Assistant integration page, the device is suddenly discovered. Cancel the Homekit Controller spinning wheel
-navigate to the discoved device in the integration page and enter the pincode as stated at the back of the device
It’s now succesfully added.
Super weird, but it works. Soldering and flashing Sonoff devices feels more straighforward to me than this, somehow i miss the logic.
I’ve good news to report. Until now, there was conflicting information about the device not working after blocking internet access.
When blocking internet access, the device keeps running. Even after power cycling it. And even after opening the Aqara app and trying to make some changes to the device (which obviously does not work since this poorly designed app is cloud-dependent).
I have upgraded the firmware to the most recent version before blocking internet access. I am running version 1.1.6_0005.0025.
Another positive observation is that speed of detection is very high: it is equally fast as the Philips Hue Motion Sensor (which is considered to be the best of its kind that you can buy).
I’m also seeing that here. I have a separate IoT VLAN, so I can easily block all the internet traffic for that entire network. Once I had one of the FP2s setup on the IoT VLAN, I blocked all access. It still reports in HA just fine. Interestingly, if I move my phone back to my regular network (which has access to the IoT network), the app still won’t talk to the FP2. So for you to use the Aqara app requires a cloud connection for sure. I may end up assigning the FP2s static IPs and then blocking their internet access and then just pause that rule any time I need to update the config or the devices.
If it’s not too much trouble, could you tell me, is the Home Assistant in the same subnet as your IoT stuff, or is it succesfully “talking” to the sensor from another subnet?
I’m asking because the older Xiaomi stuff (bulbs mostly) were setup not to responde to connections from a subnet different then the one they were on.
My solution at home has been to put one “network adapter” of the NUC I’m running HA on in the “MAIN” subnet, where the users can reach it and another in the “NOT” subnet (IoT without I), where I keep things that are never supposed to talk to the internet.
I’m thinking of getting this sensor if I dont manage to come up with something with similar capabilities but from the zigbee / z-wave reallm. Thanks in advance.
I have two set up. One in the Living Room and one in the Kitchen. They can ‘see’ a little of the same area. I just set the zones to not overlap each other and they are working great.
I have six of these to cover the whole house (only two setup so far). At bptworld said, if you do nothing, then can both show occupancy (hesitant to call that interference, as they are both properly detecting a person).
I’m using a two-fold strategy. I’m defining zones and edges to avoid some of the overlap, and in other cases I’m using the overlap to my advantage. I’m letting the sensors overlap and defining a “living room” area on the kitchen sensor (for instance). That actually helps me due to the shape of my great room, as there is some of the great room only the kitchen sensor can see and some that only the great room sensor can see. My plan is to do some template sensors in HA so that the living room is occupied if the living room zone on either sensor is occupied.
This might be extremely difficult. There is a lot more to this sensor than just presence. You will need a whole new interface for zones etc. I don’t mind having to use their app. The device itself works when offline, just need to be online for the configuration. They area also release a lot of updates so that is good as well.
My best guess is that the sensor is divided as a matrix, which each cell having a presence probabilty between 0 and 1. The rest could be all gui, summations, etc. If my assumption is correct, translation would be less difficult that it seems at first glance.
Inteseting times! I’m very curious to see how this development is going onwards.
My sensor is now installed. Correct installation is key. Try not to implement dead zones in the software. Instead, aim the sensor in such a way that the difficult spots (in my case a window and a ceiling fan) are not in sight of the sensor.
Reason not to use dead zones: if a person enters the dead zone, the presence is not detected anymore. In my case: if i would stand beneath the ceiling fan, i would become undetected.
I installed the sensor high up, in the corner, by using a angle iron (bending it to 45 degrees), taping it in white electrical tape for an incognito look, and using a white tiny cable tray. By putting it high up in the corner, facing the sensor downwards, i get 3 benefits:
-curtains/window is not detected
-ceiling fan is not detected
-perfect vision to the rest of the room
Anyone stuck on ‘Waiting…’ on the firmware update? I purchased 3 units and have 2 setup to start experimenting with. I was seeing a lot of timeout issues when making changes to zones, etc so started a firmware update about 2 hours ago and still stuck on ‘Waiting…’ on both units, with the LED indicator slowly flashing yellow. According to the manual this means they are doing an OTA update, but they never show anything more than ‘Waiting…’
Tempted to pull the plug and do a hard reset of them, but scared to brick them and since they are out of stock on Amazon there’d be no replacing. Thoughts? Guessing everyone on the planet took delivery of theirs today and maybe Aqara wasn’t ready for the load?
I just received my Fp2’s. My plan is to Install the Aqara app add the Fp2’s through the Aqara app then add to Home Assistant. Then add the Fp2’s to HomeKit. I’m wondering if I’ll get all the Zones in HA and Homekit?
