-
Notifications
You must be signed in to change notification settings - Fork 174
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
Support discovering zeroconf devices #187
Comments
I assume you already followed this doc (https://github.com/aome510/spotify-player#spotify-connect). Can you provide logs in |
I added the id of the client I created to my config. This is my config right now: client_id = "8f03b7ae0a8a45bf9dxxxxxxxxx"
enable_media_control = true
default_device = "spotify-player"
[device]
name = "spotify-player"
volume = 100
device_type = "speaker"
bitrate = 160
audio_cache = false I habe quite a few logs in that folder, is there anything particular you are looking for?
|
@flexwie thanks. I can confirm this issue is reproducible on my end. I think this issue happens because I'll try to figure out a way to make these kinds of devices discoverable by |
Related: Spotifyd/spotifyd#903 (comment)
|
Updated: adding support for discovering devices using https://en.wikipedia.org/wiki/Zero-configuration_networking requires to implement the zeroconf networking specs in Updated the issue's description. I don't have any plans to fix this issue. My suggested workaround will be either
|
Thanks for your help on this issue @aome510! |
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.
The text was updated successfully, but these errors were encountered: