So I installed the new update and it generally went fine but as with the last two or three updates I have had a strange ending to the process.  I have two  Play 3s in one room, 2 300s in another and two TVs with sound bars. (A Playbar and an Arc).  I have always used my Macbook Pro to do the updates and then updated my iOS systems afterward.  The update works as expected, sound goes, off speaker lights flash red as do the sound bars while the updating goes on. When the update goes into the finish up stage the sound returns and all speaker lights stop flashing and return to green normal operation lights.  The update stays in the finish up stage for several minutes before it finally announces that there was a problem with the update and to try the update again.  I click the try update again button and the update comes back almost immediately saying that my system is up to date and no updates are needed.  The screen drops back to the Sonos app which announces that my system firewall settings have changed and that they need to be updated before the app can find my system.  If I just close the app and reopen it my system is found and all is well without any changes to system settings.  If I select to try to follow the instructions in the app (before closing and relaunching)  for making firewall changes the information appears to be out of date for Sequoia 15.5. 

Seems that there might be a few issues with upgrade process that could be modified or if I am missing something that I should be doing that would make the finish process work correctly I am all for hearing that.   Minor concerns here really as the update does get applied and everything works eventually.

Thanks for your time and attention!

​@JayBob , that does seem to be odd behavior. Have you submitted a system diagnostic within 10 minutes of experiencing this problem, and called Sonos Support to discuss it?  Don’t post the resulting diagnostic number here, they get sensitive about GDPR.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

Thanks.  I will report it the next time I upgrade.  I started here to see if there where any other users with this experience and if there was something known that I was/am doing that might cause what I am seeing. 

Thanks for replying and I will follow up with Support next upgrade.  

The desktop app has not been a focus for Sonos for a while now. 

When a user has numerous Sonos devices, the update process can result in seeing an update error message as the process can timeout before all the devices have completed the update, rebooted and reconnected to the network. Simply, just close the Sonos app and reopen which you confirm does successfully find your system again, with no further update required.

Edit: the same update error message can also appear on iOS as the process has timed out but has actually completed successfully.

It seems the new update broke Alarms?

I was just out of town for 8 days. I returned home, connected to my Sonos system, and all my alarms were gone.

When I create a new alarm, and exit the alarms screen, that alarm is gone when I re-enter the alarm screen. 
 

I updated my phone’s OS yesterday afternoon , and all my old alarms came back… but now they’re gone again. 

Try rebooting your router.

A new Sonos app update has been released today (80.23.9 for both iOS and Android, which is unusual). The notes on the App Store, Play Store, and Sonos website just say “bug fixes and improved performance”. Helpful.

I think the issue with having to scroll down a long playlist queue to find the current playing song might be fixed — but it could just be 1) I'm approaching the queue differently for some reason, or 2) it was already fixed earlier and I’ve just forgotten! Could someone say one way or the other..??

Thanks for the update.

 The Trello (sp) board mentioned faster app loading time. Have you noticed any improvement? I’m out of town so I can’t test performance.

Hard to say. I just tested it from closed, and my loading time is instantaneous (a fraction of a second for all thumbnails to load across Services, Recently Played, Sonos Favourites, and for the now playing section to populate). But it was fast previously so I can’t really tell if that is an improvement or not...

Maybe someone for whom it was slow to open before could confirm or deny any improvement, once they have installed the update.

(By the way, no accompanying system update this time, it appears.)

Previously the App would load instantly for me, unless from a force close, where it would take 1 second to load. Its now instantly opening from background or force close, and quicker than Apple Music App takes to load. I don’t have Local Music Library, currently 18 Sonos favourites from 7 active Sonos Music Services. 

Since the latest update the slow loading time of the app is much worse for us (3 x various Android devices).  We do have A to Z scrolling though so I suppose….."what the right hand gives, the left hand takes".

​@Gegg 

If the update is slower for all your devices, then that points to an issue with your network, not the app, otherwise everyone with an Android device would be complaining about it on here. At least one of your devices would be working at normal speed if your network was fine.

Just reporting back.

I finally got a chance to download the new App version 80.23.9. It is a definite improvement regarding load time when background activity has been stopped on iOS 18.5. It goes without saying that the load time is fast when just waking up the App.

Something I observed is that downloading the new version required a few more seconds than previous versions. That suggests to me that the package is bigger given improvements (whatever they are outside of load speed).

I’ve had nothing but instability since auto-update completed yesterday. Speakers come and go; some not recognized at all; data in app loads incredibly slowly and results vary a lot. Typically - after about 4 mins load time - the app shows only 3 of 7 zones. I’ve done factory reset on missing zones, multiple router & Sonos controller reboots. Super frustrating. Does any one know how to address this? Or has Sonos posted anything re bug fix ETA?

I suspect you’re experiencing a duplicate IP address issue, which will rarely be remedied by either factory resets (not recommended unless suggested by a Sonos rep) or a controller reboot, as the issue is with your router, and not really the Sonos system per se. 

What I’d try is a network refresh. Unplug all your Sonos devices from power, then reboot your router. Wait a couple of minutes for the router to come back up, then plug back in (or turn on, in the case of portables) your Sonos devices. Wait another two minutes for them to load and connect, then test.

If that doesn’t change things, I would recommend that you submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it. Don’t post the resulting diagnostic number here, they get sensitive about GDPR.

There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution.

When you speak directly to the Support staff, they have tools at their disposal that will allow them to give you advice specific to your network and Sonos system.

Thank you for the suggestion. I should have mentioned that I did a network refresh, but the issues persisted after that. When I can carve out more time in my life for Sonos I'll reach out to their support and hope for the best.

I noticed the recently played functionality works well on Android now. Hopefully that will be coming for Apple devices soon. Might leave my old phone in the spare room as a controller. 

The apps do feel snappier now as well.

Snappy iPhone here.

Will we be seeing the ability to save the current queue as a playlist return soon? 

A much missed feature.  

One of the forum mods confirmed this week that this has now been put forward as a feature request. I’d imagine it was a feature request previously but this is at least now a recent confirmation. (Someone voiced that it shouldn’t need to be a feature request as it was there before, and remains available on the desktop app(s), but I can’t speak to that as I didn’t/don’t use queue saving.)

+1 that this deleted feature isn’t on their roadmap after 15 months is ridiculous.