Media players are no longer being updated and it probably wont be fixed.
Read it yourself and come to your own conclusions 
Yeah, that doesn’t mean it’s been abandoned. So please don’t spread that miss information.
Huh? I said it was dead, not abandoned? Did you not read the same thing I read?
A quote from one of the devs
“Given the trends, I’m expecting for Amazon to shut down the ecosystem soon. So not in my roadmap but I will take PRs of people figure it out without just spiking the polling. That’s why it’s tagged as help wanted.”
Im sure miss information is a nice girl but I dont know her 
Alexa Media Player has been in this state for 5+ years. This is nothing new. The API has always been reverse engineered and has always had the chance for it to be killed at any moment by Amazon. Nothing has changed.
2 Likes
Is there any information on how to use the tts.cloud_say support that is listed in the newer versions?
Hi all,
Im trying to add another account into Alexa media player. Is this posable?
When I try I get the dredded
500 Internal Server Error
Server got itself in trouble
Any info would be great 
Just updated Alexa Media Player addon to version 4.9.0
It says added suport for Amazon Smart Plug.
How do I use this?
Kindly guide.
Mee too. Updated to 4.9.0 and HA 2024.1.
I have an Amazon Smart Plug configured with 2 Echo. The 2 Echo works well with the integration as media players but Amazon Smart Plug entity doesn’t appear.
I tried to make a reconfiguration and checked the box for “Include devices connected via Echo” but nothing happen.
Any advice? Thanks
Please Add Integration for Alexa Alarms REST API to Manage Alarms
I frequently find myself needing to manage my Alexa alarms directly from Home Assistant, but currently, the “alexa_media_player” integration lacks the functionality to interact with Alexa alarms. This means every time I need to set or edit alarms, I have to switch to the Amazon Alexa app, which is inconvenient and disrupts the workflow of managing all smart home components from a single interface.
I would like the “alexa_media_player” integration to include support for managing Alexa alarms via the Alexa Alarms REST API. This integration should allow users to create, update, delete, and query Alexa alarms directly from Home Assistant. This would provide a seamless experience and fully integrate Alexa’s alarm functionality into the Home Assistant ecosystem, enhancing the usability and functionality of both platforms.
As an alternative, I have considered using other automation tools within Home Assistant to trigger events that simulate alarm behaviors, but these do not integrate with the actual Alexa alarms and lack the native functionality and ease of use that direct integration would provide. Additionally, using voice commands through Alexa-enabled devices is another workaround, but it lacks the automation and scheduling capabilities that could be achieved through API integration.
This feature would replicate the functionality available in the Amazon Alexa app, where users can manage their alarms. Including this in the “alexa_media_player” would align with the project’s goal of mirroring the app’s capabilities within Home Assistant. Here is the link to the official Alexa Alarms REST API documentation for reference: Alexa Alarms REST API.
Feature requests for the Alexa Media Player custom integration should be submitted to the integration’s github repo.
Hi, I’ve managed to break my previously working AMP integration by using the new Reconfiguration page and entering a device id in “Include”. All the existing entities from AMP are now no longer available.
I read the docs and understand now that if I use include it means ONLY include.
I have tried removing what I entered, but every time I blank the entity name in Include and then Save, the entity name still appears.
Any tips? Thanks
Update1 - I replaced the named entity with a single space char, but that didn’t fix it either
Update2 - the actual media players are not working either “Action notify.alexa_media not found”.
Lots of errors in the log like this (# = redacted):
2024-12-15 18:07:41.301 ERROR (MainThread) [homeassistant.config_entries] Error unloading entry ########################- amazon.co.uk for switch
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 855, in async_unload
result = await component.async_unload_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/switch/__init__.py", line 99, in async_unload_entry
return await hass.data[DATA_COMPONENT].async_unload_entry(entry)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in async_unload_entry
raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!
Update 3 - I managed to fix it by editing the file config.storage\core.config_entries. I found the config for "domain":"alexa_media" and edited the attribute "include_devices" so that it was an empty string rather than a space. I restarted HA and all, my devices and entities were back again.
So, in conclusion, I will raise an issue that it is impossible to remove all included devices once you have entered any.
Hello,
do the alexa aliases work? i setup alias but nothing happen.
That’s unrelated to alexa media player. Aliases are for the cloud integration or alexa smart home skill.
Please create a separate thread.
Good day,
I would like to hear a message on my Alexa when a specific sensor is triggered, for example, a door sensor. So, Text-to-Speech. What do I need for this? Do I have to activate the cloud function in Home Assistant for it? In ioBroker, this was relatively easy to set up. Sorry for this question, I’m new to Home Assistant.
I’ve been quite happy with my setup, where my Alexa devices provide announcements of various HA events. I’m using the following pieces:
- HA Cloud (Nabu Casa account & subscription)
- HACS integration
- Alexa MediaPlayer integration within HACS
- Chime TTS integration within HACS
Let us know if you’ve got questions after digging into those compoonents.
Is there anyway to automate the switching of spotify accounts? My wife and I both have individual spotify accounts and both of our amazon accounts are in my amazon family profile. I have to go in through the alexa app and login with a different account if I want to change which spotify account the echo uses.
@jiggahertz86
I released update v1.0.109 of the SpotifyPlus Integration a couple of days ago that fixes an issue re-awakening Amazon Alexa devices. I was not able to test it with multiple Amazon accounts though, so I can’t say if it will fix this problem or not. It might be worth a try though.
To test:
-
play some Spotify on the selected Amazon device using your wife’s Spotify account.
-
from the SpotifyPlus Card using YOUR Spotify account, select the same Amazon device to transfer control.
- Or you can issue a service call if you want to do it programmatically (change
entity_idto your SpotifyPlus account entity, anddevice_idto the Amazon device name):
action: spotifyplus.player_transfer_playback
data:
entity_id: media_player.spotifyplus_todd_l
device_id: Echo Dot 01
play: true
The questions I have would be:
- do you see the Amazon device in your SpotifyPlus Integration
source_list/ or in the SpotifyPlus Card device list when your wife’s account has control of the device?
I still might be able to fix this, but would need to do some digging.
If you don’t have the time to mess with it I understand, and no hard feelings.
UPDATE - here’s a list of reddit threads that relate to the same problem.
Hope it helps!
Has anything changed recently, some of my mp3s no longer play ?
Here are the two files. az now no longer plays ? The other works perfectly fine ?
-rw-r--r--. 1 root root 4079 Jan 3 2024 AMFMBEEP-converted.mp3
-rw-r--r--. 1 root root 1227605 Jan 3 2024 az-converted.mp3
[root@instance-20221102-1738 local]# file az-converted.mp3
az-converted.mp3: Audio file with ID3 version 2.4.0, contains:MPEG ADTS, layer III, v2, 48 kbps, 16 kHz, Stereo
[root@instance-20221102-1738 local]#
[root@instance-20221102-1738 local]# file AMFMBEEP-converted.mp3
AMFMBEEP-converted.mp3: Audio file with ID3 version 2.4.0, contains:MPEG ADTS, layer III, v2, 48 kbps, 16 kHz, Stereo
The device does show up in my list but when I try to play to this device this is the behavior:
Calling spotifyplus.player_transfer_playback with my account to the device returns the following error:
2025-05-12 20:19:47.403 WARNING (SyncWorker_29) [spotifywebapipython.spotifyclient] Verification timeout waiting for Amazon Spotif
y Connect device "Echo Office" (74313510-859a-44d3-9411-7536a3d706b7_amzn_1) to become the active device; device not activated wit
hin 5.000000 seconds of Connect
2025-05-12 20:19:47.760 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [546699514864] Not found.
@jiggahertz86
At this point, I am not sure if this problem is due to the breaking changes that Spotify made on 05/07 or if it’s related to Alexa processing.
I would suggest removing your SpotifyPlus SP_DC / SP_KEY configuration options, and try the request again.
You could also upgrade to the latest SpotifyPlus version that was released today, which removes those credentials.
The Spotify change removed access to those credentials, and also caused transfer playback errors for any device.