Public Beta Test: Audio Without Compromise - Refining the Future of Volumio on Bookworm

Volumio Development Volumio Beta Testing
, ,
427

I reinstalled IMG 4.020 (no OTA Update) and set it up using my own method - there are no problems with scanning before power off and power on again - after such a reboot the problem returns with NVME Music synchronization. I always used my method in versions 3.xxx 4.010-4.017 (the next release was installed by OTA update) there were no problems. Thank you for the correct method you specified,I did this earlier - I called the NVME SSD as “issd”, but the boot fails and needs to be reinstalled OS (now there is also an error loading Volumio to the image in the attachment)
Volumio OS 4.020 on SD card
MusicFiles on NVME SSD (not used for Volumio OS)

image1
image1964×366 31.2 KB

428

Hi everyone ! Thanks again a lot @nerd for all efforts and hard work and all people involved here !
This time, fresh installation of 4.020 on SD, and SD boot : everything is OK
RPi 4 - 4GB RAM
Touch Display Plugin (rotated 90°) with Official RPi Touch Display 2 powered by USB adapter
Squeezlite client : OK
Radioparadise : OK
DigiOne Signature : OK
Music FLAC (some tracks 24bits 192kHz) on CIFS NAS : OK
Last FM Scrobbler : OK
Logs after reboot :
http://logs.volumio.org/volumio/4wgfszA.html

Again great job guys !!! Thanks

1 Like
429

Hey @Raw ,

Thanks for continuing to test and report. However, I kindly ask that you do not rewrite or reword your previous posts multiple times during a debugging session. It makes it very difficult for us to track what changed between tests, what is working, and which specific conditions caused new failures.

We rely on precise and consistent data at the time of testing, especially when confirming regressions like those in version 4.020. Rewriting the same post with edits (especially after results or screenshots change) invalidates earlier analysis and wastes time during reproduction efforts.

From your latest message and the attached screen showing emergency mode on boot:

  • It appears that renaming your SSD label to issd may have triggered Volumio’s automount to /mnt/INTERNAL
  • But this automount likely clashed with your prior symlink or fstab override, resulting in boot failure

Please do the following in future posts:

  1. Do not edit previous posts with new results. Post a follow-up reply with exact logs or outcomes.

  2. Include one test case per reply, with:

    • Mount method
    • Label used
    • Was it OTA or fresh image
    • What plugins are installed
    • When the issue occurs (initial boot, after power-off, etc.)

  3. Always upload new logs or screenshots only after each test, not as retroactive edits.

That way we can isolate regressions and give clear help without backtracking.

Kind Regards,

430

Hey @Raw ,

The screen confirms that Volumio has dropped to emergency mode, which typically happens when a critical service or filesystem fails to mount during early boot. Based on your description, the most likely cause is the label-based automount attempt using:

LABEL=issd /mnt/NVME ext4 ...

If the NVMe drive is:

  • Missing
  • Mislabelled (label must match exactly, case-sensitive)
  • Or the filesystem is unclean or corrupt

Then systemd will treat this as a boot-critical failure and enter emergency mode unless the nofail option is present in /etc/fstab.

To find the exact cause, inside emergency mode, type:

journalctl -xb | grep -i "fail"

You’re looking for lines like:

  • Failed to mount /mnt/NVME
  • Dependency failed for Local File Systems
  • Timed out waiting for device labeled 'issd'

Also verify:

lsblk -f
blkid
cat /etc/fstab
ls -l /var/lib/mpd/music

This will help confirm whether:

  • The NVMe was detected
  • Its label matches issd
  • The fstab line caused the system to halt
  • A broken symlink is pointing to a non-mounted target

In general, we recommend avoiding manual fstab edits unless absolutely necessary. Volumio’s automount system expects internal drives with labels like issd to be mounted dynamically. If you still require persistent manual mounts, always include nofail to avoid emergency mode.

Please post the output of the above steps so we can confirm and help recover or rebuild cleanly.

Kind Regards,

431

OTA form V4.017 to V4.20, all went OK (Besides Spotify)

  • Model: Raspberry Pi 5 Model B Rev 1.0
  • Innomaker DAC Pro
  • Custom based Pyhton3 scripts for OLED
  • NAS NFS and CIFS mount
  • Qobuz
  • Tidal
  • Spotify (needs re-authentication after every reboot approx. since V4.014)
  • FusionDSP
  • IR Controller
  • Peppy Spectrum
  • IR Controller
  • Rotary Encoders
  • System Info
432

