Firmware problem with Aqara - Presence Multi-Sensor FP300

Hi everyone,
Has anyone else experienced issues with newer Aqara FP300 sensors in Homey via Zigbee?

My setup:

  • Homey Pro 2019 (no Matter support)

  • Aqara app in Homey

  • FP300 paired directly via Zigbee

What makes this confusing is that one FP300 installed about a week ago still works perfectly:

  • presence detection

  • lux

  • temperature

  • humidity

  • timestamps updating correctly

However, multiple newer FP300 units now behave like this:

  • pairing succeeds normally

  • initial values for “Motion Alarm” and “Presence Alarm” appear random/inconsistent immediately after pairing

  • those states never change afterwards, regardless of movement or occupancy

  • temperature, humidity and lux initially show “Last value unknown”

  • after a few minutes, Homey starts showing “56 years ago” for those sensors

  • the devices then appear effectively non-reporting

Troubleshooting already performed:

  • Remove Device in Homey

  • factory reset of FP300

  • direct Zigbee re-pairing

  • pairing without Aqara app involvement

  • repeated tests with multiple FP300 units

Result is always the same on the newer units.

Additional observations:

  • It is unfortunately not possible to check the FP300 firmware version once connected directly to Homey.

  • I do not want to experiment with the one currently working FP300, since it is stable and functioning correctly.

  • Resetting the entire Zigbee network in Homey is also not an attractive troubleshooting step, since it would require re-pairing a large number of already stable Zigbee devices.

At this point I suspect either:

  • a recent FP300 firmware incompatibility

  • or a regression between newer FP300 firmware and the current Homey Aqara driver.

The older FP300 still functioning correctly suggests the Zigbee network itself is healthy.
Has anyone else seen this behavior or found a workaround?
Any help would be greatly appreciated. Thanks!

Possibly related:
AFAIK often there’s “China Mainland” and “Rest of world” models offered.
Make sure you have “Rest of world” models.

How can i see I’ve it is a “rest of world” fp300 device?

Decive settings show a type description like “lumi.blah.blah”
Check the 1st post of the Aqara topic to see if it’s mentioned and thus supported.
China targeted devices have different type descriptions.

https://community.homey.app/t/app-aqara-xiaomi-smart-home-simplify-your-life-with-a-smarter-home/156/7028

Good morning, I have the same issue since a couple of days. Both my FP300 stay in the same modus as presence detected. Tried rebooting homey, preparing. Nothing works

Is your Homey having latest stable fw release 13.2.0? If yes, then updating to experimental release 13.2.1-rc.4 will help, at least in my case. Lot of problems especially with Aqara zigbee devices with 13.2.0, but workin as normally again with 13.2.1-rc.4.

But first read up on what consequences installing experimental updates might have.

TX Timo, read through implications and installed it. Working fine again.

I would seriously suggest turning off automatic updates, otherwise you run the risk of automatically receiving updates that might break things.

I know what consequences there might be with experimental updates but now it seems that even “stable” releases can break Homey, like now happened.
And there is always possibility to go back to stable releases, just unselect experimental updates from the dev tools, and whenever there is next official stable release, you are back to official firmwares again, no more experimental updates.

That’s not what @Peter_Kawa says here: [HowTo][Pro 2023/Mini] Revert from experimental to stable firmware

And that’s the “easy” way of disabling experimental updates. According to Athom, you need to do a factory reset to disable them.

At least I have disabled “experimental updates” from dev tools, back in time, and after that I received stable updates only. Just couple of days ago I make this selection again, to get rid of zigbee issues.