Hi All,
Glad to hear that there’s been an improvement in regard to this issue! We have been making progress on this issue and have isolated a potential cause, but if you do see this behavior re-occur, please do let us know.
2 Likes
@noris you probably don’t want to share the cause, but it would be great for those of us who suffered this issue for a long time to have some kind of explanation.
It’s great that it has now been fixed for more of us 
I can report that I too seem to have more reliable access to my sonos devices.
What changed?
1 Like
Wow I just read through all this. You poor poor folks.
I’ve not had troubles in the last few years with Sonos + Roon, but I have all SonosNet (wm:0) and Wi-Fi turned off for the network, and several wired backhauls for 5 of my 12 devices, and went through the whole RSTP bloody mess with Sonos before I ever arrived at Roon. So while I’ve had my share of disappearing zones, it happened in Sonos natively as well as Roon, and was my own fault for trying to get multiple wired devices and have SonosNet. But once I did that it’s been rock solid on Roon or off. Taught me a lot about networking that I had not known. But not for the faint of heart. I was faint of heart for a while but I’m preternaturally stupid and stubborn. Some in my family have described it as bullheaded. Anyhoo it got ‘er done. Needed that experience because I have a second home with 8 zones spread across 4 acres, which are also by necessity a combination of wired and not. Thank you unifi for making gear which makes this possible, though not easy per se.
Anyways, just dropped in to say wow, I hope this clears up permanently.
My two Sonos devices are hardwired and never disappear, but sometimes gaps between tracks are quite long. I turned of Wi-Fi for both of them, but how can one turn off “SonosNet (wm:0”)?
Sorry that was lazy on my part.
If I go into the Sonos app and go to Settings > System > About my System, you’ll see that below every one of my 11 zones there’s text at the bottom that says “WM: 0”.
The other option i have seen is “WM:1”. 0 means that the Sonos endpoints are on SonosNet, the proprietary wireless network optimized for sync’ed audio that is Sonos’ primary intellectual property / USP. What you’re reading above is that you ideally want all your devices on SonosNet. The way you diagnose if you’ve achieved that is by checking if you have all “WM: 0”. (This link to Sonos community explains, it’s not official so I’m not positive it’s correct, but I think so)
If not, the path there can be a bit complex. The simplest way is to only have a single Sonos device wired, and then if you need to turn off Sonos’ access to your “regular” (eg, not SonosNet) WiFi. If you want to force the issue you can go to Settings/System/Network/Manage Networks and then “delete” your Wi-Fi network and then Sonos is forced to use SonosNet. But… if you’re in a situation like me where the generally amazing SonosNet can’t reach all the far-flung corners of your home, you have to resort to having multiple wired Sonos devices. And this way lies madness. You have to learn about RSTP and have the right networking gear, and though I took copious notes I couldn’t reproduce it. So my general advice is “make sure wm:0”, “only one wired device”, “kill access to Wi-Fi if you need to”, “buckle up if you want to wire >1”.
Good luck!
1 Like
Thank you very much @Johnny_Ooooops. My two devices show “WM: 0”. One of them always had dropouts when connected to Wi_fi, now hardwired all is good, but sometimes there are gaps between tracks, but only with Qobuz streamed music and not always. I think this is not a network issue as this appears with non-Sonos endpoints also - sometimes, and only with Qobuz content.
Thanks again and have a great weekend!
1 Like
Greetings -
To share my frustration with this problem - after an upgrade from Roon some months ago I can no longer see any of my Sonos devices. I have tried different devices as Roon Servers, attached themdirectly to the switch with the primary wired Sonos (the rest are on Wifi), etc. What is odd is that in the RoonServer log you get the below, so the devices are appearing but not showing up as audio devices. I welcome any further thoughts or progress.
Thanks!
12/23 14:06:17 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.125 UDN=uuid:RINCON_5CAAFDEBE68001400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:17 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.49 UDN=uuid:RINCON_B8E93799B1F601400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect ModelNumber=ZP90
12/23 14:06:17 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.119 UDN=uuid:RINCON_949F3EB22B4801400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect ModelNumber=S15
12/23 14:06:18 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.31 UDN=uuid:RINCON_949F3EA01A2001400 Manufacturer=Sonos, Inc. ModelName=Sonos Sub ModelNumber=Sub
12/23 14:06:18 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.23 UDN=uuid:RINCON_5CAAFDEBEE7201400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:18 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.114 UDN=uuid:RINCON_949F3EB22AE601400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect ModelNumber=S15
12/23 14:06:19 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.58 UDN=uuid:RINCON_5CAAFDEBEE3C01400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:19 Debug: [easyhttp] [19] POST to https://discovery.roonlabs.net/1/register returned after 162 ms, status code: 200
12/23 14:06:19 Trace: [inetdiscovery] registered 1 devices, 5 services
12/23 14:06:19 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.5 UDN=uuid:RINCON_5CAAFDEBE64E01400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:19 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.12 UDN=uuid:RINCON_5CAAFDEBEE4401400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:20 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.6 UDN=uuid:RINCON_5CAAFDEBE50C01400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:20 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.51 UDN=uuid:RINCON_5CAAFDEBEE6E01400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:21 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.17 UDN=uuid:RINCON_5CAAFDEBEDF801400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:21 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.41 UDN=uuid:RINCON_5CAAFDEBE85C01400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:21 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.47 UDN=uuid:RINCON_5CAAFDEBE0E001400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:22 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.13 UDN=uuid:RINCON_5CAAFDEBEE5E01400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:22 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.26 UDN=uuid:RINCON_5CAAFDEBE74001400 Manufacturer=Sonos, Inc. ModelName=Sonos Connect:Amp ModelNumber=ZP120
12/23 14:06:22 Trace: [devicemanager/sonos] FOUND Device IP=192.168.169.61 UDN=uuid:RINCON_F0F6C1E1767A01400 Manufacturer=Sonos, Inc. ModelName=Sonos Sub ModelNumber=S26
Hey @noris,
Just headed over to this thread after the issue of Sonos endpoints disappearing (S1 system - mix of S1 and S2 compatible devices) came up in another discussion - https://community.roonlabs.com/t/sonos-s1-s2-sonos-move-and-sonos-roam -
As per the comments there, I see that this had been an issue I gather came and went after version 1.8, but even though I’ve had S1 Sonos components in my system for years I’ve never had any issues with them dropping off Roon as available endpoints until just after updating to the latest current version of Roon (2.0 Build 1193).
First thought it was just a temporary glitch that was fixed by restarting Roon core, but now it keeps happening over and over, some random period of time after restart. Note on each occasion, those Sonos S2 capable devices appear and can be added in Settings>Audio as Airplay devices (only) but all 4 of my other Sonos devices no longer appear, unless I restart Roon core over and over.
Note nothing whatsoever has changed on my existing, working set up other than the update to the latest Roon software, which was and has been rock solid pretty much since I first joined up a few years ago.
Please let me know if you need any further details or if you have any suggestions on a fix
Thanks
Steve
Hi @Stephen_Dixon ,
Apologies for the delay in response here. Are you still seeing this issue? We are still looking into this but reports have been intermittent.
If you or anyone else reading this regularly see this issue, we can try to enable a deeper diagnostic mode to see if we can get further details. Please let me know if you’d like to assist with this and I can provide further details, thanks!
Hi @noris
All seems fairly stable now and all S1 Sonos zones not had further disconnects recently AFAIK 
Thanks
Steve
1 Like
Hi @noris -
I am still having this issue and would welcome a deeper diagnostic mode, thank you!
Jon
1 Like
3 posts were merged into an existing topic: Sonos - “Roon lost control of the audio device” after Sonos Update [Ticket In, See Workaround]