I have fallen foul of an upgrade policy, I'm not sure it's the same one you refer too. (15-12-2021 14:51)entdgc Wrote: It sounds like you have fallen foul of the Sonos upgrade policy which caused uproar in the community and they have been forced to backtrack. My son-in-law uses Play 5's as surround for his TV and also sound good. I use Play 1s as a pair in my office and they give good sound. I’ve managed to install the LMS-to-UPNP binary on my Intel X86 Nuc (running also Roon core), this is a Linux one.Your Sonos Play 5s are IMHO very good speakers. So, looks liks synchronisation of Sonos speakers via UPnP is unlikely - unless Sonos release details of how it is done or Roon adds ability to play directly to Sonos - for now use Sonos app to group speakers and play to the group from Roon. It you have a Sonos group that is always the same, then the best is to disable all slave speakers, in the squeeze2upnp configuration file, so there is only one speaker visible in Roon. Note that if you try to play from Roon on one of the slave speakers, it will not work, you must play on the master. The only thing you can do is to create a Sonos group from the Sonos control app and when you play something using the Roon controller on the master speaker of that group, then all the Sonos speakers of that group will be synchronized. So, there is no solution to synchronize a Roon-native or a SB device with a uPnP / Sonos speaker. Sonos are controlled using uPnP but they have a proprietary sync system in addition and they do not want to release its specifications. Hi Mike – Unfortunately, uPnP standard does no allow audio synchronization, by design. Didn’t solve the synchronisation problem though - if anything, slightly worse.

Tried (2) - running multiple instances of UPnPBridge - worked OK once I ce=reated separate config.xml files for each Sonos speaker and set enabled=0 in ‘common’ section.

Sonos add upnp player