[GH-ISSUE #310] no device is found #125

New issue

Closed

opened 2026-02-28 14:47:12 +03:00 by kerem · 26 comments

kerem commented 2026-02-28 14:47:12 +03:00

Owner

Copy link

Originally created by @verajosemanuel on GitHub (Feb 24, 2020).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/310

installed spotifyd and spt.
run spotifyd

 ps -ef | grep spotify
jose     11868     1  0 12:40 ?        00:00:00 spotifyd
jose     11885 11656  0 12:40 pts/4    00:00:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn spotify

run spt (installed via snap)

Originally created by @verajosemanuel on GitHub (Feb 24, 2020). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/310 installed spotifyd and spt. run spotifyd ``` ps -ef | grep spotify jose 11868 1 0 12:40 ? 00:00:00 spotifyd jose 11885 11656 0 12:40 pts/4 00:00:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn spotify ``` run spt (installed via snap) 

kerem closed this issue 2026-02-28 14:47:12 +03:00

kerem commented 2026-02-28 14:47:13 +03:00

Author

Owner

Copy link

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

Could be that you've logged in to a different account using spotifyd compared to the account used to create the client credientials for spotify-tui?

<!-- gh-comment-id:590477268 --> @Rigellute commented on GitHub (Feb 24, 2020): Could be that you've logged in to a different account using spotifyd compared to the account used to create the client credientials for spotify-tui?

kerem commented 2026-02-28 14:47:13 +03:00

Author

Owner

Copy link

@verajosemanuel commented on GitHub (Feb 24, 2020):

Nop

<!-- gh-comment-id:590483830 --> @verajosemanuel commented on GitHub (Feb 24, 2020): Nop

kerem commented 2026-02-28 14:47:13 +03:00

Author

Owner

Copy link

@er0k commented on GitHub (Feb 25, 2020):

I have the same issue on debian buster

$ uname -srv
Linux 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26)

$ spotifyd --version
spotifyd 0.2.24

$ spt --version
spotify-tui 0.15.0

I get "No devices found" in spotify-tui.

However, if I start spotifyd and then use the Spotify client on my phone, the spotifyd device shows in the Android client. Once I switch to the spotifyd device with the Android client, the spotifyd device appears in spotify-tui and I can use it normally. So, it seems like there may be an issue with autodiscovery between spotifyd and spotify-tui?

<!-- gh-comment-id:590908613 --> @er0k commented on GitHub (Feb 25, 2020): I have the same issue on debian buster ``` $ uname -srv Linux 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1 (2020-01-26) $ spotifyd --version spotifyd 0.2.24 $ spt --version spotify-tui 0.15.0 ``` I get "No devices found" in spotify-tui. However, if I start spotifyd and then use the Spotify client on my phone, the spotifyd device shows in the Android client. Once I switch to the spotifyd device with the Android client, the spotifyd device appears in spotify-tui and I can use it normally. So, it seems like there may be an issue with autodiscovery between spotifyd and spotify-tui?

kerem commented 2026-02-28 14:47:13 +03:00

Author

Owner

Copy link

@Rigellute commented on GitHub (Feb 25, 2020):

Hmm... spotify-tui calls the devices endpoint from the spotify api and displays that list.

Is it possible that the spotifyd client is not active when spotify-tui goes to this devices screen? We could implement some polling on that endpoint (currently the request is only made when that screen is first shown).

