mherger wrote:
> > So i have been waiting for a solution.
>
> And you've now found a solution? Because I believe the "skipping in
> Denmark" issue is still happening.
Chiming in - also from Denmark.
Had this issue for at least a week - using the workaround / fallback
setting in Spotty v. 4.8.1 solved the issue partly for me without having
to modify my DNS settings.
That is, it works when using Spotty from LMS or iPeng.
When starting a Spotify Connect session from the Spotify app or the web
player, it still does the skipping part - but then, after some skipped
tracks, the connection to the player (Squeezebox Radio) breaks, and then
the radio plays the track it got to just fine... :confused:
Radios are running the community firmware 8.0.1-r16867
Have tried most combinations of advanced settings in Spotty - but even
with just the workaround enabled, Spotify Connect still does not want to
"play nice"..
Excerpt from LMS log after a service restart and the issue has occured:
Code:
--------------------
[22-03-15 11:13:59.5909] main::init (390) Starting Logitech Media Server
(v8.2.0, 1627922070, Tue Aug 3 11:37:35 CEST 2021) perl 5.030000 -
x86_64-linux-gnu-thread-multi
[22-03-15 11:14:15.0982]
Slim::Networking::SqueezeNetwork::Players::_players_error (377) Unable to get
players from SN: Timed out waiting for data, retrying in 900 seconds
[22-03-15 11:15:01.8807] Plugins::Spotty::API::__ANON__ (1442) API call:
me/player?market=from_token
[22-03-15 11:15:01.8809] Plugins::Spotty::API::__ANON__ (1446) error: 429 Too
Many Requests
[22-03-15 11:15:01.8813] Plugins::Spotty::API::error429 (1504) Access Rate
limit exceeded for: me/player?market=from_token; retry after 2 seconds.
[22-03-15 11:15:01.8949] Slim::Networking::IO::Select::__ANON__ (130) Error:
Select task failed calling Slim::Networking::Async::_async_read: Can't call
method "isa" on an undefined value at
/usr/share/perl5/Slim/Player/Squeezebox.pm line 773.
; fh=Slim::Networking::Async::Socket::HTTPS=GLOB(0x55bbde4c3920)
--------------------
I am running Spotty with a Spotify Client ID, as I saw the rate limiting
occurring in the logs sometime last week, and read that this could solve
it.
Also - a point that I am unsure if has any influence on this: in the end
of February I upgraded my Spotify plan from Duo to Family.
Spotify Connect had been working great for me for years, and then it
stops working - so could the change of plan also be part of this issue?
Might try to see if changing DNS settings works better..
*Thanks for the quick-fix and your continued work on this @mherger - it
is an awesome plugin!*
------------------------------------------------------------------------
knoer's Profile: http://forums.slimdevices.com/member.php?userid=72672
View this thread: http://forums.slimdevices.com/showthread.php?t=111923
_______________________________________________
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/plugins
