Alexa media player - Unavailable

Configuration
1

I hope that his is a easy fix, as I have google this and for some reason - I am not able to get my Alexa media to work.

the issue is that when I go to my Alexa media integration, I am inform that it an see the different Echo devices I have, but when I click on one to see it settings, I am information that it is unavailable.

I have delete and re-add the integration, but with no joy.
I have made sure I had no firewalls or VPN running, I have rebooted my HA a few times, and each time when I check I am informed that it is unavailable

within the logs I am getting

Logger: custom_components.alexa_media
Source: custom_components/alexa_media/init.py:1050
Integration: Alexa Media Player (documentation, issues)
First occurred: 14:59:24 (1 occurrence)
Last logged: 14:59:24

c******@**********u: Network Discovery: AlexaAPI returned an unexpected response. Retrying on next polling cycle

I hope this is a bug, and not my system I am current on

CORE 2026.6.3
Supervisor 2026.06.2
OS 18.0
Frontend 20260527.6

and my Alexa media version is Version 5.15.4

2

While others may disagree, AMP is heading towards EOL. Core's Alexa Devices integration is, in several cases, already better (better meaning, stable, faster, more intuitive, and more functional) than AMP. It's only missing connected devices and Fire TV media_player controls, but there's already a PR for the Fire TV controls. It has features that AMP doesn't have, like voice attributes, routine buttons, and AQI. Next month's core release looks to include Alexa todo features, which will bring in the Alexa Shopping list, task list, and custom lists into HA. The devs are also interested in streamlining MA integration and have recently reached out to the Music Assistant team in this regard. Here's a recent article about it with more info.

3

Is there a way for "last alexa" as in the custom one in the meantime? Do not find anything in the docs till now. One reason, that I'm still on amp and really needed to get the output in skills where I started my voice commands.

4

Is last_alexa actually reliable for you...? It hasn't been for me for over a year.

Be that as it may, you can now create an equivalent template sensor based on AD's "Voice Event" entities for each device. The following will return the entity ID of the most recently updated voice event:

{{ integration_entities('alexa_devices')
| select('search', '_voice_event')
| select('has_value')
| expand
| sort(attribute= 'state',reverse=true)
| map(attribute= 'entity_id')
| first }}
5

Longer time in between, no, last times, yes, again.

Thanks for the approach. Will give it a try.