[GH-ISSUE #679] Api response: No device_id selected #274

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

Originally created by @taviso on GitHub (Dec 16, 2020).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/679

I'm not having any luck trying to use the 0.22.0 release. The setup worked, and it does display the track I'm currently playing in the web player.

If I press space to pause playback, that works, but if I try to continue it says Api response: No device_id selected.

Is there any way to generate a debugging log?

The full error is:

     ┌Error───────────────────────────────────────────────────────────────────────────────────┐     
     │Api response: No device_id selected                                                     │     
     │If you are trying to play a track, please check that                                    │     
     │1. You have a Spotify Premium Account                                                   │     
     │2. Your playback device is active and selected - press `d` to go to device selection    │     
     │menu                                                                                    │     
     │3. If you're using spotifyd as a playback device, your device name must not contain     │     
     │spaces                                                                                  │     
     │Hint: a playback device must be either an official spotify client or a light weight     │     
     │alternative such as spotifyd                                                            │     
     │Press <Esc> to return                                                                   │     
     │                                                                                        │     
     │                                                                                        │     
     │                                                                                        │     
     │                                                                                        │     
     │                                                                                        │     
     │                                                                                        │     
     │                                                                                        │     
     └────────────────────────────────────────────────────────────────────────────────────────┘     
Originally created by @taviso on GitHub (Dec 16, 2020). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/679 I'm not having any luck trying to use the 0.22.0 release. The setup worked, and it does display the track I'm currently playing in the web player. If I press space to pause playback, that works, but if I try to continue it says `Api response: No device_id selected`. Is there any way to generate a debugging log? The full error is: ``` ┌Error───────────────────────────────────────────────────────────────────────────────────┐ │Api response: No device_id selected │ │If you are trying to play a track, please check that │ │1. You have a Spotify Premium Account │ │2. Your playback device is active and selected - press `d` to go to device selection │ │menu │ │3. If you're using spotifyd as a playback device, your device name must not contain │ │spaces │ │Hint: a playback device must be either an official spotify client or a light weight │ │alternative such as spotifyd │ │Press <Esc> to return │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ └────────────────────────────────────────────────────────────────────────────────────────┘ ```
Author
Owner

@VaskillerDev commented on GitHub (Dec 19, 2020):

Same error in win10 with install from cargo
upd: The discussion from here helped me: https://github.com/Rigellute/spotify-tui/issues/310

<!-- gh-comment-id:748454765 --> @VaskillerDev commented on GitHub (Dec 19, 2020): Same error in win10 with install from cargo upd: The discussion from here helped me: https://github.com/Rigellute/spotify-tui/issues/310
Author
Owner

@pawelmhm commented on GitHub (Jan 31, 2021):

Encountered same thing now, and it seems this is more a documentation issue? If I understand it right, you need to have other Spotify client open at the same time? This is what fixed it for me. Otherwise Spotify web API will respond with no active devices?

I wonder if spotify-tui could register itself as a device? Would that fix this error?

<!-- gh-comment-id:770451735 --> @pawelmhm commented on GitHub (Jan 31, 2021): Encountered same thing now, and it seems this is more a documentation issue? If I understand it right, **you need to have other Spotify client open at the same time**? This is what fixed it for me. Otherwise Spotify web API will respond with no active devices? I wonder if spotify-tui could register itself as a device? Would that fix this error?
Author
Owner

@pablodz commented on GitHub (Feb 19, 2021):

#14
Need to have an client opened, TUI controls that client opened

<!-- gh-comment-id:782424840 --> @pablodz commented on GitHub (Feb 19, 2021): #14 Need to have an client opened, TUI controls that client opened
Author
Owner

@xero-lib commented on GitHub (Jul 23, 2021):

Same issue, running spotifyd as client. I have premium.

<!-- gh-comment-id:885316275 --> @xero-lib commented on GitHub (Jul 23, 2021): Same issue, running spotifyd as client. I have premium.
Author
Owner

@quunnb commented on GitHub (Feb 11, 2022):

Same issue, running spotifyd as client. I have premium.

Same specs, my workaround has been to restart spotifyd
systemctl --user restart spotifyd

and stick alias spt="systemctl --user restart spotifyd && spt" into .bash_aliases or such.

<!-- gh-comment-id:1036720154 --> @quunnb commented on GitHub (Feb 11, 2022): > Same issue, running spotifyd as client. I have premium. Same specs, my workaround has been to restart spotifyd `systemctl --user restart spotifyd` and stick `alias spt="systemctl --user restart spotifyd && spt"` into .bash_aliases or such.
Author
Owner

@amarshall commented on GitHub (Feb 22, 2022):

This occurred for me as a result of https://github.com/Rigellute/spotify-tui/issues/579.

<!-- gh-comment-id:1048302043 --> @amarshall commented on GitHub (Feb 22, 2022): This occurred for me as a result of https://github.com/Rigellute/spotify-tui/issues/579.
Author
Owner

@xgenos commented on GitHub (Jun 23, 2022):

Same issue, running spotifyd as client. I have premium.

Same specs, my workaround has been to restart spotifyd systemctl --user restart spotifyd

and stick alias spt="systemctl --user restart spotifyd && spt" into .bash_aliases or such.

it says that you dont have any spotifyd.service exist

<!-- gh-comment-id:1164674104 --> @xgenos commented on GitHub (Jun 23, 2022): > > Same issue, running spotifyd as client. I have premium. > > Same specs, my workaround has been to restart spotifyd `systemctl --user restart spotifyd` > > and stick `alias spt="systemctl --user restart spotifyd && spt"` into .bash_aliases or such. it says that you dont have any spotifyd.service exist
Author
Owner

@quunnb commented on GitHub (Jun 27, 2022):

Same issue, running spotifyd as client. I have premium.

Same specs, my workaround has been to restart spotifyd systemctl --user restart spotifyd
and stick alias spt="systemctl --user restart spotifyd && spt" into .bash_aliases or such.

it says that you dont have any spotifyd.service exist

You need to install spotifyd and enable it as systemd-service

<!-- gh-comment-id:1167667094 --> @quunnb commented on GitHub (Jun 27, 2022): > > > Same issue, running spotifyd as client. I have premium. > > > > > > Same specs, my workaround has been to restart spotifyd `systemctl --user restart spotifyd` > > and stick `alias spt="systemctl --user restart spotifyd && spt"` into .bash_aliases or such. > > it says that you dont have any spotifyd.service exist You need to install [spotifyd](https://github.com/Spotifyd/spotifyd) and [enable it as systemd-service](https://spotifyd.github.io/spotifyd/config/services/Sytemd.html)
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#274
No description provided.