<!-- gh-comment-id:590922982 --> @Rigellute commented on GitHub (Feb 25, 2020): Hmm... spotify-tui calls the [`devices` endpoint](https://developer.spotify.com/documentation/web-api/reference/player/get-a-users-available-devices/) from the spotify api and displays that list. Is it possible that the spotifyd client is not active when spotify-tui goes to this devices screen? We could implement some polling on that endpoint (currently the request is only made when that screen is first shown).

kerem commented 2026-02-28 14:47:13 +03:00

Author

Owner

Copy link

@Spinnerthing commented on GitHub (Feb 25, 2020):

I wonder if the issue is related to spotifyd, I have been having issues with spotifyd not being viewable as a device with either the spotify web client or spt, but if I use the official spotify client on linux it can see spotifyd device and once that has seen it then spotifyd is visible to both the web client and spt.

<!-- gh-comment-id:591079499 --> @Spinnerthing commented on GitHub (Feb 25, 2020): I wonder if the issue is related to spotifyd, I have been having issues with spotifyd not being viewable as a device with either the spotify web client or spt, but if I use the official spotify client on linux it can see spotifyd device and once that has seen it then spotifyd is visible to both the web client and spt.

kerem commented 2026-02-28 14:47:13 +03:00

Author

Owner

Copy link

@pablodz commented on GitHub (Feb 25, 2020):

You need a spotify client open, maybe your phone, TV or other device. Premium is necessary.

<!-- gh-comment-id:591095471 --> @pablodz commented on GitHub (Feb 25, 2020): You need a spotify client open, maybe your phone, TV or other device. Premium is necessary.

kerem commented 2026-02-28 14:47:13 +03:00

Author

Owner

Copy link

@Spinnerthing commented on GitHub (Feb 25, 2020):

Actually for me it was a fail regarding config for spotifyd, it was in discovery mode because the username/password was not set. (Because it was not reading the conf file where I'd put it due to a typo)

<!-- gh-comment-id:591118059 --> @Spinnerthing commented on GitHub (Feb 25, 2020): Actually for me it was a fail regarding config for spotifyd, it was in discovery mode because the username/password was not set. (Because it was not reading the conf file where I'd put it due to a typo)

kerem commented 2026-02-28 14:47:13 +03:00

Author

Owner

Copy link

@Spinnerthing commented on GitHub (Feb 26, 2020):

@er0k your issue sounds like a config fail in spotifyd, when it doesn't have a valid username/password then it has a discovery mode which needs an official client to make it then become discoverable to spotify tui and even the web client.

<!-- gh-comment-id:591344161 --> @Spinnerthing commented on GitHub (Feb 26, 2020): @er0k your issue sounds like a config fail in spotifyd, when it doesn't have a valid username/password then it has a discovery mode which needs an official client to make it then become discoverable to spotify tui and even the web client.

kerem commented 2026-02-28 14:47:13 +03:00

Author

Owner

Copy link

@nachocarballeda commented on GitHub (Mar 23, 2020):

You need a spotify client open, maybe your phone, TV or other device. Premium is necessary.

I solve the same issue with this reply :¬|

<!-- gh-comment-id:602669353 --> @nachocarballeda commented on GitHub (Mar 23, 2020): > You need a spotify client open, maybe your phone, TV or other device. Premium is necessary. I solve the same issue with this reply :¬|

kerem commented 2026-02-28 14:47:13 +03:00

Author

Owner

Copy link

@Rigellute commented on GitHub (Mar 30, 2020):

Closing as @ZurMaD and @nachocarballeda are correct. Premium is necessary to control playback

<!-- gh-comment-id:605888300 --> @Rigellute commented on GitHub (Mar 30, 2020): Closing as @ZurMaD and @nachocarballeda are correct. Premium is necessary to control playback

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@breuerfelix commented on GitHub (May 1, 2020):

same issue here.
i have the spotifyd daemon run at startup as a system service.

when i start spotify tui right after system start it is able to detect the device. if i wanna hear music some hours later it is not able to detect my spotifyd again even though it is running fine. i can start listening on that via smartphone. AFTER i hit start on the smartphone it shows up when pressing d again on spotify tui.

Seems like some idling problem to me. any advices ?

<!-- gh-comment-id:622318620 --> @breuerfelix commented on GitHub (May 1, 2020): same issue here. i have the spotifyd daemon run at startup as a system service. when i start spotify tui right after system start it is able to detect the device. if i wanna hear music some hours later it is not able to detect my spotifyd again even though it is running fine. i can start listening on that via smartphone. AFTER i hit start on the smartphone it shows up when pressing d again on spotify tui. Seems like some idling problem to me. any advices ?

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@datkush420 commented on GitHub (May 4, 2020):

I'm having the same issue as outlined above by @breuerfelix. The devices menu "d" is empty. If I open spotify on my phone and select my computer, go back to terminal and hit "d" again, the list populates and I can play music.

<!-- gh-comment-id:623749762 --> @datkush420 commented on GitHub (May 4, 2020): I'm having the same issue as outlined above by @breuerfelix. The devices menu "d" is empty. If I open spotify on my phone and select my computer, go back to terminal and hit "d" again, the list populates and I can play music.

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@breuerfelix commented on GitHub (May 5, 2020):

@Rigellute maybe reopen this issue again ? :)

<!-- gh-comment-id:624073824 --> @breuerfelix commented on GitHub (May 5, 2020): @Rigellute maybe reopen this issue again ? :)

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@Spinnerthing commented on GitHub (May 6, 2020):

@breuerfelix I don't think these are issues with spotify-tui but spotifyd, @datkush420 issue sounds more like a config issue with spotifyd going in to discovery mode.

For you @breuerfelix maybe try open a bug report with spotifyd about it not being discoverable after a while of inactivity. When I had my issues I found a similar sort of problem was being discussed there too.

<!-- gh-comment-id:624466635 --> @Spinnerthing commented on GitHub (May 6, 2020): @breuerfelix I don't think these are issues with spotify-tui but spotifyd, @datkush420 issue sounds more like a config issue with spotifyd going in to discovery mode. For you @breuerfelix maybe try open a bug report with spotifyd about it not being discoverable after a while of inactivity. When I had my issues I found a similar sort of problem was being discussed there too.

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@breuerfelix commented on GitHub (May 6, 2020):

@Spinnerthing i don't think the problem is spotifyd not being discoverable.
My Smartphone (fresh start or start from idle) is doing really fine with discovering the daemon on my computer :)

