Strange as the new Sonos App is working absolutely fine at our Home & Holiday Home and not seen a crash.. it works with our mobile router too when we go travelling in the camper van. Some screen capture examples are attached.

Maybe you have some networking issues. Have you spoken to Sonos Support? If not here’s the link to contact them…

https://support.sonos.com/s/contact

Meanwhile here’s some info. and suggestions you might want to consider…

Checkout this document on WiFi interference…

https://support.sonos.com/en-gb/article/reduce-wireless-interference

Don’t use wired SonosNet connection (except as a last resort), use your Router/Mesh WiFi signal instead, it’s usually much quicker.

Set the routers 2.4Ghz WiFi Band to use a non-overlapping ‘fixed’ channel (1, 6, or 11) with a channel-width of 20Mhz only.

The routers 5Ghz band is usually fine so leave that as it is, but for stability fix its channels (rather than have them auto-select on startup).  Try to steer compatible Sonos players onto the 5Ghz band and ensure they have an SNR level of 45dB, or above, where practicable, see this link…

https://support.sonos.com/en-us/article/understanding-the-network-details-section-in-the-sonos-app

If such connections are not achievable, then consider trying the more penetrating/longer reaching 2.4Ghz band instead, or wiring a ‘standalone’ product, but always disable its WiFi adapter when not using SonosNet, but do not disable the WiFi adapter on a standalone Home Theatre device if you plan to later use it with surrounds/Sub . In fact I don’t  recommend wiring a HT product at all, as it will create a SonosNet ‘root bridge’ in some instances, unless you are using SonosNet, as the last resort. 

It’s true to say that some routers/mesh setups may work better with Sonos in SonosNet mode - Google WiFi is an example where SonosNet sometimes works better than wireless mode.

If using SonosNet, wire a device to the router, or to a "switch" linked directly off the router only. Keep any wired/or wireless devices one metre away (minimum) from any router, WiFi AP or other wireless device where practicable. 

Never wire anything ‘Sonos’ to a WiFi mesh satellite Hub

Do not use wireless range extenders, or power-line (EoP) adapters.

Set all Sonos IP addresses static, high up in the LAN subnet out the way, in the routers DHCP reservation table - all routers are different, so maybe read the user manual if you do not know already how to make a device network address static.

Now onto the Sonos controller device…

Disable  MAC spoofing (Private Address) it can cause issues with some routers. It’s often unnecessary to use that feature on a Home WiFi network.

Disable WiFi calling

Disable Mobile Data Access use for the Sonos App

Enable the following 5 things for the Sonos App to run smoothly…

• LAN Access
• Bluetooth
• Location (precise)
• Microphone
• Notifications

Ensure the mobile controller is not using…

• VPN Client
• Firewall
• Anti-virus 
• Other security software

Ensure LAN firewalls, or products like Pi-Hole, are not blocking Sonos cloud access

Some routers may have multicasting over the LAN set as ‘disabled’ - check the router configuration pages and enable it where necessary -  (it may say IGMP Snooping or IGM Proxy etc.)

Whilst in the router settings, disable QoS and/or any Airtime Fairness features.

Remember too that the Sonos App now only sees local library folders that are shared using SMBv2 or higher - (SMBv1/HTTP shares are no longer supported since the May 7th update)

Hope those things assist.

Send the $3000 speakers that don’t work back for a refund. Buy something else or Wait a few more months to see if they actually fix it once and for all. 

You say you are moving between homes. I’ve seen that it is difficult to have more than one system using the same account (more “households”) since the new app.

Yes indeed, I use the same Sonos Household extended to all the various locations where I have Sonos speakers and it works flawlessly switching between them all.

I store multiple WiFi SSID/Credentials in the system ‘network settings’ making any/every product useable at any location with Amazon Alexa  etc. and there’s no faffing around with unlinking/linking the Sonos Skill. 

Moving seekers and having multiple installations always worked. Now it doesn’t. In fact, nothing else works either.

Sonos sucks and need to be bought by Hasbro or some other low-tech consumer company that at least understands the “consumer” part of the business.

Sonos is s***. Get Bose, JBL, anything but Sonos.

Moderator Note: Modified in accordance with the Community Code of Conduct.

I have to agree.  I get that I have gen 2 equipment, but the constant reset and “something went wrong”.  You shouldn’t have to be a network engineer to run these things.  Sounds great, when it finally works.  It’s a nightmare to get everything to sync and run properly.  

Joining the sub to the Playbar has been nothing short of stupid.  I shouldn’t have to reset and test, and reset and test and reset and test to inevitably having to just listen to music without my $800 sub.   

It sounds like you’ve already done more resets than I’ve done in five years and that was only to hand old speakers onto family members or friends.

Maybe your router is one of those rare products that are unsupportive of proxying IP addresses to ‘bonded’ devices, in which case you might be able to resolve it by wiring a SonosNet compatible product to your router (not a surround, or Sub). Another thought is the WiFi adapter on a wired playbar has been disabled and is preventing the bonding of the Sub which is usually fixed by re-enabling the Playbar WiFi, even if it’s left cabled to the LAN.

It’s absolutely shocking that there are ppl on here defending Sonos. 
 

I work in IT and can say with 100% certainty that nothing on my network is causing the issues. 
 

I own 

Sub

Playbar x 2 (different rooms)

2 x 1s

2 x 3s

2 x connect

1 x amp

This system worked fine for years and now barely works due to the update in May.

Often can’t control volume levels properly

Cant control levels in multiple zones

Last week I stopped all music and had to unplug speakers to make it actually stop.

i just spent 30 minutes trying to get holiday music to play and gave up. Instead im using a little Bluetooth speaker.

if you are one of a few that doesn’t have issues that’s great, but understand there is a major problem affecting thousands of users and customer service feeds BS canned responses.

I’ve never been made to hate a company so much.  I can’t get my money back and can’t use what I pay for  I have thousands invested and it no longer works  

All you have to do Google or go look at their Instagram. Nonstop complaints. Anyone defending them either works for them or is a paid shill.

One thing is certain, as long as you are sure:

I work in IT and can say with 100% certainty that nothing on my network is causing the issues. 

There is nothing we users here in the Community forums can do for you.

On the other hand if you, like me get to the point of frustration that you are willing to try some fixes the folks here are likely going to be able to help get your Sonos working properly.

No need to even admit there is a problem with your network, just that Sonos has issues with your network. Put the blame completely on Sonos if you wish, but be open to finding a solution.

I have spent countless hours resetting speakers and network devices to resolve the issue. I’ve tried the “solutions”. 
 

 Save your BS response for people who are technically challenged. I’ve been in IT support in all areas related to network and infrastructure for over 20 years. 
 

Open your eyes. The app is broken. Plain and simple. 

The App is broken but the App is just a controller, it has nothing to do with playing music other than finding your speakers telling them what to play.

So 20 years? Wow, ever run a 10Base5 network?

When in diagnostic mode once you have decided that the issue must be […] or cannot be e…], you are likely to be blindsided. It’s always wise to play the percentages. While the controllers are not perfect, for the major problems described here, network support is the most likely fundamental cause.

While we don’t have access to the diagnostic logs here, we can offer some suggestions if we knew more about your network components. The default network settings don’t always support SONOS well.

Just resetting speakers does not change anything, so it’s hardly surprising the problem recurs. It’s only when something is changed that different results can be experienced. As a 20-year network/infrastructure IT support engineer, is your solution to all users’ problems: “just reboot it”?