Does Aqara provide OTA firmware updates via 3rd party products like Home Assistant? If not, is there a chance they will start doing this? With the still quickly evolving standard, I feel this is a mandatory feature, as each new version adds functionalities that most devices already expose via ZigBee
3 Likes
This works for most devices via Zigbee2MQTT. I’m not sure if it’s possible for all of them.
Check for your specific devices at:
1 Like
Aqara doesn’t publish the URLs of firmware updates so it relies on community members manually extracting the URLs during an update process and submitting the firmware images to public repositories.
4 Likes
Thank yo that is to bad.
2 Likes
Are you only interested in Zigbee?
For Matter, there is a directory called the Distributed Compliance Ledger (DCL), which contains all official information about devices. Manufacturers can store software update details (links and checksums) there. Home Assistant checks the ledger, finds the secure path, and then downloads the update directly from the manufacturer.
The URLs for the firmware provided by the manufacturer can be viewed publicly at: Distributed Compliance Ledger
1 Like
Im actually more interested in matter over tbread. Should have probably mentioned that 
2 Likes
you can’t update 3rd party matter devices in aqara, not supported
2 Likes
That’s good to know 
In answer to your specific question:
Yes, Aqara provides a link to the firmware update in the Distributed Compliance Ledger (DCL) for certain Matter devices. In this case, you can update the device via Home Assistant.
I have upgraded my Aqara P2 Motion Sensor (Matter over Thread) to version 1.0.3 in Home Assistant. However, this update has now been marked as invalid and Home Assistant no longer downloads it.
A link to the firmware for the W100 was also provided, for example. While there is an entry in the DCL for the P100 sensor, no firmware information was included. It therefore depends on whether Aqara has stored the firmware information in the DCL.
1 Like
Why was it marked as invalid. Did they generally pull the firmware release back?
I’m just taking a guess here, but when you read about other people having faulty sensors after the update, it seems likely that this is probably the cause.
Here’s an example from Robert Coletti:
So, versions 1.0.2.0 and 1.0.3.0 of the P2 motion sensor and 1.0.1.1 and 1.0.2.0 for the P2 door & window sensor have been revoked, and the following statement has been issued to users by support:
1 Like