OTA from V4.017 to V4.20, all went OK.

  • Model: Dell Inc. Latitude 3189
  • Tidal
  • Qobuz
  • Spotify
  • NAS NFS and CIFS mount
  • FusionDSP
  • 80s80 Radio
  • Radio Paradise
  • Spotify (No need to re-authorize after reboot)
  • System Info
  • Peppy-Meter Basic
  • Peppy-Spectrum
  • Randomizer
  • Touch Screen
  • FN Brightness
  • FN Vol Up/Down
  • FN PrtScr
  • FN Mute
433

Hi,
if I understand correctly, TIDAL Connect is currently not available with Volumio on Bookworm, right?
Is there any ETA on when this issue might be investigated and resolved?

I activated TIDAL yesterday and want to drop Spotify, but not being able to use TIDAL Connect with Volumio would be a significant limitation for me. :frowning:

434

Issue Summary – Volumio V4.020

Both TIDAL Connect and Qobuz Connect appear to be broken on firmware version V4.020:

  • Qobuz Connect
    Error: “An error occurred while playing the current track.”
    This one seems intermitted after 4-5 failures it started to work.

  • TIDAL Connect
    Error: “Failed to connect to server. Check your internet connection…”

Jul 28 14:30:42 rpi5-es9038q2m vtcs[2061]: [close:85] Entering
Jul 28 14:30:42 rpi5-es9038q2m vtcs[2061]: [close:100] Exiting
Jul 28 14:30:42 rpi5-es9038q2m volumio[1267]: info: PlaybackInactive
Jul 28 14:30:42 rpi5-es9038q2m volumio[1267]: info: Device Session is_active: true
Jul 28 14:30:42 rpi5-es9038q2m volumio[1267]: info: DeviceInactive
Jul 28 14:30:42 rpi5-es9038q2m volumio[1267]: info: Relinquishing Volumio State
Jul 28 14:30:42 rpi5-es9038q2m volumio[1267]: verbose: UNSET VOLATILE: Service: tidalconnect
Jul 28 14:30:42 rpi5-es9038q2m volumio[1267]: info: unSetVolatile called
Jul 28 14:30:42 rpi5-es9038q2m volumio[1267]: info: Relinquishing Volumio State to another service
Jul 28 14:30:42 rpi5-es9038q2m vtcs[2061]: [2025-07-28 14:30:42.567] [tisoc] [warning] [SessionManagerImpl.cpp:240] Illegal State: IDLE
Jul 28 14:30:42 rpi5-es9038q2m vtcs[2061]: [2025-07-28 14:30:42.567] [tisoc] [warning] [PlaybackControllerImpl.cpp:520] Illegal state:0
Jul 28 14:30:42 rpi5-es9038q2m vtcs[2061]: [2025-07-28 14:30:42] [info] asio async_shutdown error: asio.misc:2 (End of file)
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioGetState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CorePlayQueue::getTrack 0
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioGetState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CorePlayQueue::getTrack 0
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: Currently active: tidal
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: Stopping currently active service
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioStop
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::stop
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::setConsumeUpdateService undefined
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::updateTrackBlock
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CorePlayQueue::getTrackBlock
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::stPlaybackTimer
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::pushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CorePlayQueue::getTrack 0
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioPushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioGetState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CorePlayQueue::getTrack 0
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::serviceStop
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CorePlayQueue::getTrack 0
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::serviceStop
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: [1753705846199] ControllerTidal::stop
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::setConsumeUpdateService mpd
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: ControllerMpd::stop
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: verbose: ControllerMpd::sendMpdCommand stop
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: SPOTIFY: RECEIVED VOLUMIO VOLUME 94
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: sendMpdCommand stop took 8 milliseconds
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: TidalConnect Active
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioGetState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: Currently active: mpd
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: Setting Volatile state to tidalconnect
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::setConsumeUpdateService undefined
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::servicePushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::pushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioPushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioGetState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::servicePushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::pushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioPushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioGetState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: SPOTIFY: RECEIVED VOLUMIO VOLUME 94
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: SPOTIFY: RECEIVED VOLUMIO VOLUME 94
Jul 28 14:30:46 rpi5-es9038q2m vtcs[2061]: [2025-07-28 14:30:46.432] [tisoc] [warning] [PlaybackControllerImpl.cpp:520] Illegal state:1
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: Pushing metadata
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::servicePushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::pushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioPushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioGetState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::servicePushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::pushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioPushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioGetState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::servicePushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::pushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioPushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioGetState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: SPOTIFY: RECEIVED VOLUMIO VOLUME 94
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: SPOTIFY: RECEIVED VOLUMIO VOLUME 94
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: SPOTIFY: RECEIVED VOLUMIO VOLUME 94
Jul 28 14:30:46 rpi5-es9038q2m vtcs[2061]: [2025-07-28 14:30:46.508] [tisoc] [error] [HttpClient.cpp:469] curl_easy_perform failed. reason:SSL peer certificate or SSH remote key was not OK further detail:SSL: couldn't get peer certificate
Jul 28 14:30:46 rpi5-es9038q2m vtcs[2061]: [2025-07-28 14:30:46.508] [tisoc] [error] [QueueWindowLoader.cpp:272] status code:99
Jul 28 14:30:46 rpi5-es9038q2m vtcs[2061]: [2025-07-28 14:30:46.514] [tisoc] [error] [HttpClient.cpp:469] curl_easy_perform failed. reason:SSL peer certificate or SSH remote key was not OK further detail:SSL: couldn't get peer certificate
Jul 28 14:30:46 rpi5-es9038q2m vtcs[2061]: [2025-07-28 14:30:46.514] [tisoc] [warning] [PlaybackEngineTidal.cpp:251] url fetch error: 0, 99,
Jul 28 14:30:46 rpi5-es9038q2m vtcs[2061]: [2025-07-28 14:30:46.514] [tisoc] [error] [PlaybackEngineTidal.cpp:323] Invalid response: body=, parse_error=unexpected end of input
Jul 28 14:30:46 rpi5-es9038q2m vtcs[2061]: [close:85] Entering
Jul 28 14:30:46 rpi5-es9038q2m vtcs[2061]: [close:100] Exiting
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::servicePushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreStateMachine::pushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioPushState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioGetState
Jul 28 14:30:46 rpi5-es9038q2m volumio[1267]: SPOTIFY: RECEIVED VOLUMIO VOLUME 94
Jul 28 14:30:46 rpi5-es9038q2m vtcs[2061]: [2025-07-28 14:30:46.944] [tisoc] [error] [HttpClient.cpp:469] curl_easy_perform failed. reason:SSL peer certificate or SSH remote key was not OK further detail:SSL: couldn't get peer certificate
Jul 28 14:30:46 rpi5-es9038q2m vtcs[2061]: [2025-07-28 14:30:46.944] [tisoc] [error] [QueueWindowLoader.cpp:272] status code:99
Jul 28 14:30:48 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
Jul 28 14:30:48 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
Jul 28 14:30:48 rpi5-es9038q2m volumio[1267]: info: Discovery: Getting this device information
Jul 28 14:30:48 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::volumioGetState
Jul 28 14:30:48 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses
Jul 28 14:30:50 rpi5-es9038q2m volumio[1267]: info: CALLMETHOD: system_controller system sendBugReport [object Object]
Jul 28 14:30:50 rpi5-es9038q2m volumio[1267]: info: CoreCommandRouter::executeOnPlugin: system , sendBugReport
Jul 28 14:30:50 rpi5-es9038q2m sudo[4664]:  volumio : PWD=/ ; USER=root ; COMMAND=/sbin/iwconfig
Jul 28 14:30:50 rpi5-es9038q2m sudo[4664]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Jul 28 14:30:50 rpi5-es9038q2m sudo[4664]: pam_unix(sudo:session): session closed for user root
Jul 28 14:30:51 rpi5-es9038q2m kernel: hwmon hwmon3: Undervoltage detected!
Jul 28 14:30:52 rpi5-es9038q2m ntpd[1112]: PROTO: 45.138.55.62 unlink local addr 192.168.1.215 -> 
Jul 28 14:30:52 rpi5-es9038q2m sudo[4769]:  volumio : PWD=/ ; USER=root ; COMMAND=/bin/journalctl -p 7
Jul 28 14:30:52 rpi5-es9038q2m sudo[4769]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)

