Support for Alexa Media Player #431
Replies: 81 comments 265 replies
-
|
I've inspected this today and so far I see no easy way to make that work. The Alexa Media Player does not allow to just send a stream URL to play which is what this integration needs. The only way to make this work properly is if somebody creates a custom Alexa skill that communicates with this integration. I do not own a Alexa device so I can't do that. A little googleing I just did quickly led me to several 3rd party solutions you could use to turn the Echo device into a unpnp receiver or squeezebox player. For example: https://www.amazon.com/ComputeQ-UG-Haftungsbeschr-Roomskills-Squeezebox/dp/B0983C2377 I'm happy to work with somebody to make this work but without an actual Alexa/Echo device to test with, this is not something I can start with alone |
Beta Was this translation helpful? Give feedback.
-
|
I would gladly help, I'm not a developer, but I would help by testing it on my echos, unfortunately I'm located in Spain and the skill you pointed can be only installable on US echos (perhaps on DE as well, as per language selection) |
Beta Was this translation helpful? Give feedback.
-
|
I don't know how the SpotCast integration works but I'm able to play music from spotify on my alexa devices from Home Assistant, I don't believe a skill is needed. |
Beta Was this translation helpful? Give feedback.
-
|
@mabrochu-helpox how do you bring the Alexa's into HA as media players though? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
To be clear, this is not the official Alexa integration built into HA. This is a custom integration known as Alexa Media Player. It is found here: https://github.com/custom-components/alexa_media_player |
Beta Was this translation helpful? Give feedback.
-
For Music Assistant to work it is required that the enddevice (the speaker) supports "play from url". Music Assistant is not about playing Spotify on a speaker. Music Assistant is about playing all your online en offline media to a collection of speakers. The Spotcast implementation (and others like the alexa custom integration) send Spotify commands to the Echo speaker, not plain urls |
Beta Was this translation helpful? Give feedback.
-
|
Its hacky but you can send urls like this: Probably not the intended use but im curious if there is another api we that could be leveraged ? |
Beta Was this translation helpful? Give feedback.
-
|
Enjoyed the Open Home Audio stream with you all! Very impressive stuff all around! @marcelveldt Music Assistant seems great, and opens a world of possibilities! I just wanted to offer up a potential path forward for supporting Echo devices, and that would be using them as a bluetooth audio target. I regularly pair my Echo with my Macbook via bluetooth, and set it as my output device. No special hardware of configuration needed, just the Amazon Alexa app: The simplest solution is to pair your Echo(s) with the host OS, and use them as system output device(s) - of course, that may incur limitations regarding targeting specific connected devices/groups Traditionally, Bluetooth radios have supported a single audio streaming device per chip (except for a few specialist radios) - so 1 dongle = 1 speaker, 2 dongles = 2 speakers, etc.... However, the recent Bluetooth LE specification also adds "multi device audio streaming" from a single radio, I believe using the LC3 codec. Here's some reference links: https://www.bluetooth.com/learn-about-bluetooth/recent-enhancements/le-audio/
|
Beta Was this translation helpful? Give feedback.
-
|
Additional: I came across an article from last year on Mark Lewis's Blog, in which he configures audio with a bluetooth dongle on Home Assistant OS, seemed fairly simple: https://marklewis.blog/2021/02/25/home-assistant-bluetooth-speaker/ Mark was using a "Local VLC" community addon as a player, but I'm sure there's other things that can be done |
Beta Was this translation helpful? Give feedback.
-
|
would we possibly be able to use something like this: https://www.youtube.com/watch?v=NoCPUypkimc&ab_channel=DabbleLab as a base for a custom skill to be able to play media from a url on amazon devices? |
Beta Was this translation helpful? Give feedback.
-
|
Moved to discussions, raise your votes! |
Beta Was this translation helpful? Give feedback.
-
|
I think we would need to create a music provider following https://developer.amazon.com/en-US/docs/alexa/music-skills/understand-the-music-skill-api.html and then hook into that via alexa_media_player through alexapys |
Beta Was this translation helpful? Give feedback.
-
|
Not a coder, just a dabler. From what I understand. Activating this skill will have the backend load up an audio stream. The URL in this stream could be changed to point to your home assistant instance (or I believe nabu casa URL) for the .m3u file. If it's possible to code an audio stream, then we could use this skill. The scenario would be to have the audio stream process start when opening the media player If this is achievable, then we could adapt the stream URL to other players. Using a m3u app on your phone to stream is one example that comes to mind. Edit: |
Beta Was this translation helpful? Give feedback.
-
|
Any more progress on using the Alexa Media Player integration in conjunction with this? |
Beta Was this translation helpful? Give feedback.
-
|
It may be explained there, but it's confusing. It's hard to tell where it's step-by-step instructions and where it's presenting options. The README really needs to be rewritten and clarified.
…
On Sep 29, 2025 at 3:03 PM, Alexandre GHEZ ***@***.***> wrote:
Look at this project. All is explained :
https://github.com/alams154/music-assistant-alexa-api
Le lun. 29 sept. 2025 à 17:14, SKAL ***@***.***> a écrit :
> so, where should I have to set them? sorry... I don't understand. :-( I
> feel so dumb
>
> —
> Reply to this email directly, view it on GitHub
> <#431 (reply in thread)>;,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/APNY55QBCJ56POVG7TZ6ZK33VGOLNAVCNFSM5ZFEEO42U5DIOJSWCZC7NNSXTOSENFZWG5LTONUW63SDN5WW2ZLOOQ5TCNBVGQ3DENZW>;
> .
> You are receiving this because you commented.Message ID:
> ***@***.***
> com>
>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
No audio for me. Everything is set up according to the guide. I have https access to the api container, and am able to stream via https connection to the MA streamer (Thanks @spiegela for writing up the troubleshooting guide). I can change volume on my echo devices, however no music plays. I do have this in my Alexa logs: { UPDATE: I'm able to get the skill to play audio directly in the testing tab in the dev console AND on a Samsung soundbar. None of my 2nd-5th gen dots are able to play the stream. |
Beta Was this translation helpful? Give feedback.
-
|
@nholben that is strange. I have it working with a 5th Gen Dot. Particularly strange, if its working playing to one device but not another -- is it possible that the soundbar is actually using a different protocol (like Airplay, Google Cast, etc.)? You might also ensure that DNS is resolving as you expect from outside your local network. For this I use $ nslookup
> server 1.1.1.1
Default server: 1.1.1.1
Address: 1.1.1.1#53
> mass-stream.example.com
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
Name: mass-stream.example.com
Address: X.X.X.YIf DNS is working externally, and since you're able to stream from using VLC or a browser, then I would suspect the Alexa skill code. I would log the |
Beta Was this translation helpful? Give feedback.
-
|
Just addidng in case its helpful here as had similar to others above with no audio. I found the language in the alexa skill needs to match the device / lcoation. My device was English (UK) and skill was English (US), added the language in the dev console. Because of the new language, I had to add a custom intent for the English (UK) language with sample utterances. Build skill and then bingo, speaker works. Question - play / pause is not reflected in an alexa speaker in MA or does it work for others? |
Beta Was this translation helpful? Give feedback.
-
|
Have instead of avec. I will edit my comments.
Le ven. 3 oct. 2025 à 16:56, reryro ***@***.***> a écrit :
… Just an FYI...you use the word "avec" a couple times, which is not an
English word. But its translation to English ("with") doesn't seem to fit
your context either, so I'm not sure what you mean when you say avec.
—
Reply to this email directly, view it on GitHub
<#431 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APNY55RSWUT2PCO73Z7AV4D3V3PGXAVCNFSM5ZFEEO42U5DIOJSWCZC7NNSXTOSENFZWG5LTONUW63SDN5WW2ZLOOQ5TCNBVHA3TSMZW>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
I'm having a few issues still with this, so I'm running HAOS and so for simplicity's sake around running the container, I created a HA Addon for the music assistant alexa api and I've opened a PR @alexandreghez Below is my addon if anyone wants to try it in the meantime: I've got the skill added to alexa, ended up having to manually add it, as it just wouldn't import from the github link, not sure if related to the locale differences i.e. I'm en-GB and selected UK for hosting region too, but the locale file in the repo is en-US. Anyway I just renamed that file to en-GB.json and managed to create the skill.
Just wondered if anyone can spot what I'm doing wrong. Many thanks Andy |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
I did the same setup as @rinosaur681 but I keep getting "to get help, please contact amazon support". can someone help? |
Beta Was this translation helpful? Give feedback.
-
|
I struggled to get this to work until I changed the Echo device language to English (US) to match up with the skill language. (This is mentioned previously in the thread.) But it still isn't working quite as it should. If I initiate a track in MA, Alexa plays a random track which isn't in my MA library. (In the 'voice history' log in the alexa app on my phone it has 'Ask music assistant to play audio'.) But then, if I stop the track, and say 'Alexa, ask music assistant to play audio,' it plays the track I had originally initiated. It doesn't take long to start playing - about 5 seconds. And if I have set up a queue, it carries on as it should although there is no 'now playing' display in MA. So, although the MA/Coldflare setup appears to be working the music assistant skill does not work as it should with my first gen Echo. |
Beta Was this translation helpful? Give feedback.
-
|
Update: I changed both the Echo device language and the skill language to English (UK) as described by @fergalom. Now when I initiate a track from MA I don't get the random track playing. To get the MA track to play I have to do the 'Alexa, ask music assistant to play audio' business and it starts almost immediately. I have created a button with a script in HA to do this but would like to find a way to cut this extra step out. |
Beta Was this translation helpful? Give feedback.
-
|
I got the following error, if i am using my region amazon.de If i´m using the amazon.com i got this one: any ideas - so no devices shows up . alexa.mydomain.de -> pointing to 192.168.178.42:3000 (this is the API port for the bridge container, thats also running as a home assistant addon) - reachable from outside - {"error":"No URL available"} *edit: @spiegela also run through your troubleshoot after i start some music (Radio) on the music assistant on the device itself |
Beta Was this translation helpful? Give feedback.
-
|
alexapy was updated a few days ago to deal with this. It's probaby a matter of using the latest version in Music Assistant. |
Beta Was this translation helpful? Give feedback.
-
|
I'm running into the same Alexa Player Provider authentication issue others have reported. Here’s a clear summary of my setup, the behavior, and the logs in case it helps narrow things down. System context
Only Alexa Player Provider fails. Login behaviorMA starts the Amazon login normally:
From the logs: So the login itself is working:
Where it failsImmediately after cookies are exchanged, MA fails authentication and the Alexa provider never initializes. UI popup: Log output: Device discovery never starts. The Alexa API bridge is never contacted during this flow. Additional log lines during loginThese look like telemetry endpoints from Amazon’s login process. Alexa API Bridge sanity checkBridge responds and basic auth works: This means:
Things already tested
Same result every time. Likely failure point (inferred)Based on the logs and GitHub reports:
This matches multiple recent reports suggesting an Amazon-side API behavior change. Happy to supply more logs or enable additional debugging if needed. |
Beta Was this translation helpful? Give feedback.
-
|
Hey there, i have the same issue than @acolod but I can’t debug so good. Additionally I have a Dual Stack Lite Connection from my provider. So I can’t use IPv4. On a VPS I installed WireGuard. A Perfect Solution for it. Don‘t route the whole traffic! AllowedIPs! So i‘m very interested how to solve the issue. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
+1 for the same issue as @acolod |
Beta Was this translation helpful? Give feedback.





Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Current Status
As at August 2025 experimental support is available in the beta channel
Original Post
Trying to play music from Spotify to my Alexa devices, which are set as media devices using Alexa Media Player. Alexa gives an error stating that the proper service calls must be made.
If this could be integrated in some way, it would be a game changer for playing music via HA. Happy to test anything as needed.
Beta Was this translation helpful? Give feedback.
All reactions