S2 controller app dropping rooms

U

I have updated to S2 app and added a move speaker to the 3 Sonos 1s, 1 Sonos 3, play bar and sub . The S2 app keeps dropping the speakers and I can’t see them on app, they will then re appear only to be dropped again later, this is very annoying. I have a play 5 also which now operates on a S1 controller on the same WiFi network and this seems to be operating ok. Are there fixes planned to be made to the S2 controller app as it seems very unstable or should I revert all speakers back to S1 controller if that’s possible?

 

31 replies

G
Userlevel 1

Upgraded to S2 - worked good for a week - now everything is dropping and can’t find my speakers????? What is going on?   Had Sonos for 8 years - now all kinda of problems!   This is not good - maybe sell everything and switch to Bose !

P

I’d recommend a refresh of your local network. Unplug all your Sonos devices. Reboot your router. Give the router a couple of minutes to come back up, then plug back in your Sonos devices. Give them a couple of minutes to reboot and reconnect as well, then test. 

That is the general useless “did you try to turn it off and on again?”.
I’m a network engineer myself, and I see the same behaviour on my enterprise grade system too, since S2. OP also states he doesn’t have an issue with the Sonos speaker on a S1 controller, so very unlikely his network is the cause.
I did notice when you unplug/replug the speakers, they show up again for a brief moment… but that isn’t the solution we’re after.

G
Userlevel 1

I have rebooted modem and router - nothing seems to be helping - music stops and speakers drop off.  I have my sonos using a  separate channel on my wireless router - is this an issue with S2?  Is my router no longer compatible? Is there a list of S2 compatible routers somewhere?

M

I have the same exact problem since I upgraded to S2 and multiple attempts to get feedback from Sonos have not been answered.  Please note that the Sonos App on the MacOS is not dropping the speakers.   It is only the S2 app on my iPhone 11 (iOS 13.5.1).  And I did try to reboot the router.

G
Userlevel 1

I fixed my problems.  First, checked my matrix: https://forums.homeseer.com/forum/media-plug-ins/media-discussion/sonoscontroller-dcorsus/1283672-sonos-network-matrix

Saw I had major wi-fi interference.  Purchased a Boost and switched back to SonosNet.  So 8 speakers on SonosNet and my Move on wi-fi - every thing back in order and working great.  You can group SonosNet speakers and wi-fi speakers with no issues. 

T

It’s definitely a Sonos S2 problem. I don’t want to be bothered to turn everything off and on again every time this happens and it’s happened several times. I think Sonos needs to take a hard look at S2 and provide us an update. This never happened with S1.

T

So you ran wires for a wireless system?

T
Badge

Same issues with ‘upgrading’ to S2 controller. For 2+ years on S1 my pairs of 3’s, 1’s and Connect worked liked a charm. Then upgraded to S2 and have had nothing but problems. For over a week I’ve tried to resolve with online, chat and phone support. Everyone keeps telling me to reboot my router, direct connect one of my 3s, direct connect my Connect to the router. Reboot my devices. Reboot my router. I have tried it all with no success. Sometimes my controller (and I have it installed on two laptops as well as my mobile) sees my network, sometimes it doesn’t. Sometimes it sees my network but not all rooms, something its does. Sometimes it sees all rooms but can not connect with all music services (Sirius and TuneIn primarily). Sometimes it plays fine for 5-10 minutes, then drops connectivity. This sounds to me like a software issue but support keeps claiming, no, its a wifi network issue. I have had Xfinity run a full diagnostic on my modem so I know that’s not the issue. Is my only option to keep rebooting the network until it sticks?

C

I had similar issues. Solved it by disabling the “AIRTIME FAIRNESS” on my Netgear router.  Check your routers and see if they have AIRTIME FAIRNESS enabled or anything that prevent network lag when slower devices connect and disable it.  Worked for me.

S

I had no problems with my S2 upgrade for at least 2-3 months.  My problems started the exact same day i took on the free trial for Sonos Radio HD.  My understanding is the HD upgrade requires a feature of the S2.   I’m stuck with literally $1000s of Sonos I can’t use.  Only my Sonos move seems to reliability connect.  I’ve also noticed that my iPad had one set of rooms working while my iPhone had a different partially functional list.  This sucks!

E

I am having the same problem. I upgraded to Sonos 2 and it is now randomly dropping speakers.  Very disappointing. Doesn’t seem like there is a good solution 

controlav
Userlevel 7
Badge +23

I have just got a new router from Sky but don’t think that is the root cause.

LOL what makes you think that?? SkyQ routers are known to destroy Sonos network packets, there is a great diagram somewhere on here detailing it.

There are also SkyQ specific notes on the general WiFi page:

 

Author of the leading independent Sonos app for Windows, the only Sonos app for Xbox, and a Sonos app for iOS
S

I have now joined the ranks of having to reset the system every day so I can watch movies. I’m done with SONOS - Congratulations SONOS - you win.  The system is all sitting in the basement now and replaced by BOSE.  The BOSE System works like the flawless S1 did.

