Alexa Media Player Integration

justinhow · July 5, 2025, 9:31am

I had a power outage this morning and although the Home Assistant VM did not crash (I have it on UPS and powered the server down), since restarting the HA VM I am now getting this error and all Echo devices are unavailable:

Logger: alexapy.helpers
Source: runner.py:154
First occurred: 10:19:42 (2 occurrences)
Last logged: 10:19:42

alexaapi.get_guard_details((<alexapy.alexalogin.AlexaLogin object at 0x7f3f342c5010>,), {}): An error occurred accessing AlexaAPI: An exception of type TypeError occurred. Arguments: ("'NoneType' object is not subscriptable",)
alexaapi.get_network_details((<alexapy.alexalogin.AlexaLogin object at 0x7f3f342c5010>,), {}): An error occurred accessing AlexaAPI: An exception of type TypeError occurred. Arguments: ("'NoneType' object is not subscriptable",)

It is not offering me to re-authenticate and I am at a loss as what to do.
Version Details:

Alexa Media Player is 5.7.2
Installation method: Home Assistant OS
Core: 2025.7.1
Supervisor: 2025.06.2
Operating: System 15.2
Frontend: 20250702.1

justinhow · July 5, 2025, 10:22am

I have restored a previous HA backup and problem persists which makes me think this is probably an Amazon Alexa side change/authentication issue.

P6Dave · July 5, 2025, 12:10pm

There appears to be an issue with this. Check the Known Issues on the integration page " No Alexa devices or entities appear after successful login (2FA OK, no errors) #2934"

Dominicd · July 5, 2025, 1:34pm

same problem here ! even downgrading to 2025.7.0, problem persists

finity · July 5, 2025, 3:47pm

Same here. restarted a few times and AMP entities are unavailable.

watching to see if there’s any resolution.

WarLion · July 5, 2025, 3:57pm

It seems that Amazon is performing maintenance on the servers. This error is also appearing on Alexa devices and Alexa Media Player

https://api.amazonalexa.com/

github.com/home-assistant/core

Alexa devices; Failed setup, will retry: 299 is not a valid HTTPStatus

opened 02:30AM - 05 Jul 25 UTC

cmgestevao

integration: alexa_devices

### The problem New error with HA last update 2025.7.1 It was working well sinc…e 2025.7.0 ### What version of Home Assistant Core has the issue? core-2025.7.1 ### What was the last working version of Home Assistant Core? core-2025.7.0 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue Alexa Devices ### Link to integration documentation on our website https://www.home-assistant.io/integrations/alexa_devices ### Diagnostics information ``` 2025-07-05 03:12:35.068 DEBUG (MainThread) [aioamazondevices] GET request: https://alexa.amazon.com/api/bluetooth with payload None [json=False] 2025-07-05 03:12:35.068 DEBUG (MainThread) [aioamazondevices] Adding <{'csrf': '-951072826'}> to headers 2025-07-05 03:12:35.304 DEBUG (MainThread) [aioamazondevices] Cookies from headers: {} 2025-07-05 03:12:35.305 DEBUG (MainThread) [aioamazondevices] Response 200 for url https://alexa.amazon.com/api/bluetooth with content type: application/json 2025-07-05 03:12:35.306 DEBUG (MainThread) [aioamazondevices] Response URL: https://alexa.amazon.com/api/bluetooth 2025-07-05 03:12:35.306 DEBUG (MainThread) [aioamazondevices] Response code: |200| 2025-07-05 03:12:35.306 DEBUG (MainThread) [aioamazondevices] JSON data: |{'bluetoothStates': [{'deviceSerialNumber': REDACTED ,'deviceType': 'A2IVLV5VM2W81', 'friendlyName': None, 'gadgetPaired': False, 'online': False, 'pairedDeviceList': None, 'sconeBattery': None, 'sconePaired': False, 'softwareVersion': '35602678', 'streamingState': None}]}| 2025-07-05 03:12:35.307 DEBUG (MainThread) [aioamazondevices] GET request: https://alexa.amazon.com/api/phoenix with payload None [json=False] 2025-07-05 03:12:35.307 DEBUG (MainThread) [aioamazondevices] Changing User-Agent to Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36 Edg/138.0.0.0 2025-07-05 03:12:35.307 DEBUG (MainThread) [aioamazondevices] Adding <{'csrf': '-951072826'}> to headers 2025-07-05 03:12:35.472 DEBUG (MainThread) [aioamazondevices] Cookies from headers: {} 2025-07-05 03:12:35.472 DEBUG (MainThread) [aioamazondevices] Response 299 for url https://alexa.amazon.com/api/phoenix with content type: application/json 2025-07-05 03:12:35.472 ERROR (MainThread) [homeassistant.components.alexa_devices] Unexpected error fetching [email protected] data Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 382, in _async_refresh self.data = await self._async_update_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/alexa_devices/coordinator.py", line 54, in _async_update_data return await self.api.get_devices_data() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aioamazondevices/api.py", line 809, in get_devices_data entity_ids_list = await self._get_devices_ids() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/aioamazondevices/api.py", line 580, in _get_devices_ids _, raw_resp = await self._session_request( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<3 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/aioamazondevices/api.py", line 407, in _session_request f"Request failed: {HTTPStatus(resp.status).phrase}" ~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/enum.py", line 726, in __call__ return cls.__new__(cls, value) ~~~~~~~~~~~^^^^^^^^^^^^ File "/usr/local/lib/python3.13/enum.py", line 1201, in __new__ raise ve_exc ValueError: 299 is not a valid HTTPStatus 2025-07-05 03:12:35.481 DEBUG (MainThread) [homeassistant.components.alexa_devices] Finished fetching [email protected] data in 1.521 seconds (success: False) ``` ### Example YAML snippet ```yaml ``` ### Anything in the logs that might be useful for us? ```txt ``` ### Additional information ![Image](https://github.com/user-attachments/assets/07de7bd9-df16-4295-b2a5-fc714db86445)

