[noggin]

Recorded the file again and renamed it and moved it to what I believe is the right folder. Unfortunately, still not working. Here is the updated log file. Would be great to get some more help. Maybe worth to try OE?

http://sprunge.us/AZFN

Would you mind posting your lircd.conf file too.

Can you confirm what else is in the folder you have copied it to?

[steve1977]

Sure. The other things in the folder are hosts.conf and samba.conf.sample as well as a bunch of other folders (aacs, hwdb.d, modprobe.d, etc.).

Below is the content of the lircd.conf file:

begin remote

name beo4
bits 32
flags SPACE_ENC|CONST_LENGTH
eps 30
aeps 100

header 9021 4477
one 541 1680
zero 541 581
ptrail 555
repeat 8991 2252
gap 111550
toggle_bit_mask 0x0
frequency 38000

begin codes
KEY_UP 0x77E1D0DE 0x00000000
KEY_DOWN 0x77E1B0DE 0x00000000
KEY_LEFT 0x77E110DE 0x00000000
KEY_RIGHT 0x77E1E0DE 0x00000000
KEY_OK 0x77E17ADE 0x00000000
KEY_BACK 0x77E140DE 0x00000000
end codes

end remote

[Milhouse]

@steve1977: It's still using lircd.conf.rpi

Please run:

Code:

ls -la /storage/.config | pastebinit

and paste the output.

[steve1977]

Thanks. http://sprunge.us/RHEZ

[HiassofT]

Recorded the file again and renamed it and moved it to what I believe is the right folder. Unfortunately, still not working. Here is the updated log file. Would be great to get some more help. Maybe worth to try OE?

http://sprunge.us/AZFN

The log looks fine, lircd is using the lircd.conf with your recorded keys, but lircd seems to have problems decoding the IR signals:

Code:

Mar 12 12:46:34 LibreELEC lircd-0.9.4c[435]: Notice: repeat code without last_code received

This can happen if irrecord failed to properly recognize the remote keys - irrecord isn't perfect and it can fail for a number of reasons (it also depends on the remote, so if you have other ones try these).

If rrecord failed look here for a lircd.conf file that matches your remote: http://lirc.sourceforge.net/remotes/

If you found one, download it to /storage/.config/lircd.conf - you may have to edit it so that the keynames are KEY_LEFT, ... as mentioned before. Some of these files are older and can contain now unsupported keynames like UP/DOWN, ... (without the KEY_ prefix).

so long,

Hias

[steve1977]

Thanks. I can try, but irrecord had easily identified my key presses. When I recorded, the "dots" showed up and it was quite easy for me to configure. Also, irrecord ran some default tests and it all worked well. Plus, it used to work before with the same remote and receiver.

One other thing I can try is to go back to OE or a Jarvis built (or both) to give it a try whether this solves it? If so, the log may provide some evidence for trouble-shooting.

[ro-76]

Did you ever find a solution? I seem to be in a similar situation.

Pi Zero W, openelec 8.0.1. IR receiver working fine and irrecord worked fine on 2 attempts. I renamed the file and it's in storage/.config/lircd.conf . I'm using a white apple remote that I have used successfully with openelec on another RPi3. I have enabled the GPIO setting in libreelec settings, but the remote just doesn't seem to work.

I think all the correct processes are running

Code:

LibreELEC (official) Version: 8.0.1
LibreELEC:~ # ps | grep lirc
  242 root       0:00 /usr/sbin/eventlircd -f --evmap=/etc/eventlircd.d --socket=/run/lirc/lircd
  427 root       0:00 /usr/sbin/lircd --driver=default --device=/dev/lirc0 --output=/run/lirc/lircd-lirc0 --pidfile=/run/lirc/lircd-lirc0.pid --release=_LIRCUP /storage/.config/lircd.conf
  428 root       0:00 /usr/sbin/lircd-uinput --release=_LIRCUP /run/lirc/lircd-lirc0
  448 root       0:00 {kodi.sh} /bin/sh /usr/lib/kodi/kodi.sh --standalone -fs --lircdev /run/lirc/lircd
  452 root       0:44 /usr/lib/kodi/kodi.bin --standalone -fs --lircdev /run/lirc/lircd
  556 root       0:00 grep lirc
LibreELEC:~ # ls -l /dev/lirc0
crw-------    1 root     root      244,   0 Mar 30 21:04 /dev/lirc0
LibreELEC:~ # lsmod | grep lirc
lirc_rpi                6120  3
lirc_dev                7253  1 lirc_rpi
rc_core                17302  1 lirc_dev

Any ideas?

Thanks

[ro-76]

This is my log file:
http://sprunge.us/NMCL

[steve1977]

Unfortunately, I have not succeeded yet. Maybe your log shows some similarities that can point to a solution?

Have you tried OE yet? My sense is that the "trick" may be to start with OE and then upgrade to LE to get it working. I wanted to give this a try, but haven't found the time yet. Will try over the next few days.

[steve1977]

Good news! (or bad news depending how you think about it).

I installed OE and everything working flawless. I used the same RPi2 with same SD and same remote. Please see the OE log file as it may point to the right direction to fix LE?

http://sprunge.us/IQNW

As a next step, I will upgrade from OE to LE and see whether it keeps the remote working.

[steve1977]

Confirmed that the remote keeps working after upgrading from OE to LE.

http://sprunge.us/OJCb

[HiassofT]

Confirmed that the remote keeps working after upgrading from OE to LE.

Could you post the working lircd.conf?

so long,

Hias

[steve1977]

Here we go: https://pastebin.com/16tubVTb

[HiassofT]

Here we go: https://pastebin.com/16tubVTb

Thanks a lot!

Comparing the two files it looks like the newer irrecord deteced the codes correctly (pre_data + data + post_data of older irrecord are identical to data in newer irrecord), but for some reason wrote out an incorrect lircd.conf file - there's 0x00000000 after the codes which makes lircd reject these lines.

so long,

Hias

[steve1977]

Thanks. So, this is a LE issue, while working in OE? Maybe different lirc version?