Please take a look at the other thread I linked. You’ll notice that there is no developer. It’s just random people trying to make it work.
Downgrade Alexa Media Player to v4.13.2. HA will work fine.
- Core 2024.10.0
- Supervisor 2024.09.1
- Operating System 13.1
- Frontend 20241002.2
2 Likes
If I am understanding correctly, if I want to keep the current working version of Alexa Media Player v4.13.2 I shouldn’t upgrade to Core 10.1 since all versiosn under 4.13.3 will be blocked?
2 Likes
How could someone downgrade / remove / disable this version on HAOS?
Not an issue for me fortunately as I’m running it in proxmox and took a backup (now restored).
EDIT: would removing alexa_media dir from ~/config/custom_components be sufficient or cause other issues?
Correct. 2024.10.0 or lower and 4.13.2.
I also used a backup to fix my issue, and in fact used my backup to trouble shoot. I was the first one to report the issue on the AMP github page Version v4.13.3 is making HA fail · Issue #2579 · alandtse/alexa_media_player · GitHub To re install the previous AMP version without having to restore the full back up you can use the HACS ingegration as shown bellow
You might not have enough time to do it before your system shuts down. What you could do is right after your system boots up, go to “devices and settings” select the Alexa Media Player integration, click the 3 dots, and select disable.
Once disabled I would reboot again, and at that point your HA should be stable, and you should be able to re install the previous version of AMP
4 Likes
If going back to 4.13.2 is solving the issue from 4.13.3, why will 4.13.2 and lower be blocked?
2 Likes
If you revert back to 4.13.2 everything is working again… No need to block!!
That’s just how the blocking mechanism in HA works.
FWIW, if you just use this integration for announcements (or anything that could be triggered from a routine) and if you’re not afraid of self-hosting a skill then GitHub - sweharris/Alexa-Smart-Home-VirtualButtons: This lets you trigger Alexa routines using a HTTP API to press a "virtual button". Can be used, eg, in Home Assistant to get announcements ("Garage Door is Open", "Washing machine has finished") or anything else Alexa can do in a routine! might be an option. It’s a lot of work to set up but it works and uses official APIs.
But if you use AMP for more than that (eg to control/manage devices) then this will not meet your needs.
4 Likes
In the mean time, I just took the approach of disabling the AMP integration. That seems to have stopped the constant restarts…
1 Like
So this is installed pending restart for me
Is there any way to roll back at this point?
My ha restarts itself overnight so would like to fix this before I go to bed 
Edit:
Okay, I’ve disabled AMP and I’ve found the redownload button and redownload the old version
It now says I have two pending restarts for AMP
Am I safe to reboot?
How do you revert?
You seem to be on HACS 2.0 so in HA go to Developer Tools > Actions and then
action: update.install
data:
version: v4.13.2
target:
entity_id: update.alexa_media_player_update
then if you check the update.alexa_media_player_update entity it’ll show the installed version
1 Like
Goto Hacs press the 3 dots icon. Redownload and select the other release. Download and restart
2 Likes
Please can Home Assistant add a limit to prevent memory leaks or an addon using soo much RAM that it crashes.
I’ve found there is an option to limit RAM usage by add-on but it’s not implemented by default.
Yeah think so…if you have AMP Integration disabled it’ll not impact HA anyway…
1 Like
Add-ons and Integrations are two different things…AMP is an Integration rather than an Add-on…
In your other thread where you mention Node Red that is an Add-on.
(but a good idea if it’s possible)
Thanks a lot! this was wrecking my head all evening trying to figure out what was happening!
1 Like