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?
