Skip to main content
User910341
Contributor I
July 28, 2015

Large home with Multiple access points

  • July 28, 2015
  • 21 replies
  • 15029 views
Sonos was recently modified to allow broadcasting via WIFI without a Bridge or Boost.  This is a great option.  I would suggest a further, related enhancement.  In large homes it is common to have 2 or more access points to provide strong WIFI throughout the house.  The current deployment of Sonos over WIFI works with multiple access points on the same subnet only if you use the same SSID for all access points.

While there are some advantages to using the same SSID for "roaming" it is often found that many phones and laptops do not automatically switch to the stronger signal of the closest access point if they can still get a signal (albeit weak) from the further access point they originally connected to. To address this many of us use different SSIDs (still on same subnet) so users can manually connect to the stronger signal if desired when moving around the house.  

Unfortunately the current Sonos iphone software will not find you system if you change to a different access point with a different SSID even if still on same subnet (although computer software with a wired connection to the same subnet will).

Ideally Sonos software would be modified to allow both control from a different SSID on the same subnet, and the Sonos system itself to span multiple access point on the same subnet whether using the same or different SSIDs.  Currently the work around requires mulitple Bridges or Boosts. Pretty much all other devices on the same subnet can see each other regardless of which access point (SSID) they are attached to, why not enable this for the Sonos system?
    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.

    21 replies

    Show previous replies
    accguy
    accguy
    Lyricist III
    June 10, 2018
    Nobody says you cannot use multiple Access Points. However, they must be configured as access points, without DHCP running, and on the same subnet and SSID. In other words, they can't be configured as routers.

    And by the way, nobody from Sonos has commented in this thread. So "Sonos" is not telling anyone anything. They are all knowledgeable users who enjoy helping others, but they are not official Sonos spokespeople.

    I just got off the phone with Sonos Support. They told me that multiple APs are Not Supported. The tech told me it was because that Sonos devices do not support changing channels, and my two APs are on different channels.

    So, instead of updating their software to change channels (and maybe have the music skip, pause, or experience some other brief issue) they have decided to let the device drop from the controller so you cannot use it.

    Just when I was starting to like and recommend Sonos again...

    Might not be supported but it works if using the proper kit. I installed 8 access points with 10 zoneplayers across 3 different channels in a 3 storey Georgian 10 bed house (not my house!!) and can roam between AP’s from one end of the house to the other with an iPhone and control everything..
    I did have issues when trying to use standard residential router/ap that you could only ‘see’ the devices that were attached to the particular AP that you also were connected to, but swapped to a Ubiquiti Unfi system of managed AP and haven’t looked back in terms of coverage and performance.

    I get it, but, I have random zoneplayers that drop out from time to time. The Sonos support agent saw my diagnostic files and said my mutli AP setup was not supported. My options, if I wanted more help, were 1) configure and use SonosNet, or 2) Convert my setup to use only 1 AP. I have been using multiple APs for years, but, suddenly over the last few months I have been having issues with zoneplayers dropping off the system. And, if I want help from Sonos (not like they would expose any real troubleshooting info to users) then I have to convert a /supported/ configuration. Sucks.
      Terms & ConditionsAccessibility statement