So, I got sorted! but resolution did however involve the nuclear option.
I tried lots of things, including changing the DNS on my router, using ethernet etc to no avail.
I spent an hour with Sonos support and did get great assistance from Sonos them once i got through. I am technical and was impressed by the agents knowledge and her ability to think outside the box.
I went off to try a few more things and when I went to call back support there was an 80 minute queue - one thing that needs improvement by Sonos if you are listening is the wait time because my experience with the support person was excellent. Also the support chatbot is useless!
Here are the steps I took:
- I have a few Sonos so I powered them all off.
- Rebooted my router.
- I did a full reset on the first speaker (a One in this case)
- Went through the setup of One as brand new. (strange thing I discovered is that your services etc are all bound and stored in the Sonos device and not held up in Sonos or cloud someplace. I assume they then replicated that config device to device once joined)
- Setup completed and I could then add in all my services!
- I then reset the other powered off Sonos.
- Joined to the new system\group I created above.
- All the services carried over that I setup above
- Job done!
Obviously this would be a more painful solution if you have large numbers of devices but I thankfully only had a few. I found it better to rip the plaster off than way hoping an App update would fix things - in my case I don't think an App update would ever have resolved my particular issue..
The new App is now working great for me. I am sure there are a few niggles which Sonos will iron out in coming weeks but its working well for me!
One thing of interest I found out is that there is a web interface for each Sonos device which can be accessed to review config and check Sonos can ping update.sonos.com etc, If you google it you will find details..
