See post 
Or via Volumio.com
Thanks, but I figure that that thread is no longer being updated and the dev team has migrated to this thread for updates.
Nope, it’s now running on the Stable and Test releases.
Stable release can be downloaded from Volumio.com.
If you enable test, you get the test updates.
Same as with V3.
@alkjones76 @Wheaten @nerd
Issue located, I’m currently compiling a new kernel, now including support for RTL8812BU/RTL8822BU.
For some reason, support must have dropped out in one of the early beta releases.
2 Likes
Hi @gkkpch
I found that till V4.014 it was included as of V4.015 it’s failing.
Thanks for looking into this.
@Wheaten Let’s hope this was only a configuration issue and no other issues pop up.
Kernel 6.12.y is the first release with fairly stable mainline driver support for a series of Realtek 801.11ac chipsets, but fixes are still being applied from upstream.
The configuration fix will be applied to the next image version.
1 Like
Yeah!!!
Hi Everyone,
i just updated to Volumio 4 on my RPi 4 and have problems with the multiroom grouping.
If i try to add my second RPi 4 (Volumio 4 aswell) the music is just stuttering.
It is not possible to listen to music this way…
The moment i ungroup the device, the music is running smoothly.
Multiroom was the only thing why i upgraded my subscription from virtuoso to premium…
I also tried the current Volumio Version 4.069 from the testing feed but that didn’t help either.
With Volumio 3 the grouping was already kind of gambling if it connects on the first try without restarting one of the devices…
Can someone help me?
Starting Live Log…
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 6482
info: CoreCommandRouter::executeOnPlugin: network , getCachedIPAddresses
info: CALLMETHOD: system_controller system enableLiveLog true
info: CoreCommandRouter::executeOnPlugin: system , enableLiveLog
info: Launching a new LiveLog session
info: CoreCommandRouter::executeOnPlugin: multiroom , enableAudioOutput
info: MRS: Setting this device as multiroomSync server
info: MRS: Setting another device as multiroomSync client
info: MRS: Setting this device as Server
info:
[1763063720985] ---------------------------- MRS: Setting Multiroom Server
info: MRS: Pushing multiroomSync output
info: Enabled audio output: 3242befe-5780-4f98-93ca-4d17db68c40d
info: MRS: STARTING SNAPCLIENT
info: MRS: Updating multiroomSync output
info: MRS: Updating multiroomSync output
info: MRS: STOPPING SNAPCLIENT
volumio : PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart volumioSnapclient
pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Started volumioSnapclient.service - Snapcast client.
pam_unix(sudo:session): session closed for user root
info: MRS: SNAPCLIENT STARTED
2025-11-13 20-55-21.158 [Info] (Snapclient) Version 0.26.0
2025-11-13 20-55-21.174 [Info] (Avahi) (Browser) CACHE_EXHAUSTED
info: MRS: STARTING SNAPSERVER
info: MRS: enable multiroom server output
info: MRS: Set multiroom target PCM to volumioMultiRoom
info: Changed audio target for /tmp/multiroom/server/switch.target to volumioMultiRoom
info: MRS: Set multiroom target PCM to volumioLocalPlayback
info: MRS: Snap server restart
info: Changed audio target for /tmp/multiroom/client/switch.target to volumioLocalPlayback
volumio : PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart volumioSnapserver
pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Started volumioSnapserver.service - Snapcast server.
pam_unix(sudo:session): session closed for user root
info: MRS: SNAPSERVER STARTED
Version 0.26.0
Adding source: pipe:///tmp/multiroom/server/fifo?name=Radio&sampleformat=48000:16:2&codec=flac
Settings file: “/var/lib/snapserver/.config/snapserver/server.json”
Using HTTP host name: volumio
Adding service ‘Snapcast’
PcmStream: Radio, sampleFormat: 48000:16:2
PipeStream mode: create
Stream: {“fragment”:“”,“host”:“”,“path”:“/tmp/multiroom/server/fifo”,“query”:{“chunk_ms”:“100”,“codec”:“flac”,“name”:“Radio”,“sampleformat”:“48000:16:2”},“raw”:“pipe:////tmp/multiroom/server/fifo?chunk_ms=100&codec=flac&name=Radio&sampleformat=48000:16:2”,“scheme”:“pipe”}
Init - compression level: 2
Creating TCP acceptor for address: 0.0.0.0, port: 1705
Creating HTTP acceptor for address: 0.0.0.0, port: 1780
Creating stream acceptor for address: 0.0.0.0, port: 1704
Number of threads: 4, hw threads: 4
State changed: Radio, state: idle => playing
onStateChanged (Radio): playing
2025-11-13 20-55-22.255 [Info] (Avahi) (Browser) CACHE_EXHAUSTED
2025-11-13 20-55-22.452 [Info] (Avahi) (Browser) NEW: service ‘Snapcast’ of type ‘_snapcast._tcp’ in domain ‘local’
2025-11-13 20-55-22.454 [Info] (Avahi) (Browser) NEW: service ‘Snapcast’ of type ‘_snapcast._tcp’ in domain ‘local’
2025-11-13 20-55-22.491 [Info] (Avahi) Service ‘Snapcast’ of type ‘_snapcast._tcp’ in domain ‘local’:
2025-11-13 20-55-22.491 [Info] (Avahi) volumio.local:1704 (127.0.0.1)
2025-11-13 20-55-22.494 [Info] (Controller) Found server 127.0.0.1:1704
2025-11-13 20-55-22.494 [Info] (Connection) Resolving host IP for: 127.0.0.1
2025-11-13 20-55-22.494 [Info] (Connection) Connecting
2025-11-13 20-55-22.494 [Notice] (Connection) Connected to 127.0.0.1
2025-11-13 20-55-22.494 [Info] (Connection) My MAC: “dc:a6:32:ba:18:62”, socket: 8
StreamServer::NewConnection: 127.0.0.1
Hello from dc:a6:32:ba:18:62, host: volumio, v0.26.0, ClientName: Snapclient, OS: Raspbian GNU/Linux 12 (bookworm), Arch: armv7l, Protocol version: 2
2025-11-13 20-55-22.521 [Info] (Controller) ServerSettings - buffer: 2000, latency: 0, volume: 100, muted: 0
2025-11-13 20-55-22.522 [Info] (Controller) Codec: flac, sampleformat: 48000:16:2
2025-11-13 20-55-22.522 [Info] (Player) Player name: alsa, device: volumioMultiRoomClient, description: , idx: 14, sharing mode: unspecified, parameters:
2025-11-13 20-55-22.522 [Info] (Player) Mixer mode: software, parameters:
2025-11-13 20-55-22.522 [Info] (Player) Sampleformat: 48000:16:2, stream: 48000:16:2
2025-11-13 20-55-22.522 [Info] (Alsa) Using default buffer_time: 80 ms, default fragments: 4
2025-11-13 20-55-22.524 [Info] (Alsa) PCM name: volumioMultiRoomClient, sample rate: 48000 Hz, channels: 2, buffer time: 80000 us, periods: 4, period time: 20000 us, period frames: 960
2025-11-13 20-55-22.525 [Info] (Stream) No chunks available
2025-11-13 20-55-22.525 [Info] (Alsa) Failed to get chunk
2025-11-13 20-55-22.542 [Info] (Controller) diff to server [ms]: -0.001
Service ‘Snapcast’ successfully established.
info: MRS: Updating multiroomSync output
StreamServer::NewConnection: 192.168.178.46
Hello from dc:a6:32:3c:b9:7d, host: volumiowz, v0.26.0, ClientName: Snapclient, OS: Raspbian GNU/Linux 12 (bookworm), Arch: armv7l, Protocol version: 2
[2025/11/13 20:56:17.311901, 0] …/…/source3/nmbd/nmbd_namequery.c:109(query_name_response)
query_name_response: Multiple (2) responses received for a query on subnet 192.168.178.54 for name WORKGROUP<1d>.
This response was from IP 192.168.178.10, reporting an IP address of 192.168.178.10.
Thanks.
Where can i download volumio 4?
The latest update version is 3.866 from auto updates.
Here Volumio.com
Hey @Kampf_Keks_3000,
We need complete information to diagnose multiroom stuttering. The log excerpt you provided is partial and appears to be from only one device.
Required information:
-
Full logs from BOTH devices:
- Server device: http://volumio_server_IP/dev
- Client device: http://volumio_client_IP/dev
- Paste both complete log URLs here
-
Clear device identification:
- Server Pi: hostname, IP address
- Client Pi: hostname, IP address
-
Network connection for BOTH devices:
- Server: WiFi (2.4GHz/5GHz) or ethernet?
- Client: WiFi (2.4GHz/5GHz) or ethernet?
-
Music source:
- What are you playing? (streaming service, local files, web radio?)
- If local files: where stored? (SD card, USB, NAS?)
- What quality/bitrate?
Multiroom stuttering is typically caused by network issues (WiFi latency), insufficient bandwidth, or storage access conflicts. Every detail matters for proper diagnosis.
Kind Regards,
Hey @jocoman,
Hold on - do not pull that NVMe drive yet.
Use the Install to disk feature in the Volumio UI instead (Settings > System > Install to disk). This installer is optimized for storage device installations as opposed to microSD. There is a technical reason why it has been introduced - it handles partition layout, boot configuration, and data properly for NVMe/SSD devices.
Manual imaging with Balena Etcher or Raspberry Pi Imager will work, but you will bypass the optimizations built into the installer.
Kind Regards,
Hey @jocoman,
That timeline is very helpful - worked fine in V3.013, survived OTA updates, broke after upgrading to V4.067. Then fresh install of V4.067 never worked.
The kernel jumped from 6.12.34 to 6.12.47 between your working and non-working states. Your TP-Link Archer T3U uses the RTL8822BU chipset, which has known upstream bugs (fixed before) in the rtw88 driver:
- AP mode beacon failure (TX report mechanism timeout - firmware never sends C2H acknowledgments)
- Cold boot USB failure (USB register write fails with error -71 EPROTO at register 0x4e0 during initialization)
The cold boot USB failure matches your “waiting for carrier” symptom - the driver fails to initialize the USB interface properly on boot.
Kernel downgrade is not an option at this point - we would lose more than we gain.
I need to research what changed in kernel 6.12.34 to 6.12.47 that triggered this regression(? is it regression, or user space? too early to tell.). The fact that it worked initially after the V4 upgrade but failed after plugin update and reboot suggests a timing or initialization sequence problem.
Let me dig into this and see what needs patching.
Kind Regards,
We released a new version with the fix for TIDAL. We’ll keep fixing stuff (wi-fi is next) and update you guys over here.
2 Likes
Thanks, So would I flash an sd card with v4, insert it in the rpi5. Boot from it and then do the install to disk? is that how it would work?
Hello,
I’m using a Raspberry Pi 5 and the fan is as shown in the picture. With the V3 version, it only turned on after a long period of use. With the V4, I can hear the fan running at very high speeds immediately after turning it on.
How to change it?
PS. Does peppy_screensaver_2.2.1.zip work on V4?
Good afternoon,
I’ve performed the update to 4.069 (stable) (coming from 4.066 RC; test channel) and all went well.
I’ve switched to “stable” in " Update Channel Selection" section
and clicked on the “FALSE” button below the “Plugins Test Mode” section in /dev page.
Version 4.069 was proposed with this configuration as well.
All of the system is working as expected. Really NICE, great job! Thanks a LOT!
(HW) Config:
Pi5, Raspi 2 Display (DSI), Two rotary encoders on several GPIOs
BT remote
Testing:
• Spotify plugin, works (my only use case).
• Touch display (and corresponding plugin) works
• “Now Playing” plugin works
• Bluetooth_remote plugin works
• Rotary encoders are both working
• WiFi is working (can access from laptop / phone).
• BT remote working
CORRD link still leads to web-page , no intergrations as far as I can see.
Nice rest of the day to all of you,
Regards, Ralf
@SO3D
A1: No, the fan is hardware controlled unless you add an overlay to adjust it. So V3 or V4 should not have an impact. High speed during start is rPi5 specific on Bookworm.
A2: peppy_screensaver_2.2.1 does not work on V4, you can use Peppy_meter basic from the plugin store
1 Like
Hi Wheaten,
after editing the config.txt and performing a reboot, error message and “undefined” mixer stays the same.
Following the output of sudo i2cdetect -y 1:
volumio@volumio:~$ sudo i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- 3b -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Seems something is wrong on your device.
The Hifiberry is not recognized.
Are you using some kind of extenders between your rPi and Hifiberry?
As I recall these issues with cheap crap from Amazon, where the pins where to thin.