I´d love to keep my environment up to date automatically, but sometimes there are breaking changes included, so I do not want to risk anything… Can we allow automatic updates for those without breaking changes, but when there are, it requires a manual confirmation you want to update?
And how would we know that?
Doesn´t the add-on updater provide that? Before updating, i always check the release notes. Typical break-fix or minor updates wouldn´t, but larger version upgrades would.
Just as an example, when looking in the Zigbee2MQTT add on (which I use). If I would have had automatic updates on, it would have stopped working as the version change required a complete transformation of the config setup in the add-on.
" # WARNING! Breaking Changes Notice
Once upgraded from 1.6.0 to 1.7.0 you cannot switch back to 1.6.0 when not having a backup of the database.db!"
The updater does not have any context of what is breaking.
The releasenotes you see is from the RELEASENOTES.md file in the add-on repo.
One could look at the version numbers, but that would require a strict version scheme (like semver), and that every add-on dev actually used it, and… yeah…
I’m not saying the request is bad, I just don’t see how it would be implemented
I see where you are coming from. I was hoping for some “discipline” from the developer in indeed versioning or indicating if there are major changes (like config update requirements) that would indicate that actions are required or potential breaking changes.
Really, for add-ons, never update automatically. Always read the changelog.
I can understand why it’s tempting to just let them auto update but since there is such risks involved.
Why not just remove the newbie trap?
It is only shown when you enable the advanced options, so I would not consider it a newbie trap.
1 Like
In that case it make no sense to me.
It’s only enabled for advanced users but in order to get the configuration checker you must enable advanced mode.
Something that is more important when you are new.
The configuration is checked on restart, there is no need to provide this seperate and overflow new users with that. However, bit off topic for this topic I guess.
Ok. Probing question… Why do we allow windows to update patches without reading the change log and don’t we recommend that for HA.
Just thought minor updates should be possible…
Unless they want to use it to learn. Like I did. It was a great tool for highlighting my early mistakes. I really don’t think hiding it helps anyone.
Not sure that is a fair comparison, based on the resources available and testing performed.
Even if all addons implemented SemVer correctly, there is also the issue that some are packaging up other software, which in turn would need to implement the same versioning scheme (these in turn may be dependent on libraries, etc etc).
Personally I would like to see the automatic update option removed 
Or at the very least have an automatic snap prior to an update, which may make more sense.