Posts by HiassofT

It could be that you need to transmit the IR code multiple times - my old Panasonic CRT TV only powered up if the power button was held down for about 0.5-1 seconds.

You could try something like this:

ir-ctl -g 75000 --send=button-power--send=button-power--send=button-power--send=button-power--send=button-power

"-g 75000" sets the gap / pause between IR signals to 75ms - that's about the value I see with my panasonic remote. You can also try other values in the range of (about) 50000 to 100000.

To add more repeats just add --send... more often - maybe try with 10 instead of 5 if it doesn't work.

It's a bit odd though that the TV didn't blink when you sent the code (IIRC my old CRT TV blinked shortly, multiple times when powering up).

It could be that the recorded signals aren't accurate enough - MCEUSB has 50µs resolution and this page Description of the panasonic infrared protocol (REC-80) says the intervals are about 420µs in USA and 450 in europe (not sure if that's correct, different lengths are quite odd).

so long,

Hias

The easiest way to do that with ir-ctl would be to capture the raw signals to a file and then send those. for example:

record a button to file "tv-power"

ir-ctl -1 --receive=tv-power

transmit the signal:

ir-ctl --send=tv-power

An alternative would be to use lircd if you can find a lircd.conf with the signals/codes for your TV.

Converting those various "ir codes" you find on the net to a format suitable for ir-ctl or lircd isn't easy as there's no real standard for them.

so long,

Hias

just install the Hyperion addon from the LibreELEC repository - no need to mess around with other hyperion binaries, they are usually built for Raspbian and known to cause issues.

Read more about Hyperion on LE in the wiki Hyperion [LibreELEC.wiki]

so long,

Hias

you only need dtoverlay=gpio-ir in config.txt - that's enough to get an IR receiver connected to GPIO 18 working with an MCE remote.

Make sure you have no stale config files (eg lircd.conf) or scripts hanging around from your old installation - if in doubt remove them.

Also see the wiki for more info: Infrared Remotes [LibreELEC.wiki]

so long,

Hias

Kodi already supports context-specific keymapping. For example to map up/down on the navigation wheel to volume-up/down when visualization/full-screen music or full-screen video is playing you can use add the following block (between </global> and </keymap>) to keymap.xml:

<Visualisation>
  <keyboard>
    <volume_up>VolumeUp</volume_up>
    <volume_down>VolumeDown</volume_down>
  </keyboard>
</Visualisation>
<FullscreenVideo>
  <keyboard>
    <volume_up>VolumeUp</volume_up>
    <volume_down>VolumeDown</volume_down>
  </keyboard>
</FullscreenVideo>

The main reasons for dropping atvclient is that it didn't really work perfect and was constantly causing issues over the past few years. And as no one on the team is using an Apple IR remote testing and fixing was rather cumbersome.

As in the meanwhile the Apple IR receiver is perfectly supported by the linux kernel and with kodi keymap configuration people have a far more flexible possibility to map and configure the remote the decision to drop atvclient wasn't a really hard one - as a better alternative to it exists.

I'm a bit undecided if we should route it through eventlircd (like a few other remotes) by default, the pro of that would be that you could use the navigation wheel to navigate through the menus OOTB, but you'd also loose the possibility to use longpress mappings - which some users prefer to have on low-button-count remotes like the Apple one.

so long,

Hias

Good to know that navigation works now!

How did you previously (with atvclient) get volume up/down?

With keyboard input in kodi (which is how the remote is recognized/setup at the moment) you can assign separate functions to long-pressing a button.

eg to get volume-up/down when long-pressing up/down add the following 2 lines after the volume_up / down entires in your keymap:

<volume_up mod="longpress">VolumeUp</volume_up>
<volume_down mod="longpress">VolumeDown</volume_down>

PS: forget about lirc, it's not needed and you would loose longpress support in kodi.

so long,

Hias

Thanks for the info!

The info on the kodi wiki page looks a bit outdated. Please try with this keymap instead:

<keymap>
  <global>
    <keyboard>
      <browser_back>Left</browser_back>
      <browser_forward>Right</browser_forward>
      <volume_up>Up</volume_up>
      <volume_down>Down</volume_down>
      <key id="61952">Back</key>
    </keyboard>
  </global>
</keymap>

This maps the "menu" button on the remote to "Back" (something in kodi's "menu" key handling doesn't look quite right, therefore I had to use the id variant), long-pressing on the center return/OK/select button will bring up the context menu (that's the default action in kodi, so it's not listed in the keymap above).

so long,

Hias

First install the System Tools addon (from the LibreELEC repository, in the section "Programs") and enable debug logging in kodi. Then reboot.

Now press up/down/left/right/OK buttons (plus any other buttons on the remote) and observe if they trigger some obvious functions in kodi.

Then ssh into LE and run the following commands and post the output:

systemctl stop kodi
systemctl stop eventlircd
paste .kodi/temp/kodi.log
journalctl -a | paste
lsusb

Then run

evtest

