I’ve not done a great job keeping my hass up to date. I’ve just tried to upgrade to the latest version from one of the 2023 versions I wanna say… I can’t remember now and since my Raspberry PI is not responding I can’t check.
So any unbricking steps would be helpful! After I hard reset (kill the power) to my Raspberry Pi, it comes back briefly online. And then it dies. Even my router doesn’t see it. What is the best thing to do now? Do I need to reinstall the OS on the SD card? I don’t really want to do it since I’ll probably lose my integrations and automations. I think I do have a backup somewhere, but it’s definitely more outdated than my previous HASS version…
I guess the most convenient thing for me at this point would be to fix the issue straight on the sd card (without booting the OS, just mounting it on my PC). Has anyone tried that? Any tips here at all?
Otherwise the annoying thing is that the PI takes longer to boot up after power cycling than it’s responsive for and I feel like it’d be a loosing battle…
Have you hooked up a monitor and keyboard to the rPi? If so you can downgrade the version until it kicks back in again. My guess is that you have a bunch of stuff not designed for the latest version and that is why it is “bricked”. If it’s not that then the console will tell you what is going on - you could just have a worn out SD card, hard to know until you get a monitor on it.
Hello again!
So I’ve finally found some time to play with the Pi. The device was actually all fine when I hooked it up to an external screen. I decided to go all in and upgraded core to the latest version. The update took a while but all was fine so decided to put it back in its place (generally it’s not sitting on my desk ). Then it stopped responding again. The interesting thing is that it dies (becomes unresponsive on the web UI and ssh) whenever I connect the Zigbee dongle. Any ideas where I could look for more informative logs? How could I fix this guy? Which plugin should I remove/reinstall?
I’ve not really found anything too helpful for me in the logs. This is the only error from ha core logs: