To rule out network issues, please try the steps in this article as a first step:

Many thanks. I will give it a try. Allocating “fixed” IP addresses to my “fixed” items, TV’s speakers, etc.

Do I allocate them manually on the device as a fixed IP?

It’s easier to do on the router that allocates the IP addresses.

Look to your router’s DHCP settings page, it should walk you through the process.

Once done power down all Sonos, reboot router and controller then power up the Sonos.

Looking at your first post you may be a bit confused on the networking part, SSID is only for WiFi and isn’t part of a wired connection.

When you say you “cloned the SSID” I’m not sure what you mean, if you have set up multiple AccessPoints with the same SSID that will work as long as they are true AccessPoints and not extenders or running an internal router/dhcp server.

What you want is all Sonos on the same LAN so only one router is allowed.

If you have wired a Sonosnet capable device all other Sonosnet capable devices will attempt to connect to it. You can disable the internal radio if not using a Sub or Surrounds to avoid that.

HI Stanley_4

I probably am confused….

Here’s what I have done...

I have created a single LAN by running cables from the back of the SkyQ router into my two “remote” rooms, (lounge and kitchen). In each of the rooms I have installed a Tp-Link 5 port switch (they are both simple TP-Link unmanaged switches), and from each switch in each room I have hard wired a Sonos product, a smart TV, a Sky Box, and a Wifi Access Point (so that we can connect our I-phones and I pads onto the same network. The WIFI Access Points have the same SSID as the router so that wifi connection room to room is seamless. The WIFI Access Points that I have set up on the LAN are purely there for me to access WIFI in the two rooms which are remote from the router, with thick walls. The Access Points also all WIFI access in the upstairs bedrooms. We have two Amazon Alexa's which join the network via these access points, and a smart TV.

So, my Sonos Beam and my Play:3 are on the same LAN. 

I have had the Sonos products for a few years, and they have worked well in both rooms. But I seem to have developed issues over the past few months, so I don’t know what it is…

I may try a full new system set up first, and then go from there.

Many thanks.

That sounds good, many folks get bit by picking an Access Point or using a second Wi-Fi router that splits the LAN into segments.

Do keep in mind once you wire a Sonos device no Sonosnet capable Sonos device will use your Wi-Fi any longer. 

Once you try the static IP fix and finish your setup you are probably back to contacting Sonos support to try and diagnose the network issues.

So, I have allocated 11 reserved addresses for all the hard wired devices on my LAN, and they are all showing on my attached devices screen on my sky hub software. 

I have now created a new Sonos system, having deleted my previous Sonos app, and re-installed it. Both products seemed to add OK, but……

1. If I stand next to the router in the dining room, I only see my Beam in the Sonos System.

2. If I stand next to the EAP225 (access point for wifi)  in the lounge I also only see my Beam in the app. The Beam is in this room.

3. However, if I go into the kitchen and stand by the EAP245 (access point for wifi in the kitchen), I only see the Play:3 in the app. The Play:3 is in this room.

I know this sounds ridiculous, but could my two Access Points (EAP225 and EAP245) be acting as separate wifi networks, even though they both show SSID the same as the router? 

The router and the EAP225 in the lounge are clearly synchronised, because the move between rooms is fully seamless, but the EAP245 in the kitchen is only recognising the Play:3 on the system. I have reconfigured the EAP245 from a hard reset, to use the router SSID and password.

It’s frustrating that I can’t control the two speakers from any room…….any further thoughts on what the issue may be - the thickness of the walls making me use EAP’s is the only thing I can think of that is now causing the issue.

i think this is my final update on this subject.

Having been onto Sonos support, and being helped on the phone, I now have a Sonos App that will work from my dining room, lounge, and upstairs bedrooms, with both devices appearing.

I can’t use the Sonos App in the kitchen, as it doesn’t find the same network, even though I am accessing it on the same SSID via an EAP245

My small “walkround” is to take a walk into the dining room to launch the Play3 in the kitchen - a pain in the neck, but manageable.

Tech Support suggest adding a mesh network would solve the issue entirely. I’m not sure I want to invest what looks to be £600 to make my expensive speakers work more smoothly. For similar cost, I could invest in two decent bluetooth speakers and link them to my Alexa Echo.

Oh well. 

Thanks for all help and comments - at least I now have a well ordered LAN with most of my kit hard wired into it. Thanks again.

Don’t know that unit but it looks to offer several things that don’t play well with Sonos.

You might look at some of the Ubiquity and Unifi topics as they have similar settings.

Band Steering
Load Balance
Airtime Fairness

Wireless Mac Address Filtering
Wireless Isolation Between Clients