when will realese firmware update to change motion time interval is 1 minute below ?
@Aqara_water Thank you for reaching out with your question about the Aqara Motion and Light Sensor P2. Based on the current information available, the motion time interval for this sensor is set at a minimum of 1 minute, as stated in the reference here. Unfortunately, there isn’t any specific information about a firmware update that would allow you to set the motion time interval to less than one minute.
I understand this might not be the answer you were hoping for, but rest assured, the Aqara team is continuously working on enhancing device functionalities based on user feedback. I encourage you to keep an eye on official updates or participate in community discussions for any future developments. If you have further questions or insights, feel free to share them here!
1 Like
In my opinion there will be no firmware update for P2.
1 Like
Not alone it is not possible to set the interval, it is not either possible to set sensitivity or detection angle even though its in the promotional material.
Unfortunately this sensor far underperform the promised specs on all fronts.
1 Like
Found this post on the Aqara subreddit confirming an August 2025 firmware update for the P2 motion-lux sensor.
https://www.reddit.com/r/Aqara/comments/1mw46n5/p2_motion_sensor_firmware_update/
How can this update be applied without using an Aqara hub? I have several P2 motion-lux sensors that I am using via Apple Home but I can’t seem to find a way to update without first linking the P2s to an Aqara hub.
Probably using Home Assistant since Aqara has published the Matter OTA URL. For that you can launch a virtual machine, “share” the device to HA, update it and then you may even remove it from HA so it doesn’t waste extra battery life trying to communicate to two Matter controllers. A bit cumbersome but doable.
Would be nice to know if the update is available in other platforms like Google Home or SmartThings too.
Also, for integration purposes, what are the new attributes and supported values they’ve added?
1 Like
Interesting, I noticed a few days back HA showed firmware updates for my P2 sensors and when I checked the Aqara app it showed nothing available and still on an older build. So I updated them all using HA and when done went back into the Aqara app and they did reflect the updated firmware. I guess I just let it go and didn’t think much more about it. I do see now I can change the “Absence Delay Time” which I don’t recall if it was always an option or if it’s new? I’ve never dug into needing to change that setting.
Does anyone know if that’s new or has it always been an option?
Yes, the new features are indeed the Sensitivity and the Absence Delay Timer.
Those should also be available through Matter platforms since they’re presumably standard attributes but so far I believe none provides the user interface to change them.
1 Like
Yep saw that. Anyway thanks for sharing in forum.
I’ve got a Motion and Light Sensor P2 and I’m confused about the firmware version available. When I look in the Aqara app under “Firmware Version” I get “Your firmware is up to date. Current firmware version 1.0.2.0”. But in HomeAssistant where I’ve integrated this, it’s indicating that there’s an update available: 1.0.3.0.
Which one is right?
Aqara controls the distribution (rollout) of the updates through their hub so it’s gradual, may halt it if they detect something and then resume it, so the latest firmware is not available for everybody at the same time.
Home Assistant access the so called Matter DCL where vendors can publish the firmware update files for certified firmware versions so the platform can apply them: everybody sees the latest firmware. Well, unless they invalidate it like happened with the P2 door sensor twice (1.0.1.1 because it bricked devices and 1.0.2.0 because, I believe, reported wrong states) which now cannot be updated from Matter, only with Aqara hubs and only if it appears for your account.
1 Like
Just quick update, I believe Aqara I just pushing this new firmware to some selected users only, still pending LoL
We are in 2026 still no updates @aqara smart automation were meant to saving electricity life easy but since using these sensors for light automation, I have to manually turn off light… lol cause interval time is 1 minutes LoL and can’t change.
Still stuck on 1.0.2.0. As much as I like Aqara stuff, the purchase of this P2 has really made me feel betrayed.
I contacted support via email and they ended up installing the newer firmware 1.0.3.0 on three of my P2’s. Now all of them are running the same 1.0.3.0 update.
Aqara needs to release it for everyone, the updated features are kind of a big deal.
1 Like
After a year and a half of owning it, I still get aggravated every time I open the app and don’t see an update.
Bad news regarding 1.0.3.0, the firmware has been invalidated in the official Matter DCL which is where other platforms check for the updates, meaning Aqara considers it is bogus and should not be updated.
It’s a deja-vu because the same happened to the P2 door sensor, which is even worse since all the firmware updates are currently invalidated in Matter DCL.
1 Like
I have 3 of those and it’s why I never installed them and kept the old ones in place. I WAS hoping they would fix any issue and reissue an updated firmware at some point.
So much time has passed that there are better options available for door sensors now. It would be nice to know what Aqara is/was thinking?
I don’t need a drawer of unused devices still in the box.
1 Like
I was one of the early adopters and got the P2 door sensor on release back in July 2023. The advertised firmware update to support automations with the push button was enticing but, as we all know, never arrived and we are on the way to 3 years. I got a replacement from Aqara with a more recent firmware but that doesn’t include the push button feature either.
It was one of the first Matter over Thread devices so I’ll give them that, things not always go as planned. I had hopes the P2 motion sensor would be different but seeing this thread it seems it’s not the case.