The problem
The problem
Transport actions on an Alexa Devices media_player entity (media_pause, media_play,
media_next_track, media_previous_track) fail. The request goes to a malformed host —
"alexa.amazon.comapi" instead of "alexa.amazon.com". The slash between the base domain
and the "/api/np/command" path is missing, so the hostname becomes "alexa.amazon.comapi",
which doesn't resolve (NXDOMAIN → "Domain name not found"), and the action raises CannotConnect.
Device discovery, state, and announcements all work normally — only the np/command path is
affected, which points to URL construction specific to that endpoint rather than a network,
DNS, or auth issue.
What version of Home Assistant Core has the issue?
core-2026.6.4
What was the last working version of Home Assistant Core?
Not sure
What type of installation are you running?
Home Assistant OS (OS 18.0, Supervisor 2026.06.2)
Integration causing the issue
alexa_devices
Link to integration documentation on our website
https://www.home-assistant.io/integrations/alexa_devices/
Example YAML snippet
action: media_player.media_pause
target:
entity_id: media_player.your_echo
Anything in the logs that might be useful for us?
Source: components/alexa_devices/media_player.py:270
Connection error to https://alexa.amazon.comapi/np/command?deviceSerialNumber=&deviceType=:
ClientConnectorDNSError(ConnectionKey(host='alexa.amazon.comapi', port=443, is_ssl=True, ssl=True,
proxy=None, ...), OSError(None, 'Domain name not found'))
Resulting service-call failure:
Error during service call to media_player.media_pause: Error connecting: CannotConnect('Connection error during POST')
Note the host "alexa.amazon.comapi". Correctly-formed requests elsewhere (e.g. /api/bootstrap)
include the slash; only the np/command URL omits it.
Additional information
US account, amazon.com domain. Device list and announcement/notify actions function normally;
only transport controls (np/command) fail. Diagnostics attached.
What version of Home Assistant Core has the issue?
core-2026.6.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
alexa_devices
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response
The problem
The problem
Transport actions on an Alexa Devices media_player entity (media_pause, media_play,
media_next_track, media_previous_track) fail. The request goes to a malformed host —
"alexa.amazon.comapi" instead of "alexa.amazon.com". The slash between the base domain
and the "/api/np/command" path is missing, so the hostname becomes "alexa.amazon.comapi",
which doesn't resolve (NXDOMAIN → "Domain name not found"), and the action raises CannotConnect.
Device discovery, state, and announcements all work normally — only the np/command path is
affected, which points to URL construction specific to that endpoint rather than a network,
DNS, or auth issue.
What version of Home Assistant Core has the issue?
core-2026.6.4
What was the last working version of Home Assistant Core?
Not sure
What type of installation are you running?
Home Assistant OS (OS 18.0, Supervisor 2026.06.2)
Integration causing the issue
alexa_devices
Link to integration documentation on our website
https://www.home-assistant.io/integrations/alexa_devices/
Example YAML snippet
action: media_player.media_pause
target:
entity_id: media_player.your_echo
Anything in the logs that might be useful for us?
Source: components/alexa_devices/media_player.py:270
Connection error to https://alexa.amazon.comapi/np/command?deviceSerialNumber=&deviceType=:
ClientConnectorDNSError(ConnectionKey(host='alexa.amazon.comapi', port=443, is_ssl=True, ssl=True,
proxy=None, ...), OSError(None, 'Domain name not found'))
Resulting service-call failure:
Error during service call to media_player.media_pause: Error connecting: CannotConnect('Connection error during POST')
Note the host "alexa.amazon.comapi". Correctly-formed requests elsewhere (e.g. /api/bootstrap)
include the slash; only the np/command URL omits it.
Additional information
US account, amazon.com domain. Device list and announcement/notify actions function normally;
only transport controls (np/command) fail. Diagnostics attached.
What version of Home Assistant Core has the issue?
core-2026.6.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
alexa_devices
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
Additional information
No response