This is not the full log as requested. Just a partial cut and paste won’t help.
Sorry…
So, what’s the best way to give you the correcto log? This is exactly the live log from /dev…
Maybe this?
-- Logs begin at Thu 2019-02-14 11:11:58 CET, end at Sat 2025-05-10 20:31:16 CEST. --
May 10 20:09:43 volumio systemd[1]: Started Volumio Backend Module.
May 10 20:09:44 volumio volumio[983]: info: -------------------------------------------
May 10 20:09:44 volumio volumio[983]: info: ----- Volumio3 ----
May 10 20:09:44 volumio volumio[983]: info: -------------------------------------------
May 10 20:09:44 volumio volumio[983]: info: ----- System startup ----
May 10 20:09:44 volumio volumio[983]: info: -------------------------------------------
May 10 20:09:45 volumio volumio[983]: info: MYVOLUMIO Environment detected
May 10 20:09:45 volumio volumio[983]: info: Plugin folders cleanup
May 10 20:09:45 volumio volumio[983]: info: Scanning into folder /volumio/app/plugins/
May 10 20:09:45 volumio volumio[983]: info: Scanning category audio_interface
May 10 20:09:45 volumio volumio[983]: info: Scanning category miscellanea
May 10 20:09:45 volumio volumio[983]: info: Scanning category music_service
May 10 20:09:45 volumio volumio[983]: info: Scanning category plugins.json
May 10 20:09:45 volumio volumio[983]: info: Scanning category system_controller
May 10 20:09:45 volumio volumio[983]: info: Scanning category user_interface
May 10 20:09:45 volumio volumio[983]: info: Scanning into folder /data/plugins/
May 10 20:09:45 volumio volumio[983]: info: Scanning category user_interface
May 10 20:09:45 volumio volumio[983]: info: Plugin folders cleanup completed
May 10 20:09:45 volumio volumio[983]: info: -------------------------------------------
May 10 20:09:45 volumio volumio[983]: info: ----- Core plugins startup ----
May 10 20:09:45 volumio volumio[983]: info: -------------------------------------------
May 10 20:09:45 volumio volumio[983]: info: Loading plugins from folder /volumio/app/plugins/
May 10 20:09:45 volumio volumio[983]: info: Adding plugin upnp to MyMusic Plugins
May 10 20:09:45 volumio volumio[983]: info: Adding plugin airplay_emulation to MyMusic Plugins
May 10 20:09:45 volumio volumio[983]: info: Adding plugin upnp_browser to MyMusic Plugins
May 10 20:09:45 volumio volumio[983]: info: Loading plugins from folder /data/plugins/
May 10 20:09:45 volumio volumio[983]: info: Loading plugin "system"...
May 10 20:09:45 volumio volumio[983]: info: Loading plugin "appearance"...
May 10 20:10:57 volumio volumio[983]: info: Loading plugin "network"...
May 10 20:10:57 volumio volumio[983]: info: Refreshing Cached IP Addresses
May 10 20:10:57 volumio sudo[1024]: **volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0**
May 10 20:10:57 volumio sudo[1024]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 10 20:10:57 volumio sudo[1024]: pam_unix(sudo:session): session closed for user root
May 10 20:10:57 volumio sudo[1026]: **volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0**
May 10 20:10:57 volumio sudo[1026]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 10 20:10:57 volumio sudo[1026]: pam_unix(sudo:session): session closed for user root
May 10 20:10:57 volumio volumio[983]: info: Loading plugin "services"...
May 10 20:10:57 volumio volumio[983]: info: Loading plugin "alsa_controller"...
May 10 20:10:57 volumio sudo[1035]: **volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/iwlist wlan0 scan**
May 10 20:10:57 volumio sudo[1035]: pam_unix(sudo:session): session opened for user root by (uid=0)
May 10 20:10:58 volumio volumio[983]: info: CoreCommandRouter::executeOnPlugin: system , getSystemVersion
May 10 20:10:58 volumio volumio[983]: info: Loading plugin "wizard"...
May 10 20:10:58 volumio volumio[983]: info: Loading plugin "networkfs"...
May 10 20:10:58 volumio volumio[983]: info: Starting Udev Watcher for removable devices
May 10 20:10:58 volumio volumio[983]: info: Ignoring mount for partition: boot
May 10 20:10:58 volumio volumio[983]: info: Ignoring mount for partition: volumio
May 10 20:10:58 volumio volumio[983]: info: Ignoring mount for partition: volumio_data
May 10 20:10:58 volumio volumio[983]: info: CoreCommandRouter::executeOnPlugin: system , registerCallback
May 10 20:10:58 volumio volumio[983]: info: Loading plugin "volumio_command_line_client"...
May 10 20:10:58 volumio volumio[983]: info: Plugin upnp is not enabled
May 10 20:10:58 volumio volumio[983]: info: Loading plugin "my_music"...
May 10 20:10:58 volumio volumio[983]: info: Loading plugin "mpd"...
May 10 20:10:58 volumio volumio[983]: info: Plugin upnp_browser is not enabled
May 10 20:10:58 volumio volumio[983]: info: Loading plugin "alarm-clock"...
May 10 20:10:58 volumio volumio[983]: info: Plugin airplay_emulation is not enabled
May 10 20:10:58 volumio volumio[983]: info: Loading plugin "last_100"...
May 10 20:10:58 volumio volumio[983]: info: Loading plugin "webradio"...
May 10 20:10:58 volumio volumio[983]: info: Loading plugin "i2s_dacs"...
May 10 20:10:58 volumio volumio[983]: info: I2S DAC not set, start Auto-detection
May 10 20:10:58 volumio volumio[983]: info: Loading plugin "volumiodiscovery"...paste the url here:
Seems you need to flash a new image.
I see you have Now-Playing installed, you can create a backup in the plugin. make sure to copy the backup to your PC.
Ok… can I ask why is this happening?
This is a bit of a pain for me — having to open up my streamer and set everything up again… I just wanted to use Qobuz Connec 
I guess I can get the correct image here: Get Started - Volumio right?
Can I ask you how can I copy the plugin backup in my PC?
Thanks for your help,
I have a inside question about Qobuz connect, why is it not working with the dsp? And why does Tidal connect works properly. Will be Qobuz connect improved and fix this issue otherwise I can beter stop my Qobuz subscription. I just started because of the connect option (which I like), but I also like to use the dsp.
I believe I answered this one already for you:
Yes the fix for DSP has just been done. Few days and it will be released.
2 Likes
Don’t know what happened, hard to tell from the logs.
Yes, you can get the image there indeed. Get Started - Volumio
Backup your settings for Now Playing in the plugin settings.
The backup is placed /data/INTERNAL/NowPlayingPlugin/Settings Backups.
Install now playing again on your fresh image and copy the file back.
Import it again in Now Playing.
Great.
I’m going to do it and I’ll let you know.
1 Like
I don’t understand what just happened. I took the SD card out of the Raspberry, put it back in, and magically, it works!
Should I keep it like this if it works, or do you still recommend reflashing?
Thanks!
Thank you so much for your help.
Lastly, one hifi-guy question. I guess the sound quality both from Qobuz Connect and Volumio-straigth have to be the same, right?
Thanks!!
if it works, I wouldn’t opt for reflashing. Unless you still have errors.
1 Like
Is it normal that Qobuz Connect can only play hiRes songs? My Volumio plays them but Qobuz Connect via Qobuz Beta app only plays hiRez
Pure technical yes. However some people here experienced beter sound over connect. So I think it’s very personal.
The big advantage of Qobuz connect is that you can have all the goodies from the native Qobuz app.
2 Likes
I am sorry I missed that answer I have a intel NUC10. If I can help with log files or so let me know.
also this I guess 
1 Like
I am experiencing this behavior with my pi2AES Lite (RPi 3b) as well - playback doesn’t stop unless I clear the queue or switch to a different output in the Qobuz app. This does not happen when I use the connect feature with a RPi 4 running Volumio (similarly configured with a non-i2s DAC), only the pi2AES. Note that the i2s setting I’m using is the one recommended by pi2design (HiFiBerry Digi+ Pro).