Quick check with you on this - this question has been asked a number of times by me and other users - but was not responded directly - so I thought I wanna ask one more time before I give up
It has been answered before - this thread (and others related to Spotty) is long... answers can easily be missed. That's why I prefer to start specific threads, rather than post all kinds of problems to one generic thread like this one... But anyway:
[19-07-12 13:43:32.3858] Plugins::Spotty::Connect:: DaemonManager:: checkAPIConnectPlayers (208) Connect daemon is running, but not connected - shutting down to force restart: 02:d0:08:40:f1:ef
The underlying problem is that the spotty daemon sometimes loses connection to Spotify's servers. Or Spotify's servers decide to no longer list it as connected. Really, I don't understand what's going on. That's the reason why this problem has been around for a while and I have failed to deliver a solution.
What Spotty attempts to do in this situation is to restart the deamon. After that it would be accessible through Connect again. But as the check whether it's still working or not is timer based, there's always a gap where the device is not seen by Spotify. If you happen to need a track change in such a moment, then playback will stop.
I could certainly increase the polling rate to make that window smaller. But this call alone already represents about 10x the number of other requests being used by Spotty. It's hundreds of thousands of calls every day across all installations. Cutting the interval in half would double the number of requests etc. I fear at some point Spotify could rate limit us.
Therefore I'm sorry to say that I do not have a better answer to the problem. Connect mode stays... well... spotty.
-- Michael _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
