Interested in class action against sonos?

You’re not lucky, you’re just a simpler case user. 

All I do is listen to music from my music library - 90% of the time. So, for me, your case is not at all “in every way that people” etc., etc. When you stream your music library to 3 or 4 sync’d Ports wired to a network 10-12 hours a day, then we can compare notes.

There are quite a few issues I have read about on here too that I have not experienced. I write it down mostly to me avoiding the new app as much as possible.  There are also many issues I read about that involve features, services, and setups, that I don’t use and products that I don’t own.  But that doesn’t make them invalid just because they don’t fit my use case.  I’m really glad I have not run into the setup problems others have - my system was already set up. I assume they are legit problems since the release notes say some have been addressed.  I doubt they are trying to fix imaginary problems, do you? 
 

As you rightly say @stevepow its not the App, at least you have accepted that and the class action mentioned here is centred on that App being the issue. It seems in your case it isn’t. I suspect you will perhaps be better off speaking with Sonos Support later and describing to them your network & system setup in detail, which I think you said had been upgraded in recent times and provide them with a diagnostic report and go forward from there.

That is exactly the view point that led to the IT Industry meme about developers claiming ‘works on my machine’ when a user reports an issue or a deployment breaks production.

I already gave you explanations for why two of the items potentially wouldn’t be a user network issues. Please explain how they are?

A month ago, which is the date of the post you quoted, even Sonos wouldn't try and claim the empty Manage Networks was a user issue, nevermind a user network issue.

They acknowledged in their first list of future development that WiFi settings were missing, with a planned date of mid-June to add it back.

It has only been in the 1st July release that Sonos added the ability to change the Sonosnet channel back to the Android app, as per their own release notes. For iOS it was added 17th June, so I’m sure Sonos would been keen to understand how a month ago you had a fully working manage networks section in your app when it didn’t exist and how it being missing would be a user network issue?

Some of the items mentioned in this list have been addressed and improved by Sonos making application updates, it is visible in their release notes. So please explain why you believe the users network is the cause of all their problems including functionality that Sonos had removed and not added back to the app at the date the issues were listed?

Whatever!

Whine, whine, whine, wah, wah, wah. I guess it’s true…misery “does” love company! 😂😂😂

So do yourselves a favor …File Your Lawsuit…however, I seriously doubt it bring the Sonos gods down from Mount Olympus! 😂😂😂😂😂😂

 PS…I’m done for today. I have a 4th of July celebration to attend. Maybe you should find another diversion outside of Sonos and this thread. Have a good day 😊!

I can only agree with @AjTrek1 .  This thread has become worse than pointless.  None of us knows for sure what the causes of the various problems are.  So I suggest we all just shut up and wait and see how things pan out.  Maybe see you back here in three months to check how things have progressed (if they have)?  That can include an update on how the class action is going.

My final suggestion for amyone experiencing problems of missing zones, dropouts etc would be:

(i) Power off your network and all Sonos devices. Then power up the network followed by Sonos

(ii) If that does not help, submit a system diagnostic when things are not working properly and call Sonos Support to work through any issues revealed.

This is just a suggestion and it certainly won’t solve all problems.  But I think it is worth trying for some sorts of issue.  If it doesn’t help anyone, then I apologise for wasting your time.

See you back here in October?

In my own use-case the only difference I’m seeing is the Sonos ‘remote’ App has changed - but my existing Sonos hardware has continued to work the same as before the early May update - that includes products either standalone, or grouped, whether they’re fixed or portable.

Hardware-wise nothing appears to have changed and I play to my products (grouped and ungrouped) in a variety of ways,.. via the App, using Airplay, line-in (four different audio sources), Bluetooth, TV audio, and/or direct control. Also I’ve not encountered any changes with Alexa, or SVC voice control.

In fact I’m personally convinced if I were ever to be given the S2 App back, that things would likely work exactly as before the App was switched.

There seems to have been far more App ‘remote’ controller updates than there have been firmware updates and my thoughts are that very little has changed in terms of the Sonos firmware and was perhaps more geared around catering for the new Roam 2 and Ace Headphones being added to an existing Sonos system.

In my own use case my hardware continues to work as well. I had some issues with my Roam and updates but they eventually worked after a sonos app update, can’t remember which one.

But the new app is buggy AF, constant “Something Went Wrong”, lagging, crashes, volume changes taking 30 seconds to apply. Music Library link disappearing, music services not loading properly.

But switching over to Sonophone or the desktop app when I have issues and it just works, perfectly every time. Airplay also works. No lag, no issues with services, no something went wrong messages. Sonophone, the desktop app and Airplay work perfect when the Sonos app bugs out.

That’s helpful @Bumper and seems to infer/agree with my own thoughts that the hardware products themselves and their own network connections haven’t altered at all - I know my family and friends and others here, have not had issues network-wise since the App was switched/updated and so if I see users saying their speakers are dropping off the LAN and the such like, or their music somewhat inexplicably stops playing, then I continue to suspect that would likely to have been the case too even without the new controller App, or recent updates.

It’s why I think some users ‘likely’ have a local (network) issue rather than anything the recent updates have caused. Albeit some updates can lead to multiple product reboots and cause IP conflicts with some DHCP servers in some cases. 

I guess the fact that the existing SonoPad/Phone controller Apps still work okay for you shows that perhaps very little (if anything) has changed on the speakers themselves.

I don’t know that very little has changed on the speakers. The new web app seems to indicate a lot may have changed  

The new app sucks and some people’s systems are incredibly unreliable 2 months later. That you and another poster have amazing systems and I can play music on 3rd party app that uses the old control commands does’t prove or disprove anything other than Sonos has screwed up massively and there’s no end in sight. As John says maybe by October.