Please document that the API doesn't support Sonos devices

[softplus]

I realize there are probably good and/or legal reasons why you can't control Sonos devices via the Spotify API, but it is super-annoying to learn about this only once you're ready to try your code on various devices. Can this be better documented in the API so that developers don't waste their time, or at least have the proper expectations? If this is not unique to Sonos, it would be nice to have a list of supported or unsupported device types. (I have no interest in making something specific for Sonos, we just have a mix of devices at home and I'd love to use one thing to control them all -- alas, it turns out, that's not possible.)

Some of the API pages that could be updated with information about supported devices: "Get Available Devices", "Start/Resume Playback", "Transfer Playback". For example, you could make the "device_id" attribute a link to a page that gives information on device_id's. 

[Hubo]

Hey @softplus, welcome to the Spotify Community!

Thanks for posting your feedback here! I completely understand where you're coming from. You've come to the right place to share this. The right folks keep an eye out on these boards and will pass your feedback on. Thanks!

Hope you have a great day!
Hubo

[thlucas]

Not to hijack your thread, but I have had a question regarding Sonos and Spotify Connect ZeroConf functionality regarding token type of "authorization_code" processing on this board for over a month now with zero responses.

Is there some documentation somewhere on how the Spotify Desktop players connect to the Sonos device via Spotify Connect Zeroconf interface?  The device is responding to all of the Spotify Connect Zeroconf commands (e.g. resetUsers, getInfo, addUser), but the addUser always fails because I don't know what to pass for the "blob" parameter.

Extremely frustrating, as there is no documentation anywhere for that token type / flow!