<!-- gh-comment-id:624558024 --> @breuerfelix commented on GitHub (May 6, 2020): @Spinnerthing i don't think the problem is spotifyd not being discoverable. My Smartphone (fresh start or start from idle) is doing really fine with discovering the daemon on my computer :)

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@Spinnerthing commented on GitHub (May 6, 2020):

@breuerfelix interesting to hear, maybe post a new bug report with that all of that relevant information if you can't find another bug relating to it?
This issue people experienced in this bug report, me included, before was not a bug.

<!-- gh-comment-id:624841079 --> @Spinnerthing commented on GitHub (May 6, 2020): @breuerfelix interesting to hear, maybe post a new bug report with that all of that relevant information if you can't find another bug relating to it? This issue people experienced in this bug report, me included, before was not a bug.

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@datkush420 commented on GitHub (May 7, 2020):

I can open the official Spotify client on any device (tablets, phones, laptops, android, ios, mac, windows, linux, etc.) and immediately see spotifyd named "rhArchLinux". Spotify-tui is the only client that can't see it. I don't see how this is an issue with spotifyd when spotify-tui is the only client having trouble seeing it.

--EDIT-- it was the spotityd config after all. The wiki said to specify an audio device to stream audio to "device = alsa_audio_device" which I had set as "pulse" but spotifyd was giving a panic "pulseaudio sink does not support specifying a device name". As soon as I removed that line it worked immediately.

Thanks for the help :)

