alexa_media_player: Cannot log in with amazon.es, amazon.fr and amazon.it

Hi everyone,

Describe the bug

I lost both tts and announce features since Hassio & Alexa Media update. Alson realized I cannot log in with a amazon.fr domain, only amazon.com

To Reproduce Steps to reproduce the behavior: Update to the latest HA and HACS Amazon Media component

Expected behavior No more TTS and Announce

Screenshots

System details

Home-assistant (version): 0.110.7
Hassio : yes
alexa_media v2.8.4

Logs

2020-06-10 14:47:23 ERROR (MainThread) [alexapy.helpers] alexalogin.login((<alexapy.alexalogin.AlexaLogin object at 0x7f70cc361150>,),}): An error occured accessing AlexaAPI: An exception of type AssertionError occurred. Arguments:

. After trying TTS :

2020-06-10 14:51:26 DEBUG (MainThread) [custom_components.alexa_media.notify] Announce targets: [‘G************XTK’] entities: [<Entity Echo Dot - Study: unavailable>]

2020-06-10 14:51:26 DEBUG (MainThread) [custom_components.alexa_media.notify] Testing item: <Entity Echo Dot - Study: unavailable> against (<Entity Echo Dot - Study: unavailable>, Echo Dot - Study, G************XTK, media_player.echo_dot_study)

2020-06-10 14:51:26 DEBUG (MainThread) [custom_components.alexa_media.notify] Converting: <Entity Echo Dot - Study: unavailable> to (serialnumbers): G090U50990350XTK

2020-06-10 14:51:26 DEBUG (MainThread) [custom_components.alexa_media.notify] Testing item: <Entity Echo Dot - Study: unavailable> against (<Entity Echo Dot - Kitchen: unavailable>, Echo Dot - Kitchen, G************6RR, media_player.echo_dot_kitchen)

2020-06-10 14:51:26 DEBUG (MainThread) [custom_components.alexa_media.notify] Testing item: <Entity Echo Dot - Study: unavailable> against (<Entity Everywhere: unavailable>, Everywhere, d****************************483, media_player.everywhere)

2020-06-10 14:51:26 DEBUG (MainThread) [custom_components.alexa_media.notify] Testing item: <Entity Echo Dot - Study: unavailable> against (<Entity Echo Dot - bedroom: unavailable>, Echo Dot - bedroom, G************W6R, media_player.echo_dot_bedroom)

2020-06-10 14:51:26 DEBUG (MainThread) [custom_components.alexa_media.notify] Testing item: <Entity Echo Dot - Study: unavailable> against (<Entity Zoo: unavailable>, Zoo, 1****************************fc8, media_player.zoo)

2020-06-10 14:51:26 DEBUG (MainThread) [custom_components.alexa_media.notify] Testing item: <Entity Echo Dot - Study: unavailable> against (<Entity This Device: standby>, This Device, 5****************************126, media_player.this_device)

2020-06-10 14:51:26 DEBUG (MainThread) [custom_components.alexa_media.notify] Announce targets: [‘G************XTK’] entities: [<Entity Echo Dot - Study: unavailable>]

Additional context Everything worked fine for a long time before the update.

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 3
Comments: 79 (16 by maintainers)

Commits related to this issue

Merge pull request #785 from alandtse/#774 fix: bump alexapy to 1.10.3 — committed to alandtse/alexa_media_player by alandtse 4 years ago

Most upvoted comments

All, I found the bug’s cause and will see if I can resolve it although it honestly may not be a quick fix given it’s in a lower level library.

I’ll also clean up the thread. If you have a “me too” post, please refrain from adding it so it doesn’t explode the thread.

I don’t think there will be any workaround but if someone finds one, please feel free to post. Please note the reboot/reinstall/re-login won’t solve the problem unless Amazon changes things back.

EDIT: Please just use a 👍 on a post that matches.

+11

alandtse on Jun 14, 2020

+1 with amazon.it domain. I am having this in the notification bar:

Schermata 2020-06-13 alle 15 57 08

Then i have this:

Schermata 2020-06-13 alle 15 57 22

But when i click on it i get this error:

Fallita chiamata a servizio configurator/configure

Is it the same issue all is having?

mfabiani53 on Jun 13, 2020

I have the same problem with amazon.es

diazdeespada on Jun 14, 2020

Need testers to try a potential fix. You will need to modify your alexapy using this PR. Please only do this if you understand how to do it as I probably won’t have time to help you with the basics and with reverting it afterward.

Again, use the emoticon for thumbs up 👍 if you have a me too post. I am trying to keep this organized.

alandtse on Jun 15, 2020

I also tried to reinstall, clear the cache, etc etc … but it still doesn’t work with the IT domain

maxalbani on Jun 13, 2020

Work for me. Best regards

diazdeespada on Jun 17, 2020

Hi to All!! The latest tests: deleted the integration, the component folder alexa_media and the pickle file. Connected the Amazon account from the same lan as HA:

Logoff account from the Amazon website

changed Amazon account password

installed new Alexa Media integration via HACS

added integration in configuration.yaml

after a complete restart of HA the new devices were discovered

guided configuration of the Alexa component performed

everything was so integrated again without further problems!

Works for me. Thank you. Domain: amazon.es

nogardris on Jun 17, 2020

Pour moi, essayez de supprimer dans le répertoire «.storage» le fichier «alexa_media.xxxxxxx.pickle» et redémarrez 😃

Thanks to you, I did as you said it would work for me.

Niconath on Jun 16, 2020

Another try with the PR. Maybe something missing related with aiohttp:

Logger: homeassistant.config_entries
Source: config_entries.py:526
First occurred: 17:28:17 (1 occurrences)
Last logged: 17:28:17

Error occurred loading configuration flow for integration alexa_media: No module named 'alexapy.aiohttp'

somar05 on Jun 16, 2020