I added additional Motion and Light Sensor P2 sensors the other day and I noticed they are all running firmware 1.0.2.0 with no update available.
My other P2 sensors are all running 1.0.3.0. with updated menus and features (sensitivity settings & Absence Delay Timers). Two days have past and still no firmware updates available.
Does anyone know how to force an update? Those features are kind of a big deal.
I updated my P2 using Home Assistant.
Recently, I had the idea of temporarily activating the āBeta Version Updateā option in āMore Settingsā. I then disabled āAutomatic Updateā. However, I canāt try this out now because my P2s are already up to date. I had hoped to force the G5 Camera Hub update this way, but unfortunately it didnāt work. Perhaps it will work for you.
I thought about Home Assistant too but it shows up to date (which itās not) and no update available. Iāve had Apple Home show updates before and it shows no update either.
The new sensors work just fine I just want the additional features/options.
So Iām back to the original Q:
I actually just checked the Distributed Compliance Ledger (DCL) regarding this issue.
For firmware version 1.0.3.0, the status āSoftware Version Validā is currently set to false.
This explains why the update isnāt showing up for the sensors. Matter platforms like Home Assistant or Apple Home verify this ledger before offering an update. Since the version is flagged as invalid (either it was pulled due to bugs or hasnāt been fully certified for OTA yet), these platforms are strictly blocking the update.
Does this mean Aqara has their server turned off or on some goofy schedule?
No, it is not a server outage or a scheduling issue.
I was actually able to manually download the .ota file from their server, so the infrastructure itself is definitely online and working.
The āValid: Falseā status in the DCL is a deliberate āflagā set by Aqara. Think of the DCL as a public safety catalog for Matter devices. Even if the firmware file is technically still on their server, Aqara has updated the catalog to say āDo not install this.ā
By setting this to false, they have effectively engaged a kill switch for the update. This confirms they intentionally pulled the version, likely due to bugs found.
I am a software developer myself, and this looks like a standard āstaged rolloutā procedure. We usually release updates in waves to small groups first. If Aqara receives error reports (telemetry) from users, they can make the decision to stop the rollout. In my opinion, this is the most likely explanation.
