Skip to main content
Contributor III
Nov 4, 2017 1:31 AM UTC
Question

Shuffle with loop mode Alexa failure

I am unable to get my Sonos One to both shuffle and loop an Amazon Music playlist using Alexa. The following steps are taken:
1. "Alexa... Shuffle Arnold music" (Arnold is my dog)
2. Sonos One starts shuffled version of the playlist, stating it is playing on the Sonos.
3. "Alexa... Loop Mode"
4. Sonos One acknowledges Loop Mode is turned on.

After that, the playlist does not loop.

Is this a bug?
This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

21 replies

vlestatAuthor
Contributor III
Nov 7, 2017 10:16 PM UTC
So just to be clear, I should disable the Sonos skill inside of the Alexa app, then remove voice services from the Sonos app, then add the Sonos skill to the Alexa app and enable voice services from the Sonos app?

To answer your second question, I don't have a playlist like this on Spotify, just Amazon music.
Translate
Ryan S
Retired Sonos Staff
Nov 7, 2017 11:00 PM UTC
Those steps are correct.

(You could switch the order of which one is turned off first if you wanted, it doesn't matter for this).
Translate
Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.
vlestatAuthor
Contributor III
Nov 10, 2017 6:47 PM UTC
Hey, I tried that and it is still ceasing playback at some point in the playlist. In the 2 diagnostics that I performed after failures, is the last song played the failure? I'm wondering if the playlist has a "dead" song that it tries to play. I usually shuffle the playlist so I'll try playing it straight through with loop to see if it gets stuck on anything. I'm also going to run it on my original Echo and see if it can stay looping or not.
Translate
Ryan S
Retired Sonos Staff
Nov 10, 2017 7:20 PM UTC
It's not listing a specific track each time. The error coming up is a connection to server error, which means it's losing access to the stream in general. As a test, would you be able to try wiring your Sonos One into the network with an ethernet cable? This way we can remove any wireless environment variables as a potential issue.
Translate
Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.
vlestatAuthor
Contributor III
Nov 11, 2017 1:30 AM UTC
Ok, I tried with Ethernet and had the same results. No playback after some period of time. What strange was that when I launched the Sonos app to submit diagnostics, it started playback again.

Diag 8069510
Translate
Ryan S
Retired Sonos Staff
Nov 13, 2017 6:38 PM UTC
Thanks for the diagnostic, I have the team looking into them right now and I'll let you know if they have any recommendations.

I wanted to check how that test with the original Echo you had go. Was loop working on that device or did it do the same thing?
Translate
Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.
vlestatAuthor
Contributor III
Nov 13, 2017 6:40 PM UTC
Yes, loop seems to work fine with the original echo. I will run one more test with original echo this afternoon to verify.
Translate
vlestatAuthor
Contributor III
Nov 14, 2017 2:11 AM UTC
Ok, I didn't end up running it on my original echo because when I came home at lunch to start it, the Sonos was still playing. When I got home the Sonos had stopped working. 8079811 is the most recent diagnostic run and I will report back on the echo wireless performance
Translate
vlestatAuthor
Contributor III
Nov 15, 2017 6:41 PM UTC
Hi Ryan,

So I was able to verify that the original Echo was able to play continuously for 24 hours wirelessly. So it seems to be a problem on the Sonos side maintaining a wifi connection (or the ability to reconnect/resume playback after a wifi drop). Any other testing you want me to do?
Translate
vlestatAuthor
Contributor III
Nov 29, 2017 6:35 PM UTC
This issue has resolved itself. It now plays on and on. Thanks Ryan.
Translate