Hub or devices that include hub functionality, such as Hub M3, Camera Hub G3, Panel Hub S1 Plus, etc. These devices are usually connected to the network through WiFi. As they need to support new device access and control, the firmware update frequency is high, and a new version is usually released every 2-3 weeks.
Traditional Zigbee protocol child device for Aqara, which typically has simple functionality and does not require frequent firmware updates without functional bugs.
Some new products launched by Aqara (such as sub devices that support Zigbee/Thread dual protocols, or innovative products like FP2), due to their complex functionality or compatibility with Matter being still in the exploration stage, usually have more software bugs in the early stages, and the firmware update frequency will be higher. Once the functionality is stable, their firmware update frequency will decrease.
The firmware release rule explanation: After the new firmware passes the test, a certain proportion of users worldwide will be randomly selected for grayscale upgrade (usually 30%, with a duration of 3 days to a week, in order to prevent unknown bugs from causing widespread device paralysis). Only when there is no problem feedback for grayscale upgrade, will the new firmware be pushed to all users. This is also the reason why some users may see that their devices receive firmware updates later than others.
@Aqara_PM_Donie Thanks for sharing this information. Itâs all logical and really makes sense.
However in my case, I migrated from the M2 to M3 hub just to be able to adjust the delay settings for the Aqara Motion and Light Sensor P2. In other words, I bought a new hub just to get this specific capability. The motion sensors are currently on version v1.0.2.0 and the app reports this as the latest. Research indicated the latest is v1.0.3.0 that should provide the capability. The M3 is on FW v4.3.8_0021 again reports are the latest. How can I get the P2 v1.0.3.0 firmware? The standard process that you describe doesnât indicate how someone that needs a specific version can get it outside the standard process. Is my only option to wait until somethings triggers on the Aqara side to download the update? Thanks and keep up the good work at Aqara.
Interesting, great to see how that process worksâŚ
Are there any plans to support third party Matter firmware updates, through the MainDCL network? I currently keep a HA instance just for that and even that is very buggy to update devices. Apple home also supports that but the updates arrive very late for any devices. Having this feature in Aqara Home would help to simplify my smart home setup and management.
I second offering updates through smart home platforms thanks to Matter OTA. Looks like some are offered, although I have a P2 door sensor and all the updates have been marked invalid so it cannot be updated, not from 1.0.0.0 and not from 1.0.1.1.
@Aqara_PM_Donie SmartThings for instance supports Matter OTA but apparently only for certain partners. Iâve asked them to see if they could add the P2 motion sensor in the allow list but havenât received any answer, maybe you, as in Aqara, can make it happen.
Didnât quite get the point of the screenshot. The P2 motion sensor can be updated with the Aqara app and with Home Assistant since the firmware URL is published and has not been invalidated like happened with the P2 door sensor.
AFAIK it cannot be updated with SmartThings. And the door sensor cannot be updated with any Matter platform because all the available firmwares for Matter have been invalidated in the Matter ârepositoryâ (the DCL).
Thank you for sharing. Itâs great to get a peek into how these things work. I love how Aqara works not only to innovate but also to be as transparent as possible in how things are done.
The screenshotâs point is that Matter platforms support Matter OTA.
Including HK, and if the firmware updates for the opening sensor were recalled, there were reasons for that.
Indeed, some Matter platforms support Matter OTA of Aqara devices, that was already stated and Iâm glad Aqara is publishing the Matter firmwares and also working directly with platforms to offer them so an Aqara hub is not required.
Thatâs why I was requesting to figure out what happens with SmartThings given that Aqara is a Works With SmartThings partner and their products are WWST certified.
Thatâs a really good explanation, thanks for sharing it. It might actually make sense to consider updating all devices under the same account at the same time. If two M3 hubs end up running different firmware versions, thereâs a small chance it could cause some inconsistencies, especially with Matter or multi-hub setups.
Maybe synchronizing the firmware rollout per account would help avoid those edge cases where one hub is already on a new build while another one is still waiting for the grayscale update. Something you might want to consider for future updates.
