Had this sensor connected via Matter and worked perfectly with (only) presence detection on my Aeotec Hub V3, sometimes it had a small delay of changing status.
Then I just installed this driver for Zigbee but the presence and PIR are also slower to change their status to normal. The PIR never changes to ‘no movement’ on its own, he keeps following the presence status. Also he keeps saying it has an empty battery.
Is this a known issue?
No. See the screen recording.
Let’s wait for the next firmware update and see if these issues are fixed. We’ve seen reports in the Aqara forum and on Reddit that some devices are just faulty and must be replaced.
It doesn’t really work reliably with their own hub…
Happiness all around in this thread. Doesn’t make sense to work on this driver before the device works reliable on their own platform.
Thanks for the driver! Working well except for the battery status. I get the message “no battery” instead of percentage. Should I change some settings?
I’ll have a look at it when I have the firmware update that is currently being rolled out.
Edit: currently running it in Thread mode, because it doesn’t make a difference anyway. The issue is on the sensor side of the firmware (or even the hardware). The Aqara FP2 on the other hand uses a sensor from Texas Instruments that comes with its own firmware/SDK. Took two firmware updates until it became absolutely reliable.
Wasn’t the Zigbee firmware supposed to get much better battery life compared to the Thead mode?
Thanks, interesting thread, glad it isnt just me getting the paused status. guess i will start work on the new double socket while I wait 
I installed the latest firmware last night and re-testing with my driver. I am hoping the paused issues are resolved. Have you tested it yet?
This weekend. But I don’t expect too much…
Has anyone been able to test the new firmware release yet?
In my opinion, both the Matter/Thread firmware and the Zigbee firmware have improved slightly. I’ve now tested both versions for a week each, and I don’t see any difference in behavior.
The firmware consists of two parts in each case: the part responsible for the actual sensor and the part responsible for the protocol. The first part must be improved in the future.
However, the device behaves differently from an Aqara FP2, where you can see in real time when you enter and leave a zone. With the FP2, I can take a step to the right and the light turns on - and as soon as I take a step to the left, it turns off immediately. With the FP300, you have to wait, and sometimes you even have to hope that the light will eventually turn off after all.
I’m going to reposition my FP300 again - maybe mount it directly on the ceiling.
To form a proper opinion, it’s best to check the relevant threads on the Aqara forum and on Reddit. Some people notice a difference compared to the previous firmware, others don’t. We’ll see how it develops. That’s what happens when you run a beta test and “tech influencers” are the first to jump on it. They shoot a video, don’t really test it - and certainly don’t provide feedback. For now, I mainly use the device to keep the light on, when present and not to turn the light off.
I just ordered one. But don’t have an aqara hub is this going to effect the ability to get firmware updates?
I don’t have an Aqara hub either. Firmware update can be done by switching from Thread to Zigbee and back in the Aqara Home app.
Is there a way to disable individual features like the light or temperature sensor through the ST driver to save on battery power? Similar to how it works with the Aqara app?
Works just fine here (see Screenshot in this thread).
Delete the device, reset it, add it back again. I’ve seen reports where temporarily removing the batteries can solve this issue.
Yeah did this. In between tried to get your driver to work. It didn’t. I’m all good though. For my purposes it’s working just fine with thread.
I bought an FP300, so thank you for sharing your driver. Although it seemed to work OK, I had the problem with “no battery” being reported. I removed it from SmartThings and added it again, and also removed and replaced the batteries. This didn’t solve it, so I returned it to the retailer. It tested it using an Aqara hub and found no problem. I was using Zigbee. I don’t know what the retailer was using. Have the other reports that you have seen been using Aqara hubs, or only using SmartThings hubs?
I’m having the exact same issue with the battery level not reporting. Already tried to reset and re-add the device multiple times, but the battery level will just not show up when using the Zigbee mode.
I’ll have a look into it when I’m back home next week.
Thank you.
The retailer I bought it from has tested it using both Thread and Zigbee with an Aqara hub, and says it reports the battery correctly with both.
