Upgrading to Home Assistant 2024.8 the Alexa Media Player integration stopped working

Third party integrations
48

To be honest, I’m never looking at the logs as long as stuffs are working.
It seems that I have some errors too but it is not preventing the integration to work

Aug 11 15:02:15 hassbian hass[10728]: 2024-08-11 15:02:15.196 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry ******.******@******.com - amazon.fr for media_player
Aug 11 15:02:15 hassbian hass[10728]: Traceback (most recent call last):
Aug 11 15:02:15 hassbian hass[10728]:   File "/srv/homeassistant/lib/python3.12/site-packages/homeassistant/config_entries.py", line 604, in async_setup
Aug 11 15:02:15 hassbian hass[10728]:     result = await component.async_setup_entry(hass, self)
Aug 11 15:02:15 hassbian hass[10728]:              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Aug 11 15:02:15 hassbian hass[10728]:   File "/srv/homeassistant/lib/python3.12/site-packages/homeassistant/components/media_player/__init__.py", line 442, in async_setup_entry
Aug 11 15:02:15 hassbian hass[10728]:     return await component.async_setup_entry(entry)
Aug 11 15:02:15 hassbian hass[10728]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Aug 11 15:02:15 hassbian hass[10728]:   File "/srv/homeassistant/lib/python3.12/site-packages/homeassistant/helpers/entity_component.py", line 184, in async_setup_entry
Aug 11 15:02:15 hassbian hass[10728]:     raise ValueError(
Aug 11 15:02:15 hassbian hass[10728]: ValueError: Config entry ******.******@******.com - amazon.fr (921c00378649a4368f94a18c496a90e9) for alexa_media.media_player has already been setup!

Maybe open an issue on the gitlab of the integration

49

Thank you. Will go to gitlab and post my problem.

50

yeah, this broke my alexa media integration as well. I ended up rolling back and all is fine. I will wait until it is fixed and then update again.

51

Still not working with HA 8.2 and Alexa 4.12.8 on 08-18-24

52

Same here. Getting constantly asked to re-authenticate
image

I’m thinking to downgrade HA because of it :frowning: (never had to do it!)

1 Like
53

I have downgraded to 7.2 to keep Alexa text-to-speech working. I hope it gets fixed soon.

1 Like
54

image
image1054×268 32.8 KB

image
image850×325 14.7 KB

Does anyone know how to solve this?

No matter what version I have, this message keeps coming back

1 Like
55

Is there any update on this?

56

I know that I am not being very helpful but my text-to-speech on Alexa devices works fine in my HA.

57

Yesterday I just started to get the error:
The automation "Clear Alexa History @ 11:50 PM" (`automation.new_automation_3` ) has an unknown action: `alexa_media.clear_history` .

Is this part of the same problem?

I’ve tried

"requirements": ["alexapy>=1.28.2", "packaging>=20.3", "wrapt>=1.14.0"],
and
"requirements": ["alexapy==1.28.2", "packaging>=20.3", "wrapt>=1.14.0"],

and a restart but neither solves my problem.

Starting on July 25, 2024 I was unable to retrieve “temperature” from my echo dots which is consistent with the posts above but the “clear history” just started yesterday so I’m not sure if I have some other new problem or not.

I’m running:
image

58

The solutions above did not help.
I was hopeful 2024.9 might fix things with Alexa.
No such luck.
I had to skip all of the 2024.8 releases because Alexa’s voice is essential to my home security.
I’m going back to 2024.7.4
Is there any hope of a fix?

1 Like
59

I had the same problem.
Just noticed an update in HACS (v4.12.12) I was version v4.12.7.
Upgraded and it worked!

60

I posted on Alexa Media GitHub re the clearing of history and this is the response that I received:

Amazon no longer supports that call and you have to use their app to clear history.
Delete Some or All of Your Voice History in the Alexa App - Amazon Customer Service

:frowning:

61

I have re-authenticated everything successfully, but ALL my Alexa devices show as Unavailable.
What can I do? Already tried editing the manifest.json without luck.
Thanks!

62

I found the answer: " Are any of you using an ad blocker/firewall such as Pi-hole or AdGuard by chance? Some adlists were recently updated to block the Amazon Alexa API. This is solved by adding ^api(\.[a-z]+)?\.amazonalexa\.com$ to your Pi-hole whitelist or @@||api*.amazonalexa.com^ for AdGuard. This regex is not region specific and should work for all endpoints"

2 Likes
63

I’m desperate. I tried everything. I am stuck at the alexa webpage login, there’s my email in the form, i click next, there’s my password, i click next again, and it comes back to the first page with the login/email. I can’t see anything in the logs, i’ve deleted all the pickles and such in .storage. I have an AdGuard personal DNS server but i also tried to disable it, to add the exception you mention. I also changed the api in the manifest, disabled an re-enable 2FA in my Amazon and added back the app, nothing works, it’s really driving me crazy. Does anyone have an idea ? Thanks

64

Try this. If it works, thank whoever posted the step by step instruction.

1 Like
65

That was my discovery!

3 Likes
66

Bro. Thank you. I don’t know how you thought about this but congrats. On the other end, this extension is very nice, but so painful at the same time. How are we supposed to figure this out ?

67

I guess I’m just very good at figuring out software from a user’s perspective, plus I’ve had decades of troubleshooting experience in the IT field. I’ve spent most of my spare time in the last few months getting inside and trying to figure out this integration. I and a couple of others have learned a lot but we still have a ways to go. But in all honesty, this discovery was a happy accident. If Amazon had redesigned the forms slightly differently, we’d still be FUBAR…