mirror of
https://github.com/aome510/spotify-player.git
synced 2026-04-26 01:15:55 +03:00
[GH-ISSUE #187] Support discovering zeroconf devices #1031
Labels
No labels
bug
documentation
enhancement
good first issue
help wanted
pull-request
question
third-party
third-party
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-player#1031
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 @flexwie on GitHub (May 4, 2023).
Original GitHub issue: https://github.com/aome510/spotify-player/issues/187
Describe the bug
The devices pane does not show my spotifyd instance running on my machine. The official player and mobile app are both showing it to me.
Other Spotify Connect devices are shown in spotify-player.
To Reproduce
Install spotify-player and spotifyd, run spotifyd in the background.
Expected behavior
Spotifyd should be shown like any other Connect device.
Environment
Additional context
I have the client ID set up in my config and no username/password as per the docs.
@aome510 commented on GitHub (May 4, 2023):
I assume you already followed this doc (https://github.com/aome510/spotify-player#spotify-connect).
Can you provide logs in
~/.cache/spotify-player?@flexwie commented on GitHub (May 4, 2023):
I added the id of the client I created to my config. This is my config right now:
I habe quite a few logs in that folder, is there anything particular you are looking for?
This is the latest (I skipped the keymap and auth part)
@aome510 commented on GitHub (May 5, 2023):
@flexwie thanks. I can confirm this issue is reproducible on my end.
I think this issue happens because
spotify_playerrelies on get-devices API to list the list of available devices whilespotifydrelies on zeroconf authentication. In other words,spotifyddevice won't show up in theget-devicesAPI until it gets authenticated with spotify connect using official Spotify apps.I'll try to figure out a way to make these kinds of devices discoverable by
spotify_player. In the meantime, one possible workaround is to specifyusernameandpasswordas in https://docs.spotifyd.rs/config/File.html to makespotifyddevice authenticated w/o spotify connect.@aome510 commented on GitHub (May 5, 2023):
Related: https://github.com/Spotifyd/spotifyd/issues/903#issuecomment-1519034873
Downgrading to0.3.3is also another option.@aome510 commented on GitHub (May 5, 2023):
Updated: adding support for discovering devices using https://en.wikipedia.org/wiki/Zero-configuration_networking requires to implement the zeroconf networking specs in
spotify_player. This is not trivial though as I don't have any knowledge on this subject.Updated the issue's description. I don't have any plans to fix this issue.
My suggested workaround will be either
usernameandpasswordinspotifydconfig filespotifydusing spotify connect in an official app before usingspotify_playerspotify-playerintegrated client@flexwie commented on GitHub (May 5, 2023):
Thanks for your help on this issue @aome510!
Just adding my credentials in the spotifyd config did not solve the issue for me, but selecting the spotifyd client from the official Spotify app did!