New Aqara Human Presence Sensor FP1

Sorry for noob question, After i unzip and put the file.ota in z2m directory + update override name file. It regconize there are fw to downgrade but when I click, the system show fail image

I think the result will be the same, but you can also try this modified firmware.

same issue here, I use firmware 54 with z2m 1.36.1-1

Same problem, please help…

My understanding is that regions can only be set up in their proprietary app (but after that they are supposed to work in Z2M). Which was why I never bought one.

Hi @dmitryd, after laying in a drawer for about a year, a few months ago I decided to solder again the 2 wires of the USB cable and surprisingly they came back to life and have been working fine ever since. Hopefully that will help you revive yours as well.

1 Like

Apologies, apparently I was wrong! I learned they did get zones working in Z2M (on the original FP1)!

I still think these devices are wildly overpriced though. :smiley:

I’m happy to hear from anyone who got Zones working via Z2M.
So far, all comments here show it isn’t possible.

I think the information is over at Z2M, not here on HA forum. With the caveat it only works on the original FP1. At least that is my understanding, as I have not done it myself.

I have the same issue. After updating the firmware version to 58 (I don’t know how it happened), the sensor started switching to ā€œleaveā€ status even when there is motion. I tried rolling back to firmware version 54 by specifying a local file for the OTA update, but for some reason, Zigbee2MQTT still looks for the file in the repository and throws an error saying that the version is newer than in the repository. What should I do? Wait for an official firmware update? That might not happen. Taking a shower with a light show isn’t really an ideal option.

I contacted Aqara support. They replied that they can’t help because they don’t support direct ZigBee connections to Home Assistant — only connections through their hub (which I don’t have).

It seems my temporary solution will remain permanent. The solution is simple: in the automation for turning off the lights, I set a 1-minute delay after the sensor switches to the ā€œleaveā€ state or any other absence state. Maybe this delay can be reduced, but I haven’t experimented with that yet.