Thank you! I connected my FP300 to HA via matter/thread, not Z2M. Do you have suggestions in this case?
Are you using the thread or zigbee protocol?
Ever since I bought 3 FP300’s last year, they will randomly get stuck on detecting presence, even though no one is in the area. I’ve tried every setting combination possible and have done countless “AI Spatial Learning” calibrations. Nothing seems to fix the issue. Every time I re-calibrate them with the AI Spatial Learning, they work perfectly the next few times someone walks in/out of the area. Then they gets stuck again! I was hoping this recent firmware update would fix the issue, but unfortunately not
The next version of Z2M is out, it has
- #12383 Aqara FP300 (PS-S04D): configure reporting for presence and PIR (@drauziooppenheimer)
Thread. But it took like 20min to update each one. So we just be patient😅
Which thread border router are you using in HA?
Have you tried a factory reset and calibrate again. I know it seems the same but as it has happened to me with other devices…it’s not.
Try factory resetting it. Add again and calibrate.
Hope it helps
I am using an apple homepod mini as the thread border router
Do I have to have an aqara thread hub to be able to update? I connected FP300 to apple home and home assistant directly via thread, none of them showed the updated.
Also, my FP300 become unresponsive today (after three weeks of installation), is this expected?
How do we get the firmware on Home Assistant for Matter over Thread @Blaze?
Without using an Aqara Hub or app.
The thing that fixed this for me was pulling the batteries. During the first weeks of setting mine up I had exactly the same behaviour, stuck presence with nobody in the room, and recalibration would hold for a while before it drifted back. A full power cycle by taking the batteries out for a minute cleared it every time, and it stuck properly after that. My guess is that AI Spatial Learning writes a new baseline but the sensor is still carrying whatever state it built up before, and only a hard power cut clears that.
Worth doing in the right order: take the batteries out, put them back, and only then run Spatial Learning on the empty room. If you calibrate first and the old state is still sitting there, you are calibrating on top of the problem.
Mine have been running very reliably since. Three FP300 all misbehaving the same way does sound more like a shared cause than three faulty units, so I would try this before assuming the firmware is at fault.
Has anyone managed to get the 1 second absence confirmation period to work properly? I set mine to 1 second but the absence detection still takes between 7-10 seconds. Currently using 2 x FP300s directly with Zigbee2MQTT in Home Assistant. Many thanks.
Same here - I think its a bit faster now?
I was using old thread firmware, when I switched recently to Zigbee, 6542 was installed. I use Z2M as well, with Absence delay timer set to 1. It takes around 10 seconds. Is it possible to get it to shutdown faster?
