Closed Bug 1017281 Opened 11 years ago Closed 10 years ago

Sonos devices don't stay connected on the 1st floor

Categories

(Infrastructure & Operations Graveyard :: NetOps, task)

Product:
Infrastructure & Operations Graveyard
Component:
NetOps
Platform:
x86_64
Windows 7
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: ikon, Assigned: jbarnell)

Details

Sonos keeps disconnecting on the 1st floor (lobby, 1st floor kitchen, hallway, and bathrooms). Chris Beard and Jim Cook are interested in the progress of this bug. Please let me know if you need any information from me to help troubleshoot.
adding pdang
I've requested the following items for further understanding: 1. What are the installed (models, etc) Did we include the "sonos bridge" 2. How close are the speakers to wired network ports? Sonos allows you to turn off the wifi so it becomes just another doodad on the network. 3. For play/connect items that must be wireless we need address that once we "pair" the list by having ethernet connected device.
Assignee: network-operations → jbarnell
Is there a way to connect the main Sonos Bridge directly to the Bldg's Main Internet Provider.....when I hacked this I simply plugged it into any ethernet port...which is likely causing routing issues
Only 1 Sonos Bridge. It's placed on a desk outside the upstairs kitchen. Not the ideal nor permanent location...but the quick test was working for awhile....now time to make sure it's stable and scales ...which means putting it as a device closet to the bandwidth provider like it calls for.
I seem to remember the "network problem" with the Sonos was that they couldn't be on wireless and wired at the same time because they would cause loops. If we do connect them via wired, we need to make sure that wireless is disabled.
It's designed as it's own wireless network..mixing wired and wireless is indeed a problem...we should not be doing that. The private wireless net Sonos creates is very solid. Ultimately, I'm agreeing with Adam and will add we should NOT connect them via Wired. That defeats the whole purpose of the system and creates a whole slew of other problems like no Ethernet ports in the places we want them (bathrooms, etc)
I've never personally experienced loops with Sonos. The problem here is we use a lot of the spectrum in our Juniper wireless implementation. With sonos automatically selecting its channels we will end up with adjacent channel interference which can end up being a problem for all of the wireless.
Should we create a private wireless SSID / spectrum for the Sonos Wifi to live on?
(In reply to James Barnell from comment #2) > I've requested the following items for further understanding: > > 1. What are the installed (models, etc) Did we include the "sonos bridge" > 2. How close are the speakers to wired network ports? Sonos allows you to > turn off the wifi so it becomes just another doodad on the network. > 3. For play/connect items that must be wireless we need address that once > we "pair" the list by having ethernet connected device. James, here's the model I found in the kitchen: http://www.sonos.com/shop/products/play3
We have all models installed. Play 1's - Bathrooms and Pool Table Play 3's - Kitchen / Lobby / Other areas Play 5's - only 1 in Upstairs kitchen Media Bar - Game Room Upstairs - only 1 SubWoofer - Game Room Upstairs - only 1 If we have to use wired network ports, I'll return all this stuff....that's not how the system is designed or recommended to be used. I'm convinced we can fix wireless placement issues by moving these WiFi Access Points around. The problem I'm convinced is 2 fold 1) the placement of the 1 Bridge (the Master unit) which needs to placed or configured "closer" to the Internet/Bandwidth Access. 2) Creating a private wifi segment that this Sonos sits on to avoid any other interference and control the number of active users at any given time Jim
Summary: Sonos keeps discounting on the 1st floor → Sonos devices don't stay connected on the 1st floor
Just spoke to Sonos tech support and after I submitted a diagnostics report they suggested that we: - connect/change ethernet cable to the group controller - re position the Bridge where the other Sonos devices are no greater then 30 ft away. - clear link messages in Bridge report
Thanks Sammy! --Please explain with more details what "connect ethernet cable to group controller"..... does "Group Controller" mean the "Sonos Bridge". The Sonos Bridge IS connected to an Ethernet port but maybe the diagnostics reports don't represent that ...which is TELLING.... This suggest we connect the Bridge directly in line with our main WiFi Router. The Reposition the Bridge to no more than 30 ft away? ouch... Question back to the Rep...Can we have MULTIPLE BRIDGES? I don't think so..but it's worth asking What the heck is "CLEAR LINK MESSAGES IN BRIDGE REPORT"? How do we do that? Thanks Jim
All I reinstalled all devices from scratch late last night and ensured proper wifi placment of the devices for a proper "wireless mesh net" So far so good. The connection and connection strength appears solid. I've also found out that you can now add $49 sonos bridges (in wifi configuration) that serve only as a sonos wifi extender to cover "gap areas" I have an extra Bridge and we can plug in as needed. We are close to solving this and closing this bug.
Loree spoke to Sonos tech support today and below is what they sent her. From: "Sonos - Technical Support" <support@sonos.com> To: mtvreceptionist@mozilla.com Sent: Wednesday, June 11, 2014 1:29:51 PM Subject: Components drop from the Sonos System [Incident: 140611-001364] Recently you requested personal assistance from our on-line support center. Below is a summary of your request and our response. Subject --------------------------------------------------------------- Components drop from the Sonos System Discussion Thread --------------------------------------------------------------- Response Via Email(Edwin W.) - 06/11/2014 01:29 PM Greetings Loree, Thank you for taking the time to go over everything with me today. Please consult with your IT department to create a single Subnet for all of the Sonos Components and the Controllers. If you have any other questions or run into any issues please let me know. Your incident number for today's call is: 140611-001364 Regards, Edwin Sonos Customer Care | Tier 1 Customer Care Analyst Question Reference #140611-001364 --------------------------------------------------------------- Product Level 1: COMPONENT Product Level 2: CONNECT Date Created: 06/11/2014 01:17 PM Last Updated: 06/11/2014 01:29 PM Status: Updated - Sonos [---001:000878:10076---]
Makes Sense. Yes, please definitely CREATE this Wireless Subnet. This will not only stablize the Wifi but will also allow better Access Control as we'd only give out the password for this Wifi subnet to certain people allowed to control the music. Thanks Jim
Closing this due to Rockbot implementation. Other offices with Sonos are (Lon/Tor) have been resolved.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.