<!-- gh-comment-id:625535843 --> @datkush420 commented on GitHub (May 7, 2020): I can open the official Spotify client on any device (tablets, phones, laptops, android, ios, mac, windows, linux, etc.) and immediately see spotifyd named "rhArchLinux". Spotify-tui is the only client that can't see it. I don't see how this is an issue with spotifyd when spotify-tui is the only client having trouble seeing it. --EDIT-- it was the spotityd config after all. The wiki said to specify an audio device to stream audio to "device = alsa_audio_device" which I had set as "pulse" but spotifyd was giving a panic "pulseaudio sink does not support specifying a device name". As soon as I removed that line it worked immediately. Thanks for the help :)

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@Spinnerthing commented on GitHub (May 8, 2020):

@datkush420 I am glad to hear it's resolved. The discovery mode of spotifyd does easily cause confusion with spotify-tui.

<!-- gh-comment-id:625876061 --> @Spinnerthing commented on GitHub (May 8, 2020): @datkush420 I am glad to hear it's resolved. The discovery mode of spotifyd does easily cause confusion with spotify-tui.

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@marcelbuesing commented on GitHub (Jun 14, 2020):

Quote from spotify API docs:

Connect Web API relies on local network connections to discover and interact with some devices.

For example, when:

• A new device is added to the network
• A device is in “sleep” mode
• A device on the local network is currently tied to another user account, or
• Other reasons specific to the device

As a result, some devices that appear in the Connect picker within the Spotify application may not always be visible or available on the Connect Web API Endpoints.

https://developer.spotify.com/documentation/web-api/guides/using-connect-web-api/

Is there some way to programmatically do the same as the Spotify clients do for network device discovery, I assume it's something related to mdns?

<!-- gh-comment-id:643819612 --> @marcelbuesing commented on GitHub (Jun 14, 2020): Quote from spotify API docs: Connect Web API relies on local network connections to discover and interact with some devices. For example, when: - A new device is added to the network - A device is in “sleep” mode - A device on the local network is currently tied to another user account, or - Other reasons specific to the device As a result, some devices that appear in the Connect picker within the Spotify application may not always be visible or available on the Connect Web API Endpoints. https://developer.spotify.com/documentation/web-api/guides/using-connect-web-api/ Is there some way to programmatically do the same as the Spotify clients do for network device discovery, I assume it's something related to mdns?

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@UdittLamba commented on GitHub (May 17, 2021):

You need a spotify client open, maybe your phone, TV or other device. Premium is necessary.

that's what spotifyd is for...

<!-- gh-comment-id:841991772 --> @UdittLamba commented on GitHub (May 17, 2021): > You need a spotify client open, maybe your phone, TV or other device. Premium is necessary. that's what spotifyd is for...

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@dxtr85 commented on GitHub (Apr 21, 2022):

I have both daemon and spotify-tui built from source.
TUI does not detect daemon, I can not even connect from my phone (daemon is seen from my phone).

dxtr@W540:/projects/spotifyd$ ./target/release/spotifyd --version
spotifyd 0.3.3
dxtr@W540:/projects/spotifyd$ ../spotify-tui/target/release/spt --version
spotify-tui 0.25.0

<!-- gh-comment-id:1104722474 --> @dxtr85 commented on GitHub (Apr 21, 2022): I have both daemon and spotify-tui built from source. TUI does not detect daemon, I can not even connect from my phone (daemon is seen from my phone). dxtr@W540:~/projects/spotifyd$ ./target/release/spotifyd --version spotifyd 0.3.3 dxtr@W540:~/projects/spotifyd$ ../spotify-tui/target/release/spt --version spotify-tui 0.25.0

kerem commented 2026-02-28 14:47:14 +03:00

Author

Owner

Copy link

@TornaxO7 commented on GitHub (Jul 3, 2022):

You need a spotify client open, maybe your phone, TV or other device. Premium is necessary.

This should be added to the README in my opinion or I was just blind.

Anyways, is it possible to hear music without having the spotify-client running?

<!-- gh-comment-id:1173056255 --> @TornaxO7 commented on GitHub (Jul 3, 2022): > You need a spotify client open, maybe your phone, TV or other device. Premium is necessary. This should be added to the README in my opinion or I was just blind. Anyways, is it possible to hear music without having the spotify-client running?

