As per the suggestions - roll back to 4.13.2 to regain stability
Same problem here reverted to backup!!
I think I’m screwed. I updated AMP then before restarting updated core to 2024.10.0. The update is stuck on “Installing.” What do I do? I’m running on HA Blue so I’m not even sure how to revert to backup.
Are you able to get into the CLI ? I had same issue… If you can… issue ‘ha core stop’ command, then ‘ha core restart --safe-mode’. This should allow you to access the web UI again, and you can then restore a backup if you have one, or else disable/remove AMP addon. If you cant access CLI, you might be able to do similar in the UI… you might get 2 to 3 mins before it crashes… get to Settings>Devices&Services as quickly as you can, and find AMP, should be near the top, and disable it.
So after the myriad of problems after the last Node Red update and now this, I seriously have to ask. How do these updates get pushed without sufficient testing? Crashing someone’s entire home automation system seems like a side effect that should be caught before a release.
2 Likes
Had the same problem!
For those who don’t know how to solve it:
Disable Media Player (prevents restarts)
Download HACS integration again and select version 4.13.2)
Ignore update “offer” for 4.14.3
Restart
So far everything is stable again.
2 Likes
Did you not get the memo ?
Why do you continue to ignore the following messages in your system logfile ?
Home Assistant Core
2024-10-03 10:12:56.340 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration webrtc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-03 10:12:56.341 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-03 10:12:56.343 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration reolink_dev which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-03 10:12:56.343 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-03 10:12:56.344 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration nodered which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-03 10:12:56.345 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration tapo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-03 10:12:56.345 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration browser_mod which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-03 10:12:56.346 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration frigate which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-03 10:12:56.346 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration localtuya which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-03 10:12:56.347 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dahua which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-10-03 10:12:56.348 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration dahua_vto which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
Did I get what memo? I installed an update that doesn’t come with a memo saying that updating the core will crash your whole system. There weren’t 3 seconds between the AMP and core updates to even look at log files.
What I’m saying is that you’re running an UNSUPPORTED system
Either become compliant and uninstall all the add-ons / integrations that you’ve added to home assistant… IF you find that the system is unstable feel free to whine about it here.
If not I suggest you contact your add-on / integration provider and complain there.
This is not the place
You should ask the Alexa Media Player developer. This is their bug.
The answer has a lot to do with the state of play with that custom integration:
I guess it was more of a rhetorical question actually. But if I remember correctly, one of the recent prior AMP updates caused some major problems too. Perhaps I just need to remove this completely.
AMP has had issues every beta release of HA since April. The main developer is only pushing through changes other people make. They are not making any changes themselves. That means there is no testing at all.
2 Likes
It is and remains a compromise. HA also benefits from HACS, without these add-ons and hardware support HA would only be half as good. THAT should not be forgotten either! Sometimes you just have problems and at first many people, including me, thought that the problem was caused by HA. It’s a shame that AMP is doing so badly. Anyone who thinks badly of the fact that users are being directed to HA’s own voice output is a scoundrel? 
No, anyone who thinks that is being paranoid. Remember that correlation does not mean causation.
1 Like
I have the same constant reboot issue. I downloaded the previous version Github zip file and installed it in the docker custom-components (Homeassistant container…)
Just having the same issue. Last night just before going to sleep i’ve updated my core, and today morning saw it just rebooting after rebooting.
Just downgraded it right now, waiting for a new update.
I seriously have a question back. Have you ever participated in Beta testing? You downloaded a custom(!) integration from HACS. The C there stands for Community. That is all of us. No one earns a dime from it. It is a joint effort, a gift from those who help out.
I take part in Beta tesing. I put my real home at risk, with over a 100 integrations, so you can rest easy. It just happens to be AMP is not one of the ones I use.
There are hundreds, if not thousands of custom integrations. It is impossible to test them all, let alone on a pure test environment. I do not have money to spare for buying devices to test with. That goes for all beta testers. We all do what we can, as best we can, with our actual homes.
When we find bugs, and we do, we post them a.s.a.p. with integration owners. But they need to have spare time to fix them. And it so happens this bug is not caused by HA but by the AMP integration update. Which just happens to coincide with the HA update. The problem is with AMP, not HA. And I do not even blame the people trying to keep a sinking ship afloat there.
So I take offense with your tone of voice, because you blame us for not saving your behind, but you did not help out. You just consume, for free. The few people that do participate in beta testing take a risk, so you don’t have to. So not joining in, and complaining we don’t do enough, says more about you than it does about us. You are welcome to join the beta any time. No hard feelings if you pitch in.
2 Likes
OK Time out guys
Yes it gets on my tits too but lets leave it as it is, there will always be those who
- Don’t RTFM
- Expect the world out of a community supported project
- Not contribute any help
3 Likes
Indeed, in HACS, go to the ‘Alexa Media Player’ integration, click on the three dots next to it and click on ‘Redownload’ and select version 4.13.2. Version 4.13.3 is even not available anymore, it seems they pulled it. What a fuckup.
1 Like
Omg … Two days trying to trace the issue. Glad I finally found it. Let’s be easy guys these things happen. Everyone take a deep breath.
1 Like