Spyke

Syndicated from the fediverse. Read and engage on the original instance.

View original on lemmy.horwood.cloud

11 replies

Bluesheepreply
lemmy.world

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

3
Napatworkreply
lemmy.world

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

3

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.

1
Stampelareply
startrek.website

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.

1
Bluesheepreply
lemmy.world

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!

1

Had access to cli, restarted HA and quickly disabled the Alexa integration: so far everything is working as intended :)

1

Oh no, I was hoping that the new version would finally let my attempt at running it on proxmox work

1
lemmy.world

Been using card mod with 2024.9 since release. What problems are you having?

2

You reached the end

2024.10: Heading in the right direction | Spyke