Skip to main content
Contributor I
July 8, 2018

Why does my Sonos system turn itself on, playing a random song!?

  • July 8, 2018
  • 157 replies
  • 46483 views
kind of spooky...
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.

157 replies

Airgetlam
September 5, 2021

If you’re in a beta program, as your screenshot suggests, you should not be posting here. 

Bruce
James L.
Retired Community Staff
September 6, 2021

This just happened to me. Random song autoplayed at 6.10 am.

 

Diagnostic:

2145498528

Hi Berdle,

 

Similar to other posts here, playback originated from Spotify Connect, a session left open from earlier in the day from an iPhone (the same iPhone used to stop the music shortly after it started). Make sure to end the Spotify Connect session when you’re done listening via the Sonos app by tapping the queue button at the top right of the Now Playing screen to prevent this from happening in future.

Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.
Lyricist II
September 6, 2021

Thanks v much. 

Contributor I
September 7, 2021

Whenever my Beam or Connect ungroup from the rest of the house they cause music to resume on the rest of the speakers. I can see the suggestion is to end the Spotify connect session but surely my system shouldn’t be automatically resuming music that was stopped many hours ago? Some feedback from the tv powering on to update caused the Connect to autoplay in the middle of the night and suddenly I had music everywhere else!

Airgetlam
September 7, 2021

In your first case, your system is not automatically resuming music that was stopped many hours ago. Instead, your system is receiving a command from the still connected Spotify Connect device to resume music playback, or start a fresh song. In your second case, the TV is starting to send a signal to the Sonos soundbar, which is set to autoplay, and starts playback. 

In both cases, Sonos is acting as a receiver of data, and doing exactly what it has been ‘told/programmed’ to do.

Bruce
Contributor I
September 7, 2021

But when I turn the TV on I don’t expect my Spotify music to spontaneously play in the rest of the house. The only input to the system I am making is autoplay for line in audio, somehow the auto ungroup function is also triggering playback to resume.

 

This is what happens upon autoplay/auto ungroup

Airgetlam
September 7, 2021

So, neither case is applicable from your previous post. 

I would recommend that you submit a system diagnostic within 10 minutes of experiencing this problem, and call Sonos Support to discuss it.

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 phone folks, they have tools at their disposal that will allow them to give you advice specific to your Sonos system and network.

Bruce
Contributor I
September 7, 2021

Just tried it again with my Beam and same thing. Diagnostic is 1404966687, will try phone if no one here can give it a glance.

Xander P
Retired Sonos Staff
September 7, 2021

 Hi @ashleywntr, thanks for providing those diagnostics.

I’ve tested this on my own system and I have been able to replicate this behaviour - just to confirm, does this only occur if when the Beam is grouped, it is acting as the group coordinator? i.e. the Beam is the first room listed in the group?

It looks like when the Beam leaves the group, the stream is passed on to the next player and the stream gets unpaused - in any case I’ll pass this on to the tech leads to see if this is something they are aware of :)

 

[Edit - I have just heard back from the tech leads and we are aware of this issue - we’re currently working with Spotify to get it fixed, however I don’t have an ETA that I can share right now]

Contributor I
September 7, 2021

@Xander P thanks for taking a look, it’s great to hear it’s not just me!

It appears to be any ungrouping activity that causes it I.e. even when manually doing it in the app. Not sure if it only happens when I’m changing the group coordinator though, I’ll do some further testing.