I received a new Firmware on two of my devices. 1.2.5 now allows mounting the device into a corner and not having to bother with weird mapping stuff.
Unfortunately two unused, just unpacked devices just upgrade to 1.2.3 and another device on 1.2.4 (which one device in use never received, but now offered 1.2.5.) does not show the 1.2.5. Since I wanted to install almost all of them in corners this is annoying, but we will see how long it will take to get the new version on all of them (upgrading all at once is kinda risky anyways…).
In case it may be useful for anyone reading, using firmware 1.2.3_0005.0066, I had the luminance sensor working, but no presence detection , having tried lots of ways to make it work.
In the end it worked after I added a detection zone and deleting the zone; it reset the sensor and it appears to be working fine.
I’ve just updated my FP2s to 1.2.5_0003.0072, which is the firmware that supports corner mounting without the weird mapping.
My FP2s have always been corner mounted, but I can’t see any difference in the maps or find anything in the settings to tell it the device is mounted in a corner.
It may not require a full factory reset… Here is the procedure I tested recently.
In the Aqara App, when you select your FP2 sensor, you can go into “Zone Management” and then click the top right icon to NAME and SAVE your current Zone configuration. Verify the zone config was saved by looking for it under the lower left “Template” icon. You’ll want to have this template available for later.
To change the location of the FP2 to a Corner, go back to the main page for the FP2 sensor, then click the top right corner 3 dots menu, then Device Settings, and then Detection Mode. Make sure Zone Detection is selected, and then click “Install Now”. You will be prompted to “Reinstall” the device. Choosing to do so will allow the choice of the FP2 location. Keep working through the menus and then select the Template you saved earlier and Apply it.
NOTE: I have only done this with a FP2 sensor that I do not have connected to anything. Thus, I am not sure if the device will stay connected to HomeKit, Alexa, Google, or Home Assistant through this process. Please proceed with caution!
This is quite interesting, because - if I remember correctly - I just went the way of pressing the button “Installation Mode” and even with saving the map before I was not able to choose the map with another installation location.
I have on more device to setup in a corner and will try your way!
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…”.
