Trending Lyricist I

Answered

Sonos Sub keeps disconnecting from wired Beam 2 (5.1 setup)

38 replies
1407 views

My setup is Beam (Gen 2), two Sonos One SL and Sub (Gen 3). Also have a Playbar with 2 Play:1 and Sub (Gen 2) in another room.

I kept having the Sub (Gen 3) disconnection when on wireless mode so I switched to wiring the Beam and deleting the wireless network. The Beam is wired to a Linksys router extender. All the components, including the Playbar based 5.1 system now seem to connect through SonosNet. Everything shows WM:0. However, only the Gen 3 Sub keeps falling off to the “?” mark. It seems strange that only the newer sub keeps disconnecting when everything else works fine. In order to reconnect, I have to reboot the Sub and then it works fine for a few hours until the question mark shows up again on the app. Sucks to have to keep doing this every time plus I loose my tuning every single time it happens.

The Sub (Gen 3) is only about 3 or 4 feet away from the Beam 2. The Playbar system is a whole floor level away and works perfectly connected through the wired Beam (I am assuming this is the case as this is the only wired component and everything is at WM 0).

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.

Ken_GriffithsAnswer

The Beam is wired to a Linksys router extender.

Whether this is a simple WiFi extender or a wireless mesh node, this is an unsupported configuration. There needs to be a wired path back to the router.

Wiring to a mesh primary node is permissible. Extenders aren’t supported at all.

Except that I have had it like this on my other Sonia system for the past 4+ years without absolutely zero issues.

I think you mean with ..zero issues.
What @ratty and I mentioned is correct. If you see the below link to the Sonos ‘System Requirements’ you will see that it mentions…

In WiFi mesh networks, Sonos products must be wired to the primary mesh node if using a wired setup.
If you need to extend your home WiFi to use Sonos in a wireless setup, we recommend using a WiFi mesh router to do so.

And the following networks and devices are unsupported:

Wireless internet connections such as satellite, mobile hotspots, or LTE routers
Guest networks or networks that use a portal login page
Networks using wireless range extenders (see also 2 above)
Ethernet over Power (EOP) devices
WPA/WPA2 Enterprise

See link:

https://support.sonos.com/s/article/126

Ken_Griffiths

Ensure you have not switched off the WiFi adapter in the Beam’s room settings, this is required to communicate with the Sub direct, even when the Beam is wired, the wireless adapter needs to be set to ‘on’.

UKMedia

The sub connects to the Beam via an internal 5gHz wi-fi signal. I suspect that this is caused by wi-fi interference.

Remember: Sometimes Red Wine helps :)

ratty

The Beam is wired to a Linksys router extender.

Whether this is a simple WiFi extender or a wireless mesh node, this is an unsupported configuration. There needs to be a wired path back to the router.

Wiring to a mesh primary node is permissible. Extenders aren’t supported at all.

Ken_Griffiths

Note you would likely be better off reducing the system-backhaul by wiring a single Sonos device (not a surround or sub) direct to your main router and un-cabling the Beam from the Linksys extender too.

edit: Ah @ratty beat me to it.

S

ShadowboricuaAuthor

Trending Lyricist I

The Beam is wired to a Linksys router extender.

Whether this is a simple WiFi extender or a wireless mesh node, this is an unsupported configuration. There needs to be a wired path back to the router.

Wiring to a mesh primary node is permissible. Extenders aren’t supported at all.

Except that I have had it like this on my other Sonia system for the past 4+ years without absolutely zero issues.

Ken_GriffithsAnswer

The Beam is wired to a Linksys router extender.

Whether this is a simple WiFi extender or a wireless mesh node, this is an unsupported configuration. There needs to be a wired path back to the router.

Wiring to a mesh primary node is permissible. Extenders aren’t supported at all.

Except that I have had it like this on my other Sonia system for the past 4+ years without absolutely zero issues.

I think you mean with ..zero issues.
What @ratty and I mentioned is correct. If you see the below link to the Sonos ‘System Requirements’ you will see that it mentions…

In WiFi mesh networks, Sonos products must be wired to the primary mesh node if using a wired setup.
If you need to extend your home WiFi to use Sonos in a wireless setup, we recommend using a WiFi mesh router to do so.

And the following networks and devices are unsupported:

Wireless internet connections such as satellite, mobile hotspots, or LTE routers
Guest networks or networks that use a portal login page
Networks using wireless range extenders (see also 2 above)
Ethernet over Power (EOP) devices
WPA/WPA2 Enterprise

See link:

https://support.sonos.com/s/article/126

S

ShadowboricuaAuthor

Trending Lyricist I

The Beam is wired to a Linksys router extender.

Whether this is a simple WiFi extender or a wireless mesh node, this is an unsupported configuration. There needs to be a wired path back to the router.

Wiring to a mesh primary node is permissible. Extenders aren’t supported at all.

Except that I have had it like this on my other Sonia system for the past 4+ years without absolutely zero issues.

I think you mean with ..zero issues.
What @ratty and I mentioned is correct. If you see the below link to the Sonos ‘System Requirements’ you will see that it mentions…

In WiFi mesh networks, Sonos products must be wired to the primary mesh node if using a wired setup.
If you need to extend your home WiFi to use Sonos in a wireless setup, we recommend using a WiFi mesh router to do so.

