Skip to main content

This is more of a nuisance than anything else so I did not formulate it as a question. Periodically, the Sonos app on the iPhone, iPad or PC will be unable to find the Sonos system or will only find some of the devices in it. It is sometimes the case that the iPhone for example finds everything, the iPad finds some devices and the PC finds still a different combination of devices. The system contains a Connect, two Play 1s and a Move. Sonosnet is not in use. Sonosnet did not work well in the environment and appears to suffer from interference from my 4 node Linksys Velop mesh Wi-Fi system. The mesh makes use of the overlapping 2.4 GHz Wi-Fi channels thus stepping on Sonsnet when it tries to use 1, 6 or 11. The Connect is wired via Ethernet and its wireless radio is disabled. Both Play 1s are on Wi-Fi, as is the Move.

From the layer 2 perspective, the MAC address table of every switch in the network contains the MAC addresses of every Sonos device and of all devices running the Sonos app. The switches are all Cisco managed switches. While this problem is occurring, the MAC address tables of all switches retain the MAC information so this eliminates the possibility that the issue is due to switches losing MAC info for some devices.

From the layer 3 perspective, the Wi-Fi connected Sonos devices, the wired Sonos device, the smartphones, tablet & PC with the Sonos app that are having the issue with finding the Sonos system are on all on VLAN 1. The PC is wired via Ethernet. I have reserved the IPs for all Sonos devices in DHCP. While this problem is occurring, all Sonos devices & all devices running the Sonos app are fully pingable with sub-4ms ping times.

Many other systems that use an app on the same mobile devices, wired & Wi-Fi network & VLAN to reach their devices never have discovery issues. 9 Reolink cameras, a pool cleaner, a Simplisafe alarm system, a MyQ garage and gate opener, a Ring video doorbell with 5 Chimes, 4 Brilliance Smart outlets, 2 Govee thermometers, a Lutron Caseta system, 7 Amazon Dots, 2 Ecobee thermostats, and a sprinkler controller all with their own mobile apps all work, all of the time, and do not have issues with being unable to find their respective system components. This is clearly a Sonos-only issue on a stable, monitored and well maintained network. It is also a very small and simple Sonos implementation, having only 4 Sonos devices. It is also the case that once the app can see all Sonos devices, it readily plays music to all of them for hours at a time, until we use the app to turn off the music. It doesn’t lose track of the system once it finds it.  

Another puzzling aspect is that if it is just allowed to sit, without restarting anything, the devices will eventually show up. That is not helpful when you are ready to turn the music on and there is no system found. Very often the app can be Reset, then told to join an existing Sonos system and it finds everything it could not find prior to the Reset. As a former software developer, I see at least one change Sonos could easily make. Before telling the user their Sonos system cannot be found, the app could internally perform the same Reset step, and then tell the app to join the existing system. If it cannot find the Sonos system after that is tried, then it can say it has a problem. It seems odd that if a Reset often resolves this, that the app is not written to try that before alerting and frustrating the user. Because many other products, using various networking protocols and standards, readily find all of their devices on the same network, when the Sonos app cannot, they really need to examine what they are using as a discovery method, because it is either flawed or not robust enough.

Comments from others experiencing this behavior would be welcome and hopefully Sonos will look into what should be a simple thing to resolve.

I don’t use managed switches, but I have encountered similar issues in the past with my Sonos system and IIRC it first started for me when Apple introduced their ‘Private Address’ MAC spoofing feature and ‘WiFi Assist’ features - which I now choose to leave disabled, but whilst things have improved with the SSDP multicast discovery of devices, I still get the odd ‘glitch’ of HT surrounds not appearing occasionally. The matter is usually resolved in my case however by closing the Sonos App fully and toggling off/on the iOS mobile network connection and that often fixes the issue. 

I have also reserved all the Sonos IP addresses in the routers DHCP reservation table, but by all accounts, from loitering around the Sonos community, it does seem this is not a widely reported issue so it might be related to my wireless mesh network (albeit I run my speakers on SonosNet, but not the controllers obviously).

I haven’t noticed the issue on our Android Tablet Controller App, so I’m left wondering if it’s an iOS issue?


