Problem adding second account for v.3.4.5 and not dot.com domain after reboot
See original GitHub issueDescribe the bug It looks that two differents accounts doesn’t works fine, at least with non .com domain. The first account looks working fine (account added, reboot to test,…), but when I add the second one only works meanwhile I don’t restart Home Assistant. After that, a few errors appears and relogin is required but with not success.
To Reproduce Steps to reproduce the behavior:
- Delete previous integration version
- Add account according procedure
- Test, reboot, test (all ok)
- Add second account and looks fine but…
- Relogin is required after a few minutes. No matters if reboot or not.
System details
- Home-assistant (version): 2020.12.2
- Hassio (Yes/No): yes
- alexa_media (version from
const.py
or HA startup): 3.4.5 - alexapy (version from
pip show alexapy
or HA startup): - Amazon 2FA is enabled (y/n). We will not debug login issues if unanswered: yes
Logs
Logger: alexapy.alexawebsocket Source: /usr/local/lib/python3.8/site-packages/alexapy/alexawebsocket.py:109 First occurred: 10:08:44 (1 occurrences) Last logged: 10:08:44 Websocket is missing ubid-main and ubid-acbes cookies; please report this if anything isn’t working.
Logger: alexapy.helpers Source: /usr/local/lib/python3.8/site-packages/alexapy/helpers.py:153 First occurred: 10:04:26 (7 occurrences) Last logged: 10:09:15 alexaapi.get_device_preferences((<alexapy.alexalogin.AlexaLogin object at 0x6a316a48>,), {}): A login error occured: An exception of type JSONDecodeError occurred. Arguments: (‘Expecting value: line 1 column 1 (char 0)’,) alexaapi.get_devices((<alexapy.alexalogin.AlexaLogin object at 0x6a316a48>,), {}): A login error occured: An exception of type JSONDecodeError occurred. Arguments: (‘Expecting value: line 1 column 1 (char 0)’,) alexaapi.get_dnd_state((<alexapy.alexalogin.AlexaLogin object at 0x6a316a48>,), {}): A login error occured: An exception of type JSONDecodeError occurred. Arguments: (‘Expecting value: line 1 column 1 (char 0)’,) alexaapi.get_authentication((<alexapy.alexalogin.AlexaLogin object at 0x6a316a48>,), {}): A login error occured: An exception of type JSONDecodeError occurred. Arguments: (‘Expecting value: line 1 column 1 (char 0)’,) alexaapi.get_activities((<alexapy.alexalogin.AlexaLogin object at 0x6a316a48>, 10), {}): A login error occured: An exception of type JSONDecodeError occurred. Arguments: (‘Expecting value: line 1 column 1 (char 0)’,)
Additional context Domain .es Rolling back to 3.4.1 works fine
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:12
Top GitHub Comments
No @alandtse, my scenario is two differents Amazon accounts in the same domain (amazon.es). First post updated to avoid misunderstanding
Alexa Media Player >3.4.1 is still failing for me. Tested with 3.4.8 yesterday and the days before.
I still do get rather frequent information that the authentication needs to get recreated. Sometimes it seems to do that on its own. So, I enter the integrations page - and I see no error. Sometimes I need to manually confirm what has already been configured. Most of the time the integration has at least some outages when this happens.
I downgraded to 3.4.1 without changing any configuration or even re-authenticating and it works just fine again for >24 hours.