-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PLEASE REVOKE v4.13.3 ASAP! #2583
Comments
As a newbie, this was a nightmare to me. I upgraded AMP, then got in the disconnect loop... had no idea what was going on... tried to see on the logbook - "Repairs detected an event" with no more details, thanks a lot... googled for that expression, result: unknown... back to Settings, noticed the Tip! Went to the forums, and here I am. I have already downgraded AMP but why is the faulty version still being offered? Take it down ASAP please! |
I just spent 2 hours with cold sweats trying to understand why my HA is not responding / restarting randomly and explaining to my family why the lights and well... nothing really... works anymore :-) It is only after I disabled the recently updated Alexa integration that my system became stable again (fingers crossed). We appreciate your work, but this needs to be fixed. Thank you! PS: the error thrown by the host was "out of memory - killed process XXXX (python 3)" |
Same thing here. Endless frustration this morning as my HA rebooted constantly. I restored from a backup early this AM (before the AMP update) and everything was fine. "Skipped" the update for now. |
Oh so this is why. Ugh. What a shit show. My only option is to restore form backup? Come on guysssss |
yep... had to restore from last backup as well... |
Facing the same problem, HA keeps crashing when updated Alexa media player to version 14.13.3 |
if u mange to login to hasso disable it it or downgrade |
Same issue here, spent ages trying to figure it out until I found this :-( |
For those not reading the other issues posted.
|
I had the same issue, but I could never get into HA long enough to be able to disable and re-download. I ended up ssh'ing into the server, went to the custom_components folder and moved it out do a directory not within HA for the time being to see if that was what was causing it. Once moved out, I was able to start HA successfully and re-download. |
took me age to identify the issue. Thanks for reporting ;) |
This is the only integration I have that ever breaks and it does often. Why not setup a beta channel and actually test the changes before rolling them out? I'd be happy to help test. |
We don't need testers per se, we need devs. Dupe of #2579. |
It appears they have pulled 4.13.3. |
Describe the bug
v4.13.3 is obviously breaking complete HA installations by the dozens - or more likely though: by the thousands, with new systems affected every moment.
Please revoke this release ASAP until a fix is available.
Thanks for all your work and sorry for yelling... ;D
See:
#2582
#2579
home-assistant/core#127431
home-assistant/core#127460
home-assistant/core#127395
(and probably more to come soon)
The text was updated successfully, but these errors were encountered: