Closing the loop on this one. Placed the same reply on thread "Firmware problem with Aqara - Presence Multi-Sensor FP300" as well.
The Homey Aqara app was updated about a week ago with what appears to be the fix (explicit manuSpecificLumi binding + reporting configuration for the manufacturer-specific presence and PIR attributes) that andreas_roedl documented on the Aqara forum and that SmartThings and Zigbee2MQTT had already implemented.
One week in on my 4 FP300s: only a single hang across the entire fleet, on the lavatory unit around day 4. Otherwise stable. That’s a dramatic improvement from the every-24-hour dropout pattern we were all fighting.
A few thank-yous:
@TedTolboom for shipping the fix.
@Peter_Kawa for the IKEA routing hypothesis and the Z2M/Home Assistant reference docs — the mesh fix (removing all IKEA TRETAKTs and replacing with ThirdReality Gen 3s) was a real improvement even before the app update.
@Jason_Edwards, @Trond_Nordfjaern, and everyone else who added data points across platforms — the cross-platform evidence is what made the diagnosis convincing.
And credit to Athom support (Bas) for escalating internally when the community-facing side went quiet.
Leaving this here in case anyone lands on the thread searching for the FP300 24-hour dropout issue — the fix is in the Homey Aqara app, update it and give it a week.
