Skip to main content
Contributor I
June 27, 2019
Answered

API Feature Request - Queue Control

I am both an avid Sonos (hardware) fan and also a Control4 user who loves to program in Composer.

I'm wondering how / where I can submit feature requests to re-enable a VERY important feature in the Sonos API. And that is... the ability to replace the queue when we are calling different playlists in programming.

If Playlist A is currently in the queue, and I don't manually go into the sonos app and clear the queue first, when I call Playlist B in programming (from a custom button, voice control, etc) it will MERGE Playlist B randomly into the queue alongside Playlist A's songs.

I understand that this topic has been hotly debated for some time on what the DEFAULT handling of the situation should be. And, although I still disagree that the majority of people would ever want to merge playlists into a queue by default... I do respect the decision by the devs to be diligent in keeping the default behavior consistent. However, i do not understand why you would REMOVE the ability to clear the queue through a command in the API for those users who want to implement that behavior? I have circled this request internally with several different 3rd parties thinking that it was a feature they just weren't tapping into. But, alas, each of them came back with the same reply saying that the API used to allow it, but now explicitly prohibits it???? Again, aside from the debate on what should be the default action... why would you remove functionality from the API? And, is there any way to get it added back? I can think of no reason why I would ever want to merge playlists in a custom control system specifically designed to give me TOTAL control of everything.

Thanks to the community managers for any info you can provide on this? I greatly appreciate it.
    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.
    Ryan S
    Ryan SAnswer
    Retired Sonos Staff
    September 30, 2019
    Hi g8rfn2, I don't have a timeline right now, but you can always contact the team at https://developer.sonos.com/ in case you want to give them a direct request. They may not have time to get right back to you though.
    Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.

    28 replies

    Ryan S
    Retired Sonos Staff
    October 9, 2019
    Hi Matt, I can't promise any traction, but I'll make sure that the team has seen the request. Thanks for reaching out!
    Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.
    g8rfn2Author
    Contributor I
    October 19, 2019
    Hi Matt, I can't promise any traction, but I'll make sure that the team has seen the request. Thanks for reaching out!

     

    What could possibly be their reason for NOT supporting it? It’s SO frustrating to not get any direct communication and just vague responses. If there is a legitimate reason, then they should just tell their consumers? Can i get a refund on all my devices since they no longer work as I want them to? Extreme example, but this is the equivalent of an auto manufacturer downgrading the software on your car to give you less features than when you bought it. Just give us a method to get around the new (poorly designed) “default behavior” in programming. Again, not asking you to revert the decision, just give us an alternative! I’m not understanding why nobody can actually answer me on this? I’m “trying” to be as patient as I can be, but we’re well past 3 months now? Is there a customer service manager I can speak with on the phone? Does that do me any good?

    controlav
    Lead Maestro
    October 19, 2019

    As I said already, this is trivial to do with the UPnP API. The UPnP API is so much more complete and useful than the REST API, and this wont be the last time you are frustrated with the REST API. Just make the switch.

    I seriously doubt any communication with a CSM would result in a new API, but happy to be wrong.

    Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.
    Lyricist I
    February 6, 2020

    I would also use it very well and unfortunately do not understand why you cannot implement it.

    Regards

    Michael

    Lyricist I
    February 7, 2020

    We’re also suffering from this lack of functionality. 

     

    Contributor I
    March 4, 2020

    As I said already, this is trivial to do with the UPnP API. The UPnP API is so much more complete and useful than the REST API, and this wont be the last time you are frustrated with the REST API. Just make the switch.

    I seriously doubt any communication with a CSM would result in a new API, but happy to be wrong.

     The UPnP API is more complete, but can we be sure it will be supported in the future?

    controlav
    Lead Maestro
    March 4, 2020

     The UPnP API is more complete, but can we be sure it will be supported in the future?

    Well it has been around since the day Sonos has shipped, so it has a solid history. I guess we’ll find out its longer term plan in May.

    Author of the leading independent Sonos apps for Android, MacOS, iOS, Windows and Xbox.
    Contributor I
    March 21, 2020

    I am also in great need of this feature. I live my life based off Spotify playlists and when trying to program a keypad to have the ability to pull up and switch between playlists from Spotify in shuffle mode is something that used to work! Without the “CLEAR PLAYLIST’ it’s pointless to program more than 1 Spotify Playlist through Control4. Please help!

     

    Nick

    Contributor I
    March 29, 2020

    Same problem here, I searched for hours thinking they can not have missed that feature in the API, but it looks like it has been missed. Please add this feature. Is there a way we can at least be informed, that it will be added?

    March 29, 2020

    If the UPnP API is not supported in S2 wouldn’t that just drive more people to stay on a legacy configuration? Is that the outcome Sonos wants?

    Local music library with carefully constructed playlists - no shuffling!, Integration with Homeseer Automation, No touch screen devices, No streaming services, No Apple products ever