Skip to main content
Peter WM
Contributor I
October 3, 2018
Answered

UPnP vs New API

I control my theater room with Demopad and it includes a Connect feeding into the system. After a lot of reading and learning and much trial and error, I've been able to build a Sonos page within Demopad using UPnP, that shows cover art, a progress bar for the current track, and a queue of the current track + the next three. It also has play, pause and track skip controls.

My question - should I be trying to move across to the new API ? Will it give me more control ? Will it make things easier ?

This is purely a hobby for me so forgive me if I'm misunderstanding how the new API works.
    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
    October 3, 2018
    Hi Peter, there's a lot of functionality built into the new API. If you are curious, should definitely check it out: https://developer.sonos.com/
    Mark good posts by pressing the like button, and select the best answer on questions you've asked to help others find solutions.
    View in thread

    12 replies

    Show previous replies
    pwt
    pwt
    Virtuoso
    October 26, 2018
    I guess the thing that puzzles me (and apparently folks at Control4 and others who depend on this) is why Sonos would write an API that is less capable than the UPnP interface?
    Because it's clearly a work in progress. Expect it to evolve to become more comprehensive.

    My understanding is that the UPnP API is not documented, and is not formally supported by Sonos. It's great to have (and I use it for a bunch of automation tasks), but depending on it is risky since it's intended for Sonos's internal use and subject to change without notice.
    4 x P:5 | Sub | 4 x P:1 | 3 x Connect | 2 x Boost | Connect:Amp | 2 x One | Amp | Move | Port | Era 300
    upstatemike
    October 26, 2018
    I guess the thing that puzzles me (and apparently folks at Control4 and others who depend on this) is why Sonos would write an API that is less capable than the UPnP interface?
    Because it's clearly a work in progress. Expect it to evolve to become more comprehensive.

    My understanding is that the UPnP API is not documented, and is not formally supported by Sonos. It's great to have (and I use it for a bunch of automation tasks), but depending on it is risky since it's intended for Sonos's internal use and subject to change without notice.

    Risky or not UPnP is the only way for people to accomplish what they want to do today (and have been doing for many years). Sonos should not expect folks to adopt the new API when it is lacking so much of the functionality that UPnP provides. I wonder how much priority has been placed on closing those gaps sooner rather than later?
    Local music library with carefully constructed playlists - no shuffling!, Integration with Homeseer Automation, No touch screen devices, No streaming services, No Apple products ever
      Terms & ConditionsAccessibility statement