NOTE! This site uses cookies and similar technologies.

If you not change browser settings, you agree to it.

I understand

Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: OpenELEC 8.0 dropped LIRC support - what now?

OpenELEC 8.0 dropped LIRC support - what now? 8 months 4 days ago #1

  • elec_raspi
  • elec_raspi's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 8
  • Thank you received: 1
  • Karma: 0
Hi, I just read that the new OpenELEC 8.0 has dropped LIRC support. As my OpenELEC system bases on Raspi3 + IR receiver + LIRC
Does this mean that OpenELEC is no longer usable for me?

If it can't be used anymore what are the alternatives are there?
The administrator has disabled public write access.

OpenELEC 8.0 dropped LIRC support - what now? 8 months 4 days ago #2

  • sraue
  • sraue's Avatar
  • Offline
  • Developer
  • Posts: 2094
  • Thank you received: 650
  • Karma: 131
you dont told what for a IR receiver... OpenELEC has used LIRC in the past only for 3-4 very old remotes/receivers
The administrator has disabled public write access.

OpenELEC 8.0 dropped LIRC support - what now? 8 months 4 days ago #3

  • elec_raspi
  • elec_raspi's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 8
  • Thank you received: 1
  • Karma: 0
Hi sraue,

seems like you are not very familiar with the Raspberry, because on this platform it is obvious how to connect an IR receiver to the Raspberry:

Buy a cheap TSOP38238/TSOP4838 (about 1-2 USD) or a similar IR receiver, connect it to GPIO pin 22 or 23, Power and GND, start LIRC (and configure it) and that's it.
There are dozens of tutorials and blog entries demonstrating this way of making a Raspberry remote controllable this way.

I would assume that a large number of uses who use OpenELEC on a Raspberry use this way to make OpenELEC remote controllable. Therefore removing LIRC from OpenELEC was IMHO a wrong decision.
Last Edit: 8 months 4 days ago by elec_raspi.
The administrator has disabled public write access.

OpenELEC 8.0 dropped LIRC support - what now? 8 months 4 days ago #4

  • sraue
  • sraue's Avatar
  • Offline
  • Developer
  • Posts: 2094
  • Thank you received: 650
  • Karma: 131
use
dtoverlay=gpio-ir,gpio_pin=18,gpio_pull=1,rc-map-name=rc-rc6-mce
(set the right pin) to use gpio IR without LIRC, this is uses the newer and supported kernel driver (gpio_ir_recv).

see alsao: github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L468
The administrator has disabled public write access.
The following user(s) said Thank You: elec_raspi

OpenELEC 8.0 dropped LIRC support - what now? 8 months 3 days ago #5

  • greenkr
  • greenkr's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 8
  • Karma: 0
sraue wrote:
use
dtoverlay=gpio-ir,gpio_pin=18,gpio_pull=1,rc-map-name=rc-rc6-mce
(set the right pin) to use gpio IR without LIRC, this is uses the newer and supported kernel driver (gpio_ir_recv).

see alsao: github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L468

