Volumio 4 Feedback Thread

Wheaten · January 16, 2026, 8:43pm

LooserDS · January 17, 2026, 7:49am

@Wheaten - for me, I have read all the topics on wifi - but what is the solution when I am not able to update the device? I have no ethernet board in my Zero 2 W - and wifi is not working.

matthewk · January 17, 2026, 12:57pm

Hi there, my device offers me v4.087, but I could not really find any information about this release in any of the thread in this forum. Could you kindly point me to the thread where I can follow the discussion? Thanks.

LooserDS · January 17, 2026, 3:58pm

Ok - Feedback from my side: I took my Pi Zero 2 W with a fresh Volumio 4.073 and added a w5500 wired network inferface (only change - dtoverlay=w5500 in userconfig.txt). I found and configured the device and changed to the test channel. New firmware appeard (4.087) and I installed it. Since then the device is not reachable - not via ethernet and not via wifi.

I made this procedure 2 times - every time the same problem.

Any ideas (not able to give you logs - not reachable - also cannot ping the device)

SimonE · January 17, 2026, 4:16pm

This is the thread for Volumio 4.xx, so you’re in the right place.

HeadGeek · January 17, 2026, 6:56pm

Posting here as my original post asking for help was unanswered as it was probably in the wrong area.

Problem is that I get no audio from the output of my DAC after I update to the latest version of Volumio even though the on-board headphone output and shairport work.

This has happened a few times on both of my streamers (rPi 3B+ and rPi 4B with Innomaker and IQAudio DAC respectively) since about v4.07x. Both have been updated to 4.088 and with the rPi 4B unit the sound came back after I disabled the DAC and enabled it again. Just updated the rPi 3B+ unit now to 4.088 but that procedure isn’t working so I have no audio even though the web interface says it is playing.

Logs for the 3b+ unit where I got it working after removing and then adding back the DAC is uploaded here.
Logs for the 4b unit where I can’t get it working after removing and then adding back the DAC is uploaded here
Screenshots and log link describing the issue are in the original post.

I have been working the various beta versions from the start and thought that now we were out of beta we were OK but this is the first time I have encountered this issue. Sorry if this sounds muddled - please let me know if you need additional information.

Regards,

domcars0 · January 17, 2026, 7:42pm

Hi,
Are you able to ping it? If not may be can you connect a display on the HDMI port and a keyboard on the USB to see what’s wrong?

ClaesM · January 17, 2026, 8:23pm

Hello! @nerd @Wheaten @balbuze or just any Volumionat here.

Some questions. I think I will order this Waveshare 10.1inch IPS display and connect it to a rPi5 running Volumio Bookworm but before buying I just want to know if anyone of you have some experience with this display regarding compability issues, setup etc.
I’m sorry if I put this Q in wrong place for this question.

Waveshare 10.1inch

Kind Saturday Evening Regards / C

LooserDS · January 18, 2026, 7:42am

Ping is not working - worked with 4.073. Good idea - will try it. Thanks

LooserDS · January 18, 2026, 9:27am

Ok - after the 7 flash and update the ethernet is working. But I am still unable to activate Wifi in the settings. I set to on - Save - it wents to off.

The log is here: http://logs.volumio.org/volumio/NrbbwbB.html

nerd · January 18, 2026, 10:38am

Hey @LooserDS,

Currently I have more questions than clarity about your situation.

Hardware identification:

What exact board is this? You say Pi Zero 2 W, but can you confirm? If you have access to the SD card from another system, what does /proc/cpuinfo show, or the revision code?
From logs - eth0 is built-in Raspberry Pi ethernet (MAC dc:a6:32:fc:a6:42 = RPi Foundation) not W5500
What exact W5500 module are you using? (WIZ850io, WIZ850S2, bare breakout board, HAT?)
How is it wired? Which GPIO for interrupt? Which chip select?

Configuration:

What is the complete content of /boot/userconfig.txt? Not just “dtoverlay=w5500” - the entire file.
Did you include dtparam=spi=on before the overlay line?

Kind Regards,

nerd · January 18, 2026, 3:01pm

Hey @HeadGeek,

Thank you for the logs. I have analyzed all three files, but there is some confusion about which log corresponds to which unit.

Log file contents versus your description:

You stated:

