[GH-ISSUE #653] macOS + home-manager: no devices found #263

Open
opened 2026-02-28 14:48:07 +03:00 by kerem · 8 comments
Owner

Originally created by @rpearce on GitHub (Nov 7, 2020).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/653

image image

Hi, thank you for this project! Amazing.

I'm using macOS with nix+home-manager, and I've got everything running smoothly and have Spotify Premium, but when I try to play a song, it can't figure out what device to use. I'm on a MacBook Pro.

Here's my client.yml:

---
client_id: ...
client_secret: ...
device_id: ~
port: 8888

This happens even if I have the Spotify app running, as seemed to be suggested here: https://github.com/Rigellute/spotify-tui/issues/310. I have not been able to get spotifyd running on macOS with homebrew.

Thanks for your help!

Originally created by @rpearce on GitHub (Nov 7, 2020). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/653 <img width="988" alt="image" src="https://user-images.githubusercontent.com/592876/98446278-4ffd6080-2114-11eb-880a-5e85c789e066.png"> <img width="841" alt="image" src="https://user-images.githubusercontent.com/592876/98452244-65d74980-2145-11eb-8790-9b0287ba21c6.png"> Hi, thank you for this project! Amazing. I'm using macOS with nix+home-manager, and I've got everything running smoothly and have Spotify Premium, but when I try to play a song, it can't figure out what device to use. I'm on a MacBook Pro. Here's my `client.yml`: ``` --- client_id: ... client_secret: ... device_id: ~ port: 8888 ``` This happens even if I have the Spotify app running, as seemed to be suggested here: https://github.com/Rigellute/spotify-tui/issues/310. I have not been able to get spotifyd running on macOS with homebrew. Thanks for your help!
Author
Owner

@andersfylling commented on GitHub (Nov 16, 2020):

Exactly the same issue. I'm on arch linux. Though I am not running a the official spotify application on my computer (I assumed spotifyd was a replacement from their README).

<!-- gh-comment-id:728360084 --> @andersfylling commented on GitHub (Nov 16, 2020): Exactly the same issue. I'm on arch linux. Though I am not running a the official spotify application on my computer (I assumed spotifyd was a replacement from their README).
Author
Owner

@schwittlick commented on GitHub (Nov 18, 2020):

same issue.. it only works when the spotify app is running in parallel :/

<!-- gh-comment-id:729640881 --> @schwittlick commented on GitHub (Nov 18, 2020): same issue.. it only works when the spotify app is running in parallel :/
Author
Owner

@andersfylling commented on GitHub (Nov 18, 2020):

If the spotifyd is running in the background, the music has to be started from an official spotify client via Spotify Connect for me. I had some serious issue getting spotifyd working in the first place.

<!-- gh-comment-id:729696515 --> @andersfylling commented on GitHub (Nov 18, 2020): If the spotifyd is running in the background, the music has to be started from an official spotify client via Spotify Connect for me. I had some serious issue getting spotifyd working in the first place.
Author
Owner

@Rigellute commented on GitHub (Nov 24, 2020):

Hi! This sounds like an issue with spotifyd. The device list in spotify-tui is the result of an API call to Spotify. Sounds like spotifyd is not discoverable for some reason?

<!-- gh-comment-id:732800680 --> @Rigellute commented on GitHub (Nov 24, 2020): Hi! This sounds like an issue with `spotifyd`. The device list in `spotify-tui` is the result of an API call to Spotify. Sounds like `spotifyd` is not discoverable for some reason?
Author
Owner

@andersfylling commented on GitHub (Nov 24, 2020):

Yeah I believe so as well, seems like it can't "discover itself", until "triggered" by another device through Spotify Connect. If that makes sense.

Spotifyd is able to see other spotify devices/instances, just not itself.

<!-- gh-comment-id:733080765 --> @andersfylling commented on GitHub (Nov 24, 2020): Yeah I believe so as well, seems like it can't "discover itself", until "triggered" by another device through Spotify Connect. If that makes sense. Spotifyd is able to see other spotify devices/instances, just not itself.
Author
Owner

@codygman commented on GitHub (Dec 18, 2020):

When I get this issue just restaring spotifyd with systemctl --user restart spotifyd.service fixes the issue.

<!-- gh-comment-id:748161354 --> @codygman commented on GitHub (Dec 18, 2020): When I get this issue just restaring spotifyd with `systemctl --user restart spotifyd.service` fixes the issue.
Author
Owner

@codygman commented on GitHub (Dec 18, 2020):

https://github.com/Spotifyd/spotifyd/pull/596

<!-- gh-comment-id:748162790 --> @codygman commented on GitHub (Dec 18, 2020): https://github.com/Spotifyd/spotifyd/pull/596
Author
Owner

@llagerlof commented on GitHub (Sep 14, 2021):

Same problem here. Running on Windows 8.1 x64.

<!-- gh-comment-id:919100228 --> @llagerlof commented on GitHub (Sep 14, 2021): Same problem here. Running on Windows 8.1 x64.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-tui#263
No description provided.