spotify-tui icon indicating copy to clipboard operation
spotify-tui copied to clipboard

Api response: No device_id selected

Open taviso opened this issue 4 years ago β€’ 8 comments

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                                                                   β”‚     
     β”‚                                                                                        β”‚     
     β”‚                                                                                        β”‚     
     β”‚                                                                                        β”‚     
     β”‚                                                                                        β”‚     
     β”‚                                                                                        β”‚     
     β”‚                                                                                        β”‚     
     β”‚                                                                                        β”‚     
     β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜     

taviso avatar Dec 16 '20 05:12 taviso

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

VaskillerDev avatar Dec 19 '20 10:12 VaskillerDev

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?

pawelmhm avatar Jan 31 '21 21:01 pawelmhm

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

pablodz avatar Feb 19 '21 22:02 pablodz

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

xero-lib avatar Jul 23 '21 00:07 xero-lib

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.

demiaus avatar Feb 11 '22 22:02 demiaus

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

amarshall avatar Feb 22 '22 23:02 amarshall

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

xgenos avatar Jun 23 '22 17:06 xgenos

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

demiaus avatar Jun 27 '22 17:06 demiaus