Can I ask for more help on this please? With Openelec 6 I was using
dtoverlay=lirc-rpi,gpio_in_pin=04
in config.txt (have a Hifiberry DAC so couldn't use the default pin). So I tried
dtoverlay=gpio-ir,gpio_pin=04,gpio_pull=1,rc-map-name=SAMSUNG-REMOTE
in config.txt as I am using the Samsung TV remote and my lircd.conf has
name=SAMSUNG_REMOTE in it.
However the remote control still does not work. I'd appreciate further advice!
The administrator has disabled public write access.

OpenELEC 8.0 dropped LIRC support - what now? 8 months 1 day ago #6

  • elec_raspi
  • elec_raspi's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 8
  • Thank you received: 1
  • Karma: 0
I don't think that rc-map-name=SAMSUNG-REMOTE will work.

If I understand it right the available mappings are located in /usr/lib/modules/4.9.20/kernel/drivers/media/rc/keymaps

In this directory the following mappings are available:
rc-adstech-dvb-t-pci.ko
rc-alink-dtu-m.ko
rc-anysee.ko
rc-apac-viewcomp.ko
rc-asus-pc39.ko
rc-asus-ps3-100.ko
rc-ati-tv-wonder-hd-600.ko
rc-ati-x10.ko
rc-avermedia-a16d.ko
rc-avermedia-cardbus.ko
rc-avermedia-dvbt.ko
rc-avermedia-m135a.ko
rc-avermedia-m733a-rm-k6.ko
rc-avermedia-rm-ks.ko
rc-avermedia.ko
rc-avertv-303.ko
rc-azurewave-ad-tu700.ko
rc-behold-columbus.ko
rc-behold.ko
rc-budget-ci-old.ko
rc-cec.ko
rc-cinergy-1400.ko
rc-cinergy.ko
rc-delock-61959.ko
rc-dib0700-nec.ko
rc-dib0700-rc5.ko
rc-digitalnow-tinytwin.ko
rc-digittrade.ko
rc-dm1105-nec.ko
rc-dntv-live-dvb-t.ko
rc-dntv-live-dvbt-pro.ko
rc-dtt200u.ko
rc-dvbsky.ko
rc-em-terratec.ko
rc-encore-enltv-fm53.ko
rc-encore-enltv.ko
rc-encore-enltv2.ko
rc-evga-indtube.ko
rc-eztv.ko
rc-flydvb.ko
rc-flyvideo.ko
rc-fusionhdtv-mce.ko
rc-gadmei-rm008z.ko
rc-genius-tvgo-a11mce.ko
rc-gotview7135.ko
rc-hauppauge.ko
rc-imon-mce.ko
rc-imon-pad.ko
rc-iodata-bctv7e.ko
rc-it913x-v1.ko
rc-it913x-v2.ko
rc-kaiomy.ko
rc-kworld-315u.ko
rc-kworld-pc150u.ko
rc-kworld-plus-tv-analog.ko
rc-leadtek-y04g0051.ko
rc-lirc.ko
rc-lme2510.ko
rc-manli.ko
rc-medion-x10-digitainer.ko
rc-medion-x10-or2x.ko
rc-medion-x10.ko
rc-msi-digivox-ii.ko
rc-msi-digivox-iii.ko
rc-msi-tvanywhere-plus.ko
rc-msi-tvanywhere.ko
rc-nebula.ko
rc-nec-terratec-cinergy-xs.ko
rc-norwood.ko
rc-npgtech.ko
rc-pctv-sedna.ko
rc-pinnacle-color.ko
rc-pinnacle-grey.ko
rc-pinnacle-pctv-hd.ko
rc-pixelview-002t.ko
rc-pixelview-mk12.ko
rc-pixelview-new.ko
rc-pixelview.ko
rc-powercolor-real-angel.ko
rc-proteus-2309.ko
rc-purpletv.ko
rc-pv951.ko
rc-rc6-mce.ko
rc-real-audio-220-32-keys.ko
rc-reddo.ko
rc-snapstream-firefly.ko
rc-streamzap.ko
rc-su3000.ko
rc-tbs-nec.ko
rc-technisat-ts35.ko
rc-technisat-usb2.ko
rc-terratec-cinergy-c-pci.ko
rc-terratec-cinergy-s2-hd.ko
rc-terratec-cinergy-xs.ko
rc-terratec-slim-2.ko
rc-terratec-slim.ko
rc-tevii-nec.ko
rc-tivo.ko
rc-total-media-in-hand-02.ko
rc-total-media-in-hand.ko
rc-trekstor.ko
rc-tt-1500.ko
rc-twinhan-dtv-cab-ci.ko
rc-twinhan1027.ko
rc-videomate-m1f.ko
rc-videomate-s350.ko
rc-videomate-tv-pvr.ko
rc-winfast-usbii-deluxe.ko
rc-winfast.ko

I was testing rc-rc6-mce on a fresh OpenELEC 8 installation and surprisingly a lot of keys are working.
The administrator has disabled public write access.
The following user(s) said Thank You: greenkr

OpenELEC 8.0 dropped LIRC support - what now? 8 months 18 hours ago #7

  • greenkr
  • greenkr's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 8
  • Karma: 0
Many thanks for the pointer where to look for the ko files. I spotted rc-tivo.ko, tried that in config.txt and it just worked! Now I just need to find one to work with my Samsung Tv remote though failing that I have another spare Tivo remote.
I wonder if it's possible to customise rc-map-name files?
The administrator has disabled public write access.

OpenELEC 8.0 dropped LIRC support - what now? 8 months 18 hours ago #8

  • elec_raspi
  • elec_raspi's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 8
  • Thank you received: 1
  • Karma: 0
I don't think that a custom file would help here. The folder is part of the OpenELEC compressed image and thus it is part of the read-only system.

You would have to build your own OpenELEC distribution to change/add a file in this directory.
The administrator has disabled public write access.

OpenELEC 8.0 dropped LIRC support - what now? 8 months 12 hours ago #9

  • JimmySmith
  • JimmySmith's Avatar
  • Offline
  • Junior Boarder
  • Posts: 92
  • Thank you received: 18
  • Karma: 2
I think custom mapping should be avaible for gpio-ir too. I just dont know difference between learning gpio-ir and lirc (openelec.tv/forum/120-news-announcements/83339-stable-openelec-8-0-released?start=90#168720) yet. Bunch of tutorial for Lirc, failing to find one for gpio-ir.
RPi2 B + Panasonic TV, LE 7.0.3
RPi2 B + Samsung TV, LE 7.0.3
RPi2 B + LG TV, LE 7.0.3
RPi2 B + Older Panasonic TV, LE 7.0.1
MySQL from LAMP plugin as Library DB
Last Edit: 8 months 12 hours ago by JimmySmith.
The administrator has disabled public write access.

OpenELEC 8.0 dropped LIRC support - what now? 7 months 4 weeks ago #10

  • HiassofT
  • HiassofT's Avatar
  • Offline
  • Senior Boarder
  • Posts: 135
  • Thank you received: 73
  • Karma: 22
JimmySmith wrote:
I think custom mapping should be avaible for gpio-ir too. I just dont know difference between learning gpio-ir and lirc (openelec.tv/forum/120-news-announcements/83339-stable-openelec-8-0-released?start=90#168720) yet. Bunch of tutorial for Lirc, failing to find one for gpio-ir.
I posted a step-by-step tutorial how to do this on the LibreELEC forum:
forum.libreelec.tv/thread-7152-post-43745.html#pid43745

In OpenELEC it's basically the same, only difference is probably how to make the configuration permanent.

One possibility is to hook into ir-keytable -a /etc/rc_maps.cfg (which is automatically run when the device is registered) and override the keycode table with a file in /storage/.config/rc_keymaps:

eg if your IR receiver uses the rc-rc6-mce table you have to store your local keycode table in /storage/.config/rc_keymaps/rc6_mce. This is because of the following line in /etc/rc_maps.cfg:
*    rc-rc6-mce        rc6_mce
That line means: On any IR receiver (driver name is "*") that uses the rc-rc6-mce table lookup a file named rc6_mce. That file is first looked up in /storage/.config/rc_keymaps/ (/etc/rc_keymaps symlinks there), then in /usr/lib/udev/rc_keymaps/

To test if your configuration works run the following command:
ir-keytable -v -a /etc/rc_maps.cfg
Amongst a lot of debug output this'll print which keytable file was picked up. eg:
Table for gpio-rc-recv, rc-rc6-mce is on rc6_mce file.
Parsing /etc/rc_keymaps/rc6_mce keycode file

so long,

Hias
The administrator has disabled public write access.
The following user(s) said Thank You: Grohol, JimmySmith, greenkr

OpenELEC 8.0 dropped LIRC support - what now? 7 months 4 weeks ago #11

  • JimmySmith
  • JimmySmith's Avatar
  • Offline
  • Junior Boarder
  • Posts: 92
  • Thank you received: 18
  • Karma: 2
Thank you so much for your input. In fact, I am using LE, and just quickly test new method (as this interesting for me) yesterday, but got stucked with ir-keytable -t, which doesnt react on Remote control (in fact NEC VHS :) at all.

I will get back to some more testing tommorow, maybe I will have more luck with your posts. Considering the possibility, that lirc (eventlirc?) will be totally replaced via this kernel tool (if those have the same functionality) in rest of Kodi-Rpi OS's, its better to be prepared for the future.

I would expect some wiki page about this around Rpi/OE/LE pages - if lirc is really becoming deprecated (?), but lets see.

EDIT: NoGo :(

I have this setup:
dtoverlay=gpio-ir,gpio_pin=18,gpio_pull=1,rc-map-name=rc-rc6-mce
[   10.019347] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[   10.091965] Registered IR keymap rc-rc6-mce
[   10.092502] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input0
[   10.092889] rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0
[   10.130443] IR JVC protocol handler initialized
[   10.145872] lirc_dev: IR Remote Control driver registered, major 244
[   10.151610] rc rc0: lirc_dev: driver ir-lirc-codec (gpio-rc-recv) registered at minor = 0
[   10.151642] IR LIRC bridge handler initialized
[   10.179375] IR RC5(x/sz) protocol handler initialized
[   10.179379] IR NEC protocol handler initialized
[   10.179936] input: MCE IR Keyboard/Mouse (gpio-rc-recv) as /devices/virtual/input/input1
[   10.181908] IR MCE Keyboard/mouse protocol handler initialized
[   10.182268] IR Sony protocol handler initialized
[   10.182437] IR Sharp protocol handler initialized
[   10.183268] IR RC6 protocol handler initialized
[   10.184733] IR SANYO protocol handler initialized
systemctl stop kodi
systemctl stop eventlircd

ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event0) with:
        Driver gpio-rc-recv, table rc-rc6-mce
        Supported protocols: unknown other lirc rc-5 jvc sony nec sanyo mce-kbd rc-6 sharp xmp
        Enabled protocols: unknown other lirc rc-5 jvc sony nec rc-6 sharp xmp
        Name: gpio_ir_recv
        bus: 25, vendor/product: 0001:0001, version: 0x0100
        Repeat delay = 200 ms, repeat period = 125 ms

When I try ir-keytable -t, no input shown from NEC and Samsung remotes. I also tried all other (-p rc-5, then rc-6, sony, sanyo, nec) explicitly, and test with NEC, Samsung and even Panasonic TV remotes, and still, no info at all. I dont know, where could be a problem here. The TV (Panasonic remote) is quite new, like 2015/2016 model, so I think it should be recognized by something.

Btw., Samsung remote (which I using with lirc) has this kind of codes inside lirc conf:
begin remote

  name  /storage/.config/lircd.conf
  flags RAW_CODES|CONST_LENGTH
  eps            30
  aeps          100

  gap          50205

      begin raw_codes

          name key_up
             3338    1846     467    1127     461    1116
              472     410     461     404     467     405
              466     405     468    1120     493     378
              468    1126     461    1116     472     403
              468     410     461    1121     467     404
              468    1121     466     404     468    1115
              469     407     470     401     468     404
              468     410     461     404     472     404
              468     404     467     410     462     404
              467    1119     468     411     461     404
              468     403     472     404     468     410
              461    1120     468    1121     461     404
              472     405     467     404     467    1127
              461     404     468     404     467

Any help would be appretiated. I think system doesnt operate with IR module at all, but I dont know what to setup differently except pin number.
RPi2 B + Panasonic TV, LE 7.0.3
RPi2 B + Samsung TV, LE 7.0.3
RPi2 B + LG TV, LE 7.0.3
RPi2 B + Older Panasonic TV, LE 7.0.1
MySQL from LAMP plugin as Library DB
Last Edit: 7 months 4 weeks ago by JimmySmith.
The administrator has disabled public write access.

OpenELEC 8.0 dropped LIRC support - what now? 7 months 3 weeks ago #12

  • Grohol
  • Grohol's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 5
  • Karma: 1
In Openelec 8.0.2 it works as described in forum.libreelec.tv/thread-7152-post-43745.html#pid43745

Only change is that it has to be started in autostart.sh, because it seems that OpenElec does not process config files automatically.

Thank you very much for the info.
The administrator has disabled public write access.

OpenELEC 8.0 dropped LIRC support - what now? 7 months 3 weeks ago #13

  • aieser
  • aieser's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 7
  • Karma: 0
Sorry for my silly question, but what needs to be started? What command exactly?

I used LIRC for a long time, it was easy because I had a setup wizard

Maybe a step-by-step tutorial for OpenELEC would be of great help to those who are kind of lost like me.

Thanks!
Last Edit: 7 months 3 weeks ago by aieser.
The administrator has disabled public write access.

OpenELEC 8.0 dropped LIRC support - what now? 6 months 3 weeks ago #14

  • CrAzYLuKe
  • CrAzYLuKe's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 8
  • Karma: 0
I was also struggling with this issue. Just add in the config.txt following:
dtoverlay=gpio-ir,gpio_pin=18,gpio_pull=1,rc-map-name=rc-rc6-mce

Then it works again.

Cheers
Luke
The administrator has disabled public write access.

OpenELEC 8.0 dropped LIRC support - what now? 5 months 2 weeks ago #15

  • Brune
  • Brune's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 1
  • Karma: 0
Hi!
I had been using Openelec up to 7.0.1 with a 4838 receiver, a custom keymap and some weird remote control setup i put into my harmony 350.
Since it's a harmony I should be able to use any remote setup I want.
with the input from this thread
dtoverlay=gpio-ir,gpio_pin=18,gpio_pull=1,rc-map-name=$remote
I had no success tho. I tried several combinations of remote setups and keymaps, a rpi2 and 3, a clean install and a soft reset. nothing worked for my combination of hardware.
has anyone found a working combination of harmony setup and keymap that comes with openelec? or does anyone know what else i could try? i dont really want to be stuck on 7.0.1..
Thank you in advance!
The administrator has disabled public write access.
  • Page:
  • 1
  • 2