Please don’t be scared; it is October, Halloween is coming, and so is the next Home Assistant release: 2024.10! 🎃

  • Bluesheep@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    9 hours ago

    This happened to me, I’m running HAOS on proxmox. Ended up restoring from backup. Rollback from the CLI didn’t fix it either.

    • Napatwork@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      9 hours ago

      If you’ve got the Alexa integration installed then the latest update causes the reboot. You might be able to disable it as it’s coming up and then downgrade it to one that works

      • Bluesheep@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        9 hours ago

        I did wonder if that was the one that did it. That’ll teach me to update multiple things at once.

        The only thing I lost was a day of recorder data and since I repaired it before bed I guess if I went and recovered the previous build I’d lose what I had overnight in the switch back.

        Thanks for letting me know though, I’ll warn my friends before they update.

    • Stampela@startrek.website
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 hours ago

      Similarly unfortunate situation for me, using the backup didn’t really help. But I DO have the Alexa integration, I guess next time I get HA between reboots I’ll disable that.

      • Bluesheep@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        57 minutes ago

        If you’ve got access to the file system I think you could remove the custom component there - can’t exhausted resources if there’s no code!