Do you mean for the Aqara servers? I don’t. I have mine setup so that the FP2s can’t talk to the internet at all. When I need to do a firmware update, I disable that firewall rule, run the update, and then turn it back on.
I have the Aqara’s on my IoT VLAN, which is also where HA is, so I don’t have to do any cross VLAN configs for those two things to communicate with each other.
Has anyone faced the Problem that FP2 ist set up and needed to get rebinded to a new HA instance? How to do that without resetting and erasing zone data in FP2 device?
I think it may require a reset, however all is not lost. You can backup your Zone Data so that after a reset, you can then reload it, and then pair it with a new HA instance using the HomeKit Device integration.
I posted how to backup your zone configuration earlier in this thread. Hope this helps.
Anyone figure out how to get sleep/wake status to pass through to HA? Its configured properly in the app, but only acts as a presence sensor when passed through to HA
Has anyone figured out how to get the FP2 working in Docker? I bought it on the assumption that the Home Kit integration would do the trick, but the FP2 is never found by Home Kit.
Hi,
I just received my aqara fp2.
I haven’t Aqara hub, but I’ve a old xiaomi hub.
I download Aqara Android app and try to add FP2 to it but each time I’ve an issue “error 10004 check if device is waiting network connection. IF Hub M1S or E1 is connect to Mi Home…”.
Yeah, that’s what I want to clarify.
If I label the ceiling as interference source in the map, then anyone standing under the fan, their presence would be ignored?
Yes, that is correct. Any square on the grid marked as an interference source, will simply be ignored. Very useful for ceiling fans, as well as curtains and plants that move even a little when a fan or HVAC system is running.
Maybe? When I set mine up, the ‘auto detect’ wasn’t all that useful. I simply walked around the room with my phone in hand, and added things to the grid (exits, interferences, furniture graphics, etc.) until I was satisfied with the results and how each ‘zone’ was defined. This was back just after the FP2 was released, so maybe the ‘auto detect’ feature has been improved in later firmware revisions?