and choose the event device number of the Apple IR receiver (it should have appleir or something similar in it's description. evtest will then output some info, ignore that.

Now press all of the buttons, one after the other. You should see some lines like

Event: time 1565859742.121362, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1565859742.121362, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1
Event: time 1565859742.121362, -------------- SYN_REPORT ------------
Event: time 1565859742.137362, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e9
Event: time 1565859742.137362, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 0
Event: time 1565859742.137362, -------------- SYN_REPORT ------------

for each button press. Post that output here, too.

so long,

Hias

Try deleting /storage/.kodi/userdata/profiles.xml, it seems to have become corrupted. We got several reports of this issue, not sure what could be causing that (except for unclean shutdowns, i.e. just pulling the plug).

so long,

Hias

atvclient has been dropped in LibreELEC master and 9.2 because it was constantly causing troubles.

The remote should be supported by the linux kernel, but probably the buttons need to be remapped - the hid-appleir kernel driver sends volume-up/down and back/forward when you press the navigation keys.

Please post dmesg, lsusb and journal from LE 9.1.002 and a kodi debug log where you pressed the various buttons on the remote - this should allow us to create a proper default config for the remote.

so long,

Hias

Quote from Mario77

So I updated a RPi 3b from LibreElec Addon from 9.0.2 to 9.1.002 and it starting acting weirdly...went to safe mode many times and got over 2000 crash logs in a week..

Can you try enabling hdmi_force_hotplug=1 in config.txt? Looks like kodi is having troubles with composite video mode (which is default if no HDMI device is connected).

so long,

Hias

This is due to an upstream kernel change, previously the mce keyboard events were sent from a separate linux input device, with recent kernels they are sent from the standard rc core input device - and the events are routed through eventlircd (so normal keyboard handling is semi-broken in kodi).

You can disable routing through eventlircd by creating an empty 98-eventlircd.rules udev rules file:

: > /storage/.config/udev.rules.d/98-eventlircd.rules

This will re-establish keyboard functionality with mce_kbd but also means IR remote events (eg from an MCE remote) will show up as keyboard events in kodi and several buttons like KEY_OK won't work anymore.

This can be solved quite easily, as you are already use a custom rc keymap just change the non working keycodes in it (eg use KEY_ENTER instead of KEY_OK).

so long,

Hias

Actually this is more of a Kodi thing than a Linux one. keyboard.xml is one of Kodi's configuration files where user settings are stored.

Kodi first loads it's default configuration files (from /usr/share/kodi/system) and then the user config files (from /storage/.kod/userdata). The user config files can add new key mappings or override existing ones - we are doing the latter here, the default mapping for the power button is ActivateWindow(ShutdownMenu) - which brings up the shutdown menu.

For more details have a look at the Kodi wiki: Keymap - Official Kodi Wiki

PS: you can also change keyboard mapping with the "Keymap Editor" addon, but personally I find it a bit cumbersome to use. Creating the config files manually with an editor (nano or vi) isn't much more complicated, you see all changes you made without having to navigate through tons of submenus in the addon, and is even more flexible as you are not restricted to the functions/mappings the addon knows about.

so long,

Hias

You need to create a /storage/.kodi/userdata/keymaps/keyboard.xml file with the following contents:

<keymap>
  <global>
    <keyboard>
      <power>ShutDown()</power>
    </keyboard>
  </global>
</keymap>

The default kodi configuration is to show the shutdown menu.

so long,

Hias

Quote from Noltari

I was wondering if you could enable support for gpio-fan overlay on Raspberry Pi images, since both the 3B+ and 4B would benefit from it.

Ah, yes, that makes sense. I though we already had the gpio-fan driver enabled, but at a closer look we only enabled the fan driver for the RPi POE HAT.

I've added the config change to the LE9.2 kernel update PR so it should be included in LE 9.1.003

linux (RPi) update to 4.19.58+ by HiassofT · Pull Request #3696 · LibreELEC/LibreELEC.tv · GitHub

so long,

Hias

inputstream.adaptive is available in the LibreELEC addon repository - just install it.

RPi2/3 builds won't work on RPi4. Stick to LE 9.x for now, there won't be any RPi4 testbuilds for a while.

so long,

Hias

If you stuck your RPi somewhere in the back of your TV/shelf/... try connecting the receiver with a ~1m USB extension cable and place it somewhere in the front of the TV - so there's nothing (metal) between the keyboard and the receiver that might block RF.

so long,

Hias

The interesting line in your dmesg is this one, 2 minutes after system startup:

[ 121.582064] logitech-hidpp-device 0003:046D:400E.0004: HID++ 2.0 device connected.

I can get this on my RPi4, too, when I switch the keyboard off and then back on.

So it very much looks like the Logitech unifying receiver lost the connection to your keyboard and then reconnects. This can be for a number of reasons - RF interference, keyboard switched off/on, keyboard too far away from receiver or receiver shielded by some metal etc.

Not much we can do about it, you have to check for these things in your setup.

BTW: A couple of years ago I had connection issues with the unifying receiver plugged directly into one of the back USB ports of my PC (with metal case). Using the ~5cm adapter that shipped with it was enough to cure these. Problem in this case was the metal case shielded the receiver. So if in doubt always use the adapter.

so long,

Hias