I also experienced locked motion and presence alarms, but primarily when using them with thread. With zigbee the issues was that the devices seemed to stop reporting after about 24h, but this was fixed in v1.16.3 of the Aqara app. They have been running relatively stable since release of the new app version.I notice (also with zigbee) that devices that are situated a bit far from Homey tend to clear presence and motion a bit slower than those that are close to Homey (i.e. on the same floor). The FP300 seem very sensitive to zigbee communication issues. Do you have some grid powered zigbee router devices between Homey and the FP300 end devices? Are the problematic devices located far from Homey itself?
I do have powered Zigbee router devices between Homey and the FP300. I have Aqara smart plugs installed on every floor acting as Zigbee routers.
Current route is 0 → 7 → 8.
Before re-pairing, the route was 0 → 7 → 5 → 8.
The FP300 is located one floor above Homey and currently routes through an Aqara smart plug.
What makes me doubt this is purely a Zigbee issue is that I tested the same FP300 with an Aqara E1 hub after updating the firmware.
In Aqara Home, presence cleared correctly when leaving the room and motion behaved as expected.
After removing it from Aqara and pairing it directly to Homey again, both alarm_motion and alarm_presence remain true.
I left the room for approximately 25 minutes and both capabilities stayed active the entire time.
During that period:
RX continued increasing (101 → 128 → 182)
Last Seen remained below 1 minute
Illuminance updates continued normally
This makes it look like Homey is still receiving updates from the device, but motion and presence are not being cleared correctly.
Could this still be caused by Zigbee communication issues even though the device remains online, RX keeps increasing, and all other sensor values continue to update?
I have this same issue, but only alarm_motion remains true. But only with one FP300 of the two i have. And the one that is having issues, is like 2 meters away from my homey.
Tried so many things, and sometimes it seems like its fixed, but then within a day it gets stuck again.
If not, please contact the app developer by posting your findings into the dedicated Aqara app topic, as published on the app page at the homey.app store.
I fixed it for now by updating homey to the latest version via USB.
But now, everything time I reboot homey the aqara fp300 sensors don’t respond anymore. I always have to “repair” the device and everything is fine again.
As I am playing with the position of my homey, I noticed it multiple times.
I can confirm that I’ve also had this exact problem with three FP300 sensors failing to poll the motion and presence sensors when paired as Zigbee devices via the Aqara Homey App.
When paired to the Aqara M200 Hub, they function, but you lose finite control as they are then bridged to Homey as Matter devices.
It appears that the sensors enter a frozen loop and issue constant timeouts to Homey, as every attempt I make to reboot or calibrate the sensors returns timeout disconnect error.
Hopefully someone is able to track down this bug as it is hugely disruptive for lighting flows. The only way I’ve been able to reset the sensors is by clicking “Repair,” which seems to wake the device again and gets things working until the next time it shows up again (multiple times per day).
I recently purchased 2 of these and very disappointed. I connected to Aqara app, updated firmware and changed to zigbee, paired successfully direct with homey (done have a Aqara hub) and worked fine for a few hours then gets stuck on motion detected and doesn’t release. Zigbee has it as direct connection, no hops. I only have 4 other zigbee devices as still just testing everything before moving into our new home. The only other devices are Sonos speakers, Philips hue bridge and some globes.
I wish I saw this before purchasing. I have now ordered some Zemismart ZPS to try.
Using a honey pro 2023 on latest version. Aqara app on 1.19.1
Can you all share more information on which Homey version you are experiencing these issues with the FP300?
Please run the latest test version of the Aqara app (v1.19.2), see Aqara app topic for direct link.
Please check in the developer tools for these devices:
Are the sensors directly connected or do they depend on another node?
Any Rx or Tx errors visible?
Note: please focus on the presence alarm only.
The behavior of the FP300 is that motion alarm will not cancel until presence alarm is reset and motion alarm is not exposed on either thread or Aqara hub.
New app update has been release with improved communication (active check after 15 minutes if presence is still active), including the firmware update option to update the FP300’s to the latest version.
Current test at the latest FW version, with capturing the RAW zigbee communication as well as comparing the actual hub logs, between a set of FP300’s paired to Homey and a Aqara M3 hub, did not show any differences in cancellation behavior.
