Option to disable built-in WiFi, when Sonos is used as a single device.
There are certain users, who don't utilize multi-zone capabilities, since they've picked up just a single Sonos player - be it Connect or Play - for one-room music experience. Naturally, those users don't need to keep the built-in WiFi in always ON state. Please, consider adding an option to disable WiFi, when it is not required. This will reduce power consumption, interference with other wifi sources, and keep the environment clean and free of extra EMR.
Show first post
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.
+26Quite the heated discussion going on here. Just a note VAX, I know it's not always brought up but Sonos players can be set not to use SonosNet and instead operate on the home WiFi as a standard wireless device. The dedicated Sonos wifi (SonosNet) isn't broadcasting and the player will connect right to the home wireless. To clarify too, SonosNet is the same sort of 802.11 b/g/n that other routers would use, just with some extra mesh networking built in.
The standard setup can get messy in a house where you've got 3 separate APs and each one is broadcasting a different SSID or on a different channel, but it can certainly be managed. Grouping rooms off of multiple networks and channels can have some syncing issues at times. In general, as your network gets more complicated it tends to be better to run on SonosNet.
In this setup, the players would function much like other wireless streamers and would be fighting for bandwidth along with everything else on the network. However, you wouldn't be getting any 2.4GHz interference from the players as they aren't broadcasting anymore, they're strictly receivers. This is the setup that's known as "Standard Setup" and is the basic direction that the Sonos app talks you through to begin with. The wired setup is a secondary setup for if the first has trouble.
Finally, if you ever have trouble with a setup and need a hand, our support team is ready and able to help. Feel free to give us a call on our support line if you need a consultation or just have some questions. We're happy to help.
The standard setup can get messy in a house where you've got 3 separate APs and each one is broadcasting a different SSID or on a different channel, but it can certainly be managed. Grouping rooms off of multiple networks and channels can have some syncing issues at times. In general, as your network gets more complicated it tends to be better to run on SonosNet.
In this setup, the players would function much like other wireless streamers and would be fighting for bandwidth along with everything else on the network. However, you wouldn't be getting any 2.4GHz interference from the players as they aren't broadcasting anymore, they're strictly receivers. This is the setup that's known as "Standard Setup" and is the basic direction that the Sonos app talks you through to begin with. The wired setup is a secondary setup for if the first has trouble.
Finally, if you ever have trouble with a setup and need a hand, our support team is ready and able to help. Feel free to give us a call on our support line if you need a consultation or just have some questions. We're happy to help.
One word: Paragraphs.
And if the worst thing you have to do today is get paid $100 for telling someone to move their Sonos Boost away from their router, I can understand why you would be so upset. I can't wait to see your solution when someone decides to binge watch House of Cards in HD on the WiFi TV and New Direction starts dropping out on the Denon HEOS in the daughter's room. I'm sure they will be quite pleased about Denon's ability to "work with your network not against it" then. 😃
And if the worst thing you have to do today is get paid $100 for telling someone to move their Sonos Boost away from their router, I can understand why you would be so upset. I can't wait to see your solution when someone decides to binge watch House of Cards in HD on the WiFi TV and New Direction starts dropping out on the Denon HEOS in the daughter's room. I'm sure they will be quite pleased about Denon's ability to "work with your network not against it" then. 😃
The RF interference of which I speak has nothing to do with broadcast beacons to discover players, etc which send out small bursts of data every 30 seconds or so but the RF carrier wave that carries those packets. With wi-fi these carrier waves radiate 24/7 unless Sonos does something different when operating on SonosNet but I would suspect the radios would have to be on at full power 24/7 to transmit data on demand. These carrier wave which usually operate on channels 1,6,11 for SonosNet are the same used for wi-fi so even if there are no clients on the network and you have a SonosNet and a wi-fi AP operating on the same channel they will interfere and how close they are determines how much they will interfere and then where in relation to those radios a client is. As far as being competent to install multi room streaming devices, well that's basically what Sonos is doing but their installers are the general untrained public and they shouldn't have to be able make network adjustment and definitely shouldn't have to tweak STP setting should they have equipment installed professionally that wasn't bought off the shelf from Best Buy. Again for most folks it shouldn't be a problem since most installations have just one low grade wi-fi router supplied by their ISP or one they buy from Best Buy but the homes I deal with all have at least 3 APs, usually Pakedge W7s, so when someone comes home with a Sonos it's not a piece of cake if it's put adjacent to an AP on the same channel. If they buy a couple and install on connected wall ports well that's an immediate call for help and again my 1st question will be "did you buy a Sonos". I would normally follow with, "throw it out" but I'm trying to be tolerant and accommodating. 🙂 Now since I don't want radios on radiating carrier waves 24/7 that don't need to be on when devices are wired since they will, regardless of what you guys say, interfere I just asked a few questions to learn more about this product. Well I guess there's always HEOS, they don't have any of these issues since they work with your network not against it. 🙂
I'll add to ratty's short but more than sufficient retort by saying if one is going to be in the business of installing multi-room networked streaming systems, I would think it a prerequisite to be competent in basic network configuration. At the very least they should be able to do consumer level adjustments like changing conflicting channels, reserving IP addresses, or configuring a few STP toggles. If one is not capable of doing this, they shouldn't be in the business of installing multi-room networked streaming systems.
And at the risk of restating the obvious, the bulk of the problems are IP conflicts. If my 99.9% number is used, I'd estimate 99.8% are conflicts, and .1% are STP. In fact, my personal theory is the "WiFi option" was probably put in place for the odd whackadoodle who is afraid of "all 'dem radio waves running through my body when I'm sleepin'", rather than any fear of STP configuration.
And at the risk of restating the obvious, the bulk of the problems are IP conflicts. If my 99.9% number is used, I'd estimate 99.8% are conflicts, and .1% are STP. In fact, my personal theory is the "WiFi option" was probably put in place for the odd whackadoodle who is afraid of "all 'dem radio waves running through my body when I'm sleepin'", rather than any fear of STP configuration.
I agree with all of the above. Disabling wifi should be possible through the interface for those of us who don't need / want it.
there should be no duplicate IPs since simple systems are strictly DHCP
Many consumer routers don't persist lease IP info across a reboot. When things don't work the customer's first reaction is often to do a router reset. You can work out what happens next.
if the bulk is then an STP issue then that proves my point
Very few issues are STP related. Most owners don't multiply wire, and most simple network devices are STP-transparent anyway.
that says nothing about Sonos being on the same RF channels as the home's wi-fi.
At setup Sonos will scan and try to choose the clearest SonosNet channel. Sometimes that is the WiFi channel.
the RF radiation itself that interferes with any other radio operating on the same channels.
It doesn't, unless there's a lot of traffic. In a fully wired system there'd be one STP packet per second on each blocked virtual tunnel, i.e. a tiny trickle.
Most Sonos systems aren't installed by competent installers and most of those installing these systems have no idea what RF interference is or what channels are used or what can be done to avoid it. Most Sonos installer wouldn't be able to make the connections as to why their network isn't working right and most of these installers don't join forums to discuss their problems, they simply don't know the forums exists. As far as 99% of the problems reported here are STP or duplicate IPs, well there should be no duplicate IPs since simple systems are strictly DHCP and if the bulk is then an STP issue then that proves my point and that says nothing about Sonos being on the same RF channels as the home's wi-fi. 99% of these systems are being bought by home owners who don't know what they are doing and there's nothing on the box or in the set up to warn them so if they bring a Sonos home and put in a Boost or something else next to their access point, both on channel 6, well that's a problem that most home owner won't figure out and isn't readily recognizable. If they plug in multiple device to the wired network and a broadcast storm crashes their network well then they might make that connection, but maybe not. When someone calls with network issues the 1st thing I ask them now a days is "did anyone buy a Sonos system" and then if the answer is yes we can work to fix it. These people don't join the forum to complain. Yes, setting up STP isn't that complicated, if you're doing the install yourself and you're familiar with setting up your L2/L3 switches but how often do people by these things for Christmas or birthdays and plugged them into an active wall port and oops, they goes the network. I guess we could config every port with proper STP settings to be pro-active but why. By pollution I don't mean chatty products that broadcast non stop but the RF radiation itself that interferes with any other radio operating on the same channels. IMHO it is a Sonos problem not mine and your problem is something else entirely. 🙂
VAV wrote:
I'm an AMX programmer/dealer so I know how to install a standard high end distributed system but the market has shifted and Sonos is perfectly capable of being deployed using multiple connect amps or just connects using high end amps. Sonos just makes it complicated when it doesn't have to be and even in simple systems that they were original designed for they're still notorious for destroying home's networks which is why they now have the wi-fi option but they still cause issues if the radiios are on and all devices are wired which they should be if there is no need to be portable and a wired connection is available. The notion that radios should be on regardless of being wired is ridiculous considering the polution in the 2.4ghz spectrum.
Nonsense. The "WiFi option" has been an undocumented feature for years, it is just unsupported because any competent installer should be able to implement STP correctly. And if "even in simple systems" Sonos was truly "notorious for destroying home's networks", you'd see a flood of these complaints here, instead of the few posts that 99.9% of the time end up being STP or duplicate IP problems.
As to "the notion that radios should be on regardless of being wired is ridiculous considering the pollution in the 2.4ghz spectrum", when wired the "pollution" put out by Sonos devices is barely a trickle. There is no "pollution" at all. Your problem is your own, not Sonos'.
I'm an AMX programmer/dealer so I know how to install a standard high end distributed system but the market has shifted and Sonos is perfectly capable of being deployed using multiple connect amps or just connects using high end amps. Sonos just makes it complicated when it doesn't have to be and even in simple systems that they were original designed for they're still notorious for destroying home's networks which is why they now have the wi-fi option but they still cause issues if the radiios are on and all devices are wired which they should be if there is no need to be portable and a wired connection is available. The notion that radios should be on regardless of being wired is ridiculous considering the polution in the 2.4ghz spectrum.
VAV,
You would probably be more comfortable with a RUSSOUND, URC, C4, or similar system and a couple Bluetooth, AudioEngine, or WiSa speakers for Patios.
You would probably be more comfortable with a RUSSOUND, URC, C4, or similar system and a couple Bluetooth, AudioEngine, or WiSa speakers for Patios.
A few questions since finding real info is such a PITA. 1st I've found the config setups for the Cisco switches and router I tend to use and while it's again a PITA to have to worry about this crap and setting up the STP per port since you know patch cables never move but in the ideal world Sono's radio's should be turned off for any thing that isn't meant to be portable. My configs would be most amps or connects with decent 3rd party amps driving in wall speakers through out. I would prefer not using Sonos but the market seems to force AV guys and integrators down this path. I hate the idea I having anything in 2.4ghz spectrum other than my wi-fi gear and I don't what to worry about Sonos mucking things up so I want radios off unless I'm using wireless speakers for use on Patios or similar installs where fixed in place speaker aren't practical or ideal. So for those I'd use the houes wi-fi and everything else would be wired so here's a few questions:
1, If wired and radios turned off would STP still be an issue on L2/L3 switches. I wouldn't think so since the wireless causes the bridge but.. ?
2, When using speakers on wi-fi (not SonosNet) are they simply clients or will they act like APs and try to create a mesh and cause those STP issues?
3, If wired and radios off and/or using a couple speaker on wi-fi (not SonosNet) will they discover each other or do they need SonosNet for the initial setup?
4, How much broadcasting do these devices do, are the so chatty they should be on their own subnet, maybe just their own switch?
Why after all this time why is it so hard to find proper install setups that AV integrators would want to use like all wired connect or amps with maybe a few speakers on wi-fi and what this does or doesn't means to your network for a wired, wi-fi, wired or wi-fi or the SonosNet setups? Why are people still buying these things, bringing them home and screwing up their networks due to the lack of proper disclosure.
1, If wired and radios turned off would STP still be an issue on L2/L3 switches. I wouldn't think so since the wireless causes the bridge but.. ?
2, When using speakers on wi-fi (not SonosNet) are they simply clients or will they act like APs and try to create a mesh and cause those STP issues?
3, If wired and radios off and/or using a couple speaker on wi-fi (not SonosNet) will they discover each other or do they need SonosNet for the initial setup?
4, How much broadcasting do these devices do, are the so chatty they should be on their own subnet, maybe just their own switch?
Why after all this time why is it so hard to find proper install setups that AV integrators would want to use like all wired connect or amps with maybe a few speakers on wi-fi and what this does or doesn't means to your network for a wired, wi-fi, wired or wi-fi or the SonosNet setups? Why are people still buying these things, bringing them home and screwing up their networks due to the lack of proper disclosure.
This computer sits in a difficult to wire location. It is connected through a wireless CONNECT. I don't have any issues.
Devices also need to bridge everything in order to support Android devices connected directly to SonosNet. This is a commonly used scenario.
User148058 wrote:
How strange that this intelligent request is not even under consideration by what would appear to be an open-minded company. This would be a simple functionality to accommodate those who prefer wired networking with one or many devices for any number of reasons... and it would not hurt the bottom line one bit. I mean only to say that this system I JUST PURCHASED which is neither TRULY Airplay compatible as advertised NOR CAPABLE of turning off a function I don't actually want or need is super, super easy to return considering the premium one pays to own a Sonos and the wave of competitors waiting at your front door.
Moot? Not so moot. But rah rah rah. FYI: There is no direct streaming of iTunes outside of iOS, which is ridiculous because even the largest iPhone or iPad can only hold a small fraction of the average person's library. Worse, if you want to stream via iTunes Match, i.e., your entire library, you can't do that with Sonos currently. That's a key differentiator, and Sonos marketing language obscures this fact and is basically misleading. Sure, you can make Sonos point to files on a Mac hard drive or on an NAS that *might* get recognized by an Airport Extreme and actually share...but...you sure you want to have this conversation? Are you an intern or something?
Dear Sonos
I would like to see the feature of turning off the wireless net especially over night within a timerange I can define, like many users do use this on there NAS systems or with the normal WLAN in there homes. Especespecially with the introduction of the beloved Play:1 you step more and more in our bath- and bedrooms - private areas. People would see these areas free of WLAN - as many others said "better save than sorry"
So please consider and implement this feature for all equipments - Bridge too
Thanks in advance
I would like to see the feature of turning off the wireless net especially over night within a timerange I can define, like many users do use this on there NAS systems or with the normal WLAN in there homes. Especespecially with the introduction of the beloved Play:1 you step more and more in our bath- and bedrooms - private areas. People would see these areas free of WLAN - as many others said "better save than sorry"
So please consider and implement this feature for all equipments - Bridge too
Thanks in advance
I am also sure that people how can afford the SONOS components will have invested in wire solutions like I have. I don't want to have my home with little kids as a massive electro smoke house. Please make sure you have a software option ready soon.
Furthermore - I would also like to suggest to have a power on/off on the devices. It can be that we try to safe energy all the time and have power safing light bulbs and then have all those devices on while we are not even at home. Wake-up on LAN might be a first step...or just a normal on/off. I have manually added this on the power cord.
Thanks for your consideration to make a fabulous product even better!
Furthermore - I would also like to suggest to have a power on/off on the devices. It can be that we try to safe energy all the time and have power safing light bulbs and then have all those devices on while we are not even at home. Wake-up on LAN might be a first step...or just a normal on/off. I have manually added this on the power cord.
Thanks for your consideration to make a fabulous product even better!
I too would like this feature to be enabled and supported - as I too like to limit wireless activity in my house and will not have a Sonos unit in my bedroom for similar reasons above. There are unsupported techniques to achieve this, I just don't understand why this is not a simple option/tick box in the preferences.
Danny wrote:
I would also like to see this feature enables . . we constantly do racks with 10-12 Sonos' as well as whole houses with individual systems. There are cases where the systems are too far for reliable wireless but will catch it from time to time . . meaning if we hardwire (which we normally have the option to and prefer) the connect/connect:amp/bridge will create a network storm and bring down the network. this has happened on several jobsites and it is a PITA to force the client to needlessly hide a bridge somewhere when it is sitting right nest to an ethernet jack. Please let us have the option to disable in some advanced menu. (enable it by default for normal users + compatibility with adding more zones). Also, I miss having the ability to choose a channel. We used to keep Sonos' on Channel 11 and force our access points to auto select between channels 1-8.
You can still set the channel, they have not eliminated it.
I would also like to see this feature enables . . we constantly do racks with 10-12 Sonos' as well as whole houses with individual systems. There are cases where the systems are too far for reliable wireless but will catch it from time to time . . meaning if we hardwire (which we normally have the option to and prefer) the connect/connect:amp/bridge will create a network storm and bring down the network. this has happened on several jobsites and it is a PITA to force the client to needlessly hide a bridge somewhere when it is sitting right nest to an ethernet jack. Please let us have the option to disable in some advanced menu. (enable it by default for normal users + compatibility with adding more zones). Also, I miss having the ability to choose a channel. We used to keep Sonos' on Channel 11 and force our access points to auto select between channels 1-8.
How about this senario: Put this option under the room configuration menu: Disable wireless when the ethernet port has an active connection? That way if I accidentaly activated this checkbox I could always connect to the device wirelessly when no ethernet cable is plugged in.
Sonos, can you provide some insight as to why this idea is not being considered, considering it has been raised so many times in the forums? Many of us are concerned about needless radio waves, especially when we have them hardwired with ethernet, and would like to have a unit in our bedrooms. Although the dury is out as to whether there is any long term impact, there is nothing wrong with 'better safe than sorry'. I currently will not put a unit in my bedroom even though i would like to, for this reason. This is a basic software fix with a single check box in the settings menu, and seems like such a simple thing. Not really sure why the community is being ignored on this issue, considering we see it as a potential health issue.
User148058 wrote:
How strange that this intelligent request is not even under consideration by what would appear to be an open-minded company. This would be a simple functionality to accommodate those who prefer wired networking with one or many devices for any number of reasons... and it would not hurt the bottom line one bit. I mean only to say that this system I JUST PURCHASED which is neither TRULY Airplay compatible as advertised NOR CAPABLE of turning off a function I don't actually want or need is super, super easy to return considering the premium one pays to own a Sonos and the wave of competitors waiting at your front door.
Yet you lurk on these boards and engage in a conversation that doesn't acknowledge a concern or desire from a new customer? I have an issue about the wifi yet you jump on "wave of competitors" comment like a paid shill? My friend, if you're compensated for your cheerleading, you're not doing anyone any favors.
User148058 wrote:
How strange that this intelligent request is not even under consideration by what would appear to be an open-minded company. This would be a simple functionality to accommodate those who prefer wired networking with one or many devices for any number of reasons... and it would not hurt the bottom line one bit. I mean only to say that this system I JUST PURCHASED which is neither TRULY Airplay compatible as advertised NOR CAPABLE of turning off a function I don't actually want or need is super, super easy to return considering the premium one pays to own a Sonos and the wave of competitors waiting at your front door.
No, I am hardly an "intern" (LOL!) and I do not work for Sonos. However, an accusation of me working for Sonos is where I bow out, for in my experience the conversation goes downhill fast when the messenger is attacked instead of the message. Cheers! Enjoy what ever competitve system you find.
Mike C wrote:
If an Idea's status changes we will reflect it within the original request. There will be no need to open a new Idea.
Dear Mike. Any news the those requests? I stronly beleive that you guys would make a big difference to other products on the markets and as suggested by Christoph. This could also be a market differentiator for your company and show that you really care.
KR
Andreas
User148058 wrote:
How strange that this intelligent request is not even under consideration by what would appear to be an open-minded company. This would be a simple functionality to accommodate those who prefer wired networking with one or many devices for any number of reasons... and it would not hurt the bottom line one bit. I mean only to say that this system I JUST PURCHASED which is neither TRULY Airplay compatible as advertised NOR CAPABLE of turning off a function I don't actually want or need is super, super easy to return considering the premium one pays to own a Sonos and the wave of competitors waiting at your front door.
Airplay is a competitor in product awareness, but it is hardly a competitor in functionality. Especially since the main reason for people wanting Airplay - direct streaming of iTunes from iDevices - is now moot.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.