Triggerhappy doubling commands after moving to Volumio 4

Help and Support
1

Hello,

I have got annoying problem with triggerhappy - it doubling at least three my commands: MUTE TOGGLE, VOLUME UP, VOLUME DOWN

Mute button pressed only once - it mutes system but after then I am not able to unmute - one button press triggers doubled action - I can see very quick change: to unmute and mute again.

The same for volume -/+ - once pressed volume - or + key changing volume level by two units (- or +).

Problem can be temporary fixed by restarting Triggerhappy service. I use ‘/etc/init.d/triggerhappy restart’ command. It persists fixed until next system boot.

The same I observe on two my RPI5s and as well on Intel Nuc.

The outputs from command: ./thd --dump /dev/input/event* look the same: prior to Triggerhappy service restart and after that.

Part of my audio.conf:

#MUTE TOGGLE
KEY_MUTE 1 /usr/local/bin/volumio volume toggle
#VOLUME UP
KEY_VOLUMEUP 1 /usr/local/bin/volumio volume plus
#VOLUME DOWN
KEY_VOLUMEDOWN 1 /usr/local/bin/volumio volume minus

I am using Rii mini i25 wireless remote

Thank you.

Regards,
Bartosz

2

Hey @Bigu1975,

Before investigation can proceed, one clarification is needed from your post.

You wrote that thd --dump output “looks the same” before and after service restart. Does this mean:

A) Single event per key press in dump, but Volumio executes the action twice
B) Doubled events visible in dump output per single key press

This distinction determines whether the issue is software-side or remote-side.

If you have not already done so, perform a full reset of the Rii mini i25 remote and receiver, then re-pair. If the remote has learned IR codes, re-learn them from a stable source signal. Unstable capture during IR learning can produce repeated codes.

Please also provide:

  1. Exact Volumio version (not “latest” - the actual number from Settings > System)

  2. Log link from http://volumio.local/dev

  3. Full content of your audio.conf:

cat /etc/triggerhappy/triggers.d/audio.conf

The partial config in your post shows commented lines. Need to see the complete file to check for duplicate entries.

  1. Confirm all three systems (2x RPi5, Intel NUC) exhibit identical behavior with the same remote, or if you have tested with different remotes.

Kind Regards,

3

Hey @nerd
Many thanks for your interest and for willing to help, highly appreciated.

In both cases - with the problem and without problem - thd dump looks exactly the same: there is single event logged (1 followed by 0). With problem it triggers doubled action, without problem it doesn’t but the event looks the same.

Two times mute pressed with doubled action:

volumio@volumiostreamer:/usr/sbin$ sudo ./thd --dump /dev/input/event*
[sudo] password for volumio:
EV_KEY KEY_MUTE 1 /dev/input/event7

KEY_MUTE 1 command

EV_KEY KEY_MUTE 0 /dev/input/event7

KEY_MUTE 0 command

EV_KEY KEY_MUTE 1 /dev/input/event7

KEY_MUTE 1 command

EV_KEY KEY_MUTE 0 /dev/input/event7

KEY_MUTE 0 command

Two times mute pressed without doubled action:
volumio@volumiostreamer:/usr/sbin$ sudo ./thd --dump /dev/input/event*
[sudo] password for volumio:
EEV_KEY KEY_MUTE 1 /dev/input/event7

KEY_MUTE 1 command

EV_KEY KEY_MUTE 0 /dev/input/event7

KEY_MUTE 0 command

EV_KEY KEY_MUTE 1 /dev/input/event7

KEY_MUTE 1 command

EV_KEY KEY_MUTE 0 /dev/input/event7

KEY_MUTE 0 command

As I restarted Rii Mini (I am using only wireless command, not IR) and as always after restarting triggerhappy process manually - it works fine, my best guess is that it not remote controller side problem.

My exact system version (it is in Polish but I think it is enough):

image

Links to both logs - first with the problem (captured just after system boot and with mute button pressed there times: first press muted system, second made doubled action - unmuted and immediately muted, third time exactly as second time:

http://logs.volumio.org/volumio/KQcNDdz.html

Link to the log after other reboot when the triggerhappy process has been restarted after boot (the same three times mute pressed - this time without doubled action. I had just sequence: mute - unmute - mute.
http://logs.volumio.org/volumio/nOAQRxG.html

volumio@volumiostreamer:~$ cat /etc/triggerhappy/triggers.d/audio.conf
#VOLUMIO TRIGGERHAPPY CONFIGURATION FILE
#MUTE TOGGLE
KEY_MUTE 1 /usr/local/bin/volumio volume toggle
#VOLUME UP
KEY_VOLUMEUP 1 /usr/local/bin/volumio volume plus
#VOLUME DOWN
KEY_VOLUMEDOWN 1 /usr/local/bin/volumio volume minus
#PLAY PAUSE TOGGLE
KEY_PLAYPAUSE 1 /usr/local/bin/volumio toggle
#NEXT
KEY_NEXTSONG 1 /usr/local/bin/volumio next
#seek plus
KEY_RIGHT 1 /usr/local/bin/volumio seek plus
#PREVIOUS
KEY_PREVIOUSSONG 1 /usr/local/bin/volumio previous
#seek minus
KEY_LEFT 1 /usr/local/bin/volumio seek minus
#power_off
KEY_SLEEP 1 /etc/trigger.sh
#repeat
KEY_BACK 1 /usr/local/bin/volumio repeat
#enter
KEY_ENTER 1 /usr/local/bin/volumio toggle
#peppy_screensaver
KEY_COMPOSE 1 /data/INTERNAL/peppy.sh
volumio@volumiostreamer:~$

Yes I confirm - the same I have noticed on two remaining rpi5 volumio installation as well. If I am not mistaken on RPI I have one system version back. The problem I have noticed after migration to volumio 4.
Btw the doubled action is most likely not only limited to volume and mute controlling. I have noticed that for instant for KEY_NEXTSONG action. As the mute test is the easiest to reproduce I described it together with volume.

Since reporting this issue on Sunday, I am using work around which fix this behavior - via systemd I am calling the script which does systemctl restart triggerhappy.service after system boot.

Hope it helps.

Thank you!!!

4

And one more thing. I think, at least for NUC my volumio version, there is another process which reacts on my wireless remote controller. And maybe it is the issue?

It comes from fact that this event:
#power_off
KEY_SLEEP 1 /etc/trigger.sh
should trigger the scripts which should turn the NUC off, but put it into sleep (the power led is blinking).
And this key on my remote (sleep) works (causing system going to sleep) even when triggerhappy process is stopped. Unfortunately when triggerhappy is stopped there is no reaction neither on mute nor volume buttons pressed :frowning: