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!

  • d0ntpan1c@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    2
    ·
    19 hours 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.

    • jws_shadotak
      link
      fedilink
      English
      arrow-up
      5
      ·
      2 days ago

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

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

    • MudMan@fedia.io
      link
      fedilink
      arrow-up
      3
      ·
      2 days 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.

    • mac@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      1 day ago

      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
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 day 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.

  • TedZanzibar@feddit.uk
    link
    fedilink
    English
    arrow-up
    4
    ·
    2 days ago

    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!

    • realitista@lemm.ee
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

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

      • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.dbzer0.comOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        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

        • realitista@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 hours 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 ;-).