Sonos announcement doesn't work anymore

Third party integrations
1

Hi

For some reason the announcement feature for sonos stoped working and I can’t figure out why. Here ist the script:

announce: true
extra:
  volume: 20
media:
  media_content_id: /local/Soundeffects/announcement.mp3
  media_content_type: music
  metadata: {}

if I remove the “announce” part it works. If not, I get the error message:

Error when calling Sonos websocket: Unexpected response received: 503, message=‘Invalid response status’, url=‘wss://192.168.1.44:1443/websocket/api’

The log file doesn’t help me either:

2025-10-16 17:39:39.750 ERROR (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Error executing script. Error for call_service at pos 1: Error when calling Sonos websocket: Unexpected response received: 503, message='Invalid response status', url='wss://192.168.1.44:1443/websocket/api'
2025-10-16 17:39:39.750 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140598046547040] Error handling message: Error when calling Sonos websocket: Unexpected response received: 503, message='Invalid response status', url='wss://192.168.1.44:1443/websocket/api' (home_assistant_error)

The HA Server is in an other Subnet (192.168.2.x) where all my IoT devices resides with limited internet access (with exception of the HA server of corse), but that wasn’t an issue until now. And as mentioned, playing media in general isn’t a problem.

Can someone push me in the right direction to find the error?

Thanks in advance!

2

No one got an idea? It’s quite annoying, since I was heavily reliant on the announcement feature.

3

Hi,

I can just confirm i’m experiance the same problems using the announcement.

Example:

2025-10-22 20:35:49.999 ERROR (MainThread) [homeassistant.components.automation.hoveddoren_er_aben] Hoveddøren er åben: Error executing script. Error for call_service at pos 1: Error when calling Sonos websocket: Unexpected response received: 503, message='Invalid response status', url='wss://10.43.101.4:1443/websocket/api'
2025-10-22 20:40:32.994 ERROR (MainThread) [homeassistant.components.automation.hoveddoren_er_aben] Hoveddøren er åben: Error executing script. Error for call_service at pos 1: Error when calling Sonos websocket: Unexpected response received: 503, message='Invalid response status', url='wss://10.43.101.4:1443/websocket/api'

Using configuration as:

action: media_player.play_media
metadata: {}
data:
  media:
    media_content_id: >-
      media-source://tts/tts.google_translate_da_dk?message=Hovedd%C3%B8ren+er+%C3%A5ben&language=da
    media_content_type: audio/mp3
    metadata:
      title: Hoveddøren er åben
      thumbnail: https://brands.home-assistant.io/_/google_translate/logo.png
      media_class: app
      children_media_class: null
      navigateIds:
        - {}
        - media_content_type: app
          media_content_id: media-source://tts
        - media_content_type: audio/mp3
          media_content_id: >-
            media-source://tts/tts.google_translate_da_dk?message=Hovedd%C3%B8ren+er+%C3%A5ben&language=da
      browse_entity_id: media_player.kokken_h
  announce: true
target:
  area_id: kokken

The Sonos devices is running version 17.1 (build 85.0-65270)
And the devices that have the problem is Sonos Roams both gen 1 and 2.

However the cable connected ones Beam, and Play Ones does indeed work as expected like:

2025-10-22 21:37:20.113 DEBUG (MainThread) [homeassistant.components.sonos.media_player] Playing http://10.43.10.171:8123/api/tts_proxy/V1-RvZo9MvRLQVm6GnvvAw.mp3 using websocket audioclip
2025-10-22 21:37:20.113 DEBUG (MainThread) [sonos_websocket.websocket] Sending command: [{'namespace': 'audioClip:1', 'command': 'loadAudioClip', 'playerId': 'RINCON_542A1B89A41001400'}, {'name': 'Sonos Websocket', 'appId': 'com.jjlawren.sonos_websocket', 'streamUrl': 'http://10.43.10.171:8123/api/tts_proxy/V1-RvZo9MvRLQVm6GnvvAw.mp3'}]
2025-10-22 21:37:20.113 DEBUG (MainThread) [sonos_websocket.websocket] Websocket connection reset, will try again
2025-10-22 21:37:20.114 DEBUG (MainThread) [sonos_websocket.websocket] Opening websocket to wss://10.43.101.1:1443/websocket/api
2025-10-22 21:37:20.223 DEBUG (MainThread) [sonos_websocket.websocket] Successfully connected to wss://10.43.101.1:1443/websocket/api

Best Regards
Thomas

4

Strange as of today its working, without any changes done.
It seems to be a random timed problem.


2025-10-26 14:02:26.897 DEBUG (MainThread) [homeassistant.components.sonos.media_player] Playing http://10.43.10.171:8123/api/tts_proxy/URfUAcsN3FMnGUoj8J7x3g.mp3 using websocket audioclip

2025-10-26 14:02:26.898 DEBUG (MainThread) [sonos_websocket.websocket] Sending command: [{'namespace': 'audioClip:1', 'command': 'loadAudioClip', 'playerId': 'RINCON_C43875C3D9FA01400'}, {'name': 'Sonos Websocket', 'appId': 'com.jjlawren.sonos_websocket', 'streamUrl': 'http://10.43.10.171:8123/api/tts_proxy/URfUAcsN3FMnGUoj8J7x3g.mp3'}]

