-
Notifications
You must be signed in to change notification settings - Fork 79
sonos devices in API devices list #1337
Comments
I would like to see this as well, you can get them listed when you connect trough them using your phone. From that moment they will connected to your account for a while but somehow the API sometimes loses them. The web api can't really get to those devices so I think the spotify app remote SDK should be the one who can list devices... |
+1 If Spotify App can discover sonos and play songs it isn't technically impossible - so why does API not support this? This is kind of ... |
+1 is there any plan to support SONOS devices in web api? |
Why is this still not supported. Obviously support for Sonos works as it works as a connected device in the regular app and Sonos devices are also visible on the Could someone from Spotify at least comment on what is holding them back in removing the |
Please provide a response to this query. |
Any update on this? There seems to be a documentation ticket at #654 and it was closed without explanation some years ago #671 Since this worked once with my sonos devices, I would like to have some explanation on what is keeping me them form being visualized when calling https://developer.spotify.com/documentation/web-api/reference-beta/#endpoint-get-a-users-available-devices This site gives some general information though: https://developer.spotify.com/documentation/web-api/guides/using-connect-web-api/
|
Would love to have the Sonos devices un-restricted I can connect to and control them from Desktop, Phone, and Web Player?? But not Web Api, doesn't make any sense. |
Any updates on this? |
There are a lot of people wating for a solution. Me,too. |
Any update on adding Sonos devices in the API devices list?
Locally on my network I can see the Sonos devices from Mobile and PC apps, however not from the webapp.
Would want to run an app internally within my network but unable to pull the full devices list that app would see as Sonos devices are enabled.
The text was updated successfully, but these errors were encountered: