Odd, I updated a couple of hours ago from the iOS store, and have had no issues at all. 

If you’re unwilling to call Sonos Support directly to discuss it, I’d suggest a couple of things. Not sure if it is the controller app, or last week’s firmware update, but I’d try a couple of things. 

First, I’d delete the controller completely from my iOS device. Then I would hard reboot the iOS device, just to clear any lingering memory issues. I’d double check for any Apple updates to iOS and apply them. Finally, I’d try a fresh download of the app from the iOS ‘store’, and re install the app. If presented with the option, always select ‘Connect to existing system’. 

If it’s firmware on the speakers you’re experiencing trouble with, I’d just walk away for half an hour, then check again. I’ve noticed with some updates that the ‘process’ in the controller can ‘finish’ before the actual process completes on my speakers, and if I just wait, the process finishes, and when I ‘check for updates’, it finally tells me that no updates are necessary. 

Before seeing your reply, I chose the “walk away option.”   After 40 mins I stopped the update, turn off my phone and back again.  Everything was fine. Not sure of why, but it seems everything is working as it should. 

It seems to work, when I run into that issue, which is extremely occasional. For instance, neither the .34 or .35 updates did I have that issue, but the it has happened once over say the last six months.

My suspicion is that the process on the (iOS) controller is timing out, and presenting as ‘done’ with an error, when in fact there’s at least one device that hasn’t finished the update process, and is still ‘going’. If I just wait, and then check later, I get the kill products are up to date’ message, whereas at the ‘end’ of the first time through, I get the ‘this/these devices have failed to update’ message. I can only assume this is a time out in the code, where the controller is thinking it must present something, otherwise the user will think it’s taking to long, but in fact, the errant devices are still updating, and once they’re ‘done’, rebooted, and reporting back to the controller properly with the correct ‘update code’. It’s mildly disconcerting at first, but it’s probably happened three times to me over the last year or two. I attribute it to either poor download speeds (I have an atrocious internet connection), or slow CPUs (as it seems to most often be on my older, slower PLAY:1s). Could just as well be the slowish LAN connection, or duplicate IPs causing data interruptions to my speakers, too. Used to freak me out, now I’m much more laissez-faire about it. 

Bruce:

yes thanks, just grateful that it works! I don’t want to return to Sonos update, days! So glad I stayed.

thx again and regards.