Do you just use streaming services through the Port or do you have another device (like a turntable) connected to the line-in on the Port?

Do you have the option to wire the Port directly to your router?

Your Port may be suffering from an IP related issue, easily fixed either temporarily or permanently.

The quick fix is to power down all Sonos, reboot the router, power the Sonos back up. If it is IP address related that usually clears the issue.

If it clears it but then it recurs you can set static/reserved IP addresses for all Sonos (not just the Port) using your router’s DHCP settings page. It is usually fairly quick and simple to do and the router’s help screen should see you through the process. Once done again, power down all Sonos, reboot the router, power the Sonos back up.

Port does not have a turntable attached.  It is connected directly to the amplifier which is connected to our Elan whole home distribution system.

Stream music from Apple and Amazon via fiber optic broadband.  Port is connected to our router mesh using WiFi 2.4 GHz.

Everything worked fine until Sonos launched their new iOS app.  Been nothing but problems since then.

Not spending any additional $$ until Sonos gets their act together 

All other video and online gaming has been great so it’s not a router / IP issue

Thanks for your replies

As the Port supports 5GHz, you’ll get less interference and better stability than on 2.4GHz. Might help telling your mesh system to get the Port to use 5GHz.

I have a Sonos Port and use it most days and it has been fine with the new Sonos update. If you go into the Port ‘room’ settings and select the device, it will show its network connection details and the strength of the WiFi connection - SNR level. (See attached example).
 

I would ensure that the SNR level is at least 45dB or higher, which is a strong connection. I also agree with others here that putting the Port onto the faster 5Ghz WiFi band might help and to perhaps fix its IP address too… which are two things I have done with the Sonos Port and I’ve not seen any issues with it.

Is the port the only Sonos device you have? When you say it feeds the whole house distribution, do you mean just from an audio output perspective? 

The SNR of my Port is 65 dB using 2.4 GHz WiFi

We also have a Sonos Arc, a Move and two pairs of Sonos One speakers, both configured a stereo pairs.  I haven’t had issues with these products, only the Port

I cannot relocate the Port as I stated previously it is cable connected to my amplifier which is connected directly to the Elan system (built-in / fixed location) which provides audio output/signal distributed to various rooms and our outdoor patio which use non-Sonos audio speaker pairs

Thanks for your replies

OK, so you have a few Sonos devices, are any of them plugged in via ethernet and are you able to get an ethernet cable to the Port? 

Before looking to cable anything here and perhaps going over to SonosNet (not that a Move can use that connection), I would first consider trying a different non-overlapping WiFi channel using channels 1, 6 or 11. Also if your router allows, set a channel-width of 20MHz only for the 2.4Ghz WiFi band and see if that makes a difference.

Ian_S - All utilize WiFi - Elan/Amp/Port are all co-located together - house was not wired for CAT5/6

Ken_Griffiths - Thanks for the suggestions, but everything worked fine until Sonos released their revamped app/software.  The new product was not ready for prime time and certainly didn’t undergo much QC testing.  If they can’t get their act together then I’ll look elsewhere to resolve the issue since I’m not going to run downstairs to reboot the Port every time is stops working

Thanks for all of your feedback and suggestions

That’s clearly your prerogative @Olengr - I can only add that the Port here (used almost daily) has been fine with the new Sonos App and in terms of that Sonod product, I’ve not seen (m)any complaints about it, even in recent times.

Once the chosen Sonos audio source has started playing from the new Sonos App, the App can be fully closed and the mobile device switched off, as it’s merely a ‘remote’ and not an ‘audio player’ so I don’t think the App is at the heart of your issue here. My earlier suggestion, still stands, but it’s entirely upto you, if you do still think it’s related to the new App.

Despite some people’s protestations that the app is merely just a controller and therefore it must be your network, the new app potentially uses new API’s in the speakers that were not in use before and may be less reliable. 

So one ‘cheap’ option is to try a 3rd party controller such as Sonophone. It’s not free, but in the context of finding something else, could be the cheapest route to working until Sonos manage to fix their new ecosystem. These 3rd party controllers use older interfaces so could be more reliable if the system was working well before the new app fell out the wrong hole … 

OK, for 2.4 GHz WiFi band I set my router to channel 11 and channel width to 20 MHz (was previously on Auto).  In addition Sonos posted and update for their app.  I had to cycle the Port power this morning and currently it’s working.  For how long we’ll see.

Thanks for the advice

The Port stayed connected for about 5 hours before it went south.  Maybe there was a firmware update that caused it.  I did check to see if there were any firmware updates available but no joy.

Hopefully Sonos gets it sorted out

And the fix for everything is unplug router which is going really old!! It isn’t my internet 

Seems a strange first post - your community profile doesn’t even state that you have a Sonos Port, which is the subject of this thread?

Resetting the router is an ‘easy’ fix for duplicate IP addresses, assuming the Sonos devices are unplugged first. Usually easier than setting up reserved IP addresses in the router’s UI, but less permanent, too. If a router has gotten in to a situation where it was giving out ‘bad’ IPs, it’s liable to get in that state again. 

Sonos, as a client device, doesn’t have the ability in the networking world, to set its own IPs.