I have experienced the same problem, sometimes they trigger false positives. I think they do it randomly but haven’t investigated if they do it on a fixed time. It’s a shame they don’t have an option to set the sensivity to fix this problem.
You can use this AppDaemon app to reset the sensor state after 5 seconds.
Should be available on HACS in the next couple of days or you can install manually.
Yes, this works in conjunction with the hardware mod. The hardware mod makes the device report motion every 5s, but the state in HA remains on for up to 300s before resetting to off. The app resets it after 5s, so together the motion sensors in HA work great every 5s.
The only difference is what you have seen, the time that takes to reset. I suppose in Aqara’s/Xiaomi’s closed ecosystem it makes sense because the automations are much simpler than what is achievable in Home Assistant
Ah, ok Thanks! I’m now also just using the sensor directly with zha and the automation that has been posted above to reset the sensor every 5 seconds. No hardware hack! Works perfectly
You need the hardware mod too. Without it it’s going to work fine just for some hours after pairing, after that the motion trigger will just trigger once each 2 minutes
But does it also trigger again after 5 seconds? That’s where the hardware mod is for. So you can actually trigger it after 5 seconds. The software hack is to reset it after 5 seconds.
Move in front of the sensor to trigger. Wait 5 seconds for it to reset. Then try trigger it again as soon as it’s off. Will that work, or will it not trigger for 2 minutes?
You should have an apps.yaml in config/appdaemon/apps. That’s where you put all your app configurations. The default install should contain a hello world app.
Is the AppDaemon app still working in 115.3? Just made the hwmod and installed app via HACS, but sensors state is resetted after 1min30s even though timeout is set to 5 in apps.yaml.
I did the hardware hack on 3 xiaomi/mijia sensors, and with the 3 sensors I’m getting false/ghost triggers after the initial motion trigger. The false triggering occurs at random delays after the first, real trigger… sometimes it is 7 secs later, other times even a minute later… the 3 sensors exhibit the same behavior… I’m connecting my HA to them via ZHA to Sonoff Zigbee Bridge flashed with Tasmota.