And the following networks and devices are unsupported:

Wireless internet connections such as satellite, mobile hotspots, or LTE routers
Guest networks or networks that use a portal login page
Networks using wireless range extenders (see also 2 above)
Ethernet over Power (EOP) devices
WPA/WPA2 Enterprise

See link:

https://support.sonos.com/s/article/126

Sorry for the spelling errors before. I was in a rush.

Thank you for your response regarding this configuration. Would you be able to explain why this is a problem that only affects the Gen3 Sub and not my other Gen2 Sub or surround speakers?. They are all connected to the same network in exactly the same manner and only the Gen3 keeps disconnecting.

Ken_Griffiths

Sorry for the spelling errors before. I was in a rush.

Thank you for your response regarding this configuration. Would you be able to explain why this is a problem that only affects the Gen3 Sub and not my other Gen2 Sub or surround speakers?. They are all connected to the same network in exactly the same manner and only the Gen3 keeps disconnecting.

A Sonos Subs does not ‘normally’ use a local router WiFi, or SonosNet signal - instead it connects directly to its ‘bonded’ speaker/main-player using either a 5Ghz ad-hoc wireless connection (which is highly recommended method of connectivity). or in some cases it may use a wired network connection if the wireless connection to the main player is inhibited by its WiFi adapter being switched off (not a recommended method of connectivity) …In the latter case, it’s always good practice to wire all players, but as stated that type of setup is not helpful in some cases, as network latency often comes into play with that type of setup.

If the first ad-hoc wireless setup method is proving problematic for you, then perhaps the first thing to look at is ‘wireless interference’ in and around the Sub and the main bonded player. Sometimes, a simple reboot of the main player can solve the situation, or simply moving the Sub closer to the main player, or changing its location in the room might sort the matter.

The reasons for the earlier settings mentioned was mostly to improve the overall network connectivity and reduce the general wireless interference, so that the SSDP multicast discovery of the players and unicast connection could be improved using SonosNet on the same chosen channel, rather than using your WiFi mesh system, which may have Hubs operating on their own different WiFi channels.

Hope that assists.

S

ShadowboricuaAuthor

Trending Lyricist I

Sorry for the spelling errors before. I was in a rush.

Thank you for your response regarding this configuration. Would you be able to explain why this is a problem that only affects the Gen3 Sub and not my other Gen2 Sub or surround speakers?. They are all connected to the same network in exactly the same manner and only the Gen3 keeps disconnecting.

A Sonos Subs does not ‘normally’ use a local router WiFi, or SonosNet signal - instead it connects directly to its ‘bonded’ speaker/main-player using either a 5Ghz ad-hoc wireless connection (which is highly recommended method of connectivity). or in some cases it may use a wired network connection if the wireless connection to the main player is inhibited by its WiFi adapter being switched off (not a recommended method of connectivity) …In the latter case, it’s always good practice to wire all players, but as stated that type of setup is not helpful in some cases, as network latency often comes into play with that type of setup.

If the first ad-hoc wireless setup method is proving problematic for you, then perhaps the first thing to look at is ‘wireless interference’ in and around the Sub and the main bonded player. Sometimes, a simple reboot of the main player can solve the situation, or simply moving the Sub closer to the main player, or changing its location in the room might sort the matter.

The reasons for the earlier settings mentioned was mostly to improve the overall network connectivity and reduce the general wireless interference, so that the SSDP multicast discovery of the players and unicast connection could be improved using SonosNet on the same chosen channel, rather than using your WiFi mesh system, which may have Hubs operating on their own different WiFi channels.

Hope that assists.

So in conclusion, would my problem be solved if I just wired the Beam directly to the Verizon FIOS modem/router instead of the extender?

Ken_Griffiths

So in conclusion, would my problem be solved if I just wired the Beam directly to the Verizon FIOS modem/router instead of the extender.

Yes, the recommendation has been to wire a Sonos device to your main router, which will put all players onto SonosNet and reduce any backhaul too.. the wired device can be a your Beam, or any standalone modern Sonos device (ideally), just do not use a surround, or Sub …and obviously do not wire your Sonos products to your other WiFi access points/hubs.

When wiring a player to the router, ensure it’s at least one metre away from the router to reduce interference and set the SonosNet channel so that it is at least 5 channels away from your router 2.4Ghz channel. It’s best to set your router to use fixed non-overlapping WiFi channel 1, 6 or 11 too.

Its helpful to set your router and any access points to use the same SSID, WiFi channels and set all 2.4Ghz band connections to use a channel-width of 20MHz only.

When done and all your Sonos devices are then running on their SonosNet signal (which is confirmed in the Sonos ’About My System’ area of the App - it will show the wireless modem of each device as WM:0) ..then goto ‘Settings/System/Network/Manage Networks’ in the Sonos App and remove the 2.4Ghz SSID/Network credentials (if stored?) - If you have Sonos portable devices (Roam/Move) then leave the 5Ghz SSID and run those devices on that band, otherwise remove those 5Ghz credentials too (if applicable)… The wireless network credentials are not required for devices running on a SonosNet signal and doing these things will help to ensure your products do not ‘hop’ between the SonosNet signal and your WiFi signal.

Show more replies

Sign up

Login to the community