Skip to main content
Trending Lyricist I
September 6, 2014

Problems finding Sonos system when using powerlink adaptor to extend home network

My kitchen is a wifi blackspot and so I have used a TP-LINK AV200 power-line adaptor to extend the range of my wifi to that room. So I in effect have two wifi access points (for present purposes, lets call them HomeNet and HomeNet-TPL). My kitchen is the room we use the most and the Sonos Play 5 we have there connects to HomeNet-TPL. At least, I assume it does since they are next to each other and HomeNet doesn’t normally reach the kitchen. The Sonos Bridge connects by Ethernet cable to the Homenet Router. The problem is that my iPhone App doesn’t always find my Sonos Network when it connects to HomeNet-TPL (as it normally does when I am in the kitchen) and so I cannot control Sonos. I normally fix this by walking towards the HomeNet Router and then when my iPhone connects to that part of my network it then finds Sonos. However, this is an intermitted problem. Sometimes, my iPhone app does succeed in finding Sonos when it connects to HomeNet-TPL. Any ideas to avoid this annoying problem? It is embarrassing when I have friends around and show off my Sonos system and then my controller app can’t connect! They aren’t impressed.
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.

70 replies

ratty
September 17, 2015
I think you're missing the point. Sonos can't update software to fix an inherent problem caused by some models of Powerline adapter blocking certain types of network traffic. I should point out that Sonos uses standard UPnP procedures to locate the Players; it's those Powerline units which aren't standards compliant.
jgatie
September 17, 2015
It may not be the fault of Sonos, however updated software that allows this configuration to work would be greatly appreciated. The more configurations supported would allow more units to be sold. That should be the carrot for Sonos to add this "feature".

Why would they spend the time to update software to support a configuration that they officially do not support? There is a reason powerline adapters are not supported, it is because their performance is greatly dependent on the age and usage of your electrical system, for which there are no standards. Programming to and/or supporting that type of non-standard infrastructure would be a support nightmare, which is why they do not support it.
buzz
Grand Maestro
September 18, 2015
Graham_7,

Power lines were designed over a century ago to supply 50Hz or 60Hz energy for lights, appliances, and industry. There was no anticipation of a future attempt to stuff music and video onto these wires too. Using some very sophisticated technology, we can superimpose a high frequency "carrier" on the power lines to facilitate sending some data over the power wiring, but this is a very fragile situation because, to some extent power wiring picks-up stray radio and TV transmissions and this can cause interference with electronic devices such as TV's, radios, and computers. To mitigate this interference we install filters to strip this stray high frequency energy from our power lines. This is a touted feature of all of the up scale surge suppressors -- resulting in better audio and TV and more robust computing.

On one had we are stuffing a high frequency carrier on to the power lines, but "best practices" suggest that we should strip all high frequency information from the power lines. Even if we don't explicitly strip the carrier, large appliances such as microwave ovens, furnaces, and air conditioners tend to absorb the carrier -- unless they have been specifically designed not to do this.

Bottom line, transmitting audio, video, and data over power lines is hit or miss and very much depends on the local situation. Some users report success while others report frustration. Further, a working situation could be disrupted after the installation of a new appliance as simple as a modular power supply. Personally, I would not design a system to rely on EoP (Ethernet over Power Line), but EoP is worth a try in situations that are too hostile for WiFi or SonosNet wireless and pulling Ethernet cables is not practical. Sometimes EoP is a miracle, mostly it is a frustrating waste of time.
Contributor III
September 27, 2015
There's an easier way to do this. Set up a wireless access point from the Sonos itself. This way you do not have to set up the access point from hard wiring to the main router, you can simply hardwire the access points into one of the spare Ethernet ports at the back of the Connect.

I use Sonos to distribute wifi throughout my house this way. I have Sonos everywhere to create the sonosmesh, then connect a wireless access point a sonos on each floor.
buzz
Grand Maestro
September 27, 2015
pknowq,

Yes, this painless scheme works, but at some point one can swamp the SonosNet with non audio traffic. Careful use of this facility can work miracles. While I'm not supporting a WiFi access point here, I'm typing through a wireless CONNECT because my computer is sitting in a hard to wire spot.
Trending Lyricist I
October 18, 2015
Thought I'd check in to see whether there are any further ideas. I have continued to live with and be frustrated by this problem.

Interesting thought from Buzz to get an access point connected to the SonosNet which I will immediately try and sort out. Does an "Access Point" have the same network name as the main wireless point? Will devices get confursed "roaming" from one to the other. I really don't know. I assume not but will give it a go.

Thanks, Buzz

One point though on your earlier comment that electrical wires were not designed for audio etc. All that seems to be going over it though as far as Sonos is concerned are instructions to the SonosNet since the audio doesn't use it. So rather simple and presumably non-intensive audio. So still surprised that Sonos do not somehow fix the lack of network "purity" with some software fix.

But thanks anyway.

Kind regards
TMONTB
buzz
Grand Maestro
October 18, 2015
TheManOnTheBus,

Start with the same SSID ("network name") for all of the access points and try not to use the same RF channel for overlapping areas. This is the conventional wisdom for "best practice". Unfortunately, I find that "roaming" can be hit or miss, particularly for iDevices. Some devices roam better if one uses different SSID's for each access point. Although it is counter intuitive in most cases, a given collection of devices may roam better if all of the access points use the same channel. In any case, restrict your choices to channel 1, 6, or 11. Avoid using "Wide" or "40MHz" channels. Experiment and use the scheme that works best for you.

iDevices are very stubborn and refuse to give up a distant access point, even when a much better deal is available nearby. You can force the iDevice to shop around by swiping up from the bottom of a screen, turning OFF the WiFi for a second, then turning the WiFi ON again.

---

There is a different approach for high end (usually called "enterprise") networking. In addition to the enterprise grade access points, there is a "controller" managing all of the access points. In this scheme the controller manages roaming. As a client moves from one coverage area to another, the controller passes the client from one access point to the next. This is seamless for the user. Unfortunately, the cost for this level of performance is out of the comfort zone for most home users.

---

If you wire a SONOS unit into an EoP (Ethernet over Powerline) device, SONOS will use this path for all data -- music and control. If the EoP device is struggling with its own connectivity, the issue is physical and not something that SONOS can fix in firmware. (It is really a variant of a "defective network cable")
Lyricist I
March 16, 2016
Hi guys,
I had exactly the same problem. Not the powerline seems to be the problem but the wifi established by the powerline device. I now disabled the powerline wifi and used an airport express instead. The airport express is connected to the powerline device with ethernet cable. Since that (a few days now) I have no problems to use my sonos controller with my iPhone. Maybe it' going to help you, too.
Cheers
ratty
March 16, 2016
I had exactly the same problem. Not the powerline seems to be the problem but the wifi established by the powerline device. I now disabled the powerline wifi and used an airport express instead. The airport express is connected to the powerline device with ethernet cable. Since that (a few days now) I have no problems to use my sonos controller with my iPhone. Maybe it' going to help you, too.
Sonos controllers use discovery broadcasts to locate the players. Some Powerline/AP units appear to be a bit reluctant to forward such traffic between their own WiFi and the Powerline connection.
Lyricist I
June 28, 2016
I had this issue recently. My controllers could not see the sonos system after I had installed much needed powerline extenders.

I solved it by plugging the master of my powerline extender into my router. Then I plugged in the slave out in my living room and connected it to my connect via ethernet. Now everything works perfectly. Has anyone else tried this and been successful. My tplink powerline extender slave unit has two ethernet ports.I have an android phone that I'm controlling the system with, but it also worked on my pc. So happy to have this resolved.