What did Sonos Support say, when you called them? As far as I’m aware, the vast majority of ‘closed’ threads are because of lack of activity over time.
Important to note that your Sonos reaches out to a different server than the Deezer app itself. Always a safe bet to uninstall Deezer from Sonos, and add it back in, to force a new handshake with the Deezer auth server, too.
What did Sonos Support say, when you called them? As far as I’m aware, the vast majority of ‘closed’ threads are because of lack of activity over time.
I didn’t call them, because the previous thread noted that there was already a development ticket opened to address this issue; the original quote was:
I have spent 2hrs on the phone with tech support, the guy was very helpful, it's been reported as a bug now, it will get fixed.
I would have posted this request for an update in that thread, but it was locked. it looks like the identical issue with Spotify was recently fixed, so I was hoping it was something I was either missing, or that there would be info from Sonos on. Would be nice if there was some visibility into the issue tracker at the Sonos end (although I also understand why there isn’t).
Important to note that your Sonos reaches out to a different server than the Deezer app itself. Always a safe bet to uninstall Deezer from Sonos, and add it back in, to force a new handshake with the Deezer auth server, too.
Thanks, that’s good to know; I’ll try it, although given that there were enough other people with the same issue that I don’t have super high hopes. But if it’s that simple I’ll be pretty happy!
More data supplied always helps a coder who is trying to track down an issue, just because it is a ‘known’ doesn’t mean there isn’t value in adding your concern to the ‘list’. There is always value in calling in.
The vast majority of ‘locked’ threads are due to the automated system that closes threads due to no activity, and not because Sonos feels the situation has been resolved.
I can just confirm the issue hasn't been resolved
More data supplied always helps a coder who is trying to track down an issue, just because it is a ‘known’ doesn’t mean there isn’t value in adding your concern to the ‘list’. There is always value in calling in.
The vast majority of ‘locked’ threads are due to the automated system that closes threads due to no activity, and not because Sonos feels the situation has been resolved.
Being respectful to both my time and the support person’s time, I didn’t spend more time on the phone with support because the issue clearly easily recreates, there is no more information to be added other than to clearly describe the steps to recreate. This was done in both this thread and the linked thread. It also also described by multiple users as an active issue. Why waste hours of both my time and a support person’s time doing the same thing again?
If Sonos is monitoring these threads, then I’d expect a dev / BA to ask for detail if necessary - but there’s where I could be wrong; perhaps they have no visibility into these posts? I would assume they have company mods making the necessary connections to internal technical resource, but that’s just a guess based on what I’ve seen with other companies.
All the same, the issue is not a complex one; using “Start Radio” with Deezer as the provider causes tracks to endlessly skip one to the next without playing audio. All other Deezer functionality appears to work. If this is logged with development (as per the other thread), I would expect they have more than enough information to replicate and solve it.
My question, going back to it, is this an active dev issue still?
Same issue with Deezer.
Sonos, what's are you doing to resolve this issue?
I have the same issue and it's been months like this.
Unbelievable poor support.
