Merry Christmas to the Volumio team and to all the Volumionauts!
I’ll test the latest dev release as soon as I’ll be back home! Thank you.
And a very merry Christmas to you @volumio !
You are entitled to a day off now and again!
Updated to 4.084
Pi5, NVMe boot, wired.
CPU use is low after boot, but I hadn’t noticed a problem before.
Log after a few minutes use following update:
http://logs.volumio.org/volumio/agNRRwe.html
Now back to the washing up.
I usually get problems with drive expansion after first install. I had some issues to get the touch display start working.
I flashed the SDcard like 5 times from the Raspberry pi imager and the file expansion failed all times. Raspberry pi imager run at a laptop with Debian OS and Volumio latest stable (4.073) raspberry pi3B+, also tested on raspberry pi4B with SSD-disk connected trough USB. Both same behaviour but works fine to do the drive expansion from the computer with GParted.
A positive observation from the latest ota update…both Pi5 and PC loaded “Now Playing” background and weather immediately right from boot up. Previously, these 2 devices may boot up with black background and no weather display until it first update cycle or manual screen update.
Updated both my pi5 to 4.073 and they can’t connect to wifi. Hotspot&fallback doesn’t seem to work either. Is this a known problem?
edit: After about 5 attempts (reflash the sd) hotspot showed up and after additional few attempts to set it up, it manged to connect to the wifi and seem to work. Configuring wifi while connected to ethernet didn’t work at all.
edit2: No problems upgrading both my pi3b+… Curious.
Excuse me, it’s not “too long”, scanning do not end. I left it working for three days, the log infinitely says this:
“info: CoreCommandRouter::executeOnPlugin: mpd , getMyCollectionStats”
After system restart Volumio cannot read music database, showing green stripe with no end.
I can get var/lib/mpd/tag_cash file through SSH, not broken. File has a complete end like this
“end: NAS”
I tried with new fresh 4.071 install and again with tag_cash deleted and saw the same behavior.
Do you need the whole log after “info: CoreCommandRouter::executeOnPlugin: mpd , rescanDB” ?
Hey @strumf666,
The WiFi problems you experienced on version 4.073 align with known issues that were addressed in subsequent releases. Version 4.082 and later include significant WiFi system improvements specifically targeting the connection and hotspot reliability problems you described.
Since your Pi5 systems are now running 4.084 with the latest WiFi fixes:
-
Are both Pi5 units connecting to WiFi reliably now?
-
Does hotspot mode activate properly when no known network is available?
-
Can you configure WiFi settings while connected via ethernet without issues?
If any of these problems persist on 4.084, please provide a fresh log link from http://volumio.local/dev so we can investigate whether there are remaining edge cases not covered by the recent fixes.
The difference in behavior between Pi5 and Pi3B+ during upgrades is expected - the Pi5 uses different wireless hardware (CYW43455 on Pi5 vs CYW43456 on Pi3B+) with distinct driver paths, which is why fixes sometimes need platform-specific attention.
Kind Regards,
Hey @learner,
Although you directed your post @volumio,
thank you for the additional detail - this helps narrow the problem space.
What you are describing:
The repeated getMyCollectionStats messages are normal behavior. This function polls MPD every few seconds during scanning to update the UI with track/album/artist counts. Seeing it continuously means Volumio believes a scan is in progress and is waiting for MPD to report completion. It is not the cause of the problem - it is a symptom.
What tag_cache “end: NAS” means:
The “end: NAS” line indicates MPD finished writing the database structure for your NAS mount point. However, this does not guarantee:
- The content between “begin: NAS” and “end: NAS” is valid
- MPD can successfully read the database back
- No corruption occurred during write
- All files were actually indexed
A structurally complete tag_cache can still contain invalid entries, encoding problems, or be unreadable by MPD due to version mismatch or corruption.
Why the green progress bar persists after restart:
On boot, Volumio queries MPD for database status. If MPD reports the database is empty, unavailable, or in an inconsistent state, Volumio shows the scanning indicator because it believes indexing is needed. The fact that this happens on fresh install with deleted tag_cache AND with existing tag_cache points to something in your library content or mount configuration.
What we need to investigate:
- Log link from http://volumio.local/dev - mandatory, no exceptions
- Hardware: exact Pi model (use identification guide if unsure)
- Music source: NAS brand/model, mount type (NFS or CIFS), share path
- Filesystem on NAS: ext4, NTFS, HFS+, Btrfs
- Library size: approximate track count
- Filenames: any non-ASCII characters (Cyrillic, Chinese, Japanese, accented European)
- File formats: FLAC, MP3, M4A, AIFF, or mixed
The log will show MPD’s actual database errors, mount status, and where exactly the process fails. Without it, everything above is speculation.
4.084 is current. 4.071 is over a month old and missing fixes that may be relevant.
Kind Regards,
Thank you, I should upgrade Volumio to latest version first.
Hello,
I’m having the same issue with my system. It’s been playing up recently so I did a fresh new image today. Works fine over wired connection but not over WiFi.
The WiFi ssid’s all show up, I can click and enter the password, it stays it’s restarting but nothing really happens after that. Full power cycle and it still won’t work.
Running the latest version, Pi3. Any ideas? Pi3
Hey @Bibio,
Thanks for reaching out. I can see you are trying to get help with an issue, but I am missing some essential information needed to investigate.
Do not worry - this is a common first-post situation and easily fixed.
Here is what I need from you:
- Device and storage - What hardware are you running Volumio on? Raspberry Pi 3 - great! Something else? Is it booting from SD card, SSD, or USB?
- Volumio version - The exact version number. You can find this in Settings, then System. It looks like “3.569” or similar.
- Log link - This is the most important part. Go to http://volumio.local/dev in your browser, click “Send,” and paste the URL it gives you here.
There is a helpful guide that explains all this in detail: Tips and guidelines to get faster help
Take your time reading through it. Once you reply with those details, I can actually dig into what is going wrong.
Kind Regards,
Hi, thanks for the swift response.
1.Yes Pi 3 running on SD card, with an Allo digione card fitted. Its been working for 4+ years.
2. 4.073 which should be the latest version
3. http://logs.volumio.org/volumio/Fd9oQ6o.html
Thanks very much
Hey @Bibio,
I moved your posts to this thread because the issue you describe has nothing to do with Volumio 3 - you are running Volumio 4.073 which is based on Debian Bookworm with an entirely different codebase and architecture.
Read this thread. It covers what has been reported, what has changed, and why.
Your log shows wireless.js at 61% CPU - the same pattern documented throughout this discussion.
Version 4.084 on the test channel includes a completely rewritten wireless.js that addresses this. Update and report back.
Kind Regards,
Hi @nerd, thanks very much.
Am I being an idiot, I can’t find the download for 4.084.
The latest I can find is 4.067 here Public Beta Test: Audio Without Compromise - Refining the Future of Volumio on Bookworm - #3 by nerd
Hey @Bibio,
To access the test channel:
- Go to http://volumio.local/dev in your browser
- Scroll to Update Channel Selection
- Change dropdown from Stable to Test
- Go to Settings then System
- Check for updates
4.084 will appear.
Kind Regards,
Unfortunately, my Primo 1 has completely stopped working. Neither my Fritzbox, Safari, nor the app can find it. The only thing that still works is the ringtone after I plugged it back in. It probably started updating on its own, without asking for permission. I hate it. It would be great if you offered the update as a downloadable file so I could put it on a USB stick.
hello!
1-By default, automatic update is disable. So unless you choose it, no update.
2-No volumio4 update is available (yet) for Primo.
So there is something else wrong.
As this is a Volumio hardware, a dedicated @volumio support will help you 
Hi,
I’m sorry to say that, for me , on my Pi 3B+ and on my Pi 4 the 4.084 release does not resolve the xruns (decoder is too slow) issue 
Here is the logs for the Pi4
https://logs.volumio.org/volumio/0FkooGm.html
Hi @nerd
Thanks for answering. All of my Pis are running 4.073; after I managed to get them working I had no further issues.
- They are still connected to the wifi after a few days and playback (webradio and tidal connect with or without multiroom) still works fine.
- I haven’t needed or tested the hotspot function after the initial setup.
- I haven’t tried past the initial few failed attempts when I figured out that setting the wifi through the hotspot works. Android app/hotspot wasn’t exactly flawless either, since the phone often reconnected to my home wifi in the middle of the setup, but in the end I was succesfull. This issue isn’t unique to the tidal android app, I have had the same problem with the shelly app so I am guessing it’s android/honor related.
Kind regards,
Peter