Posts by HiassofT

  • IR receiver driver is not loaded

    The logs look fine,

    The Ortek IR receiver shows up as keyboard+mouse input devices and isn't handled by the rc-core subsystem so it won't show up in ir-keytable and you can only use it with the remote it was bundled with.

    I did a quick test here on RPi4 with the remote+receiver and it worked out of the box.

    so long,

    Hias

  • Challenge: Translate IR received command into different IR transmit command

    With gpio-ir-tx it's similar as for gpio-ir, you can use gpio_pin=XX to use a different GPIO.

    Actually, it'd be best to connect the IR transmitter to GPIO 18 (and use a different one for receive), then you can use pwm-ir-tx instead of gpio-ir-tx (pwm-ir-tx uses the PWM to generate the carrier frequency and is therefor e more precise and less cpu intensive than the bit-banged gpio-ir-tx).

    With these 2 overlays loaded you'll get two /dev/lircX devices and you'll need to add some udev rules to create eg /dev/lirc-transmit and /dev/lirc-receive symlinks - it's not guaranteed that eg /dev/lirc0 will always be receive, this may change.

    As you already have a working lircd setup you can use that for receive - just change the device in lirc options to the /dev/lirc-receive one.

    To use lircd for transmitting you'd need to setup a second lircd instance (separate lircd.socket and lircd.service systemd units plus separate lirc options and lircd.conf files), which is a bit tricky. Also lircd has some nasty bugs when transmitting (I reported that aeons ago but it hasn't been fixed) - so better avoid lircd.

    You can use ir-ctl instead for sending, it doesn't require a background daemon and you can simply specify the lirc device and protocol+scancode (or alternatively a raw file which you can capture with ir-ctl -r, if the protocol isn't natively supported by ir-ctl). To find out the scancode+protocol simply run ir-keytable -p all -t on the receiving device and push buttons on the remote which you want to simulate.

    Also search this and the raspberry pi forum, I posted several more infos about IR there (search for my username and/or ir-ctl, gpio-ir, ir-keytable).

    so long,

    Hias

  • Challenge: Translate IR received command into different IR transmit command

    With an IR transmitter connected to your RPi you could simply use irexec to execute irsend when a specific button is pressed.

    irexec is available in LE but not run by default - you'll need to start start it via autostart.sh or a systemd service.

    You'll probably need to delay the irsend call a bit (eg do it via a shell script and add a sleep 1 before), otherwise the IR signal from your remote (where you are pressing the button) will interfere with the IR signals transmitted by the RPi.

    so long,

    Hias

  • LibreELEC on berryboot

    NOOBs (and I think also PINN) support the installation of custom/locally created images.

    I used that successfully when testing RPi4 noobs installation of LE about half a year ago but can't remember the details. IIRC you need a tar file for each partition or sth like that - just check the NOOBs docs or the thread on the RPi forum.

    so long,

    Hias

  • Can't get my IR receiver to work

    It's a bit odd that the Xbox remote doesn't work. I checked the driver code and it should support all variants of the NEC protocol.

    Getting an (HP branded) MCE receiver is the best option. The IR receiver in these DVB dongles isn't too great, it reacts quite sluggish and I often had issues with it as well in the past (even with the Hauppauge RC5 remote that came with it).

    so long,

    Hias

  • after RPi3 -> RPi4 upgrade: Infrared remote not working anymore

    Are you sure your Harmony is set up right? In general it's recommended to configure the Harmony remotes to use the Microsoft Media Center (MCE) remote profile (NOT the MCE keyboard profile!), then it'll work out of the box with LE (you only need to add the dtoverlay=gpio-ir line to config.txt).

    If in doubt simply run ir-keytable -p all -t, that'll show scancodes of all supported protocols that the IR receiver saw. If you don't see anything from your Harmony remote, look at the Harmony config.

    so long,

    Hias

  • Can't get my IR receiver to work

    First of all I'd recommend updating to LE 9.2 - 8.2.5 is quite old.

    To change the protocol simply use ir-keytable -p ... (leaving out the -d device) or specify the rcX device with -s rcX.

    Your IR receiver is a bit limited as it contains a hardware decoder that only supports a few protocols. It should work fine with the remote that came with it but it- could well be the remotes you tried use a protocol that this receiver can't understand.

    For further info also check the Wiki: Infrared Remotes [LibreELEC.wiki]

    so long,

    Hias

  • Shall I update the Bootloader EEPROM and/or VIA USB3 firmware?

    Odd, haven't seen a hang on reboot here yet. The hangs reported in the linked thread were caused by early versions of the USB firmware updater (which updated the firmware while the system was running), LibreELEC ships with a later version where updates are performed by the bootloader (recovery.bin to be more specific).

    In LibreELEC settings you can't reflash the firmware if they are up to date, but you can do it manually via ssh if you like. LibreELEC includes the rpi-eeprom-update tool (same tool as on Rasbian) and you can also use it to install beta firmwares (do that at your own risk though).

    To re-flash the USB firmware use the "-u" option of rpi-eeprom-update

    Code
    rpi-eeprom-update -u /lib/firmware/raspberrypi/bootloader/critical/vl805-000137ab.bin

    so long,

    Hias

  • Samsung Remote for rpi 4 media center with libreelec 9.2

    You seem to have put a lircd.conf file into /storage/.config so lirc is used - make sure the file matches the remote you are using.

    You can also try running ir-keytable -p all -t, if that outputs lirc scancodes when you press buttons it means the IR protocol is supported by the kernel (the output will show you which protocol that is) and you can drop the lircd.conf file and use ir-keytable / rc_maps.cfg configuration instead (which is a lot less error-prone than using irrecord to create a lircd.conf file).

    so long,

    Hias

  • Shall I update the Bootloader EEPROM and/or VIA USB3 firmware?

    Yes, it's recommended to apply these updates.

    The official LibreELEC 9.2 builds only ship with the "critical" firmware updates (which are applied automatically on Raspbian) and in general it's safe to install them.

    Milhouse builds and other development/test builds may contain beta firmware versions, so be careful in this case.

    The VL805 update should reduce temperature quite a bit (3-5°C IIRC).

    LibreELEC 9.2.1 will ship with a newer RPi firmware and kernel which will reduce (idle) temperature further. I've been testing these here the last months, all initial bugs and rough edges seem to have been ironed out and it's working fine here.

    so long,

    Hias