CSPOT device not listed on Spotify Web API #153
Comments
|
I had the same problem. But I run a Squeezelite-ESP32 (Generic/I2S) . |
|
Same here, I realized that when integrating with HomeAssistant |
|
Well, just thought about it more 🤓. ZeroConf is used by default but that means that Spotify servers have no way to see local players, as they are not registered (not discovered) yet. They will only be when a local applicatio on your network discovers them and then registers them. You need to use login/password so that the player is known and then you'll see them from the webAPI |
|
Having said that, unfortunately, there is still a problem where the authorization works as expected but getting the AccessKey fails all the time |
|
Right, my understanding is that now that Spotify's CDN is used, we need credentials to get an access token/key (was not the case before). These credentials are given by Spotify controller when using ZeroConf but when using username/password, they are return as part of the authorization/authentication process. These were discarded previously but now they probably need to be used. I'll see if I can figure out something or hopefully @feelfreelinux will jump in and do in 5 min what will take me 5 days 😄. |
|
Done - it took me 5 hours which is still 295 minutes more than @feelfreelinux. I'll submit a PR soon |
|
It's fixed now, you just need to sue username/password once. After that, you can create a json credential files to be re-used for next sessions. |
|
Hello @philippe44,
So it looks like access tokens can be fetched. Any idea, what I could have done wrong here? Many thanks again in advance for the help |
|
This is weird, I'm using it now with the option to store credentials all the time. I'll verify with -u -p |
|
After starting the SpotifyApp once, it got visible also in the Web API... Sorry I should have read the instructions probably. Sorry! |
|
But it seems then that the -u/-p/-c options are not required. |
|
Nono don't think it should. Try the -c and create/store credentials once. Then restart it |
|
I did the following now:
So still not working as expected for me. |
|
Here is the trick that works for me: you have 2 identifiers on Spotify: your email address and a profile name. You can use both with the same password on -u and -p, but only if you use the profile name will the player appear in the webUI . Don't ask me exactly why but I think credential should also be created the same way, using for -U, not the email. Remember as well that the .json file can be created without using -u and -p, just use -c and connect once using the desktop app, it will create the credential files. |
|
Hello @philippe44, that is it, I use the email as username before and not the profile name - now it works! Thanks a lot for the hints and support. Marcus |
|
YES!!!!! @philippe44 |
Hello all,
I got CSPOT running on a ESP32. It is possible to connect via Spotify App from my phone and play music.
However, using the Spotify Web API (Get Available Devices), the CSPOT devices does not show up. (I can use the Web API to fetch my playlists - so overall auth did work).
It seems that "thrid-party" devices are not supported via the Web API.
Did anyone here succeed in controlling the CSPOT via Spotify Web API?
Many thanks in advance
Marcus
The text was updated successfully, but these errors were encountered: