Alexa Media Player - Custom Integration - On Life Support - Help wanted

[davidm (David Miller)]

I make heavy use of this integration in my Home Assistant configuration, to play alert sounds and speak notifications on multiple Alexa devices around the house. This all stopped working after I updated to HA Core 2024.5.5 last night. I came to these forums to request help, and saw this post - so I guess there are bigger problems.

There is an update available which I will try - I’m still using 4.9.0 which is several versions out of date.

However, given how incredibly useful I find Alexa Media player, if the original developer is no-longer able to maintain it I wonder whether the Home Assistant team could consider promoting it to an official integration. There must be a lot of Home Assistant users with Alexas who would benefit from this.

[aruffell]

@davidm

I wonder whether the Home Assistant team could consider promoting it to an official integration

While I would love this, I believe the founder once mentioned how difficult it was to keep this integration alive due to constant changes, I assume, on Amazon’s side.

Given all we use our dozen+ echos is for timers, announcements and above all home control via HA, I am looking forward to a good looking, well built/packaged HA Assist solution. Just like I de-applefied my household years ago, I will also de-amazon my house as well.

[dbrunt (Daniel)]

@chemelli

I’m interested in people testing the login process and confirming is working

Confirmed working with --country CA and using \$ rather than S in my password.
OTP came from Bitwarden.
Also tested library_test.json (which does need the $ in the password escaped).

python library_test.py --configfile library_test.json

[handcoding (Ashley Bischoff)]

In case it might be helpful to anyone else, this comment has a fix that got Alexa Media Player working for me again with HA 2024.8.0.

To recap the fix:

1. First, using Visual Studio Code (or any other file editor of your choice), open this file:
   /homeassistant/custom_components/alexa_media/manifest.json

2. 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"],

3. Then reboot Home Assistant.

PS Full credit to sca075 within that issue thread for this fix.

[Yomegaman (Mike Caffrey)]

handcoding - your fix worked for me … Thanks!

[Javisendra (Javier)]

I only see one temporary solution and that is to go back to the July OS version. The problem is to see if someone can offer that version for downgrade.

[mhoogenbosch (Martijn Hoogenbosch)]

Doesn’t the latest version just work? I’m using 4.12.8 and it works on 2024.8.2 just fine for me.

[Duke_box]

+1 from me.

2024.8.2 AMP version 4.12.10 just works!

[aruffell]

I still have to do at least one reload and/or reconfigure and then it works.

[Paul_Biod]

Thank you so much, now my AMP is working again.

[andresrdz (Andres)]

Is there any way to make Alexa devices work with MQTT or matter as a way to break away from the Amazon API madness described here ?

[michael.schoenegger]

Hi,
i have HO version 2024.9.2 and Alexa version 4.13.1 installed.
When i try to add the integration, i’m forwarded to the Alexa webpage for login, but every time i log in it refreshes the site and nothing happens.

Does anyone have this issue and does anyone have a solution?
P.S. i had the integration working for a couple of months and it stopped working, so i tried to reconfigure it.
Thanks

[Holdestmade]

Does this work for you ?

Alexa Media Player failing at startup

The problem is the new three page login sequence with email, then password, then 2SV AMP was programmed to do the callback after two pages (the way the Amazon login used to be) but gets an “unsuccessful” response after only two pages since the login sequence did not finish all three pages and AMP returns you to the previous (first) page to try again. So… At this screen, select the first option [image] Enter “x x” for First and last name and click CREATE YOUR AMAZON ACCOUNT [image] When t…

[michael.schoenegger]

Yes, thanks a lot. This worked for me.

[delboydell]

just found this post, and tried as above and it went back to home assistant with a failed message.!

[stephanschleichstr13]

@petro Make it sence that someone create a PR with the “Open source compliance” from 2024.9 so we dont need the old creater? Or i miss understand the function from that?

[ravioli-pretzel]

Are there more specific how to get involved instructions? @petro just posted a link to the github repo, which is a good start. But I guess I’m looking for a planning thread or something. Who’s working on what, what’s needed, what are the biggest issues, what’s the long term direction, etc.

[collelog]

I tested aioamazondevices.

Amazon-JP returns the first request response with an error screen, so the command fails in the form data parsing process (KeyError: ‘method’).

For Amazon-JP, the request parameter “openid.asset_handle=amzn_dp_project_dee_ios” needs to be replaced with “openid.asset_handle=jpflex”.

• Non-existent account.
  Before:
  An error occurs and the command is aborted.
  After:
  processing As a result of command execution, “Cannot authenticate with [email protected] credentials” is displayed.

• Correct account.
  Before:
  An error occurs and the command is aborted.
  After:
  the command is executed, device information is displayed.

[petro]

Please write this up on the github page, also provide the steps you ran.