Spotify Connect Web

**awiouy** · November 29, 2016 at 9:32 AM Official Post

Check its content, name and location. According to your logs and scw github issues, it could be that app key is invalid.

Pansky · November 29, 2016 at 6:10 PM

Hi,
first thanks for that addon but i have a problem.
I installed the addon from the repo after that i put my spotify_appkey.key in the folder.
But when i try to configure ALSA with the wizzard only the message "Could not find a playback device" pop up.

Code

-- Logs begin at Sun 2016-11-20 12:10:08 CET, end at Tue 2016-11-29 19:02:24 CET
. --
Nov 20 12:10:11 LibreELEC systemd[1]: Started spotify-connect-web.
Nov 20 12:10:11 LibreELEC sh[433]: Playback device not set

I hope u can help me

**awiouy** · November 29, 2016 at 6:12 PM Official Post

Pansky,

On what are you running on (hw + le release). Any idea of the sound device you use?

Pansky · November 29, 2016 at 6:35 PM

Quote from awiouy

Pansky,

On what are you running on (hw + le release). Any idea of the sound device you use?

Wow that was fast,
i use a RPI 2 with KODI 17 Millhouse Build with no extra device.

**awiouy** · November 29, 2016 at 6:46 PM Official Post

Hm... weird
Try this command at the console and then try again:
dtparam audio=on

If that does not work, try adding the following line to config.txt, reboot and retry:
dtparam=audio=on

If that does not work, try vanilla LE

Pansky · November 29, 2016 at 7:30 PM

Quote from awiouy

Hm... weird
Try this command at the console and then try again:
dtparam audio=on

If that does not work, try adding the following line to config.txt, reboot and retry:
dtparam=audio=on

If that does not work, try vanilla LE

dtparam=audio=on fixed my problem thank you!

i got now 2 devices, HDMI and audio jack or?

Danmann · November 29, 2016 at 7:51 PM

Quote from awiouy

Check its content, name and location. According to your logs and scw github issues, it could be that app key is invalid.

Thanks.

But I can't find in the "28 issues" any problems like this, on github.

Edit:
I have 4 options in my email from spotify.
HEX/BASE16 APPKEY
BASE64 APPKEY
BINARY APPKEY
C APPKEY

Under these options are a lot of "words" Maybe i can do something with this stuff?

Well, and the spotify_app.key from spotify, as well.

**awiouy** · November 29, 2016 at 8:51 PM Official Post

Quote from Danmann

Thanks.

But I can't find in the "28 issues" any problems like this, on github.

Edit:
I have 4 options in my email from spotify.
HEX/BASE16 APPKEY
BASE64 APPKEY
BINARY APPKEY
C APPKEY

Under these options are a lot of "words" Maybe i can do something with this stuff?

Well, and the spotify_app.key from spotify, as well.

See post #147 and upwards. Can't test myself (no key e-mail). Maybe see with effe.rnr how he got his key working. If you manage, please be so kind to document in this thread, for other users. Tia
[hr]

Quote from Pansky

dtparam=audio=on fixed my problem thank you!

i got now 2 devices, HDMI and audio jack or?

Sounds familiar: use ALSA and PCM, select the desired output HDMI or jack

lollo78 · November 29, 2016 at 9:19 PM

Hi, I received the email with the .key file in attached, but it doesn't work. I can't see the rpi3 libreelec 7.0.2 from the Spotify app.

I can't check the .Key content because the text inside is "compiled". I suppose that it is the binary file.

The previous page
Libspotify Application Keys - Spotify Developer
used to download the personal Keys does't work anymore.
So the email is the only source.

Another question, It's not clear (at least for me) how to check the 4000 port.
I type in my browser (in the same LAN of rpi3) 192.268.1.86:4000 (.86 is my rpi3) but the page is blank (ERR_CONNECTION_REFUSED)

Any help, please?

**awiouy** · November 29, 2016 at 9:25 PM Official Post

Quote from lollo78

Hi, I received the email with the .key file in attached, but it doesn't work. I can't see the rpi3 libreelec 7.0.2 from the Spotify app.

I can't check the .Key content because the text inside is "compiled". I suppose that it is the binary file.

The previous page
Libspotify Application Keys - Spotify Developer
used to download the personal Keys does't work anymore.
So the email is the only source.

Another question, It's not clear (at least for me) how to check the 4000 port.
I type in my browser (in the same LAN of rpi3) 192.268.1.86:4000 (.86 is my rpi3) but the page is blank (ERR_CONNECTION_REFUSED)

Any help, please?

According to post #147 and previous, some info from the key email must be processed to generate the app key. I can't test this, because I have no key email. If the key is not valid, the service (and its web ui) will fail.

lollo78 · November 29, 2016 at 11:02 PM

Hi, solved.
It's not an issue of base64 decode. We can use directly the .Key file attached in the email. In my case the issue is that I didn't use the alsa configurazione wizard.
After doing that, all works fine.
Yes I know... I'm a dork

I really love this addon. Thank for all

**awiouy** · November 29, 2016 at 11:04 PM Official Post

