I believe Librespot.
Keep in mind that Volumio stepped in and delivered a replacement within 8 days.
Just being rude will not help. You might consider using some nuances.
There were two Spotify plugins, one based on the dedicated API, and one based on some (cryptically named ) vollibrespot.
The new plugin uses this vollibrespot as well, but has a lot of bugs that the old one didn’t have. So if you rushed it and made it in 8 days, why remove the old working one?
Sorry, all the nuance in the world won’t let me wrap my head around this.
Meanwhile Spotify announced that they kill the API in 2015 … So they actually had how many years?
But what ever dev weren’t probably paying attention to Spotify’s warnings so it hit them " out of the blue", so great job you rushed somethIng in 8 days…
But don’t kill the other working plug in for this rush job…
If you don’t want to use it …that’s fine by me
If you can code even better love to see your nice coding.
If you can’t code don’t talk about the work they did in a few days.
It’s a lot of coding and testing to get it to work.
In time this plug-in will be better.
And volumio just switched to the buster so a lot of things had to be fixed or re-written they are after Months still buzy with that.
If you like to kick against something pick a big stone instead of them.
You can only hurt yourself instead of the hard working guys who do a lot in there spare time.
Let me explain something.
The new plugin is based on the same lib ‘vollibrespot’ a fork of librespot made by @ashthespy than Spotify connect 2.
So it is supposed to do the same thing+ local Spotify browsing (done by the previous deprecated Spotify plugin using spop.)
As the new plugin is doing the same thing than the two others, it is the reason this now the only one.
Unfortunately, this is not as smooth as expected…
Sorry for this…
The old plugin is still available for a manual install: volumio-plugins/plugins/music_service/volspotconnect2 at alsa_modular · balbuze/volumio-plugins · GitHub
If it’s a “community developed plugin” and the Volumio them stepped in, great job … but you only need to read through posts like below to see why the sudden love for this “community developed” plugin… sorry let’s call it what it is. You guys have the Spotify logo on your landing page. Own it, or remove it.
Or if you replace a “community developed” plugin with a rush hack job… Then don’t just remove the working said “community developed” plugin?
Thanks to tips from @balbuze I now see I need to SSH and jump through other hoops to install what I could just click click and goo previously…