-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All devices unavailable after restart, list of device not appearing with new installation #2558
Comments
Same here. on home assistant core 2024.9.2 and alexa media player 4.13.2. thanks, bye |
adding another one |
Same here, integration is now saying “Failed setup, will retry: Connection Error during login” HA core 2024.9.2 |
same. Error setting up entry [email protected] - amazon.com for alexa_media and This error originated from a custom integration. Logger: alexapy.helpers alexalogin.login((<alexapy.alexalogin.AlexaLogin object at 0x7fbe9f8be120>,), {'cookies': {}}): An error occurred accessing AlexaAPI: An exception of type TypeError occurred. Arguments: ('can only concatenate str (not "NoneType") to str',) |
Same here
AMP 4.13.2 |
Same problem Too Many Requests |
Same issue after 20/30 min -> “All devices unavailable” i try time polling to 500 , but don’t work HA core 2024.9.2 |
Exact same issue. Poorly tried changing public domain to local ip and adding and removing trailing / |
Same here for me in the UK Error setting up entry p.p.*******@*******net.com - amazon.co.uk for alexa_media
Logger: alexapy.helpers alexalogin.login((<alexapy.alexalogin.AlexaLogin object at 0x7fe1963f2150>,), {'cookies': {}}): An error occurred accessing AlexaAPI: An exception of type TypeError occurred. Arguments: ('can only concatenate str (not "NoneType") |
Same here for me (Spain) Registrador: homeassistant.config_entries Error setting up entry joe*****@*******.com - amazon.es for alexa_media |
Same issue unfortunately :( |
Same issue here from UK. Error for me is: |
I got mine working by updating to HA Core 2024.9.3. (that seemed to remove the "none type" error I was getting before) but then I was getting a generic authentication failure error in the logs. I removed the AMP integration, restarted Home Assistant, and re-added it. Ran through the setup and everything is working again. For those who said they are worried about automations, the devices picked right back up and I didn't miss a beat. |
Same problem here in Germany. I tried to uninstall and reinstall and now I'm in a endless loop on the Amazon Login website during setup. |
Hi, there is a workaround for endless loop signin here. #2514 |
I did use that workaround. After the next restart AMP was disconnected again. Accidentally logging into amazon.com instead of amazon.de didn't have any issue. This is really annoying. |
I think linked to this issue, after removing and reinstalling integration and following the workaround for the login loop, I receive a blank 'Error' dialogue back in HA at the final step and nothing is added. This is using 2SV and both amazon.com and amazon.co.uk domains in setup. |
I'm in the same boat. I've tried removing the component completely, reinstalling, and now I get an error when trying to log in. I've gone back all the way to v12.2 |
using AMP version 4.12.7 and 2024.9.3 for HA I don't encounter any problems. |
I've done this multiple times. Its when I get returned to HA that HA just shows a blank error screen. |
This ^ It is not the Amazon login or 2SV that's the issue. The workaround for create new, then login works. It's back in HA at the final step that the error is generated and setup of thr integration fails. |
By following this procedure I was able to get the installation to work several times. |
I don't know what to tell you - it's great that it works for you, I'm simply saying that it doesn't for me, and others.
This is on the latest AMP version, and up to date HA install. |
This was even after completely removing AMP, removing config files, clearing cookies, removing alexa and .pickle within .storage. I reinstalled at AMP 4.12.11 and on HA 2024.8.2. As you can see the Amazon login/workaround for creating an account works. It's when we get back to HA, we get the error. |
Maybe this helps? |
Oh, thank you!! This was it for me, using pi hole. Disabling blocking didn't seem to work but adding the new regex fixed it. AMP seems to be working again. |
Thanks, but trying adding whitelist regex filter or disabling blocking for exact domain not working for me. I have same error after some minutes. " An error occurred accessing AlexaAPI: An exception of type AlexapyLoginError occurred. Arguments: ('Login error detected; not contacting API',)" |
I found the answer on github!: "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" |
Same issue for me. Suddenly all alexa devices are showing as unavailable. |
In my installation of Home Assistant 2024.9 and AMP 4.13.2, I have encountered both errors. However, with amazon.com, I am unable to control any devices, though all of my devices are available when using amazon.com. If I try with amazon.de, no devices are shown. I have tested this with Pi-hole disabled, and I have completely opened my firewall. Hopefully, someone can help. |
You can't play games with Amazon Alexa as she doesn't know how to play! If your devices are registered via your account at amazon.com then you need to use amazon.com. If your devices are registered via your account at amazon.de then you need to use amazon.de. |
@elbrondor What devices are you trying to control? |
I can confirm that whitelisting ^api(.[a-z]+)?.amazonalexa.com$ in Pi-Hole fixed the issue for me. |
Here are the related log lines: 2024-10-04 15:22:38.796 DEBUG (MainThread) [custom_components.alexa_media] Discovered new media_player G09G |
None of the solutions are working for me anymore. Amazon login loop, workaround - check. Reconfiguration to my domain .de - check. Pihole regex whitelist for api.amazonalexa.* - check. No changes. All the entities are in a "not available" state. I tried several versions of HA Core and AMP. I cant get it to work at all. After every reconfiguration alexa app is saying that it detected some new devices, but its not possible to control anything from HA. Any solution would be great. I could provide logs, but nothing which wasn't already posted here. |
IMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.
Describe the bug
I am using this integration since few years, i was using it without any issue since a month ago, while upgrading to 4.13+ i had authentication issue, so i went back to 4.12.
Then, the 12th of september after a HA restart, all alexa echo devices appear offline ever since. I tried to reinstall the intregration, upgrade and reauthenticate from fresh, but in case of a fresh new installation the list doesn't appear at all (therefore why is unavailable in the list already present since previous)
To Reproduce
i can install a fresh new integration and list of devices not appearing even if the alexa account is active and devices there and working
ì
System details
const.py
or HA startup log):pip show alexapy
in homeasssistant container or HA startup log):Debug Logs (alexa_media & alexapy)
Please provide logs.
Additional context
The text was updated successfully, but these errors were encountered: