You are probably still using the lirc-rpi dtoverlay. You need to use "dtoverlay=gpio-ir" instead.
so long,
Hias
You are probably still using the lirc-rpi dtoverlay. You need to use "dtoverlay=gpio-ir" instead.
so long,
Hias
The position of the IR receiver can certainly have an impact, you can try rotating/moving your RPi - ideally the receiver should point directly to you.
Use of Hifiberry should be harmless, I'm using a GPIO receiver myself with the Cirrus logic audio card.
Since you mentioned streaming from NAS the linked issue immediatly came to my mind. Simply speaking: transferring data via USB can mess with GPIO IR receivers. And on RPi the (wired) ethernet chip is connected via USB.
While personally I haven't experienced that issue yet (but I mainly play from local USB HDD, sometimes stream from the internet) it's not unthinkable that you are hit by it.
so long,
Hias
Could you give 8.1.0 beta a try? KEY_OK should work there, but make sure Lirc is disabled in LibreELEC settings.
There was a bug reported of KEY_OK not working in 8.0.x, eventlircd somehow didn't seem to pick up the remote events as it should. I couldn't reproduce it myself but we got reports that it works in 8.1.0
so long,
Hias
First check with "mode2" that your IR receiver is hooked up correctly and the GPIO pin setting in config.txt is correct. You should get a bunch of "pulse" and "space" messages when you press a button on your remote.
I'm currently writing a new guide on IR remotes in LibreELEC, until that's finished here are some additional hints and pointers.
Instead of "dtoverlay=lirc-rpi" better use "dtoverlay=gpio-ir". To configure the latter for GPIO 4 add this line to config.txt:
With gpio-ir you can use the new (and IMO easier to use) "ir-keytable" method to configure remotes and don't need to enable lirc.
Have a look at this thread for detailled infos on how to setup a custom configuration using ir-keytable:
so long,
Hias
Hi, I'm a little confused now. For me before everything was fine (no repetitions) but now the key presses are repeated sometimes (Logs). I have new batteries in my remote and I really only pressed once
It seems like it occurs more often when I watch a file from my NAS then when I watch it from a USB Stick, but maybe this is just arbitrary.
Quite certainly you are hit by this issue: lirc_rpi is sensitive to interrupt latency · Issue #906 · raspberrypi/linux · GitHub
Unfortunately there's not much we can do about that, it's a general problem of the RPi and how USB and GPIO remotes are handled.
As an alternative you can use a USB IR receiver, eg one integrated into a USB DVB receiver:
[SOLVED] LibreELEC + PCTV 461e + XBox One Remote
so long,
Hias
Similar issue with double press with 8.1 generic with harmony remote upgraded from 8.0.2. Lirc is not listed under my services. Is there a file I can edit to disable lirc?
Scroll down to the end of services, the option should be there always (in 8.0 the option was only shown if an IR receiver was detected).
You can also manually disable lirc via
and then reboot.
so long,
Hias
Another thing I noticed is that my IR remote stops working for about a minute after I switch my HDMI output cables. Not a big deal, but maybe it is helpful to know.
Have you double-checked the batteries in the remote aren't flat?
Other than that: output of
after this has happened could be useful.
Also check with "mode2" if the IR receiver is getting any signals.
so long,
Hias
Hmmm, probably this (huge left/right padding)
/* force left sidebar to 255px */
.col-3cm .main { background: url(../img/sidebar/s-right-s2.png) repeat-y right 0; }
.col-3cm .main-inner { background: url(../img/sidebar/s-left.png) repeat-y left 0; padding-left: 255px; padding-right: 260px; }
.col-3cm .sidebar.s1 { float: left; margin-left: -255px; }
.col-3cm .sidebar.s2 { float: right; margin-right: -260px; /* ingenuity! */ position: relative; right: -100%; }
.col-3cm .content { float: right; }
.sidebar.s1 { width: 255px; z-index: 2; }
.s1.expanded .post-nav { opacity:1;min-width: 255px; }
These settings are without @media
so long,
Hias
I can reproduce this with firefox-esr on debian stretch
hias@camel2:~$ apt-cache policy firefox-esr
firefox-esr:
Installed: 52.3.0esr-1~deb9u1
Candidate: 52.3.0esr-1~deb9u1
Version table:
*** 52.3.0esr-1~deb9u1 500
500 http://security.debian.org stretch/updates/main amd64 Packages
100 /var/lib/dpkg/status
45.9.0esr-1 500
500 http://ftp.at.debian.org/debian stretch/main amd64 Packages
Anyone played with the CSS lately?
so long,
Hias
nslookup is the wrong tool to look up .local addresses, you have to use avahi-browse for that.
For local DNS in your LAN you should use .lan, .private or similar TLDs - .local should NOT be used for DNS, that's reserved for mDNS ("zeroconf", "avahi").
See rfc6762 for details RFC 6762 - Multicast DNS
so long,
Hias
Yes it works fine, but my key mappings don't work, so I will stick to my old configuration.
Thanks for checking!
so long,
Hias
This time, I was able to use my remote once after I started the Pi (not immediately), afterwards, the remote was dead again.
Update: After I posted this, I removed the batteries and put them back into my remote. Now it works again, so the problem was the remote, sorry. So everything works perfectly fine for me with LibreELEC 8.1 and "Enable Lirc" activated.
Thanks for your help
Cool, I like problems that can be solved that easily
As I have you here with an Xbox One remote, could you test another thing?
Change the "dtoverlay=lirc-rpi" line in config.txt to "dtoverlay=gpio-ir", disable Lirc in LE settings and then reboot.
The Xbox one remote should work out-of-the box, without having to run lirc.
so long,
Hias
if you still need some feedback :
Thanks a lot for the logs!
It looks like lircd runs a tad earlier than on my RPi, disabled in-kernel decoding, but the udev rule configuring ir-keytable seems to have run a bit later (not visible in the logs), as at the end nec and rc-6 protocols are also enabled.
Parallel startup and race conditions can be a lot of fun
so long & thanks to all of you for your feedback,
Hias
It's strange. I have activated 'lirc', reboot, and the error with double commands no longer occurs. But if I now deactivate 'lirc' again, irc no longer works, so I have to activate 'lirc' in settings now. o0
This means lircd successfully disabled in-kernel decoding. If you then disable lirc that won't be re-enabled again and your remote no longer works. You could manually enable it on the shell via "ir-keytable -p rc6,nec", but in general it's easier to just reboot.
QuoteHere still my logs:
Crap, the interesting stuff (enabled protocols) didn't make it into the logs - ir-keytable sends them to stderr instead of stdout...
If you catch a situation with double-presses again, please run these commands instead:
But no need to spend too much time on that, the info that the issue doesn't always occur was already helpful!
QuoteLooks as if the error only happens at the first reboot after update.
It's probably rather random if you get that issue or not - after all if there's a fight between 2 configuration services it's not good and the easy solution is to just disable lirc in LE settings.
so long,
Hias
Hi, I recently switched from Openelec to LibreELEC. I added the files lircd.conf, Lircmap.xml and remote.xml on LibreELEC 8.1. It didn't work until I turned on "Enable Lirc". After this it worked perfectly fine, but after some time it stopped working completely. I don't understand what's wrong. Under Openelec 5.95.3 everything was fine. Turning "Enable Lirc" on and off allows me to use my remote once, but afterwards it stops working. The remote I'm using is the Xbox one remote. I also added dtoverlay=lirc-rpi to the config.
Please post the output of these commands when the remote stopped working:
journalctl -a | paste
dmesg | paste
systemctl status lircd | paste
systemctl status lircd-uinput | paste
systemctl status eventlircd | paste
so long,
Hias
Nothing special, I just update LE v8.0.2MR through the le-addon. After reboot the entry 'lirc' was present and active.
My device: Zotac Zbox ci321nano with LE x86_64_generic
I could now (partly) reproduce the issue on RPi and understand what's going on:
In LE 8.0.x lirc is automatically enabled if an IR receiver supporting the /dev/lirc interface is detected. If you go to LE Settings->Services "Enable Lirc" will be set to on.
But although lirc was enabled it wouldn't be started unless you had a .config/lircd.conf file or were using the lirc_rpi driver on RPi or had an old xbox dvd remote dongle connected. As the remote buttons were still decoded by the kernel everything worked as before and we all seem to have missed the fact that Lirc was actually enabled when it shouldn't have been...
In 8.1.0 Lirc handling changed: on a fresh install it won't be enabled by default, and if you enable it it will actually be started - using a default lircd.conf file if you didn't provide your own.
So, on a 8.0.x->8.1.0 upgrade you are now presented with an enabled and actually running lircd.
The one thing I don't quite understand, and also couldn't reproduce so far, is why you get the "double buttonpresses" on Generic.
When lircd starts it will automatically disable in-kernel decoding. OTOH there's also the ir-keytable auto-configuration running which enables in-kernel decoding for MCE and a bunch of other remotes. Although that leads to 2 configuration services fighting against each other I had expected lircd to be run last, and thus win, and lead to remote buttons only be decoded by lircd, not the kernel - this is also what I got in my tests on RPi.
It would be great if someone plagued by double-presses could do a few tests on 8.1.0, maybe that'll give some clues about why that happens:
Enable lirc in LE settings, reboot, then run the following commands:
so long,
Hias
Make sure lirc is disabled in LE settings.
In 8.0.2 enabling lirc didn't have any effect unless you also created a .config/lircd.conf file (or were using lirc_rpi on a RPi). In 8.2 this is changed and now lirc will use a default config if you enable it in LE settings.
so long,
Hias