mirror of
https://github.com/lox-audioserver/lox-audioserver.git
synced 2026-04-26 06:45:47 +03:00
[GH-ISSUE #145] [4.x Beta5] spotify with sendspin not working #83
Labels
No labels
bug
enhancement
pull-request
released
released on @beta
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lox-audioserver#83
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wiking-at on GitHub (Jan 30, 2026).
Original GitHub issue: https://github.com/lox-audioserver/lox-audioserver/issues/145
I installed [testing-20260125114926]. i can play a radio stream - but spotify is not working. I did a fresh configuration, inserted my client id and authenticated with my spotify user.
Logs with level spam:
from a user perspective it looks like if spotify is connected - but from the log it looks like i don't get audio data - right?
@wiking-at commented on GitHub (Jan 31, 2026):
today the playback of a playlist started - but it never changed to the second song in the playlist.
the song "Makina Time" is only 2:10 long. this is also correctly displayed in the loxone app. but when the song is finished it keeps "staying" on that song - and not switching to the next one - still in a play state.
here is a debug log - i also tried a tts message and a radio stream which did work.
Also skipping forward in the same songs seems not to work. I use my own spotify client id and can successfully log on to spotify.
I use only the one zone in the debug logs currently:
Spam Level Logs
i use the following setup for the sendspin client - music assistant is stopped and lox-audioserver is the only sendspin server in my network.
Config Sendspin
edit:
in line 1695 i see the message ""Playback error: spotify end_of_track before pcm"" - where the song should end a switch to the next song should occur. it seems that the audio broadcast still continues until i manually switch to another song. the manual switch worked again.
@rudyberends commented on GitHub (Feb 7, 2026):
Is this still an issue with the latest beta4?
@wiking-at commented on GitHub (Feb 8, 2026):
unfortunately, after the update i can't connect to spotify with my client-id anymore. i inserted the new callback url (after github repo rename). i double checked my client id (also removed and readded it).
when i press the button "add spotify account" i get the error "INVALID_CLIENT: Invalid redirect URI". also tried a private mode window with another browser - still the same error.
i use the docker beta 5 package you provide. i don't build from git for this project - i just pull new beta images if you release them.
@wiking-at commented on GitHub (Feb 13, 2026):
@rudyberends thanks for the hint with the callback url in #155 - i can now authenticate. Spotify playback is still not working unfortunately. i can now search tracks and see cover-art in the loxone app. radio streams are working - although there is annoying noise and stop every few seconds - the radio stream starts itself after that again. spotify playback is not working at all. i also connected the same sendspin player to a music-assistant instance - spotify and radio playback is working without issues - so i think the issue should be somewhere in the current beta implementation with sendspin.
Here is a SPAM level debug log where I run a radio stream - which I stop - and then i try to start a spotify track. the playback in the loxone app jumps immediately to stop after i press play.
if you need other logs or infos let me know.
@wiking-at commented on GitHub (Feb 13, 2026):
Some - hopefully helpful observations (assisted by gemini log review):
Login Denied: The logs show that node-librespot fails during the SPIRC (Spotify Interface Remote Control) startup:
spirc start failed: Invalid state { Login request was denied: BAD_REQUEST }
Infinite Skip Loop: Once a track is requested, it fails with FailedPrecondition / FaultyRequest(BAD_REQUEST), and the server attempts to skip through the entire playlist.
Discovery Issue: Interestingly, the zone does not appear in the Spotify Connect device list in the official Spotify app at all, even though the token refresh in the logs is marked as successful.
Single Zone: This is a single-zone setup, so there are no conflicting instances on the same machine.
Relevant Log Snippet:
It seems like the session handshake between node-librespot and Spotify's AP servers is being rejected, despite a valid OAuth token. Any idea if this is related to the specific node-librespot version used in Beta-5 or a session handling regression?
@rudyberends commented on GitHub (Feb 13, 2026):
Yes, I am aware of this. It's already reported in 155. I told you the callback issue was not relevant because there where bigger Spotify issues.
Let's close this one as it's basically a duplicate of 155 now.
I can confirm there are no general issues with sendspin as it is my own primary protocol for my setup. If you have issues with sendspin with any other source besides Spotify, please open a new issues so we can look at that specific problem.
@wiking-at commented on GitHub (Feb 13, 2026):
as mentioned also the radio playback isn't working properly.
radio streams are playing - but stop every few seconds before restarting again. I wait until the spotify issues are fixed and revert my install back to music assistant (without loxone integration) until the spotify issues are adressed. if spotify works and there are issues left with radio i open a new issue. thanks for you fast support.