PDA

View Full Version : [Announce] Spotty 2.0.0 - Spotify Connect for your Squeezebox



Pages : [1] 2 3 4

mherger
2018-01-13, 04:22
Now with Windows support - at last!

As otherwise this is basically the same as 1.99.x with improved Windows support, I'll re-post the announcement :-).

Except for how to enable the feature. Read all of this announcement to get things working!


Control Spotify playback on your Squeezebox using Spotify's applications (desktop, mobile)
Get access to (some of - see below) the Spotify content which is not available through their API yet, thus can't be accessed through the plugin
Transfer Spotify playback from your office Squeezebox to your phone to your car to your phone to your home Squeezebox


It's a bit of a hack, but it seems to be working reasonably well. So here's the list of open issues and limitations I'm aware of:


For whatever reason Spotify would not allow me to play Podcasts to Spotty
Squeezebox would show the next track's metadata 5-10s before it actually starts playing (whil the previous track was still active)
Spotify's limitations apply: if you play music to your Squeezebox using Connect, you cannot listen to Spotify on your phone or any other Spotify Connect endpoint.
Doesn't work with password protection on LMS.


If you want to give Spotty Connect a try, go to the LMS web UI, Settings/Player/Spotty, and enable the feature for the device(s) you want. Please note that every activated player will launch a daemon in the background. Be careful if you run LMS on a NAS with 256MB or even less...

PS: NAS devices known to be compatible or not with Spotty at this point:

Synology: check out your model in the CPU architecture overview (http://www.synology-wiki.de/index.php/Welchen_Prozessortyp_besitzt_mein_System%3F). If it's in the Intel x86-*, or armv7 section, then you're fine. Make sure you're running the latest DSM and LMSRepack (http://forums.slimdevices.com/showthread.php?107180-Synology-7-9-1-packages&highlight=lmsrepack) or LMSUpdate. Otherwise I'm sorry.
ReadyNAS: The old Sparc based devices (Duo, NV), as well as their ARMv5 based successors (Duo v2, NV v2) will not work. On newer models you might need to manually install IO::Socket::SSL (http://forums.slimdevices.com/showthread.php?107615-Announce-Spotty-v1-1-0&p=889635#post889635).
QNAP: similarly to Synology there are many different models. Unfortunately I haven't found a good overview (https://eu1.qnap.com/Storage/TechnicalDocument/20140618-QNAP_Turbo_NAS_Hardware_Manual_ENG.pdf). If you're on Intel, then you should be fine. ARM - depends on what exact model. You, too, might need to install IO::Socket::SSL (http://forums.slimdevices.com/showthread.php?107615-Announce-Spotty-v1-1-0&p=890362&viewfull=1#post890362)

Simon_rb
2018-01-13, 05:33
Excellent.. Have you managed to find a way of Spotty playing on the selected player rather than the last player/current player that is on? For example...

If the Dining Room Radio is on and I select Kitchen Radio then it will play on the Dining Room Radio even though it shows its playing on Kitchen Radio on the Spotify app. My players are sync'd so I don't know if that causes issues?

Other than above it has been super stable and well chuffed with it

Cheers

ButC
2018-01-13, 06:44
A quick test gives an impressive improvement :) Seems super stable and everything just works - skip, volume, switching between playlists. Amazing!

maddymarc
2018-01-13, 08:11
I updated to 2.0 and enabled my piCore server in the Spotify mobile app. So the API app works in LMS.
But when I try to enable a player, the mobile app doesn't give it as an option. What am I missing? I've tried restarting LMS after applying the enable checkbox, restarting with the checkbox empty... can't get Spotify to show my players as options.
Thanks for your continued excellent work for LMS, Michael.

mherger
2018-01-13, 08:22
> A quick test gives an impressive improvement :) Seems super stable and
> everything just works - skip, volume, switching between playlists.
> Amazing!

If you're on Windows, then I'd say this is the first version which
actually works... I'm glad you can confirm.

--

Michael

maddymarc
2018-01-13, 15:00
can't get Spotify to show my players as options.

I used the web player instead and added players to Connect. All working now.

Nomen Nescio
2018-01-14, 02:21
tnx again Michael for this great work!

Seems to work great. All my boxes are sync'ed so hoping for the best.
Three family accounts.
LMS on Windows 10 (as a server)

ButC
2018-01-14, 03:34
If you're on Windows, then I'd say this is the first version which
actually works... I'm glad you can confirm.

--

Michael

Indeed.

I noticed that after having turned my Touch off and when turning it on and resuming play, the last played song of the playlist keeps repeating itself infinetely. "Squeezelite" (the player that was selected for the playlist) is also then no longer a selectable device. Exiting the Spotify app on the phone and entering again seems to solve the problem.

This isn't a huge problem but I thought I'd mention it.

24394

Nomen Nescio
2018-01-14, 04:26
tnx again Michael for this great work!

Seems to work great. All my boxes are sync'ed so hoping for the best.
Three family accounts.
LMS on Windows 10 (as a server)

Something goes wrong. Just one number from a playlist like daily mix or easy 80's is playing over and over.

jasell
2018-01-14, 04:26
Great work!
I loved to see the how you continue to refine this awesome feature of LMS!

A minor detail, on my SB3 I use MIS to show details about the now playing song.
I wish to show PLAYTIME / SONGTIME but SONGTIME is always 0:00 when playing from spotify (Spotify app+connect or Spotty in LMS)

PS. Are we supposed to move our discussion over to this thread, from previous 1.9.0 thread?
-I now see two parallel threads being active...

DigitalMitch
2018-01-14, 04:28
Michael,

I have tried the latest and previous versions with LMS running on Windows Home Server (Service Pack 2 - AMD Sempron 3400+ 1.8Ghz, 1.96GB of RAM)
LMS fails to restart each time. I then have to remove it from the server and reinstall to get LMS back.

Is this a limitation with Spotty (and/or Connect) or perhaps an issue with my setup?
Does anyone have Spotty working on WHS?

The logfile shows the esmae single line for both the successful restart (without spotty at 11:01) and the faile done (with Spotty at 11:08)

[18-01-14 11:01:09.4258] main::init (387) Starting Logitech Media Server (v7.9.1, 1515659378, Thu Jan 11 09:03:00 CUT 2018) perl 5.014001 - MSWin32-x86-multi-thread
[18-01-14 11:08:23.3633] main::init (387) Starting Logitech Media Server (v7.9.1, 1515659378, Thu Jan 11 09:03:00 CUT 2018) perl 5.014001 - MSWin32-x86-multi-thread

I have it working from my laptop (but that's no good for family, when I'm out).

Mitch

jasell
2018-01-14, 06:17
I have problem using Connect with multiple user accounts, it plays the wrong song...

If the player has be used with another Spotify account before and I start a new playing session using Spotify Connect then the player is not visible in my Spotify device list for the new Spotify account.
This is as before, I assume, and is managed by using the Spotty app in LMS by playing a song with the new Spotify account. This make the player show up in the Spotify Connect Devices.
-It would be easier if all players show up for all users and any one who starts a Spotify connect session highjacks the player.

The main problem is:
when playing a song to the player, it starts to play a timely manner, but the wrong song! The songs that is played is the last one from the previous session, which is then repeated.

I tried several "tricks" to get rid of the "previously played song" like restarting LMS, switching Spotty Connect option on/off etc.
I found that when playing on the desired player using Spotty in LMS on the new Spotify account, then high-jacking the player with the Spotify App by starting session using Spotify connect, with the same Spotify account, managed to switch the player to the new account and play the correct song.

Blue Fishey
2018-01-14, 09:57
Hi

Using windows :)

Yes stable

The only 2 issues thus far, if you skip a rack then the now playing changes, but if you leave it to play through list it doesnt, the music does change

Also the visuals on the player seem out of step with the track playing

keep it up mate !

Blue

Nomen Nescio
2018-01-14, 10:23
Hi

Using windows :)

Yes stable

The only 2 issues thus far, if you skip a rack then the now playing changes, but if you leave it to play through list it doesnt, the music does change

Also the visuals on the player seem out of step with the track playing

keep it up mate !

Blue

You have no endless repeating song? Has to be something wrong with my settings then.

slartibartfast
2018-01-14, 11:34
You have no endless repeating song? Has to be something wrong with my settings then.If you only had one song in the playlist it would repeat endlessly.

Sent from my SM-G900F using Tapatalk

Nomen Nescio
2018-01-14, 12:27
If you only had one song in the playlist it would repeat endlessly.

Sent from my SM-G900F using Tapatalk

I had a playlist selected from spotify (easy on sunday) in the Chome webplayer and on Android. On Android only the first song was played over and over. The webplayer just played one song.
Tried again on Windows 10 app and now it's playing ok (4th number allready). ;)

slartibartfast
2018-01-14, 12:34
I had a playlist selected from spotify (easy on sunday).I have seen this happen to me when playing albums from Spotify but not recently. How frequently does it occur?

Sent from my SM-G900F using Tapatalk

Nomen Nescio
2018-01-14, 12:46
I have seen this happen to me when playing albums from Spotify but not recently. How frequently does it occur?

Sent from my SM-G900F using Tapatalk

First day on 2.0.0 with connect because LMS on Windows.

bigsur78
2018-01-14, 13:46
I've updated everything... Max2play 2.45, LMS 7.9.1 and Spotty 2.0
Still for some reason I can search for music and see results on Spotty, but when I play a song, it plays for about 4 seconds with no sound, then skips to the next track. Same thing on the next track, and so on.
Can anyone help? I want to get this working so badly!
Thanks
b

Blue Fishey
2018-01-14, 13:50
You have no endless repeating song? Has to be something wrong with my settings then.

no mate all ok here, Iphone for spotify and softsqueeze for test with

mherger
2018-01-14, 13:56
> If the Dining Room Radio is on and I select Kitchen Radio then it will
> play on the Dining Room Radio even though it shows its playing on
> Kitchen Radio on the Spotify app. My players are sync'd so I don't know
> if that causes issues?

Synced players certainly provide an additional level of confusion. I
think I never tried that with Connect myself...

--

Michael

mherger
2018-01-14, 13:58
> I have tried the latest and previous versions with LMS running on
> Windows Home Server (Service Pack 2 - AMD Sempron 3400+ 1.8Ghz, 1.96GB
> of RAM)

If this is Windows Home Server v1, then I'm sorry, Spotty will not work.
If not, you might want to check out the server.log to get us some
information about the failure.

--

Michael

mherger
2018-01-14, 14:01
> I have problem using Connect with multiple user accounts, it plays the
> wrong song...

The multiple user scenario is still a bit confusing, and not satisfying.
You have to make sure that the player you want to target last had been
used with your account, and not somebody else's.

> -It would be easier if all players show up for all users and any one who
> starts a Spotify connect session highjacks the player.

Unfortunately this is a bit more complicated than I thought. LMS doesn't
know from which account a request came when it's told to play some
Spotify content. I'll have to figure out a manual way (like polling all
accounts...) to make this happen.

--

Michael

mherger
2018-01-14, 14:02
> The only 2 issues thus far, if you skip a rack then the now playing
> changes, but if you leave it to play through list it doesnt, the music
> does change
>
> Also the visuals on the player seem out of step with the track playing

What kind of player?

--

Michael

mherger
2018-01-14, 14:04
> A minor detail, on my SB3 I use MIS to show details about the now
> playing song.
> I wish to show PLAYTIME / SONGTIME but SONGTIME is always 0:00 when
> playing from spotify (Spotify app+connect or Spotty in LMS)

I finally have to dig that issue a bit deeper. Thanks for the reminder!

> PS. Are we supposed to move our discussion over to this thread, from
> previous 1.9.0 thread?
> -I now see two parallel threads being active...

We can certainly continue on the existing thread. But anything new or
2.0 specific should be reported here.


--

Michael

slartibartfast
2018-01-14, 14:18
First day on 2.0.0 with connect because LMS on Windows.Does it happen every time you play a playlist?

Sent from my SM-G900F using Tapatalk

Blue Fishey
2018-01-14, 14:50
> The only 2 issues thus far, if you skip a rack then the now playing
> changes, but if you leave it to play through list it doesnt, the music
> does change
>
> Also the visuals on the player seem out of step with the track playing

What kind of player?

--

Michael

testing with softsqueeze but will try my transporter

Blue

Shozzer
2018-01-14, 16:06
Working fine for me so far. Thanks very much Michael for this and all you do for us.

mherger
2018-01-14, 22:42
> testing with softsqueeze but will try my transporter

Ok, that would confirm the issues people have been reporting with the
"classic" display. Will investigate.

--

Michael

mherger
2018-01-14, 22:51
> I noticed that after having turned my Touch off and when turning it on
> and resuming play, the last played song of the playlist keeps repeating
> itself infinetely. "Squeezelite" (the player that was selected for the
> playlist) is also then no longer a selectable device. Exiting the
> Spotify app on the phone and entering again seems to solve the problem.

The daemon sometimes still crashes, but should be re-started
automatically. But it can take some time before the Spotify client
applications pick up that change.

--

Michael

ButC
2018-01-14, 23:47
The daemon sometimes still crashes, but should be re-started
automatically. But it can take some time before the Spotify client
applications pick up that change.

--

Michael

Yes, it seems sometimes it takes quite a bit longer for the Daemon to restart and sometimes it is done rather quickly. But as it is now, it's not a big problem. The overall feeling is a really stable and well working Connect on Windows installations :) Thanks!

mherger
2018-01-15, 04:18
> A minor detail, on my SB3 I use MIS to show details about the now
> playing song.
> I wish to show PLAYTIME / SONGTIME but SONGTIME is always 0:00 when
> playing from spotify (Spotify app+connect or Spotty in LMS)

MIS 4.4.12 should fix this. I'm surprised this only showed up now, as I
would have expected the same result for many streaming services. Didn't
you see this with other services, too? It must have been around for years...

--

Michael

ncameron
2018-01-15, 10:49
Thanks for this Michael; excellent.

By far not the worst thing about all this is being able to control the music coming out of my home Hi-Fi system by my Apple Watch, via Connect on my iPhone! :)

jasell
2018-01-15, 10:53
>
MIS 4.4.12 should fix this. I'm surprised this only showed up now, as I
would have expected the same result for many streaming services. Didn't
you see this with other services, too? It must have been around for years...

--

Michael
Thanks!
Just using Spotify and my local archive, didn’t considered it to be top priority for spotty, but it has been there for awhile.
//Jakob



Sent from my iPad using Tapatalk

jasell
2018-01-15, 13:24
I noticed that I have several Spotty processes running on my Qnap, I have 5 or more but only 4 players that have Spotty enabled, is this correct?
How many spotty processes should there be compared to the numbered of Spotty enabled players?

mherger
2018-01-15, 13:33
> How many spotty processes should there be compared to the numbered of
> Spotty enabled players?

Please take a seat... one per Connect enabled player, plus one for every
playing device. Sums up to twice the number of players if all are
playing and Connect enabled.

And add one if you are in the process of authenticating :-)

Please make sure you have the latest 2.0.x running, as previous versions
had a bug which would leave instances running while re-starting new ones
all the time.

--

Michael

Blue Fishey
2018-01-16, 03:21
yeps works super cool on my Transporter :)

Well Done mate

pery
2018-01-16, 11:25
After trying on a temporary server I finally dared to install it on my Ready-NAS.

Thank you for good work!

/Per

jasell
2018-01-16, 14:39
> A minor detail, on my SB3 I use MIS to show details about the now
> playing song.
> I wish to show PLAYTIME / SONGTIME but SONGTIME is always 0:00 when
> playing from spotify (Spotify app+connect or Spotty in LMS)

MIS 4.4.12 should fix this. I'm surprised this only showed up now, as I
would have expected the same result for many streaming services. Didn't
you see this with other services, too? It must have been around for years...

--

Michael
is MIS 4.4.12 released? My LMS only see MIS 4.4.11

mherger
2018-01-16, 22:20
> is MIS 4.4.12 released? My LMS only see MIS 4.4.11

Yes, it is. I do see it in the repository file:

http://svn.slimdevices.com/repos/slim/vendor/plugins/repo.xml

--

Michael

ButC
2018-01-17, 00:19
i've had a few spontaneous stops when using Connect on a Windows server. In the attached log near the middle of Cranberries Zombie, for example. There has never been any problem resuming by pressing play.


24406

mherger
2018-01-17, 00:36
Am 17.01.18 um 08:19 schrieb ButC:
>
> i've had a few spontaneous stops when using Connect on a Windows server.
> In the attached log near the middle of Cranberries Zombie, for example.
> There has never been any problem resuming by pressing play.

Unfortunately there's nothing Spotty specific in that log file. You'd
have to set plugin.spotty to INFO to get more information.

--

Michael

Raymond Woodward
2018-01-17, 00:37
i've had a few spontaneous stops

Can't say I've had that, but on a couple of occasions I've had it stop at the end of a track when running playlist - having to press 'play' to start the next track on the list...

--

Ray

Windows 10 Home 16299.192

LMS 7.91 (current release)

TomAmes
2018-01-18, 08:50
Can't say I've had that, but on a couple of occasions I've had it stop at the end of a track when running playlist - having to press 'play' to start the next track on the list...

--

Ray

Windows 10 Home 16299.192

LMS 7.91 (current release)

Same here. Also on Windows 10 Home & LMS 7.9.1

slartibartfast
2018-01-18, 08:59
Same here. Also on Windows 10 Home & LMS 7.9.1I have seen the same but on Linux so it isn't specific to Windows.

Sent from my SM-G900F using Tapatalk

Rheinländer
2018-01-18, 10:36
I have seen the same but on Linux so it isn't specific to Windows.

Sent from my SM-G900F using Tapatalk

I can confirm that behavior running LMS on max2play. This bug has been around for a while.

Regards

Rheinländer

the_arm
2018-01-18, 13:28
I can confirm that behavior running LMS on max2play. This bug has been around for a while.

Regards

Rheinländer

Likewise, I've seen this on osx as well. I've actually been meaning to write in about it and ask if there are solutions. Occasionally it will stop at the end of a track, I'll forget about it, and many hours later start playing again. But generally I catch it and hit "next track" and it's good to go. It's like it times out waiting for the next track or something.

There was similar behavior before Spotty, too, with Triode's plugin for me both on linux and then on osx.

ElFishi
2018-01-19, 00:07
I run two SB3 and one pCP and can confirm that v2.0.0 mostly works as expected.
I consistently used to lose the players from spotify connect in the night. Now the players are there in the morning, albeit not connected.

One problem I have still is volume control. All of my players are synchronised, but set to control their own volume.
I observe that the pCP volume is controlled by spotify while the SBs only accept their own volume control. Whats more the pCP frequently starts with zero volume and I need to crank it up first. My preference would be to ignore the spotify volume in all players.

Any hints?

mherger
2018-01-19, 00:35
> My preference
> would be to ignore the spotify volume in all players.

Just to be sure I understand correctly: while you want to be able to
control general playback (content, play/pause/fwd) through the Spotify
apps, volume should be ignored?

That's currently not possible. Might add it to the todo list.

