Firmware problem with Aqara - Presence Multi-Sensor FP300

Devices
21

Hey Ken,

  1. I am still on 5841. I am reading in the Aqara community that 6542 seems to have resolved this issue so I need to get it installed. Was a great device when it worked properly.
  2. I did try reinstalling the firmware a few times with no difference.
  3. My problem started when I updated the firmware to 5841 which I did not do intentionally. I switched to Matter to play around and of course when I went back to Zigbee the process installed the latest firmware.
  4. I use Zigbee. I am not that impressed with Matter or Thread at this time.

I will install the update later today and see what happens.

22

Coming back to this thread with a significant update. I just finished migrating to my Homey Pro 2026 and was about to reinstall my 4 FP300s when I came across new information that actually diagnoses what’s been going on - and the fix appears to land on the Homey Aqara app side.

@TedTolboom - tagging you because this is squarely in your court and I’d value your read.

Quick recap of where I left this thread: 4 FP300s on Homey Pro 2023, paired via your Aqara app in Zigbee mode, ran flawlessly for 4 months, then in late May all units started exhibiting stuck-state behavior (presence and PIR motion latching on for minutes to many hours). I’ve already reflashed all 4 to Zigbee firmware 0.0.0_6542 via Bluetooth, factory reset, re-paired, re-ran AI Spatial Learning, rebuilt the Zigbee mesh, confirmed no environmental correlation, and verified the bug persists across Homey firmware 13.2.0 and 13.2.1. Worked an email thread with Aqara support that ultimately went nowhere - they confirmed they can only investigate via an Aqara hub, which I don’t own.

The new finding (June 8 2026):

A developer named andreas_roedl, who maintains the SmartThings Edge driver for the FP300, posted a technical breakdown on the Aqara forum (thread 299625, post #10). His diagnosis: firmware 6542 is actually more standards-compliant than 5841 was, but it no longer reliably emits autonomous Zigbee attribute reports for the FP300’s manufacturer-specific presence and PIR motion attributes unless reporting is explicitly configured by the integration.

Manual reads still work. Refresh still works. Temperature, humidity, lux still work. But presence/motion gets stuck because the integration is waiting for autonomous reports that never come after the firmware change.

The fix he applied to his SmartThings driver, which made his FP300 “extremely reliable, no issues anymore”:

  • Bind manuSpecificLumi (cluster 0xFCC0) to the coordinator
  • Manufacturer code: 0x115F
  • Configure reporting for:
    • Attribute 0x0142 (presence)
    • Attribute 0x014D (PIR motion)
  • Type: Uint8 (0x20)
  • Min interval: 0, Max interval: 300, Reportable change: 1

The same fix is in progress for Zigbee2MQTT as PR #12383 (open, not yet merged). ZHA needs a quirk update too. Cross-platform users (Home Assistant + ZHA, Hubitat, and SmartThings before andreas_roedl’s fix) are all reporting the same stuck-state behavior, which aligns with the diagnosis.

References:

Two questions, @TedTolboom:

  1. Is the Homey Aqara app currently binding manuSpecificLumi and configuring reporting for 0x0142 and 0x014D, or is that something that would need to be added?

  2. If it’s the latter, do you have a rough timeline? I’m trying to decide whether to delay reinstalling the FP300s on my 2026 hub or push ahead and live with the bug temporarily.

Happy to provide logs, device IDs, or whatever else would help. Thank you for the work you’ve put into the Aqara app - it’s been solid for me until this firmware change blindsided everyone.