Sonos made several huge errors with the app changes, there is not much they can do but try to keep their heads above water while they struggle to recover from that massive foul up.

The decision was made that they would not let folks stay or return to the original app, apparently Sonos had not yet realized/admitted to themselves the disaster they had created. That really hurt them, and us.

They are making progress but from here it looks like they are still suffering from the development team blowing smoke about features and timelines for fixes. Sounds like the team inflated both their skills with the develop ent tools and their ability to understand/recreate the app's functions on the new platform.

I don't see a good, fast, path forward, once you are this deep in a hole there is little you can do to recover quickly. It does appear that Sonos has at least stopped digging and is making some progress. Eventually (we all hope) the development team will get up to speed and quit flailing about fixing one bug while creating several others. We don't know all the internal problems but it is obvious they are many and severe.

I'm hanging on and hoping nothing major goes wrong and progress will continue and maybe even speed up.

Thanks for the answer. Seems like big problems… I neerly doesn’t use the system anymore because eventime I use it I experience even more bugs. 
 

hmmm patience required - but how long…

How long is the question that is so hard for outsiders, or even insiders that haven't come to grips with the core issues with the developers to answer.

Seen similar issues like this from the inside, I was on the clueless / incompetent development team. Our bosses kept making impossible promises to the project owner while beating their staff (including me!) to make progress on a system we didn't understand, using tools we weren't competent to use. I needed the job, my bills loved the overtime and I got paid to soak up some very expensive training. Much of it wasn't applicable to our actual situation, like the four object oriented college classes that focused on buzzwords  and charting, we did write about 100 lines of c in the labs though. In the mid-term the competent (but not in this area) programmers left. Long term all but the complete deadwood left, including me. The project owner fired the development company and hired, at great expense and with no promises on actually fixing things, a different company.

What stage Sonos is at and how fast they will progress is something I can't answer,  but I still have hope.

Sorry you are having so many issues. The app is working for me although l’ll admit my Sonos gear consists of nothing older than a Port or Sonos Amp.

It would be a lot easier to offer help if you could start with one issue and allow us to gather information about it rather than throwing several at once.

Hi again and tanks’s for all answers. My frustration let me to post this thread as the 2 errors mentioned have been present since I was pursvaded into upgrading to S2 app by support. 
 

I know now that it propably wont better from here on - I just feel left a little with hardware equipment that is far to expensive to be left not working just because of software problems. 
 

and I have some experience with software development processes - so not reallly surprised but disappointed. 
 

what happend to the old julebox approach?

What is ‘the julebox approach’?

Jukebox. 

Still no clue what that means, sorry.

If you have the time you can view the YouTube explanation regarding the jukebox approach. Although I still fail to make a constructive link to what the OP is trying to convey.

There are other explanations on the internet as well. However still a bit of a conundrum to me.

I liked to use recently played a lot, adding new albums occasionally while letting some drift out, and it's never recovered. It's somewhat better on Android but not ideal. I imagine at this point it never will, at least on iPhone. 

Wasn’t there an open source Jukebox project, that ended up failing?

I have no idea. I never heard of a Jukebox project until today. I guess I’ll have roll back my rock more often. 😂

I may have been thinking of Squeezebox. 

In re-reading the original post, most of these, maybe all, seem to be related to network issues, not endemic issues with Sonos software itself. OP, what did Sonos Support say, when you called in to discuss it?

Ok so i Will end the question by saying that I dont expect a lot from the bug fixing - my s1 worked fine on same network as the current the s2 doesnt…

my reference to jukebox was an attemt to be funny - a jukebox was simple right - one song after another- no “line jumpers” - everyone understood the rules - now the complexity breaks the experience. Sad. 
 

over and out - thnx for the answers.