--

Michael

ElFishi
2018-01-19, 02:20
> while you want to be able to
control general playback (content, play/pause/fwd) through the Spotify
apps, volume should be ignored?


precisely.
when playing on more than one player it is unlikely that identical volume is what you want in the first place.
in my configuration one SB3 is set to 100% anyway, b/c the preamp has remote control.
in the other SB3 and in the pCP I control volume remotely through LMS. this I want to do individually.
I don't expect the spotify app to handle individual volumes for synchronised players. so LMS needs to set volume independent from Spotify.

thanks for putting it on the list.

Chouca
2018-01-19, 02:58
Thanks for a Spotty, truly great!

Spotify Connect from LMS server switches mostly OK, quiet often when switching to SB Receiver the volume is set to 0.

Spotify App in Android phone does not show SB Players. SB Reciever shows up if I have switched to it from Spotify from LMS server but disappears from the phone if I switch to another player.

Running Spotify from Spotty in phone works great.

jasell
2018-01-19, 15:24
precisely.
when playing on more than one player it is unlikely that identical volume is what you want in the first place.
in my configuration one SB3 is set to 100% anyway, b/c the preamp has remote control.
in the other SB3 and in the pCP I control volume remotely through LMS. this I want to do individually.
I don't expect the spotify app to handle individual volumes for synchronised players. so LMS needs to set volume independent from Spotify.

thanks for putting it on the list.

Have you tried the groups plugin?
It deals with grouping of several player in to one virtual player that control the relative volume for all connected players together (the virtual group player can be controlled by Spotify connect if you like) or adjust volume on one individual player relative the others in the group using LMS GUI or iPeng.


Sent from my iPhone using Tapatalk

gharris999
2018-01-19, 22:03
I'm having trouble with Spotty (v2.0.0). After install, when I click on the settings link, I get the following error in the WebUI:

404 Not Found: plugins/Extensions/settings/plugins/Spotty/settings/basic.html

The full path on my system to basic.html is:

/var/lib/lms_data/public/7.9/cache/InstalledPlugins/Plugins/Spotty/HTML/EN/plugins/Spotty/settings/basic.html

mherger
2018-01-19, 23:38
> I'm having trouble with Spotty (v2.0.0). After install, when I click on
> the settings link, I get the following error in the WebUI:
>
> 404 Not Found:
> plugins/Extensions/settings/plugins/Spotty/settings/basic.html

Didn't you report this before? Just use Settings/Advanced/Spotty.

And I finally have to figure out why this doesn't work on some
systems... (it certainly does on all I own and tested with, which covers
Mac, pCP, Synology, CentOS based Linux).

What LMS version are you using?
--

Michael

ElFishi
2018-01-20, 01:46
ooops,
this morning spotify connect again lost all players despite running v2.0.0 (on a Raspi3/stretch lite).
I have 6 instances of sputty-muslhf running on the sever for 3 players. Reconnecting the players worked.

dora89
2018-01-20, 01:48
Since two days, the connect in Spotify does not work again. The LMS is not shown in Spotify App, but it should be connected and the settings should be correct.

The log shows the following:
[18-01-20 09:32:04.5146] Slim::Formats::Playlists::Base::playlistEntryIsVal id (125) Warning: file:///home/music/music_files/spotify:/track:1vUjlWB6JKuX4el561XrIe found in playlist:
file:///var/lib/squeezeboxserver/prefs/clientplaylist_014d306affb8.m3u doesn't exist on disk - skipping!

simonewings
2018-01-20, 12:18
Just updated to the new version and enabled connect on my touch, lms running on Windows 10 and so far it's working perfectly. [emoji5]

Sent from my SM-G930F using Tapatalk

ButC
2018-01-20, 12:53
Noticed that a problem of the first iteration of Connect for Windows is back. Having ticked the box for Connect for my Touch and then trying to start a playlist from the Touches interface (not using Connect) makes playlists repeat the first song infinetly. And Skip just starts the same song from the beginning. Unticking the Connect box now doesn't solve the problem, which it did with 1.9.x. I'd rather be without the Connect feature since this is how I mainly use Spotty.

I had logging for Spotty set to INfo this time.

benrjunk
2018-01-20, 19:44
Thanks for a great plugin. Allows me to keep using my squeezebox hardware.

I'd like to mention a problem that has already been brought up but I don't see a solution.

With multiple Spotify users (eg. for a family account), only one user can see the Spotify connect endpoints in the Spotify app. I'm wondering if there's any way so all users can see the connect players.

Thanks again.

Ben

mherger
2018-01-21, 07:53
> Since two days, the connect in Spotify does not work again. The LMS is
> not shown in Spotify App, but it should be connected and the settings
> should be correct.

I've seen various reports of users who flipped the "only show local
devices" setting in their Spotify app. This would effectively hide
Spotty devices (unless you install the upcoming 2.1.0 ;-))

--

Michael

mherger
2018-01-21, 07:54
> Just wanted to bring something up that has already been mentioned -
> multiple users.

Please update to Spotty v2.1.0. It should highly improve the Connect use
case with multiple accounts. Even guests would be able to play to your
Spotty enabled device if they were on your LAN.

--

Michael

mherger
2018-01-21, 07:57
You should finally be able to play to your Spotty Connect enabled device from any Spotify app in your local network. It doesn't even need to be configured in LMS itself.

Unfortunately this feature is not available on Windows...

dora89
2018-01-21, 09:02
No, this is not checked. So it should be possible to see the LMS in the Spotify app.

dora89
2018-01-21, 09:06
Now, after update to 2.1 it works again :)

Chouca
2018-01-21, 09:57
Spotify Connect from LMS server switches mostly OK, quiet often when switching to SB Receiver the volume is set to 0.

Spotify App in Android phone does not show SB Players. SB Reciever shows up if I have switched to it from Spotify from LMS server but disappears from the phone if I switch to another player.
.

2.1 Fixed the problem, SB players do now show up in Android phone!

Volume still set to 0 when switching.

Great Update!

gharris999
2018-01-21, 11:25
> I'm having trouble with Spotty (v2.0.0). After install, when I click on
> the settings link, I get the following error in the WebUI:
>
> 404 Not Found:
> plugins/Extensions/settings/plugins/Spotty/settings/basic.html

Didn't you report this before? Just use Settings/Advanced/Spotty.

And I finally have to figure out why this doesn't work on some
systems... (it certainly does on all I own and tested with, which covers
Mac, pCP, Synology, CentOS based Linux).

What LMS version are you using?
--

Michael
Sorry, trumpiness has lead to all kinds of cognitive difficulties for those of us who live in the US, memory problems among them.

I'm running LMS straight from the 7.9 git code.

jsandquist
2018-01-21, 11:41
Wow wow wow, just a heads up and confirmation that Spotty 2.1 greatly improved the Spotify Connect experience and now listens all Squeezeboxes available even in multi user scenarios. And the smart authentication/authorization worked like a charm also for the one account (out of the 5) using Facebook login to Spotify - after you click "Add account" in the advanced settings.

Running LMS in a Docker container on a Synology 415+ (on host network, not bridged).

Cheers!

mherger
2018-01-21, 12:52
> Noticed that a problem of the first iteration of Connect for Windows is
> back. Having ticked the box for Connect for my Touch and then trying to
> start a playlist from the Touches interface (not using Connect) makes
> playlists repeat the first song infinetly. And Skip just starts the same
> song from the beginning. Unticking the Connect box now doesn't solve the
> problem, which it did with 1.9.x. I'd rather be without the Connect
> feature since this is how I mainly use Spotty.

Next time this happens could you please check how manyspotty.exe
processes are still running? And how many player are playing Spotify
content, how many are exposed to Connect?

(If in doubt, just disable Connect for all players, it's still an
optional feature)

--

Michael

mherger
2018-01-21, 12:52
> I'm running LMS straight from the 7.9 git code.

Oh, on what platform? And how do you start it?

--

Michael

benrjunk
2018-01-21, 14:59
Thank you so much with 2.1.0! Addresses issue with multiple users/accounts.

Sincerely,

Ben

jasell
2018-01-21, 16:23
I just updated to 2.1.0 . But now I can’t see any player in Spotify connect. The players have connect enabled, both under the advanced menu (new feature) and player menus.

I have restarted the server.

I checked the device settings in Spotify, only local player is off.

Spotty app in LMS works fine!

Any advice?


Sent from my iPad using Tapatalk

ButC
2018-01-22, 00:18
> Noticed that a problem of the first iteration of Connect for Windows is
> back. Having ticked the box for Connect for my Touch and then trying to
> start a playlist from the Touches interface (not using Connect) makes
> playlists repeat the first song infinetly. And Skip just starts the same
> song from the beginning. Unticking the Connect box now doesn't solve the
> problem, which it did with 1.9.x. I'd rather be without the Connect
> feature since this is how I mainly use Spotty.

Next time this happens could you please check how manyspotty.exe
processes are still running? And how many player are playing Spotify
content, how many are exposed to Connect?

(If in doubt, just disable Connect for all players, it's still an
optional feature)

--

Michael

This is repeatable for me, it happens every time I try to start a playlist from Squeezelite (I use the Local player plugin and uses a Touch as UI for Squeezelite). The Connect part seems to work as it should, where I can skip and switch between playlists just fine. But when starting a playlist, any playlist, from Squeezelite, it just repeats the first song - switching between playlists is working, though. And it doesn't help to disable Connect, something that did help for Spotty up until 2.0.

There are 2 Spotty.exe processes and when trying to skip (having started the playlist from Squeezelite) a third Spotty.exe is created for half a second (while trying to skip) and then when the same song starts all over that third Spotty.exe is being killed.

I only use one player (Squeezelite). And only one is exposed to Connect (none when Connect is disabled, of course)

DigitalMitch
2018-01-22, 04:52
"If this is Windows Home Server v1, then I'm sorry, Spotty will not work.
If not, you might want to check out the server.log to get us some
information about the failure."


Michael, bought a Max2Play Rasberry Pi to act as server, now up and running thanks for the App.

I am sure some long term Squeezebox users, like me, will upgrade to spotify and try and use through squeezebox straight away without understanding Spotify first.
My key understanding is as follows:-

There are two different ways of operating Spotty.
1) use Spotty on LMS (in my case via iPeng) which pulls music down from Spotify
2) use Spotify app to push to Squeezebox (Spotify Connect)

Other than choice of interface, there seems to be a difference in where the playlist/queue resides. If you select off Spotify, it has the playlist and Squeezebox can only see one song.
If you use Spotty then the whole playlist is in LMS, and you can resort or even add songs from the server to the current playlist, but Spotify apps won't report what is being played.

Mitch

loopguru
2018-01-22, 08:01
Thanks Michael for introducing the multi account feature. Works great!

I have another question where I would need some education

I realized my Squeezebox Radios at home are still listed as Spotify Connect devices when I'm traveling abroad. More disturbingly they really work: I really can choose them and they start playing 100 kilometers away at home.
I found out it is possible to remove these remote devices from the app by switching on in the app "show local devices only".

Questions are now:

Can I enable my Squeezebox Radios as local device only. So Radios vanish in the Spotify app when I leave my LAN?
If a guest chooses a Radio while being at my home: Can he stream to my Radios even if he is gone?

Thanks,
Tom

jasell
2018-01-22, 08:38
I just updated to 2.1.0 . But now I can’t see any player in Spotify connect. The players have connect enabled, both under the advanced menu (new feature) and player menus.

I have restarted the server.

I checked the device settings in Spotify, only local player is off.

Spotty app in LMS works fine!

Any advice?


Sent from my iPad using Tapatalk

On a LMS restart I get a lot of these...

0052: note: Run with `RUST_BACKTRACE=1` for a backtrace.
0051: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /checkout/src/libcore/result.rs:859
0050: note: Run with `RUST_BACKTRACE=1` for a backtrace.
0049: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /checkout/src/libcore/result.rs:859
0048: note: Run with `RUST_BACKTRACE=1` for a backtrace.
0047: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /checkout/src/libcore/result.rs:859
0046: note: Run with `RUST_BACKTRACE=1` for a backtrace.
0045: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /checkout/src/libcore/result.rs:859
0044: note: Run with `RUST_BACKTRACE=1` for a backtrace
Should I uninstall spotty and clean out all spotty file and install from fresh?


Sent from my iPad using Tapatalk

mherger
2018-01-22, 08:44
> - Can I enable my Squeezebox Radios as local device only. So Radios
> vanish in the Spotify app when I leave my LAN?

No, unfortunately this won't work.

> - If a guest chooses a Radio while being at my home: Can he stream to
> my Radios even if he is gone?

Now that's a good one... I think it _might_ work as long as you haven't
taken over control of that Radio from one of your accounts, or have
restarted LMS. Or the spotty daemon hasn't crashed :-)

--

Michael

mherger
2018-01-22, 08:45
> I just updated to 2.1.0 . But now I can’t see any player in Spotify
> connect. The players have connect enabled, both under the advanced menu
> (new feature) and player menus.

Anything in server.log? Would you see spotty processes in your
task-manager (or process list)?

--

Michael

mherger
2018-01-22, 08:48
> On a LMS restart I get a lot of these...
>
> Code:
> --------------------
> 0052: note: Run with `RUST_BACKTRACE=1` for a backtrace.
> 0051: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /checkout/src/libcore/result.rs:859

These look like helper crashes. Odd. Did you recently update your
operating system? The spotty helper has not changed from 2.0 to 2.1.

There's a new setting in Settings/Advanced/Spotty which would allow you
to disable the local discovery mode. Would it run smoother with that
option checked?

--

Michael

mherger
2018-01-22, 08:49
> This is repeatable for me, it happens every time I try to start a
> playlist from Squeezelite

A Spotify playlist or any playlist? What if you started to play a local
album?

--

Michael

ButC
2018-01-22, 09:37
> This is repeatable for me, it happens every time I try to start a
> playlist from Squeezelite

A Spotify playlist or any playlist? What if you started to play a local
album?

--

Michael

Skip doesn't seem to work at all when playing via Squeezelite. Doesn't matter if it's a Spotify playlist, any playlist, local artist or album. The only thing that works is if I for example starts to play an album and then, using the Touches remote, clicks Right when on the Now playing screen and gets the list of songs on that album, I then can choose whichever song I want and it plays - but no skipping.

It seems like unticking the Connect feature doesn't actually Disable Connect as it did prior 2.0.

I've restarted both server and Touch.

bakker_be
2018-01-22, 10:34
Unfortunately this feature is not available on Windows...

Hi Michael,
Do you mean for LMS running on Windows or for Spotify clients (Spotify app, web client) running on Windows?

loopguru
2018-01-22, 12:32
> Can I enable my Squeezebox Radios as local device only. So Radios
> vanish in the Spotify app when I leave my LAN?
No, unfortunately this won't work.

> - If a guest chooses a Radio while being at my home: Can he stream to
> my Radios even if he is gone?

Now that's a good one... I think it _might_ work as long as you haven't
taken over control of that Radio from one of your accounts, or have
restarted LMS. Or the spotty daemon hasn't crashed :-)

I did more testing with remote clients and multiple accounts:


If you are a guest (= no Spotify account configured in Spotty plugin) and leave the WLAN then all Squeezeboxes are vanishing (puhhh!). No chance to wake up your friends.
If you leave the WLAN and have a configured account in Spotty then you only see Squeezeboxes which are switched to your account.

Summarized it seems there are two ways Spotty advertises Squeezeboxes: As authenticated device or as anonymous device. Authenticated devices stay visible to the account owner even if one goes abroad.

There are two improvements I could think off in an upcoming Spotty release:


Only advertise Squeezeboxes anonymously. Playing on a remote Squeezebox seems to have no meaningful use case. Even worse you cannot switch off the Squeezebox remotely if you streamed to it in error.
Turn Squeezeboxes off after playing stops in Spotify Connect. This is the standard behavior on most Spotify Connect enabled devices. It is more convenient as it does not force you to switch to iPeng or walk to the box if you are done with listening.

Tom

mherger
2018-01-22, 12:51
> Skip doesn't seem to work at all when playing via Squeezelite.

Are you sure you haven't enabled track repeat?

--

Michael

mherger
2018-01-22, 12:52
> mherger wrote:
>> Unfortunately this feature is not available on Windows...
>
> Do you mean for LMS running on Windows or for Spotify clients (Spotify
> app, web client) running on Windows?

Running LMS on Windows. It doesn't support the discovery mode (yet?).

--

Michael

mherger
2018-01-22, 12:56
> - If you are a guest (= no Spotify account configured in Spotty
> plugin) and leave the WLAN then all Squeezeboxes are vanishing
> (puhhh!). No chance to wake up your friends.
> - If you leave the WLAN and have a configured account in Spotty then
> you only see Squeezeboxes which are switched to your account.

Thanks for the testing! Sounds good.

> - Only advertise Squeezeboxes anonymously. Playing on a remote
> Squeezebox seems to have no meaningful use case. Even worse you cannot
> switch off the Squeezebox remotely if you streamed to it in error.

Unfortunately this isn't possible, as some platforms don't support the
local announcement (Windows!).

> - Turn Squeezeboxes off after playing stops in Spotify Connect. This
> is the standard behavior on most Spotify Connect enabled devices.

SB obviously isn't a standard Spotify Connect device. But I see your
point. Connect Stop should be the same as "Power Off" in SB terms?

--

Michael

shade73a
2018-01-22, 13:04
2.1 = Big WAF. Thx!

On the other hand, while wife is happy, the kids, even more. I got a problem.
They can all play on all players! I cant stand their music in the kitchen and living room.
Perhaps not a big problem for so many.
But I for one, would be very greatful if there was a possibility to map the accounts to the players, like a matrix.

Br Fredrik

loopguru
2018-01-22, 13:08
> - Only advertise Squeezeboxes anonymously. Playing on a remote
> Squeezebox seems to have no meaningful use case. Even worse you cannot
> switch off the Squeezebox remotely if you streamed to it in error.
Unfortunately this isn't possible, as some platforms don't support the
local announcement (Windows!).

I see. Maybe there could be a checkbox in the LMS Spotty plugin config "only advertise locally".


> - Turn Squeezeboxes off after playing stops in Spotify Connect. This
> is the standard behavior on most Spotify Connect enabled devices.

SB obviously isn't a standard Spotify Connect device. But I see your
point. Connect Stop should be the same as "Power Off" in SB terms?

Yes, exactly.

Tom

cramcram
2018-01-22, 13:17
Running LMS in a Docker container on a Synology 415+ (on host network, not bridged).

How did you do that? Is there a tutorial? Can you update the LMS to the latest nightly build?

mherger
2018-01-22, 13:17
> mherger wrote:
>>> - Only advertise Squeezeboxes anonymously. Playing on a remote
>>> Squeezebox seems to have no meaningful use case. Even worse you
>> cannot
>>> switch off the Squeezebox remotely if you streamed to it in error.
>> Unfortunately this isn't possible, as some platforms don't support the
>> local announcement (Windows!).
>>
> I see. Maybe there could be a checkbox in the LMS Spotty plugin config
> "only advertise locally".

