Alexa Media Player Unable to Login

Third party integrations
21

I’ve been sadly disappointed over the last couple months for Alexa integrations with HA. Well, the cloud voice assist function still works, which is a huge part of HAF (Household Acceptance Factor) in this house, for voice control of HA devices.

But another very large part of Alexa with HA has been providing voice announcements for HA notifications (“Clothes dryer is done”, etc.) And that’s unfortunately been unworkable for a while.

After seeing all the trials and tribulations on the forum about AD and AMP, and some efforts of my own, I gave up on trying to keep up with the troubleshooting and Amazon-induced changes. I uninstalled both AD and AMP.

I greatly appreciate the persistent folks who keep trying to make it work.

I do hope they can make AD work. Meanwhile, maybe I’ll start building out more HA media players. Maybe it’s time I start looking at Music Assistant. Maybe it’s time I start seriously working with HA voice satellites.

Cloud dependence is painful.

22

So I was able to finally reauthenticate AMP. However every time I reboot HA, I have to reauthenticate. This is not ideal, but at least it continues to work until i must reboot.

23

reauthenticating worked fine for me, but TTS is not working at all. I know it is communicating with the Amazon cloud since I can see the status of the Echos, what song is playing, etc… and I can control the player status, volume, etc

24

how did you do that ? for both alex integration `?

it dont work for me
Thx

25

We should have a fix soon:

image
image1282×213 12.5 KB

From:

26

@Esmax555 I had to be on WiFi on the same network as the Alexa’s when I reauthorized. This was for AMP. I do not currently have AD yet.

27

Screenshot_20251108-005339~2
Screenshot_20251108-005339~21080×2400 107 KB

Screenshot_20251108-005318
Screenshot_20251108-0053181080×2400 45.7 KB

Screenshot_20251108-005326
Screenshot_20251108-0053261080×2400 46.3 KB

It’s not working for either the HACS nor official integration since two days now. Amazon seems to be authenticating just fine but it seems to fail when looking for devices. Did something change in their API?

28

There is a workarround waiting for a new realease but it is not made for the weakest.
It is described here, I did it and sure enough, it is working like before

EDIT: It has been updated since. No need to do this trick anymore

29

Editing the manifest

"requirements": ["git+https://gitlab.com/JtMotoX/alexapy.git@fix-auth", "packaging>=20.3", "wrapt>=1.14.0"],
"version": "5.7.11-beta1"

and rebooting HA worked perfectly for me (amazon,it). Authentication is now fixed and all echo devices are available and fully responsive again.

1 Like
30

Didn’t work for me… but I’m in the USA

image
image879×256 77.6 KB

I thought I was losing my mind. Been doing battle trying to get this working for a couple hours now with ZERO luck which led me here.

AMP has been nothing but headaches for as long as I can remember. I hope this gets fixed soon…

EDIT… I thought it was only the “version” section that needed to be updated like in times past. It needs BOTH of these lines modified.

"requirements": ["git+https://gitlab.com/JtMotoX/alexapy.git@fix-auth", "packaging>=20.3", "wrapt>=1.14.0"],
"version": "5.7.11-beta1"

It now authenticates and works:

image
image585×109 12.2 KB

31

It’s broke again… this is very frustrating.
Get this when trying to reconnect.
Invalid Authenticator App key for Amazon 2SV

32

Spent hours trying to fix AMP after upgrading HA OS/Core with no luck: kept getting the 500 Server Error.

On a whim, I finally tried to do the AMP configuration from the HASS Android app (even though I saw many posts saying you’re supposed to do it from a browser and not the app) and that fixed it: after I logged in: instead of getting the 500 error, I got a 2FA prompt. Put in my code and the integration lit up!