Is there a way to auto update to latest dot version of a previous release? IE - I want to avoid going through the dot versions that get released so instead update to the latest version of the last release. So when 22.8.0 comes out it would automatically update to 22.7.7
As of Supervisor 2022.8.5 it seems we can now disable auto updates.
I went to Developer Tools > States and selected the update.home_assistant_supervisor_update entity, and changes the auto_update attribute to false.
Hopefully this works, and I can update manually once I confirm the update won’t have any major conflicts with my addons/integrations.
That is… Not how that works. Updating the state of entities in dev tools is just for testing, it doesn’t change anything except the state of that entity. At least until the integration updates it state again with what the value is supposed to be. I would guess if you looked again you’ll see that attribute is true again.
However you are correct that you can disable automatic updates for supervisor now. To actually do that you need to enter this in the cli:
ha supervisor options --auto-update=false
Note that while supervisor is out of date nothing else can be updated. It also won’t even check for updates to addons as just reading in their config can break things if they are expecting the latest supervisor features. You also cannot install new addons or add new addon repositories.
In addition your system will be considered unsupported while supervisor is out of date as only the latest version is supported. Wanted to make sure you weren’t surprised by any of these restrictions before you changed it.
4 Likes
So that’s the reason for the auto update,
still I can imagine some smart mechanism not breaking stuff while the supervisor is out of date,
for me there seems to be some kind of contradiction,
for haos and ha core, please read through all changes before installing because you might break something and then the supervisor is just pushed whether the time suits me or not.
On the other hand, this update has never broken anything for me, still a little more consideration would be nice.
I need 2022.8.5 to use this command? Can I use this on an older version?
If you’re referring to the command in my post it came out in 2022.08.4 of supervisor. And you definitely have it because supervisor auto-updated for everyone with no ability to turn that off prior to that release.
What version of core you are on (I assume that’s what you’re referring to) does not affect what commands are available in the CLI.
Is there any way to stop all update checks/notifications entirely? They’re not an issue for my own personal systems/spaces, but deploying this for a customer, neither of us can afford the annoyance of the update checks and notifications. In such a situation I’d manually handle updating once or twice per calendar year or at any other scheduled maintenance such as when adding new hardware.
No, there’s not. If the icon in the sidebar really bothers you though you could edit each of the update entities and disable them.
1 Like
That might be too much maintenance (moving targets, things missed) and instead it’s looking like locking them out of the HA web UI and app is the better move, relying strictly on Apple Home for their interaction.
Or set them up with a user account rather then an admin one. User accounts don’t see update notifications or the entire settings panel when they log in.
1 Like
Now THAT’s a tip I can use! Thanks for the suggestion. I’d honestly forgotten completely that HA even had the capability of different user access.
1 Like