Try turning off your speakers, and then log out of the Sonos App.
Turn on the speakers one at a time until the white light shows, then move onto the next one.
Log back into the Sonos App and try the Amazon Music search/play again.
Hi Rhonny,
thanks for your quick reply. I tried it and kept the speakers off for some minutes before powering them up slowly one after another.
Unfortunately the error pattern persists - I get a mix of “Leider ist ein Fehler aufgetreten!” (Unfortunately an error occured) and a constantly spinning circle on the playback button in the app.
I tried Android and iOS but got the same results on both OSes.
That’s disappointing. The only other thing would be to reboot your router too, let is boot up fully, and see if that makes a difference. (Force close the app first.)
Other than that, I’m afraid I can only suggest you contact Sonos support, unless someone else on here has any suggestions?
I’ve had to power down my Sonos, reboot the router and power my Sonos back up in the past.
With the new app the “Force Close” has been needed a few times, being lazy and having no clue how to do that I rebooted the controller’s device which accomplished the same thing.
“Force Close” has been needed a few times, being lazy and having no clue how to do that
On iPhone, slowly drag up from the very bottom of the screen until you see all your recent apps lined up. Let go, then just swipe up on the Sonos app to swipe it away. That force closes it.
@c4t0r
Are you having ussue still? There seems to be a few of us with the same issue the last few days in another thread
Hi @all,
I gave it another try yesterday and removed any possible obstacle and it finally worked!
Today it stopped suddenly again.
After resetting one speaker I realized blocked DNS queries towards “sonos.amazonmusic.com” in my PiHole DNS Server.
As it turns out this domain seemingly was an origin for malware once and has become serious in the meantime. Unfortunately it is not only under Amazon’s control now but seems to be necessary for Sonos Playback…
So, whoever is currently using PiHole with several public gravity lists and encountering similar problems should check for blocked queries and whitelist some domains.
Thanks @all for you suggestions that finally led me to my self-made problem.
