Here’s the log right after 1st start (no plugins installed).
And the log after.
IR is working properly now.
Shall I try installing the other plugins now?
Touch Screen, Now Playing, Spotify, Bandcamp.
Hey @SimonE,
Thanks for sharing both logs - having a clean snapshot right after first boot and another after plugin installation made this much easier to trace.
IR Plugin and GPIO
There are no errors in the logs regarding LIRC, GPIO, or the IR plugin setup. Everything looks clean, and from your confirmation, IR is working properly now. That strongly suggests the earlier issue may have been due to:
- A partial or interrupted install (possibly a Wi-Fi hiccup mid-process).
- Or a stale GPIO state not reset cleanly between reboots.
Now that IR is functional on GPIO pin 25, you should be good to proceed with other plugins. If the issue resurfaces, capturing logs immediately after enabling the plugin would help us trace any misfires at the lircd or udev layer.
Wi-Fi Dropout or Web UI Unreachability
The second log doesn’t show failures from hostapd, dhcpcd, or dnsmasq, so there’s no obvious crash. But on some setups - particularly those using Broadcom Wi-Fi (e.g., onboard Pi 3/4) - we’ve seen rare cases where - The interface remains pingable, but browser access fails, especially when combined with USB DAC enumeration or IR device init.
Appreciate your methodical testing - it helps the whole team move forward with confidence.
Kind Regards,
That definitely happens sometimes, but always OK after a restart.
I’ll let you know if anything goes wrong with the other plugins. So far, working very well.
2 Likes
So far, everything important seems to be working very well for me - thank you very much for the great work!
The OTA update 0.63 to 0.65 worked without any problems.
I tested these and they work very well:
Both on RPI3 M. B 1.2 and 1.3
Allo BOSS
Allo DigiOne Signature (coax to E50 DAC)
USB on Musical Fidelity V90 44.1/16 to 192/24
Qobuz (on Volumio)
44.1/16 to 192/24 (Qobuz)
44.1/16 to 192/24 (Flac, NAS)
Radio
I’ve encountered these issues:
Qobuz Connect is missing
Tidal Connect is included twice as a source
Almost all of my favorite saved radio stations aren’t displaying their logos. (e.g., Radio Swiss Jazz)
After reconnecting the DAC to USB, the volume is at 100…!
Logs-
Allo BOSS
http://logs.volumio.org/volumio/nxADjtv.html
Allo DigiOne Signature
http://logs.volumio.org/volumio/rB3f9Gy.html
RPI3B USB on Musical Fidelity V90
http://logs.volumio.org/volumio/eTUgM4H.html
Dear @nerd,
thanks for your effort even on weekend!
The with first suggestion newly introduced “dsi0” gave me optimism, but it fails, as well…
I’ve followed your suggestion and disabled ALL other entries (despite those for touch display plugin) so userconfig.txt currently looks like:
# Add your custom config.txt options to this file, which will be preserved during updates
# Power-LED und Status LED vom Raspberry Pi abschalten
#dtparam=pwr_led_trigger=default-on
#dtparam=pwr_led_activelow=off
#dtparam=act_led_trigger=none
#dtparam=act_led_activelow=off
#dtparam=eth_led0=4
#dtparam=eth_led1=4
[all]
#display_auto_detect=1
#display 7Zoll
# raspi 4
#dtoverlay=vc4-kms-v3d-pi4,nohdmi
#dtoverlay=vc4-kms-dsi-ili9881-7inch
#Raspi 5:
dtoverlay=vc4-kms-dsi-ili9881-7inch,dsi0,rotate=90
#### Touch Display rotation setting below: do not alter ####
display_lcd_rotate=1
display_hdmi_rotate=1
but it doesn’t work either
I’ve tried both of your suggestions and in addition fiddled with an invented one - no luck…
Had tried:
dtoverlay=vc4-kms-dsi-ili9881-7inch,dsi0,rotation=90
dtoverlay=vc4-kms-dsi-ili9881-7inch,dsi1,rotation=90 <---- "invented" ...
dtoverlay=vc4-kms-dsi-ili9881-7inch,rotation=90
For me this doesn’t really matter - most important is that the system itself is dsiplayed corrctly - which is definitely true…
I would be more than happy to try something else if you like - but from my perspective you doesn’t have to dig deeper …
Thanks a lot!
Warmest regards,
Ralf
I have the Web UI unreachable problem again. This time when installing the Now Playing plugin. I can SSH in and start livelog, but the cat dmesg > dmesg.txt doesn’t seem to work. I made a screenshot of the livelog though.
log no web ui.txt (39.3 KB)
Update (OTA) to 0.065 has worked without any problem.
Pi5, Raspi 2 Display (DSI), BT remote & two rotary encoders on several GPIOs
Mainly using spotify, works.
Touch display works
Rotary encoders are working
BT remote is working
WiFi is working (can acces from laptop / phone).
Great work!
regards,
Ralf
Hey @SimonE,
You are right to call this one out. I have edited original instructions.
@patrickkfkan - can you kindly verify kew failure? Perhaps a private node module version require restart?
Kind Regards,
Higole 2 Pro
volumio v0.065
Onboard screen
boot images :
Screen displays needs a 90° rotation
Touch display needs a -90° rotation (it is 180°/display)
1st Conf wizard
network page empty!
Network
No wifi scan when hotspot enabled.
A manual wifi should be available in this case.
Eth cable mandatory…
Audio
Internal audio ok + HW mixer auto configured
BT
ok but no volume control from volumio
Appears as a computer
Sources
Radio ok
Qobuz ok
plugins
FusionDsp ok
Systeminformation ok
peppymeterbasic ok
Nas
not tested
Maybe irrelevant, but my time was not correct - 30 mins out. I just reset it using @Wheaten 's script.
Still can’t access the webUI, but maybe that caused the issue during plugin install.
For a complete log, in ssh, do
volumio logdump 'description'
example
volumio logdump test
Saving as: /var/tmp/logondemand
then copy paste the file here
Thanks, but too late now as I’ve just reflashed it. Will follow the same steps to see if it happens again and then post the log.
yeah wrote it for you 
, still using it myself.
1 Like
Clean install logs
Enabled ssh and test plugins, checked time - ok
Installed Touch Screen plugin - ok
Install Now Playing - ok
Log
IR-Remote, Bandcamp and Spotify also good.
All working properly now. Maybe the date/time issue, or a wifi hiccup during the plugin install,
Current log
Hey @SimonE,
Appreciate the follow-up and the re-test confirmation - sounds like the fresh boot with valid time and Wi-Fi resolved everything cleanly.
You’ve actually touched on an important issue we’ve been tracking:
Time skew during early boot can cause:
- Secure connections (HTTPS, MyVolumio auth) to silently fail
- Plugin installation scripts to misbehave
- General instability with services that depend on valid system time
This can especially hit devices using Wi-Fi only, where NTP sync races against network readiness.
I am now considering adding a defensive mechanism into early boot:
Something like a setdatetime.service, similar to what @Wheaten prototyped, which uses a delayed curl request to fetch current date from a known HTTP response header - as a fallback if NTP hasn’t succeeded by a certain boot stage.
If you’d like to try the current workaround:
# /lib/systemd/system/setdatetime.service
[Unit]
Description=Set local time using time server
[Service]
Type=oneshot
ExecStart=/bin/bash -c "sleep 30; date -s \"$(curl -s --head http://google.com | grep ^Date: | cut -d' ' -f2-7)\""
[Install]
WantedBy=multi-user.target
Then:
sudo systemctl enable setdatetime.service
It’s not elegant, but it does work in scenarios where NTP hasn’t initialized fast enough (will need to think this through).
Thanks again for pointing this out in context I’ll consider including this (or a cleaned-up version) in upcoming releases to improve early boot consistency.
Kind Regards,
Hello I have tested 0.63 and still no sign of the hotspot. Log file http://logs.volumio.org/volumio/er0lvW0.html
Hey @JohnR,
Thanks for the follow-up and the log.
You’ve correctly uncovered a problem - the hotspot fails to start because the RT5370 USB WiFi dongle remains soft-blocked by rfkill during boot. Although our early boot unblock service is active, it appears to run too early or is not effective for this specific chipset (rt2800usb).
This is a known quirk with some Ralink-based adapters, and we’ll address it in an upcoming build by refining the rfkill handling logic.
Thanks again for your persistence - your tests help uncover these edge cases that we can’t reproduce in-house easily.
Kind Regards,
Allo Kali with Piano 2.1 still working good in dual mono mode with v0.65 on a PI3
Hello I have just tried 0.65, still no hotspot. I set up with ethernet all seemed OK , discovered that wireless network was off in on network page:; did a restart; no output. Log file
http://logs.volumio.org/volumio/JHSrqwT.html