First, using Visual Studio Code (or any other file editor of your choice), open this file: /homeassistant/custom_components/alexa_media/manifest.json
Then, locate the line within that file that says requirements: and change that line to this: "requirements": ["alexapy>=1.28.2", "packaging>=20.3", "wrapt>=1.14.0"],
Same issue also for me (on amazon.it domain).
The integration works for few minutes after “reinstalling” it.
Then nothing appears weird but the integration stops to work.
If I “reload” the integration the cycle repeats (ok for mins, ko after).
Okay, can someone explain this to me? Having Alexa devices announce things to me is core to my alerting strategy, and I assume many others.
If this integration is all but abandoned, what’s next? Are there so few who use the media player integration for voice announcements? Are there other solid ways to have Echo devices speak notifications to us?
I also rely on echos for voice notifications around the house…cheap and great devices. Easy integration with alexa is the main reason I pay subscription to Nabucasa as well…I know it is only part of it and the custom “alexa media player” is needed but I would assume either an official integration or maintenance of the custom one would be granted since it is most likely something a lot of people use…I doubt people are willing to invest on other speakers if they already have alexa like it is my case…
I am not IT apart from very simple things with HA but seriously this “alexa issue” is not in the TOP priority for the HA team and community?
No, it is not a priority at all for the HA team because the integration you are referring to is not part of HA core. No one in the HA team is responsible for this custom integration.
As for the community, an attempt has been made here to find another suitable person to maintain the integration here, but no one seems to have taken on the challenge so far, and I don’t blame them.
Amazon is what it is - they will keep changing their API and will probably start charging for stuff which used to be free before. The devices were cheap because they thought they’d get lots of profits from people using them to order stuff from Amazon.
Well, they were wrong and it cost them something in the region of $25 billion in four years. Basically, if you own an echo, it’s living on borrowed time.
It does seem that for such a major player in the computer world with so many millions of devices that HA would care enough to offer some sort of core support. So, what are the alternatives that are core supported by HA?
The main developer stopped writing code for it in January 2024. All the magic you’re talking about is random people making small fixes. The integration and it’s upstream library needs a complete overhaul, which is a massive undertaking. I.e. A main developer is needed.
Please take the time to read the post I linked above, it explains everything.
I need HA to make announcements around the house. I’ve been using Alexa and echos as speakers with the alexa media player. Been paying for nabucasa since it came online to support HA development. Very disappointed to see alexa announcing is not considered core support for HA.
What announcing mechanism is supported by HA? What would the speakers be?
Click the link in the post you replied to. Your questions are answered there already.
If you still have questions, there are about 7 “Year of the voice” blog posts, each with their separate thread full of questions and answers.
I take it this is dead now? Alexa media not loading for me at all. I reinstalled and when I try to log into alexa to give it 2FA codes it just loops between entering password and going back to log in.
This is literally the only reason I pay 7 quid a month to HACs.
It has 1 foot in the grave. Daniel is trying to fix everything he finds, however there’s a larger bug that requires some major rework with how HTTP is being used so that it stops blocking HA’s event loop. A reload of the integration typically fixes the issue, but its seemingly random on my end.
That money does not go to Alexa Media Player developers, you’re giving money to people who created HACS. They are unrelated.
He Petro yes I understand that, I was expressing my concern at no alexa, its the only reason I use HACS.
Yes I have had a reload issue frequently over the last year but a refresh sorted it, No such luck this time so I deleted and readded, but when it goes to the alexa sign in it just loops. So I cannot sign in to get the key.
Such a shame, I’ll take a look at Homebridge. HAC own solution looks interesting but I just want a solution I am not geeky enough!
This is such a shame. Alexa is a great way to power speakers all over the house. I keep hearing Assist but don’t see how it replaces a media player. This one a priority for me and love how it works now. Is anyone aware of another platform that can do it , like Homebridge or Node Red,and could that be controlled from a Home Assistant dashboard?
Hey @garethsnaim, have you tried the follow workaround that was posted on Github?
Through trial and error trying to figure out the flow sequence, I was able to trick it and get to the OTP window.
After you’ve cycled through name, password and back to name, select the option Create Account New to Amazon? Fill in a first & last name (anything at all as not going to matter so “Q W” is quick and easy to type!)
Amazon will then inform you that an account with your email already exists.
At that point re-select “Sign in Already a customer?” and proceed with the email and password windows and then the OTP window should appear.
By that point though, the integration generated OTP has likely expired but you can just enter your current app generated OTP code and it should work.
If it returns to the integration add window and it just sits and spins and never progresses, that likely means the proxy listening session has expired and you’ll have to repeat the process.
