Skip to main content

Long thread on Reddit here

 

Tl;dr

  • Affects iOS and Android, ie OS agnostic
  • Affects variety of iPhones and Android devices ie device agnostic
  • Affects multiple combinations of Sonos devices and firmware
  • Affects multiple routers
  • Steps to reproduce
    • Use Spotify connect on Spotify app

  • Actual behaviour

    • The Spotify app thinks it's successfully connected to a Sonos speaker.

    • The Spotify app thinks it's playing.

    • No sound comes from the speaker.

    • The Sonos app doesn't think anything is playing to the speaker, and doesn't show the Spotify connection (it'll either show the last thing the Sonos app thinks was playing on that speaker, or "No content").

  • Temporary workarounds include removing Spotify account from device and re-adding it, reauthenticating Spotify account from Sonos app, starting to play music via Spotify on Sonos app and then opening Spotify app. The problem always recurs, unsure exactly how quickly after. 

Can a ticket be opened for this pretty please?

 

ps For me at least it’s coincided with the launch of Spotify lossless. Might be coincidence ofc but worth investigating 

Hi ​@abhi_a, welcome to the Sonos Community!

I’m sorry to hear that you’re having issues using Spotify Connect with your Sonos system. 

I had mentioned in another thread on the community that I’ve raised the reddit thread with the relevant team, and I’ve also raised the Spotify Connect issue users are having so we can investigate. While there isn’t a ticket open currently and I don’t have anything to share, I’ll update the relevant threads on the community once I hear back about the status of this.

I hope this information helps!

Thanks ​@Jamie A . Mind pointing me in the direction of the other thread? I’ll follow that one and save you some effort 😁

Hi ​@abhi_a,

Sure, this one seems to have the most views and replies, so I’d suggest sticking to this one: 

Again, if I hear anything, I’ll try to update all the relevant threads and tag them. 

For anyone coming here: the firmware update 91.0-70070 seems to have solved the issue. For me at least

Terms & ConditionsCookie settingsAccessibility statement