Alexa Devices / Störung?

thorkillar · 29. Juni 2026 um 06:48

Guten Morgen,

seit einigen TAgen habe ich massiv Probleme mit allen Alexa Geräten in “Alexa Devices”.

Zuerst hatte ich das Problem, dann alle Entitäten “nicht verfügbar” waren.
Dann habe ich über neu laden und neue konfigurieren versucht, den Fehler zu beheben.
Auch ein Löschen und neue anlegen des HUBs hat nur dazu geführt, das das Problem wieder da war. (nicht verfügbar). Die u.g. Fehlermeldung kommt häufiger, wenn ich neu Konfigurere. Muss dann ein paar mal versuchen.

Habt Ihr Ideen, woran das liegen kann? Gibt es ein allgemeines Problem?

harryp · 29. Juni 2026 um 07:51

Ist bekannt und wird mit dem Release 2026.7.0 gefixet.

github.com/home-assistant/core

Alexa Devices: media_player transport commands fail — malformed host "alexa.amazon.comapi" (missing slash before /api/np/command)

offen 02:28AM - 28 Jun 26 UTC

davidtatwood

integration: alexa_devices

### The problem ### The problem Transport actions on an Alexa Devices media_pla…yer 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=<REDACTED>&deviceType=<REDACTED>: 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 ```yaml ``` ### Anything in the logs that might be useful for us? ```txt ``` ### Additional information _No response_

Bei mir hat geholfen das hier zu deaktivieren:

Thema		Antworten	Aufrufe
Alexa Devices Entitäten nicht verfügbar Integrationen	2	129	24. November 2025
Probleme mit Alexa Media Player & ALEXA Devices nach Core-Updates Allgemein	217	9416	12. November 2025
Alexa Media Player wieder Probleme? Allgemein	447	11282	18. Mai 2026
Umstellung von "media_player" zu "alexa core" Problem bei mehreren Geräten Automationen	28	920	4. Juli 2025
Alexa Entitäten nicht verfügbar Integrationen	12	2649	10. Oktober 2025

Alexa Devices / Störung?

Verwandte Themen