-
-
Notifications
You must be signed in to change notification settings - Fork 221
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't see device - troubleshooting help? #706
Comments
quite same problem here, all my devices can be managed by some headless apps I have, but raspotify can't, I must start my spotify app (on my phone for example), and next I can. Is it a way to manually "wake-up" it ? |
Did you do OAuth? |
Okay, a quick note for users who are feeling confused about this: OAuth: Authorization Password login has been deprecated and is no longer supported. Instead, OAuth Authorization must be used. Follow the steps below at START HERE to authenticate using OAuth: To use Midori browser under vnc comment out #python3 spotifypod.py in sudo nano /etc/xdg/openbox/autostart [INFO librespot_oauth] OAuth server listening on 127.0.0.1:5588 The authentication token will be in the folder YOUR_CONFIGURATION_PATH called credentials.json. I copied that now to the raspotify folder cp credentials.json /var/cache/raspotify/ Updated the raspotify config file sudo nano /etc/raspotify/conf to comment out below items to enable 0Auth instead of username/password: #LIBRESPOT_DISABLE_CREDENTIAL_CACHE= Restarted raspotify with systemctl restart raspotify and everything worked, In sudo nano /etc/xdg/openbox/autostart un-comment python3 spotifypod.py save and reboot. Good Luck. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent START HERE: Password login has been deprecated and is no longer supported. Instead, OAuth Authorization must be used. Follow the steps below to authenticate using OAuth: #Run the following command to initiate the OAuth process: librespot --cache /var/cache/raspotify -j Press Ctrl-C to quit. [2024-12-31T05:17:30Z INFO librespot] Gracefully shutting down. pi@sPoT:$ cd /var/cache/raspotify/ pi@sPoT:$ cd /var/cache/raspotify ==== AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon === Update: the raspotify config file sudo nano /etc/raspotify/conf to comment out below items to enable 0Auth instead of username/password: #LIBRESPOT_DISABLE_CREDENTIAL_CACHE= sudo reboot note: However you may still need to select the device from the spotify-connect list (if you didn't do OAuth (Open Authorization) with your computer/phone first you may have to refresh the Spotify-Connect list a few times to be able to see your "sPoT" device on the list of available devices - you can close immediately after otherwise you will receive "error no devices". |
In my case, I wasn't authenticating, just trying to use Zeroconf. The problem in my case was that I was connected to a VPN (NordVPN) that enabled a firewall. I disabled the firewall and things were fine. This can definitely be closed, though that is a helpful post! |
Okay ... Your Welcome. |
Due Diligence
What can we help you with?
I just installed raspotify on my raspberry pi 4, and it simply is not appearing on my network. The pi is connected over Ethernet. I have tried clients connected over wifi and also my PC connected to the same router as the pi, nothing show up. Nothing shows up in journalctl except start and stop notices. No crash report. Service shows as running.
I use multiple google homes which show up no problem. I have also used an Android device as a Spotify connect receiver with an APK I found online, which also uses librespot as a backend, and it appears fine (though it doesn't connect, but that's a different issue).
Is there a guide or series of steps I can try to follow to pinpoint where the issue is occuring? I'm guessing it has something to do with zeroconf over my router but I am in a bit over my head. I'm very tech capable just not hugely knowledgeable about network stuff.
The text was updated successfully, but these errors were encountered: