Hello nerd
Thanks for the detailed instructions, they also solved my problem with getting SSH to work. Sorry for the delay in reply.
Here’s the file contents
=== WiFi Interface Summary ===
I see that AP is a supported mode and it did work when I used it with a new flash for Volumio 3. Is there anything that has changed in Volumio 4 that would make it worth a new flash of volumio 4 to see if the hot spot now works?
Here’s a log from a fresh flash of 4.012 on Pi5 8gb w/ nvme. Happy to report that I didn’t experience crashes with the previous 4.010 when installing plugins, especially Now Playing. This log shows me playing various files, including DSD. Outputs used were i2s/HDMI and spdif/coax from the HAT only, and NOT from the Pi itself, ever.
Log from Pi4b 8gb on USB on 4.012. Playback for all formats was fine thru USB output until activating PeppyMeterBasic and FusionDSP. I played around with it a bit and sound comes back in all formats including DSD upon stopped those 2 plugins again.
This gets confused everytime I report in details. No, I was not expecting DSD and FusionDSP to work together. When I turned those plugins on, all playback stopped. I only mentioned DSD as an “all format played” comment.
So again, playback of non-DSD files stopped when those plugins were turned on, and playback returned to normal after I turned them off.
please remove and reinstall peppymeterbasic, something is wrong in your logs:
Jun 16 23:34:28 volumio-pi4-beta volumio[1036]: error: PeppyMeterBasic ---Error writing config Error: ENOENT: no such file or directory, open '/data/plugins/user_interface/peppymeterbasic/BasicPeppyMeter/config.txt'
I did the same install with FusionDsp and peppymeterbasic and no issue…
Anyone else has issues using Tidal Connect? Tidal on Volumio works but can’t get Tidal connect to work anymore. Can provide logs if I am the only one having this issue. I get 401 when trying Tidal Connect but the same account works fine on tidal app and on Volumio tidal integration.
Edit: Logs
volumio : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0
pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
pam_unix(sudo:session): session closed for user root
volumio : PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0
pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
pam_unix(sudo:session): session closed for user root
info: CoreCommandRouter::executeOnPlugin: my_volumio , getAutoUpdateCheckEnabled
info: CoreCommandRouter::volumioGetVisibleSources
info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources
info: CoreCommandRouter::volumioGetState
info: CorePlayQueue::getTrack 3
info: CoreCommandRouter::executeOnPlugin: metavolumio , getInfinityPlayback
info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom
info: Error : CoreCommandRouter::executeOnPlugin: No method [getMultiroom] in plugin multiroom
info: Received Get System Info
info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CorePlayQueue::getTrack 3
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses
info: CoreCommandRouter::volumioGetState
info: CorePlayQueue::getTrack 3
info: Listing playlists
info: CoreCommandRouter::executeOnPlugin: appearance , getUiSettings
info: CoreCommandRouter::executeOnPlugin: system , getPrivacySettings
info: CoreCommandRouter::executeOnPlugin: updater_comm , getUpdateMessageCache
info: CoreCommandRouter::executeOnPlugin: wizard , getOnboardingWizard
info: CoreCommandRouter::executeOnPlugin: my_volumio , getMyVolumioStatus
info: Received Get System Info
info: CoreCommandRouter::executeOnPlugin: system , getSystemInfo
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getThisDevice
info: Discovery: Getting this device information
info: CoreCommandRouter::volumioGetState
info: CorePlayQueue::getTrack 3
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses
time=“2025-06-17T21:41:30+01:00” level=trace msg=“sent dealer ping”
time=“2025-06-17T21:41:31+01:00” level=trace msg=“received dealer pong”
systemd-timedated.service: Deactivated successfully.
[2025-06-17 21:41:38.686] [tisoc] [error] [WebsocketServerTls.cpp:90] [WebsocketServerTls onTlsInit Error] use_certificate_chain: no start line
[2025-06-17 21:41:38] [error] handle_transport_init received error: TLS handshake failed
[2025-06-17 21:41:38] [info] asio async_shutdown error: asio.ssl:167772567 (shutdown while in init)
[2025-06-17 21:41:38.686] [tisoc] [error] [WebsocketServerTls.cpp:103] Connection failed. Session State: 3, Error Code: 8, Message: TLS handshake failed
[2025-06-17 21:41:46.089] [tisoc] [error] [WebsocketServerTls.cpp:90] [WebsocketServerTls onTlsInit Error] use_certificate_chain: no start line
[2025-06-17 21:41:46] [error] handle_transport_init received error: TLS handshake failed
[2025-06-17 21:41:46] [info] asio async_shutdown error: asio.ssl:167772567 (shutdown while in init)
[2025-06-17 21:41:46.089] [tisoc] [error] [WebsocketServerTls.cpp:103] Connection failed. Session State: 3, Error Code: 8, Message: TLS handshake failed
info: CorePlayQueue::getTrack 3
info: CorePlayQueue::getTrack 4
info: Prefetching next song
info: [1750192916478] ControllerTidal::prefetch
info: Getting stream with soundQuality LOSSLESS
info: getStreamUrl took 276 milliseconds
error: Could not get TIDAL Stream URL: Could not get TIDAL Stream URL: failed to get stream from provider tidal: rpc error: code = PermissionDenied desc = failed to get track playback info: got 401: {“status”:401,“subStatus”:4006,“userMessage”:“Session does not have streaming privileges”}
time=“2025-06-17T21:42:00+01:00” level=trace msg=“sent dealer ping”
info: CoreStateMachine::startPlaybackTimer
info: CorePlayQueue::getTrack 4
time=“2025-06-17T21:42:01+01:00” level=trace msg=“received dealer pong”
info: CoreStateMachine::pushState
info: CorePlayQueue::getTrack 4
info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
info: CoreCommandRouter::volumioPushState
info: MRS: Pushing multiroomSync output update for this device
info: MRS: Pushing multiroomSync output
SPOTIFY: RECEIVED VOLUMIO VOLUME 14
SPOTIFY: SPOTIFY VOLUME 15
SPOTIFY: VOLUMIO VOLUME 14
SPOTIFY: DELTA VOLUME ENOUGH: false
arbitrabbit - If you go back somewhere in the earlier messages about this ‘beta’ release, “Tidal Connect” and “Qobuz Connect” aren’t working at present and are under developer review or something to that effect. Curious ‘connect’ worked in the ‘alpha’ release but not now.
ALSA device present and correctly defined as card PCH, device 1
Observed Issues:
Multiple restarts of the node /volumio/index.js process within a short window.
No direct stack traces or fatal exceptions are shown in the visible portion of the log, but there is heavy activity related to search endpoints.
/var/log/mpd.log consistently throws:
mixer: Failed to read mixer for "alsa": no such mixer control: PCM
This is benign and unrelated to TIDAL restarts.
Confirmation - Known Issue:
Yes, the symptom you are reporting (player restart while browsing TIDAL content, especially under the “Titles” tab) is already acknowledged as part of the Volumio 4.012 Known Issues, specifically:
TIDAL genre and moods search - Broken, reported
TIDAL Connect - Under developer review
This instability may manifest during metadata-heavy UI operations such as track or title search due to backend JS/REST timeouts, not due to device configuration or network.
Action:
No local fix is required or available at this point. Please hold for an upstream patch in a future OTA update.
Thanks for the detailed report and log. Great to hear that OTA from 4.011 to 4.012 went smoothly on your Pi4B setup with the 7" display and Topping D10s DAC.
Bluetooth, multiroom, media sources, and all listed plugins confirmed working - this is solid validation for Beta stability.
No errors of concern found in the log you linked (sqV4250). System initialized cleanly, and all plugins loaded without warnings.
Thanks once again for the update and for validating the OTA to 4.012 - glad to hear the process remains smooth and that your full hardware stack continues to operate reliably (apart from the known Bluetooth input issue).
I haven’t forgotten about the BT remote investigation. The matching controller has arrived, but I’m currently tied up with high-priority custom software builds. As soon as I clear that queue, I’ll begin focused debugging on the HID input handling path - including triggerhappy and related layers - to determine where the signal loss occurs.
Please continue sending your observations. Your consistent reports are helping to anchor this issue clearly within our regression tracking.
You’re using the “Audiophonics I-Sabre ES9028Q2M” profile.
The board is a generic TZT/Ustars clone of an ESS-based HAT.
Based on the log and your matrix:
Findings:
PCM up to 96/24 plays cleanly over i2s/HDMI and SPDIF.
192/24 on i2s shows playback active but no actual output to DAC. This could suggest either:
The HAT silently rejects 192kHz over i2s, or
The driver (snd-soc-i-sabre-q2m or overlay) is misreporting capability.
DSD fails on i2s when switching between DSD tracks. Initial track plays silently, next causes dropout. Classic sign of broken DSD DoP handshake or buffer negotiation failure.
All SPDIF playback OK, which aligns with the DAC likely handling SPDIF separately via onboard receiver.
Suggestions:
Consider trying “Generic I2S DAC” profile for further isolation. Many clone HATs diverge from Audiophonics’ true GPIO mappings or kernel expectations.
Also try toggling “DSD Direct” vs “DoP” modes if selectable.
Confirm that “Mixer Type” is set to None, to prevent software volume interference.
Thanks for the detailed logs again. I reviewed your Pi5 8GB + Waveshare 8.8in + 4.012 + i2s DAC log (A9LmhBF) and performed a full ASoC-layer error audit, including event context and frequency. Below is a structured breakdown for your internal debugging and potential escalation.
ASoC error summary and frequency
Error Message
Count
ASoC: CPU DAI bcm-i2s.0 not registered
7
ASoC: no DAI link
7
ASoC: failed to instantiate card -19
7
asoc-simple-card: probe of sound failed with error -19
7
snd_soc_register_card: failed to add platform sound/soc/bcm/ai-soundcard: -517
3
asoc-simple-card sound: ASoC: failed to instantiate card -517
3
Breakdown by event context
Event 1 - Early kernel boot (Timestamp: ~6s)
Lead-In Events:
Device tree loads overlay for the i-sabre DAC.
ALSA subsystem begins card registration.
Errors:
snd_soc_register_card: failed to add platform sound/soc/bcm/ai-soundcard: -517
asoc-simple-card sound: ASoC: failed to instantiate card -517
Explanation:
Probe deferred due to missing device or clock dependency (classic -EPROBE_DEFER).
Event 2 - Later boot (~8s to ~11s)
Lead-In Events:
ALSA resumes retrying card probe.
Errors:
asoc-simple-card sound: ASoC: CPU DAI bcm-i2s.0 not registered
asoc-simple-card sound: ASoC: no DAI link
asoc-simple-card sound: ASoC: failed to instantiate card -19
asoc-simple-card: probe of sound failed with error -19
Explanation:
CPU DAI “bcm-i2s.0” not present.
Platform binding fails.
Final ENODEV due to non-existent DAI node.
This sequence repeats 7 times across boot phases.
Interpreted root cause
Your clone HAT is triggering overlay “i-sabre-q2m”, which expects to bind to bcm-i2s.0.
On kernel 6.12.y, this DAI may have been renamed or its registration deferred/missing.
Overlay or kernel DAI schema mismatch is causing ASoC card creation to fail completely.
Next step
Please collect same set of logs from a working Volumio 3.x (kernel 6.6) setup with:
sudo dmesg | grep -i asoc
sudo journalctl -b | grep -i i-sabre
aplay -l
We suspect this is kernel/overlay regression between 6.6 and 6.12.
Notes
Working theory - your playback issue at 192kHz and DSD over i2s is not userland - it is rooted in DAI registration failure caused by overlay-driver mismatch or missing kernel binding logic.
Once 6.6 log is available, we can prepare a focused escalation to kernel maintainers if regression is confirmed.
Appreciate the logs and the clarity of your report - the 401 error and TLS handshake failures are a direct match with the issue listed in the Known Issues Tracker, already shown earlier in this thread.
To avoid duplication and help others track issue state more easily, please always check the known issues post if you’re reporting in the same thread - especially when it’s actively maintained and referenced just above.
That said, your logs confirm the existing issue and are still helpful for verifying that it’s not a local configuration fault.
You’re absolutely right. The core issue is that the backend plugins in the Volumio v4 Bookworm BETA are now rebuilt using OpenSSL v3, as required by the Debian Bookworm environment. However, the “Connect” service APIs (like TIDAL Connect and Qobuz Connect) are still running against OpenSSL v1 from the legacy Volumio v3 (Buster-based) backend.
In the ALPHA, things worked because some binaries were reused or compatibility layers existed. In the BETA, with clean builds, this mismatch causes failures.
Volumio developers need to deliver a clean and non-regressive solution that supports both ecosystems (v3 and v4), which is a non-trivial task due to the OpenSSL ABI differences.
