Roon Server Log shows a line like this one for all Sonos speakers:
10/19 17:08:42 Trace: [devicemanager/sonos] FOUND Device IP=192.168.1.79 UDN=uuid:RINCON_000E58FCD8AE01400 Manufacturer=Sonos, Inc. ModelName=Sonos Play:3 ModelNumber=S3
I have a dedicated mini pc running windows 10 that I tried Roon on (same version). No difference from Roon on the Synology NAS - identical view of Audio devices. (ie: missing the same Sonos pieces).
Update: I didn’t want to do it, but I factory reset all 24 pieces of Sonos equipment I have, readded them to the S2 app, and now they all appear in Roon!
2 hours of work that I resisted, but it was obviously what was needed.
Wow. That lasted 20 minutes. Every single Sonos device in the house was available in Roon immediately after opening Roon after all the devices had been factory-reset and then re-added to Sonos S2.
Sadly Andrew it is a problem that impacts a number of Sonos user’s across all platforms and not just Synology.
There are a couple of open thread’s for the issue and Sonos are looking at it, but no promise’s on a fix
I fixed my problem by removing all wired Sonos devices and factory resetting and adding them back as basic WiFi only.
Also I have given them all reservations in DHCP.
Almost 3 weeks of solid Sonos since then.
Thanks Michael. I’ve removed ethernet from all but one connect - since I was under the impression that Sonos required at least one wired device. If not, I can unwire it as well and try again…
Andrew Trust me I know the feeling, I had 5 days without music as I tried to give Roon plenty of log files so they could get more information.
For SonosNet it does require one device (or Boost) but on all WiFi none are required and surprisingly I have had barely a skip or stutter since I made the changes.
Sadly it doesn’t hold for all
Short term solution, just restart the application on Synology and they should be back inside 30 seconds if like the rest of us. My experience was it sometimes lasted for upto a day.
Roon are looking at it but it cannot come quickly enough for some.
I had this Sonos bug for a number of weeks. Tried many things posted in the recent threads on here. Some of these brought the devices back, but only temporary. All my Sonos devices are on wifi.
What eventually made my Sonos devices stick was this:
Do you by any chance have another Roon Core you can temporarily try to use? It would be good to see if the issue still occurs without the Synology in the mix. You can use these instructions to do so:
Open Roon on the other PC you wish to try as the Core
Roon Settings → General
Disconnect
On the “Choose your Core” screen, press “Use this PC”
If asked to Unauthorize, you can go ahead and do so. You are limited to one active Roon Core at a time but you are free to switch between them as often as you’d like.
Verify if the same behavior occurs on the different PC