Sportswagoneer wrote:
> Thank you so much!
>
> I had the exact same problem! Suddenly experienced +/- 30sec lag in
> Spotty and often (but not allways) access token error in web ui.
>
> Problem arose in LMS 7.9 so I upgraded to 8.1.1 incl. plugins. No dice.
>
> Turned out ipv6 has been turned
Paulussie wrote:
> Old thread, but it saved me!
> .
> And who knows, maybe this helps someone else.
Thank you so much!
I had the exact same problem! Suddenly experienced +/- 30sec lag in
Spotty and often (but not allways) access token error in web ui.
Problem arose in LMS 7.9 so I
pavowren wrote:
> i know it is *hard* to believe, but i have had issues when connecting to
> 5 ghz ssid.
> i'm certain that you can take out that v4.0.6 disable-asynch option,
> though i do not know the situation with the other fellow that was having
> the token problem.
>
> in any case, at
mherger wrote:
> > i have found the culprit:
> > 5GHz wifi access point used by LMS machine.
>
> Wow... that would be some oddity!
>
> --
>
> Michael
i know it is *hard* to believe, but i have had issues when connecting to
5 ghz ssid.
i'm certain that you can take out that v4.0.6
i have found the culprit:
5GHz wifi access point used by LMS machine.
Wow... that would be some oddity!
--
Michael
___
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins
i have found the culprit:
5GHz wifi access point used by LMS machine.
i happened to check the machine and it was connecting to the 5GHz AP
i'm guessing due to its stronger signal.
i disabled the 5GHz and instead connected to the 2.4GHz AP.
and all seems to be working normally!
n.b.
come to
Bronsky wrote:
> My squeezebox radio behaves the same way. The music starts playing on
> web interface (selected ist Sqeezebox radio), but there is no music on
> the Squeezebox radio. On the Squeezebox Radio "Connection ..." appears
> for a very long time and after a minute the playback on the
mherger wrote:
> > no token timeout errors.
>
> Oh, never had recently? Then you're on the wrong thread :-)
> --
>
i stated previously that *after* the latest 4.0.6 with its asynch
option,
token errors went away.
mherger wrote:
> >
> And still nothing in the server.log file, even if you
pavowren wrote:
> Ogg has been disabled for Spotty.
> no token timeout errors.
> but playback is a problem; when a track is selected, sqzlite shows
> "Connecting..."
> yesterday, i saw that at least on the LMS web page, after about 2
> minutes, the progress bar
> jumped back to zero point and i
no token timeout errors.
Oh, never had recently? Then you're on the wrong thread :-)
but playback is a problem; when a track is selected, sqzlite shows
"Connecting..."
yesterday, i saw that at least on the LMS web page, after about 2
minutes, the progress bar
jumped back to zero point and i
mherger wrote:
> > yes, it used to work for months.
> > i see a bunch of Ogg's; which ones are you referring to?
>
> Spotty -> Ogg - anything in server.log?
>
> --
>
> Michael
Ogg has been disabled for Spotty.
no token timeout errors.
but playback is a problem; when a track is selected,
mherger wrote:
> > ISP ist Unitymedia.
>
> Could everybody on here please tell me what country you're in, and what
>
> ISP you're using?
>
> --
>
> Michael
i'm using T-Mobile home internet gateway in USA;
has been for almost a year.
ISP ist Unitymedia.
Could everybody on here please tell me what country you're in, and what
ISP you're using?
--
Michael
___
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins
mherger wrote:
> > I'm a little bit confused now. I wanted to run through the setup
> above
> > again and note the corresponding times. Now I suddenly get the token
> > error message again.
>
> With or without that new option set? That would (unfortunately) prove
> there's a problem outside
I'm a little bit confused now. I wanted to run through the setup above
again and note the corresponding times. Now I suddenly get the token
error message again.
With or without that new option set? That would (unfortunately) prove
there's a problem outside our control :-(
I might have asked
mherger wrote:
> > Here are some "fresh" log-files with V4.0.6 and NOT set the new
> option.
> > New logs start at 07:38. Everything works the same as with the new
>
> No more timeouts? Then that setting is moot, because it was just...
> whatever? Argh...
>
> > option set. I'm able to walk
Here are some "fresh" log-files with V4.0.6 and NOT set the new option.
New logs start at 07:38. Everything works the same as with the new
No more timeouts? Then that setting is moot, because it was just...
whatever? Argh...
option set. I'm able to walk through menu on
mherger wrote:
> > It happens with the old (but customized Version of spotty) and the
> > aktuell spotty (V4.06). The server.log is taken with the customized
>
> Is some of this latest log file with v4.0.6 and the default token
> refresh behaviour (the new option NOT set)?
>
> --
>
>
It happens with the old (but customized Version of spotty) and the
aktuell spotty (V4.06). The server.log is taken with the customized
Is some of this latest log file with v4.0.6 and the default token
refresh behaviour (the new option NOT set)?
--
Michael
yes, it used to work for months.
i see a bunch of Ogg's; which ones are you referring to?
Spotty -> Ogg - anything in server.log?
--
Michael
___
plugins mailing list
plugins@lists.slimdevices.com
mherger wrote:
> > The file doesn't cover the non-working period, I updated the file in
> > nextcloud, now you can find log's from the non-working period, too:
> >
> > https://cloud.bronsky.net/index.php/s/qtz7DHDZtH3qqtC
>
> That links is not found.
>
> > I've tested playing music with my
pavowren wrote:
> hi, michael,
> with 4.0.6 and the new option, i'm no longer getting the token error.
> i can select Spotty and all view appear as expected.
> but NO audio!
>
> all apps show the squeezelite device playing; progress bar is
> advancing.
> at the RPi screen, i do see the correct
mherger wrote:
> > with 4.0.6 and the new option, i'm no longer getting the token error.
> > i can select Spotty and all view appear as expected.
> > but NO audio!
>
> Has it ever worked before? Please check transcoding settings and disable
>
> Spotty -> Ogg if it's enabled
The file doesn't cover the non-working period, I updated the file in
nextcloud, now you can find log's from the non-working period, too:
https://cloud.bronsky.net/index.php/s/qtz7DHDZtH3qqtC
That links is not found.
I've tested playing music with my squeezebox radio just a few minutes
ago.
with 4.0.6 and the new option, i'm no longer getting the token error.
i can select Spotty and all view appear as expected.
but NO audio!
Has it ever worked before? Please check transcoding settings and disable
Spotty -> Ogg if it's enabled (Settings/Advanced/File Types).
--
Michael
mherger wrote:
> > I changed line 192 in file Token.pm in "elsif (0)", restarted
> squeezebox
> > server and I'm able to access spotty again :-) I can surf through
> > "spotty-menu" and i'm able to choose my playlists.
>
> That would be a great finding! Thanks a lot!
>
> >
mherger wrote:
> I just pushed out v4.0.6 with a new option to "Disable asynchronous
> token refresh call" (see Settings/Advanced/Spotty toward the bottom). If
>
> this was _not_ available to you and you double-checked you were using
> v4.0.6, then please tell me the spotty helper version
I just pushed out v4.0.6 with a new option to "Disable asynchronous
token refresh call" (see Settings/Advanced/Spotty toward the bottom). If
this was _not_ available to you and you double-checked you were using
v4.0.6, then please tell me the spotty helper version you're using.
This setting
I changed line 192 in file Token.pm in "elsif (0)", restarted squeezebox
server and I'm able to access spotty again :-) I can surf through
"spotty-menu" and i'm able to choose my playlists.
That would be a great finding! Thanks a lot!
https://cloud.bronsky.net/index.php/s/zA53bCr8kD3sTdm
mherger wrote:
> >
> /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-custom
> > -n Squeezebox -c "/var/lib/squeezeboxserver/cache/spotty/097202c7"
> > --save-token ~/token.json has given the same output in token.json as
> > printed on screen a few days ago.
mherger wrote:
>
>
> Are you using your own client_id with Spotty? If not, could you please
> try to do so? As you're running your own Spotify application, you should
>
> already have one?
>
> --
>
> Michael
just tried my own client_id, no difference.
same token error.
OK, but I just can give it a try tomorrow. Shall I change Line 48 back?
Yes, revert that first change. Thanks!
--
Michael
___
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins
mherger wrote:
> >
> /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-custom
> > -n Squeezebox -c "/var/lib/squeezeboxserver/cache/spotty/097202c7"
> > --save-token ~/token.json has given the same output in token.json as
> > printed on screen a few days ago.
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-custom
-n Squeezebox -c "/var/lib/squeezeboxserver/cache/spotty/097202c7"
--save-token ~/token.json has given the same output in token.json as
printed on screen a few days ago. I can send you the file token.json
mherger wrote:
> Argh... I don't understand why the token call would fail if you were
> able to authenticate. Thus just doesn't make sense...
>
> Could you please try the following (based on your successful token call
> from a day or two ago):
>
> >
Code:
> >
Bronsky wrote:
> I deleted my credentials and re-authentifcates. I still got the follwing
> error in server.log:
Argh... I don't understand why the token call would fail if you were
able to authenticate. Thus just doesn't make sense...
Could you please try the following (based on your
Hello Michael,
I deleted my credentials and re-authentifcates. I still got the follwing
error in server.log:
[20-05-02 15:58:01.1215] Slim::Networking::IO::Select::__ANON__ (130)
Error: Select task failed calling Slim::Web::HTTP::processHTTP: Not a
SCALAR reference at
Guys - could you please all go to Settings/Advanced/Spotty, delete your
credentials, and re-authenticate? Would that help your situation?
--
Michael
___
plugins mailing list
plugins@lists.slimdevices.com
mherger wrote:
> > If it's the Telekom's fault (I'll gladly blame anything on them), why
> is
> > it working on my Test server (Windows 10, this very machine)?
>
> Well, then it's not. In fact, one of the user's who's got a problem on
> Unitymedia did NOT experience his issues on a Telekom
Hmm... is Spotty using spotty-custom, too? You can check this in
Settings/Advanced/Spotty.
And did you send the manually launched command from the same machine and
environment as where LMS is running?
--
Michael
Hello Michael,
LMS is running on V-Server with ubuntu 16.04, the clients
Unfortunately I still get the following errors in server.log and I'm not
able to get access through spotify on squeezebox clients:
[20-04-30 09:25:44.2218] Plugins::Spotty::API::Token::_killTokenHelper
(169) Timed out waiting for a token
Hmm... is Spotty using spotty-custom, too? You can
mherger wrote:
> > root@h2772242:~#
> >
> /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
> > -n Squeezebox -x
> > ok spotty v0.35.0
> >
>
If it's the Telekom's fault (I'll gladly blame anything on them), why is
it working on my Test server (Windows 10, this very machine)?
Well, then it's not. In fact, one of the user's who's got a problem on
Unitymedia did NOT experience his issues on a Telekom connection. Yours
must be
I just had the most awesome idea and rebooted my NAS. Please don't hit
me. It works now.
A minor thing, though: I clicked on Artists / Phoebe Bridgers / Top
Tracks and got Roger Waters Top Tracks instead. I tried a different
artist that also showed the wrong albums in there. Naturally, I wanted
If it's the Telekom's fault (I'll gladly blame anything on them), why is
it working on my Test server (Windows 10, this very machine)?
QLMS 8.0.0@2.20 x64 (digimaster) with perl 5.30.1 / QNAP 469L QTS 4.3.4
mherger wrote:
> > Okay, something has changed. I renamed spotty-x86_64 to
> > spotty-x86_64_old and spotty-custom to spotty-x86_64 and then
> restarted
> > the server. I then removed my credentials from Spotty ("delete") and
> had
>
> You could just put spotty-custom in a path, it would be
I'm not sure I understand. The credentials are stored in
/share/CACHEDEV1_DATA/.qpkg/LogitechMediaServer/SlimServer/Cache/spotty/,
where that is created for every player that got checked in
Spotty's settings. Where's that derived from? My credentials
are unique, of
Okay, something has changed. I renamed spotty-x86_64 to
spotty-x86_64_old and spotty-custom to spotty-x86_64 and then restarted
the server. I then removed my credentials from Spotty ("delete") and had
You could just put spotty-custom in a path, it would be picked up first.
a look at my
Okay, something has changed. I renamed spotty-x86_64 to
spotty-x86_64_old and spotty-custom to spotty-x86_64 and then restarted
the server. I then removed my credentials from Spotty ("delete") and had
a look at my Spotify app, which this time showed the Spotty
Authentication. I clicked on it and
mherger wrote:
> > root@h2772242:~#
> >
> /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
> > -n Squeezebox -x
> > ok spotty v0.35.0
> >
>
mherger wrote:
>
> It's not really an error. I figured the release build was different on
> Linux than on macOS. Please continue on the other thread where I've
> linked a new test build.
Yes, I already tried that but couldn't really tell if I was helping or
distracting.
mherger wrote:
>
root@h2772242:~#
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
-n Squeezebox -x
ok spotty v0.35.0
{"debug":false,"lms-auth":true,"ogg-direct":true,"podcasts":true,"save-token":true,"version":"0.35.0","volume-normalisation":true}
Could you please
mherger wrote:
> > Michael doesn't see edits. Most of the time. Or something like that.
>
> It's almost embarrassing how everybody has to explain me... :-D Thanks!
>
> --
>
> Michael
You're welcome. Why don't you just put that piece of information in your
signature? Oh, and I tried the
Michael doesn't see edits. Most of the time. Or something like that.
It's almost embarrassing how everybody has to explain me... :-D Thanks!
--
Michael
___
plugins mailing list
plugins@lists.slimdevices.com
Bronsky wrote:
> That's the result:
>
> root@h2772242:~#
> /var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
> -n Squeezebox -x
> ok spotty v0.35.0
>
That's the result:
root@h2772242:~#
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
-n Squeezebox -x
ok spotty v0.35.0
{"debug":false,"lms-auth":true,"ogg-direct":true,"podcasts":true,"save-token":true,"version":"0.35.0","volume-normalisation":true}
root@h2772242:~#
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
-n Squeezebox -c "/var/lib/squeezeboxserver/cache/spotty/097202c7"
--get-token
Use --client-id to provide a CLIENT_ID
Ahm... what version of spotty is this? Please run the following:
without "-i abcd" that's the output:
root@h2772242:~#
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
-n Squeezebox -c "/var/lib/squeezeboxserver/cache/spotty/097202c7"
--get-token
Use --client-id to provide a CLIENT_ID
Oliver
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
-n Squeezebox -c "/var/lib/squeezeboxserver/cache/spotty/097202c7" -i
abcdef1234567890 --get-token
Oh, please try again without the "-i abcd..." parameter.
--
Michael
Hello Michael,
I disabled Firewall just for the test, but the result ist the same:
root@h2772242:~#
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
-n Squeezebox -c "/var/lib/squeezeboxserver/cache/spotty/097202c7" -i
abcdef1234567890 --get-token
I changed to command line and tried to get a token manually:
/var/lib/squeezeboxserver/cache/InstalledPlugins/Plugins/Spotty/Bin/i386-linux/spotty-x86_64
-n Squeezebox -c "/var/lib/squeezeboxserver/cache/spotty/097202c7" -i
abcdef1234567890 --get-token
error getting token MercuryError
Any Idea
Hello together,
two days ago I have installed spotty on my V-Server and got a little
Problem with the firewall:
https://forums.slimdevices.com/showthread.php?112074-Spotty-through-OpenVPN-firewall-routes
After the hint of a board member everything was OK. I was able to access
Spotify through
62 matches
Mail list logo