2025-10-26 14:02:26.898 DEBUG (MainThread) [sonos_websocket.websocket] Websocket connection reset, will try again

2025-10-26 14:02:26.898 DEBUG (MainThread) [sonos_websocket.websocket] Opening websocket to wss://10.43.101.4:1443/websocket/api

2025-10-26 14:02:26.976 DEBUG (MainThread) [sonos_websocket.websocket] Successfully connected to wss://10.43.101.4:1443/websocket/api

2025-10-26 14:02:26.976 DEBUG (MainThread) [sonos_websocket.websocket] Sending command: [{'namespace': 'audioClip:1', 'command': 'loadAudioClip', 'playerId': 'RINCON_C43875C3D9FA01400'}, {'name': 'Sonos Websocket', 'appId': 'com.jjlawren.sonos_websocket', 'streamUrl': 'http://10.43.10.171:8123/api/tts_proxy/URfUAcsN3FMnGUoj8J7x3g.mp3'}]

2025-10-26 14:02:27.016 DEBUG (MainThread) [soco.events_asyncio] Event 289 received for ZoneGroupTopology service at 1761483747.0169754
5

Yes, I power cycled all my Sonos speaker yesterday (which was quite tiresome, since I hid the power cables and sockets quite well) and it seems to work now too. Sonos just seems unstable at the moment.

6

I’ve been experiencing the 503 error since around August. Interestingly, the Sonos app on Android and iOS shows no content for the affected speakers, while the Windows Sonos app works fine. I can start playback on these speakers, but I cannot control the volume through the app. Playback control works fine in Home Assistant, except for the 503 error when doing announcements.

Power-cycling the speakers restores functionality, and reconnecting them to Wi-Fi also works. After a few days, the speakers sometimes recover automatically, only for the 503 error to occur again. This only affects 3 of my 7 Sonos speakers. I have a mix of single and paired Sonos One’s and Era 100’s.

I have a fairly simple UniFi network with two APs, also running Pi-hole. After many hours on the phone with Sonos support, I’m now talking to level 5 support. Sonos has taken several packet captures, but I haven’t heard back in over a month. They claim I’m the only one experiencing this issue.

Has anyone else called Sonos support about this problem? Getting past level 2 tech support was very time-consuming. Level 3 and 4 support confirmed the issue pretty quickly and escalated it. I suspect Sonos may have updated something, as I didn’t have any issues before.

7

Since the one time I wasted more than an hour with the Sonos support (chatbot, than waiting in line for a human to chat with. I miss simple ticketing systems) just to find out that I had to use the PC software instead of the Android app, I’ve vowed to only use the support when absolutely nescessary. Since it kind of works for me with reseting the devices from time to time (automation with smart plugs), I was not that desperate, but I’m glad you were :smiley:

Please keep us posted, that would be very appreciated.

8

Good news I’m pretty sure I’ve solved my 503 errors! I replaced my Netgear GS108PEv3 PoE switch with a UniFi US-8-150. Sonos has been working better than ever for the last 2.5 weeks. No errors for Sonos in HA or issues with the Sonos app. So it was my network but there is no actual proof.

In my UniFi network settings I set:
Forward Unknown Multicast Traffic → Multicast Router Port, turned on Flood Known Protocols, and Fast Leave. I set the AP’s, Gateway, Home Assistant ports to Multicast Router Ports.

My WiFi setting:

Multicast Filtering: Off

Network Optimizations:
Multicast to Unicast: Enabled
Multicast and Broadcast Blocker: Disabled
Client Device Isolation: Disabled
Private Pre-Shared Keys: Disabled

Advanced Features:
MLO (Multi-Link Operation): Disabled
Band Steering: Disabled
Hide WiFi Name: Disabled
Proxy ARP: Disabled
BSS Transition: Enabled
UAPSD: Disabled
Fast Roaming: Enabled
WiFi Speed Limit: Disabled

802.11 DTIM Period: Auto
Minimum Data Rate Control: Manual
2.4 GHz - 12 Mbps
5 GHz - 9 Mpbs

Sonos support came back with the follow:

The principal engineer reviewing the captures provided an update today. He expected to see TLS connection failures but did not, and he is continuing to analyze the data.

As a troubleshooting step, you could try moving Sonos to a separate VLAN to isolate it from other smart home devices on the network. If isolating Sonos resolves the issue, we can then gradually reintroduce the other devices to determine whether a specific device triggers the problem.

Best regards,

Curtis

S o n o s | Customer Experience Senior Escalation Engineer

I’ve been having issues with Sonos for the last 8 months, it’s nice to have things working again. crossed-fingers.

1 Like
9

Thank you very much for the detailed description, I’ve also got Ubiquiti network devices and configured eveything as you mentioned (except for fast roaming, which seems to crash most of my WLAN). The error seems to be gone, but the announcement is still not playing. Still seems like an improvement, I didn’t know that I could set these multicast settings. I would be very thankfull if you would keep posting your findings. Currently I have an automation that hard resets all my Sonos devices with smart plugs and setting them back as they were.