Quote from lollo78

Hi, solved.
It's not an issue of base64 decode. We can use directly the .Key file attached in the email. In my case the issue is that I didn't use the alsa configurazione wizard.
After doing that, all works fine.
Yes I know... I'm a dork

I really love this addon. Thank for all

Great! Thank you for the feedback!

effe.rnr · November 30, 2016 at 11:56 PM

Quote from Danmann

Thanks.

But I can't find in the "28 issues" any problems like this, on github.

Edit:
I have 4 options in my email from spotify.
HEX/BASE16 APPKEY
BASE64 APPKEY
BINARY APPKEY
C APPKEY

Under these options are a lot of "words" Maybe i can do something with this stuff?

Well, and the spotify_app.key from spotify, as well.

you can generate your app key by doing the following steps:

1. open Base64 Online - base64 decode and encode
2. paste your key in the into the field
3. select decode and "to binary file"
4. save the binary file. With this file it should work

tehzaz · December 2, 2016 at 3:12 PM

Quote from lollo78

Another question, It's not clear (at least for me) how to check the 4000 port.

For information : With SSH in LibreElec, you can type :

Code

netstat -taupen | grep 4000

If the service is working, you should see something like :

Code

tcp        0      0 0.0.0.0:4000            0.0.0.0:*               LISTEN      593/spotify-connect

If nothing appears, something is wrong.

Danmann · December 4, 2016 at 2:23 AM

Quote from effe.rnr

you can generate your app key by doing the following steps:

1. open Base64 Online - base64 decode and encode
2. paste your key in the into the field
3. select decode and "to binary file"
4. save the binary file. With this file it should work

Thank you,

but it doesn't work for me.

I think my key isn't made for any acc. Just a "test-key" maybe.

Code

LibreELEC:~ # spotify-connect-web.start
Simple mixer control 'PCM',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback -10239 - 400
  Mono: Playback -1727 [80%] [-17.27dB] [on]
numid=3,iface=MIXER,name='PCM Playback Route'
  ; type=INTEGER,access=rw------,values=1,min=0,max=2,step=0
  : values=0
Loading Spotify library...
Established under name 'TestConnect'
min_volume_range: 0.0
Using libspotify_embedded version: release-esdk-1.20.0-v1.20.0-g594175d4
SpInit: 5
SpInit failed, exiting

Display More

Do you guys see you're acc name at this place? ....Established under name 'TestConnect'.....

I tried to put just the "BASE64 APPKEY" text which is written in the email, as well. But same problem. So i don't know.

effe.rnr · December 4, 2016 at 2:58 PM

Quote from Danmann
Thank you,

but it doesn't work for me.

I think my key isn't made for any acc. Just a "test-key" maybe.
Code
LibreELEC:~ # spotify-connect-web.start
Simple mixer control 'PCM',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback -10239 - 400
  Mono: Playback -1727 [80%] [-17.27dB] [on]
numid=3,iface=MIXER,name='PCM Playback Route'
  ; type=INTEGER,access=rw------,values=1,min=0,max=2,step=0
  : values=0
Loading Spotify library...
Established under name 'TestConnect'
min_volume_range: 0.0
Using libspotify_embedded version: release-esdk-1.20.0-v1.20.0-g594175d4
SpInit: 5
SpInit failed, exiting
Display More
Do you guys see you're acc name at this place? ....Established under name 'TestConnect'.....

I tried to put just the "BASE64 APPKEY" text which is written in the email, as well. But same problem. So i don't know.

I have this name too

lollo78 · December 4, 2016 at 9:00 PM

Quote from Danmann
Thank you,

but it doesn't work for me.

I think my key isn't made for any acc. Just a "test-key" maybe.
Code
LibreELEC:~ # spotify-connect-web.start
Simple mixer control 'PCM',0
  Capabilities: pvolume pvolume-joined pswitch pswitch-joined
  Playback channels: Mono
  Limits: Playback -10239 - 400
  Mono: Playback -1727 [80%] [-17.27dB] [on]
numid=3,iface=MIXER,name='PCM Playback Route'
  ; type=INTEGER,access=rw------,values=1,min=0,max=2,step=0
  : values=0
Loading Spotify library...
Established under name 'TestConnect'
min_volume_range: 0.0
Using libspotify_embedded version: release-esdk-1.20.0-v1.20.0-g594175d4
SpInit: 5
SpInit failed, exiting
Display More
Do you guys see you're acc name at this place? ....Established under name 'TestConnect'.....

I tried to put just the "BASE64 APPKEY" text which is written in the email, as well. But same problem. So i don't know.

Copy the .Key file, attached in the spotify email, in the right folder, after go inside the addon config: set your login info and use the alsa wizard. After do this all works fine for me. If you don't do this the local server on 4000 port will not work.

Danmann · December 11, 2016 at 6:37 AM

Hi,

Thanks to everyone.

I don't know why but it's working now.

I just installed the connect web again. But I did it before, too. So yeah, I don't know.

Thanks.

Similar Threads

Spotify Connect