PS: I know nothing about creating/testing Edge drivers. I’m happy to help if I can, but you’ll need to explain step-by-step how I can help!
You can try mine, I need to clean up my repo at some point, but been using these with no issues yet https://bestow-regional.api.smartthings.com/invite/VbMbe5PgWjB8
Thanks, I’ll try it soon. I’ve noticed that the sensor detects motion every hour or two when nobody is in the house. A motion sensor in the same room doesn’t detect any motion at the same time. I’ve bought another FP300, so will see what happens with that.
Your driver seems to work fine for me so far. There’s even an option to independently disable the temperature and humidity sensors. @Andreas_Roedl Could you maybe integrate that as well?
Just a quick update: I can replicate the “no battery” issue. All I have to do is delete and add the device often enough until the firmware thinks that it doesn’t have a battery! I was wondering what you guys were talking about, but while working on the next version of the driver, it happened to me.
It is not a driver issue; it’s a device issue.
Thanks for looking into the battery problem. I don’t think that your explanation explains my problem because:
-
It happened the first time I added the device. Unless somebody at Aqara has added and removed it many times before supplying it, of course!
-
The supplier tested the FP300 itself and found the battery reporting OK.
Once you experienced the problem, did you find removing and replacing the batteries as you mentioned before solved it?
I don’t have to explain anything - especially not this weird device.
Here’s what happened just a few minutes ago while adding the device:
Deleted and added the device:
Same driver, of course - the one I’m currently working on. Maybe a timing issue.
This isn’t the only weird behavior. I can let the device go offline when using @Blackduke ‘s driver and writing certain attributes by changing the preferences.
Also interesting: I was on a work trip for four weeks and a couple of days in, the device - in Thread mode - went offline. Came home, didn’t want to deal with it and out of nowhere it came back online. Weeks later, without intervention.
It has its quirks. I also think my detections have slowed down. I think with the updated firmware, I might start again, as I did a lot of messing around. I do like the device, though.
I have tested your driver for only an hour or so and while doing so, I just had a glance at the logs. There’s a reason why I omitted some of the fancier settings in the first version of my driver.
The most annoying part of developing a driver for this device is the testing. I often let it rest for a while, because I think it needs to re-learn the room.
Released an update:
───────────────────────────────────────────────────
Driver Id f918d83c-f5b6-44f3-b05f-c0a64118c845
Name Aqara FP300 Presence Sensor
Package Key aqara-fp300
Version 2026-03-31T15:12:07.916878249
───────────────────────────────────────────────────
I’m really sorry for phrasing my reply badly and sounding like I expected you to explain my problems. That definitely wasn’t my intention and I will try to phrase things better in the future.
Thank you both for your help and for publishing your drivers.
Have you tried the latest version of my driver?
Now I understand what you mean. What I was trying to say is that this seems to happen randomly when the device is added. I had to delete, reset, and add the device back to the same driver several times before I was able to reproduce the issue. When it did happen, the next delete-reset-add cycle fixed it.
It feels a bit like a timing issue, so I’m keeping an eye on it.
Have you tried the latest version of my driver? For Zigbee devices in general, it’s really important to delete, reset, and add the device again after (certain) driver updates. The device is configured when it’s added.
Thank you again for your help.
I tried deleting and adding the device several times, but didn’t reset it in-between. Having said that, I removed the batteries, and the seller changed between Zigbee and Thread, so that probably reset it.
I haven’t checked how it works with your new driver. If I understand drivers correctly, they’re updated automatically. I will follow your advice of removing, resetting, and adding it again.
When you delete the device in the SmartThings app, it should automatically go into pairing mode, but sometimes not. You should wait about one minute, before you press and hold the button until the LED starts to flash blue. Sometimes you’ll have to try it a couple of times.
See how flaky this device is? Good luck.
I haven’t removed and added the FP300 yet, but it must be using your new driver now because it’s showing the battery level now. It still incorrectly detects motion every couple of hours. I’ve changed the motion sensitivity (presence detection sensitivity) to low and disabled detection over 3 metres, but this hasn’t helped. I’ll try enabling the AI features…….
I might keep one FP300 for the bathroom and buy the previous powered version for other rooms because it seems less flakey.
Thanks again for all your help.
Same here. Works well enough now with the default settings of my driver. I’ll keep the device in Zigbee mode, because in Thread mode it randomly went offline. Hopefully, they’ll fix it in the next firmware update.
I have added a huge section about the battery issue to my original post - might be interesting for you.
Thanks for your help, your driver, and all the information in your updated post. Sorry for my tardiness in replying.
PSA: To change some of the settings you have to press the physical button on the device first. Only works sometimes in the Aqara Home app …
Might that be the reason why the device is still giving me temperature and light readings even though I’ve set those to off in the settings?
Who knows? I’m not the developer of the device’s firmware.