Sonos Integration Issue? July 2019

Anyone else having issues with the Sonos integration? ST seems to only be able to get volume information from Sonos for me and nothing else,

All I’m seeing in my logs is:

    c457403c-715c-4e7a-836a-dc608f76e8b3  6:48:12 PM: debug Not parsing XML message:
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<s:Body>
<u:GetVolumeResponse xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1">
<CurrentVolume>
15
</CurrentVolume>
</u:GetVolumeResponse>
</s:Body>
</s:Envelope>
c457403c-715c-4e7a-836a-dc608f76e8b3  6:48:12 PM: trace Extracting current volume
c457403c-715c-4e7a-836a-dc608f76e8b3  6:48:12 PM: trace sonosAction(GetVolume, RenderingControl, /MediaRenderer/RenderingControl/Control, [InstanceID:0, Channel:Master])
c457403c-715c-4e7a-836a-dc608f76e8b3  6:48:12 PM: trace getVolume()
c457403c-715c-4e7a-836a-dc608f76e8b3  6:48:12 PM: trace doPoll

Resolved the issue by pulling the power to the ST hub, then running a add new device search so it did the UPNP discovery process again (though I didn’t have to re-add my speakers).

Can you explain what you did in more detail as I’m a bit confused and have the same issue as you were having. Thanks![quote=“swamplynx, post:3, topic:168718, full:true”]
Resolved the issue by pulling the power to the ST hub, then running a add new device search so it did the UPNP discovery process again (though I didn’t have to re-add my speakers).
[/quote]

  1. Reboot hub (remove power and batteries)
  2. Go through the add new device process, same as you would a new Zigbee or Z-Wave device, and leave it on that screen for at least a minute. It won’t find anything new, but if you look at your hub even logs you can see this triggers the UPNP discovery process to and reconnect to Sonos.

Chris - thank you so much for the detail! I’ll be doing it as soon as I get home