I’m currently having an issue with my Aqara Presence Sensor FP2 since the latest firmware update 1.3.6_0003.0099. It repeatedly detects a false presence, which keeps my kitchen lights turned on even when no one is in the area.
To make it worse, when I check the app (as you can see in the attached screenshot), the “ghost” presence is located directly inside an area configured as an Interference Zone. The sensor should be completely ignoring activity in those specific grids, but it’s triggering anyway.
Has anyone else run into this issue since the update?
Is this a known bug, and does anyone know if it will be fixed in the next release?
Hi there, it looks like you’re experiencing a support-related issue. We’ve automatically created a support ticket for you and will reach out via the forum email within the next two business days.
If other members have any suggestions or insights on this topic, feel free to share!
Have you tried vacating the area completely and running through “AI Learning” on the sensor via the Aqara mobile app? This will reset everything to ‘absent’ in the space.
In the Aqara mobile app, open up your FP2 sensor, then click the three dot menu in top right corner, then Device Settings, the “AI Learning” and follow the instructions. Hope this helps to remove your ghost!
Thanks for the suggestion! I’ve actually run through the AI Learning process multiple times now, but the ghost presence keeps coming back.
What’s strange is that this wasn’t an issue prior to the firmware update. It’s possible the update somehow reset the AI’s learning data. However, logically speaking, setting an “Interference Zone” should act as a hard exclusion for that specific grid without needing any additional AI training, right?
I have left my FP2 sensors running an earlier firmware version for now, as they have been working very reliably for me for quite some time. Same with 2 out of 3 of my FP300 sensors. The one FP300 sensor I upgraded was so that I could fix the Zigbee driver for it on the Hubitat platform. New FP300 users automatically receive the latest Aqara firmware when they switch the sensor from Thread to Zigbee. Since this new firmware broke Hubitat, SmartThings, and Home Assistant Zigbee drivers, all had to be fixed. Always something to keep us on our toes, eh?
Yes, everything was running perfectly for me too.
Well, hindsight is always 20/20.
That’s just how it is with updates. Yesterday, an update here in Germany presumably brought all the trains to a standstill. It shouldn’t happen, but it does – that’s just the way it goes.
Well I had same issue till yesterday and aqara support told me to add walls on sides of the zone and use AI for better detection as I was seeing not one but two three ghosts in my kitchen and mine is small kitchen.last night I remade the holo zone with walls and added a few more things into the zona space were I knew that I have the door or some furniture this way the sensor will detect better and so far works perfectly.here is my zona made for the kitchen
Great for me as of now works perfectly and I didn’t notice ghosts so far.but do it the same way and try it for a few days and see how it goes.i am using it with the led strip t1
I haven’t touched the map in a long time, so I’m still figuring it out again. To edit the walls, simply long-press the gray area. Overall, changing the interference zones to walls has definitely made things better.
I do not know how was working before as I recently bought it and I had 2 updates in a row .ether way I already report it to aqara and see what they will say about
I have extensively discussed this problem with Aqara Support, and they performed a backend downgrade of my FP2’s firmware from 1.3.6 to 1.3.3 for testing.
After the rollback, the ghost presence issue (where actual absence was not detected inside the interference zone) stopped completely. The sensor’s behavior now actually leans slightly in the opposite direction: in about 1 out of 10 cases, it falsely detects an absence even though a person is still in the zone. However, this is perfectly acceptable to me, and I will be staying on version 1.3.3 for the time being.
Support also informed me that they have forwarded all my test findings to the R&D team for further optimization in future updates.
Big kudos to the Aqara support team at this point—they handled this case very professionally!
Have ran into this issue in the past (not with the latest update and it was in an inference source zone). I had to remove the interference source zone, run the AI learning, and then add the interference source zone back. Ghost entity stayed away after that.
Thanks for the tip! I actually tried that multiple times without success, too. Only the downgrade finally made the problem go away.
Overall, version 1.3.6 tends to falsely detect presence more frequently (even outside the interference zone) when there is actually no one left in the area. With 1.3.3, it’s exactly the opposite: now, in rare cases, it detects absence even though someone is still in the zone. But since you can just ask Siri to turn the lights back on, it’s not a big deal, and it definitely happens less frequently.
I can’t confirm an issue like this on my end since updating. It’s working as expected for me. Fingers crossed you can sort this out quick!
When I have issues with ghosts I ran AI learning multiple times and had set up walls since the beginning. It’s working good since but you already did that as well
Can confirm the 1.3.6 firmware is completely ignoring interference zones regardless of what the user does.
It seems that they overdid things in a effort to fix 1.3.3 rare missing detection issues and went to far in the other direction causing a bigger issue.
