Volumio 3 Buster Beta for RPi

Maybe GPIO19 is already used by your DAC? My HifiBerry DAC+ uses GPIO18…21 for it’s own signaling. I had this problem recently when selecting “spare” GPIO for a rotary encoder volume control.

I did see a message about the GPIO being used in a HifiBerry forum last night. I will try another GPIO pin.

Thanks Andrew…

I should of re-read the iq-audio docs… I have had this board for a few years, I thought I used GPIO18 before, but the documentation says it is used for i2s…so I was stamping all over the codec! When I was connecting it again… something in the back of my mind was telling me it should be connected further down the board.

On another topic the socket-io api is working fine in V3.


I’ve been trying out beta3 and the most noticeable problems are volume control slider does nothing (volume doesn’t change at all), my USB thumb drive is seen by OS but is never seen/added to my library.
running on rpi3b+ using iqaudio DAC pro. the USB stick is 64g Memorex cheapo.

Hallo… reporting the problem
I am using v3.074… with raspberry 3 model B+
using hifi AIODE Digi Pro Digital out
in i2s selector, i used to choose HifiBerry Digi+ Pro…
now in v3, everytime i choose HifiBerry Digi+ Pro, it reporting error when playing the song and the song did not play at all…
so i choose HifiBerry Digi, now it play… but all the song play in slower… it is very noticeable cause i already try some of my song collection and all of them play slower…


confirm after i using volumio v2.882, everything back to normal… i can select HifiBerry Digi+ Pro and using Hifi AIODE Digi Pro Digital out… the speed of playback also back to normal…

OffTopic: Bullseye release date is in +/- one month :wink:

HI, Downloaded the latest version of the beta.
I cannot do apt-get update or install packages from repositories, like unzip.
Any idea? I also uncommented the line in
sudo nano /etc/ssh/sshd_config

this is what I get:
volumio@volumio:~$ sudo apt-get update
Err:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Could not connect to raspbian.raspberrypi.org:80 ( - connect (111: Connection refused)
Err:2 http://archive.raspberrypi.org/debian buster InRelease
Could not connect to archive.raspberrypi.org:80 ( - connect (111: Connection refused)
Err:3 https://deb.nodesource.com/node_14.x buster InRelease
Could not connect to deb.nodesource.com:443 ( - connect (111: Connection refused)
Reading package lists… Done
W: Failed to fetch http://raspbian.raspberrypi.org/raspbian/dists/buster/InRelease Could not connect to raspbian.raspberrypi.org:80 ( - connect (111: Connection refused)
W: Failed to fetch https://deb.nodesource.com/node_14.x/dists/buster/InRelease Could not connect to deb.nodesource.com:443 ( - connect (111: Connection refused)
W: Failed to fetch http://archive.raspberrypi.org/debian/dists/buster/InRelease Could not connect to archive.raspberrypi.org:80 ( - connect (111: Connection refused)
W: Some index files failed to download. They have been ignored, or old ones used instead.

and, if ping

volumio@volumio:~/touch_display_1_2_1Busterbeta$ ping -c 1
PING ( 56(84) bytes of data.
From icmp_seq=1 Destination Host Unreachable

— ping statistics —
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

pi is connected via lan port and the webinterface works perfeclty.

Any suggestion?

What line did you uncomment?

It looks like you might have some connectivity issues, could your Pi be gated to LAN, with no WAN access?

In this release the crontab is still present but after the boot it lost the configuration, why ?

Hi volumio team,
thank you for this great peace of software and the work you invest!
Today I discovered a new Version 3.078 … but since several revisions the “Fixes” textbox tells me the same:

Do not scan internal drives
Multiroom Handling Backend and User interface
Temporarily removed multiroom
TIDAL Connect with alsa

Could you please give some information what was really changed between the revisions? Providing a link to the changelog in git or something similar would also be highly appreciated. (Even if I am the only one who does not find the changes in git :frowning: )
Thank you & best regards,


Looks like there are not many bugs left to fix. How far is the development? Would you call the current version close to stable? And are plug ins introduced to this version yet? Thanks in advance!


Updated version to 3.078 …

I had installed version 3.074. I noticed a new version is shown is this thread, but it is not detected through the Check Updates feature of the application. Is it possible to install the new version without reverting to the default configuration?

You have to go to http://your-device/dev and enable “Test Mode” to receive onair updates in this version.

I would like to have the following improvement in the Buster version: when using the web UI, the spacebar should toggle between play/pause. Currently, it doesn’t work like this, and the rest of the other applications (i.e. Spotify Web) do it.
Thank you in advance and best regards.

Hi Manuel_Couceiro,

You can achieve that by installing triggerhappy (in v2 it is preinstalled) and configure that in the “audio.conf” file.


Don’t think triggerhappy will work while controlling the device from another device via the webUI - that needs to be implemented in the front end UI logic.

This method works, but it is not plain to me why the design would require enabling updates, through an explicit process even when such updates are initialized manually.

Is this restrictions documented? I have no memory of reading about it.

Well, anyway, I have the update installed, but still have the problem of non-working functionality for appending to the queue.

You have to activate dev mode in order to test untested, unstable version…