[GH-ISSUE #151] API: skip to next track #93

New issue

Closed

opened 2026-02-28 14:25:16 +03:00 by kerem · 3 comments

kerem commented

2026-02-28 14:25:16 +03:00

Owner

Originally created by @stronk-dev on GitHub (Dec 7, 2024).
Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/151

Hi, I've started work on a simple React component so that I can have media controls on my homepage (for users on my local network or VPN) and have a touchscreen on my Pi for quick controls.

So far very happy with go-librespot and to have a working spotify daemon again! The only issue I am running into is what to provide to the /player/next API endpoint, is it not possible to just skip to the next song? Right now I seek to the end of the song as a substitute.

Originally created by @stronk-dev on GitHub (Dec 7, 2024). Original GitHub issue: https://github.com/devgianlu/go-librespot/issues/151 Hi, I've started work on a [simple React component](https://github.com/stronk-dev/react-librespot-controller) so that I can have media controls on my homepage (for users on my local network or VPN) and have a touchscreen on my Pi for quick controls. So far very happy with `go-librespot` and to have a working spotify daemon again! The only issue I am running into is what to provide to the `/player/next` API endpoint, is it not possible to just skip to the next song? Right now I seek to the end of the song as a substitute.

kerem closed this issue

2026-02-28 14:25:16 +03:00

kerem commented

2026-02-28 14:25:17 +03:00

Author

Owner

@devgianlu commented on GitHub (Dec 11, 2024):

You should be able to make a POST request to /player/next with an empty JSON object as body. The uri field is not mandatory.

@devgianlu commented on GitHub (Dec 11, 2024): You should be able to make a POST request to `/player/next` with an empty JSON object as body. The `uri` field is not mandatory.

kerem commented

2026-02-28 14:25:17 +03:00

Author

Owner

@stronk-dev commented on GitHub (Dec 12, 2024):

You are correct, that works just fine 😅

@stronk-dev commented on GitHub (Dec 12, 2024): You are correct, that works just fine 😅

kerem commented

2026-02-28 14:25:17 +03:00

Author

Owner

@iVolt1 commented on GitHub (Mar 1, 2025):

I have been running go librespot .20 for a couple of months and it is working flawlessly, connecting fast and staying connected all day with a smaller cpu and memory foot print. Great work!

The only issue I have seen so far is the play-next api is slightly different than for librespot -java in that the play-next api does not require a uri or empty json object. This breaks the home assistant media player play-next button because media player does not send a uri or empty json object.

I hope this can be fixed and metadata through linux pipes can be completed soon so the Homepod Connect addon can have advantages go librespot brings.

Issue: Add metadata output to a pipe as it is in librespot-java #157

Thanks,
iVolt1

@iVolt1 commented on GitHub (Mar 1, 2025): I have been running go librespot .20 for a couple of months and it is working flawlessly, connecting fast and staying connected all day with a smaller cpu and memory foot print. Great work! The only issue I have seen so far is the play-next api is slightly different than for librespot -java in that the play-next api does not require a uri or empty json object. This breaks the home assistant media player play-next button because media player does not send a uri or empty json object. I hope this can be fixed and metadata through linux pipes can be completed soon so the Homepod Connect addon can have advantages go librespot brings. Issue: Add metadata output to a pipe as it is in librespot-java #157 Thanks, iVolt1