Having the same issue. Guess I should’ve posted here.
https://community.volumio.com/t/spotify-wont-show-track-progress-anymore/64072
Small update:
This afternoon, I suddenly got the track progress back. And a little while later it broke again.
When it was working, I had the spotify desktop app playing and the android app also connected. I walked outside for a minute with my phone in my pocket and when I returned it had stopped working again.
Not sure if it’s related, but this is what happened. I’ll try to reproduce this scenario.
Hi
I detected an issue related to Spotify duo account. My wife and me have a duo. It works ok with librespot-based devices - we have two.
Usually we control Spotify from the app in our phones. I checked, it’s the same version.
We have also volumio installed on a raspberry. It worked ok until recently. She stopped seeing the volumio device on her phone. She now can’t connect to volumio unless I start a jam on it.
Could this be related to the plugin update?
Thanks
Hi Joaquim,
I am in exactly in the same situation with my wife’s Spotify Duo account.
Happily @balbuze turned out in another topic this can be solved by just not to login into the plugin’s logon ability - if i understood right.
That certainly will lead to not be able to browse Spotify from the Volumio UI - but- who cares if connect is doing the job.
I do not have time to check against currently for different reasons - sorry - @volumio - but that sounds logical to me.
Spotify changed the API - and the question for me, that may be the reason of this culprit is - how should Spotify know who is going to “connect”
in former times, when Volumio v2 was good to go with their old API there were 2 plugins for that, that did the job in a stable way.
So my thinking (yes i am not a coder but more some kind of itsec guy) is to develop 2 plugins again.
1 for beeing able to browse in the Volimio UI with authentification - and 1 for beeing able to let others in “Spotify DUO” - or Family accounts “CONNECT” - at least there is a big less in the documentation.
And to come before - sure there may be issues with authentication process, sure. I guess that could be solved with Spotify support.
Hi Josh.
I tried your workaround, it seems to work perfectly.
That is good enough for us, indeed we do not use volumio ui to control Spotify.
Thank you so much!
it is not me but @balbuze who checked first…
anyway i am happy to helped
- in other words - my family will be happy to know
and yeah - for sure - it always seems to be harder to document than to develop 
1 Like
Hi there. I started using Volumio today (moved from another audiophile RPi project). The audio quality is amazing. Great stuff.
I installed the Spotify plugin and it works fine if I use the iPhone app; however, it doesn’t work if I use the Spotify API (that is what I need in the end).
For instance, if I use the endpoint https://api.spotify.com/v1/me/player/play, I get a 404.
In the RPi I get this kind of errors:
volumio go-librespot[2583]: time="2023-12-06T21:53:07+01:00" level=error msg="failed unmarshalling dealer request payload" error="json: cannot unmarshal number into Go struct field RequestPayload.target_alias_id of type string" uri="hm://connect-state/v1/player/command"
I have a Raspberry Pi 4, the Spotify Plugin 4.0.3, and the latest Volumio image (3.569). I don’t have premium.
Any ideas on how to fix it?
Thanks.
Hi!
I am building two standalone portable music players for my kids with Raspberry Pi Zero W and Pirate Audio Headphone hat. I’m using Volumio + Spotify and Pirate Audio plugins. We have a Spotify family account and each of the kids have their own accounts. They DO NOT have a device to use Spotify Connect. Besides, I want them to be able to browse playlists and music from the portable music player.
This is working great so far… for a single player.
Is it possible to add functionality to allow multiple authorized Spotify accounts in the plugin?
The only other workaround I can see is to create a second Volumio account and manage them separately. Less than ideal, but if necessary I will go that direction. It would force me to stick with the free version of Volumio instead of upgrading to premium (not a threat, just a reality for me).
At any rate, really happy with Volumio. It is exactly what I needed to make these music players work.
Hi everyone, I’m new to this world and recently I installed the latest version of Volumio (v3.569) on my Raspberry Pi 4 and I noticed a big problem with all the latest Spotify plugin versions: shuffle playback doesn’t work and neither does smart shuffle. Also if I want to add or change the order of the songs in the queue, on the Spotify app they result as changed but on volumio they still go in playlist/album order. Why?
PS: I have Spotify Premium and all the other requirements
I am using a raspberry pi as a Spotify playback device using Spotify connect and the plugin. Problem here being that when I select a song to play from my computer and change the player to my pi, it only plays the songs in a certain order. If I pick a certain song, it only plays that and 3 others, and stops. If I choose another one however it plays that and 15 others but still in the same order. How can I fix this so it plays randomly?
I have problem with Spotify, volume level is too low, i tryied my Allo digione and raspberry pi4 with my dac, volume is full on spotify app and mixer is set NONE on Volumio. My streambox s2 ultra work just normally and spotify sound much more louder.
What would be problem ?
i used long time raspberry pi4 with my dac and spotify worked just normally, after updating volumio and spotify plugin this problem begins, i tryied to older versions of volumio and spotify plugin but not helped.
Encountered the same issue few weeks ago.The average SPL level is several dB’s quieter compared to the previous plugin implementation (it’s a total rework). When contacted the developer, it turned out that the plugin itself outputs multiplied samples according to Spotify’s volume level. This can’t be seen from the mixer. In certain configurations, Volumio also performs its own volume adjustment on top of the ALSA audio backend, i.e. the volume is then adjusted twice…
However, this is not the story end. In addition to this, volume normalization was done with a different default setting compared to the previous plugin implementation. This is now parameterized: the value of normalisation_pregain can be given from configuration parameters.
Can i make those changes by myself ?
I also have this issue
Hi
I experienced the volume issue with the latest Spotify plugin.
Reading the comments above, just i conclude teh issue will soon been solved in future version. Of the plugin or is it better to go with an older versio ?
Regards
Yes. Edit the following file using SSH:
nano /data/plugins/music_service/spop/config.yml.tmpl
Add the last line in config file:
log_level: trace
device_name: “${device_name}”
server_port: 9879
audio_device: “volumio”
device_type: “${device_type}”
bitrate: ${bitrate_number}
normalisation_pregain: 6.0
Then restart Spotify plugin from Volumio.
Finally, check that the normalisation parameter is applied:
cat /tmp/go-librespot-config.yml
volumio@volumio:~$ cat /tmp/go-librespot-config.yml
log_level: trace
device_name: "Volumio"
server_port: 9879
audio_device: "volumio"
device_type: "avr"
bitrate: 320
normalisation_pregain: 6.0
credentials:
type: zeroconf
HOX! When updating the plugin, this change may have to be made again until the plugin developers add it to the plugin’s settings in Volumio
Thank you very much for this!
Hi
Regarding Blamphos solution to edit congig.yml.tpml, how to check it is really 6dB that is needed?
I did it, seems to work in the sense that sound level increased a bit, but definitively not to the level i was used to.
=I would like to add more, but don’t know how much to go back to the former noise level with Spotify plugin. Is there a rule / somewhere it could be checked from the Raspberry Pi ?
[last time i had an issue, i could see the Alsa config not being OK, added 20dB back to normal! But it was visible on the Alsa meter. Here is different]
Thank you for this !
I addded normalisation pregain 6.0 but seems it not helped on my situation,
volume level is still very low.
is there option shut down whole volume normalisation ?
Spotify sounds now like there is only 50% volume even it is set full from app and and on volumio there is volume level max too.
Seems Tidal connect play normal volume level, so i think problem should be on spotify plugin.
This is a bit problematic and I really wonder why the team has not noticed this issue. As I mentioned in the original message, the go-librespot daemon running under the Spotify plugin adjusts the volume internally, i.e. the samples decoded by the Ogg Vorbis decoder are multiplied according to the Spotify volume level, which due to the large buffer size works quite slowly, i.e. is not very responsive if the volume is adjusted quickly.
This system works independently of the pregain_normalisation parameter, and since this was also a problem in my setup, where I wanted the actual volume control completely outside, I asked the developer to implement a parameter that bypasses the internal adjustment. When the line
external_volume: true
is defined in the config, then the volume level is adjusted only via Volumio and ALSA backend, i.e. Spotify’s Volume level messages only pass through the daemon in both directions. Maybe this will help in your case too.