mirror of
https://github.com/librespot-org/librespot.git
synced 2026-04-27 08:15:50 +03:00
[GH-ISSUE #372] Invisible after using with another account #247
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#247
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 @hige-agusd on GitHub (Sep 17, 2019).
Original GitHub issue: https://github.com/librespot-org/librespot/issues/372
So the raspotify device can be discovered on any Device in my LAN, just like it should. If Account 1 plays Music, it disappears. Still fine. But if Account 1 disconnects from the raspotify by switching the playback device back to smartphone or what else, the raspotify keeps beeing visible only to devices logged in to account 1. Devices with other accounts can't see the raspotify and restarting the service doesn't seem to fix the issue
@linibou commented on GitHub (Sep 25, 2019):
Same issue for me
@Faabvk commented on GitHub (Oct 15, 2019):
Also affected by this. It's advertised that the device can be discovered on the same network, but I can only seem to connect to it when logged in to my account that I set Librespot up with.
@illtrick commented on GitHub (Mar 30, 2020):
I hit this same issue with the Volumio plugin and posted my logs here No attention there yet either but I thought it might help whomever might be troubleshooting.
Oddly I do not have this issue at all with Ropieee XL, it handles multiple accounts flawlessly.
@roderickvd commented on GitHub (May 25, 2021):
Fixed downstream in https://github.com/balbuze/volumio-plugins/issues/259.
If this still occurs in the latest
librespot(and not just Volumio) then feel free to re-open.