That's something somebody else already mentioned. But I'm not sure it's
technically possible.


--

Michael

mherger
2018-01-22, 13:35
> They can all play on all players! I cant stand their music in the
> kitchen and living room.
> Perhaps not a big problem for so many.
> But I for one, would be very greatful if there was a possibility to map
> the accounts to the players, like a matrix.

You can disable the local discovery in the settings. Doesn't prevent
them from using your players. But it's more complicated. They would only
see the players which are configured to use their account.

--

Michael

ButC
2018-01-22, 14:04
> Skip doesn't seem to work at all when playing via Squeezelite.

Are you sure you haven't enabled track repeat?

--

Michael

It was turned off but to check whether it was on or off I pushed the dedicated button on the Touches remote and when it turned repeat on I had to turn it off again. And after that skip worked for local music. But then every option in Spotty was empty, and I then noticed a new update for LMS. After installing this update I had to pull the plug on the Touch in order to get Spotty working. But. Now it seems to work! You're a genius :)

I'll do a little more testing tomorrow.

Thanks for the heads up :)

gharris999
2018-01-22, 21:28
> I'm running LMS straight from the 7.9 git code.

Oh, on what platform? And how do you start it?

--

Michael
re platform:
Ubuntu 16.04.3 LTS, Linux scserver 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

re how do you start it:

systemd service unit file:


## /lib/systemd/system/lms.service -- Sat Jun 17 18:14:09 MDT 2017
## systemctl service unit file

[Unit]
Description=Logitech Media Server git code Daemon
After=local-fs.target syslog.target network.target

[Service]
#UMask=0002
Nice=-19
LimitRTPRIO=infinity
LimitMEMLOCK=infinity
EnvironmentFile=/etc/default/lms
RuntimeDirectory=lms
Type=simple
User=lms
Group=nogroup
ExecStart=/usr/local/share/lms/server/slimserver.pl ${SLIM_OPTIONS} --pidfile=${SLIM_PIDFILE} --cachedir=${SLIM_CACHEDIR} --prefsdir=${SLIM_PREFSDIR} --logdir=${SLIM_LOGDIR} --charset=${SLIM_CHARSET}

PIDFile=/var/run/lms/lms.pid
RestartSec=5
Restart=on-failure

[Install]
WantedBy=multi-user.target



Resulting process:



lms 1120 0.8 3.2 364168 254564 ? S<s 20:18 0:34 /usr/bin/perl /usr/local/share/lms/server/slimserver.pl /usr/local/share/lms/server/slimserver.pl --nosb1slimp3sync --pidfile=/var/run/lms/lms.pid --cachedir=/var/lib/lms/cache --prefsdir=/var/lib/lms/prefs --logdir=/var/log/lms --charset=utf8

mherger
2018-01-22, 22:37
> Ubuntu 16.04.3 LTS, Linux scserver 4.4.0-112-generic #135-Ubuntu SMP Fri
> Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

> lms 1120 0.8 3.2 364168 254564 ? S<s 20:18 0:34 /usr/bin/perl /usr/local/share/lms/server/slimserver.pl /usr/local/share/lms/server/slimserver.pl --nosb1slimp3sync --pidfile=/var/run/lms/lms.pid --cachedir=/var/lib/lms/cache --prefsdir=/var/lib/lms/prefs --logdir=/var/log/lms --charset=utf8

I don't get it... run LMS from a git clone on a 16.04 with above command
(adjusting paths where necessary). And it just worked. What browser did
you use? From the server itself or a different Computer?

--

Michael

slartibartfast
2018-01-23, 06:03
I know this has been reported before but all of my Connect enabled players were missing from "Devices available" this morning. This is the first time in a long while it has happened. Restarting LMS fixed it.

Sent from my SM-G900F using Tapatalk

BillatLakeGeorge
2018-01-23, 06:15
Since Spotty 2.1 was installed my Squeezebox no longer shows up in connected devices. I have tried reinstalling and rebooting with no luck.

mherger
2018-01-23, 06:49
> Since Spotty 2.1 was installed my Squeezebox no longer shows up in
> connected devices. I have tried reinstalling and rebooting with no
> luck.

What device/platform/OS are you running?

Try disabling the discovery mode in Spotty's settings.

--

Michael

BillatLakeGeorge
2018-01-23, 06:59
> Since Spotty 2.1 was installed my Squeezebox no longer shows up in
> connected devices. I have tried reinstalling and rebooting with no
> luck.

What device/platform/OS are you running?

Try disabling the discovery mode in Spotty's settings.

--

Michael

Disabling discovery settings worked.

Thanks

mherger
2018-01-23, 07:29
> Disabling discovery settings worked.

What device/platform/OS are you running Spotty on?

--

Michael

slartibartfast
2018-01-23, 08:27
I know this has been reported before but all of my Connect enabled players were missing from "Devices available" this morning. This is the first time in a long while it has happened. Restarting LMS fixed it.

Sent from my SM-G900F using TapatalkJust turned on another Radio and it doesn't show up as an available device. The settings box to prevent devices appearing is unticked which I assume is correct.

Sent from my SM-G900F using Tapatalk

korecto
2018-01-23, 09:07
> Disabling discovery settings worked.

What device/platform/OS are you running Spotty on?

--

Michael

Hi Michael,

Thx for this massive plugin ;)

I have the same problem with my Synology Nas DS214play Intel AtomCE5335 with last update DSM, LMS, Spotty 2.1... The discovery is not working (only local discovery in Spotify app is disable) on Squeeze Radio, Boom, Duet.

Best regards

slartibartfast
2018-01-23, 09:46
Just turned on another Radio and it doesn't show up as an available device. The settings box to prevent devices appearing is unticked which I assume is correct.

Sent from my SM-G900F using TapatalkAll devices disappeared again requiring a restart of LMS.

Sent from my SM-G900F using Tapatalk

BillatLakeGeorge
2018-01-23, 10:26
> Disabling discovery settings worked.

What device/platform/OS are you running Spotty on?

--

Michael

Squeezebox Classic, Synology DS414j, not sure of OS.

mherger
2018-01-23, 10:56
>> Sent from my SM-G900F using TapatalkJust turned on another Radio and it doesn't show up as an available
> device. The settings box to prevent devices appearing is unticked which

Check that box and try again.

What system are you running your LMS on?

--

Michael

mherger
2018-01-23, 10:57
> I have the same problem with my Synology Nas DS214play Intel AtomCE5335
> with last update DSM, LMS, Spotty 2.1... The discovery is not working
> (only local discovery in Spotify app is disable) on Squeeze Radio, Boom,
> Duet.

Did you check the "disable local discovery" box in Spotty's settings?

--

Michael

mherger
2018-01-23, 10:57
> Squeezebox Classic, Synology DS414j, not sure of OS.

Thanks, that's a data point. I will try to be smarter about the
discovery mode in the next version.
--

Michael

slartibartfast
2018-01-23, 11:51
>> Sent from my SM-G900F using TapatalkJust turned on another Radio and it doesn't show up as an available
> device. The settings box to prevent devices appearing is unticked which

Check that box and try again.

What system are you running your LMS on?

--

Michael

I tried ticking the box and all the devices disappeared. Unchecked the box again and one of the Radios appeared briefly and disappeared before my eyes.
max2play on Raspberry Pi.

Sent from my SM-G900F using Tapatalk

jasell
2018-01-23, 11:53
I just updated to 2.1.0 . But now I can’t see any player in Spotify connect. The players have connect enabled, both under the advanced menu (new feature) and player menus.

I have restarted the server.

I checked the device settings in Spotify, only local player is off.

Spotty app in LMS works fine!

Any advice?


Sent from my iPad using Tapatalk
If I enable setting:
"Don't announce Squeezebox players running in Spotify Connect mode in your network. Check this option if you don't want your Spotify Connect enabled Squeezebox player to show up in all Spotify apps in your network. "

I can now use Spotify Connect as before, without issues in the server-log as well.
But I can't see a specific player from multiple Spotify accounts simultaneously though...

korecto
2018-01-23, 12:17
> I have the same problem with my Synology Nas DS214play Intel AtomCE5335
> with last update DSM, LMS, Spotty 2.1... The discovery is not working
> (only local discovery in Spotify app is disable) on Squeeze Radio, Boom,
> Duet.

Did you check the "disable local discovery" box in Spotty's settings?

--

Michael

Yes, the connect fonction only work if this option is activated

ButC
2018-01-23, 12:45
I've had the chance to test it some more now and it generally works well, skipping, volume, switching between playlists. But sometimes when having started a playlist from the Squeezebox Touches ui and trying to switch playlist by using the Connect feature from the phones Spotify app it finds the device to play to and selects it and plays the song but the ongoing playlist continues to play on the Touch and the new playlist plays on the phone (without sound). In short, Connect doesn't always manage to overtake an ongoing playlist.

It's right at the end of the log.

mherger
2018-01-23, 12:46
> I can now use Spotify Connect as before, without issues in the
> server-log as well.
> But I can't see a specific player from multiple Spotify accounts
> simultaneously though...

That's the downside of the improved compatibility. It seems that on some
systems the discovery mode is causing issues (crashes). But without
discovery mode you're stuck with streaming from the accounts you've
configured in your Spotty.

> NAS: QNAP TS-459U+ -QTS 4.2.6- (4x 2TB, RAID5)

Is this the device you use to run LMS?

--

Michael

mherger
2018-01-23, 12:46
> max2play on Raspberry Pi.

Are you running other services on that Pi? If so, which ones?

--

Michael

slartibartfast
2018-01-23, 12:50
> max2play on Raspberry Pi.

Are you running other services on that Pi? If so, which ones?

--

MichaelMusicIP is all I can think of.

Sent from my SM-G900F using Tapatalk

slartibartfast
2018-01-23, 13:02
> max2play on Raspberry Pi.

Are you running other services on that Pi? If so, which ones?

--

MichaelAfter reading another post I rechecked the box in the settings and restarted LMS. Now it seems to be working and a newly turned on device appears in the devices list.

Sent from my SM-G900F using Tapatalk

Huey11
2018-01-23, 14:39
Hi, I had to reinstall my LMS. Now when adding Spotty 2.1.0 and trying to open settings I get: 404 Not Found: plugins/Extensions/settings/plugins/Spotty/settings/basic.html

Please advice?
TIA

slartibartfast
2018-01-23, 14:41
Hi, I had to reinstall my LMS. Now when adding Spotty 2.1.0 and trying to open settings I get: 404 Not Found: plugins/Extensions/settings/plugins/Spotty/settings/basic.html

Please advice?
TIATry accessing the settings through the "Advanced" tab. Spotty should be listed.

Sent from my SM-G900F using Tapatalk

slartibartfast
2018-01-23, 16:04
After reading another post I rechecked the box in the settings and restarted LMS. Now it seems to be working and a newly turned on device appears in the devices list.

Sent from my SM-G900F using TapatalkIt seems to be working as all my devices are visible but I can't play anything. The Spotify app thinks it is playing to my Touch but the Touch is not playing.

Sent from my SM-G900F using Tapatalk

Huey11
2018-01-23, 16:19
Try accessing the settings through the "Advanced" tab. Spotty should be listed.

Sent from my SM-G900F using Tapatalk

Ok, now I get to the dreaded: "Spotty requires the Perl module IO::Socket::SSL. You can NOT use Spotty without this module. Please use your operating system's package manager to install it."
Forgot about this. Installed libnet-ssleay-perl and libio-socket-ssl-perl on my raspberry and now it works again. Thanks!

mherger
2018-01-23, 22:16
>> Sent from my SM-G900F using TapatalkIt seems to be working as all my devices are visible but I can't play
> anything. The Spotify app thinks it is playing to my Touch but the Touch
> is not playing.

Hmm... could you please restart a bit of everything?... Touch, Pi,
Router? Anything in server.log when the non-playing happens? Would Touch
show metadata, but not play any audio?

--

Michael

mherger
2018-01-23, 22:20
> I've had the chance to test it some more now and it generally works
> well, skipping, volume, switching between playlists. But sometimes when
> having started a playlist from the Squeezebox Touches ui and trying to
> switch playlist by using the Connect feature from the phones Spotify app
> it finds the device to play to and selects it and plays the song but
> ongoing playlist continues playing on the touch and the new playlist
> plays on the phone (without sound). In short, Connect doesn't always
> work.

Hmm... you're now the third person to report an issue with similar
symptoms in the log (inability to get a token) on Windows. What Windows
version are you using? What if you removed credentials from Spotty's
settings and re-started over?
--

Michael

slartibartfast
2018-01-24, 02:23
>> Sent from my SM-G900F using TapatalkIt seems to be working as all my devices are visible but I can't play
> anything. The Spotify app thinks it is playing to my Touch but the Touch
> is not playing.

Hmm... could you please restart a bit of everything?... Touch, Pi,
Router? Anything in server.log when the non-playing happens? Would Touch
show metadata, but not play any audio?

--

Michael

For some reason the log does not go back that far. The touch was just displaying the "stopped" screensaver.

After unticking the "Don't announce" box I could play tracks but this morning the Touch has disappeared and the server log contains

[18-01-24 09:08:16.0094] Plugins::Spotty::API::getToken (121) Failed to get Spotify access token: malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "(end of string)") at /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/API.pm line 118.

mherger
2018-01-24, 05:21
> For some reason the log does not go back that far. The touch was just
> displaying the "stopped" screensaver.

Download the full log file, not just the 50 lines the web UI would show.
It goes back to day 0 (unless it had reached 100MB after that day).

> [18-01-24 09:08:16.0094] Plugins::Spotty::API::getToken (121) Failed to
> get Spotify access token: malformed JSON string, neither array, object,
> number, string or atom, at character offset 0 (before "(end of string)")

This looks like an invalid response from Spotify's server. Could you try
again in a bit?

--

Michael

slartibartfast
2018-01-24, 07:09
> For some reason the log does not go back that far. The touch was just
> displaying the "stopped" screensaver.

Download the full log file, not just the 50 lines the web UI would show.
It goes back to day 0 (unless it had reached 100MB after that day).

> [18-01-24 09:08:16.0094] Plugins::Spotty::API::getToken (121) Failed to
> get Spotify access token: malformed JSON string, neither array, object,
> number, string or atom, at character offset 0 (before "(end of string)")

This looks like an invalid response from Spotify's server. Could you try
again in a bit?

--

MichaelThe earliest event in the complete server log is at 6:25 this morning. The whole thing is only 294KB.
Spotty seems to be working at the moment with the "Don't announce Squeezeboxes" setting unticked. I have not tried again with the box ticked.

Sent from my SM-G900F using Tapatalk

ButC
2018-01-24, 09:19
> I've had the chance to test it some more now and it generally works
> well, skipping, volume, switching between playlists. But sometimes when
> having started a playlist from the Squeezebox Touches ui and trying to
> switch playlist by using the Connect feature from the phones Spotify app
> it finds the device to play to and selects it and plays the song but
> ongoing playlist continues playing on the touch and the new playlist
> plays on the phone (without sound). In short, Connect doesn't always
> work.

Hmm... you're now the third person to report an issue with similar
symptoms in the log (inability to get a token) on Windows. What Windows
version are you using? What if you removed credentials from Spotty's
settings and re-started over?
--

Michael

I'm running Windows 10.

I removed the credentials and restarted LMS and added them again and after that Connect managed to overtake an ongoing playlist. But it's too soon to say anything since this sometimes worked and sometimes didn't. I'll let you know how it plays out.

ButC
2018-01-24, 09:53
I'm running Windows 10.

I removed the credentials and restarted LMS and added them again and after that Connect managed to overtake an ongoing playlist. But it's too soon to say anything since this sometimes worked and sometimes didn't. I'll let you know how it plays out.

After trying just a little bit more I ran into trouble. Having switched a few times between different playlists using Connect all the time, it suddenly refused to switch playlist - and Spotty more or less hanged; I couldn't even switch playlist if I tried to do it from the Touch's UI. Local music played fine.

BillatLakeGeorge
2018-01-24, 12:47
> Squeezebox Classic, Synology DS414j, not sure of OS.

Thanks, that's a data point. I will try to be smarter about the
discovery mode in the next version.
--

Michael

Music stopped playing in the middle of an album. I had to uncheck announcement and then recheck it to get it to play again.

devilsfun
2018-01-24, 13:17
Hi,

after updating to version 2.0.0 (now 2.1.0) the automatic power off function doesn't work anymore. Situation bevor updating: after playing an audiobook on the squeezebox player it shuts off automatical (hibernate) and shows the clock. now the picture of the played audio stays on the screen.

Is this a known problem?

Daniel

jsandquist
2018-01-24, 14:09
How did you do that? Is there a tutorial? Can you update the LMS to the latest nightly build?

Replying a little late and maybe there is a better thread available for this but still.

This got me started a while back - https://www.hanselman.com/blog/DockerOnASynologyNASAlsoRunningASPNETAndNETCore.as px - with a link to a more technical blog post at http://www.jinkit.com/docker-on-synology/

However, I did it all through Synology's "Docker GUI" and tested a couple of different LMS containers:

Simply search for "Logitech" in the registry tab and quite a few hits will show up
After testing a few different ones I found https://hub.docker.com/r/jboesl/logitechmediaserver/ to be working fine for me
When you the launch it click Advanced settings
Tick "Use same network as docker host" (as I don't know what ports settings to use for Spotify Connect)
Possibly add an environment variable "TZ" with a value like "CET-1CEST,M3.5.0,M10.5.0/3" to get your Squeezeboxes to show the proper time - you might ssh into your Synology to find the proper value
I have not done any volume mappings so any configurations within LMS will currently be lost


Regarding (2) there seems to be updated containers available every now and then - I am currently at 7.9.1 - 1513951369 @ Fri Dec 22 2017.

mherger
2018-01-24, 15:25
> Music stopped playing in the middle of an album. I had to uncheck
> announcement and then recheck it to get it to play again.

Please always, did I say: ALWAY!, check your server.log when you're
reporting some failure. The log will tell us what happened. At least
part of the story. Eg it would tell us whether the daemon crashed.

--

Michael

2eleven
2018-01-24, 22:30
Thanks so much for the work on this plugin!

I don't think this has been asked before (my search didn't turn up any results). Is there a way to unfollow an artist? I couldn't find a way, but it would be a very welcome feature if it's possible.

Thanks again,
John

mherger
2018-01-24, 22:41
> after updating to version 2.0.0 (now 2.1.0) the automatic power off
> function doesn't work anymore. Situation bevor updating: after playing
> an audiobook on the squeezebox player it shuts off automatical
> (hibernate) and shows the clock. now the picture of the played audio
> stays on the screen.

I guess you are on Windows? I could imagine that LMS would no longer let
the computer go to power saving mode as the spotty helper application is
running in the background to announce itself as a Spotify Connect
endpoint. If you have enabled Connect for one of your players, please
disable it and see whether it changes the behaviour for your system.

--

Michael

mherger
2018-01-24, 23:00
> I don't think this has been asked before (my search didn't turn up any
> results). Is there a way to unfollow an artist? I couldn't find a way,

