witnessmenow / spotify-api-arduino

Arduino library for integrating with the Spotify Web-API (Does not play music)
MIT License
178 stars 33 forks source link

Update documentation that some endpoints require premium #28

Open arno4000 opened 3 years ago

arno4000 commented 3 years ago

The API client is working great so far on an ESP32 TTGO T-Display. But there is one problem:

All API functions, that use the /v1/me/player endpoint fail with the following error message

Skipping to next track.../v1/me/player/next
api.spotify.com
[E][ssl_client.cpp:36] _handle_error(): [send_ssl_data():301]: (-80) UNKNOWN ERROR CODE (0050)
Failed to send request

I have tested it with my own code, but also the example at https://github.com/witnessmenow/spotify-api-arduino/blob/master/examples/esp32/playerControls/playerControls.ino. Is this a bug or am I doing something wrong?

witnessmenow commented 3 years ago

Will test again when I'm at my computer, weird that those would fail!

On Fri 21 May 2021, 20:14 arno4000, @.***> wrote:

The API client is working great so far on an ESP32 TTGO T-Display. But there is one problem:

All API functions, that use the /v1/me/player endpoint fail with the following error message

Skipping to next track.../v1/me/player/nextapi.spotify.com [E][ssl_client.cpp:36] _handle_error(): [send_ssl_data():301]: (-80) UNKNOWN ERROR CODE (0050) Failed to send request

I have tested it with my own code, but also the example at https://github.com/witnessmenow/spotify-api-arduino/blob/master/examples/esp32/playerControls/playerControls.ino . Is this a bug or am I doing something wrong?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/witnessmenow/spotify-api-arduino/issues/28, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAL5PQT24VL24TDTF523HI3TO2WI5ANCNFSM45JW3XXQ .

arno4000 commented 3 years ago

I have tried the functions in the spotify developer console and there I am getting a 403 error with the message, that premium is required. Therefore I am closing the issue. I will reopen it, when i have tested it with a premium account and the ssl error is still there. Maybe you could add this to the readme.

witnessmenow commented 3 years ago

Ah thank you. Will add some info about this to the readme