Announce: Spotify Premium Plugin (Beta)

[fmahia]

Spotify plugin V2.2.7 doesn't work for me with a Windows 7 Squeezeplay:

Helper App Running PASS
Logged In PASS
Spotify Metadata OK PASS
Streaming from Spotify OK PASS
Unable to authenticate player FAIL
Helper app unable to authenticate player (error: -5)

Logs ok until:
[12:21:28.164] check_player:253 player address mismatch 192.168.0.1 169.254.90.207
[12:21:28.164] main:785 unable to play on this player: -5

Firewall rules are ok
LMS 7.7.2 on the same PC

Any idea to make it work?

[Triode]

Spotify plugin V2.2.7 doesn't work for me with a Windows 7 Squeezeplay:

Helper App Running PASS
Logged In PASS
Spotify Metadata OK PASS
Streaming from Spotify OK PASS
Unable to authenticate player FAIL
Helper app unable to authenticate player (error: -5)

Logs ok until:
[12:21:28.164] check_player:253 player address mismatch 192.168.0.1 169.254.90.207
[12:21:28.164] main:785 unable to play on this player: -5

Firewall rules are ok
LMS 7.7.2 on the same PC

Any idea to make it work?

Can you identify where the two IP addresses are - the plugin requires the player to connect using the source IP address that LMS knows it as. It looks like this is not the case for you - are you using NAT?

[AndrewFG]

[12:21:28.164] check_player:253 player address mismatch 192.168.0.1 169.254.90.207

Can you identify where the two IP addresses are - ... - are you using NAT?

The 169.254.xxx.yyy IP block is the range reserved for AutoIP (see http://tools.ietf.org/html/rfc3927 ) - AutoIP is used by PC (Windows) clients to assign themselves an IP address if they are not able to get an address from a DHCP server. Probably this means that either the OP's client has had its DHCP disabled, or that his Gateway/Router is not running a DHCP server; but it might be a one time drop out, so try resetting the NIC (or rebooting the PC) since this may be sufficient to force it to grab an address via DHCP...

[fmahia]

Thank you very much, I've found the problem: it was a virtual network card "PdaNet Modem" which was defined as "default connexion". No problem without it.

Thanks a lot.

[ceterisparibus]

This sounds related to the firewall not the spotify plugin as that output from the self test is what I would expect when there is no network access from the player to the helper app. Is there a way to delay the loading of the LMS service - is it possible that it needs the firewall to be loaded first?

Edit: instead of reinstalling the plugin, could you test with changing one of the settings such as bitrate or volume normaisation? This will case the helper app to be restarted - if this fixes the problem, then I think the issue is starting the helper app before the firewall is ready and it may be possible to delay the initial start of the helper app.

Thanks Triode.

I tried changing bitrate and normalization, applying, and attempting to play something several times - same results.

Additionally, I've attempted to kill the spotifyd process (it pops right back up under a different pid without me needing to restart it) and unplugging/plugging one of the players to reestablish a connection to the LMS server - the only thing I've found that works is restarting LMS.

By the way, this is on Ubuntu 12.04 LTS and my iptables are currently empty (below).

~$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

[Triode]

Thanks Triode.

I tried changing bitrate and normalization, applying, and attempting to play something several times - same results.

Additionally, I've attempted to kill the spotifyd process (it pops right back up under a different pid without me needing to restart it) and unplugging/plugging one of the players to reestablish a connection to the LMS server - the only thing I've found that works is restarting LMS.

By the way, this is on Ubuntu 12.04 LTS and my iptables are currently empty (below).

~$ sudo iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

What happens if you change the http port number in the plugin settings? This is a problem which is specific to your machine, its worth checking what else is running at startup and what is using each port. Try telnetting to the helper app port from the local machine and a remote machine to prove that it is working and reachable.

[ceterisparibus]

What happens if you change the http port number in the plugin settings? This is a problem which is specific to your machine, its worth checking what else is running at startup and what is using each port. Try telnetting to the helper app port from the local machine and a remote machine to prove that it is working and reachable.

Same thing with the helper app on a different port.
nmap shows port 9000 listening but not 9005 (that's true before and after LMS restart).
Telnet to 9000 works, Telnet to 9005 works but connection gets closed almost right after opening ("Connection closed by foreign host."). Same behavior before/after LMS restart so I don't think it's significant (since the plugin does work after LMS restart).

The only other thing that occurs to me is the machine has dual ethernet - eth0 is plugged in, eth1 is not. But, again, after LMS restart - everything works.

It's a pretty fresh install so there's not tons of stuff installed but I was considering reinstalling for partitioning reasons anyway. I've got a workaround at the moment and I'll report back after I get around to reinstalling in the next week or two and let you know if it's working directly after a fresh install + LMS before anything else gets thrown into the equation.

Thanks again for your help and for making the SBs that much more awesome!

[Triode]

Same thing with the helper app on a different port.
nmap shows port 9000 listening but not 9005 (that's true before and after LMS restart).
Telnet to 9000 works, Telnet to 9005 works but connection gets closed almost right after opening ("Connection closed by foreign host."). Same behavior before/after LMS restart so I don't think it's significant (since the plugin does work after LMS restart).

The only other thing that occurs to me is the machine has dual ethernet - eth0 is plugged in, eth1 is not. But, again, after LMS restart - everything works.

It's a pretty fresh install so there's not tons of stuff installed but I was considering reinstalling for partitioning reasons anyway. I've got a workaround at the moment and I'll report back after I get around to reinstalling in the next week or two and let you know if it's working directly after a fresh install + LMS before anything else gets thrown into the equation.

Thanks again for your help and for making the SBs that much more awesome!

Sounds strange. Let us know what you learn.

[mo5265654]

Hi,

I just signed up for a premium Spotify account to try on my Squeezebox system (Touch and Radio). Works like a charm now.

Thought I would share one problem I had though: After installing and restarting the server, the self-test of the plug-in said streaming from Spotify did not work. Some searching the net brought some tips for checking: (a) is spotifyd running => no was not (b) try to start by hand => not succesfull, said port 9005 was already used. So I changed to 9015 and ... voila, self-test successful, first "real" test using Squeezeplay also worked and then as expected worked also in the real system.

Thanks Triode for a very excellent plugin!!!

And of course controlling this using Squeezecommander from my Android devices makes this even better. Strongly recommended as well.

Thanks,
Mo

[oivindi]

I've had the Spotify plug-in working on and off, but I always end up with a non-working plug-in sooner rather than later. Now it's stopped working again. I am running the latest version (2.2.7) on Logitech Media Server 7.8 (beta). I used to run 7.7 until recently, but after having some problems, I decided to reinstall everything.

However, still no luck with the 3rd party Spotify plug-in. Running the self-test, everything but streaming to the player (a Squeezebox Boom) works. The player fails to authenticate. I have turned off the firewall completely on the machine running the server, but that didn't affect anything. Also, from the log I can't understand this line:

"check_player:169 unable to create cli connection to 127.0.0.1:9090"

Where is this address coming from? Why 9090? Also, I have tried other helper ports than 9005, but that didn't change anything. I am using 9001 as the default port for LMS.

Any help/ideas?

Log is included.