“Logs for the 3b+ unit where I got it working”
“Logs for the 4b unit where I can’t get it working”

However, the logs show:

File	MAC Address	Pi Model	Volumio	DAC	Status
JtuMNCE	e4:5f:01:9a:2b:16	Pi 4B Rev 1.5	4.085	IQaudIODAC	WORKING
jpax5l5	e4:5f:01:9a:2b:16	Pi 4B Rev 1.5	4.088	IQaudIODAC	NOT WORKING
JG85KvN	b8:27:eb:1f:af:77	Pi 3B+	4.088	BossDAC	WORKING

JtuMNCE and jpax5l5 are from the same RPi 4B unit (identical MAC address). JG85KvN is the RPi 3B+ with Innomaker/BossDAC.

Problem on the RPi 4B:

The DAC is not selected in Volumio.

From the working state (JtuMNCE - version 4.085):

dtoverlay=iqaudio-dacplus,unmute_amp

pcm.volumioHw {
    type hw
    card "IQaudIODAC"
}

From the non-working state (jpax5l5 - version 4.088):

(no dtoverlay line - DAC not selected)

pcm.volumioHw {
    type hw
    card "Headphones"
}

The dtoverlay for the IQaudio DAC is completely absent, and asound.conf points to “Headphones” instead of “IQaudIODAC”.

Why the DAC still appears in aplay -l:

The IQaudIO DAC Plus has an onboard EEPROM that causes the Raspberry Pi firmware to load the overlay automatically, independent of Volumio configuration. The kernel log confirms GPIO22 unmute occurs during boot. However, Volumio does not route audio to the DAC because it is not selected in playback options.

Try:

Go to Settings - Playback Options - Output Device and select “IQaudIO DAC Plus” from the I2S DAC dropdown. Save and reboot.

After reboot, verify by generating a new log that:

dtoverlay=iqaudio-dacplus appears in config.txt
asound.conf shows card “IQaudIODAC”

Note on the RPi 3B+ (BossDAC):

This unit shows correct configuration - dtoverlay=allo-boss-dac-pcm512x-audio is present and asound.conf points to card “BossDAC”. This explains why the disable/re-enable procedure worked on this unit but not the other.

Kind Regards,

LooserDS · January 18, 2026, 6:47pm

Yes - it is a Pi Zero 2 W - here cpuinfo:

volumio@volumio4-wz:~$ cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 64.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 1
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 64.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 2
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 64.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

processor : 3
model name : ARMv7 Processor rev 4 (v7l)
BogoMIPS : 64.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd03
CPU revision : 4

Hardware : BCM2835
Revision : 902120
Serial : 00000000beaa41e9
Model : Raspberry Pi Zero 2 W Rev 1.0

Here is the usericonfig.txt:
# Add your custom config.txt options to this file, which will be preserved during updates
[all]
dtoverlay=w5500

I have only changed this file - all other are from the image.

As said - now I have access via Ethernet - but i am unable to activate Wifí.

The Zero is on a board with DAC and Ethernet connector - it is a Raspberry PI Media Center (Raspberry PI Media Center – Sonocotta) without amp. The chip is a Wiznet W5500 (hard to read on the chip itself).

nerd · January 18, 2026, 7:19pm

Hey @LooserDS,

Thank you for the details. Sonocotta Media Center board with integrated W5500 - can not locate schematics, but should be a generic SPI.

Volumio uses Single Network Mode - only one interface active at a time. If W5500 reports link up, WiFi will not associate. We need to investigate whether W5500 carrier detection is working correctly.

Please run these diagnostic steps:

Enable wireless debug:

sudo sed -i 's/DEBUG_WIRELESS=false/DEBUG_WIRELESS=true/' /volumio/.env

Reboot:

sudo reboot

After reboot, try to configure WiFi via the UI; do not reboot until all steps are completed.
Unplug ethernet cable from W5500 port
Check if WiFi connects - wait 30 seconds, then check if associates or creates HotSpot, in which case try to configure again.
Check if WiFi connects - wait 30 seconds
Plug ethernet cable back in
Generate logs via http://volumio-ip/dev and provide the link
Zip and share the wireless debug log (do NOT reboot before this):

cd /tmp
zip wireless_debug.zip wireless.log

Then download the file via SFTP or SCP to your computer and attach it to your forum reply.

