Hi. I recently paired two Aqara window door sensors (same model) to the M3 Hub and ran the Check Firmware for Update feature and both came back “Up to Date”.
Except both sensors are running 2 different firmware versions.
1 sensor is on firmware 1.0.1.1.
1 sensor is on firmware 1.0.0.0.
How do I fix this so they at least both run the same firmware?
@smcalli1013 It seems like you’re experiencing a discrepancy in firmware versions between your two Aqara Door and Window Sensors (P2 model) even though the Check Firmware for Update feature indicated that both are up to date. This can occasionally happen due to various reasons such as regional firmware release schedules or temporary glitches.
Unfortunately, there isn’t specific information in the reference material about manually forcing a firmware update to unify the versions for your sensors. However, here are a few steps you can try:
Recheck for Updates: Sometimes, firmware updates might not appear immediately. Try checking for updates again after some time.
Ensure Network Stability: Make sure that your M3 Hub is connected to a stable network and that both sensors are in range.
Restart and Reconnect: Try restarting the Aqara Hub and reconnecting the sensors to see if that triggers any updates.
If these steps don’t resolve the issue, I recommend reaching out to Aqara Customer Service for more specific assistance. You can do so by opening the Aqara Home App and navigating to Profile > Help & Feedback > Customer Service. Alternatively, you can scan the QR code below for efficient support:
If you don’t have an Aqara Home account, please click here to create a ticket. Apologies for any inconvenience this may cause, and thank you for your patience!
This appears to be an issue with where you received the item or from which vendor. I didn’t get a crystal clear explain tion. Support had to connect to my HUB and grant access; and they tweaked some things to resolve this.
@smcalli1013 It sounds like you had an interesting experience with resolving the firmware version issue on your Aqara Door and Window Sensors. It’s great to hear that Aqara Support was able to remotely connect to your hub and make the necessary adjustments. This highlights the importance of having responsive customer support for troubleshooting such technical issues. Thank you for sharing your experience! It may help others who face similar challenges. If you encounter any more issues or have any tips to share, feel free to post them here. Your insights are valuable to the community!
Hello @smcalli1013
There were no new firmwares for these devices, your sensor which is on a newer firmware is probably a newer batch and it was initially updated at the manufacturer’s factory. A sensor with an older firmware cannot be updated, this can be done if the firmware becomes available in Aqara home
Aqara actually released a firmware update for the P2 door sensor, published in the Matter DCL with the OTA URL so any Matter platform could update it if they wished.
Word of mouth is it bricked devices so Aqara had to invalidate the update (software version valid = false) but never released a fixed one and just shipped new devices with the new firmware.
My understanding after these two years is that the first version of the P2 door sensor had a bug that prevents updating the firmware. That has never been confirmed by Aqara but, if that’s the case, a confirmation would be nice, and even a recall of the product would be better since none of the promised features will arrive if the product cannot be updated.
Can someone from Aqara give a definitive explanation of what happens for people who bought the sensors back when they were released to the market? Are they doomed with no updates?
Edit: Coincidentally, the new firmware release notes mentions fixing issues with the OTA updates, hinting at a problem with the updates of the original version. This is a pic taken from reddit:
I was wondering what happened to the 1.0.1.1 version and that pretty much explains it all… Looks like my sensors won’t be updated anytime soon… I hope I’m wrong
Version 1.0.2.0 is available for the sensors from version 1.0.1.1.
I’m waiting for the Support team to give me the thumbs up to hit the upgrade button.
I’m a little Sketched out doing firmware upgrades because I already bricked one going from 1.0.0.0 to 1.0.1.1 (support team did graciously RMA it).
Needless to say; if your stuck on the old batch of 1.0.0.0; I wouldn’t expect any upgrades available unless you have the support team involved/allowed them access to the M3 Hub to perform tweaks.
They really need to recall sensors with 1.0.0.0 firmware given it seems true they cannot be updated so they won’t get any of the announced features nor the security patches of recent Matter SDK versions.
I only bought one, but it’s still under warranty (3 years here) and it’s clearly a factory defect.
Do you know if they’ve enabled the push button for automations in the new version?
Now they did the same with 1.0.2.0. It appear to be discontinued too!
You’re right! 
I didn’t even checked, but Software Version Valid is indeed false!
What is going on with the P2 updates??
Looks like 1.0.2.0 still doesn’t have the announced push button functionality, but adds sensitivity adjustment! A user mentioned having issues with the sensor detecting randomly opened states after the upgrade when it’s closed. Might be a bug in the new sensitivity feature and may be why they’ve invalidated the Matter update.
Also, if this Home Assistant code is correct, then Aqara implemented the standard sensitivity attribute backwards, using 0 for the highest sensitive level (10 mm) and 2 for the least sensitive (30 mm) when it should be the other way according to the Matter 1.4 spec: sensitivity levels SHALL be ordered by sensitivity, where a value of 0 SHALL be considered the lowest sensitivity level (least sensitive). That would be another reason to invalidate it and fix the protocol conformance.
Oh. That’s explain a lot. I hope they fix it and release a new update asap.
Aqara support has been wonderful and I’m getting a replacement for my 1.0.0.0 sensor since they understood I won’t be able to get the advertised updates. Hopefully it will include at least 1.0.1.1. so I can update it through Matter… when a new valid update is published and someone confirms it’s safe to install 
.
I’m grateful to Aqara since the process was easy and fast but I still miss some official explanation, especially now that 1.0.2.0 has been invalidated. TBH I got the Aqara for the promise of the smart button, which I learned is not in 1.0.2.0, but at least should be able to update when the time comes.
I have P2 which was gifted to me from Aqara from U200 Kickstarter it is used on my Front Door.
It got the update and I tried to update it several times, but it always failed.
After 5 tries I have rebooted the M3 matter hub and now it seems that the P2 is updated to 1.0.2.0 - I can see there is a new setting: “Installation distance adjustment” which previously was not there.
Also the Add-in interface looks differently but this maybe coming from the Aqara app itself.
P.S. now I have opened another brand new P2 that I have and it is on version 1.0.1.1, but it did not find any firmware updates to update to!
It doesn’t have the setting: “Installation distance adjustment”.
Mine updated to .1 yesterday… or tried to, and now it’s a brick!!
