alexa_media_player: Error after "Loading next step" and New access token received
Describe the bug The integration of alexa media player doesn’t arrive to finish the isntallation. After I authenticate my connexion with amazon, it loops in state “Loading next step for Alexa media player” until a pop-up “Error”. The authentication of the amazon credential seems to work, I have the sentence “success, you can close this windows”. I don’t know if it’s the cause of my issue but I change my router (my gateway was 192.168.0.1 and become 192.168.1.1). I connect all my echo to the new router wifi but the integration in HA is failed. I only change the router and nothing about the configuration in HA. With my old router the integration worked fine.
I uninstall the integration, remove from HACS, reboot and try again, but it’s style has the same behaviour.
To Reproduce Maybe changes the router or the gateway.
Expected behavior I expected I retrieved all my device of my amazon echo and I can use TTS commands for example.
Screenshots 2 screenshots showing the 2 pop-up explained in description.
System details
- Home-assistant (version): 2022.11.2
- alexa_media (version from
const.py
or HA startup): v4.3.2 - alexapy (version from
pip show alexapy
or HA startup): - Amazon 2FA is enabled : n
Logs I join log’s file and in the end of log we can see: {“requested_extensions”}, {“Value”:} 2022-12-02 11:20:24.715 DEBUG (MainThread) [alexapy.alexalogin] Successfully registered ***'s 16th Alexa Media Player device with Amazon 2022-12-02 11:20:24.715 DEBUG (MainThread) [alexapy.alexalogin] Received registration data: {“success”: ***}} 2022-12-02 11:20:24.716 DEBUG (MainThread) [alexapy.alexalogin] New access token received which expires at 2022-12-02 12:20:24.716127 in 0:59:59.999968
Additional context The Alexa provided by home assistant works fine without changes everything. I’m able to access to my HA outside of my private network.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (2 by maintainers)
fixed this on my end, disabling ipv6 let the integration install and discovered all devices.
@Cmo2788, thank you so much for the comment about IPv6. I disabled IPv6 in HA Network settings, restarted, and everything works again. I had been experiencing failure of the integration to startup for quite a while now. Suffering by myself, trying to debug, seeing the
aiohttp
timeout. Long time spent initializing, then usually failure, and many times telling me I needed to reauthenticate with Amazon. Other integrations were very slow to start until disabling IPv6. Now startup is fast. Thanks a bunch!I try to disable the ipv6 and it works too for me. I retrieve all my device and I can control them. Thank you all for your help and Cmo2788 for the solution.
Alandtse you can reproduce the bug I think. I let you manage the issue.