A G410 owner recently asked what changed in an offered firmware version because they couldn’t find release notes. For devices that affect notifications or access, I’d like to know what behavior is expected to change before installing an update.
A useful note would name the affected models and versions, fixes and new features, known issues or prerequisites, rollout regions, and checks to perform afterward. If rollback isn’t supported, stating that would also help set expectations. What details do you look for before updating, and where do you find reliable Aqara firmware notes?
Hey James,
This is a request that comes up all the time around here!
Technically, when you do the update directly through the Aqara app, the release notes are always displayed on the screen before you install. The catch? They are usually incredibly vague. Nine times out of ten, you will just see something super generic like “Optimize device-related functions” or “Fix known issues”.
We have been asking Aqara for detailed changelogs for a very long time now. Until they start giving us the specifics, a lot of us just wait a few days to see if anyone else on the forum breaks their setup first, or we just cross our fingers and hit update!
Sometimes the update just includes some technical changes (aka cosmetic changes in code, which make the maintenance easier in the future for the devs) or security fixes.
The thing is, in this case, you cannot easily describe what was changed without disclosing some information about the underlying implementation or security features. It would either:
confuse the users (and scare some of them), which will hurt the PR (it’s not easily fixable, once people think you’re bad, they don’t want to come back),
confuse the user in a way that it will discourage the update,
or just leak some info that will affect/hurt the security measures related to IoT, your account.
Some fixes are sometimes made for maintenance reasons. It don’t change anything from the perspective of the user, but for example, make it clearer for the dev what the device did when the device malfunctions (and you need the support to diagnose and fix it).
And some fixes are just made there based on a theoretical situations that could happen if the code did X, but it currently doesn’t do X, but some dev could make it do X and then we will brick the device. It’s actually pretty hard to explain, but in simple words - a fix like this also changes nothing, but greatly reduces the risk of bricking your device in the future as a side effect.
But imagine a changelog with even a fragment of what I wrote. Could you imagine how confused or scared would the non-technical, I-just-want-to-turn-it-on-and-forget users?
You can let me know which specific firmware version of the G410 has unclear documentation. I review the release notes for all Aqara Cameras for every firmware rollout. At times, I rephrase highly technical descriptions to make them easier for general users to understand. Other Aqara products may vary due to different product managers’ management styles, but my requirement is that update notes for cameras must be clear and accurate.
I must admit - I give them a cursory glance if I even see them. I believe I have auto update on as everything has been at the latest firmware every time I’ve checked
The G410 owner who prompted this question reported firmware 4.5.80_0002.0108 in this thread. They said they couldn’t find official release notes for that version. I can’t verify their device or rollout region, but a link to the relevant camera release notes or the canonical place to check them would help.