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