Monthly core releases, plus core updates: 7 in september, already 3 on 11th for October, plus supervisor and addon updates.
For example : three in four days on 11, 13 and 14 september.
I globally understand that major releases add features, and minor correct bugs, and I am very happy to see all that work to make HA better and better. This shows the momentum of our project, and I want to be clear, I far prefer too much updates than no updates !
But I dont want to spend more time checking HA status than checking my home !
This gives me an insecurity feeling. Should I just ignore minor releases notifications ? I hate to let these notifications pending …
I suggest to group minor releases in some fixed dates in the month (patch tuesday style).
Developers, would that hinder your work ? What do you think about that ?
today’s solution: update y to the previous major version. For example today update to 2022.9.last
otherwise consider voting on WTH below. Imo it may improve reliability thus limit number of fixes. granted it could however increase number of separate updates.
I don’t think the other WTH is a good substitute for the problem at hand. I too dislike all the updates. I wouldn’t mind having a setting in the update section to only get the last stable version or something like it.
There’s a “skip” option when you pull up an update from the notification. Then you won’t see that notification again.
I prefer to stay current, but I can’t commit the time to researching the impact of all the changes, backing up, making the update, and doing testing, every time there’s an update.
I do one update a month, after all the changes have settled down, usually after the third week of the month.
If you read the linked WTF above you’ll see how any suggestion to re-consider the update process gets a lot of push-back from the devs. As much as I believe there’s got to be a better way, they are the ones whose opinion counts here.
hm… I don’t agree with the statement from the TO
Checking for updates is at least a thing that forces you to navigate through your HA System… (while everything is running smoothly in the background and automated )
You can skip minor updates using an automation + the update entity and parsing the version string. Slightly hacky solution, but I think a lot of people have different needs for how often they want to update. I personally just auto-update most things.
automation:
- alias: Update only to last stable
trigger:
platform: state
entity_id: update.home_assistant_core_update
attribute: latest_version
to:
condition: >-
{{ trigger.to_state.attributes.latest_version | version
> trigger.to_state.attributes.installed_version | version }}"
action:
if: "{{ version(trigger.to_state.attributes.latest_version).major }}"
then:
alias: Update HA (HA has gone to a new major version)
service: update.install
data:
version: "{{ trigger.from_state.attributes.latest_version }}"
entity_id: "{{ trigger.entity_id }}"
backup: true
else:
alias: Skip it (not the last one of the month)
service: update.skip
data:
entity_id: "{{ trigger.entity_id }}"
Just replace update.home_assistant_core_update with whatever entity ID you choose for the core update entity. Basically when a new major version comes out then it updates to release that preceeded it (i.e. the last stable version of the prior month).
I made the automation auto-update but it could just as easily send a notification about the update if you don’t want to do that. Just replace the update.install bit with a call to the notification service of your choice. Might want to send a notification action that triggers the update though since actually clicking “update” will update to the first version of the new month. Will have to enter the correct version in a call to update.install in dev tools (or have a notification action that just does the right thing with an automation when pressed).
Although I should probably note that as written this automation will only work on >= 2022.10 as it relies on the new version filter. To make it work on 2022.9 you’d have to replace the version stuff with string parsing to find the two months and compare them.
The update pace is dizzying and requires some effort for users to keep pace
The HA team is incredibly responsive and new features are awesome!
Is it possible to do something like the Ubuntu Long Term support plan?
Decide on a stable release schedule (yearly, 2 years. Pick a cycle that works)
The LTS branch gets only non breaking security updates as needed
new features continue in the active release branch
If users want a particular new feature or fix, they can always move to the active branch, but cannot go back to the LTS branch until the next LTS cycle.
I would Upvote the downvote possibility.
I don’t have any opinion on this topic, but I believe a downvote is a good tool with WTH (and feature requests in general).
The way we have it now is we can either like the WTH or not.
Not liking, not seeing and outright hating it are all clumped together as “don’t vote”.
bad idea bro
you aren’t inventing anything new. I saw it few times and always have been removed. the ideas were being burried down by people who did have no expertize or just didn’t need particular change (haters aside).
I can also feel a bit stressed of the orange number next to settings, and the list of new updates on top of the settings menu. I have a suggestion of a opt in/out UI feature, “show all updates”.
If you have it off:
The orange number on the side bar only show for major releases and security updates. At a major release or a security update everything behaves as normal.
But when you have the latest major installed:
Instead of a large list of add-ons/core/os/etc releases on top of the settings menu, if you have updated, it is only a thin banner with a menu option like “Look for updates”, something that feels less urget.
Note: I would probably have this turned off because I like to install all uppdates all of the time, but I recognize the feeling of stress that it adds. (I updated less frequently when I ran it in a docker container and did not had this reminder)
You don’t have to update every time there is an update available.
the major release is the only release that offers updated functionality. If you want that functionality then you update to the new major release.
But the newest release can come with bugs. If you are OK with taking that risk then update to the .0 release. If not then wait a few .x releases for the bugs to get worked out then update. that’s what I do.
then update one time. You don’t need to update to any further .x releases because it adds no additional functionality and assuming there is no bug fix that you need you gain absolutely no benefit at all from further updates.
I update one time a month. If there is a bug I roll back to my previous working version and wait for that bug to get fixed and then update once more. If everything works then that’s it. Whether there are updates everyday after that or not I never update again until the next stable (moderately bug free) major release.
Very well said… and update strategy is a personal thing… some people want to keep the system always updated to the latest patch, while other people would like more to keep on the safe side and only install more stable updates. Both have advantages and disadvantages, so you have to choose yourself.
I’m on the first group, so I use this blueprint to keep everything always updated, regardless the risk involved on that.
If you are in the other group, this automation suggested by @CentralCommand may be the right direction for you.
It’s not some much about when to update or have it update automatically. It’s more about the notification and when to get a notification. You want a system which is always up to date and have it auto update alle the time so you don’t see the notification. But for people like me who have a system which needs to be stable more then being up to date, we have a constant orange notification which is annoying and distracting from other more important notifications. We like to be able to at least choose which update we get notified for.
An option for me could be that notifications for updates deliver a green badge and more important notifications from the system an orange badge. That way I can at least see the difference.
A patch will include a fix for something. Maybe it’s not related to your system at all, so it’s fine if you don’t apply that patch, but many times it could be related to something that you haven’t noticed yet, but could be causing some damage or risk to your system, so you probably should apply the patch.
Updates are there not only to add functionalities.
It won’t because I don’t think automations are meant for this. And another thing is that I don’t do automations with templates or Jinja. That’s a personal choice I know. But i think this WTH could easily be a choice in settings.
!