I'm sorry, no. This currently isn't available. I'll add it to my list.


--

Michael

loopguru
2018-01-25, 03:27
after updating to version 2.0.0 (now 2.1.0) the automatic power off function doesn't work anymore. Situation bevor updating: after playing an audiobook on the squeezebox player it shuts off automatical (hibernate) and shows the clock. now the picture of the played audio stays on the screen.

Is this a known problem?

I thought I experience a similar issue but couldn't confirm that:

If I play any song from LMS my Squeezebox Radio never shuts down after stop/pause unless I power off explicitly.
So Spotify Connect makes no difference: After pressing pause the last artwork stays on the screen forever.

To overcome I activated the PowerSave plugin from Jason Holtzapple. Allows to power down after a adjustable time span when Squeezebox is on pause/stop.

Tom

slartibartfast
2018-01-25, 03:29
I thought I experience a similar issue but couldn't confirm that:

If I play any song from LMS my Squeezebox Radio never shuts down after stop/pause unless I power off explicitly.
So Spotify Connect makes no difference: After pressing pause the last artwork stays on the screen forever.

To overcome I activated the PowerSave plugin from Jason Holtzapple. Allows to power down after a adjustable time span when Squeezebox is on pause/stop.

TomWhat do you have a "stopped" screensaver?

Sent from my SM-G900F using Tapatalk

loopguru
2018-01-25, 03:46
What do you have as "stopped" screensaver?
None

slartibartfast
2018-01-25, 04:20
NoneThat might be why the artwork remains on the screen.

Sent from my SM-G900F using Tapatalk

fbomke
2018-01-25, 05:52
Hi Michael,
first of all thanks for your great work on making spotify (and spotify connect) work for LMS and Squeezeboxes.
For now I have some issues with the spotify daemon on windows, once I enable it for at least one of my devices.
When logged in via RDP I can see the daemon crashing (cmd windows popping up, prompting the user to terminate spotty.exe).
When this happens, I end up with up to 4 processes (since the crashed one automatically starts a new instance) in the task manager until I terminate the crashed spotty.exe manually.

I would be thankful if you could take a look at my log file and tell me where my problem is...

Setup:
- LMS (Logitech Media Server Version: 7.9.1 - 1516565589 @ Mon Jan 22 08:01:18 CUT 2018) running on Windows 10 maintained through RDP
- Devices: 1 Squeezebox Radio and 2 o2 jogglers running SqueezeOS

Server log:
24434

BillatLakeGeorge
2018-01-25, 06:18
> Music stopped playing in the middle of an album. I had to uncheck
> announcement and then recheck it to get it to play again.

Please always, did I say: ALWAY!, check your server.log when you're
reporting some failure. The log will tell us what happened. At least
part of the story. Eg it would tell us whether the daemon crashed.

--

Michael

Here is the log I don't know what to look for thanks.


[18-01-25 07:38:46.7775] Plugins::Spotty::API::getToken (127) Caching for 3600 seconds.
[18-01-25 07:38:46.7798] Plugins::Spotty::API::_call (1303) Trying to read from cache for me
[18-01-25 07:38:46.7815] Plugins::Spotty::API::_call (1312) API call: me
[18-01-25 07:38:46.7895] Plugins::Spotty::API::_call (1312) API call: me/player/devices
[18-01-25 07:38:47.1424] Plugins::Spotty::API::__ANON__ (1357) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[18-01-25 07:38:47.1448] Plugins::Spotty::API::__ANON__ (1359) Data cached (https://api.spotify.com/v1/me)
[18-01-25 07:39:30.6784] Plugins::Spotty::Connect::__ANON__ (75) Discovery mode for Connect has changed - re-initialize Connect helpers
[18-01-25 07:39:30.6806] Plugins::Spotty::Connect::initHelpers (373) Need to start Connect daemon for 00:04:20:07:ed:c0
[18-01-25 07:39:30.6831] Plugins::Spotty::Connect::startHelper (430) Starting Spotty Connect deamon:
/volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c /volume1/@appstore/SqueezeCenter/Cache/spotty/021b18d6 -n Bills SB3 --disable-audio-cache --bitrate 96 --player-mac 00:04:20:07:ed:c0 --lms 192.168.0.197:9002 --disable-discovery
[18-01-25 07:39:35.0047] Plugins::Spotty::API::_call (1303) Trying to read from cache for me
[18-01-25 07:39:35.0066] Plugins::Spotty::API::_call (1306) Returning cached data for me
[18-01-25 07:39:35.0097] Plugins::Spotty::API::_call (1312) API call: me/player/devices
[18-01-25 07:40:31.3533] Plugins::Spotty::Connect::_connectEvent (252) Got called from spotty helper: start
[18-01-25 07:40:31.3577] Plugins::Spotty::API::_call (1303) Trying to read from cache for me
[18-01-25 07:40:31.3595] Plugins::Spotty::API::_call (1312) API call: me
[18-01-25 07:40:31.3677] Plugins::Spotty::API::_call (1312) API call: me/player
[18-01-25 07:40:31.7151] Plugins::Spotty::API::__ANON__ (1357) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[18-01-25 07:40:31.7173] Plugins::Spotty::API::__ANON__ (1359) Data cached (https://api.spotify.com/v1/me)
[18-01-25 07:40:31.8295] Plugins::Spotty::Connect::__ANON__ (288) Got a new track to be played: spotify:track:0KL9K9gnnbVEdA5t1F6EIs
[18-01-25 07:40:31.8694] Plugins::Spotty::API::_call (1303) Trying to read from cache for me
[18-01-25 07:40:31.8713] Plugins::Spotty::API::_call (1306) Returning cached data for me
[18-01-25 07:40:31.8731] Plugins::Spotty::Connect::getNextTrack (131) Don't get next track as we got called by a play track event from spotty
[18-01-25 07:40:31.8788] Plugins::Spotty::Plugin::purgeAudioCacheAfterXTrac ks (428) Played 3 song(s) since last audio cache purge.
[18-01-25 07:40:31.9892] Plugins::Spotty::Connect::_onPause (209) Got a stop event within 5s after start of a new track - do NOT tell Spotify Connect controller to pause
[18-01-25 07:40:37.3279] Plugins::Spotty::Connect::_connectEvent (252) Got called from spotty helper: stop
[18-01-25 07:40:37.3324] Plugins::Spotty::API::_call (1303) Trying to read from cache for me
[18-01-25 07:40:37.3343] Plugins::Spotty::API::_call (1306) Returning cached data for me
[18-01-25 07:40:37.3484] Plugins::Spotty::API::_call (1312) API call: me/player
[18-01-25 07:40:37.5878] Plugins::Spotty::Connect::__ANON__ (322) Spotify told us to pause
[18-01-25 07:40:37.6100] Plugins::Spotty::Connect::_onPause (213) Got a pause event - tell Spotify Connect controller to pause, too
[18-01-25 07:40:37.6147] Plugins::Spotty::API::_call (1303) Trying to read from cache for me
[18-01-25 07:40:37.6169] Plugins::Spotty::API::_call (1306) Returning cached data for me
[18-01-25 07:40:37.6215] Plugins::Spotty::API::_call (1312) API call: me/player/pause?device_id=a4c6d9db3f3d500210e260dde1126bfeb9 5e4e91

BillatLakeGeorge
2018-01-25, 06:54
Double Post

devilsfun
2018-01-25, 09:42
> after updating to version 2.0.0 (now 2.1.0) the automatic power off
> function doesn't work anymore. Situation bevor updating: after playing
> an audiobook on the squeezebox player it shuts off automatical
> (hibernate) and shows the clock. now the picture of the played audio
> stays on the screen.

I guess you are on Windows? I could imagine that LMS would no longer let
the computer go to power saving mode as the spotty helper application is
running in the background to announce itself as a Spotify Connect
endpoint. If you have enabled Connect for one of your players, please
disable it and see whether it changes the behaviour for your system.

--

Michael

double post

devilsfun
2018-01-25, 09:47
>
I guess you are on Windows? I could imagine that LMS would no longer let
the computer go to power saving mode as the spotty helper application is
running in the background to announce itself as a Spotify Connect
endpoint. If you have enabled Connect for one of your players, please
disable it and see whether it changes the behaviour for your system.

--

Michael

Hi Michael,

sorry forgot to mention.

I'm running spotty on a ds214 with LMS 7.9.1-1504317335, spotty helper app (v0.9.0) and none of the players are checked for connect.

Daniel

jasell
2018-01-25, 10:46
Just tried 2.2.1

When I uncheck the "Don't announce..." option

I get this in my server log

0024: note: Run with `RUST_BACKTRACE=1` for a backtrace.
0023: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /checkout/src/libcore/result.rs:859
0022: note: Run with `RUST_BACKTRACE=1` for a backtrace.
0021: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /checkout/src/libcore/result.rs:859

And I see no player on my spotify devices.

When I check the option I emmidiatly see the player appearing in my Spotify Devices menu.

loopguru
2018-01-25, 11:26
What's new in 2.2.1?
Tom

mherger
2018-01-25, 12:21
What's new in 2.2.1?

The most important change is (hopefully) a fix for the crashes of the Connect daemon on Windows.

Another change is that you wouldn't get an empty player list to enable Connect on if there was no player. Most likely irrelevant to most of you :-).

mherger
2018-01-25, 12:22
> 0022: note: Run with `RUST_BACKTRACE=1` for a backtrace.
> 0021: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 92, message: "Protocol not available" } }', /checkout/src/libcore/result.rs:859

I think on some systems (mostly NAS devices afaict so far) the discovery
mode seems to conflict with another component running on that system. I
don't know whether I'll have a fix for this.

--

Michael

mherger
2018-01-25, 12:23
> I'm running spotty on a ds214 with LMS 7.9.1-166, spotty helper app
> (v0.9.0) and none of the players are checked for connect.
>
> Bevor updating to your version 2.0 the hibernation mode works perfect.

Can you please double check that by uninstalling Spotty power saving
would work again? I don't know what would have changed in this regard...

--

Michael

mherger
2018-01-25, 12:29
I'm running spotty on a ds214 with LMS 7.9.1-1504317335, spotty helper app (v0.9.0) and none of the players are checked for connect.

Please see http://forums.slimdevices.com/showthread.php?108561-Announce-Spotty-2-0-0-Spotify-Connect-for-your-Squeezebox&p=905214&viewfull=1#post905214

tfec
2018-01-25, 13:17
Just tried 2.2.1
When I uncheck the "Don't announce..." option
... I see no player on my spotify devices.

When I check the option I emmidiatly see the player appearing in my Spotify Devices menu.
Here the same with 2.2.1. I lost all players as spotify devices. Then I changed my LMS to a backupped system from late 2017 and all player came back. After rebooting the LMS the spotty plugin was automatically updated and all players lost until I checked the switch to hide them. Now they went unhidden, viewable ... :confused:

2eleven
2018-01-25, 19:41
> I don't think this has been asked before (my search didn't turn up any
> results). Is there a way to unfollow an artist? I couldn't find a way,

I'm sorry, no. This currently isn't available. I'll add it to my list.


Many thanks - it will be much appreciated!

jsmathers
2018-01-26, 12:16
Michael, I have just noticed an issue with the Connect feature. This may have existed in previous versions, I'm not sure. I'm running Spotty 2.1.1 and LMS 7.9.1 on a Synology DS414. FYI it appears to now be necessary for me to enable "Don't announce Squeezebox players" in the Advanced settings to get my SB players to show up in the Spotify App.

Here are the issues I am seeing:
1. Play a playlist from the Spotify app. Pause music from LMS Web UI (Spotify App shows music as paused). Play music from LMS Web UI (Music starts playing, but Spotify App does not update status... still shows as paused.) If I wait till the end of the song, the next song starts playing and then the Spotify App updates status correctly at this point. This behavior is OK, as it is able to recover... but not ideal since the Spotify App is in an incorrect state until the next song starts playing.

2. Play a playlist from the Spotify app. Next, I run a script which calls the SB CLI to do the following (among other things)... Pauses the music, call "playlist save" CLI command, play a Google TTS audio alert, wait until alert stops playing, call the "playlist resume" CLI command. Again, the spotify music starts playing, but the Spotify App does not update the status... still shows as paused. However, this time if I wait till the end of the song, the next song in the Spotify playlist does not start playing. Perhaps this is an issue with the "playlist resume" and "playlist save" CLI functionality when using remote streams, but I never noticed this before. Any thoughts or suggestions?

Thanks for taking the time to read this, and for all of your great work on this plugin.

BillatLakeGeorge
2018-01-26, 13:40
Michael it stopped again and I had to uncheck announcements and recheck.

Here is the log immediately after it stopped.

