Thanks Darmur.
The upgrade to RPi-0W sounds like a good plan.
But maybe I have a different problem and leapt to a false conclusion:
After the Volumio app upgrade, I can discover my old RPi-0 devices, but pressing ‘connect’ returns a ‘Error connecting to the device’. Prior to the app upgrade they were working fine.
Any ideas?
Hi @nerd
Following @Darmur’s reply, I am thinking it isn’t Volumio V4.
But I’m not sure what is causing the issue, or which thread I should be posting in.
Ok the first impression is very sobering.
here the bugs i found so far:
Volumio 4.069 running on P3b with HifiBerry Dac 2 HD
Thats the bugs i found in the first 5 Minutes, i think i go back to the latest 3.x Release till its fixed
Hey @TrabaZoni,
Thank you for sharing your experience. As any other experience it is a matter of perception. For full assessment whether there is a real “bug” we have strict “bug” reporting requirements as you can read from here.
What we need from you
We need clear, complete, and specific information to help you. We do not have a crystal ball.
When reporting bugs, always include:
If your report involves hardware, include:
Full identification of the device:
What is connected to what, and how (USB hub, GPIO pins, power source, etc.)
You can see the result, but the big why is in the logs.
Kind Regards,
2 things I really want to see…
I. Please add a sticky post with changelogs and download links like in Volumio 4.xxx Beta thread.
I think that should be mandatory for all OS.
2.Please make available Plugin updates visible under Installed Plugins Tab. (I wrote this before)
Best Regards / C
Thanks for your reply, but creating the log is the next problem. It hangs sind 15 minutes in “Sending Log report, please Wait”
Thats what i see in Livelog Session
Starting Live Log…
info: CoreCommandRouter::getUIConfigOnPlugin
info: CoreCommandRouter::executeOnPlugin: appearance , getConfigParam
info: CoreCommandRouter::executeOnPlugin: appearance , getConfigParam
info: CoreCommandRouter::executeOnPlugin: appearance , getConfigParam
info: CoreCommandRouter::executeOnPlugin: appearance , getAvailableUIs
info: Received Get System Version
info: CoreCommandRouter::executeOnPlugin: system , getSystemVersion
info: CALLMETHOD: system_controller system enableLiveLog true
info: CoreCommandRouter::executeOnPlugin: system , enableLiveLog
info: Launching a new LiveLog session
wlan0: WPA: Group rekeying completed with 60:b5:8d:d3:52:f8 [GTK=CCMP]
Starting setdatetime-helper.service - Time Synchronization Helper Service…
setdatetime-helper: all HTTPS Date fallbacks failed
setdatetime-helper.service: Deactivated successfully.
Finished setdatetime-helper.service - Time Synchronization Helper Service.
Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories…
systemd-tmpfiles-clean.service: Deactivated successfully.
Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories.
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
wlan0: WPA: Group rekeying completed with 60:b5:8d:d3:52:f8 [GTK=CCMP]
Starting setdatetime-helper.service - Time Synchronization Helper Service…
setdatetime-helper: all HTTPS Date fallbacks failed
setdatetime-helper.service: Deactivated successfully.
Finished setdatetime-helper.service - Time Synchronization Helper Service.
Starting Live Log…
process exited with code nullwlan0: WPA: Group rekeying completed with 60:b5:8d:d3:52:f8 [GTK=CCMP]
Starting setdatetime-helper.service - Time Synchronization Helper Service…
setdatetime-helper: all HTTPS Date fallbacks failed
setdatetime-helper.service: Deactivated successfully.
Finished setdatetime-helper.service - Time Synchronization Helper Service.
info: CALLMETHOD: system_controller system enableLiveLog true
info: CoreCommandRouter::executeOnPlugin: system , enableLiveLog
info: Launching a new LiveLog session
info: Killing previous LiveLog session
info: Live Log process terminated: null
I spent this weekend updating my old Volumio installation to v4. I had some trouble with the touchscreen, but after some time, I figured out what the issue was: I did power down my raspberry pi, but did not unplug it from power. That’s why the display did not light up after starting volumio. Once I unplugged it before starting, it works as expected (and I’ve read about this here or in the raspi forum, but completely forgot about it 
)
Anyway, I do have a question regarding Volumio 4: The announcement says “There’s also a new plugin that lets you send audio from Volumio to Bluetooth speakers”. But I cannot find that plugin, the topics here are about an old plugin with an unclear status. Or is the topic well hidden? If anyone can hint me to the correct plugin, I would love to give it a try (that announcement was the main reason I updated to v4 in the first place)
Thanks in advance!
Hi @nerd,
Thanks, I’ll update as soon as I have a log ready. However, I wonder:
Volumio 4 was announced as solving the USB CD playback issues with drives over-reading that plagued V3. CD Playback is a Premium feature.
If power management has these strict policies on Bookworm, how was this tested before launch? Were only drives connected to powered usb hubs, or independent powered USB drives always the norm?
As for my Pi 4B’s specifications:
- Peripherals:
Nothing else is connected. No screens, dongles, devices, hats, GPIO attachments, etc. Plugins enabled: Spotify. Nothing else is installed.
PSU is the official RPi 15W USB-C PSU. No voltage drops or throttling warnings in past logs; no power issues recorded.
Will update with logs when ready. And thanks for the help!
Is there a forecast fix date for the WIFI dongle issues? txs.
The change/addition for these dongles are currently being tested, I expect it should reach the main release soon.
Power Breakdown for USB CD/DVD Drives
Power Breakdown Kingston 128GB Canvas Go:
3.3V ~ 400mA = 1.32W
USB Power Output Breakdown (Raspberry Pi 4 + Bookworm)
| Port Type | Max Current | Voltage | Max Power |
|---|---|---|---|
| USB 2.0 (x2) | 1.2A each | 5V | 6W total |
| USB 3.0 (x2) | 1.2A shared | 5V | 6W total |
| Total | – | – | ~12W |
So with all test I have done, the USB Drive was always powered by a hub. you might try to use a split cable to combine both USB2.0 (power) and USB3.0 (Data).
Both before (when prompted that new update was available) and after a fresh install with v4.069 all of Volumio’s system icons are missing and display as an empty rectangle.
What’s up?
Did you clear your browser cache?
Yes.
At first the icons disappeared (after a restart) when I told Volumio to ignore the update.
I then updated and the icons reappeared.
A large addition (≡75 new albums) require me to rebuild the library on SSD and fully reload the Volumio OS on its SD card. To avoid the update request I downloaded the v4.069 image.
As installed from the new v4.069 image the system icons are missing and nothing I do brings them back.
p.s. User-supplied artist art is still a total mess requiring lots of time, effort and seeming luck to get it to display. Multiple genres still refuse to separate as was presumably possible in the past. The entire “user” section of artwork that exists on the Volumio SD card [seems] to be utterly ignored.
@SwampeastMike
Moved your post to the correct topic. A bit surprised as V3 and V4 uses the same backend for Artist collection.
Hey @TubularBells,
Thank you for the detailed hardware specifications - that helps significantly.
Regarding your QA question:
The Volumio 4 announcement about “solving USB CD playback issues” refers to fixing the excessive CD re-reading problem from V3 (the “space shuttle takeoff” - constant high-speed disc reads). This was resolved with proper CD drive speed control in V4. This fix has nothing to do with USB power management or Bookworm’s stricter power enforcement.
CD playback functionality in V4 works properly with appropriate hardware configurations. Testing was conducted with various drive types including Blu-ray drives on Pi 5 with i2s DACs without power issues.
Your specific issue - power budget:
Based on your hardware specifications, here’s the power breakdown:
System power draw:
USB power draw:
As @Wheaten called out.
The problem:
Raspberry Pi 4B USB power budget: 1.2A total for ALL USB devices
During CD playback spin-up:
Kernel 6.12.x (Bookworm) strictly enforces USB power limits. Volumio 3 (older kernel) did not enforce these limits, which is why your setup worked before.
Diagnostic confirmation:
To validate this diagnosis with exact measurements, use a USB power meter/monitor (USB current monitor dongle) between the Pi and each USB device. Measure actual current draw during:
This will confirm whether you’re exceeding the 1.2A budget.
Work around:
Awaiting Logs:
The logs from http://volumio_IP/dev will confirm USB power enforcement messages in dmesg showing device disconnects due to insufficient power.
No rush - reply when you have the logs available.
Kind Regards,
I restarted my computer–not just my browser which is set to delete cookies on exit–and the icons are back.
Thanks and sorry for not thinking to restart my computer.
the version 4.069 has a problem with system log link generation, this has been fixed on version 4.071, just released as hot-fix
Please update your devices to 4.071 before trying to generate a system log link
Hi @nerd ,
here are finally the logs for the stuttering problem.
Server:
http://logs.volumio.org/volumio/sFQNSi0.html
Client
http://logs.volumio.org/volumio/fSLPz47.html
regards