Please be not confused about that the remote control power on/off signals seems to work already. This function is only partially dependent on these scripts. The power command is interpreted by the RP2040 inside the case directly. The underlying OS doesn’t know about that event and doesn’t shut down graceful, if the scripts to observe the input signals not working right.
To get the remote control to work like a regular one, the system must support this - for example with LIRCD. You can grab a conf file from here. libreelec_package_argonforty-device/source/resources/data/argon.lircd.conf at master · Argon40Tech/libreelec_package_argonforty-device · GitHub
But the second requirement would be, that the used desktop manager of Pi OS interprets the incoming events right. I don’t know if that works out of the box as soon you have LIRCD configured right.
EDIT:
Instead of LIRC you can alternativly use ir-keytable. This seems the modern way with kernel drivers. But it seems seldom used in tutorials. I found this one: gordonturner.com
You can find a toml file for the Argon40 remote here:
libreelec_package_argonforty-device/source/resources/data at libreelec12 · HungerHa/libreelec_package_argonforty-device · GitHub
For the config.txt this is the line for the IR receiver of the Argon ONE case.
dtoverlay=gpio-ir,gpio_pin=23
I think it could work if you:
- ensure, that the correct dtoverlay line is active in config.txt
dtoverlay=gpio-ir,gpio_pin=23 - install ir-keytable
sudo apt install ir-keytable - copy argon40.toml to /etc/rc_keymaps
- add this line to /etc/rc_maps.cfg
* * /etc/rc_keymaps/argon40.toml - reboot