[18-01-26 15:11:06.1244] Plugins::Spotty::Plugin::purgeAudioCacheAfterXTrac ks (432) Played 5 song(s) since last audio cache purge.
[18-01-26 15:11:21.0016] Plugins::Spotty::Plugin::purgeAudioCache (446) Starting audio cache cleanup...
[18-01-26 15:11:21.0050] Plugins::Spotty::Plugin::purgeAudioCache (500) Starting temporary file cleanup... (/volume1/@appstore/SqueezeCenter/Cache/spotty)
[18-01-26 15:11:21.0990] Plugins::Spotty::Plugin::purgeAudioCache (520) Audio cache cleanup done!
[18-01-26 15:14:11.6392] Plugins::Spotty::API::_call (1307) Trying to read from cache for me
[18-01-26 15:14:11.6409] Plugins::Spotty::API::_call (1316) API call: me
[18-01-26 15:14:11.6471] Plugins::Spotty::Connect::getNextTrack (115) We're approaching the end of a track - get the next track
[18-01-26 15:14:11.6512] Plugins::Spotty::API::_call (1316) API call: me/player/next
[18-01-26 15:14:12.1872] Plugins::Spotty::API::__ANON__ (1361) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[18-01-26 15:14:12.1893] Plugins::Spotty::API::__ANON__ (1363) Data cached (https://api.spotify.com/v1/me)
[18-01-26 15:14:12.2154] Plugins::Spotty::API::_call (1316) API call: me/player
[18-01-26 15:14:12.4428] Plugins::Spotty::Connect::__ANON__ (129) Got a new track to be played next: spotify:track:4PTfrK6IhnTOd7SRpH17EK
[18-01-26 15:14:12.4492] Plugins::Spotty::Plugin::purgeAudioCacheAfterXTrac ks (432) Played 1 song(s) since last audio cache purge.
[18-01-26 15:18:08.4308] Plugins::Spotty::API::_call (1307) Trying to read from cache for me
[18-01-26 15:18:08.4326] Plugins::Spotty::API::_call (1316) API call: me
[18-01-26 15:18:08.4387] Plugins::Spotty::Connect::getNextTrack (115) We're approaching the end of a track - get the next track
[18-01-26 15:18:08.4429] Plugins::Spotty::API::_call (1316) API call: me/player/next
[18-01-26 15:18:08.8483] Plugins::Spotty::API::__ANON__ (1361) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[18-01-26 15:18:08.8504] Plugins::Spotty::API::__ANON__ (1363) Data cached (https://api.spotify.com/v1/me)
[18-01-26 15:18:08.8733] Plugins::Spotty::API::_call (1316) API call: me/player
[18-01-26 15:18:09.1014] Plugins::Spotty::Connect::__ANON__ (129) Got a new track to be played next: spotify:track:2NTDt9Fiqp5wTBM6cLO6Bu
[18-01-26 15:18:09.1078] Plugins::Spotty::Plugin::purgeAudioCacheAfterXTrac ks (432) Played 2 song(s) since last audio cache purge.
[18-01-26 15:22:06.6484] Plugins::Spotty::Connect::_connectEvent (230) Got called from spotty helper: start
[18-01-26 15:22:06.6529] Plugins::Spotty::API::_call (1307) Trying to read from cache for me
[18-01-26 15:22:06.6547] Plugins::Spotty::API::_call (1316) API call: me
[18-01-26 15:22:06.6624] Plugins::Spotty::API::_call (1316) API call: me/player
[18-01-26 15:22:07.0792] Plugins::Spotty::API::__ANON__ (1361) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[18-01-26 15:22:07.0816] Plugins::Spotty::API::__ANON__ (1363) Data cached (https://api.spotify.com/v1/me)
[18-01-26 15:22:07.0937] Plugins::Spotty::Connect::__ANON__ (266) Got a new track to be played: spotify:track:2Sqv9Ne6ibOZsKxY7o0t6t
[18-01-26 15:22:07.1233] Plugins::Spotty::API::_call (1307) Trying to read from cache for me
[18-01-26 15:22:07.1254] Plugins::Spotty::API::_call (1310) Returning cached data for me
[18-01-26 15:22:07.1272] Plugins::Spotty::Connect::getNextTrack (109) Don't get next track as we got called by a play track event from spotty
[18-01-26 15:22:07.1331] Plugins::Spotty::Plugin::purgeAudioCacheAfterXTrac ks (432) Played 3 song(s) since last audio cache purge.
[18-01-26 15:22:07.2422] Plugins::Spotty::Connect::_onPause (187) Got a stop event within 5s after start of a new track - do NOT tell Spotify Connect controller to pause
[18-01-26 15:27:08.1088] Plugins::Spotty::API::_call (1307) Trying to read from cache for me
[18-01-26 15:27:08.1106] Plugins::Spotty::API::_call (1316) API call: me
[18-01-26 15:27:08.1167] Plugins::Spotty::Connect::getNextTrack (115) We're approaching the end of a track - get the next track
[18-01-26 15:27:08.1207] Plugins::Spotty::API::_call (1316) API call: me/player/next
[18-01-26 15:27:08.5076] Plugins::Spotty::API::__ANON__ (1361) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[18-01-26 15:27:08.5097] Plugins::Spotty::API::__ANON__ (1363) Data cached (https://api.spotify.com/v1/me)
[18-01-26 15:27:08.5322] Plugins::Spotty::API::_call (1316) API call: me/player
[18-01-26 15:27:08.7771] Plugins::Spotty::Connect::__ANON__ (129) Got a new track to be played next: spotify:track:3inSmIa388icRdpDi5ecJd
[18-01-26 15:27:08.7835] Plugins::Spotty::Plugin::purgeAudioCacheAfterXTrac ks (432) Played 4 song(s) since last audio cache purge.
[18-01-26 15:27:09.3491] Plugins::Spotty::API::_call (1307) Trying to read from cache for me
[18-01-26 15:27:09.3512] Plugins::Spotty::API::_call (1310) Returning cached data for me
[18-01-26 15:27:09.3572] Plugins::Spotty::Connect::getNextTrack (115) We're approaching the end of a track - get the next track
[18-01-26 15:27:09.3671] Plugins::Spotty::API::_call (1316) API call: me/player/next
[18-01-26 15:27:09.6581] Plugins::Spotty::API::_call (1316) API call: me/player
[18-01-26 15:27:09.9402] Plugins::Spotty::Connect::__ANON__ (129) Got a new track to be played next: spotify:track:0Tr5G2mE56eLUGvCaXRM8I

mherger
2018-01-26, 15:05
> Michael it stopped again and I had to uncheck announcements and
> recheck.
>
> Here is the log immediately after it stopped.

And you wouldn't have the log from when it happened?...

--

Michael

Mj4586
2018-01-26, 16:20
Hi, first post here and wasn't sure if I should post in this thread or elsewhere.

I'm using Spotty 2.1.1 on a Joggler with LMS 7.7.3 and it's working well when I select 160kbs but if I try 320kbs the tracks always stop around 20 seconds before the end and restart at the beginning. Has anyone come across this problem before and if so is there a solution. I don't think I can update the LMS within the squeezebox OS, although I'm not sure.

Any help would be really appreciated.

Man in a van
2018-01-27, 03:48
@Mj4586

Welcome to the forum.:)

Yes a new thread would have been best and posting it over at the Joggler forum maybe even better (https://www.jogglerwiki.com/forum/):p

LMS can be updated without a problem, which version of Squeezeplay OS are you using? and is it internal (or external on a USB stick?).

ronnie

You can pm me for advice or start a new thread.:D

Are you Spotify Premium?

BillatLakeGeorge
2018-01-27, 06:20
> Michael it stopped again and I had to uncheck announcements and
> recheck.
>
> Here is the log immediately after it stopped.

And you wouldn't have the log from when it happened?...

--

Michael

The log shows everything from 15 minutes before up to stopping.

Mj4586
2018-01-27, 07:16
Thanks Man in a van, I've posted over there.

gert
2018-01-28, 04:25
hi,

I have some problems, running spotty on my brand new DS218.
DSM 6.1.4-15217 Update 5
LMS 7.9.1-166
Spotty V 2.1.1 installed.
Unfortunately, i cannot find the correct LMS update. Can i use another one?




Error message in the settings:

There has been a problem running the Spotty helper application. Most likely your operating system and/or platform is not supported. Please report the following details to me:

Operating system: Synology DiskStation / aarch64-linux

Helper Applications Folder:
/volume1/@appstore/SqueezeCenter/Bin
/sbin
/bin
/usr/sbin
/usr/bin
/usr/syno/sbin
/usr/syno/bin
/usr/local/sbin
/usr/local/bin
/usr/libexec
/volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin
/volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux
sh: ldd: command not found

Log error:
24439

mherger
2018-01-28, 04:48
> I have some problems, running spotty on my brand new DS218.

> Operating system: Synology DiskStation / aarch64-linux

Oh... Ok, I might have been wrong. It is an aarch64?!? You then need
that additional Spotty Helper for AARCH64 plugin. I thought DS218 wasn't
armv8.

--

Michael

gert
2018-01-28, 05:01
Hi Michael,

This is what I know:

The CPU is a Realtek RTD 1296 (quadcore) ARMv8 model

The exact ID is ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.7.0, stripped

I will try the Helper App, and will let you know.

gert
2018-01-28, 05:07
Works like a charm!!

Thanks Michael, many kudo's
:D

Wigster
2018-01-28, 07:00
What's new in 2.2.1?
Tom

Hi Michael,

My LMS is not offering 2.2.1 in the plugins list. It’s still 2.1.1. I am on Windows with the latest nightly LMS.


Sent from my iPhone using Tapatalk

stgiese
2018-01-28, 07:45
Hi Michael,

is there a way to use the spotify-plugin with just a free-spotty-acount???
Or am I out of the game with my free acount...

Regards,
Stefan

mherger
2018-01-28, 08:02
> is there a way to use the spotify-plugin with just a
> free-spotty-acount???

No, you need a premium account.

--

Michael

Tomsen77
2018-01-28, 11:39
Since I got the Update notification this morning Spotty was gone.

I tried several times to activate the plugin with no success.

In the server log This line shows me the Problem:


[18-01-28 18:51:19.5240] Slim::Utils::PluginDownloader::_downloadError (217) unable to download Spotty from hxxp://downloads.nixda.ch/Spotty-2.1.1.zip - 403 Forbidden

Via Webbroser I can download the ZIP file but on LMS on my Pi and also on my DS214play i get this Error message after pressing the botton to restart the server.

Is there something wron on the repo?

Tomsen77
2018-01-28, 11:44
since I was notified about the updated plugin this morning I get this error message everytime i try to update or activate the spotty plugin


[18-01-28 18:51:19.5240] Slim::Utils::PluginDownloader::_downloadError (217) unable to download Spotty from h t t p://downloads.nixda.ch/Spotty-2.1.1.zip - 403 Forbidden

manuallyI can download the zip file

Is there something wron with the repo?

mherger
2018-01-28, 11:52
Slim::Utils::PluginDownloader::_downloadError (217) unable to download Spotty from h t t p://downloads.nixda.ch/Spotty-2.1.1.zip - 403 Forbidden

That's odd. Cloudflare might be "protecting" the URL a bit too aggressively. Can you try again later?

I guess your LMS is behind the same IP address as you are browsing from?

Tomsen77
2018-01-28, 12:14
Yes, suddenly it works.
Nao everything is up and running again.

Thanks for your great work.

kidstypike
2018-01-28, 14:48
Hi Michael,

My LMS is not offering 2.2.1 in the plugins list. It’s still 2.1.1. I am on Windows with the latest nightly LMS.


Sent from my iPhone using Tapatalk

I think 2.2.1 was a typo, latest Spotty is 2.1.1.

dimmer
2018-01-28, 21:31
I'm new to Spotify and this project has breathed some new life into my LMS system.
I just started using spotty and have been reading the threads.
It is obvious that Michael is putting countless hours into this project.
I'm using a Windows server and am looking forward to testing the latest version ... keep up the great work!

ButC
2018-01-29, 01:26
> Skip doesn't seem to work at all when playing via Squeezelite.

Are you sure you haven't enabled track repeat?

--

Michael

This happened to me again: The first song of the playlist repeats itself infinetely. The solution is once again the same - turn Repeat ON and then turn it OFF. So, it seems there's a bug somewhere. To be clear, I hadn't turned Repeat On before the problem occurred. Nor had I last time it happened

It's not a huge problem, just thought I'd mention it.

I could add that I had to untick and retick the box for my player (Squeezelite) under the plugins Spotty settings, in order for my device to be discovered from the Spotify android app.

MathSWE
2018-01-29, 02:41
Here the same with 2.2.1. I lost all players as spotify devices. Then I changed my LMS to a backupped system from late 2017 and all player came back. After rebooting the LMS the spotty plugin was automatically updated and all players lost until I checked the switch to hide them. Now they went unhidden, viewable ... :confused:

Same issue here - after updating to 2.1.1 all my squeezeboxes vanished from the Spotify Android app. But putting a check-marker in the "Don't announce Squeezebox players"-box actually makes them appear again, quite the contrary to expectations from that option! ;)

mherger
2018-01-29, 03:06
Same issue here - after updating to 2.1.1 all my squeezeboxes vanished from the Spotify Android app. But putting a check-marker in the "Don't announce Squeezebox players"-box actually makes them appear again, quite the contrary to expectations from that option! ;)

What kind of system are you running LMS on?

MathSWE
2018-01-29, 03:35
What kind of system are you running LMS on?

Linux NOSTROMO 3.4.6 #1 SMP Sat Dec 30 05:40:30 CST 2017 x86_64 GNU/Linux

It is a QNAP TS-469 Pro.

Update: hmm.... the behaviour is a bit odd, Ill try to explain. Let me know what logs you might need.

1. Enabling "Don't announce" makes the players pop up in the Android app, but then they disappear.
2. Disabling "Don't announce" does nothing
3. Re-enabling "Don't" announce" made them pop back.

But then after disappearing again they just wont pop back whatever I do.

The only line in the server logs about Spotty is:


[18-01-29 11:31:33.6843] Plugins::Spotty::API::__ANON__ (1373) Invalid data


How can I get better logs foor you?

slartibartfast
2018-01-29, 03:38
Linux NOSTROMO 3.4.6 #1 SMP Sat Dec 30 05:40:30 CST 2017 x86_64 GNU/Linux

It is a QNAP TS-469 Pro.

Update: hmm.... the behaviour is a bit odd, Ill try to explain. Let me know what logs you might need.

1. Enabling "Don't announce" makes the players pop up in the Android app, but then they disappear.
2. Disabling "Don't announce" does nothing
3. Re-enabling "Don't" announce" made them pop back.

But then after disappearing again they just wont pop back whatever I do.

The only line in the server logs about Spotty is:


[18-01-29 11:31:33.6843] Plugins::Spotty::API::__ANON__ (1373) Invalid data


How can I get better logs foor you?Have you tried rebooting the NAS? I saw similar behaviour on my PI. Rebooting seemed to fix it.

Sent from my SM-G900F using Tapatalk

MathSWE
2018-01-29, 04:01
Have you tried rebooting the NAS? I saw similar behaviour on my PI. Rebooting seemed to fix it.

Sent from my SM-G900F using Tapatalk

Tried that no with no result - and now I cant get my squeezeboxes to show up at all anymore.

slartibartfast
2018-01-29, 04:07
Tried that no with no result - and now I cant get my squeezeboxes to show up at all anymore.In that case restart LMS. It may have started before the network was available.

Sent from my SM-G900F using Tapatalk

MathSWE
2018-01-29, 05:17
In that case restart LMS. It may have started before the network was available.

Sent from my SM-G900F using Tapatalk

That did it! Thanks for the tip!! Note that the option "Dont announce" is still enabled so thats kind of opposite of its purpose.

Michael - is there something you can do to fix for the case of LMS starting before network is available?

mherger
2018-01-29, 05:22
> It is a QNAP TS-469 Pro.

Ok. I bet it's running avahi. There's a known issue with the underlying
librespot if avahi is already running on a system. I should try to at
least not have it crash. Thanks for the feedback!

> But then after disappearing again they just wont pop back whatever I
> do.

That's not good. Could you check what spotty process there would be left
running ("ps ax | grep spotty")?

--

Michael

mherger
2018-01-29, 05:26
> This happened to me again: The first song of the playlist repeats itself
> infinetely. The solution is once again the same - turn Repeat ON and
> then turn it OFF. So, it seems there's a bug somewhere. To be clear, I
> hadn't turned Repeat On before the problem occurred. Nor had I last
> time it happened :)

The most recent entries in your server.log point at a networking issue.
But in this case you wouldn't have been able to play at all. There are
messages not only from spotty, but from LMS failing to reach TuneIn or
mysb.com, too. When did it happen? There are other messages from a few
days ago.

--

Michael

slartibartfast
2018-01-29, 05:48
That did it! Thanks for the tip!! Note that the option "Dont announce" is still enabled so thats kind of opposite of its purpose.

Michael - is there something you can do to fix for the case of LMS starting before network is available?I have "don't announce" unchecked now and it seems to work. I am not entirely sure what that option is meant to do.

Sent from my SM-G900F using Tapatalk

mherger
2018-01-29, 06:10
> I have "don't announce" unchecked now and it seems to work. I am not
> entirely sure what that option is meant to do.

Spotify Connect clients are registered on Spotify's back-end. But you'd
only see those devices if your app was connected using the same
credentials as all those clients. If your family members/friends
visiting you etc. want to play on such a Squeezebox, they wouldn't see
it, as they are using a different Spotify account. With the local
announcement enabled, Spotify apps would discover them if they were on
the same network, even if using different credentials. This allows your
visitors to play their tunes on your SB without any configuration work.

Unfortunately this announcement code seems to conflict with avahi, which
often is being used to announce services in the local network on NAS
devices. In that case spotty currently is crashing. Therefore you can
enable that mode.

--

Michael

ButC
2018-01-29, 07:49
> This happened to me again: The first song of the playlist repeats itself
> infinetely. The solution is once again the same - turn Repeat ON and
> then turn it OFF. So, it seems there's a bug somewhere. To be clear, I
> hadn't turned Repeat On before the problem occurred. Nor had I last
> time it happened :)

The most recent entries in your server.log point at a networking issue.
But in this case you wouldn't have been able to play at all. There are
messages not only from spotty, but from LMS failing to reach TuneIn or
mysb.com, too. When did it happen? There are other messages from a few
days ago.

--

Michael

I'll present a new log next time it happens. A few minutes went by between the Repeat ON/OFF and the unticking of the settings so it might be a bit back. But next time I'll upload the log immediately when it happens.

jsmathers
2018-01-29, 10:00
I already posted about this a few pages back, but I didn't see any response. Is anyone else seeing the issue where if you start playing music from the Spotify Android App (or Windows App), and then pause and then play in the LMS Web UI, that the Spotify Android App status does not update as playing? The same issues applies if you skip ahead or back in the track in the LMS UI... the time doesn't update in the Spotify Android App.

The Spotify App status usually syncs back up on the next song, but I have seen cases where this does not happen.... and the music stop playing completely.

slartibartfast
2018-01-29, 10:16
I already posted about this a few pages back, but I didn't see any response. Is anyone else seeing the issue where if you start playing music from the Spotify Android App (or Windows App), and then pause and then play in the LMS Web UI, that the Spotify Android App status does not update as playing? The same issues applies if you skip ahead or back in the track in the LMS UI... the time doesn't update in the Spotify Android App.

The Spotify App status usually syncs back up on the next song, but I have seen cases where this does not happen.... and the music stop playing completely.Yes I just tried this to test it and see the same. Another strange thing I have seen is that when playing tracks using Spotify connect, if I start playing tracks from my local music collection the first track will start playing and stop almost immediately.

Sent from my SM-G900F using Tapatalk

Huey11
2018-01-29, 14:14
I already posted about this a few pages back, but I didn't see any response. Is anyone else seeing the issue where if you start playing music from the Spotify Android App (or Windows App), and then pause and then play in the LMS Web UI, that the Spotify Android App status does not update as playing? The same issues applies if you skip ahead or back in the track in the LMS UI... the time doesn't update in the Spotify Android App.

The Spotify App status usually syncs back up on the next song, but I have seen cases where this does not happen.... and the music stop playing completely.

Are you sure it stops: I have the issue it starts but with the volume all the way down to 0 on LMS... When I crank it up it stays up for most songs but sometimes pause again. when reuming, it starts and then again goes to 0 or maybe mute.

Not sure yet on what occasions this happens. On 1.9.something it seemed gone, but i had my LMS on a bananapi. Now reinstalled on a raspberry and with 2.0.0 this starts occurring again. (now on 2.1.1)

mherger
2018-01-29, 23:37
> 1. Play a playlist from the Spotify app. Pause music from LMS Web UI
> (Spotify App shows music as paused). Play music from LMS Web UI (Music
> starts playing, but Spotify App does not update status... still shows as
> paused.)

I think I've seen this, too. Noted.

> 2. Play a playlist from the Spotify app. Next, I run a script which
> calls the SB CLI to do the following (among other things)... Pauses the
> music, call "playlist save" CLI command, play a Google TTS audio alert,
> wait until alert stops playing, call the "playlist resume" CLI command.
> Again, the spotify music starts playing, but the Spotify App does not
> update the status... still shows as paused. However, this time if I
> wait till the end of the song, the next song in the Spotify playlist
> does not start playing. Perhaps this is an issue with the "playlist
> resume" and "playlist save" CLI functionality when using remote streams,
> but I never noticed this before. Any thoughts or suggestions?

Ok, that's likely an issue with the playlist commands I'm not listening
to. Will take a look into this, too. BTW: aren't you doing what the
"playlist preview" command would do automatically?

--

Michael

MathSWE
2018-01-30, 07:39
> It is a QNAP TS-469 Pro.

Ok. I bet it's running avahi. There's a known issue with the underlying
librespot if avahi is already running on a system. I should try to at
least not have it crash. Thanks for the feedback!

> But then after disappearing again they just wont pop back whatever I
> do.

That's not good. Could you check what spotty process there would be left
running ("ps ax | grep spotty")?

--

Michael

Sure thing, I dont know where the linefeeds should be but here goes:

9209 squeezeb 2868 S < /share/MD0_DATA/.qpkg/LogitechMediaServer/SlimServer/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c /share/MD0_DATA/.qpkg/LogitechMediaServer/SlimServer/Cache/spotty/cce851dd -n Squeezeboxen --disable-audio-cache --bitrate 96 --player-mac 00:04:20:1e:d7:17 --lms 192.168.0.157:9001 --disable-discovery
15468 squeezeb 2148 S < /share/MD0_DATA/.qpkg/LogitechMediaServer/SlimServer/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -n Squeezebox -c /share/MD0_DATA/.qpkg/LogitechMediaServer/SlimServer/Cache/spotty/cce851dd --single-track spotify://track:41C4fZ0CiHyJjw3iaxwrQH --bitrate 320 --disable-discovery --disable-audio-cache
15672 mathias 704 S grep spotty

However, since I rebooted the NAS and then restarted the LMS it has been working flawless! BR //Mathias

slartibartfast
2018-01-30, 07:43
I have an issue which can be reproduced as follows.
1. Play something using Connect.
2. While this is playing select a local music track or Radio station and play it.
3. The local track will play for a few seconds then stop.
4. Player volume also gets set to zero occasionally when this test is repeated.

Sent from my SM-G900F using Tapatalk

jsmathers
2018-01-30, 09:03
I originally considered using the "playlist preview" CLI command for my script, but I needed to break up the save and resume parts so the TTS alert could be played elsewhere... but now I have everything in one script, so I may try the "playlist preview" approach again. Thanks!


> 1. Play a playlist from the Spotify app. Pause music from LMS Web UI
> (Spotify App shows music as paused). Play music from LMS Web UI (Music
> starts playing, but Spotify App does not update status... still shows as
> paused.)

I think I've seen this, too. Noted.

> 2. Play a playlist from the Spotify app. Next, I run a script which
> calls the SB CLI to do the following (among other things)... Pauses the
> music, call "playlist save" CLI command, play a Google TTS audio alert,
> wait until alert stops playing, call the "playlist resume" CLI command.
> Again, the spotify music starts playing, but the Spotify App does not
> update the status... still shows as paused. However, this time if I
> wait till the end of the song, the next song in the Spotify playlist
> does not start playing. Perhaps this is an issue with the "playlist
> resume" and "playlist save" CLI functionality when using remote streams,
> but I never noticed this before. Any thoughts or suggestions?

Ok, that's likely an issue with the playlist commands I'm not listening
to. Will take a look into this, too. BTW: aren't you doing what the
"playlist preview" command would do automatically?

--

Michael

slartibartfast
2018-02-01, 05:49
I have an issue which can be reproduced as follows.
1. Play something using Connect.
2. While this is playing select a local music track or Radio station and play it.
3. The local track will play for a few seconds then stop.
4. Player volume also gets set to zero occasionally when this test is repeated.

Sent from my SM-G900F using TapatalkNobody else seen this?

Sent from my SM-G900F using Tapatalk

mherger
2018-02-01, 06:23
> Nobody else seen this?

I think I did. And it's pretty high up on my todo list.

--

Michael

slartibartfast
2018-02-01, 06:57
> Nobody else seen this?

I think I did. And it's pretty high up on my todo list.

