All of these streaming methods fall under different categories:
Spotify Connect - Community plugin
Qobuz Connect and Tidal Connect - MyVolumio proprietary premium plugins
All rely on the volumio3-backend, which is:
Primarily written for Buster / Node.js 14
Now running on Bookworm / Node.js 20
Shared between Buster and Bookworm builds
Most backend functions still work on Buster with Node 14.
The current failures are caused by race conditions and timing issues that surface under Bookworm with Node 20.
Either:
Volumio Core Team developers will need to take ownership, maintain and mend this shared backend code,
Or stem the Bookworm version and keep it separate. This is a Volumio decision.
Whichever way is chosen, this is outside the scope of the volumio3-to-volumio4 porting effort.
At this stage, the problems are core Volumio backend behavior, not the OS build base.
I have found that loading the plugin FusionDSP is a workaround. The plugin needs to be enabled but all of the DSP effects can be DISABLED. With this plugin my streaming and switching between spotify and qobuz is much more stable.
unfortunately my system stopped to work for my main usecase: Spotifyā¦
Iām still on 4.020 which worked like a charm until yesterdayā¦
I definitely have done nothing and Volumio stopped to play in the middle of a song and doesnāt come back since then.
Iāve seen Spotify disappeared from my sources - so I went to the plugin-config and reauthorize - this doesnāt help.
It seems Iām hitting the Spotify Authorization Issue , but in opposite to the statement in the answer āAnyway, the issue is just the UI, all configuration files are saved correctly and the plugin works as expected.ā - this is not true, my plugin doesnāt work as expected.
My log after fresh re-authorize is here.
Have tried: deinstall plugin, reboot, re-install (worked), re-authorize (worked) - but still no sound.
Playing any readio station - works.
Iāve read - spotify is not in focusā¦
Any idea haow to re-animate spotify on my volumio?
Or do I have to wait?
Apologies in advance as I donāt have a log that may provide better insight for development, however, I also suspect that it is perhaps not even an issue with Bookworm. Nor am I reporting for the sake of seeking remedial solutions and Iāve already fixed the issue.
Yesterday, my Pi5 lost all of its music from the NAS NFS shares. The shares were still there and āworkingā in Sources, but nothing showed for the artist/album/playtime columnsā¦not even 0. I tried to update and rescan to no avail, as well as rebooting several times. It felt as if the installed image got corrupted when I unplugged the power from the Pi5 the day prior. Out of desperation and before disassembling the streamer to flash the NVME, I removed the NFS shares, rebooted and added the NFS shares againā¦and it worked and is working fine now.
Pretty sure something broke when pulling the plug.
If you empierce other weird responses/behavior from the system, I would for sure opt for a āFactory Resetā
If I was to have an idea for developmentā¦one thing from that wishlist will be the ability to copy network shares settings directly from another Volumio device that it detects on the same network.
Iāve put it off to report this issue cuz I had no logs and I thought it was a user [me] error. But after the last instance of my Pi5 losing NFS shares, and attempting to factory reset and re-adding my shares, the Pi5 lost them again after reboot. As such, I decided that perhaps a fresh install of 4.021 may help. Upon reflashing, adding plugins and my shares on a fresh install, I then rebooted normally and it lost the NFS shares again. I donāt have a log from that instance but the following log is taking after I re-added the shares, left it overnight, and rebooted this morningā¦and again, the NFS share paths show but itās like it canāt rescan or update the content. I have other Volumio installs that are not showing this symptom so I havenāt ruled out itās something specific to me and not the betaā¦
ā mpd.service - Music Player Daemon
Loaded: loaded (/lib/systemd/system/mpd.service; disabled; preset: enabled)
Active: active (running) since Thu 2025-08-14 09:59:44 +07; 2h 52min ago
TriggeredBy: ā mpd.socket
Docs: man:mpd(1)
man:mpd.conf(5)
Process: 1988 ExecStartPre=/usr/bin/sudo /bin/chown mpd:audio /var/log/mpd.log (code=exited, status=0/SUCCESS)
Main PID: 1996 (mpd)
Tasks: 4 (limit: 4915)
CPU: 6.901s
CGroup: /system.slice/mpd.service
āā1996 /usr/bin/mpd --no-daemon
Aug 14 09:59:44 volumio-pi5-beta systemd[1]: Starting mpd.service - Music Player Daemonā¦
Aug 14 09:59:44 volumio-pi5-beta sudo[1988]: root : PWD=/ ; USER=root ; COMMAND=/bin/chown mpd:audio /var/log/mpd.log
Aug 14 09:59:44 volumio-pi5-beta sudo[1988]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Aug 14 09:59:44 volumio-pi5-beta sudo[1988]: pam_unix(sudo:session): session closed for user root
Aug 14 09:59:44 volumio-pi5-beta mpd[1996]: 2025-08-14T09:59:44 decoder: Decoder plugin āwildmidiā is unavailable: configuration file does not exist: /etc/ti>
Aug 14 09:59:44 volumio-pi5-beta systemd[1]: Started mpd.service - Music Player Daemon.
You mentioned this log was captured after remounting, but I donāt see any scan processes triggered. My initial suspicion is a permissions issue.
Could the credentials or access rights have changed, perhaps due to maintenance or modifications made from a Windows machine on those folders?
Please try running: sudo systemctl restart mpd
Then click āUpdateā in the Volumio interface.
If that still doesnāt work, run the following command and share the output: ls -ld /mnt/NAS/FLAC
This will help us check the permissions and mount on the FLAC mount.
But It seems you are not mounting it correctly, as your stating to use NFS. (Look at the // before Music) Your log shows:xx.xx.xx.xx:/mnt/TheKeyPool//Music/FLAC_Music But it should show:xx.xx.xx.xx:/mnt/TheKeyPool/Music/FLAC_Music
for my main usecase: Spotifyā¦