so if you still had a working AMP or AD dont you dare restart you home assistant or integration or you will be unable get a token

justinhow · July 6, 2025, 9:05am

I can confirm that Alexa Media Player 5.7.3 update fixes this issue. Thanks!

rddelacosta · September 25, 2025, 1:46pm

Hi everyone. I’ve been trying to use this to show an image to my echo show but this just does not work (the message part works but not the image) - does anyone know how to make this work? Thanks:

action: notify.alexa_media
data:
  message: Hi
  title: Hello
  data:
    image: "https://upload.wikimedia.org/wikipedia/commons/thumb/1/15/Cat_August_2010-4.jpg/1920px-Cat_August_2010-4.jpg"
  target: media_player.show_10k

Ltek · November 18, 2025, 4:59pm

guys is TTS broken in AMP? It was working fine for a long while but a few weeks ago it stopped working for me. I wrote up a project that leverages it, and while the volume controls and such work fine, the TTS does not work at all.

Any fix?

finity · November 22, 2025, 4:23am

Have you tried updating to the latest version of AMP? It was broken in the last couple of weeks due to a change on the Amazon end but the latest version (I think it’s 5.7.13) has been working for me for a few days now.

gil1 · November 22, 2025, 4:12pm

I’m running Version 5.7.13 at the moment. When I upgraded HA core to 2025.11.3 it immediately broke AMP. Anyone else see this? Any ideas on repair? Thanks…

Ltek · November 22, 2025, 5:40pm

All my devices showed ‘unavailable’ so after a few re-auth attempts I just tried removing and re-adding the Amazon account… AMP is dead it looks like since no devices are being pulled in now.
log shows…

Error fetching alexa_media data: Error communicating with API: object of type 'NoneType' has no len()

EndUser · November 22, 2025, 10:00pm

Same with me.

I keep getting this when copying the authentication key from my Google Authenticator:

Invalid Authenticator App key for Amazon 2SV

finity · November 23, 2025, 1:07am

…sigh… that’s unfortunate…again…

poudenes · November 23, 2025, 8:49am

Hey All,

EDIT: After visiting Github I see an issue because of HA 2025.11.3. I think this will also be the issue for me with 2025.11.4:

github.com/alandtse/alexa_media_player

all echos are unavailable since latest core (2025.11.3) update

geopend 08:33AM - 23 Nov 25 UTC

bEdA8101

**IMPORTANT: Please search the issues, including closed issues, and the [FAQ](ht…tps://github.com/alandtse/alexa_media_player/wiki/FAQ) before opening a new issue. The template is mandatory; failure to use it will result in issue closure.** **Describe the bug** **To Reproduce** 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** **Screenshots** **System details** - Home Assistant version: - alexa_media version (from `const.py` or HA startup log): - alexapy version (from `pip show alexapy` in homeasssistant container or HA startup log): - Is Amazon [2SV via Authenticator App](https://github.com/alandtse/alexa_media_player/wiki/Configuration#enable-two-factor-authentication-for-your-amazon-account) (not 2SV OTP via SMS) enabled? (y/n): - Amazon Domain: **Debug Logs (alexa_media & alexapy)** Please provide [logs](https://github.com/alandtse/alexa_media_player/wiki/FAQ#how-do-i-enable-debug-logging-for-the-component). **Additional context**

Original post:

Alexa Media Player: Version 5.7.13
Installation methodHome Assistant OS
Core2025.11.3
Supervisor2025.11.4
Operating System16.3
Frontend20251105.1

Also my integration stopped working. Then did those steps

remove the integration
restart HA
add the integration again
add credentials and created a 2SV
used the code to verify the new app
marked: Yes, OTP code was verified
got a new window to login into my amazon account.
back to HA: Created configuration for amazon_us@ - amazon.com

Only see the integration part where you can change the settings.
No echo is shown (Echo Livingroon, Echo Bedroom)

Do I still something wrong?

Error logs:

Logger: homeassistant.config_entries
Source: config_entries.py:975
First occurred: 09:52:55 (5 occurrences)
Last logged: 09:52:55

Error unloading entry amazon_us@<MY DOMAIN> - amazon.com for media_player
Error unloading entry amazon_us@<MY DOMAIN> - amazon.com for switch
Error unloading entry amazon_us@<MY DOMAIN> - amazon.com for sensor
Error unloading entry amazon_us@<MY DOMAIN> - amazon.com for light
Error unloading entry amazon_us@<MY DOMAIN> - amazon.com for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 975, in async_unload
    result = await component.async_unload_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/media_player/__init__.py", line 487, in async_unload_entry
    return await hass.data[DATA_COMPONENT].async_unload_entry(entry)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 228, in async_unload_entry
    raise ValueError("Config entry was never loaded!")
ValueError: Config entry was never loaded!

Logger: custom_components.alexa_media
Source: helpers/update_coordinator.py:435
integration: Alexa Media Player ([documentation](https://github.com/alandtse/alexa_media_player/wiki), [issues](https://github.com/alandtse/alexa_media_player/issues))
First occurred: 09:53:02 (1 occurrence)
Last logged: 09:53:02

Error fetching alexa_media data: Error communicating with API: object of type 'NoneType' has no len()

gil1 · November 24, 2025, 4:46am

The update I received tonight corrected the problem. Thanks folks, much appreciated…