Interested in class action against sonos?

I do have to agree that, even if it is (as we all suspect) individual network issues/conflicts, that is really no excuse. For once I am with @Starmont - no-one should need to have any knowledge of anything technical further than installing and using the app.  The app should be downloaded, connected to the user’s wifi, the speakers set up and off we go…

On another thread, I have been asking for people’s set-up to try to deduce a common denominator that might be a temporary fix for some people while Sonos sorts things out. But it’s not likely to lead anywhere as there are limitless number of network setups in households and businesses - all of which should be served by a simple, seamless, functioning app. 

It will all go back to normal but it must be frustrating in the meantime for those who can’t play music. Yes, it’s a local network issue rather than an app issue (as there are many, like myself, who luckily don’t experience these issues), but the app should be universally compatible with all of them without tinkering - just like every other app...

Says you.  Thankfully Sonos don't agree or they wouldn't be fixing (or even be able to fix) them all.

I remember you having issues with prior versions of new app. What did you change on your network to make it work so good for you?

Using the new app this morning Sirius XM wouldn’t play “Something Went Wrong”. Switched to SonoPhone and it worked first try. Totally anecdotal but you’ve seen all the posts like this here. (beyond anecdotal SonoPhone was #1 app in music on iOS App Store the other day 🤣) 

How can the previous App and the likes of Sonophone work so well with such network issues?

please sue them…. i have purchased thousands of dollars of equipment… they have systematically reduced it to nothing!!! the most horrible company ever… way to go guys…. you are a model for screwing up a good thing

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

:)

I’m fairly sure I have not had any issues with the app since it was updated - other than one of my Symfonisk speakers falling off the network (which came back after a reboot, some patience, and some luck!). Early on I was lamenting on here the lack of per-song options (e.g. editing queue, or adding to end of queue, Play Next, etc), and needed help to know the tap up and down for volume, but generally not made any adjustments as it has worked for me so far.

I do still sometimes have issues in Lossless not showing when the playlist is a mix of Atmos and Lossless, and also crossfading doesn’t work on Lossless or Atmos tracks (which was a problem prior to the app update).

But since the update, the system has never failed to load, or find the system. Unless I have forgotten an issue, which is possible!

That is a very simplistic response, 2 of those issues can be attributed to things outside of an owners network and control along with poor app design.

• "Owner must be logged in" loop bug

Sonos either run or pay a 3rd party to provide oauth servers and services used for login. The app makes a call out to an external oauth endpoint under the Sonos domain. As long as the user isn’t blocking the endpoint using a Pihole or similar, then they have no control over what happens with their ISP, the various internet exchanges and routes used by backbone internet providers, Sonos cloud hosting providers or servers.

Occasionally the old app would show me a notification that my Sonos account wasn’t logged in. It would then clear up when after background retries it received a successful response from the Sonos servers. That login failure had zero to do with my local network.

A significant change in the app appears to be the new app refuses to let a user do anything if it can’t login or the oauth token expires before it can be refreshed. The old app did not require the Sonos account to be logged or still have a valid oauth token to perform any playback actions.

That change in behaviour is entirely on Sonos and entirely on them to ensure their app behaves appropriately when either their infrastructure or an external to the user internet issue occurs. Looping suggest a bug with the app using the failed cached response and not even bothering to retry the call properly. The bigger question is why does the new app now prevent any use if the login fails when the previous app didn’t?

• "Unable to register your Sonos product" bug

The again involves making a call over https, to the backend Sonos services. Unless the user has blocked Sonos endpoints, the cause is unlikely to be within the local network or control of an end user. This is entirely the responsibility of Sonos to ensure they have a robust application and method of handling what happens to requests to their servers. Whether that is suitable retries dues to shifting network routes on backbone providers or within their own service hosting, there is little to nothing a user can do to fix this other than constantly retrying at different time intervals.

While some things with Sonos can be affected by local equipment interfering with the multicast and local network, it is still the responsibility of Sonos, who are targeting a primarily non-technical market with ‘plug and play’ products, to ensure it’s products are robust enough for the market they target.

Of course they can’t test every combination of switch, router, WiFi access point, but not every ‘network’ issue is due to the users equipment. If it worked in a previous app, then there is no reason for it to be broken in a newer app.
 

These are digital systems shifting data around using mostly typical protocol standards that have existed for years, your mechanical analogy makes little sense because my switch, router, WiFi AP, Ethernet cable and existing Sonos devices don’t wear out and suddenly start breaking because a new app is released.

Yep…Says me and anyone who can look at the premise being put forth to justify the class action. But…go ahead and continue to promote this class action nonsense. BTW… have you and your other antagonists thrown your hats into the ring 🤔.  Action speaks louder than words and put an end to your boisterous posturing! Just Do it!!! 😂😂😂

I have no time or interest in any kind of class action, I was merely posting how silly your claims are that they aren't even bugs and that they can ALL be traced back to local issues.

The previous post makes some great points about just how many other things are at play in the update.  I made a similar point a month or so back that ISPs and routing all have a big part to play now so to still be insisting that if one user's setup is OK with a specific ISP or speed (speed should be all but irrelevant for the comms that are happening) then all other issues must be local is more and more futile by the day.

Whatever!