Usually not. In general you can assume most anything labeled homekit works with HA, locally and without any cloud dependencies. It’s not quite 100%, but pretty close.
Apple would want you to think that, but no, HA actually has the codes where you can turn your HA server into an (non-Apple) HomeKit “hub”, where your HomeKit devices can talk to.
I can’t pair the sensor with my new HA instance.
I recently setup a whole new HA environment. I used to have the FP2 sensor paired with my old instance using the HomeKit controller integration. Before destroying the old HA instance, I did not unpair the FP2 sensor from the integration. I am now trying to repair the sensor with the HomeKit integration but the device never shows up.
I have reset the device and factory reset it (by pushing the reset button 10 times) but I still cant get it to show up in HA, I am worried that the factory reset does not unpair it from the old controller. Has anyone else had any success moving the device to to a different HA?
edit: This turned out to be 2 completely unrelated issues; my sensor and home assistant were on different vlans with a firewall rule blocking them and my device discovery wasn’t working properly from inside a docker container.
1 Like
How did you fix the docker container issue?
got one today. New version firmware too : 1.2.3_0005.0066
Strange, 2 days ago, upon checking for FW update I noticed that on one of my FP2s there is update available to 1.2.5.0003.0072. Strangely just a minute later this update was not available for any of other FP2s… So only one updated. All other stays for now on 1.2.3.0005.0066.
After the update sensor started to behave strangely, so I had to go through initial setup process. Now it finally allows to set position of the sensor to the corner of the room (which actually was the case for this specific sensor!). After reconfiguration (edge detection and AI absence learning procedure) everything seems to work fine.
Anyone seen this update and succesfully updated? Any info why this was pulled from distribution?
https://www.reddit.com/r/Aqara/comments/1ab7xxl/new_fp2_update_125_00030072
only reference to be found
1 Like
The angle mounting is nice, but it’s a pain in the app to actually find it. When you click on installation mode, you just get something telling you the current installation mode. It took me 20 minutes before I decided to click the text that says INSTALLATION GUIDE. When you do that it walks you through some steps that will let you pick the angle mounting. The Aqara folks desperately need some UI folks. Or at least they need to stop having a German translate everything from Japanese to English.
I also noticed a couple of features that are listed as “limited free.” That includes:
- advanced functions (currently visit counts/current count)
- sleep monitoring detection mode
I have no idea when those showed up though. I only stumbled on them while trying to find the angle mounting setup.
It’ll be interesting to see if they want to start charging monthly or one time for these new services, and what that might mean for the ability to run these with internet blocked. I mostly have these blocked from internet access and only unblock to do updates (or unblock for awhile if I’m troubleshooting zone setups). I’ll be a little ticked if they go from “internet for setup only” to “internet required.” I’ve tried a couple other mmWave based sensors, and the FP2s are the only things that seem to work well in my environment.
1 Like
you dont have to ‘pick’ the angled installation. It just shows that angle is fine. The info on UI is indeed somewhat confusing. Also editing the room and the sensor placement is huge challange for me. Detection is quite ok, number of persons is easily miscounted
I have a complexly configured map of my room with a corner mounted sensor, still in the version where the room map is angled.
Now a new firmware has arrived and also a new version of the app. Is there any way to upgrade the current map to the new layout, or do I have to delete it and completely reconfigure it again?
1 Like
Since the last update to “1.2.5” my two Aqara FP2 are not connecting to the Homekit integration. They are working from the official APP and I see that they are online (I have pinged from OS and it responds to ping). anyone else is the same thing happening to them?
➜ ~ ping 192.168.1.89
PING 192.168.1.89 (192.168.1.89): 56 data bytes
64 bytes from 192.168.1.89: seq=0 ttl=255 time=168.309 ms
64 bytes from 192.168.1.89: seq=1 ttl=255 time=166.312 ms
64 bytes from 192.168.1.89: seq=2 ttl=255 time=177.092 ms
64 bytes from 192.168.1.89: seq=3 ttl=255 time=196.302 ms
64 bytes from 192.168.1.89: seq=4 ttl=255 time=15.104 ms
^C
--- 192.168.1.89 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 15.104/144.623/196.302 ms
I’m sure I read somewhere that turning polling Off and On again kicks it back in
I finally had to reset the device, it seems that the homekit connection was being used by another hub instead of home assistant. I did not understand why. The good thing, even if you reset the device, the zone settings are retained.
As I understand it:
press and hold button for 10 sec resets network.
(press quickly 10 times is factory reset)
I have exactly the same error for my 3 FP2 devices. Can you please elaborate what steps you took to get your devices to connect again?
I tried to reset one device by pressing the button for 10 seconds and reintegrating it into the aqara app, but unfortunatly the HomeKit integration still throws the same error after restarting.
I had some problems where the FP2 was not detected in HA. They are on different vlans. I restarted the avahi service on pfSense and it was detected within a few seconds.
FW 1.2.6 is out and I observed strange issue with MAC address change after update. Luckily Homekit Controller exposes them to HA without changes, but my Uptime Kuma monitoring alerts me now about these sensors being unavailable - moved from IP reservation to DHCP… Any known solution?
Same here, getting multiple entries in unifi network
I can only confirm the truth of what you’re seeing. I updated one of my FP2s, and the MAC address changed (as did the Manufacturer information in the Unifi console). I went in to the offline area in Unifi, removed the static DHCP assignment for the old MAC address device and removed it. Then I set the new MAC address device to use the IP I had originally assigned to it and rebooted. Now the device has its old IP again. I’m glad I only have four of these in use, so it won’t be too bad to get them all back on their old IP addresses (which I need to do because I block them from internet access unless I need to upgrade the firmware).