Something got messed up with my justboom IR remote with a recent update. I previously had a justboom IR remote and an IR receiver working on GPIO pin 5 that now no longer works with recent update.
Trying to piece together what i need to fix. here is what I’ve done:
# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS=""
#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false
#Don't start irexec, even if a good config file seems to exist.
#START_IREXEC=false
#Try to load appropriate kernel modules
LOAD_MODULES=true
# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="UNCONFIGURED"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE=""
MODULES="gpio_ir_recv"
# Default configuration files for your hardware if any
LIRCD_CONF=""
LIRCMD_CONF=""
added gpio-ir to /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
i2c-dev
lirc_dev lirc_rpi gpio-ir gpio_in_pin=5
edit /etc/lirc/hardware.conf
# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS=""
#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false
#Don't start irexec, even if a good config file seems to exist.
START_IREXEC=true
#Try to load appropriate kernel modules
LOAD_MODULES=true
# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="default"
# usually /dev/lirc0 is the correct setting for systems using udev
DEVICE=""
MODULES="lirc_rpi"
# Default configuration files for your hardware if any
LIRCD_CONF="\etc\lirc\lircd.conf"
LIRCMD_CONF=""
Yes, I second @balbuze. Try without all that manual modifications but use the config page of the IR Controller plugin to set the GPIO pin to 5. Before doing so make sure the files you have modified manually are back to their default content.
# Add your custom config.txt options to this file, which will be preserved during updates
# Add your custom config.txt options to this file, which will be preserved during updates
dtoverlay -l
volumio@volumio:~$ dtoverlay -l
No overlays loaded
If you now enable the plugin do you see the option to configure the GPIO pin on the config page of the plugin? If that should not be the case please post the result of
IMHO there must either be other hardware connected that occupies the gpio-ir module during boot or there is still some modification in the play that leads to the same effect. Make sure your “/etc/modules” is back to its default content. I’m not sure if a factory reset does that for.
If nothing helps you may consider starting with a fresh Volumio installation. Could be faster in the end
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
i2c-dev
is a single i2c-dev entry the default for etc/modules?
OK! back in action. Just had to reset /boot/config.txt
Thanks so much for your help!!!
So to summarize: I had previously followed some old instructions on the forums to enable the IR remote. This messed with the automatic configuration of the plugin. resetting all my edits allowed the plugin to do it’s job from the GUI.
Just for others following this thread: The “/boot/config.txt” from post #6 does not show any content that would have to be reset to get the plugin working.
Just for others following this thread: The “/boot/config.txt” from