starred/spotify-tui

Fork 0

mirror of https://github.com/Rigellute/spotify-tui.git synced 2026-04-26 08:05:57 +03:00

[GH-ISSUE #560] Spotify-tui does not initially recognise spotifyd #231

New issue

Closed

opened 2026-02-28 14:47:54 +03:00 by kerem · 6 comments

kerem commented

2026-02-28 14:47:54 +03:00

Owner

Originally created by @pujiii on GitHub (Aug 17, 2020).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/560

When i run spotifyd, spotify-tui does not list it as a device. However spotifyd is running correctly, because on my phone it is listed as a device.

When i play a song from my phone on the spotify-d device, then suddenly it appears in the device list on spotify-tui. But before that it doesn't

Originally created by @pujiii on GitHub (Aug 17, 2020). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/560 When i run spotifyd, spotify-tui does not list it as a device. However spotifyd is running correctly, because on my phone it is listed as a device. When i play a song from my phone on the spotify-d device, then suddenly it appears in the device list on spotify-tui. But before that it doesn't

kerem closed this issue

2026-02-28 14:47:54 +03:00

kerem commented

2026-02-28 14:47:55 +03:00

Author

Owner

@Peterwmoss commented on GitHub (Sep 1, 2020):

What version of spotifyd and spotify-tui are you running?

@Peterwmoss commented on GitHub (Sep 1, 2020): What version of spotifyd and spotify-tui are you running?

kerem commented

2026-02-28 14:47:55 +03:00

Author

Owner

@pujiii commented on GitHub (Sep 2, 2020):

spotify-tui 0.21.0
spotifyd 0.2.24

@pujiii commented on GitHub (Sep 2, 2020): spotify-tui 0.21.0 spotifyd 0.2.24

kerem commented

2026-02-28 14:47:55 +03:00

Author

Owner

@pujiii commented on GitHub (Sep 2, 2020):

also i saw a typo in my original post i corrected it

@pujiii commented on GitHub (Sep 2, 2020): also i saw a typo in my original post i corrected it

kerem commented

2026-02-28 14:47:55 +03:00

Author

Owner

@piotr-calus commented on GitHub (Sep 2, 2020):

When i run spotifyd, spotify-tui does not list it as a device. However spotifyd is running correctly, because on my phone it is listed as a device.

Run the spotifyd without detaching (--no-daemon) and check that configuration file is loaded correctly and the daemon is connected and authenticated. You can add --device-name for easier identification - temporary_device_name shoud be visible in spotify-tui devices list.

$ spotifyd --no-daemon --device-name temporary_device_name
Loading config from "/home/user/path/to/spotifyd.cfg"
[...]
Connecting to AP "gew1-accesspoint-b-v4hx.ap.spotify.com:443"
Authenticated as "_spotify_user_name_" !

If you do not get info about configuration file loading add the --config-path to the run command and try again.

$ spotifyd --no-daemon --config-path ~/.config/spotifyd/spotifyd.cfg

If config file is loaded but daemon is not connected/authenticated verify your config file:

cache_path (with full path, do not use ~) e.g. cache_path = /home/user/.cache/spotifyd
and/or
username and password

The <cache_path>/credentials.json file is created after (first) correct authorization.

Let us know what works / doesn't work. Good luck.

@piotr-calus commented on GitHub (Sep 2, 2020): > When i run spotifyd, spotify-tui does not list it as a device. However spotifyd is running correctly, because on my phone it is listed as a device. Run the spotifyd without detaching (_--no-daemon_) and check that configuration file is loaded correctly and the daemon is connected and authenticated. You can add _--device-name_ for easier identification - _temporary_device_name_ shoud be visible in spotify-tui devices list. ``` $ spotifyd --no-daemon --device-name temporary_device_name Loading config from "/home/user/path/to/spotifyd.cfg" [...] Connecting to AP "gew1-accesspoint-b-v4hx.ap.spotify.com:443" Authenticated as "_spotify_user_name_" ! ``` If you do not get info about configuration file loading add the `--config-path` to the run command and try again. ``` $ spotifyd --no-daemon --config-path ~/.config/spotifyd/spotifyd.cfg ``` If config file is loaded but daemon is not connected/authenticated verify your config file: - cache_path (with _full path_, do not use **~**) e.g. `cache_path = /home/user/.cache/spotifyd` and/or - username and password The _<cache_path>/credentials.json_ file is created after (first) correct authorization. Let us know what works / doesn't work. Good luck.

kerem commented

2026-02-28 14:47:55 +03:00

Author

Owner

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

Any luck @snst-p?

@Rigellute commented on GitHub (Sep 30, 2020): Any luck @snst-p?

kerem commented

2026-02-28 14:47:56 +03:00

Author

Owner

@Yazir commented on GitHub (Oct 5, 2020):

Had the same issue, config wasn't loading.

What I needed to do is to change filename of ~/.config/spotifyd/spotifyd to spotifyd.conf (default cfg path)

@Yazir commented on GitHub (Oct 5, 2020): Had the same issue, config wasn't loading. What I needed to do is to change filename of ~/.config/spotifyd/spotifyd to spotifyd.conf (default cfg path)

kerem referenced this issue

2026-02-28 14:50:28 +03:00

[PR #231] [MERGED] Fix tiny term crash #684