This will show us what wireless.service sees when ethernet state changes and whether W5500 carrier detection works properly.

Kind Regards,

LooserDS · January 18, 2026, 8:29pm

This is my problem - I am not able to activate WiFi in the gui. When enable WiFi the network restarts, after that the gui refreshes and it is disabled again. Not possible to go any further.

nerd · January 18, 2026, 8:40pm

Hey @LooserDS,

That is useful information - WiFi cannot even be enabled while ethernet is active. The GUI disables it again after network restart. This is Single Network Mode behavior, but the debug log will show exactly why.

We still need the logs to understand what wireless.service decides and why. Even if WiFi does not enable, the debug log will capture the attempt and the reason for rejection.

Please proceed with:

Enable wireless debug:

sudo sed -i 's/DEBUG_WIRELESS=false/DEBUG_WIRELESS=true/' /volumio/.env

Reboot:

sudo reboot

Try to enable WiFi in the GUI (it will fail - that is expected)
Unplug ethernet cable
Wait 30 seconds, try WiFi again in GUI
Plug ethernet cable back in
Without rebooting - collect both logs:

cd /tmp
zip wireless_debug.zip wireless.log

Generate log link via http://volumio-ip/dev

Attach the zip file and provide the log link. The timestamps must be from the same session so we can correlate events between both logs.

Kind Regards,

LooserDS · January 18, 2026, 9:00pm

Ok - one question to step 5 - how can I access the gui when Ethernet cable is disconnected?

backenst · January 18, 2026, 9:43pm

Feedback on Volumio 4 and FLIRC USB plugin for IR remotes

Running a Pi4 b (v4.073) into the Preciso via USB and into Peachtree amp.

In the past I have configured the FLIRC USB plugin with IR remotes to control the Pi4 and 5bs but with software versions 3.x with no problems. Currently I am trying to set up a FLIRC USB into the Pi4b, this time running 4.073 but nothing is happening. I have tested the remote into notepad to confirm its sending signals and it is, but nothing happens when plugged into Pi4b.

Not sure if logs will help but here goes:http://logs.volumio.org/volumio/tk1MWg9.html

nerd · January 18, 2026, 10:08pm

Hey @LooserDS,

Good question. When ethernet is disconnected, check with your smartphone for a WiFi network called “Volumio-xxxxx” (the hotspot). Connect to it the same way you would during initial device setup.

If the hotspot appears:

WiFi hardware is working
Connect to it and access the GUI at http://192.168.211.1
Try to configure your home WiFi network from there

If the hotspot does NOT appear:

That is also useful diagnostic information
Simply plug the ethernet cable back in and collect the logs

Either way, after testing:

Plug ethernet cable back in
Zip the debug log:

cd /tmp
zip wireless_debug.zip wireless.log

Generate log link via http://volumio-ip/dev
Attach the zip and provide the log link

Kind Regards,

nerd · January 18, 2026, 10:24pm

Hey @backenst,

Key findings from log:

FLIRC USB is properly detected and enumerated:
- Device: Bus 001 Device 004: ID 20a0:0006 Clay Logic flirc
- Driver: usbhid (correct)
- Three HID keyboard interfaces active
Triggerhappy daemon (thd) is running:
- PID 686, watching /dev/input/event*
Installed plugins show no FLIRC or IR-related plugin:
- GPIO Buttons
- System information
- Now Playing
- Touch Display

Clarification needed:

There is no “FLIRC USB plugin” in the Volumio 4 plugin ecosystem. FLIRC works differently from GPIO IR receivers - it emulates a USB keyboard and requires triggerhappy configuration to map key presses to Volumio commands.

Questions:

How exactly did you install and configure FLIRC on Volumio 3.x and Volumio 3.x? Did you:
- Create a triggerhappy configuration file manually?
- Install a community plugin or script?
- Use some other method?
What FLIRC profile did you program your remote with using the FLIRC desktop application? (Kodi, Full Keyboard, custom keys?)
Can you SSH into the Pi and run this command to verify if the FLIRC is sending key events:
```
sudo thd --dump /dev/input/event*
```
Then press a button on your remote - does any output appear?
Can you check if any triggerhappy configuration exists:
```
cat /etc/triggerhappy/triggers.d/audio.conf
```

This information is essential to determine what the issue is.

Kind Regards,