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

homeassistant

13401 readers
5 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
greatalbatross@lemmy.world
51
Upgrading from an ancient version of Home Assistant (images2.imgbox.com)
submitted 3 weeks ago by lemann@lemmy.dbzer0.com to c/homeassistant@lemmy.world
17 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 17 comments
sorted by: hot top controversial new old
[–] mhzawadi@lemmy.horwood.cloud 26 points 3 weeks ago (2 children)

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

[–] jws_shadotak@sh.itjust.works 6 points 3 weeks 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.

[–] ravermeister@lemmy.rimkus.it 1 points 3 weeks 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.

[–] MudMan@fedia.io 3 points 3 weeks 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.

[–] roofuskit@lemmy.world 17 points 3 weeks ago (2 children)

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

[–] mac@lemm.ee 3 points 3 weeks ago* (last edited 3 weeks 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?

[–] roofuskit@lemmy.world 4 points 3 weeks 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.

[–] portageinclusion@lemm.ee 1 points 2 weeks ago (1 children)

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

[–] roofuskit@lemmy.world 2 points 2 weeks ago

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

[–] merthyr1831@lemmy.ml 8 points 3 weeks ago

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

[–] limelight79@lemm.ee 5 points 3 weeks ago (1 children)

Well how did it go?

[–] lemann@lemmy.dbzer0.com 3 points 3 weeks ago* (last edited 3 weeks 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

[–] limelight79@lemm.ee 2 points 3 weeks ago

Good luck!

[–] Undearius@lemmy.ca 5 points 3 weeks ago

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

[–] lemann@lemmy.dbzer0.com 3 points 2 weeks ago

Quick update if anyone is reading this in future - the upgrade was successful!

Hats off to the HA developers and contributors - even though my install was completely unsupported, the updater pretty much sailed smoothly through everything.

It ended up taking several days to process all the database schema changes, along the way I did need to modify the MySQL InnoDB cache size from 128MiB to 1GiB (not the fault of Home Assistant at all - I didn't set up MySQL correctly πŸ˜‚) once that was done things significantly sped up.

Looking forward to all the new features HA has to offer πŸ™‚

[–] d0ntpan1c@lemmy.blahaj.zone 2 points 3 weeks 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.