this post was submitted on 23 Feb 2025
51 points (100.0% liked)

homeassistant

13032 readers
138 users here now

Home Assistant is open source home automation that puts local control and privacy first. Powered by a worldwide community of tinkerers and DIY enthusiasts. Perfect to run on a Raspberry Pi or a local server. Available for free at home-assistant.io

founded 2 years ago
MODERATORS
[email protected]
[email protected]
51
Upgrading from an ancient version of Home Assistant (images2.imgbox.com)
submitted 1 week ago by [email protected] to c/[email protected]
20 comments fedilink hide all child comments
 

Trying to upgrade from a 2021 release to the latest one, absolutely no idea whether this will work or not...

Originally I abandoned this install because the API I used to integrate a DIY addressable LED strip (controlled by a media player entity, changed colour to match the cover art) was removed and replaced with something else, and I didn't have time to redevelop it.

For a while its been possible to do something pretty similar with WLED - at that point I was just putting off the upgrades to not break anything πŸ˜…

At this point it's probably a better idea to re-install but let's see how this goes!

top 20 comments
sorted by: hot top controversial new old
[–] [email protected] 26 points 1 week ago (2 children)

Do a backup first, if the update does go south the backup might apply to a new install

[–] jws_shadotak 6 points 1 week ago (1 children)

That's what I just did with pihole v6 lol.

Updated, internet went down and WebUI bork. Uninstalled, wiped config, reinstalled, restored backup.

[–] [email protected] 1 points 1 week ago (1 children)

Same for me but I managed to rescue the existing installation, but unfortunately my reverse proxy for the web interface doesn't work anymore.

[–] [email protected] 3 points 1 week ago

On the plus side, if the update works there is a good automated backup system now, so it won't be an issue again, I suppose.

[–] [email protected] 17 points 1 week ago (2 children)

That's going to be a LOT of reading breaking changes.

[–] [email protected] 1 points 2 days ago (1 children)

That’s all I could think of. So many changes and things to repair

[–] [email protected] 2 points 2 days ago

Honestly probably better to start from scratch. Backup yaml automations and scripts outside of Home Assistant and start over.

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago) (1 children)

Read breaking changes? People don't accidentally hit update as they see the bold BREAKING CHANGE then deal with the consequences of their actions for the next 20-30 minutes?

[–] [email protected] 4 points 1 week ago

The only reason I update Home Assistant monthly is so I'm never in the position to have to read more than one months worth of breaking changes.

[–] [email protected] 8 points 1 week ago

make a backup, but yeah maybe just reinstall lmao. good luck!

[–] [email protected] 5 points 1 week ago (1 children)

Well how did it go?

[–] [email protected] 3 points 1 week ago* (last edited 1 week ago) (1 children)

Still going πŸ˜… database migration has been running for 21 hours so far lol.

Screenshot spoiler![https://images2.imgbox.com/01/e4/lXcuc2ox_o.png](Screenshot of database migration message)

Everything has gone smoothly so far. Spent two hours looking through all the release notes and have a loooong list of stuff to sort out as soon as it completes 🀞

Edit: fix spoiler

[–] [email protected] 2 points 1 week ago

Good luck!

[–] [email protected] 5 points 1 week ago (1 children)

Uh, good luck! It's giving me cold sweats just looking at that version disparity!

If it were me I'd be looking at doing some intermediate upgrades to help it along, if that's even possible. But hey, it might work, please report back!

[–] [email protected] 2 points 1 week ago (1 children)

It's possible from the command line. And how I will do this when I'm eventually forced to.

[–] [email protected] 1 points 1 week ago (1 children)

Oh no πŸ˜‚πŸ˜‚ what version are you on now?

I remember a looong while ago when I broke my virtualized install by trying to update with too little virtual disk space, had to expand it and manually install the latest core from a shell within the VM. On another occasion the sqlite database completely filled up the virtual disk (I disabled automatic pruning of old data) and that was a pain to export... eventually dumped it into a dedicated MySQL installation and all was well after that.

I've seen that they now have A/B boot (similar to how Android devices do) so hopefully these are issues of the past

[–] [email protected] 2 points 1 week ago

I think I'm about 9 months back or more. Sick of breaking changes and I know there are a lot coming up. Seeing how long I can hold out ;-).

[–] [email protected] 5 points 1 week ago

I was expecting something like version 0.112 but this is pretty close.

[–] [email protected] 2 points 1 week ago

I did a similar jump a while back, actually went quite well, at least via docker. I kept the old image on hand in case I needed to revert.

But yes, backup first.