I have a mini emergency: The Home Assistant server is up, and the console looks normal. However i can't access it in the web browser. If i reboot it, i can access it for about 90 seconds then it goes offline again. How do i check the logs or at least restart the internal webserver from the console? Or at least roll it back to the backup that it made before the last update from the console.
it is in a death loop rebooting. any help would be appreciated.
-I was able to get in and launch the backup roll back, it stayed up for almost 2 minutes before it rebooted again
#HA inaccessable after latest update
glass sage
cinder remnant
Yep, started after the Core update to 2024.10.0, for my system. The OS is up, but the Core is crashing. When you reboot, immediately revert to last good backup. This was 2024.9.3 for my HA Green box.
glass sage
is there any way to do that from the cli on the console?
cinder remnant
I don't have a console, sorry
Also having to restore last full backup now. Not sure if it's Core or one of the integration updates, but it's still not running right yet.
glass sage
at least i don't feel so alone about this happening. it said something about migrating the esphome too when i ran the update to the latest core. do you know anything about that?
cinder remnant
Don't get me ranting about esphome 🙂
cinder remnant
Ok, I reverted to a full backup from Oct 1st, and the system has been up for 30min now. Not sure which of these updates breaks it, I'm tired of being an Alpha Tester.
glass sage
mine is stuck trying to do the restore. it wont stay up long enough to complete. any idea how to do the restore from the cli?
i will definately not install the next update right when it comes out. lol
now it wont come up at all
uncut tusk
The issue is not the HA update
It's AMP
It also breaks older HA versions
The custom integration owner doesn't maintain it anymore, but does accept PRs without proper testing
Which can have the effect you see now
glass sage
AMP? how can i stop/disable it?
glass sage
that wasnt my screenshot, but i do have it pending too. i looked through the backups and i don't see where it was backed up at an earlier version. how do i revert it?
solemn bisonBOT
that wasnt my screenshot, but i do have it pending too. i looked through the bac...
Congratulations @glass sage! You just advanced to level 7!
uncut tusk
You can download an older version in HACS
solemn bisonBOT
You can download an older version in HACS
Congratulations @uncut tusk! You just advanced to level 6!
uncut tusk
There are no backups when you install a custom component
glass sage
bummer. ok, how can i kill it for now from the cli or the console "ha>"
uncut tusk
Did you already update
You can remove the component from your custom_ components folder and restart core
Or just revert to a full backup before the update of AMP
glass sage
the backup is unlikely. all of my core backups seem to be partial/incremental. Any idea how i can get to the folder from the ha prompt and what to delete? i am a bit of a noob when it comes to digging around in the guts of home assistant
blazing agate
You could [re]start in safe mode, fix AMP then reboot normally.
"Safe mode loads Home Assistant Core, but no custom integrations, no custom cards, and no custom themes. If the issue does not persist in Safe mode, the issue is not with Home Assistant Core."
If you cannot reach the UI, you can enable Safe mode from the command line:
ha core restart --safe-mode
toxic dock
I just had this happen myself. It started yesterday morning right after updating AMP to 4.13.3. So I rebooted HA and immediately went in and "redownloaded" 4.13.2. I have rebooted and so far everything seems to have been fixed... so if you don't have any backups, just try redownloading the previous version.
I do have 1 backup but it is from yesterday morning and I don't know if it was before or after I updated. If it was after, then it wouldn't help and I know the restore can take a LONG time. So I figured I would try this method first.
glass sage
it was up long enough for me to kill the alexa media player add on and then i was able to recover it back. it broke a bunch of other add ons with the roll back, but at least i didn't have to rebuild. lol
Thanks for all of your help.
Anyone feel like adding their expertise to the "renaming network interfaces" thread?
cinder remnant
4.13.4 is out claiming to fix an infinite loop. Yeah, you think???
glass sage
4.13.4 is out claiming to fix an infinite loop. Yeah, you think???
i sure hope so, but im gonna wait a few days before i run the patch/update
toxic dock
i sure hope so, but im gonna wait a few days before i run the patch/update
Lol, this is exactly what I came here for, to see if anyone had confirmed it's ok to update.
glass sage
just pulled the pin on the version that supposedly fixed the reboot loop.. lets see how it goes
cinder remnant
So did I, seems to have been fixed
lusty karma
It has to do with the Alexa Media Player integration, it should be fixed by now.
glass sage
all good so far. Toya's monthly login is getting annoying however
toxic dock
all good so far. Toya's monthly login is getting annoying however
Thanks for the update. I guess I will go ahead and upgrade mine.
and ya, those monthly "re-verifications" are super annoying, I get them for Tuya and Kasa
cinder remnant
all good so far. Toya's monthly login is getting annoying however
Try the new integration, once it imports from SmartLife, you're set.
glass sage
Try the new integration, once it imports from SmartLife, you're set.
What integration? You mean toya local?
cinder remnant
No, that's what I used to use also, but this last year they updated the official integration to import your devices via the SmartLife app on your phone. No maze of BS on the tuya.com again.
toxic dock
This has started happening for me again today, and I JUST updated Alexa Media Player again. I am waiting for my latest restart to finish loading (which now takes a long time, for some reason) and I will try rolling the AMP installation back as before.
Is this happening to anyone else?