Posts by ghtester

You can use almost any Remote Control with kernel IR drivers using GPIO pin at RPi 4B, if you create your own custom keymap file (by editing one of most similar default templates). Even without Harmony. Just use a Remote Control from an old TV. There are many examples here, how to do it.

Perhaps look here, the difference for Argon ONE would be to use GPIO 23 instead of default GPIO 18.

RE: LibreELEC 9.2.6 Raspberry 4 and IrDA Dongle

If you have the Harmony, look here: Kodi, Harmony, and Raspberry PI 4 with IR sensor newb guide

Just use .gz file for upgrade to official LE 9.2.6.

For LE 9.80 Nightly test builds you can find the .tar files here: Index of /

Check the /flash/config.txt file and make sure it contains this line, which enables the analogue jack :

dtparam=audio=on

If there's not such line or if it's commented by # , edit the /flash/config.txt file ( Config.txt - LibreELEC.wiki ) to add it or uncomment and reboot the device.

Then you can set the analogue jack as output device (in LE 9.2.6 also together with HDMI audio) in Settings / System / Audio /Audio output device .

If everything is set properly and audio output through analogue jack still does not work, you may perhaps try another options: Onboard analogue audio options in config.txt (3.5mm jack) - Raspberry Pi Documentation

Or start with a fresh and clean installation of LE 9.2.6 to make sure there are no incompatible add-ons installed and it will work.

No problem, I'm glad I could help.

FYI there's also a fresh how-to made by Skripo here: Kodi, Harmony, and Raspberry PI 4 with IR sensor newb guide

Regarding to rc-empty - I don't know, perhaps the -c cleared the default keymap. I have never used that parameter so I don't know details.

Or it depends on .toml file structure which is maybe missing some keywords, I really don't know.

I think the Default keymap is assigned by kernel driver when the IR device is detected.

Probably it does not matter if there's rc-empty when everything is working fine. And when it stops working, you know what to check / how to make it working again...

Great, a good work!

Fixed in LE 9.80 Nightly build 20210128. Thanks for a quick solution!

Try to do what's described here: RE: LibreELEC 9.2.6 Raspberry 4 and IrDA Dongle

( a solution should be to use ir-keytable -a .... )

In LE 9.80 Nightly builds there're newer drivers so the mapping files have a bit different structure ( and .toml extension) but in general it's the same (also the older files without .toml extension are supported as well).

I believe this thread should be marked as Resolved as you are asking off-topic quiestions here which you should perhaps ask in your another - original thread... But hopefully you can finish what you need if you follow instructions already published here: RE: LibreELEC 9.2.6 Raspberry 4 and IrDA Dongle Do not disable anything, do not use -c parameter, just make the config files properly ( use some of example / default mapping files from the /usr/lib/udev/rc_keymaps folder as template, which is most similar to your remote control - the first line is important ), put them to override folders and use commands mentioned in the linked thread and that's all...

Maybe a small tip - search the default mapping files for a protocol that you are looking for, for example:

grep -rn '/usr/lib/udev/rc_keymaps/' -e 'rc6'

It will list the files that might be interesting for you.

Read carefully here: Infra-Red Remotes - LibreELEC.wiki

Use override directories to put updated files there as described in wiki. Do not try to modify the read only filesystem.

Use a working SSH client instead, I hope Putty could be usable: PuTTY SSH client for Mac OSX - download and tutorial

I would not try to modify the LE filesystem this way. If there're hidden folders, there's perhaps a reason why... And there's no issue to access them.

As today no fresh Nightly build was released, I reverted back to LE 9.80 20210125 which works fine again.

You are welcome.

Perhaps there's a typo and CTRL+C should be there instead of just +

So if everything is already working fine, please mark the thread as resolved.

Don't try to do many unnecesary things...

It looks you did not use the -a parameter properly. After any change in mapping file ( /storage/.config/rc_keymaps/custom_remote ) do this to save the changes permanently:

systemctl stop kodi

systemctl stop eventlircd

ir-keytable -a /storage/.config/rc_maps.cfg -s rc0

systemctl start eventlircd

systemctl start kodi

Of course in your /storage/.config/rc_maps.cfg file you need to have this line:

