This comment caught my attention.
I can’t comment on 4.072 to 4.073, but going from the last version 3 to 4.073, there is a slight edginess to the mids/highs, maybe a small tilt ‘forward’ in the overall sound. This seems to be the same on a couple of radio stations and Qobuz (via a USB DAC). I realize this may be highly context/system specific 
Hey @pwstereo,
This is significant. Fresh install reproduction eliminates accumulated state and configuration drift as factors.
Log analysis confirms identical failure pattern:
Timeline from: k0hc0iU.html:
Netstat at failure:
tcp 0 0 127.0.0.1:59176 127.0.0.1:6600 CLOSE_WAIT 1451/upmpdcli
tcp 15 0 127.0.0.1:42338 127.0.0.1:6600 CLOSE_WAIT 1451/upmpdcli
tcp 0 0 127.0.0.1:38000 127.0.0.1:6600 ESTABLISHED 1451/upmpdcli
tcp 1 0 127.0.0.1:38002 127.0.0.1:6600 CLOSE_WAIT 1451/upmpdcli
Node backend (PID 1702) shows ZERO connections to MPD port 6600. This matches your ethernet test exactly - after MPD restart, the backend does not reconnect.
Secondary observation: MPD log shows “No such playlist” exception after nearly every successful playback. This may contribute to connection churn, though root cause remains the reconnection failure.
Pattern:
You mentioned adding stations to My Web Radios before testing. My tests used only the built-in radio directory. This could be relevant if custom stations trigger different code paths - though I suspect it is not the differentiator since the failure mechanism is backend reconnection, not stream handling.
Current status:
This meets the threshold for serious investigation. The evidence points to a backend issue with MPD connection management. Before suggesting a GitHub issue, I want to attempt reproduction on a Pi 3 to match your hardware class. Still dealing with priorities.
One request: after your next failure, before restarting, could you SSH in and run:
cat /proc/$(pgrep -f "node /volumio/index.js")/fd/* 2>/dev/null | head -100
This would show what file descriptors the backend process has open, which might reveal whether it is attempting connections that are stuck.
Kind Regards,
Hey @mogelsvs,
V3 to V4 is a major architectural jump - Debian Buster to Bookworm, kernel upgrade to 6.12.x, updated MPD version, ALSA library changes, potentially different default buffer and resampling settings. Unlike the 4.072 to 4.073 comparison, there is actual technical substance here that could theoretically produce different behavior.
However, without verified identical playback settings between your V3 and V4 installations, logs showing MPD configuration from both, and level-matched blind A/B comparisons, we cannot isolate variables. This is subjective audiophile territory which is difficult to address with technical evidence alone. Perceived differences without controlled testing cannot be reliably attributed to software changes versus expectation bias.
If you want to dig deeper, provide logs and playback settings screenshots from both versions and we can compare configurations for actual measurable differences.
Alternatively you can remain on v3 if this is your preference:
Kind Regards,
OK, I used the volumio account to login with Putty, created the issue by changing web radio stations, then ran the command. It produced no output in the Putty terminal session. Had to Ctrl-c to get the command prompt back, tried it a couple of times, same result.
Then ran a log upload in case the cat output is there (seems unlikely).
http://logs.volumio.org/volumio/ku1YnqK.html
Hi @nerd,
Thanks for taking time for the thoughtful reply!
My “OCD” would not do well with rolling back to V3 so the ears/imagination will have to adjust 
I am a lifetime subscriber and can’t imagine listening to V3 in year 2050 
Cheers, Soren
Dear Volumionauts,
Volumio version 4.074 introduces significant changes to WiFi and network management. This release is experimental and requires careful consideration before updating.
What changed:
This version implements a new wireless management system designed to address networking issues that have affected the Bookworm-based Volumio 4 platform since its release.
Important warnings:
Who should update:
Who should wait:
If you encounter network issues after updating:
The only guaranteed recovery path is a fresh flash. Have your SD card imaging tools ready before updating.
Feedback on this experimental release helps identify remaining issues. If you test this version, report your hardware configuration and any problems encountered.
Kind Regards,
Testing v4.074
RPi 5
SD card 32 GB
IQAudio DAC Pro Hat
QOBUZ
NAS OpenMediaVault audio library approximately 45000 tracks
Successfully updated OTA wireless connection from v4.073 to v4.074
No problems encountered - will now boot from either Ethernet or WiFi
Hope this information is what you need to hear !
regards, Michael
A big update on the switching web radio stations breaking MPD.
Today I built a new Raspberry Pi 5 (8GB) setup with Allo Boss V1.2 and the default cooler.
Ran through basic setup, all good. Re-scanned USB music library, all good.
Started it playing one of the Radio Paradise radio stations, all good.
Went through and added all my web radio stations to My Web Radios, all good.
Played each web radio station in turn to test and confirm stream URLs all OK, failed after 12 or so stations were swapped.
Same symptoms as on the R Pi 3B+, no more web radios will play, no list under Artists for the music library.
Hi @nerd
I did the OTA from 4.073 to 4.074
Pi5, wired connection, USB DAC, NVMe boot
Update was successful and GUI accessible via my network.
In network settings is showed both my wired connection and details of a wifi hotspot address next to it.
Test 1
Test 2
Conclusion: wifi/ethernet hot switching is working as intended!
Hi @nerd!
OTA from 4.073 to 4.074
Rpi 5, Wifi connection , NVME boot
All went fine. Reboot is very fast.
I have nothing more to say than other members already said in erlier posts.
This seems to be a very important update for Volumio Bookworm.
Best Regards / C
After a long time planning I recently started to use Volumio partially in Multiroom, had some minor issues and was glad to find that there is a new version just released. Hope it solves the small issues. A bit unstable, and maybe worst, if I start one system (with fixed volume amplifier) it tells the volume right but starts at max volume.
Yesterday I took some time to start installning the new Volumio 4 on my Audiophonics RASPDAC mini LCD (With an pi4B 1GB). After the installation I didn’t find any Volumioxxxx hotspot at all. Connected it to the wired LAN but couldn’t even see it connected to the network port. Thought I did something wrong while flashing the SD-card so I reflashed the card, took the image from the pi image tool this time, showed up that I used 3.8x worked flawlessly. Reflashed the card with volumio 4. Same thing. Didn’t see it from WIFI, connected by wire but still couldn’t see any unit (LED lighted up at the pi itself).
Finally I put the SD-card in another player with a pi 3B+. Now the hotspot showed up. I made some settings and connected it to the home network.
After moving the card back to the pi4B in Audiophonics casing everything worked flawlessly.
I’m not sure about what happened.
Didn’t really used it yesterday since everything took much longer than expected, but seem to work really fine and seems a little bitt quicker.
Saw I wasn’t able to connect multiroom between the Volumio 3 device (the one I used to manage to boot Volumio 4 SD-card) This wont be a problem since this will probably be updated today. But it will give the problem that I won’t be able to play multiroom together with my Volumio Primo device for some time.
Hi @nerd
OTA from 4.074 to 4.075
Pi5, USB DAC, NVMe boot, wired connection
Update successful
Different behaviour to previous version:
Hi @nerd
OTA from 4.075 to 4.076
Pi5, USB DAC, NVMe boot, wired connection
Update successful. Wired and Wireless Hotspot visible in the network settings.
After disconnecting the ethernet cable:
After reconnecting the ethernet cable
Power off while on wired / disconnect ethernet cable / restart:
Hi @nerd
I also updated on my Pi 3B+ from 4.073 to 4.076.
When update was done, unplugging the Ethernet cable instandly lead to a switch to WiFi.
Also after a subsequently reboot the system has connected to WiFi successfully.
Hi @nett_flanders and @nerd
My bad. I rebuilt this system a few hours ago after it crashed testing a plugin. I didn’t re-enter my wifi password.
I can confirm what @nett_flanders says - it switches immediately over to wifi when the ethernet cable is disconnected.
Sorry for any confusion caused.
Edit: the switchover is so fast that a song playing is not interupted!
Hello @nerd,
I have a question regarding Volumio 4 and a fan control script from Argon.40 that I’ve used before without issues on V3:
I use an Argon ONE case (Argon One V2 for RPi 4B: Argon ONE V2 Case for Raspberry Pi 4 – Argon 40 Technologies Web Store) which uses a GPIO fan controlled by a script. The script, as per the manual states, installs via SSH with the following command:
curl https://download.argon40.com/argon1.sh | bash
This worked fine under Volumio 3. I could then run argonone-config to set my fan operation parameters without issues. However, on Volumio 4, I’m running into the following error when I try to install:
>
> ...
> ***********
> Argon Setup
> *************
> 100 22747 100 22747 0 0 35772 0 --:--:-- --:--:-- --:--:-- 35765
> Installing/updating dependencies...
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> E: Unable to locate package python3-libgpiod
> ********************************************************************
> Please also connect device to the internet and restart installation.
> ********************************************************************
Is there an issue with python3-libgpod in Volumio 4? Thanks for the help.
Hey @TubularBells,
Before running the Argon40 installation script, you need to refresh your apt package cache:
sudo apt update
Then retry the installation:
curl https://download.argon40.com/argon1.sh | bash
The error “Unable to locate package python3-libgpiod” typically occurs when apt does not know what packages are available. The package exists in Debian Bookworm repositories - apt just needs to be told to fetch the current package lists first.
The Argon40 script assumes apt cache is current and does not perform this step itself.
Let me know if the installation succeeds after the update, or if you encounter a different error.
Kind Regards,
Thanks @nerd for the quick reply and help!
I updated the cache, then ran into errors connecting to a specified source mirror. I ended up installing python3-libgpiod individually (with sudo apt-get install python3-libgpiod) and then running the curl install script again. The fan is working now 
.
Hey @nerd
I updated Volumio 4.074 to 4.076 on both rPi4 wired and rPi5 through wifi.
After the update, wlan and lan were shown as active. rPi4 was also connected to both lan and wlan. The update also took a very long time.
rPi5 was also connected to wlan and lan (127.0.0.1)
It would be good if the update process could read the previous OS network settings if possible.
Or maybe it’s just me who experienced the same behavior after updating?
Best Regards / C
Hey @nerd !
Thanks for last update to 4.078
Updating worked well and no strange network behaviour at start up.
Best Regards / C