Thank you for responding to my post. I will give these suggestions a try!


Thank you again for your reply.

On investigating ‘Private Address’ MAC spoofing and ‘WiFi Assist’, I found, as you mentioned, these are Apple features. While that could explain the inability of my iPhone or iPad to locate my Sonos system, or parts of it, it would not explain the Windows Sonos app on a Windows 10 PC having that issue too. On the plus side, Sonos seems to play from all my devices most of the time, even if it only appears to ‘find’ 1 or 2 of them. 


That certainly may be one cause of many, but I’d also be looking at the potential for wifi interference To be causing any of your controllers at startup to have the potential challenge of finding the Sonos ‘system’. The need for each Sonos device to cross communicate, something not common to most of the devices you’ve listed, makes them potentially more susceptible to interference in the rich environment you have. 
 

However, lacking hard data is inhibiting an intelligent analysis. I would certainly recommend that you submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the phone folks, they have tools at their disposal that will allow them to give you advice specific to your Sonos system and network.


Thank you!

I just submitted a system diagnostic while this was occurring. I have investigated wi-fi interference as best I can with the tools I have. I also had my mesh system re-examine the 2.4GHz channels it is using and pick those with the least interference. I am not using Sonosnet, so it is not taking channel 1, 6 or 11, and potentially introducing interference with Wi-Fi mesh. One thing that has me discounting interference as the cause of not finding the Sonos system is that the device most frequently not seen is my wired Ethernet Connect while using the Sonos app on my Wired Windows 10 computer. 


When a SONOS controller starts up, it must “discover’ all of the players. I find that the controllers are very impatient. If discovery is too slow, for whatever reason, you’ll have this result. I see this too. Slow discovery can be a result of network traffic or a process that is distracting the controller device.

Out of curiosity, how many devices are on your network? This is pure speculation on my part, but I wonder what happens if there are x devices on the network, the controller device (phone-pad-PC) can only process x-n devices per second, sometimes a SONOS device or two fall at the end of the list and the SONOS controller App times out before discovering a SONOS device or two.

Is your network partially wired, fully wired, or fully wireless? On your PC go to Help → About My Sonos System… .  and look at the Associated Product. The controller is working through this SONOS device. If the Associated Product is struggling for data or the PC is struggling with its connection to the Associated product, you might experience timeouts. Are you experiencing any issues with missing album artwork? There is an aggressive timeout here too.


Thank you!

I just submitted a system diagnostic while this was occurring. I have investigated wi-fi interference as best I can with the tools I have. I also had my mesh system re-examine the 2.4GHz channels it is using and pick those with the least interference. I am not using Sonosnet, so it is not taking channel 1, 6 or 11, and potentially introducing interference with Wi-Fi mesh. One thing that has me discounting interference as the cause of not finding the Sonos system is that the device most frequently not seen is my wired Ethernet Connect while using the Sonos app on my Wired Windows 10 computer. 

If one or more SONOS devices is wired, you are using SonosNet. MOVE and ROAM cannot be wired and will use WiFi. In About My Sonos System… WM:0 indicates a unit is using SonosNet, WM:1 indicates WiFi. MOVE and ROAM will always be WM:1.


Remember, as discussed in the Diagnostics - How do they work? thread, you have to notify Sonos as to what diagnostic they’re going to look at, and for what issue. Faster response tends to be from a call to Sonos Support directly to discuss it, but posting the diagnostic number here will hopefully elicit an answer from the forum moderators, when they have a chance. 


The two Play 1s and the Move are WM:1. The Connect is WM:0. Connect has wireless disabled. There is no Sonosnet at work from viewing the matrix and with no other wireless WM:0 devices for the Connect to build a Sonosnet with, I have ruled out Sonosnet as a factor. 

Things have been solid since I reworked STP for my wired 100Mbit devices on the theory that blocking could have cutoff the Connect at times. In cases where the problem was most chronic, restarting the Connect was always a reliable way to get things working again, hence my focus on things that could afftet the wired Connect. 

Thank you all for the suggestions and comments I will followup if things change.