Thank you. Once i submitted junk it refreshed with the code
Sorry to hijack this current thread…I am at a loss…
I upgraded to home assitant 0.111 from 110.7 and have had a fully functional echo discovery on my system for the past couple of years…I am often having to remove the pickle and then rediscovering throught the integrations panel Alexa Media Player where it discovers without any issue 8 echo devices that I have…
Now however these devices all appear offline…I have deleted the pickle and the integration and still they won’t discover. I have now gone back to 0.110.7 and still nothing discovers…Is there something that I am missing that is obvious to somebody else…or any suggestions on what to try…
Thanks
If I enter the configuration details as amazon.com it finds the devices…but they don’t work…If I enter the details as amazon.co.uk which I have always done living in the UK they are not recognised anymore…Is this an amazon uk problem ?
It’s an international problem. It looks like Amazon changed how those servers respond which breaks an underlying library’s cookie management (aiohttp). I’ll work on it this weekend but I don’t know if it’ll be a quick fix. So far, there’s no workarounds.
What happens if I go back to the yaml integration of Alexa and delete the UI integration? I found the first more reliable than the second. Is it possible running 0.111.1?
I’ve tested it multiple times on amazon.com and I’m not running into the error. Might depend on what region in the US you’re connecting to though. I’m connecting from Southern California so perhaps only some of the servers are causing the issue.
Probably nothing. On HA startup, it’s just converting the yaml to a UI integration. If it detects the integration already exists, it’ll just update with whatever is in the yaml. Of course, if you delete the integration, it’ll disappear until the next restart.
I’m in the SE US and haven’t had any issues since the capthca problem 8 days ago.
Yes, I noticed I can not configure alexa media player today. I’m using amazon.es and got this error when trying to log.
alexalogin.login((<alexapy.alexalogin.AlexaLogin object at 0x6ed36350>,), {‘data’: {‘url’: ‘amazon.es’, ‘debug’: False, ‘scan_interval’: 60, ‘email’: ‘[email protected]’, ‘password’: ‘xxxxxxxxx’, ‘include_devices’: ‘’, ‘exclude_devices’: ‘’}}): An error occured accessing AlexaAPI: An exception of type InvalidURL occurred. Arguments: (URL(‘’),)
I have noticed it is being taken into account at: Cannot log in with amazon.es, amazon.fr and amazon.it · Issue #774 · alandtse/alexa_media_player · GitHub
Metoo’ed and subscribed there. Thanks.
Triggered by your statement I tried if my problem could be something else even if the symptom is the same. I live in Denmark but always used from early days the amazon.com domain.
I removed the entire integration and reinstalled. Then I could perform a login with captcha and it all works again for me. So amazon.com still works.
I am sure i am being blind or stupid, but I cant find the sensors for:
- sensor.media_player_next_alarm
- sensor.media_player_next_timer
- sensor.media_player_next_reminder
I have 3 dots and 1 show, and use timers all the time. The configuration is working fine for me using TTS on them and showing what music is playing etc. Do i need to enable this sensor or make it via a template somehow?
I tried lots of searching for the answer but other people just seem to have the sensor.
I don’t really use timers/reminders but had noticed that the timers seemed to be unavailable unless one was currently running…
(I just tested this and my echo timer went from “unavailable” to the timestamp for the timer)… may try setting a timer and see if it becomes
Available?
Nope, nothing, tired setting an Alarm and a countdown timer, when you have one set, does it show up under entities on yours @Bartem?
Both things set on the kitchen one and nothing extra, and i still get entity not found if i try to reference it by name.
I can’t find and I can’t manage to create a band to play in multiroom on all my alexa echos.
Thank you.
I changed my amazon account to 2FA auth. Now Alexa Media Player is not working anymore and complaining about bad cookie. Where exactly can I find that cookie so I can remove it?
Not sure if i missed a post but lately (2 times this month…about 15June and about 6June) this component stopped working and basically required me to redownload for github and setup again. Prior to those I had not touched this/updated it for about 4 months.
I need to reinstall integration because if I do not I cannot authenticate (no captcha or 2FA) with Amazon.
Is there reason it keeps disconnecting and requiring reauthenticate with Amazon?
So answer myself: in the hidden folder:/config/.storage/*.pickle
Are you using include_device or exclude_device? Then yes you need to correctly use those filters.
There should never be a need to reinstall the component as you described. You either can authenticate or you can’t with Amazon. Reinstalling the component doesn’t change how it tries to authenticate you. The fact it’s reasking you after a period of time is because Amazon is expiring your session.
I agree. Session is expiring.
Question is why? Or more importantly, when it expire why does captcha not appear to allow login and why not propmt for 2FA? You have any hint about this?
Ahhhh @alandtse yep i am! Thanks (sorry, didnt think of that bit).
How do i change them if they have been setup via the UI? Do i have to simply delete and re-add the integration, this time using exclude for the Echos i dont want in HA, then i will get all items for the echos that are outside of the exclude list?
It should detect the expired cookie and pop up a notification allowing you to relogin. If you’re not seeing it, then that’s a bug and you should report it with logs.
Yes, that’s probably the easiest way in case we ever add new entities.
1 Like