--

MichaelThanks Michael.

Sent from my SM-G900F using Tapatalk

mherger
2018-02-01, 09:45
v2.1.2 tries to fix the "pause after local track plays" issue. Please
test. Thanks!

--

Michael

loopguru
2018-02-01, 10:10
v2.1.2 tries to fix the "pause after local track plays" issue. Please test.
Fixed now! :)
Tom

slartibartfast
2018-02-01, 10:44
Fixed now! :)
Tom+1 :)

Sent from my SM-G900F using Tapatalk

Squid
2018-02-01, 11:38
Since a couple days, spotty.exe is crashing on me on Windows10 running LMS 7.9.0. I don't recall the last time that I successfully used Spotty but it's probably not that long ago.
The crash happens as soon as I select the Spotty application in either the Web UI or my Squeezebox apps (Squeezepad on IOS or Squeeze Commander on Android). The crash actually blocks LMS entirely until on the server I go click 'Close Program' in the Spotty.exe crash popup.
The crash happens regardless of whether I have 'Spotify Connect' checkbox ticked or not.

The versions numbers are 2.1.2 for Spotty and 0.9.0 for Spotty Helper.

This is what I see in the logs :
[18-02-01 19:36:06.9503] Plugins::Spotty::API::getToken (125) Failed to get Spotify access token: 'true' expected, at character offset 0 (before "thread 'main' panick...") at C:\ProgramData\Squeezebox\Cache\InstalledPlugins/Plugins/Spotty/API.pm line 122.

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 123, message: "The filename, directory name, or volume label syntax is incorrect." } }', src\libcore\result.rs:860
note: Run with `RUST_BACKTRACE=1` for a backtrace.
[18-02-01 19:36:06.9506] Plugins::Spotty::API::getToken (142) Failed to get Spotify access token

PaulinPosset
2018-02-01, 12:14
Since a couple days, spotty.exe is crashing on me on Windows10 running LMS 7.9.0. I don't recall the last time that I successfully used Spotty but it's probably not that long ago.
The crash happens as soon as I select the Spotty application in either the Web UI or my Squeezebox apps (Squeezepad on IOS or Squeeze Commander on Android). The crash actually blocks LMS entirely until on the server I go click 'Close Program' in the Spotty.exe crash popup.
The crash happens regardless of whether I have 'Spotify Connect' checkbox ticked or not.

The versions numbers are 2.1.2 for Spotty and 0.9.0 for Spotty Helper.

This is what I see in the logs :
[18-02-01 19:36:06.9503] Plugins::Spotty::API::getToken (125) Failed to get Spotify access token: 'true' expected, at character offset 0 (before "thread 'main' panick...") at C:\ProgramData\Squeezebox\Cache\InstalledPlugins/Plugins/Spotty/API.pm line 122.

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 123, message: "The filename, directory name, or volume label syntax is incorrect." } }', src\libcore\result.rs:860
note: Run with `RUST_BACKTRACE=1` for a backtrace.
[18-02-01 19:36:06.9506] Plugins::Spotty::API::getToken (142) Failed to get Spotify access token

I too have just experienced a problem with Spotty.exe on a Win 7 machine crashing after updating to spotty version 2 .1.2. Fortunately had version 2.1.0 on another machine so deleted the 2.1.2 spotty folder in ‘installed plugins’ and transferred the 2.1.0 folder from the second machine. Restarted LMS and all working OK.

Haven’t got a log or know if 2.1.1 worked without crashing but 2.1.2 definitely crashes and 2.1.0 doesn’t!

LMS version 7.9.1-1516947667 Win 7

mherger
2018-02-01, 13:14
> I too have just experienced a problem with Spotty.exe on a Win 7 machine
> crashing after updating to spotty version 2 .1.2. Fortunately had
> version 2.1.0 on another machine so deleted the 2.1.2 spotty folder in
> ‘installed plugins’ and transferred the 2.1.0 folder from the second
> machine. Restarted LMS and all working OK.

Hmm... the spotty.exe file has not changed since 2.0.0. I doubt 2.1.0
would behave differently than 2.1.2. There must be something else
triggering the problem.

Do you see the same error message as the one you quoted?

> Haven’t got a log or know if 2.1.1 worked without crashing but 2.1.2
> definitely crashes and 2.1.0 doesn’t!

I doubt it :-P. Maybe a temporary hiccup which happened while you were
using 2.1.2, and disappeared when you downgraded.

--

Michael

mherger
2018-02-01, 13:20
[18-02-01 19:36:06.9503] Plugins::Spotty::API::getToken (125) Failed to get Spotify access token: 'true' expected, at character offset 0 (before "thread 'main' panick...") at C:\ProgramData\Squeezebox\Cache\InstalledPlugins/Plugins/Spotty/API.pm line 122.

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 123, message: "The filename, directory name, or volume label syntax is incorrect." } }', src\libcore\result.rs:860
note: Run with `RUST_BACKTRACE=1` for a backtrace.
[18-02-01 19:36:06.9506] Plugins::Spotty::API::getToken (142) Failed to get Spotify access token

Could you please set logging for plugin.spotty to INFO, then reproduce the issue. Then provide the server.log. Above error message means that the helper tries to access a file it can't find. From the server.log I might see what it tries to do, what files/folders it's trying to access.

mherger
2018-02-01, 14:05
> Haven’t got a log or know if 2.1.1 worked without crashing but 2.1.2
> definitely crashes and 2.1.0 doesn’t!

I doubt it :-P. Maybe a temporary hiccup which happened while you were
using 2.1.2, and disappeared when you downgraded.

Oh... I was wrong... it's not the binary which is causing the crash, but the way how I start it. 2.1.3 should fix the crash on Windows. Please test. Thanks!

PaulinPosset
2018-02-01, 14:09
> I too have just experienced a problem with Spotty.exe on a Win 7 machine
> crashing after updating to spotty version 2 .1.2. Fortunately had
> version 2.1.0 on another machine so deleted the 2.1.2 spotty folder in
> ‘installed plugins’ and transferred the 2.1.0 folder from the second
> machine. Restarted LMS and all working OK.

Hmm... the spotty.exe file has not changed since 2.0.0. I doubt 2.1.0
would behave differently than 2.1.2. There must be something else
triggering the problem.

Do you see the same error message as the one you quoted?

> Haven’t got a log or know if 2.1.1 worked without crashing but 2.1.2
> definitely crashes and 2.1.0 doesn’t!

I doubt it :-P. Maybe a temporary hiccup which happened while you were
using 2.1.2, and disappeared when you downgraded.

--

Michael

Yes I could see from the file dates that spotty.exe itself hadn’t changed so agree it must be something else that changed. But whatever has been changed definitely caused both spotty and LMS to stop working. After several restarts of LMS and consequent spotty crashes I decided to ‘downgrade’ to the earlier version which has been playing without issue.

Edit: Can see you’re onto the problem! Thanks👍

PaulinPosset
2018-02-01, 14:19
Oh... I was wrong... it's not the binary which is causing the crash, but the way how I start it. 2.1.3 should fix the crash on Windows. Please test. Thanks!

2.1.3 working fine. Thanks for quick fix! 👍👍👍

BillatLakeGeorge
2018-02-01, 15:00
Server log after crashing with 2.1.3


[18-02-01 16:29:43.8309] Plugins::Spotty::API::__ANON__ (1364) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[18-02-01 16:29:43.8330] Plugins::Spotty::API::__ANON__ (1366) Data cached (https://api.spotify.com/v1/me)
[18-02-01 16:29:43.8526] Plugins::Spotty::API::_call (1319) API call: me/player
[18-02-01 16:29:44.0844] Plugins::Spotty::Connect::__ANON__ (129) Got a new track to be played next: spotify:track:7Gr61S9VTm8fcYfAo4Fd9g
[18-02-01 16:29:44.0907] Plugins::Spotty::Plugin::purgeAudioCacheAfterXTrac ks (432) Played 5 song(s) since last audio cache purge.
[18-02-01 16:29:59.0016] Plugins::Spotty::Plugin::purgeAudioCache (446) Starting audio cache cleanup...
[18-02-01 16:29:59.0034] Plugins::Spotty::Plugin::purgeAudioCache (500) Starting temporary file cleanup... (/volume1/@appstore/SqueezeCenter/Cache/spotty)
[18-02-01 16:29:59.0063] Plugins::Spotty::Plugin::purgeAudioCache (520) Audio cache cleanup done!
[18-02-01 16:35:34.4248] Plugins::Spotty::API::_call (1310) Trying to read from cache for me
[18-02-01 16:35:34.4266] Plugins::Spotty::API::_call (1319) API call: me
[18-02-01 16:35:34.4326] Plugins::Spotty::Connect::getNextTrack (115) We're approaching the end of a track - get the next track
[18-02-01 16:35:34.4369] Plugins::Spotty::API::_call (1319) API call: me/player/next
[18-02-01 16:35:34.8197] Plugins::Spotty::API::__ANON__ (1364) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[18-02-01 16:35:34.8218] Plugins::Spotty::API::__ANON__ (1366) Data cached (https://api.spotify.com/v1/me)
[18-02-01 16:35:34.8387] Plugins::Spotty::API::_call (1319) API call: me/player
[18-02-01 16:35:35.0757] Plugins::Spotty::Connect::__ANON__ (129) Got a new track to be played next: spotify:track:02BsTeJE4q5gWOTt58ur5U
[18-02-01 16:35:35.0820] Plugins::Spotty::Plugin::purgeAudioCacheAfterXTrac ks (432) Played 1 song(s) since last audio cache purge.
[18-02-01 16:40:29.4607] Plugins::Spotty::API::_call (1310) Trying to read from cache for me
[18-02-01 16:40:29.4624] Plugins::Spotty::API::_call (1319) API call: me
[18-02-01 16:40:29.4686] Plugins::Spotty::Connect::getNextTrack (115) We're approaching the end of a track - get the next track
[18-02-01 16:40:29.4727] Plugins::Spotty::API::_call (1319) API call: me/player/next
[18-02-01 16:40:29.8470] Plugins::Spotty::API::__ANON__ (1364) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[18-02-01 16:40:29.8491] Plugins::Spotty::API::__ANON__ (1366) Data cached (https://api.spotify.com/v1/me)
[18-02-01 16:40:29.9179] Plugins::Spotty::API::_call (1319) API call: me/player
[18-02-01 16:40:30.1563] Plugins::Spotty::Connect::__ANON__ (129) Got a new track to be played next: spotify:track:4UK1g9Z1lWedkmIQuSyCe5
[18-02-01 16:40:30.1628] Plugins::Spotty::Plugin::purgeAudioCacheAfterXTrac ks (432) Played 2 song(s) since last audio cache purge.
[18-02-01 16:47:03.3246] Plugins::Spotty::API::_call (1310) Trying to read from cache for me
[18-02-01 16:47:03.3265] Plugins::Spotty::API::_call (1319) API call: me
[18-02-01 16:47:03.3325] Plugins::Spotty::Connect::getNextTrack (115) We're approaching the end of a track - get the next track
[18-02-01 16:47:03.3372] Plugins::Spotty::API::_call (1319) API call: me/player/next
[18-02-01 16:47:03.7139] Plugins::Spotty::API::__ANON__ (1364) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[18-02-01 16:47:03.7160] Plugins::Spotty::API::__ANON__ (1366) Data cached (https://api.spotify.com/v1/me)
[18-02-01 16:47:04.3867] Plugins::Spotty::API::_call (1319) API call: me/player
[18-02-01 16:47:04.6211] Plugins::Spotty::Connect::__ANON__ (129) Got a new track to be played next: spotify:track:0ofHAoxe9vBkTCp2UQIavz
[18-02-01 16:47:04.6276] Plugins::Spotty::Plugin::purgeAudioCacheAfterXTrac ks (432) Played 3 song(s) since last audio cache purge.
[18-02-01 16:51:21.1257] Plugins::Spotty::API::_call (1310) Trying to read from cache for me
[18-02-01 16:51:21.1276] Plugins::Spotty::API::_call (1319) API call: me
[18-02-01 16:51:21.1335] Plugins::Spotty::Connect::getNextTrack (115) We're approaching the end of a track - get the next track
[18-02-01 16:51:21.1378] Plugins::Spotty::API::_call (1319) API call: me/player/next
[18-02-01 16:51:21.1695] Plugins::Spotty::API::__ANON__ (1364) Caching result for 60 using max-age (https://api.spotify.com/v1/me)
[18-02-01 16:51:21.1717] Plugins::Spotty::API::__ANON__ (1366) Data cached (https://api.spotify.com/v1/me)
[18-02-01 16:51:21.1835] Plugins::Spotty::API::_call (1319) API call: me/player
[18-02-01 16:51:21.2100] Plugins::Spotty::Connect::__ANON__ (129) Got a new track to be played next: spotify:track:0ofHAoxe9vBkTCp2UQIavz
[18-02-01 16:51:21.2114] Plugins::Spotty::Connect::__ANON__ (135) Stopping playback, as we have likely reached the end of our context (playlist, album, ...)
[18-02-01 16:51:21.2182] Plugins::Spotty::Plugin::purgeAudioCacheAfterXTrac ks (432) Played 4 song(s) since last audio cache purge.
[18-02-01 16:51:21.2679] Plugins::Spotty::API::_call (1319) API call: me/player/pause?device_id=a4c6d9db3f3d500210e260dde1126bfeb9 5e4e91
[18-02-01 16:51:31.2894] Plugins::Spotty::API::_call (1310) Trying to read from cache for me
[18-02-01 16:51:31.2913] Plugins::Spotty::API::_call (1313) Returning cached data for me
[18-02-01 16:51:31.2930] Plugins::Spotty::Connect::getNextTrack (109) Don't get next track as we got called by a play track event from spotty

Squid
2018-02-02, 00:21
UPDATE (Solved) : Problem went away after I removed my account in the Spotty settings, and then re-created device account in Spotify and entered the credentials in Spotty.




Could you please set logging for plugin.spotty to INFO, then reproduce the issue. Then provide the server.log. Above error message means that the helper tries to access a file it can't find. From the server.log I might see what it tries to do, what files/folders it's trying to access.

INFO didn't seem to reveal much more so opted for DEBUG. Even then not sure if it is that helpful. The cachefolder does exist.


[18-02-02 08:18:13.8644] Plugins::Spotty::API::getToken (98) Didn't find cached token. Need to refresh.
[18-02-02 08:18:13.8660] Plugins::Spotty::API::getToken (118) Trying to get access token: C:\PROGRA~3\SQUEEZ~1\Cache\INSTAL~1\Plugins\Spotty \Bin\MSWIN3~1\spotty.exe -n Squeezebox -c 'C:\ProgramData\Squeezebox\Cache\spotty\03f3660b' -i abcdef1234567890 --get-token --scope 'user-read-private,user-follow-modify,user-follow-read,user-library-read,user-library-modify,user-top-read,user-read-recently-played,user-read-playback-state,user-modify-playback-state,playlist-read-private,playlist-read-collaborative,playlist-modify-public,playlist-modify-private'
[18-02-02 08:18:22.7929] Plugins::Spotty::API::getToken (121) Got response: thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 123, message: "The filename, directory name, or volume label syntax is incorrect." } }', src\libcore\result.rs:860
note: Run with `RUST_BACKTRACE=1` for a backtrace.
[18-02-02 08:18:22.7933] Plugins::Spotty::API::getToken (125) Failed to get Spotify access token: 'true' expected, at character offset 0 (before "thread 'main' panick...") at C:\ProgramData\Squeezebox\Cache\InstalledPlugins/Plugins/Spotty/API.pm line 122.

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 123, message: "The filename, directory name, or volume label syntax is incorrect." } }', src\libcore\result.rs:860
note: Run with `RUST_BACKTRACE=1` for a backtrace.
[18-02-02 08:18:22.7935] Plugins::Spotty::API::getToken (142) Failed to get Spotify access token


EDIT: after a machine reboot, the behavior is slightly different. Rather than spotty.exe crashing, the cmd.exe that pops up just hangs with no messages. Also then, LMS is completely stuck. This is the DEBUG output :

[18-02-02 09:23:43.2006] Plugins::Spotty::API::getToken (124) Got response: thread 'main' panicked at 'Authentication failed', C:\cygwin\home\mh\git\spotty\target\i686-pc-windows-msvc\release\build\librespot-9051d0392225d7bf\out/lib.rs:369
note: Run with `RUST_BACKTRACE=1` for a backtrace.
^C
[18-02-02 09:23:43.2011] Plugins::Spotty::API::getToken (128) Failed to get Spotify access token: 'true' expected, at character offset 0 (before "thread 'main' panick...") at C:\ProgramData\Squeezebox\Cache\InstalledPlugins/Plugins/Spotty/API.pm line 125.

thread 'main' panicked at 'Authentication failed', C:\cygwin\home\mh\git\spotty\target\i686-pc-windows-msvc\release\build\librespot-9051d0392225d7bf\out/lib.rs:369
note: Run with `RUST_BACKTRACE=1` for a backtrace.
^C
[18-02-02 09:23:43.2013] Plugins::Spotty::API::getToken (145) Failed to get Spotify access token
[18-02-02 09:23:43.2064] Plugins::Spotty::Connect::DaemonManager::initHelpe rs (54) Initializing Spotty Connect helper daemons...
[18-02-02 09:23:43.2403] Slim::Networking::IO::Select::__ANON__ (131) Error: Select task failed calling Slim::Web::HTTP::processHTTP: illegal file descriptor or filehandle (either no attached file descriptor or illegal value): at /Slim/Networking/IO/Select.pm line 134.
; fh=Slim::Web::HTTP::ClientConn=GLOB(0xd578fd4)
[18-02-02 09:23:43.2407] Plugins::Spotty::Connect::DaemonManager::initHelpe rs (54) Initializing Spotty Connect helper daemons...
[18-02-02 09:23:43.3061] Plugins::Spotty::API::getToken (93) Found cached token: -1

mherger
2018-02-02, 01:07
> INFO didn't seem to reveal much more so opted for DEBUG. Even then not
> sure if it is that helpful. The cachefolder does exist.

Did you try the latest 2.1.3 update?

--

Michael

Squid
2018-02-02, 06:29
Did you try the latest 2.1.3 update?


Yes, but see first line of my post (which I added last). The problem was solved by basically clearing my Spotty config and reconfiguring the account.

zen2000
2018-02-02, 08:07
Hello, Spotty quit working after last updates on my PiCore Player version 3.22 running or Rasberry Pi3.
Slim Server version

Logitech Media Server Version: 7.9.1 - 1517314665 @ Tue Jan 30 13:29:18 UTC 2018
Hostname: piCorePlayer
Server IP Address: 192.168.1.26
Server HTTP Port Number: 9000
Operating system: piCore - EN - utf8
Platform Architecture: armv7l-linux
Perl Version: 5.24.0 - arm-linux-gnueabihf-thread-multi-64int
Audio::Scan: 0.95
Database Version: DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
Total Players Recognized: 1

I got this message

There has been a problem running the Spotty helper application. Most likely your operating system and/or platform is not supported. Please report the following details to me:

Operating system: piCore / armv7l-linux

Helper Applications Folder:
/usr/local/slimserver/Bin/armhf-linux
/usr/local/slimserver/Bin
/usr/local/sbin
/usr/local/bin
/sbin
/usr/sbin
/bin
/usr/bin
/usr/local/slimserver/Cache/InstalledPlugins/Plugins/ShairTunes2W/Bin
/usr/local/slimserver/Cache/InstalledPlugins/Plugins/Spotty/Bin
/usr/local/slimserver/Cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux
/usr/local/slimserver/Cache/InstalledPlugins/Plugins/SpottyBinFreeBSD/Bin

mherger
2018-02-02, 08:29
> There has been a problem running the Spotty helper application. Most
> likely your operating system and/or platform is not supported. Please
> report the following details to me:

Hmm... third user reporting this within an hour :-(.

Anything in server.log?

> /usr/local/slimserver/Cache/InstalledPlugins/Plugins/SpottyBinFreeBSD/Bin

Oh, get rid of this plugin. You're not running FreeBSD.

--

Michael

Axel Foley
2018-02-02, 08:35
Hi Michael,

just installed 2.1.3 of the plugin. But when I configure it, I see the following:


There has been a problem running the Spotty helper application. Most likely your operating system and/or platform is not supported. Please report the following details to me:
Operating system: Synology DiskStation / x86_64-linux

Helper Applications Folder:
/volume1/@appstore/SqueezeCenter/Bin
/sbin
/bin
/usr/sbin
/usr/bin
/usr/syno/sbin
/usr/syno/bin
/usr/local/sbin
/usr/local/bin
/usr/libexec
/opt/bin
/volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux
/volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin
sh: ldd: command not found


I only see two plugins available, ARMv8 and macOS. I guess these won't work. Do i need one for my NAS?

Thanks.

zen2000
2018-02-02, 08:39
> There has been a problem running the Spotty helper application. Most
> likely your operating system and/or platform is not supported. Please
> report the following details to me:

Hmm... third user reporting this within an hour :-(.

Anything in server.log?

> /usr/local/slimserver/Cache/InstalledPlugins/Plugins/SpottyBinFreeBSD/Bin

Oh, get rid of this plugin. You're not running FreeBSD.

--

Michael

[18-02-02 09:56:37.4894] main::init (387) Starting Logitech Media Server (v7.9.1, 1517314665, Tue Jan 30 13:29:18 UTC 2018) perl 5.024000 - arm-linux-gnueabihf-thread-multi-64int
[18-02-02 09:56:46.9723] Plugins::NPRRadio::Metadata::init (21) Register NPR meta provider, default icon=
[18-02-02 09:56:48.7872] Plugins::Spotty::Connect::canSpotifyConnect (66) Cannot support Spotty Connect, need at least helper version 0.9.0
[18-02-02 09:56:49.6979] Plugins::ShairTunes2W::Plugin::publishPlayer (380) avahi-publish-player not in path
[18-02-02 09:56:49.6995] Plugins::ShairTunes2W::Plugin::publishPlayer (388) dns-sd not in path
[18-02-02 09:56:49.7011] Plugins::ShairTunes2W::Plugin::publishPlayer (396) mDNSPublish not in path
[18-02-02 09:56:49.7020] Plugins::ShairTunes2W::Plugin::publishPlayer (398) using built-in helper: /usr/local/slimserver/Cache/InstalledPlugins/Plugins/ShairTunes2W/Bin/shairport_helper-armv6hf
[18-02-02 09:56:49.7171] Plugins::ShairTunes2W::Plugin::playerSubscriptionC hange (291) create client Slim::Player::SqueezePlay=ARRAY(0x57444c0) with proc Proc::Background=HASH(0x176dc60)
[18-02-02 09:57:04.3451] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 09:57:33.3835] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 09:57:33.3848] Plugins::Spotty::Connect::canSpotifyConnect (66) Cannot support Spotty Connect, need at least helper version 0.9.0
[18-02-02 09:58:46.0605] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:09:34.5418] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:09:34.5727] Plugins::Spotty::API::getToken (128) Failed to get Spotify access token: malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "(end of string)") at /usr/local/slimserver/Cache/InstalledPlugins/Plugins/Spotty/API.pm line 125.

