Rage321
(Rage321)
October 5, 2024, 11:10pm
42
Hi everyone. I’m glad I found this thread. I’m not exactly sure what to do, but I’m stuck where I can’t get into HA via a browser nor through SSH. I have a ping -t going, to see if it truly rebooting on me like the others, and if so I going to log in as quickly as possible and disable the Alexa.
Still, I’m not able to get in, what are my options? I have a back up from 3 days ago.
petro
(Petro)
October 5, 2024, 11:22pm
43
Power it off, plug a keyboard and monitor into the system. Turn it on, when the screen boots up, type
ha core restart --safe-mode
Once you’re into safe mode, disable the integration. And you can restart in non safe mode to downgrade it
3 Likes
Rage321
(Rage321)
October 5, 2024, 11:40pm
44
Thank you for this response. I’ve gone just this, and I see hope. Hope on a Saturday!
So, just to get this clearly out there.
If you STAY on AMP 4.13.2 you should NOT upgrade to HA 2024.10.1. Is this correct? Otherwise AMP won’t work?
Until a new stable version of AMP is released, then HA should NOT go above 2024.10.0, correct?
Gav_in
(Gavin)
October 6, 2024, 8:06am
46
No…AMP 4.13.2 works fine with HA 2024.10.1…the block was pulled, see PSA: Alexa Media Player v4.13.3 breaks all versions of Home Assistant - #36 by Gav_in for the details
Sammy521
(Sammy521)
October 6, 2024, 11:20am
47
How to downgrade? Can you explain for dummies like me?
I experience unstability HA boots new every now and then. Maybe coz i made the last alexa media player Update
Gav_in
(Gavin)
October 6, 2024, 11:25am
48
How have you installed AMP?
Version 4.13.3 is no longer available so if for example you are using HACS to install this, then just redownload the custom component and you’ll be back to 4.13.2…if you search this thread there are a few mentions of how to install…
Gav_in
(Gavin)
October 6, 2024, 9:45pm
50
AMP 4.13.4 is available now and according to release notes fixes the resource issues of 4.13.3
diedrichg
(Diedrich)
October 7, 2024, 1:30am
51
Can anybody confirm stability for 4.13.4?
I’m wondering if anyone here in this thread is able to use AMP in HA 2024.10.x in region amazon.de at all?
Für me it stopped working HA releases far in the future (where I’m still sitting because of this problem). Regardless of AMP version.
_dev_null
(/dev /null)
October 7, 2024, 9:20am
53
Gav_in
(Gavin)
October 7, 2024, 9:26am
54
according to the main GitHub issue this was reported on/worked on there are numerous people who have been successful with the fix in 4.13.4 so should be ok for all (but obv that’s not a guarantee)
opened 06:18AM - 03 Oct 24 UTC
closed 08:10PM - 06 Oct 24 UTC
**IMPORTANT: Please search the issues, including closed issues, and the [FAQ](ht… tps://github.com/alandtse/alexa_media_player/wiki/FAQ) before opening a new issue. The template is mandatory; failure to use it will result in issue closure.**
**Describe the bug**
I installed v4.13.3 and shortly after my HA kept loosing connection. I would re boot, it would work fine for a few minutes, then it would disconect.
**To Reproduce**
I used a full backup for HA for Sept 30th. Before the Alexa update I did a core update, assumed that caused the issue. Once I restored I didn't do the core update but did do the Alexa update. Few minutes later issue of disconnect started again.
Restored the Sept 30th backup again. This time I did the HA core update, but skipped the v4.13.3 update for Alexa. My HA has been stable for over 30 minutes now.
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
I would expect to install v4.13.3 and not have my HA system crash.
**Screenshots**
No screen shots
**System details**
- Home Assistant version: Running HA via proxmox server. Updated to the last version
- alexa_media version (from `const.py` or HA startup log): Stable version 4.13.2
- alexapy version (from `pip show alexapy` in homeasssistant container or HA startup log):
- Is Amazon [2FA/2SV enabled](https://github.com/alandtse/alexa_media_player/wiki/Configuration#enable-two-factor-authentication-for-your-amazon-account) (y/n):
- Amazon Domain:
**Debug Logs (alexa_media & alexapy)**
Please provide [logs](https://github.com/alandtse/alexa_media_player/wiki/FAQ#how-do-i-enable-debug-logging-for-the-component).
**Additional context**
1 Like
4.13.4 working fine for me also
1 Like
_dev_null
(/dev /null)
October 7, 2024, 11:37am
57
4.13.4 loaded ok for me too
1 Like
Alexa has censored certain curse words here for a long time… if that didn’t use to be the case for you, it’s more likely related to an update by Amazon, not AMP.
ColtonYYZ
(ColtonYYZ)
October 7, 2024, 7:48pm
60
4.13.4 has loaded fine with no issues for me. I am updated on Hass also. So I’m good!
1 Like
Gav_in
(Gavin)
October 7, 2024, 7:56pm
61
never actually knew what I was missing out on…
Petro has a workaround in this thread if anyone does feel the need to have Alexa swear at you
uh, so I make alexa swear all the time, they may have just added ass to the list of swear words. To get her to swear…
fu'ck
b'itch
sh'it
you get the idea. I just do a find/replace on the string to get her to swear.
Details here:
1 Like
I keep running into the auth issue where it redirects to the different screen. Anyone have ideas as to why? I’ve tried multiple different versions. It just asks me for my creds over and over again.