I have moved my six FP300 from matter over to zigbee now. The 24h bug seems to be gone. As for reliability I need to give it a week or so. But it looks relatively promising so far. A bit of random variation in how long time they use to drop presence after people have left a room, but rarely exceeds 2 minutes (timeout set to 15 seconds). I can live with that compared to matter where they could randomly get stuck on presence alarm for hours. Thanks for all your efforts @TedTolboom
Since the last update, none of my fp300 sensors are reporting luminance. What seems to be the problem here?
This is also no good. Random locked presence 10 minutes after a room was left. No way to tell if it is due to Homey Zigbee, the Homey App or the FP300 firmware. The particular device mostly works fine and this happens rarely, but these devices need close to full reliability to be useful. Random hangups have consequences.
Edit: 34 minutes and counting. Had to repair the device to recover after 1h.
I am on v 16.3. What this update fixed was the 24h bug where everything stopped reporting back to home after about 24h. The issue described here happened after several days and I think lux, temp, hum etc. kept reporting. Just locked up in presence alarm when no people around in the room (failed to clear the presence alarm when supposed to). It is not a systematic issue and most of the time this sensor works fine, but yesterday had this locked in presence alarm issue.
I have given up on the FP300 for controlling lights in my lounge and sent it back. I have bought a Hue Motion Sensor instead to try on my stairs to control the lights on them. I now have an issue with the luminance being updated homey. It seems to only change when i go in to the hue device in homey. My issue is that I i have a homey flow that uses the luminance card and checks the luminance to only allow the lights to come on if below a certain setting. Problem is when my lights do come on the lux jumps up, expected that, but then homey holds on to that setting even after my lights go off. This means that my lights do not come back on even if the motion alarm is yes.
Closing the loop on this one.
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.
A week after the update i can confirm my presence and motion alarms keep working, but unfortunatly the temp, humidity and luminance are all stuck. Tried repairing them and then it works again for a while but stops reporting afterwards (seems alot like the issue with the presence and motion sensors before)
