[ST Edge] Aqara FP300 (Zigbee)

Devices & Integrations Community Created Drivers
63

After updating the Zigbee firmware to the latest build 0.0.0_6542, motion and presence detection is no longer working properly with my ST hub. However, when I pair the sensor to an Aqara hub, everything works as intended. Did they change something in the firmware that makes the ST device driver not work anymore? Did anyone else noticed this change in behavior?

64

I can test it later today tomorrow.

65

Can confirm: it’s broken. Awesome!

I’ll have to find out what has changed in the latest firmware version. In the meantime, switch to Matter.

Nothing regarding motion or presence is coming from the device anymore - no Zigbee messages at all… Let’s wait and see if this is accidental or intentional.

66

It’s broken in Hubitat too … :frowning:

67

… and other platforms: Aqara, Aqara, …

Reminds me that I also have an Aqara hub (that wants to be a Matter camera) and I could test the device with that.

68

Fixed version:

───────────────────────────────────────────────────
 Driver Id    22ab5410-84cd-46c3-8c76-1e675850e5a7 
 Name         Aqara FP300 Presence Sensor          
 Package Key  aqara-fp300-presence-sensor          
 Version      2026-06-01T23:11:42.60575408         
───────────────────────────────────────────────────

ScreenRecording20260602010735SmartThings-ezgif.com-video-to-webp-converter

This Reddit comment was extremely helpful!

Hi everyone! Just wanted to chime in to say that I faced this exact same issue on what turned out to be a very frustrating afternoon: purchased an FP300, switched to latest zigbee firmware from aqara app, then paired to Z2M network. I noticed the exact same symptoms as OP with occupancy states not auto-reporting and “sticking” until refresh pressed manually (and even that worked only for 5-10 mins after pairing, afterwards that would stop working too). Initially I thought I had a defective unit, did all the usual troubleshooting, but to avail. After digging a bit deeper in the docs and in the Z2M logs, I think I found the root cause.

The clue was that the FP300 was not autonomously reporting the proprietary Lumi presence/PIR attributes, but since manual reads worked (and temp and humidity were actually working as expected), it looked like reports were not configured properly by Z2M for this particular firmware version when setting up the device upon joining.

My workaround is a custom Zigbee2MQTT external converter which binds manuSpecificLumi and manually configures reporting for 0x0142 / 322 (presence) and 0x014d / 333 (PIR detection) which are the two “stuck” readings.

After restarting Z2M and re-pairing/reconfiguring the FP300, it started sending real attributeReport messages and presence has been stable and flawless for the last couple of days.

So for everyone having this issue, my suggestion is to skip all the usual troubleshooting steps (device placement, firmware re-flash, etc), and to check the Z2M logs for attributeReport, cluster manuSpecificLumi, and data containing 322 or 333 to confirm the issue.

@TOMillr

69

Thanks, I’ll give it a try once the update is published. My driver is still on the version of March 31th at the moment.

70

Delete the device from SmartThings, delete and re-install the driver from this channel, add the device.

Takes 5 minutes. Did the same a couple of minutes ago to test the very latest version that tries to interpret the battery value correctly.

12? What do you mean? 12 %? 12 mV? 12 as in 0 or 1 is empty and 12 is full? Nobody knows - not even ZHA or Z2M. The raw value 12 means “full” in the Aqara Home app.

71

@Andreas_Roedl add a new updates from your testing? Has it improved with matter? Or buy it and stick with your your driver?

Thanks

Dom

72

Both firmwares are much more reliable now. Use my Zigbee driver if you need the features, otherwise use the Matter firmware.

73

I can also confirm that the new firmware is more reliable compared to the previous version. The fixed driver version by @Andreas_Roedl is also working again. :+1:

74

Is their any feature that isnt in matter but in zigbee? I thought it was something the multiple zones or presence? I only have 1 matter sensor, eve and that only does motion.

75

Read the product page first and then my original post. This should answer all of your questions.

76

Hi @Andreas_Roedl

I’ve been using it for a few days and its driver is quite consistent. I noticed that the lux range is a little lower than other Tuya devices I have - but no problem.

Now, I still don’t understand how to use the target distance setting.

I enabled it, in configuration, but it always shows 0.50m - could you explain how to use it better?

77

And lower than the FP2.

Now, I still don’t understand how to use the target distance setting.

I enabled it, in configuration, but it always shows 0.50m - could you explain how to use it better?

Even in their own ecosystem / app, you have to press the button on the device when changing certain settings.

See here: