Pretty sure this guy is going back. I did resolve my issue previously reported. Apparently for HA to discover the HomeKit device after it’s been deleted from HomeKit, it has to be on the same broadcast domain (same subnet). I can live with that. Now, I had it installed, it was in Home Assistant working fine until I use the Aquara app to create some additional Zones. As soon as I did that, and tried to reload the HomeKit device integration, it could no longer connect to the FP2. And if you remove it from HA, expecting it to be discovered again and hopefully showing your new zones, thou shalt be disappointed. It’s just gone, and you get to go through the while dance again. I am exhausted and I haven’t even created an automation to use it yet. This sucker may work with Home Assistant, but I’d not call it Home Assistant compatible.
Did we always have to remove a device from HomeKit to use it in HA?
Thanks, but no help for my situation. Addresses other Auara devices, and the Sleep mode of the FP2. I would not be using sleep mode. Still, I appreciate the response.
tl;dr blocking FP2 from WAN access decreases latency
Sure, it is an older thread but that is sometimes where the gold is!
I have been hunting for ways to reduce Aqara FP2 latency, both time to detect and FP2 presence detection to HA action. These two together I refer to as “overall latency.”
Use case: position-sensitive lighting.
Integration: My two FP2s are integrated via Aqara app to HomeKit, and then via HomeKit Device to HA.
Blocking outbound WAN access from the FP2 cut overall detection latency roughly in half. It also reduced missed detections arising from faster moving targets
That’s all I can give you now until I get more data.
Blocked:
Outbound port from FP2: 63296
Destination: 35.167.31.59:11111