These issues persist despite stable network conditions and proper account authentication.

435

You can still use Tidal Connect on Buster

1 Like
436

Hey Volumionauts,

With the release of Volumio V4.020 now available, it’s time to really put it through its paces. We encourage everyone testing the BETA to focus on real-world usage, especially premium MyVolumio features like TIDAL Connect and Qobuz Connect.

Please take a few minutes to verify their behavior and share detailed feedback. Confirm what’s working, what’s broken, and whether issues are consistent or intermittent. This will help us lock down regressions and get closer to a stable release.

Thanks for being part of this important phase.

Kind Regards,

FYI
@volumio, @devgianlu, @DED

437

In v4.xxx, persistent queue is not working.
Each reboot, Volumio starts with an empty playback page, but the queue is full
http://logs.volumio.org/volumio/vtGOZ51.html

image
image727×534 48.9 KB

edit : V4.0.20 On x86 (higole) samba share was not started
edit: the issue comes from BT enabled in sources! Disabling it fix the issue.

438

:test_tube: Feedback Report – Volumio V4.020 (Raspberry Pi 3 Model B+)

Device: Raspberry Pi 3 Model B+ + Allo Digione
Volumio Version: V4.020
DAC: SMSL RAW-MDA1 (Coaxial connection via Allo Digione)
Network: Ethernet

