Problem with tts and sonos

Configuration
21

No mention of it :<(
I also searched the full change log for both the GitHub ticket number and ‘jjlawren’.

22

Sometimes that happens when a fix is tagged for a point release that was never actually released (2023.5.5 in this case). It’s included in 2023.6.0.

23

@ jjlawren
Thanks for the response on Wednesday. Since then I installed 2023.6 and 2023.6.1, rebooted and restarted Home Assistant but continue to be unable to send TTS messages to anything but the target speaker. All attempts to join speakers into the group only result in the target producing the output.
I have downloaded the Sonos diagnostics and it does confirm sonos-websocket==0.1.2

    "requirements": [
      "soco==0.29.1",
      "sonos-websocket==0.1.2"
    ],

I’ve also tested with a simplified automation where there are no passed variables, choose statements or any other complex coding. Just a simple join and speak automation.

- id: media_sandbox_4
  alias: Media Sandbox 4
  description: 'Generic testing utility'
  initial_state: true
  mode: restart
  trigger:
  - platform: state
    entity_id: switch.momentary_sandbox_4
    to: 'on'
  condition:
  - condition: state
    entity_id: input_boolean.sandbox_testing
    state: 'on'
  action:
  - service: media_player.join
    target:
      entity_id: media_player.kitchen_white
    data:
      group_members:
        - media_player.living_room
        - media_player.sunroom_black
        - media_player.mbr
        - media_player.office
        - media_player.garage_speakers
        - media_player.patio_speakers
  - service: tts.google_cloud_say
    data:  
      entity_id: "media_player.kitchen_white"
      message: "The quick brown fox jumps over the lazy dog."

Today I have turned on Debug Logging and can provide those findings after tomorrows morning briefing. Lastly, I have confirmed the the target device is in fact grouping the other speakers in the States tab of Dev Tools.

group_members: media_player.kitchen_white, media_player.garage_speakers, media_player.office, media_player.patio_speakers, media_player.mbr, media_player.sunroom_black, media_player.living_room
volume_level: 0.2
is_volume_muted: false

I’m at a loss as to why I can no longer group these speakers and make a whole house announcement. Everything always ONLY plays on the Kitchen device (master). Any suggestions would be greatly appreciated.

24

If you’re using a tts.*_say with Sonos, the speaker groupings no longer have any effect. Only the explicitly targeted speakers will play, regardless of any group structure used for music playback. Just list all of the destination speakers in the TTS call:

  - service: tts.google_cloud_say
    data:  
      entity_id:
        - media_player.kitchen_white
        - media_player.living_room
        - media_player.sunroom_black
        - media_player.mbr
        - media_player.office
        - media_player.garage_speakers
        - media_player.patio_speakers
      message: "The quick brown fox jumps over the lazy dog."

This avoids the need to snapshot/regroup/etc to play announcements. Music playback, groupings, and volume levels are no longer affected by TTS or media_player.play_media calls with the announce option enabled.

25

I’m sorry, but the above code does not work as intended. Every speaker in the entity_id list is milliseconds out of synch with its neighbor. See TTS: Speaker Group - Jitter/Stutter