mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #1672] Spotify is not finding the device, despite librespot advertising correctly #761
Labels
No labels
A-Alsa
SpotifyAPI
Tokio 1.0
audio
bug
can't reproduce
compilation
dependencies
duplicate
enhancement
good first issue
help wanted
high priority
imported
imported
invalid
new api
pull-request
question
reverse engineering
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librespot#761
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 @twaclaw on GitHub (Dec 31, 2025).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/1672
I am using version
0.8.0over Moode audio (10.3) on a Raspberry Pi 5. The installed version is0.8.0-moode1.librespotseems to be advertising correctly but the Spotify app cannot find the device.This is the Moode log
@kingosticks commented on GitHub (Dec 31, 2025):
Can you get more log, there's nothing to show a problem here.
@twaclaw commented on GitHub (Dec 31, 2025):
Thanks @kingosticks, that's as much as I got from moode's initialization command:
I will check to see if I can collect any additional logs, or if I can make them more verbose, and then I will post them here.
@twaclaw commented on GitHub (Dec 31, 2025):
@kingosticks, I don't see more log output than the one above. The command is already running with
-v.Spotify connect was working before I flashed the latest moode image
moOde: 10.0.3 2025-12-28. I am using the latest Spotify app9.1.6.1142. As I mentioned before,librespotseems to be advertising correctly, I don't see traces of any error. I am puzzled.@kingosticks commented on GitHub (Dec 31, 2025):
You could run it in your terminal without the output redirection. Remove:
from the end and reproduce the issue.
@twaclaw commented on GitHub (Dec 31, 2025):
I did so, I get the same log output.
@lumixing commented on GitHub (Dec 31, 2025):
I've also just stumbled upon a similar issue where the librespot device is shown on the official Spotify app device list but not in their Web API (https://developer.spotify.com/documentation/web-api/reference/get-a-users-available-devices). I'm pretty sure that was not an issue some time ago (I don't remember exactly when). Also, verbose logs don't indicate anything wrong.
(using version: librespot 0.8.0
3eca1ab(Built on 2025-12-30, Build ID: tsllhEcI, Profile: debug)).@kingosticks commented on GitHub (Dec 31, 2025):
For librespot to be shown on their web API you must have librespot login to your account i.e. using oauth. I don't think that's what the OP wants to do here as they are talking about zeroconf advertisements and there's clearly no oauth or saved credentials login happening.
@twaclaw commented on GitHub (Jan 3, 2026):
As I mentioned above, my Spotify App is @
9.1.6.1142. I tried with a different device which is at version9.1.2.1254. This time I can see my spotify connect device but I cannot connect to it. Since I did this, I get more log lines.This is the only error I spotted
[2026-01-03T08:56:07Z DEBUG librespot_core::connection] Connection to "ap-gew4.spotify.com:4070" failed: Connection refused (os error 111).Any ideas? Suggestions?
Thanks in advance
@twaclaw commented on GitHub (Jan 3, 2026):
I don't know what I did, but the problem is resolved. I can see my spotify connect device.