Life is too short for Rip offs like this.

 

 

 

Airgetlam

I’d recommend a refresh of your local network. Unplug all your Sonos devices. Reboot your router. Give the router a couple of minutes to come back up, then plug back in your Sonos devices. Give them a couple of minutes to reboot and reconnect as well, then test. 

Bruce
M
Userlevel 2
Badge

Thanks - will have a play with sky q to see if I can follow what it says in the article

106rallye
Userlevel 7
Badge +17

Yet you did not ask for help? 

Airgetlam

That’s indeed the general ‘it might be a duplicate IP address issue due to problems with your router and improper IP assignments, which also fixes potential issues with DNS data not being transferred through the system properly‘, although the latter is not the issue that this user is experiencing. 

If you are indeed a network engineer, you’ll be familiar with both the more complex way that Sonos interacts with a network, as well as the challenges presented by some routers not handling proper DHCP assignments due to failures of various types within the router, exposed by the Sonos doing a soft reboot during the update process, and requesting new IP addresses. 

But I’m not a network engineer. I’m just familiar with the way Sonos works, and have been helping folks long enough to know that in greater than 95% of the cases, this resolves the issue. I’m also smart enough to know that it isn’t a silver bullet, but once it has been completed unsuccessfully, can then focus on other, rarer potential issues. 

But since you’re a network engineer, and must have greater knowledge than I, I will bow out, and let you resolve this user’s, and your, issues. 

Bruce
P

I don’t know which part of: “The Play:5 still on the S1 controller operates normal and doesn’t drop off” you missed. Also personally never had routers hand out duplicate IP addresses. I’ve seen many ISP endpoints stop handing out IP addresses, bc the DHCP pool was too small, and/or leases of devices that left the network didn’t expire already (to make the IP address(es) available again for new clients).
I do agree that making IP reservations based on devices MAC-addresses outside of the DHCP scope, rules out many issues people have with bonjour/mdns and caching in their computers/other endpoints. That way, you simply cannot hand out the same IP address twice. Most of the time duplicate IP addresses are the user’s fault, bc they manually assigned one on a device, and didn’t exclude it from the DHCP scope. And maybe when the timing is right (and such IP is handed out by DHCP), and afterwards they start up the manually assigned device, mayhem happens… but any other order, prevents the router from handing out that IP, as it should be in it’s ARP cache.

P

I noticed too, that while the devices drop from the iOS controller, their Airplay keeps advertising.

i also use Roon, and while they dropped, I can also still see the Airplay endpoints, but the sonos ones disappeared. Not all Airplay endpoints are able to stream though.

Unplugging 1 speaker from mains, or ‘reset/reboot’, usually brings back the entire system.

I’m considering resetting all speakers, and do a downgrade to S1.

R

 i have the same issue - before upgrading to S1 ourer sonos was stable as a mofo,

We have a unifi network - all speakers worked like a charm

 

We have 2 x S1 + 1 Move + 2 x play5 - after upgrading its becoming very useless and really really unstable.

 

Airgetlam

I’d be happy to pay for shipping of these unused Sonos devices, so that you don’t have to waste space storing them. 

Bruce
R

Hi - we solved all ourer issues by cabling some of the units - after this everything been rocksolid.

A
Badge

I have avoided changing to S2 due to all the issues I was seeing, however two weeks ago I added a new speaker that was only compatible with S2.

 So I have had no choice but to split my network and leave my older stuff that isn't compatible on the S1 app and the newer stuff on the S2 app.

I bet you don't need them, but I'll give you two guesses which system works and which one is as good as useless!!!

 I thought splitting the network and having to use two apps was ridiculous at first, now I'm just glad that at least the S1 stuff works.

I would have hoped after over 2 years this would have been resolved, its a joke considering the costs involved in a system.

I refuse to constantly reboot all my speakers scattered around the whole house and I don't see why I should have to mess around with router settings or even attempt to wire, what was pointed out above, a 'wireless' system. If it all worked on S1 and some still does, working on the same router, with the same settings and same network traffic, surely it is a fundimental S2 issue that requires urgent attention.

 The only solution I can see currently is to scrap the new speaker, switch it all back to S1 and not bother with any more Sonos in the future, which would be a real shame as I've loved it up to this point.

Airgetlam

So, you’re saying you bought network based devices, but are unwilling to do any work on your network in order to facilitate the devices you purchased to connect to it. 

Kind of like buying a car, but refusing to put tires on it when it is necessary. Not exactly, but close enough. 

You may not care, but for others who are interested, this is most likely either wifi interference of some type, or even a simple duplicate IP address issue, easily solved by going in to your router’s software and setting up reserved IP addresses for your Sonos devices, all of which work off of your network. 

Bruce
A
Badge

Apologies, but that is a nonsensical response in my opinion.

I had written a longer reply, but having now seen your replies on other posts from frustrated people, I just think you are missing the point, simply put it worked on S1, it now doesn't on S2.

 However if your advice helps anyone then it's certainly worthwhile, I just don't agree that it should be required.

Reply


Terms & ConditionsCookie settings