michaelherger/librespot

Open Source Spotify client library

librespot's Issues

Version mismatch - How to get the current one?

Hello,

thank you for all your effort and your time!

I saw now, that the spotty repo was archived and you switched over to this one. Are there any changes to do to get the updates from this repo?

I'm a little bit confused, since in the changelog the latest version is 0.4.2 (probably from the upstream), in the tags there is a version spotty-v1.3.0 and in LMS I see the version 4.8.8 installed. It would be great, if you can clarify this and tell me how I can be sure, that the correct and up to date version is installed.

GitHub tags

LMS plugins

LMS + Spotty "Failed to get Access token"

Hello, I'm getting:
"Failed to get access token Please check Settings/Advanced/Spotty Spotify for Squeezebox in the web interface"

I've deleted my account in the spotty plug in, restarted LMS, re-entered the account info to link with success. I've also reset my password and used the manual method for linking. Still getting the same error. Log says "Update Required"

server.log.zip

Thank you for all you do for us Michael!

Spotify Access Token keeps being Disabled and Blocked

Am using the Spotty plugin for years now, very happy with it. However, in the recent months or so my Access Tokens (Spotify Development) keep being Disabled and Blocked. If I look at the "endpoints" (I assume the # of API calls) is above 4k per day.

I am using 6 Spotify users on 1 LMS server, but am doing this for years already. Dus to this behaviour I have to create a new App in the Spotify Development portal, but this is not fixing the real issue. Anyone any idea?

Error: Failed to create session or connect to servers.

I've recently been trying to setup Spotify inside of Kodi using this addon which mentions using spotty from you repo. When entering the credentials, it uses spotty with the following arguments to get a token:

spotty.exe --cache
 "I:\Portable Programs\Kodi\portable_data\userdata\addon_data\plugin.audio.spotify/spotty-cache" --ap-port 54443 --verbo
se --enable-audio-cache --name temp-spotty --get-token --scope user-read-playback-state,user-read-currently-playing,user
-modify-playback-state,playlist-read-private,playlist-read-collaborative,playlist-modify-public,playlist-modify-private,
user-follow-modify,user-follow-read,user-library-read,user-library-modify,user-read-private,user-read-email,user-read-bi
rthdate,user-top-read -u *** -p ***

I've tried both my email address and username with the correct password, but still the title's error message is given. Can you tell me in more detail what this error means and why it occurs? Thanks in advance!

Played Tracks Not Added to Spotify Recently Played

Hi, I noticed quite a while back this issue was raised by you with librespot. I can't figure out what became of this issue. I think maybe it's on a librespot to-do list. What is your understanding of what's happening?

Spotty/Spotify-Connect: Essential firewall rules for the plugin to work are not described in the README.md

When your spotty plugin isn't running on a dedicated sound server like a Raspberry Pi, but rather on a home server, it is not a good practice to disable the firewall. I think it is good to be clear about which firewall rules are required. I now see spotty accepting connections on different port every time I restart (this is output from 'sudo netstat -tulpn |grep spotty' on my Ubuntu system):

tcp 0 0 0.0.0.0:33583 0.0.0.0:* LISTEN 26893/spotty-x86_64
udp 0 0 0.0.0.0:5353 0.0.0.0:* LISTEN 26893/spotty-x86_64
udp6 0 0 :::5353 ::: * LISTEN 26893/spotty-x86_64

So that port 33583 changes each time LMS (and spotty) restarts.
The 5353 is for the zeroconf/avahi/mdns/bonjour protocol that is being used I guess(?)

Could you describe how to configure a firewall in the README.md? I can not safely open it up for all incoming ports. That is against most good practices for a home server.
Personally I'm happy with a description about the necessary rules just for linux (ufw then preferrably), but a generic description of the necessary rules for all systems seems smart as well.

If the rules can be safely altered upon installation of the plugin itself that would be fine with me as well, but I can imagine that's against some good practices.

Maarten

Can Spotty Be Made to Work on Android

Hi, I'm trying to get the 'plugin.audio.spotify' plugin going again for Kodi (https://github.com/glk1001/plugin.audio.spotify). It works fine with the latest Spotty on Windows 10 and Ubuntu 22.04. Someone tried it on Android and it didn't work. From what I can see Spotty is not designed to work on Android. Is this the case?

spotty issue with default skin

My server freezes completely if there is any spotify song in the queue and I open the default skin web page.
This does not happen with the material skin.

I think this has something to do with the spotify cover. I was able to grab this from the logs:

[21-11-29 12:36:12.4407] Plugins::Spotty::API::ANON (1333) do {
my $a = { xxx }
[21-11-29 12:36:12.4414] Plugins::Spotty::API::Token::get (199) Found cached token: xxx
[21-11-29 12:36:12.4415] Plugins::Spotty::API::ANON (1329) Trying to read from cache for users/xxx/playlists?limit=50
[21-11-29 12:36:12.4416] Plugins::Spotty::API::ANON (1338) API call: users/xxx/playlists?limit=50
[21-11-29 12:36:20.4728] Plugins::Spotty::Connect::DaemonManager::initHelpers (90) Checking Spotty Connect helper daemons...
[21-11-29 12:36:20.4734] Plugins::Spotty::Connect::DaemonManager::initHelpers (120) This is the sync group's master, or a standalone player with Spotify Connect enabled: xxx
[21-11-29 12:36:20.4738] Plugins::Spotty::Connect::DaemonManager::initHelpers (120) This is the sync group's master, or a standalone player with Spotify Connect enabled: xxx
[21-11-29 12:36:20.4742] Plugins::Spotty::Connect::DaemonManager::initHelpers (120) This is the sync group's master, or a standalone player with Spotify Connect enabled: xxx
[21-11-29 12:36:52.5891] Plugins::Spotty::API::ANON (1435) error: Connect timed out:
[21-11-29 12:36:52.5896] Plugins::Spotty::API::ANON (1446) undef
[21-11-29 12:36:52.5910] Plugins::Spotty::API::Token::get (199) Found cached token: xxx
[21-11-29 12:36:52.5915] Plugins::Spotty::API::ANON (1329) Trying to read from cache for me/albums?limit=1
[21-11-29 12:36:52.5916] Plugins::Spotty::API::ANON (1338) API call: me/albums?limit=1
[21-11-29 12:37:24.7047] Plugins::Spotty::Connect::DaemonManager::initHelpers (90) Checking Spotty Connect helper daemons...
[21-11-29 12:37:24.7053] Plugins::Spotty::Connect::DaemonManager::initHelpers (120) This is the sync group's master, or a standalone player with Spotify Connect enabled: xxx
[21-11-29 12:37:24.7057] Plugins::Spotty::Connect::DaemonManager::initHelpers (120) This is the sync group's master, or a standalone player with Spotify Connect enabled: xxx
[21-11-29 12:37:24.7060] Plugins::Spotty::Connect::DaemonManager::initHelpers (120) This is the sync group's master, or a standalone player with Spotify Connect enabled: xxx
[21-11-29 12:37:24.7070] Plugins::Spotty::API::ANON (1435) error: Connect timed out:
[21-11-29 12:37:24.7074] Plugins::Spotty::API::ANON (1446) undef
[21-11-29 12:37:24.7078] Slim::Music::Import::countImporters (625) Found importer: Slim::Plugin::FullTextSearch::Plugin
[21-11-29 12:37:24.7079] Slim::Music::Import::countImporters (625) Found importer: Slim::Media::MediaFolderScan
[21-11-29 12:37:24.7079] Slim::Music::Import::countImporters (625) Found importer: Plugins::Spotty::Importer
[21-11-29 12:37:24.7080] Slim::Music::Import::countImporters (625) Found importer: Plugins::OnlineLibrary::Importer
[21-11-29 12:37:24.7129] Slim::Music::Import::launchScan (203) Running scanner using arguments: /usr/bin/perl (
xxx
)

I don't think I have any connection issues since it works perfectly with material skin. Songs are playing without any problem.

Logitech Media Server Version: 8.2.1 - 1634705759 @ Wed Oct 20 07:12:08 CEST 2021
Spotty v 4.6.2

LMS + Spotty plays a few seconds of a song, then skip to the next one

Using spotty from logitech media server, randomly, the system starts to behave incorrectly, playing only the first seconds of a song then skip to the next one. It happens with most of the songs, but sometimes a song is played to the end. Then it goes nuts again, or works fine for a while, it depends.

Looking at the processes, there is a lot of zombie spotty processes. I don't know if it is related though...

819      1120558  0.0  0.0      0     0 ?        Z    07:42   0:00 [spotty-x86_64] <defunct>
819      1120563  0.0  0.0      0     0 ?        Z    07:42   0:00 [spotty-x86_64] <defunct>
...
And hundreds more lines like these

I did not find anything relevant in the LMS logs.

---

Logitech media server 8.2.0 1627922070 running in a podman container on a fedora 35 OS
Plugin version Spotty v4.8.3
helper spotty v1.3.0 - using librespot 0.4.1 c5b689f (Built on 2022-06-04, Build ID: NGB9GMS0, Profile: release)

LMS/Spotty/Spotify-Connect usage: Last song stops playing 10 seconds before end

When I select a single song in the Spotify mobile or desktop application and play it with Spotify Connect (the devices icon in the bottom) on my Squeezebox Classic using LMS/Spotty, it always stops playing exactly 10 seconds before the end of the song. This does not happen when there are multiple songs in the queue, except for with the last one. Seems the playback gets stopped before the playback buffer is empty. My LMS/spotty server is an Ubuntu 22.04 LTS machine.

I have been searching for a solution for quite a while, but didn't find anything

Some *(new?) albums are skipping songs instantly - only on Spotify Connect

We use the Spotify Connect aspect of Spotty almost exclusively and it works beautifully. Recently my daughter started noticing that new albums are skipping after 1s of each track.

• Hozier: Unheard
• Declan Mckenna: What Happened to the Beach?

This is not an exclusive list but reliably don't work.

When I play them with spotty through the LMS web interface they play perfectly. It is only Spotify Connect that does not work.

LMS:

docker container running as "host" image on a Raspberry Pi4: lmscommunity/logitechmediaserver:stable

• Logitech Media Server Version: 8.5.1 - 1712473975 @ Mon Apr 8 04:13:10 CEST 2024
• Server HTTP Port Number: 9000
• Operating system: Debian (Docker) - EN - utf8
• Platform Architecture: aarch64-linux
• Database Version: SQLite

Player:

Raspberry Pi3B - quite old but works fine, max2play appears abandoned though so I may look at updating it
(we run two Squeezebox Radios but not as Spotify Connect devices - if I enable them as devices we get the same effect, so I guess it it not player related)

• Player Model: SqueezeLite
• Player Type: squeezelite
• Firmware: Max2Play v1.0.3 based on v1.8.7-999

Other information

• In Spotify developer site I have all the potential users entered as authorised users.
• I have none of the check boxes ticked at the bottom of settings
• I do have my Client ID entered (or nothing works)
• We usually run as one user as a "jam" but in testing the effect is seen with any user set up on Spotty

The relevant few seconds of trying to play Hozier are in the attached log with Spotty on "Info".

server.log