:musical_note: Local Playback

Format Status Notes
FLAC :white_check_mark: Different resolutions, including hi-res
MP3 :white_check_mark:
WAV :white_check_mark:
DSD :white_check_mark:

:repeat: Connect Features

Feature Working? Notes
TIDAL Connect :x: Error: “Failed to connect to server. Check your internet connection…”
Spotify Connect :white_check_mark:

:toolbox: User Interface & Control

Functionality Status Notes
UI Navigation Smooth
Track Switching Responsive
Mobile App :yellow_circle: I can’t adjust the volume from the official Volumio app on Android 16, but overall functionality and playback work fine.
“Play here” :yellow_circle: Tested on both mobile and desktop, using both Wi-Fi and mobile data connections. It’s ok, but with a weak connection, tracks sometimes skip or restart from the beginning. However, this has always happened, even with previous Volumio versions.

:jigsaw: Plugins & Extra Features

Plugin or Feature Working? Notes
Radio Paradise :yellow_circle: Very slow (at least today). “Please wait for radio channel…” then I had to wait up to two minutes before the audio started.
Spotify Plugin :white_check_mark:
LastFM Plugin :white_check_mark:
Now Playing :white_check_mark:

:speech_balloon: Notes

  • When I updated to Volumio V4.020 via OTA (from V4.017), I didn’t follow the update process on screen because I was busy with something else. After a few minutes, when I came back to check, I couldn’t reach the system—neither through the app nor by accessing the IP address in the browser.
    I had to power off and restart the Raspberry Pi manually. After rebooting, everything seemed fine, and the system correctly reports version 4.020.

  • It seems slower on startup (compared to V4.017).

LOGS: logs.volumio.org/volumio/wqiV44t.html

439

Hi @Ema82

I’ve seen this a couple of times, but only when I start to play RP before the final toast message from Volumio was shown (after reboot) or when switching between plugins (like 80s80s and RP). Did you do something similar?

440

No, I didn’t do any of the things you mentioned. I even tried rebooting, waited a few minutes after the system was fully up, and then started Radio Paradise—but the same issue occurred. I’ve attached the logs in the previous post in case it helps with further analysis.

442

Have you tried to reset the album cache?

444

Dear Volumionauts,

You asked - and the light has come.

We’re excited to share that Bluetooth remote support is now a reality in Volumio, thanks to the hard work and dedication of our talented @balbuze.

Introducing the BluetoothRemote plugin, now available as beta.

This plugin enables the use of compatible Bluetooth remotes with your Volumio system, offering a new level of control and convenience. It’s a long-awaited feature that many of you have requested, and we’re thrilled to see it take form.

Join the discussion, test the plugin, and give your thanks to @balbuze for bringing this powerful feature to life.

Kind Regards,

3 Likes
445

Yeah thumbs up again for @balbuze

@balbuze, notre maître des plugins, le roi du code, le magicien numérique qui fait danser nos extensions comme Edith Piaf sous les étoiles de Paris !

2 Likes
446

The bug also exists in Beta 4.020…
3-dot context in tile view partially not correct

447

This Bug still exists in 4.0.20

I have investigated the behaviour of the suggestions a bit more and found that they choke when the suggestion originates from my library (which sits on the NAS and has lastname, firstname artist format.
When the suggestions go from a qobuz album to a qobuz album (both firstname lastname artist format), they seem to work.

It would be great if the suggestion engine could go seamlessly between DLNA NAS, local storage and streaming services and between firstname lastname and lastname, firstname artist formats. But I am not holding my breath for that, given that UPnP search for MinimServer has not been implemented yet.

Some thought is needed how to not present suggestions that end up in a cul-de-sac and present an error.

448

Hallelujah.

1 Like