Hey @Rochambeaux,
You flashed 4.084 and have the same issues. This confirms it is not a Volumio version problem.
Time Sync failure
Both your Pi 5 and x86 logs show:
setdatetime-helper: all HTTPS Date fallbacks failed
Your Pi 5 boots with the system clock set to 1970. NTP cannot resolve pool servers because DNS is failing. The HTTPS fallback also fails. With wrong system time, TLS certificates appear invalid and OAuth tokens get rejected - this common scenario where streaming services fail to authenticate.
DNS failures
Your x86 log shows Spotify failing 12 consecutive times with “device or resource busy” on DNS lookups. OAuth token refresh fails the same way.
@vmiguel already pointed you toward your network. Volumio works fine on multitude of installations. When identical failures appear across Pi 4, Pi 5, Pi 400, and x86, the problem is not Volumio - it is your local network. I can not reproduce the issue on my entire fleet from Pi Zero 2W all way up to CM5, and I mean every single Raspberry Pi SBC SKU.
Check your router. Some routers have unreliable DNS forwarding, caching issues, or rate limiting. Try configuring 8.8.8.8 or 1.1.1.1 as upstream DNS.
Why Tidal Connect works
Tidal Connect works because the Tidal app pushes to the device. Volumio does not need to initiate outbound connections or validate certificates for incoming streams. Qobuz, Spotify, and other services require Volumio to reach out and authenticate - which fails when DNS is broken and time cannot sync.
See also: [GUIDE] Volumio Time Sync Watchdog (setdatetime-helper)
Roon Bridge
This is a community plugin - issues should be raised with the developer here: [PLUGIN] Volroon - Roon Bridge plugin with metadata and control
We can help with official releases and beta - current version is 4.119.
Kind Regards,