I tested using Ogewon’s dedicated driver as well, but it also didn’t work after updating the FP300 firmware.
Are you absolutely sure that the motion active/inactive is updated automatically after updating the firmware to 0.0.0_6542 ? What is your HE hub model?
No, Im not 100% sure - it might have been the refresh command that did it. Im on a C8 Pro.
I have now published on GitHub the test version of the Aqara P1 Motion Sensor driver that worked for me after updating the FP300 firmware.
Driver version is "2.1.3", time stamp "2026/05/29 8:43 PM"
Note, that at this time the changes are only in the multi-device driver, not in the dedicated FP300-only one. If the patches are working with this driver, hopefully the dedicated driver will be updated as well.
Use the HE inbuilt 'Device' driver to delete the old states, attributes, child devices, etc.. when switching between the two Aqara drivers.
You will need to pair the FP300 one or two more times to your hub after switching to the P1 driver. If the initialization works, the 'motion' attribute should change automatically to active/inactive, without clicking on the Refresh button.
it is working like a charm. thank you.
i do miss being able to see the configured detection ranges directly from Current States. using back this driver enables me to do that again
This driver does seem to have fixed the issue, mine with the new firmware are now responding
just to share, the device went offline by itself in the wee hours of the morning. i had to re-pair it the next day. other than that, so far so good. will have to continue monitoring for quirkiness.
The FP300 /w latest firmware going offline after some time problem is confirmed… Back to the drawing board. Finding a solution will take more time.
As warned on the dedicated driver thread - do not update the FP300 firmware for now.
Update: whoever has the latest FP300 firmware already updated, please update again manually the P1 driver - same version 2.1.3, new time stamp "2026/05/31 9:37 AM". I have changed the driver response to the ZDO cluster 0x002 (Node Descriptor Request) and added periodic syncing of the device date/time. We will know the effect after 24 hours...
Update2: Unfortunately, the device went offline after 26 hours ... 
Last breath was :
mine is still running after close to 30 hours. there had been movement (a fair bit) during the period - which could be helping to keeping the device alive?
I just saw this information regarding a possible fix for the reporting issues for Z2M. Not sure if this helps or not? Or is the same set of changes you've already made?
Issues with Aqara FP300 (latest firmware) with Zigbee2MQTT : r/smarthome
I am definitely no expert at the Zigbee low level stuff. Wish I could help more...
No, my changes are different and in the opposite direction... At the moment, I don't know which of the changes in the P1 driver have effect and which not.
I am running a Zigbee sniffer 24 hours now, hopefully it can catch what exactly happens before the 'last breath' registered message.
I am monitoring also this thread :
Update: with the previous code, the FP300 stopped sending PIR and mmWave presence updates as well.. : (
I have now implemented the explicite reporting configuration patch : driver version "2.1.3" , time stamp "2026/06/03 7:49 AM".
Will know the results after 24 hours tomorrow.
Update2 - FP300 stopped reporting again after ~24 hours ... : (
New patch attempt- re-configuring the 0xFCC0 cluster every time a ZDO Node Descriptor request is received. The results will be known after one day. Driver version "2.1.3" , time stamp "2026/06/04 7:51 AM".
Update3 - finally some hope, 24 hours boundary passed, and the occupancy is still reported automatically. However, there was an automatic hub restart at 5:34 at night (I forgot that I have a Rebooter app scheduled), which may have affected the tests.
No code changes, testing for another 24 hours period now.
Aqara P1 Motion Sensor ver. 2.1.4 2026-06-06 is available for manual update (or perform a 'Repair' from HPM) :
There are a lot of changes/added code into this driver in my attempts to find a workaround for the FP300 0.0.0_6542 not reporting occupancy. I am not sure which of all these changes were absolutely needed and which were not.
The next step is to experiment with minimal code changes to the Dedicated Aqara FP300 Presence Multi-Sensor Zigbee Driver until the same effect is achieved.
mine went unresponsive after updating to this version. after re-pairing, went unresponsive again within hours.
the earlier version “2026/06/03 7:49 AM” worked for me.
I haven’t had time to play with driver versions lately. I did however raise a support ticket with Aqara along with apparently every man and his dog.
hopefully they’ll fix their fk up!
In the past, they have stated that they do not support any integration except though the Aqara hub. Are those using their hub having the same issues?
No idea, but if they don’t want to support other platforms, they shouldn’t provide Zigbee support.
I am pretty sure Aqara provides no documentation whatsoever on how they utilize Zigbee. Thus, I believe all of their Zigbee products have to be reverse-engineered to work with other systems like Hubitat and Home Assistant. It would be really nice if Aqara would follow the Zigbee specifications fully, however they seem to like using custom Zigbee clusters, which is supported by the Zigbee specification, but makes it very challenging to use these devices reliably with any system other than Aqara’s own hubs (especially with no documentation!)
The thing is, they claim to support other platforms like HA, so they need to be more mindful of breaking changes.
Please refer to the “Hub may be required for certain ecosystems…” note above. My guess is they mean one should use an Aqara hub to integrate with third-party ecosystems. I know from my personal experience that Aqara devices work very well when paired to an Aqara M3 Hub, and then integrated to Hubitat and/or Home Assistant via the Aqara hub’s Matter Bridge functionality. Likewise, Aqara devices work very well with Apple Home using either the HomeKit or Matter protocol via their Aqara hubs.
I do wish they would not make breaking changes to their Zigbee implementation on their devices.
How well do they work directly paired to HomePod’s using matter?
I assume you’re referring to Matter over Thread Aqara devices? If so, I don’t know as I have focused most of my effort on using Aqara devices in Zigbee mode.
