S1 app suddenly unable to find my system today 11 Mar 2026

Follow up - within 10 minutes of posting my question I rebooted my router and this time Sonos S1 app has found my system and is working again. About a 2 hour outage. !!! 

Could be time for a new router...

Thanks for your response. No, pretty sure the router is fine. After sending my follow-up message above the system repeatedly disconnected throughout the day but I was eventually able to reconnect it by the conventional methods, i.e unplugging everything to re-boot and then plugging everything back in. That’s quite a chore to keep repeating as I have 9 Sonos devices using S1 throughout the house plus a Roam which uses S2.

Having received repeated warnings when adding more tracks that there is insufficient memory I’m guessing that is the problem. I need to find a solution so I'm thinking of stripping my classical tracks out of the library and putting them into a separate library, that should free up a significant amount of memory?

I could delete some of my playlists but I use them a lot so that might be a last resort. I know I have a lot of duplicate tracks but I’m not keen to weed those out because a. it would take forever, and b. It would mean being unable to listen to complete albums.

I'm guessing this is a common problem as the years go by and collections grow.  Any suggestions gratefully received !!

John

There is a hard limit of 65K Library tracks, but there is also a memory limit. Long track titles and file names can exhaust memory before the 65K limit is reached. I’ve noticed that some rippers will insert the whole first stanza into the track name and file name. In terms of file name 01.FLAC, etc. is fine.

Playlists and Queues can also run out of memory, I use short file names. Using the Windows Desktop Controller I can manage Playlists and Queues with tens of thousands of tracks.

S1 and S2 systems can coexist on the network, but not interoperate.

If you haven’t already, I recommend that you “reserve” IP addresses in the router for all regular network clients.

Over the past few days there have been reports suggesting that SONOS has recently amended the network protocol such that some router defaults are no longer appropriate.

Possibly move some or all your music to a Plex server? 

https://support.sonos.com/en-us/services/plex

Thanks so much for responses:

Buzz -

Just checked and saw that 62,884 tracks in my library but admit I do use long titles for classical tracks in particular.

My library is located on the hard drive of my iMac so no Windows Desktop Controller. I’m not very technically knowledgeable so not sure if there is a Mac equivalent.

Yes I knew that S1 and S2 operate independently. I have separate, but identical, libraries for the S1 and S2 systems (Roam 2). I get same the warning when I add tracks to the Roam’s library but the Roam is still connecting OK. Maybe problems with S1 memory shortage could also be because 3 of my S1 devices are first generation S5 players so getting ancient? Also have 5 Play 1’s and a 1st generation Beam on S1.

I’m sorry for my lack of technical knowledge but I’m afraid I don’t understand your final 2 points about reserving IP addresses and regular network clients, and SONOS network protocol amendments. 

Stanley 4 -

I might look into that if it’s not too complex. Presumably that’s like a streaming service? Someone did mention one of those to me a while ago when I had some problems. It looked like a time consuming process to migrate all the music. Maybe you mean something different?

Thanks again both.

John

The link to setting up Plex looks pretty simple, a lot of the discussion of transcoding and needing a powerful CPU doesn't really apply to using it for Sonos.

If you submit a diagnostic and call Sonos they can tell you your internal memory status, users can't see that.

Reserving addresses is pretty simple just go to the DHCP Settings page on your router and it should have instructions. Once done power down all So os, reboot the router and power the Sonos back up to lock in the new addresses. 

A “network client” is anything that uses the local network. By “regular client” I mean devices in your home that use the network. This would be SONOS, TV’s, computers, phones, light switches, curtains, etc. There is little benefit reserving addresses for guests who occasionally use your network. Some routers “reserve” addresses while others “fix” addresses. It’s the same result. Using different names just keeps users confused and the technical consultants employed.

Similar to stopping at the reception desk when entering a building, network clients are given an “IP address” as they sign-in. This number is their identity on the local network. This address is “leased” for a period, usually 24 hours. As its lease expires, the client must return to the desk and “renew” the lease. In many routers, keeping track of leases is very informal and after a power failure or reboot of a device(s), the IP address assignments may change. You can think of your own situation of going into the restroom and on exit, your name has been changed — without notice. SONOS units constantly chat with each other and the controllers. If IP addresses change on the fly, the result is chaos. “Reservations” assure that a given client will always be assigned the same address. It’s a one time messy project to reserve addresses.

Very interesting to read that Buzz. I never realised routers did all that. I might contact Sonos and someone might be able to explain exactly what the problem relates to and maybe offer a range of potential solutions.  After completely ignoring the system today I finally got around to the usual routine of re-booting everything again about hour and half ago. The system was found within a moment and I’ve been playing it ever since - using airplay direct from my iTunes library to my Beam which then feeds all the other S1 speakers.  I bet overnight the problem will have recurred when I try it in the morning.

Stanley 4 - Thanks for the advice but my router just sits behind the TV and all I know about it is how to switch it on and off. There is a tab at the back which has the password and mentions entering an IP address on the internet to access advanced settings but I’m certain to mess everything up even more if I try without close supervision !!

Cheers both, John

Avoid Factory Reset without further consult. It’s a lot of extra work that will almost never resolve fundamental issues.

Brief update - It’s now about 10:00 hrs and my S1 app immediately found my system when I tried connecting at about 06:30 hrs and it’s still playing now. 

It may help to look at your tags to make sure there are no unnecessary tag categories.  The only tags that are necessary are the ones that control point apps use.  The Sonos app is a control point app.  If you open Music Library on the Sonos app you can see what tag categories should be used.  Any other tags should be removed.  Some control point apps vary a little when you look at those library categories.  So the only tags I use are Artist - Title ( track name ) - Album - Track Number - Genre - Date - Album Artist.  You may want to also use Composer.  Any other tags are not needed because no control point apps use those tags.  You don’t have to do tagging this way, but when tagging classical my Artist & Album Artist are both the last name of the composer.

 I’m using DbPoweramp for tagging.

A further brief update: 14th March 11:00 GMT.

My system ran perfectly throughout yesterday playing radio initially and then moving onto music from my library.  So far today it is has again also been working perfectly since about 06:30. I haven’t changed any settings or anything  else at all at my end. I even added a few more CDs yesterday and successfully updated my libraries. So ‘go figure’, I have no idea what might have caused the problem but I really appreciate your responses. I may be back, but hope not to  !!!

John