Important change in LE13 remote handling

  • Thanks to long-time joint effort work Kodi now has significantly improved input handling.

    This allowed us to finally drop the eventlircd workaround and use standard linux (lib)input handling for remotes, too.

    Currently LE13 images are building and the next nightlies will contain this change.

    One of the benefits is that Kodi now supports a lot more buttons/keys and the majority of the remotes should now work out-of-the-box.

    Another benefit of standard Kodi input handling is that you no longer need to fiddle around with Lircmap.xml or remote.xml to remap the buttons but can use the keymap editor addon from the kodi repo (or modify keyboard.xml).

    And this finally brings long-press support to remotes, too - which helps a lot if your remote has very few buttons. eg longpress-OK will open the context menu.

    As with every big change there will be some minor disruptions:

    If you previously adjusted the button mapping with remote.xml you'll now have to redo it.

    Even if you didn't change it the mapping may now be a bit different - just use the keymap editor addon to adjust it to your preferences.

    And although kodi now supports a lot more buttons it could be that your remote uses some keycodes that kodi doesn't support (yet).

    In this case we need your help so we can further improve Kodi and LibreELEC:

    Please tell us about the vendor and model of your remote and which buttons are not working and also post a kodi debug log:
    Enable debug logging in the kodi settings, then reboot, then just press the non-working keys and then upload the log - either by running "pastekodi" over ssh or with the log upload function in the LibreELEC settings - and post the URL to the log.

    so long,

    Hias

  • Hi Hias.

    What's the new procedure for over-riding the /usr/share/kodi/ - special://xbmc/system/keymaps/*.xml  ?

    In General Support/Nightly LE13: remote.xml not loaded, lomion asked :

    lomion
    June 29, 2026 at 7:34 PM


    The further conversation focused on sorting out his specific issue, but the initial question got left behind.

    I have a number of entries such as :

    Code
    <mute>RunScript(/storage/.config/BTconnect.py)</mute>
    <record>ToggleWatched</record>

    The Keymap Editor addon isn't useable for that, and a re-customised keyboard.xml or remote.xml files saved to special://profile/keymaps/ (/storage/.kodi/userdata) are still ignored.

    https://paste.libreelec.tv/cottaged-sunni.log

  • Create a keyboard.xml with a keyboard instead of a remote section.

    The key/button codes are a bit different (remote had special remote button codes), eg instead of mute you likely have to use volume_mute - if in doubt check the HandleKey lines in kodi.log in debug mode.

    so eg this should work:

    Code
    <keymap>
      <global>
        <keyboard>
          <volume_mute>RunScript(/storage/.config/BTconnect.py)</volume_mute>
          <record>ToggleWatched</record>
        </keyboard>
      </global>
    </keymap>

    Have a look at the system keyboard.xml for current default mappings and available key codes.

    Edit: kodi log shows it's tripping over the media and exit button/keycodes in your xmls.

    so long,

    Hias

  • Aaah, got it.

    Thanks :thumbup:

    Edit: kodi log shows it's tripping over the media and exit button/keycodes in your xmls.

    Edit: Yeah - that's a long-standing thing likely stemming from some fiddling I did with Logitech Harmony mapping years ago.

    I never did track down what the exact issue was between harmony/lirc/remote.xml - all I recall now is that is was non-obvious and would likely require some action from Logitech support, and considering they had shut down that product line ... never going to happen.

    Long story short - it's a bit of log noise I have ignored for years because it doesn't affect anything I do.
    Might as well give it another pass, since I am already re-doing the map - I can at least comment out the offending bits if I don't track down the issue once more :P

    Edited once, last by kurai: Respond to Hias' edit (July 6, 2026 at 9:33 PM).

  • Ah, likely you had media and exit buttons in a remote section - that won't work.

    The lirc/ir remote handler is quite limited, it only supports a handful button codes - see https://github.com/xbmc/xbmc/blob…slator.cpp#L161

    You had to map linux input codes (like KEY_MENU) to those kodi remote button codes via a Lircmap.xml and then map the kodi remote buttons to kodi actions in remote.xml.

    Quite annoying, especially if you had a remote with lots of buttons.

    Fortunately all this is gone now :)

    so long,

    Hias

  • My mind is refreshed on what the ancient problem was, now - for what it's worth :P

    The Harmony mapping software (back when it was still an actively supported thing by Logitech) had issues with a different IR receiver I added after the old one died - the previous one was some Hauppage-alike thing that was fine as being talked to as "Generic PC IR" and JustWorked[tm], but the new one had to be specifically defined as a Microsoft Media Center Extender (MCE) receiver.

    The problem arose because Logitech's definition table of MCE controls didn't 100% match Microsoft's defintions, and the button fucntion remaps were only available as pre-defined options from a drop-down menu, rather than customisable.

    So, as you say, I had to do an annoying chain of workarounds - in Harmony, map a broken definition to a working but unused one, that also had a matching linux input code, then shovel that into lircmap, then a final kodi remote.xml entry. <X

    It was a bit of work to unpick all that old nonsense and translate it to the much saner new method, but worth it.

    Should be much easier to change/maintain in future if I need to alter anything again.

    <3