gpio_ir_recv * /storage/.config/rc_keymaps/custom_remote

Test with

ir-keytable -t -s rc0

while pushing RC control buttons to check if you are receiving scancodes (need to have the appropriate RC protocols enabled, for example ir-keytable -plirc -pnec -pRC5 -s rc0 )

Then use

irw

to test the key mapping.

It looks that support for Stereoscopic 3D mode was added (a 'glasses' symbol in Kodi Player) but it makes trouble with some Live TV channels on my RPi 4B.

The issue was observed with one Live TV H.265 channel at 1280x720 px Video stream, 1.78 AR, 50.000 FPS which is flickering (never seen that before).

The same issue is also with H.265 1440x1080 px stream (The Display resolution is 1920x1080)

When I tried to play with 'glases' or 'wheel / Video' settings, the only change I could make was to achieve a black screen with audio. It was not possible to disable the 3D mode so the channel is not viewable.

Other channels (with H.265 streams 1920x1080, 960x544) are working fine.

Edit - it looks I have turned on the Stereoscopic 3D mode when I tried to stop flickering and it's not easy to get away the 'glasses' from the bar...

Nevertheless, so far I could not fix that annoying issue...

Edit 2 - When the issue happens (currently a black screen), one CPU is running at 100%. At random intervals, this 100% load moves to some other CPU, at that switch moment a picture snapshot is displayed for a moment and audio is interrupted for a moment.

I have also tried to record the stream and open recording afterwards - the same issue...

I believe with WinSCP client ( WinSCP :: Official Site :: Download ) the necessary file transfers between Windows and LibreELEC are also as easy as can be...

1) I would say NO, at least NOT the device you mentioned above because IrDA/USB Bridge purpose is 2-way data transfers between IrDA devices (mostly in past) and AFAIK in general it's a quite different protocol than any of IR remote control protocols. Maybe some IrDA devices can be also used as IR RC receiver but I don't have any experience with this and it may vary. See Infrared Data Association - Wikipedia versus Remote control - Wikipedia

2) On RPi 4B it's not a big difference between Raspberry_Pi_OS and LibreELEC (with the same or similar kernel release) regarding to IR remote control configuration, you just need to use the proper config files / config files paths in LibreELEC as some default files are in read-only filesystem and you need to put the files (that you need to edit) to override paths as described in wiki here: Infra-Red Remotes - LibreELEC.wiki

Everything is working fine on RPi 4B / LE 9.2.6 so just read carefully and follow the instructions.

The simple IR sensor can be used on RPi through GPIO pins.

The /flash/config.txt update you have done should be OK, although I would put a pin number there:

dtoverlay=gpio-ir,gpio_pin=18

You may change the GPIO pin, GPIO18 is a default when not specified.

Connect the IR sensor's data pin to GPIO18,, Vcc to 3,3V, GND to GND, reboot the RPi and use ir-keytable to configure / map keys in accordance to wiki examples. That's all.

Also don't forget to update the RPi's bootloader to some of recent versions (at least directly from LE 9.2.6).

In case you still won't get a reply from ir-keytable similar to example below, your LE installation is probably screwed up somehow and consider to start with a fresh LE 9.2.6 installation:

Found /sys/class/rc/rc0/ with:

Name: gpio_ir_recv

Driver: gpio_ir_recv

Default keymap: rc-rc6-mce

Input device: /dev/input/event1

LIRC device: /dev/lirc1

Attached BPF protocols:

Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm

Enabled kernel protocols: lirc nec

bus: 25, vendor/product: 0001:0001, version: 0x0100

Repeat delay = 500 ms, repeat period = 125 ms

At first, I would read here and try to follow the instructions: HOW-TO: provide bug-reports

In general, it's easy to make the IR receiver working on RPi 4B using GPIO and IR sensor.

At first, you need to enable it - put this line to /flash/config.txt file (read only by default, remount as RW before edit):

dtoverlay=gpio-ir,gpio_pin=18

You may change the GPIO pin, GPIO 18 is a default when not specified.

Then connect the IR sensor's data pin to GPIO18, reboot the RPi and use ir-keytable to configure / map keys as described here: Infra-Red Remotes - LibreELEC.wiki