[18-02-02 10:09:34.5738] Plugins::Spotty::API::getToken (145) Failed to get Spotify access token
[18-02-02 10:09:45.7108] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:10:27.6549] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:14:47.6079] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:18:29.1934] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:18:41.9234] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:18:53.5203] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:18:57.8232] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:19:11.5631] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:19:16.6060] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:25:08.0180] Plugins::ShairTunes2W::Plugin::revoke_publishPlaye r (351) Stop old publish players services:6075
[18-02-02 10:25:08.5267] Plugins::ShairTunes2W::Plugin::shutdownPlugin (263) Killing all processes shairport_helper-armv6hf
[18-02-02 10:25:08.7221] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:25:15.0236] main::init (387) Starting Logitech Media Server (v7.9.1, 1517314665, Tue Jan 30 13:29:18 UTC 2018) perl 5.024000 - arm-linux-gnueabihf-thread-multi-64int
[18-02-02 10:25:22.1755] Plugins::Spotty::Connect::canSpotifyConnect (66) Cannot support Spotty Connect, need at least helper version 0.9.0
[18-02-02 10:25:46.3154] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:25:52.4567] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:26:29.8529] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:26:36.2413] main::init (387) Starting Logitech Media Server (v7.9.1, 1517314665, Tue Jan 30 13:29:18 UTC 2018) perl 5.024000 - arm-linux-gnueabihf-thread-multi-64int
[18-02-02 10:26:45.1311] Plugins::Spotty::Connect::canSpotifyConnect (66) Cannot support Spotty Connect, need at least helper version 0.9.0
[18-02-02 10:27:42.5934] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:27:49.0057] main::init (387) Starting Logitech Media Server (v7.9.1, 1517314665, Tue Jan 30 13:29:18 UTC 2018) perl 5.024000 - arm-linux-gnueabihf-thread-multi-64int
[18-02-02 10:29:52.6467] main::init (387) Starting Logitech Media Server (v7.9.1, 1517314665, Tue Jan 30 13:29:18 UTC 2018) perl 5.024000 - arm-linux-gnueabihf-thread-multi-64int
[18-02-02 10:30:02.9773] Plugins::Spotty::Connect::canSpotifyConnect (66) Cannot support Spotty Connect, need at least helper version 0.9.0
[18-02-02 10:30:20.2337] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:30:43.6058] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:32:07.9589] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!
[18-02-02 10:32:14.3296] main::init (387) Starting Logitech Media Server (v7.9.1, 1517314665, Tue Jan 30 13:29:18 UTC 2018) perl 5.024000 - arm-linux-gnueabihf-thread-multi-64int
[18-02-02 10:32:26.0063] Plugins::Spotty::Connect::canSpotifyConnect (66) Cannot support Spotty Connect, need at least helper version 0.9.0
[18-02-02 10:32:27.5470] Plugins::ShairTunes2W::Plugin::publishPlayer (380) avahi-publish-player not in path
[18-02-02 10:32:27.5487] Plugins::ShairTunes2W::Plugin::publishPlayer (388) dns-sd not in path
[18-02-02 10:32:27.5504] Plugins::ShairTunes2W::Plugin::publishPlayer (396) mDNSPublish not in path
[18-02-02 10:32:27.5513] Plugins::ShairTunes2W::Plugin::publishPlayer (398) using built-in helper: /usr/local/slimserver/Cache/InstalledPlugins/Plugins/ShairTunes2W/Bin/shairport_helper-armv6hf
[18-02-02 10:32:27.5673] Plugins::ShairTunes2W::Plugin::playerSubscriptionC hange (291) create client Slim::Player::SqueezePlay=ARRAY(0x5fefb20) with proc Proc::Background=HASH(0x5b55c18)
[18-02-02 10:32:38.6635] Plugins::Spotty::Plugin::getHelper (638) Didn't find Spotty helper application!

mherger
2018-02-02, 09:42
> just installed 2.1.3 of the plugin. But when I configure it, I see the
> following:
I just pushed out a change which might have been causing this issue
(though I don't understand, as I've been using that changed code all the
time...). Could you please give 2.1.4 another try? Thanks!


--
--

Michael

Axel Foley
2018-02-02, 11:32
> just installed 2.1.3 of the plugin. But when I configure it, I see the
> following:
I just pushed out a change which might have been causing this issue
(though I don't understand, as I've been using that changed code all the
time...). Could you please give 2.1.4 another try? Thanks!


--
--

Michael

Ok, now it starts. Problem: can't authorize. When I put user/pw of my premium account and I hit apply, it says "Authorization failed".



On my spotify windows client, in the spotify connect device list, I already see my 2 squeezeboxes available, it doesn't ask me to authorize Spotty (probably because in the past I already authorized Spotty on LMS).
When I execute the Spotty app on the SB player, it says "Spotify Credentials missing. Please check advanced settings..."

I tried with user/pw instead, and they are correct, already tried logging into spotify via browser.

Here's the INFO level log (I modified my account username from the log):


[18-02-02 19:20:49.5623] main::init (387) Starting Logitech Media Server (v7.9.1, 1503129892, Sat Aug 19 09:00:13 UTC 2017) perl 5.024000 - x86_64-linux
[18-02-02 19:25:51.7117] main::init (387) Starting Logitech Media Server (v7.9.1, 1503129892, Sat Aug 19 09:00:13 UTC 2017) perl 5.024000 - x86_64-linux
[18-02-02 19:26:42.3853] Plugins::Spotty::SettingsAuth::handler (73) Authorization failed:
[18-02-02 19:32:59.0787] Plugins::Spotty::SettingsAuth::handler (73) Authorization failed:
[18-02-02 19:34:22.4262] Plugins::Spotty::SettingsAuth::startHelper (137) Starting authentication deamon: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -a
[18-02-02 19:34:22.7108] Plugins::Spotty::SettingsAuth::startHelper (137) Starting authentication deamon: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -a
[18-02-02 19:34:24.7254] Plugins::Spotty::SettingsAuth::startHelper (137) Starting authentication deamon: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -a
[18-02-02 19:34:26.7282] Plugins::Spotty::SettingsAuth::startHelper (137) Starting authentication deamon: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -a
[18-02-02 19:34:28.7323] Plugins::Spotty::SettingsAuth::startHelper (137) Starting authentication deamon: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -a
[18-02-02 19:34:30.7376] Plugins::Spotty::SettingsAuth::startHelper (137) Starting authentication deamon: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -a
[18-02-02 19:34:32.7332] Plugins::Spotty::SettingsAuth::startHelper (137) Starting authentication deamon: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -a
[18-02-02 19:34:34.3219] Plugins::Spotty::SettingsAuth::handler (66) Trying to authenticate using: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -u '1199702102' -p '********' -a --disable-discovery
[18-02-02 19:34:34.3450] Plugins::Spotty::SettingsAuth::handler (73) Authorization failed:
[18-02-02 19:34:34.3464] Plugins::Spotty::SettingsAuth::startHelper (137) Starting authentication deamon: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -a
[18-02-02 19:34:34.8731] Plugins::Spotty::SettingsAuth::startHelper (137) Starting authentication deamon: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -a
[18-02-02 19:34:36.8589] Plugins::Spotty::SettingsAuth::startHelper (137) Starting authentication deamon: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -a
[18-02-02 19:34:38.8676] Plugins::Spotty::SettingsAuth::startHelper (137) Starting authentication deamon: /volume1/@appstore/SqueezeCenter/Cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64 -c '/volume1/@appstore/SqueezeCenter/Cache/spotty/__AUTHENTICATE__' -n 'Spotify Authorization (Axel's Library)' -a

In the Approved Apps section of spotify website, I can see "Spotty enabled Spotify for Squeezebox" in the list. So it seems that automatic authorization worked.

Any advice?

lopho
2018-02-02, 13:06
Hi
I'm new to spotty. After installation of spotty my credentials aren't accepted in LMS and my premium spotify account doesn't list spotty under apps. Spotty shows up on my squeezebox radios but a message appears that my spotify credentials are missing.
I've read the post about WHS version 1 not being supported. I suppose that I'm running version 2 (see below). Please, could you help me find out what I am missing?

LMS log:
[18-02-02 20:16:23.5892] Plugins::Spotty::SettingsAuth::handler (73) Authorization failed:

My setup:
windows home server 2011 running on an amd 5150 athlon
LMS information:
Logitech Media Server Version: 7.9.1 - 1517314665 @ Tue Jan 30 12:43:23 CUT 2018
Hostname: RIPNAS
Operating system: Windows 2008 Server R2 - EN - cp1252
Platform Architecture: 8664
Perl Version: 5.14.1 - MSWin32-x86-multi-thread
Audio::Scan: 0.95
Database Version: DBD::SQLite 1.34_01 (sqlite 3.7.7.1)
Total Players Recognized: 5

Player Model: Squeezebox Radio
Player Type: baby
Firmware: 7.7.3-r16676

mherger
2018-02-02, 13:07
> Ok, now it starts. Problem: can't authorize. When I put user/pw of my
> premium account and I hit apply, it says "Authorization failed".

WTF. I reverted a whole bunch of changes I had applied since 2.1.0.
Could you please update to 2.1.5 (or whatever will be the latest...)?
Thanks!

--

Michael

Axel Foley
2018-02-02, 15:33
> Ok, now it starts. Problem: can't authorize. When I put user/pw of my
> premium account and I hit apply, it says "Authorization failed".

WTF. I reverted a whole bunch of changes I had applied since 2.1.0.
Could you please update to 2.1.5 (or whatever will be the latest...)?
Thanks!

--

Michael

Ok, 2.1.5 worked with user/pw. :)

Great job Michael.

zen2000
2018-02-03, 10:39
> just installed 2.1.3 of the plugin. But when I configure it, I see the
> following:
I just pushed out a change which might have been causing this issue
(though I don't understand, as I've been using that changed code all the
time...). Could you please give 2.1.4 another try? Thanks!


--
--

Michael

Thanks Michael the latest update works perfectly!

TonioRoffo
2018-02-05, 11:29
Just got the update to 2.1.5

Playing, next, previous, seek, ... all works. Except Pause. Doesn't pause. Second time I hit pause the track plays from the top. Will restart everything to see if the problem is on my end.

derdon
2018-02-06, 09:30
Hello everyone and hello Michael,

First of all a very big thank you for the great work and keeping spotify alive on LMS!
I guess this is my first bug report:

On Logitech Media Server Version: 7.9.1 - 1515659378 @ Thu Jan 11 09:19:10 UTC 2018 with Spotty 2.1.5 installed, I experience the following problem:
I use two different Spotify accounts each showing a submenu. Regularly the menus are incomplete: for example the Albums selection is empty or after a search there is no selection for found albums or artists. Nevertheless I can still continue playing spotify tracks from the current playlist. A simple reboot solves the problem an all menu entries are visible again.

Has anybody experienced the same issue an knows a solution?

Enjoy the music, best regards,

Don

Chippy
2018-02-06, 13:22
OK so this is ridiculous. I'm using Spotify Connect on my 12 year old Squeezebox 3.

Michael we really don't deserve this level of support, but thank you so much!

Chippy

mherger
2018-02-06, 14:31
> I use two different Spotify accounts each showing a submenu. Regularly
> the menus are incomplete: for example the Albums selection is empty or
> after a search there is no selection for found albums or artists.
> Nevertheless I can still continue playing spotify tracks from the
> current playlist. A simple reboot solves the problem an all menu entries
> are visible again.

Could you please check your server.log to see whether there are any
traces of the issue?

--

Michael

ButC
2018-02-07, 00:47
Playing a playlist yesterday, using Connect, I once again experieniced how Skip just restarted the now playing song from the beginning. Trying then to Shuffle the same playlist once again, the previously used Device was no longer selectable. This is the third time I'm having a similar problem, but apart from that the Spotify experience on Windows now seems quite stable :)

fry2305
2018-02-07, 08:05
Hi Michael,

thank you at first for your great work! I'm currently running the latest Spotty version on my rasperry pi with LMS. Today I read the worrying news, that Spotify is removing the the Spotify Connect implementation for a lot of wireless speakers. For Logitech they are stating that "The Spotify custom integration will be completely removed from the Squeezebox and UE Smart Radio speakers." Will this have any impact on your Spotty implementation on the LMS?

slartibartfast
2018-02-07, 09:34
Hi Michael,

thank you at first for your great work! I'm currently running the latest Spotty version on my rasperry pi with LMS. Today I read the worrying news, that Spotify is removing the the Spotify Connect implementation for a lot of wireless speakers. For Logitech they are stating that "The Spotify custom integration will be completely removed from the Squeezebox and UE Smart Radio speakers." Will this have any impact on your Spotty implementation on the LMS?Can you post a link to this?

Sent from my SM-G900F using Tapatalk

ButC
2018-02-07, 09:41
Can you post a link to this?

Sent from my SM-G900F using Tapatalk

https://support.spotify.com/us/listen_everywhere/on_speaker/why-cant-i-use-the-spotify-app-on-my-speaker/

slartibartfast
2018-02-07, 09:43
https://support.spotify.com/us/listen_everywhere/on_speaker/why-cant-i-use-the-spotify-app-on-my-speaker/OK. So it is old news and the reason Spotty exists.

Sent from my SM-G900F using Tapatalk

fry2305
2018-02-07, 09:59
OK. So it is old news and the reason Spotty exists.

Sent from my SM-G900F using Tapatalk

Hi,

I'm not sure that it is old news, because I stumbled upon it, reading an article published today:

https://www.heise.de/newsticker/meldung/Spotify-Connect-verschwindet-von-aelteren-Lautsprechern-und-Receivern-3962595.html (german)

so I wasn't sure if it is really something new or not and I was just curious if it my influence the spotty plugin (development)....

ButC
2018-02-07, 10:00
OK. So it is old news and the reason Spotty exists.

Sent from my SM-G900F using Tapatalk

Still, this has been brought up again this last week so it'd be great if Michael could confirm it doesn't affect Spotty :)

slartibartfast
2018-02-07, 10:17
Hi,

I'm not sure that it is old news, because I stumbled upon it, reading an article published today:

https://www.heise.de/newsticker/meldung/Spotify-Connect-verschwindet-von-aelteren-Lautsprechern-und-Receivern-3962595.html (german)

so I wasn't sure if it is really something new or not and I was just curious if it my influence the spotty plugin (development)....It sounds as though people with affected speakers have finally been cut off and they are complaining. The Spotify item linked to in the article is months old as they say. Let's hope so anyway.

Update. Lots of complaints from Pioneer owners here
https://community.spotify.com/t5/forums/v3_1/forumtopicpage/board-id/002/thread-id/49794/page/9


Sent from my SM-G900F using Tapatalk

fry2305
2018-02-07, 12:10
It sounds as though people with affected speakers have finally been cut off and they are complaining. The Spotify item linked to in the article is months old as they say. Let's hope so anyway.