kerem commented 2026-02-28 14:47:15 +03:00

Author

Owner

Copy link

@mirachh commented on GitHub (Jan 26, 2024):

Same problem. Any solution?

<!-- gh-comment-id:1911633319 --> @mirachh commented on GitHub (Jan 26, 2024): Same problem. Any solution?

kerem commented 2026-02-28 14:47:15 +03:00

Author

Owner

Copy link

@TornaxO7 commented on GitHub (Jan 26, 2024):

@mirachh I highly recommend spotify-player since it's easier to setup and actively maintained.

<!-- gh-comment-id:1911655971 --> @TornaxO7 commented on GitHub (Jan 26, 2024): @mirachh I highly recommend [spotify-player](https://github.com/aome510/spotify-player) since it's easier to setup and actively maintained.

kerem commented 2026-02-28 14:47:15 +03:00

Author

Owner

Copy link

@mirachh commented on GitHub (Jan 26, 2024):

Thanks...

<!-- gh-comment-id:1911668877 --> @mirachh commented on GitHub (Jan 26, 2024): Thanks...

kerem commented 2026-02-28 14:47:15 +03:00

Author

Owner

Copy link

@jaketae commented on GitHub (Jan 30, 2024):

Here's something that worked for me on macOS.

1. Install spotifyd and spotify-tui
2. Set up spotifyd (documentation)
3. Start spotifyd via brew services start spotifyd
4. Run spt; spotifyd should now show up as an available device

<!-- gh-comment-id:1915877908 --> @jaketae commented on GitHub (Jan 30, 2024): Here's something that worked for me on macOS. 1. Install `spotifyd` and `spotify-tui` 2. Set up `spotifyd` ([documentation](https://docs.spotifyd.rs/config/File.html)) 3. Start `spotifyd` via `brew services start spotifyd` 4. Run `spt`; `spotifyd` should now show up as an available device

kerem referenced this issue 2026-02-28 14:50:14 +03:00

[PR #126] [MERGED] Prevent Gauge error when track progress is negative #619

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

dependabot/cargo/bumpalo-3.12.0

dependabot/cargo/serde-1.0.152

dependabot/cargo/serde_json-1.0.91

dependabot/cargo/anyhow-1.0.68

dependabot/cargo/smallvec-1.8.0

dependabot/cargo/futures-task-0.3.21

dependabot/cargo/futures-util-0.3.21

dependabot/cargo/lock_api-0.4.6

dependabot/cargo/hyper-0.13.10

dependabot/cargo/socket2-0.3.19

dependabot/cargo/nix-0.20.2

dependabot/cargo/crossterm-0.22.1

dependabot/cargo/dirs-4.0.0

dependabot/add-v2-config-file

async-await

async-await-tokio-1

echoSayonara-fork-modify-artist-window

SethGower-notifications

revert-133-page-scroll-rigel

revert-133-page-scroll

auto-redirect-code

jump-to-currently-playing-artist

move-device-cache-to-config

v0.25.0

v0.24.0

v0.23.0

v0.22.0

v0.21.0

v0.20.0

v0.19.0

v0.18.0

v0.17.1

v0.17.0

v0.16.0

v0.15.0

v0.14.0

v0.13.0

v0.12.0

v0.11.0

v0.10.0

v0.9.0

v0.8.0

v0.7.5

v0.7.4

v0.7.3

v0.7.2

v0.7.1

v0.7.0

v0.6.2

v0.6.1

v0.6.0

v0.5.0

v0.4.0

0.3.0

v0.3.0

v0.3-alpha

v0.2-alpha

0.1

Labels

Clear labels   

bug

  

enhancement

  

good first issue

  

help wanted

  

pull-request

Mirrored from GitHub Pull Request

No labels

bug

enhancement

good first issue

help wanted

pull-request

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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#125

No description provided.