Could you tell us more about your setup, did you add special config files, how are you starting irexec, did you update LibreELEC or something else before it stopped working? Have you actually been running lircd before, i.e. was lirc enabled in LE settings (irexec can work without lircd, too).
With an MCE remote and the builtin receiver it's generally recommended to disable lirc. The kernel then takes care about decoding the remote signals. Lirc is only needed for remotes with odd protocols that aren't supported by the kernel.
First check with irw:
This checks the remote buttons right before they enter kodi. If you see buttons here, check with kodi conf.
If you are using lirc to decode remote buttons (check with ps if lircd and lircd-uinput processes are running) you can use irw to see if lircd is working correctly:
irw /run/lirc/lircd-lirc0
if this works, then either lircd-uinput or eventlircd aren't working correctly.
If you get nothing, test with mode2 to see if the IR receiver receives any signals:
In case you are not running lircd you first have to stop kodi and eventlircd - if they are running they'll interfere with the tests.
systemctl stop kodi
systemctl stop eventlircd
Run ir-keytable to see if the kernel IR decoder is setup properly. The output should look like this:
LibreELEC:~ # ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event1) with:
Driver gpio-rc-recv, table rc-rc6-mce
Supported protocols: unknown other lirc rc-5 rc-5-sz jvc sony nec sanyo mce-kbd rc-6 sharp xmp
Enabled protocols: lirc nec rc-6
Name: gpio_ir_recv
bus: 25, vendor/product: 0001:0001, version: 0x0100
Repeat delay = 500 ms, repeat period = 125 ms
Check that you have the "rc-rc6-mce" table and "nec" and "rc-6" listed amongst the enabled protocols.
Also test the kernel can decode the remote signals:
If you still don't see anything and lirc is listed under supported protocols you can use "mode2" as above as well to check if any IR signals are received.
so long,
Hias
Display More
Hi, and thanks for your reply. And what a reply! Great stuff!
First, about my setup. It's a Intel NUC (NUC5CPYH). About the custom files, it's just the remote.xml that's in the main (not user path) kodi path, copied to my /.kodi/userdata and edited some stuff. No big things.
My lircrc is started with the autostart.sh with this lines.
#!/bin/sh
#start IRexec
/usr/bin/irexec -d /storage/.config/.lircrc
I didn't do any update to LibreELEC right before my remote stopped working. The only thing I can think of is that i MIGHT have switched the lirc option in the LibreELEC addon in Kodi. I saw it, and thought "hey, shouldn't this be enabled since I use a remote". But even if I disable and reboot, the remote still doesn't work. It might also be that I switched the lirc option before the weekend, and it was first yesterday I rebooted LibreELEC (even though I think I rebooted LibreELEC because it did respond to the remote and I did a hard reboot, but it might be something else that forced me to do a reboot also...).
As I said, I don't think I had that option enabled before, and my remote and irexec worked anyway it seems.
When I run "irw" in a terminal and press the remote, nothing happens. When I run "mode2" this happens.
About the other tests you asked me to do, this is the result of them. It looks like I got what you asked for, but with the last test nothing happens when I press buttons on the remote.
EDIT: It doesn't got all the things that should be enabled. Missing "nec" and "rc-6" listed amongst the enabled protocols.
In ~/.config I got a file called remote.conf, where the line that not has a # in front says " REMOTE_BACKEND="lirc" "
In ~/.kodi/userdata I got a file called Lircmap.xml that looks like this
I hope this can give you some more information about what might have gone wrong for me. As I said, everything has worked just great with the remote before this. I've once learned how it all worked with the config files and then forgot about it again, but since OpenELEC and LibreELEC I got kind of spoiled with the lirc part just working. =)
Thanks.
/Söder