Update. Lots of complaints from Pioneer owners here
https://community.spotify.com/t5/forums/v3_1/forumtopicpage/board-id/002/thread-id/49794/page/9


Sent from my SM-G900F using Tapatalk

...hopefully this will not happen to the Spotty plugin!

mherger
2018-02-07, 13:41
> thank you at first for your great work! I'm currently running the latest
> Spotty version on my rasperry pi with LMS. Today I read the worrying
> news, that Spotify is removing the the Spotify Connect implementation
> for a lot of wireless speakers. For Logitech they are stating that "The
> Spotify custom integration will be completely removed from the
> Squeezebox and UE Smart Radio speakers." Will this have any impact on
> your Spotty implementation on the LMS?

TBH: I don't know. Native support for SB has been pulled months ago. But
Spotty, I'm not sure. The librespot community (on which Spotty is based)
is positive that this will not have any influence on the project, except
probably more interest in it as people will be looking for alternatives
to the official implementation...

--

Michael

frooop
2018-02-08, 02:31
Hi,
I run the plugin version 2.1.5 with a Logitech Media Server Version: 7.9.1 on my Synology DSM 6.1.5-15254.

My problem is that a while ago the spotify connect feature became very "erratic". It sometimes just stops working and then after a couple of restarts it comes back again. What I noticed is that it never works when the "disableDiscovery" flag is set to 1. But for some reason it keeps switching back to that, even if I deactivate the checkbox or edit the spotty.prefs (while the LMS is turned off) it comes back after a while and then my phone and macbook are not able to "see" the player anymore.

Any ideas? Any more Information I can provide to help debug this?

Thanks.

scoob101
2018-02-08, 07:39
Just wanted to add my thanks for the phenomenal commitment Michael continues to show to the community.

Also a quick reminder for anyone who is interested that Michael does have donate button on his page if you wanted to show your gratitude http://www.herger.net/slim/

EDIT:: Did a quick test earlier and as far as a can see it works almost exactly as you would expect. Running Spotty 2.1.5 on LMS 7.9.1 - 1511768958 for Windows. Brilliant.

mherger
2018-02-08, 09:10
> My problem is that a while ago the spotify connect feature became very
> "erratic". It sometimes just stops working and then after a couple of
> restarts it comes back again. What I noticed is that it never works when
> the "disableDiscovery" flag is set to 1. But for some reason it keeps
> switching back to that, even if I deactivate the checkbox or edit the
> spotty.prefs (while the LMS is turned off) it comes back after a while
> and then my phone and macbook are not able to "see" the player anymore.

That flag would be set if the helper crashed a few times within a few
minutes (I think 3x in 5 minutes). Because if that happens we can assume
discovery doesn't work, but makes the helper crash. Therefore the plugin
disables discovery mode.

When it's disabled, are you sure your phone's Spotify app is configured
with the same credentials as your Spotty plugin?

--

Michael

frooop
2018-02-08, 11:53
> My problem is that a while ago the spotify connect feature became very[color=blue]

When it's disabled, are you sure your phone's Spotify app is configured
with the same credentials as your Spotty plugin?

--

Michael

Yes, I only have credentials of that one account. Funny thing is that it does seem to work for a while after a restart of the service. If I then start playing something very quickly it stays like that. But if I restart the service and try to play something in half an hour the player does not show up in the client anymore.

mherger
2018-02-08, 22:35
> Yes, I only have credentials of that one account. Funny thing is that it
> does seem to work for a while after a restart of the service. If I then
> start playing something very quickly it stays like that. But if I
> restart the service and try to play something in half an hour the player
> does not show up in the client anymore.

Please set logging for plugin.spotty to INFO and provide the server.log
file next time this happens.

--

Michael

mherger
2018-02-08, 23:00
> Playing a playlist yesterday, using Connect, I once again experieniced
> how Skip just restarted the now playing song from the beginning. Trying

Would you skip from LMS or a Spotify app?

> then to Shuffle the same playlist once again, the previously used Device

Shuffle: on LMS or Spotify?

> |Filename: server.log (2).zip |

Unfortunately this log file lacks any information about Spotty. Next
time this happens please set plugin.spotty to INFO.

--

Michael

Stefan121
2018-02-08, 23:28
Hallo,

I have problems withe the version 2.1.5 of the spotty-plugin in the logitech media server (7.9.1) on my raspberry3 (max2play, debain jessie). I am using the DAC+ Pro Soundcard in my raspberry. When I want to use the "spotty connect" options with my spotfy app on my iphone, i can connect with the max2play-player. But I can't nothing hear on my sourroundsystem.

I have activated the "debug" information in der protocol but I can't find anything of informations:

[18-02-08 21:05:39.0031] Plugins::Spotty::Connect::DaemonManager::initHelpe rs (54) Initializing Spotty Connect helper daemons...
[18-02-08 21:06:39.0040] Plugins::Spotty::Connect::DaemonManager::initHelpe rs (54) Initializing Spotty Connect helper daemons...
[18-02-08 21:07:39.0041] Plugins::Spotty::Connect::DaemonManager::initHelpe rs (54) Initializing Spotty Connect helper daemons...
[18-02-08 21:08:39.0030] Plugins::Spotty::Connect::DaemonManager::initHelpe rs (54) Initializing Spotty Connect helper daemons...

When I am using the spotty-app in the lms i can hear the music.

Can anybody help me? Is there somewhere an option to setup the soundcad (Hifiberry DAC+ pro)?

Thanks,
Stefan

ButC
2018-02-08, 23:38
> Playing a playlist yesterday, using Connect, I once again experieniced
> how Skip just restarted the now playing song from the beginning. Trying

Would you skip from LMS or a Spotify app?

> then to Shuffle the same playlist once again, the previously used Device

Shuffle: on LMS or Spotify?

> |Filename: server.log (2).zip |

Unfortunately this log file lacks any information about Spotty. Next
time this happens please set plugin.spotty to INFO.

--

Michael

I used Skip from LMS.

I used Shuffle from Spotify.

I thought I had logging set to INFO - does it revert back to default after a certain time? Well, I'll set it again to INFO.

Mnyb
2018-02-09, 04:22
I used Skip from LMS.

I used Shuffle from Spotify.

I thought I had logging set to INFO - does it revert back to default after a certain time? Well, I'll set it again to INFO.

There is a setting for the log settings to stick during reboots

Simon_rb
2018-02-09, 06:43
Just thought I'd let you know that I have tried this with Apple's HomePod and appears to work at the moment with early testing. Seems its using AirPlay 1 at the moment. I use Philippe's brilliant AirPlay bridge to show the player in LMS.

Cheers

ButC
2018-02-09, 06:54
There is a setting for the log settings to stick during reboots

Okej, thanks.

frooop
2018-02-09, 07:19
>

Please set logging for plugin.spotty to INFO and provide the server.log
file next time this happens.

--

Michael

Here is the file: 24507. I did the following:


Set disableDiscovery to 0 in the config file
Start the LMS
I do see the player on my Spotify Client and play a song
From that point on, I'm not able to see the Player on any other device and it also does not come back when I stop the playback.

mherger
2018-02-09, 09:30
Hi Stefan

would you be able to play Spotify tracks using Spotty's menus, rather than Spotify Connect?

Please make sure you set plugin.spotty to INFO to get more information. And make sure you're running the latest max2play version. I think Spotty is not compatible with older versions.

Michael

Stefan121
2018-02-09, 09:37
Hi Stefan

would you be able to play Spotify tracks using Spotty's menus, rather than Spotify Connect?

Please make sure you set plugin.spotty to INFO to get more information. And make sure you're running the latest max2play version. I think Spotty is not compatible with older versions.

Michael


Hi Michael,

when I'm using the Spotty's menus in the LMS, I don't have any problems.
I have checked max2play of new versions, but I am up-to-date (not beta). The LMS is the latest version 7.9.1.

Is it right, that the field "Spotify client id" have to be empty?

later I can set the plugin.spotty ti INFO and check if something more is in the protocol.


Stefan

Stefan121
2018-02-09, 11:44
Hi Michael,

when I'm using the Spotty's menus in the LMS, I don't have any problems.
I have checked max2play of new versions, but I am up-to-date (not beta). The LMS is the latest version 7.9.1.

Is it right, that the field "Spotify client id" have to be empty?

later I can set the plugin.spotty ti INFO and check if something more is in the protocol.


Stefan

Hi Michael,

the server.log contains the following details:


[18-02-09 19:19:14.4315] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table
[18-02-09 19:19:14.5194] Slim::Schema::forceCommit (2149) Warning: Trying to commit transactions before DB is initialized!
[18-02-09 19:21:28.0343] Plugins::Spotty::Connect::DaemonManager::__ANON__ (43) Discovery mode for Connect has changed - re-initialize Connect helpers
[18-02-09 19:21:28.0359] Plugins::Spotty::Connect::Daemon::stop (104) Quitting Spotty Connect daemon for b8:27:eb:27:93:32
[18-02-09 19:21:28.0415] Plugins::Spotty::Connect::DaemonManager::startHelp er (84) Need to (re-)start Connect daemon for b8:27:eb:27:93:32
[18-02-09 19:21:28.0457] Plugins::Spotty::Connect::Daemon::start (63) Starting Spotty Connect deamon:
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c /var/lib/squeezeboxserver/cache/spotty/b827eb279332 -n max2play --disable-audio-cache --bitrate 96 --player-mac b8:27:eb:27:93:32 --lms 192.168.188.6:9000
[18-02-09 19:21:39.4770] Plugins::Spotty::Connect::Daemon::stop (104) Quitting Spotty Connect daemon for b8:27:eb:27:93:32
2018-02-09 19:21:39 squeezeboxserver_safe stopped.
2018-02-09 19:21:53 squeezeboxserver_safe started.
[18-02-09 19:21:59.5598] main::init (387) Starting Logitech Media Server (v7.9.1, 1517314665, Tue Jan 30 14:05:44 UTC 2018) perl 5.020002 - arm-linux-gnueabihf-thread-multi-64int
[18-02-09 19:22:00.3889] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table
[18-02-09 19:22:00.4163] Slim::Schema::forceCommit (2149) Warning: Trying to commit transactions before DB is initialized!
[18-02-09 19:22:00.7068] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table
[18-02-09 19:22:00.7664] Slim::Schema::forceCommit (2149) Warning: Trying to commit transactions before DB is initialized!
[18-02-09 19:22:11.9286] Plugins::Spotty::Plugin::purgeAudioCache (446) Starting audio cache cleanup...
[18-02-09 19:22:11.9308] Plugins::Spotty::Plugin::purgeAudioCache (469) Max. cache size is: 0MB, current cache size is 0MB
[18-02-09 19:22:11.9315] Plugins::Spotty::Plugin::purgeAudioCache (500) Starting temporary file cleanup... (/var/lib/squeezeboxserver/cache/spotty)
[18-02-09 19:22:11.9323] Plugins::Spotty::Plugin::purgeAudioCache (520) Audio cache cleanup done!
[18-02-09 19:22:12.0996] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table
[18-02-09 19:22:12.1637] Slim::Schema::forceCommit (2149) Warning: Trying to commit transactions before DB is initialized!
[18-02-09 19:22:12.3353] Plugins::Spotty::Plugin::findBin (704) Trying helper applicaton: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf
[18-02-09 19:22:12.4041] Plugins::Spotty::Plugin::findBin (708) Found helper applicaton: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf
[18-02-09 19:22:12.6801] main::checkDataSource (1110) Warning: Schema updated or no media found in the database, initiating scan.
[18-02-09 19:22:13.1199] Plugins::Spotty::Connect::DaemonManager::startHelp er (80) Need to create Connect daemon for b8:27:eb:27:93:32
[18-02-09 19:22:13.1232] Plugins::Spotty::Connect::Daemon::start (63) Starting Spotty Connect deamon:
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c /var/lib/squeezeboxserver/cache/spotty/b827eb279332 -n max2play --disable-audio-cache --bitrate 96 --player-mac b8:27:eb:27:93:32 --lms 192.168.188.6:9000
2018-02-09 19:22:14 squeezeboxserver_safe stopped.
[18-02-09 19:22:14.4149] Plugins::Spotty::Connect::Daemon::stop (104) Quitting Spotty Connect daemon for b8:27:eb:27:93:32
2018-02-09 19:22:14 squeezeboxserver_safe started.
[18-02-09 19:22:18.2419] main::init (387) Starting Logitech Media Server (v7.9.1, 1517314665, Tue Jan 30 14:05:44 UTC 2018) perl 5.020002 - arm-linux-gnueabihf-thread-multi-64int
[18-02-09 19:22:18.8425] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table
[18-02-09 19:22:18.9049] Slim::Schema::forceCommit (2149) Warning: Trying to commit transactions before DB is initialized!
[18-02-09 19:22:19.2677] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table
[18-02-09 19:22:19.3280] Slim::Schema::forceCommit (2149) Warning: Trying to commit transactions before DB is initialized!
[18-02-09 19:22:20.2890] Plugins::Spotty::Plugin::purgeAudioCache (446) Starting audio cache cleanup...
[18-02-09 19:22:20.2904] Plugins::Spotty::Plugin::purgeAudioCache (469) Max. cache size is: 0MB, current cache size is 0MB
[18-02-09 19:22:20.2912] Plugins::Spotty::Plugin::purgeAudioCache (500) Starting temporary file cleanup... (/var/lib/squeezeboxserver/cache/spotty)
[18-02-09 19:22:20.2920] Plugins::Spotty::Plugin::purgeAudioCache (520) Audio cache cleanup done!
[18-02-09 19:22:20.4355] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table
[18-02-09 19:22:20.4938] Slim::Schema::forceCommit (2149) Warning: Trying to commit transactions before DB is initialized!
[18-02-09 19:22:20.6742] Plugins::Spotty::Plugin::findBin (704) Trying helper applicaton: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf
[18-02-09 19:22:20.6912] Plugins::Spotty::Plugin::findBin (708) Found helper applicaton: /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf
[18-02-09 19:22:20.9241] main::checkDataSource (1110) Warning: Schema updated or no media found in the database, initiating scan.
[18-02-09 19:22:21.3764] Plugins::Spotty::Connect::DaemonManager::startHelp er (80) Need to create Connect daemon for b8:27:eb:27:93:32
[18-02-09 19:22:21.3791] Plugins::Spotty::Connect::Daemon::start (63) Starting Spotty Connect deamon:
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c /var/lib/squeezeboxserver/cache/spotty/b827eb279332 -n max2play --disable-audio-cache --bitrate 96 --player-mac b8:27:eb:27:93:32 --lms 192.168.188.6:9000
[18-02-09 19:22:24.8540] Slim::Utils::SQLiteHelper::postConnect (374) Optimizing DB because of missing or empty sqlite_stat1 table
[18-02-09 19:22:24.8785] Slim::Schema::forceCommit (2149) Warning: Trying to commit transactions before DB is initialized!

I can't hear anything else on my raspy.

The next problem what I have is that the next songs on my playlist not switch to the next at the end of a song. I have to switch them manuelly.

I hope that you can help me.


Stefan

ElFishi
2018-02-10, 00:21
since a few days I have problems starting spottify connect in the morning.
I need 4 - 5 attempts to connect to my squeezebox with the "connect to a device" function of the Windows app.
only after the last attempt the log file shows

[18-02-10 08:13:36.0033] Plugins::Spotty::Connect::DaemonManager::startHelp er (84) Need to (re-)start Connect daemon for 00:04:20:xx:xx:xx
[18-02-10 08:13:36.0070] Plugins::Spotty::Connect::Daemon::start (63) Starting Spotty Connect deamon:
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/arm-linux/spotty-muslhf -c /var/lib/squeezeboxserver/cache/spotty/000420xxxxxx -n Salonbox --disable-audio-cache --bitrate 96 --player-mac 00:04:20:xx:xx:xx --lms 192.168.0.107:9000
[18-02-10 08:14:00.6726] Plugins::Spotty::Connect::_connectEvent (230) Got called from spotty helper: start
I the earlier attempts the player name in the menu goes grey for a few seconds and then the spotify app is again connected to This Computer. There is nothing that shows in the logfile.

loopguru
2018-02-10, 03:17
since a few days I have problems starting Spotify Connect in the morning.
I need 4 - 5 attempts to connect to my squeezebox with the "connect to a device" function of the Windows app.
[...]
I the earlier attempts the player name in the menu goes grey for a few seconds and then the Spotify app is again connected to This Computer. There is nothing that shows in the logfile.

Experiencing the same. Spotify app on iPhone tries connecting and finally gives up. Even several connection attempts fail.

If I then switch to another Squeezebox Radio connection succeeds. Switching back to the initial Squeezebox Radio leaves both (!) Squeezebox Radios playing.
Absolutely nothing in the logs.

I can not recall this happened in the past so it might be a regression with one of the recent Spotty updates.

Tom

Spotty 2.5.1, LMS 7.9.1 on Synology 916+ (Intel Pentium N3710), perl 5.024000 - x86_64-linux

slartibartfast
2018-02-10, 03:23
Experiencing the same. Spotify app on iPhone tries connecting and finally gives up. Even several connection attempts fail.

If I then switch to another Squeezebox Radio connection succeeds. Switching back to the initial Squeezebox Radio leaves both (!) Squeezebox Radios playing.
Absolutely nothing in the logs.

I can not recall this happened in the past so it might be a regression with one of the recent Spotty updates.

Tom

Spotty 2.5.1, LMS 7.9.1 on Synology 916+ (Intel Pentium N3710), perl 5.024000 - x86_64-linuxSeems to be an issue with the Android Spotify app. I can't play anything at all even on the phone.

Sent from my SM-G900F using Tapatalk

slartibartfast
2018-02-10, 03:36
Seems to be an issue with the Android Spotify app. I can't play anything at all even on the phone.

Sent from my SM-G900F using TapatalkI reinstalled Spotify on my phone. When I started the app I saw "playing on Touch do you want to listen on this phone" I clicked on "yes" and music played on the phone. I then chose Radio from devices available and the Radio started to play. I tried to select Touch from devices available but saw the message "Play some music before selecting player" or similar.
So once a player is selected I can't change it. Very strange.

Sent from my SM-G900F using Tapatalk

slartibartfast
2018-02-10, 03:46
I reinstalled Spotify on my phone. When I started the app I saw "playing on Touch do you want to listen on this phone" I clicked on "yes" and music played on the phone. I then chose Radio from devices available and the Radio started to play. I tried to select Touch from devices available but saw the message "Play some music before selecting player" or similar.
So once a player is selected I can't change it. Very strange.

Sent from my SM-G900F using TapatalkThis only happens when a Squeezebox payer is selected. If any other player is selected I can change player.

Sent from my SM-G900F using Tapatalk

loopguru
2018-02-10, 04:50
Switching back to the initial Squeezebox Radio leaves both (!) Squeezebox Radios playing.

This is reproducible for me. It even happens if I switch from a Squeezebox Radio to my Raumfeld Spotify Connect enabled streamer: The Squeezebox Radio continues to play although it is not the chosen device.