I have about 15 sonos devices in my system, mostly Play1’s, a Play5, and several connect:amps. Because of their age, I have to keep them on S1, which has been totally fine.
What kills me though is SonosNet. There are a large number of nearby WAPs, and using SonosNet is just a disaster. I’d love to connect everything via ethernet, but it is just not practical. So, wireless it is. I’ve created a separate 2.4Ghz only wifi network for the sonos system and have it VLAN tagged so their IP addresses are in a range distinct from everything else. Works great, except when it doesn’t.
A couple times a year we find sonos components disappearing off the system, playback being flaky, interrupted, etc. And, sometimes our entire wifi network just goes tits up. When this happens, I usually find that some of the sonos components have turned their SonosNet back on and somehow or another are creating massive packet collisions on the network. So, then I have to go through the annoying process of reconfiguring those components to use the network I’ve made for them. I can usually identify the culprits because their IP is not from the range that my SONOS VLAN is supposed to use.
Still, I think it would awesome if there was a way to permanently disable SonosNet on componenents
Permanently Disable SonosNet on S1 systems
Your post is a bit confusing as your profile shows you have products that will operate on S1/S2, products that are S1 only and products that are S2 only. That said:
- Are you running to separate Sonos being S1 and S2?
- Have you gotten rid of the S2 only products?
- Are you trying to run everything on S1?
- What products are actually involved?
- Is there a Sonos Bridge (or Boost) involved?
Instead, why not remove the troublesome Ethernet connections (which permanently disables Sonosnet) and follow tne Sonos recommendations to use only Wi-Fi?
As no changes to S1 are anticipated seeing new options isn't likely.
You might also consider DHCP reserved addresses for all Sonos as that has been shown to improve stability on many systems.
sorry, i must have mispoke on my mix of devices. I don’t have any S2 only devices. They are all either S1 only or S1/S2 so i’ve been running an S1 system.
I have removed the ethernet connections and have set them up to use my wifi. nevertheless, every now and again one or more devices go rogue, turns on SonosNet again and causes huge network hiccups.
SonosNet is not a factor when no Sonos device is wired back to the router. Whatever network issues you are having is not due to SonosNet.
+17sorry, i must have mispoke on my mix of devices. I don’t have any S2 only devices. They are all either S1 only or S1/S2 so i’ve been running an S1 system.
I have removed the ethernet connections and have set them up to use my wifi. nevertheless, every now and again one or more devices go rogue, turns on SonosNet again and causes huge network hiccups.
The Arc and Roam 2 are S2 only speakers, so you do have a mix of S1 and S2 devices.
That being said, you have use both apps in order to control all your Sonos devices, and sometimes there can be hiccups.
More likely (although impossible for us without access to diagnostic data to be certain) that it’s duplicate / warring IP information.
I’d certainly suggest a network refresh, by unplugging all Sonos devices from power, then rebooting your router (in most systems, this is the IP generation device). Wait two minutes for that router to recover, then plug in the Sonos devices to power. This should cause them not only to reload their firmware, but also request new IPs from the refreshed router’s DHCP table.
If the issue continues, I would recommend that you submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it. Don’t post the resulting diagnostic number here.
There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution. Certainly, we in the public don’t have access to this ‘hard’ data about what is causing the issue.
When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.
sorry, i must have mispoke on my mix of devices. I don’t have any S2 only devices. They are all either S1 only or S1/S2 so i’ve been running an S1 system.
I have removed the ethernet connections and have set them up to use my wifi. nevertheless, every now and again one or more devices go rogue, turns on SonosNet again and causes huge network hiccups.
Per your profile:
The Arc, Roam2 and Sub Mini are S2 only products. Do you not own them any longer? If you are trying to run all in S1 (which shouldn’t be possible) there may be your problem.
AHA! Two systems, one at home, one at work. I actually probably have 30 sonos devices total! One of the networks is S2 and has all the newer stuff, including the Arc, Roam2, sub mini. The other network is S1 only and has all the older devices
AHA! Two systems, one at home, one at work. I actually probably have 30 sonos devices total! One of the networks is S2 and has all the newer stuff, including the Arc, Roam2, sub mini. The other network is S1 only and has all the older devices
Thanks for the clarification. The question just didn’t follow your profile. 😊
Just to be clear the SonosNet can’t engage itself without an active wired connection to a router. There are only two ways to activate the SonosNet:
- Wire a speaker to a router
- Wire a Sonos Boost or Sonos Bridge to a router.
The Sonos Bridge is most definitely not recommended as it’s old tech (that causes issues) and was replaced by the Sonos Boost. If you had a Sonos Bridge in your network you must follow the procedure in this link to properly remove it. As suggested by
Barring anything else running a diagnostic as suggested by
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.