In the past when I have done a FLIRC USB IR solution, I simply programmed the remote using either the media keyboard or the full keyboard, which I used this time. So I programmed the buttons using the little FLIRC interface and then simply plugged the USB into the Pi or Rivo rebooted and it works. Right now in Md for instance I have my Peachtree Audio remote somehow controlling the Rivo using this configuration, Unfortunately I cannot try that one now because I am in Florida with a Pi4. So for questions 1 & 2 i only used FLIRC no trigger happy anything as I donât even know how to do that. I only downloaded the GPIO plugin as something that might help but as you explained it wonât.
Good afternoon!
Volumio 4 is installed on the sd card. At the same time, USB boot priority is set in the EEPROM on the RPI 4B 2g. OSMC is installed on the USB flash drive. If an SD card with Volumio and a USB flash drive with OSMC are installed in the RPI, then OSMC is loaded. If the USB flash drive is not installed, then Volumio is loaded. When restarting RPI from the Volumio menu and with the USB flash drive from OSMC installed, Volumio boots again, although the USB flash drive from OSMC should be loaded.
What could be the problem?
After being away from this for a bit, I came to see Volumio 4 was released.
i did fresh install on all 5 of my clients, a mix of Pi4 and Pi 5.
Every single one installed and configured perfectly, down to the Plugins.
EXCEPT for WiFi. I cannot get a single device to connect to WiFi. I have tried every combination of configuring though wired first, configuring âstand aloneâ using a keyboard, disabling Hot Spot, Different SSID, making an SSID 2.4 only, etc.
Itâs not the router or my settings. I have a large number of devices, some old some new, connecting just fine. When the clients were running Volumio 3 they connected fine.
Is this a known issue or is there a setting somewhere buried that needs to be set?
Please read this, then do a forum search for volumio 4 and wifi (a very handy feature) as the issue has been discussed many times.
If it does not solve your issue, do not hesitate to post again for help with the information requested.
I read through that miles long multi topic thread as best I could, which is why I tried all the different combinations listed above.
I managed to get a completely fresh install to connect to WiFi just now by doing initial connection via my phone and connecting to the hotspot. If thatâs the only way setting up WiFi will work there should be something on the initial splash screen and documentation clearing stating it.
UPDATE
Going back on a fully functioning wired client and turning on Hotspot in the hopes of setting up WiFi via the phone process completely nuked that client - wonât even boot. (Verified this twice, on a second new install). Which means I get to spend my afternoon disassembling all my clients to get to the SDCards, re-flashing and setting them up from scratch.
Correction to Above
Apparently the Pi 5 behaves differently and HotSpot is not enabled at first boot, so itâs impossible to configure it via the phone app. Basically Pi 5 cannot be used wireless. This means Iâll have to redo my original layout to make sure the Pi 5âs are placed where they can be wired.
Thank you but been down that rodeo before. If itâs not a known/simple fix, Iâll must musical chair the devices to where they work and move on. Not ideal but better than endless hours of frustration and waiting for an answer.
Step 1: Open the latest app and configure your device.
Yes, it should work over WiâFi.
Yes, it works on all my systems.
Yes, your device should cooperate. (Should⌠)
Step 2: Or go oldâschool: plug in a network cable, set everything up, WiâFi included, then reboot, yank the cable out, and watch Volumio gracefully switch to WiâFi like a wellâtrained digital acrobat.
If none of this works for you, weâll need logs.
If youâre not willing to provide logs, or if you feel the community should deliver premium concierge tech support in under 60 secondsâŚ
well⌠you may enjoy reading this delightful reality check:
Thank you and i truly do appreciate the community support. but the issue with connectivity are a basic function that Volumio should be responsible for (and should have QAâd) before release.
Step 1 only worked on Pi 4 devices (4 of them). The 2 Pi 5 devices, nada. And none of hardware was purchased âtogetherâ so the chances of HW failures across multiple devices at the same time, is well, astronomically small.
Step 2 I did try (my original approach) but no matter what combinations I tried the WiFi wouldnât âstickâ - canât think of a better word. The SSID, password, etc. were all correct and it looked like it was accepted.
And working in IT and as customer facing PM, I do not expect concierge support (been on the other side of that expectation). The solution i found (using Pi 5 connected and Pi 4 wireless) isnât ideal but it works and Iâm done with it.
Again, not something I expect the community to address if thereâs not a simple explanation - Volumio should step up and handle this as the product OEM.
The statement âPi 5 cannot be used wirelessâ is not accurate. Pi 5 WiFi functions correctly in current Volumio 4 releases. The WiFi subsystem received significant fixes in version 4.082 and later, including a complete rewrite of wireless.js addressing connection stability and hotspot reliability. Pi 5 systems running 4.084 or newer are operating on WiFi without issue.
Version matters
You have not stated which Volumio 4 version you installed. Early 4.0xx releases (particularly 4.067-4.073) had known WiFi problems that were subsequently addressed. If you flashed an older image, the problems you describe align with issues that have since been resolved.
Hotspot behavior
Hotspot not appearing on first boot when ethernet is connected is expected behavior - this is by design. The hotspot activates when no network connection exists. This applies to both Pi 4 and Pi 5.
Boot failure claim
The assertion that enabling hotspot âcompletely nukedâ a working wired client twice is a serious claim. Without logs or any diagnostic information, this cannot be investigated. Boot failures from toggling a network setting would indicate either a pre-existing filesystem problem, storage failure, or a reproducible bug - but determining which requires evidence.
Requirements
If you decide you want this investigated rather than working around it:
Exact Volumio version number from Settings > System > System Version
Upload log /tmp/wireless.log (requires internet connectivity via ethernet)
Pi board identification per the guide referenced earlier
SD card brand and model for all affected devices
Without this information, no investigation is possible. The community volunteers and Volumio developers need data to identify problems - this is not optional.
Your workaround is functional. If that suffices, understood. If WiFi on Pi 5 matters to you, update to 4.084 or later and test again before concluding it does not work.
BEFORE YOU POST ABOUT WIFI PROBLEMS
READ THIS FIRST
This thread has over ONE HUNDRED posts discussing WiFi connectivity issues
on Volumio 4. Before adding another âWiFi not workingâ report, understand
the current situation:
VERSION HISTORY
4.073 (First Official Release)
Shipped with wireless.js marginally updated from Volumio 3
Known problems: CPU runaway (61-99% on Pi 3, 22-77% on Pi 4), connection
failures, hotspot/client switching issues, network stack starvation
Good progress. The FLIRC hardware is working correctly - your thd --dump output confirms key events are being received.
The empty audio.conf is the problem, but this is unusual. On a standard Volumio 4 installation, that file should contain default key mappings. Need to determine why yours is empty.
Please provide these additional diagnostics:
ls -la /etc/triggerhappy/triggers.d/
systemctl status triggerhappy.service
systemctl status triggerhappy.socket
stat /etc/triggerhappy/triggers.d/audio.conf
This will show whether the file is zero-length or corrupted, what permissions are set, whether other configuration files exist that might interfere, and whether the service loaded correctly.
Once we have this information, we can determine if this is a restoration issue or something else caused the file to be emptied.
This behavior - cold boot respecting USB priority but warm reboot falling back to SD card - is a documented pattern related to USB device enumeration timing during software-initiated reboots.
During cold boot (power cycle), USB devices power up and enumerate alongside the bootloader initialization. During warm reboot, USB devices may not reset and re-enumerate quickly enough for the bootloader to detect them before it moves to the next boot mode (SD card).
To diagnose this properly, I need the following information:
Exact Volumio version number (from Settings - System)
EEPROM bootloader version and configuration. Connect via SSH and run:
If possible, connect a monitor during warm reboot to observe bootloader diagnostic output - this will show whether USB is being detected at all during the reboot sequence.
Potential causes include:
USB flash drive requiring longer initialization time than bootloader timeout allows
EEPROM timing parameters need adjustment (USB_MSD_PWR_OFF_TIME, USB_MSD_STARTUP_DELAY, USB_MSD_DISCOVER_TIMEOUT)
Bootloader firmware version requiring update
Known maskrom behavior where certain SD card partition layouts affect boot priority
Please provide the requested information so I can give specific guidance.
Version 4.082 introduced WiFi subsystem improvements, and version 4.084 includes a complete rewrite of wireless.js specifically addressing the connection stability and hotspot reliability issues you encountered. These fixes are the direct result of feedback from testers running earlier 4.0xx releases
Connect one of your Pi devices via ethernet and perform an OTA update:
Under âUpdate Channel Selectionâ, select âTestâ from the dropdown
Go to Settings > System > System Updates > Check Updates
Apply available update
This will bring the system to current version with the WiFi fixes applied. After the update completes and the system reboots, configure WiFi through the UI while still on ethernet, then disconnect ethernet and reboot to verify WiFi connectivity persists.
Repeat for remaining devices.
Regarding the Boot Failure
The issue where enabling hotspot on a wired client rendered it unbootable is separate from the general WiFi connectivity problems. If this occurs again after updating to current version, a log would be necessary to determine root cause. On a device that will not boot, the SD card can be mounted on another system to retrieve logs for analysis.
)