Thank you. Will go to gitlab and post my problem.
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.
Still not working with HA 8.2 and Alexa 4.12.8 on 08-18-24
Same here. Getting constantly asked to re-authenticate
I’m thinking to downgrade HA because of it 
(never had to do it!)
1 Like
I have downgraded to 7.2 to keep Alexa text-to-speech working. I hope it gets fixed soon.
1 Like
1 Like
Is there any update on this?
I know that I am not being very helpful but my text-to-speech on Alexa devices works fine in my HA.
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:
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
I had the same problem.
Just noticed an update in HACS (v4.12.12) I was version v4.12.7.
Upgraded and it worked!
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
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!
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
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
That was my discovery!
3 Likes
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 ?
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…
I ended up ditching the integration all together and building the most basic fully local HA Media Player, just for my voice announcements