I know I can “skip” updates and keep skipping. But eventually when I want to update, it seems I must update to the very latest release. My question is - is it possible to update to an older release. Not to be confused with restoring from backup.
To make sure my question is clear here is a small summary:
My HA version - 2024.5.x
Current HA version - 2024.7.x
I want to upgrade to 2024.6.x
Is this possible?
The reason for this is probably obvious. I’ve found HA to be incredibly reliable and robust but when it does fail, the impact and disruption to my family is way too big. I’ve found that in 11+ months of using it I’ve only had one large issue but that was still disruptive enough for me to want to be on an update cadence that lags by about a month.
While I do realize this won’t eliminate all risk, it will certainly mitigate some of it since all my issues so far – whether the one large one or several small ones – would have been entirely avoided if I had upgraded a bit later. My plan is to update to the last incremental patch of each month, lagging by a full month from official releases.
P.S. I realize if everyone followed this rule, that would actually not be great for the community as no one will be experiencing and reporting bugs. I don’t have a good answer to that other than that I choose to be a NabuCasa subsriber so at least I contribute to the quality of the HA project in some way.
My pattern is to update around the last day of the month. That picks up any point releases and leaves me routinely a month behind. I actually think HA update approach is a deterrent to making HA a mainstream user tool. If that is what the developers want they will ultimately need to move to a no breaking changes between major releases that span at the very least a year. I say this as a lifelong software guy who understands the value of the current approach. But it isn’t an approach that will support the mass market user.
Last Wednesday of the month is when beta testing starts and there will be no more minor releases for the month. Unless a major security flaw is detected. But you will know about that if it happens, banners on the forum, alerts in your repairs (I think), it is advertised widely and loudly.
Set yourself a calendar notification for the Last Wednesday of every month to update. Or to come and join the beta testing
@tom_l , considering how severely disabling supervisor updates impacts eligibility for all other updates, is a decent pattern to just update supervisor on the last Wed and then pick up all the notifications for updates of other components that will come (either bringing them up to latest, or using CLI to pick specific versions from month before)?
