LE12 - PS3 BD Remote re-configure mapping

DerDominik · January 7, 2025 at 12:18 PM

Hello @ll,

since a long time I'm using LE11 on my NUC which is working good, and I want to change to LE12.
But there's a small problem with my PS3 BD Remote, where not all buttons are working like "normal".

I created for comparison two log-files.

LE11 -> Working
Button pressing from line 1050

LE12 -> Not working
Button pressing from line 1309

What I'm wondering. In LE11 LIRC is used and in LE12 I don't see something like LIRC in the log files?!
Don't wonder, LE12 is installed on a RPi4, but same behabiour on my NUC.

Is there a possibility to re-map the buttons from my PS3 BD Remote?

Thanks and best regards,
Dominik

DerDominik · January 8, 2025 at 1:20 PM

Today I did some more test with LE12 and I'm more and more confused.

I stopped kodi from ssh terminal (systemctl stop kodi) and started a libinput logging with "libinput debug-events --show-keycodes"
Here I see the buttons from my Sony BD Remote as I would expect

Code

LibreELEC:/etc/bluetooth # libinput debug-events --show-keycodes
-event2   DEVICE_ADDED            Logitech USB Keyboard             seat0 default group1  cap:k
-event3   DEVICE_ADDED            Logitech USB Keyboard             seat0 default group1  cap:kp scroll-nat
-event4   DEVICE_ADDED            BD Remote Control                 seat0 default group2  cap:k
event4   KEYBOARD_KEY            +0.000s       KEY_UP (103) pressed
event4   KEYBOARD_KEY            +0.109s       KEY_UP (103) released
event4   KEYBOARD_KEY            +0.439s       KEY_DOWN (108) pressed
event4   KEYBOARD_KEY            +0.546s       KEY_DOWN (108) released
event4   KEYBOARD_KEY            +1.014s       KEY_LEFT (105) pressed
event4   KEYBOARD_KEY            +1.121s       KEY_LEFT (105) released
event4   KEYBOARD_KEY            +1.389s       KEY_RIGHT (106) pressed
event4   KEYBOARD_KEY            +1.476s       KEY_RIGHT (106) released
event4   KEYBOARD_KEY            +2.544s       KEY_AUDIO (392) pressed
event4   KEYBOARD_KEY            +2.572s       KEY_AUDIO (392) released
event4   KEYBOARD_KEY            +3.040s       KEY_ANGLE (371) pressed
event4   KEYBOARD_KEY            +3.168s       KEY_ANGLE (371) released
event4   KEYBOARD_KEY            +3.596s       KEY_SUBTITLE (370) pressed
event4   KEYBOARD_KEY            +3.684s       KEY_SUBTITLE (370) released
event4   KEYBOARD_KEY            +4.051s       KEY_RED (398) pressed
event4   KEYBOARD_KEY            +4.179s       KEY_RED (398) released
event4   KEYBOARD_KEY            +5.367s       KEY_INFO (358) pressed
event4   KEYBOARD_KEY            +5.476s       KEY_INFO (358) released
event4   KEYBOARD_KEY            +5.924s       KEY_MENU (139) pressed
event4   KEYBOARD_KEY            +6.031s       KEY_MENU (139) released
event4   KEYBOARD_KEY            +6.341s       KEY_CONTEXT_MENU (438) pressed
event4   KEYBOARD_KEY            +6.468s       KEY_CONTEXT_MENU (438) released
event4   KEYBOARD_KEY            +6.777s       KEY_ESC (1) pressed
event4   KEYBOARD_KEY            +6.885s       KEY_ESC (1) released

Display More

But if I start Kodi it seems that another mapping is automatically taken.

Most of the buttons are working, but the (for me) important Menu button is not working (the part after left, right should be the menu button)

Code

2025-01-08 13:16:15.382 T:10771   debug <general>: Keyboard: scancode: 0x6c, sym: 0x112, unicode: 0x00, modifier: 0x0
2025-01-08 13:16:17.463 T:10780   debug <general>: CLibInputKeyboard::ProcessKey - using delay: 500ms repeat: 125ms
2025-01-08 13:16:17.463 T:11295   debug <general>: Thread Timer start, auto delete: false
2025-01-08 13:16:17.471 T:10771   debug <general>: Keyboard: scancode: 0x69, sym: 0x114, unicode: 0x00, modifier: 0x0
2025-01-08 13:16:17.471 T:10771   debug <general>: HandleKey: left (0xf082) pressed, window 10000, action is Left
2025-01-08 13:16:17.581 T:11295   debug <general>: Thread Timer 545578151680 terminating

2025-01-08 13:16:17.601 T:10771   debug <general>: Keyboard: scancode: 0x69, sym: 0x114, unicode: 0x00, modifier: 0x0
2025-01-08 13:16:19.394 T:10780   debug <general>: CLibInputKeyboard::ProcessKey - using delay: 500ms repeat: 125ms
2025-01-08 13:16:19.394 T:11304   debug <general>: Thread Timer start, auto delete: false
2025-01-08 13:16:19.398 T:10771   debug <general>: Keyboard: scancode: 0x6a, sym: 0x113, unicode: 0x00, modifier: 0x0
2025-01-08 13:16:19.398 T:10771   debug <general>: HandleKey: right (0xf083) pressed, window 10000, action is Right
2025-01-08 13:16:19.502 T:11304   debug <general>: Thread Timer 545578151680 terminating

2025-01-08 13:16:19.521 T:10771   debug <general>: Keyboard: scancode: 0x6a, sym: 0x113, unicode: 0x00, modifier: 0x0
2025-01-08 13:16:20.741 T:10780   debug <general>: CLibInputKeyboard::ProcessKey - using delay: 500ms repeat: 125ms
2025-01-08 13:16:20.742 T:11309   debug <general>: Thread Timer start, auto delete: false
2025-01-08 13:16:20.742 T:10771   debug <general>: Keyboard: scancode: 0x8b, sym: 0x00, unicode: 0x00, modifier: 0x0
2025-01-08 13:16:20.742 T:10771   debug <general>: GetActionCode: Trying Hardy keycode for 0xf200
2025-01-08 13:16:20.742 T:10771    info <general>: Skipped 3 duplicate messages..
2025-01-08 13:16:20.742 T:10771   debug <general>: HandleKey: 0 (0xf200, obc-61697) pressed, window 10000, action is
2025-01-08 13:16:20.865 T:11309   debug <general>: Thread Timer 545578151680 terminating

2025-01-08 13:16:20.901 T:10771   debug <general>: Keyboard: scancode: 0x8b, sym: 0x00, unicode: 0x00, modifier: 0x0
2025-01-08 13:16:21.714 T:10780   debug <general>: CLibInputKeyboard::ProcessKey - using delay: 500ms repeat: 125ms
2025-01-08 13:16:21.714 T:11314   debug <general>: Thread Timer start, auto delete: false
2025-01-08 13:16:21.718 T:10771   debug <general>: Keyboard: scancode: 0x0, sym: 0x00, unicode: 0x00, modifier: 0x0
2025-01-08 13:16:21.718 T:10771   debug <general>: GetActionCode: Trying Hardy keycode for 0xf200
2025-01-08 13:16:21.718 T:10771    info <general>: Skipped 3 duplicate messages..
2025-01-08 13:16:21.718 T:10771   debug <general>: HandleKey: long-0 (0x100f200, obc-16838913) pressed, window 10000, action is
2025-01-08 13:16:21.846 T:11314   debug <general>: Thread Timer 545578151680 terminating

2025-01-08 13:16:21.881 T:10771   debug <general>: Keyboard: scancode: 0x0, sym: 0x00, unicode: 0x00, modifier: 0x0
2025-01-08 13:16:22.659 T:10780   debug <general>: CLibInputKeyboard::ProcessKey - using delay: 500ms repeat: 125ms
2025-01-08 13:16:22.659 T:11319   debug <general>: Thread Timer start, auto delete: false
2025-01-08 13:16:22.663 T:10771   debug <general>: Keyboard: scancode: 0x1, sym: 0x1b, unicode: 0x1b, modifier: 0x0
2025-01-08 13:16:22.774 T:11319   debug <general>: Thread Timer 545578151680 terminating
2025-01-08 13:16:22.781 T:10771   debug <general>: Keyboard: scancode: 0x1, sym: 0x1b, unicode: 0x1b, modifier: 0x0
2025-01-08 13:16:22.781 T:10771   debug <general>: HandleKey: escape (0xf01b) pressed, window 10000, action is PreviousMenu

Display More

I tried to create a keymap xml with different entries, but nothing worked.

Code

        <keyboard>
               <key id="0xf081">KEY_UP</key>
               <key id="0xf080">KEY_DOWN</key>
       </keyboard>

Code

        <keyboard>
               <key id="f081">KEY_UP</key>
               <key id="f080">KEY_DOWN</key>
       </keyboard>

Maybe someone has an idea how to solve?

Jogee · January 10, 2025 at 3:44 PM

Have you tried mapping with the Keymap Editor addon?

When doing my own mapping on my tv remote I made the mistake of using the wrong keyname -- I used <remote> instead of <keyboard>. The keymap editor helped me find that problem.

Take a look at keynames at Keymap if you haven't already. It might not be <keyboard>.

You can use the keymap editor addon just to help find the right syntax, then use it to roll your own version as you like without needing the addon.

DerDominik · January 12, 2025 at 4:03 PM

Yes, I tried also with the Keymap Editor, but more/less same error.

If I configure some actions with buttons I get everytime the same key id, but I pressed different buttons on remote.

Code

<keymap><global><keyboard>
       <key id="16839168">audionextlanguage</key>
       <key id="16839168">nextsubtitle</key>
       <key id="16839168">menu</key>
</keyboard></global></keymap>

If I test again with the ev-test like mentioned before I see the different buttons.

In my mind main problem is, that the remote is not correct recognized (as keyboard as I see in the logs).
Is there a possbility to see some logs from LibreElec Bluetooth connection? I think there is the main problem?

**chewitt** · January 12, 2025 at 4:29 PM Best Answer

See https://github.com/LibreELEC/LibreELEC.tv/pull/9587

You can replicate this locally by creating /storage/.config/udev.rules.d/98-eventlircd.rules with the same content as the PR.

I'm interested in testing/feedback a) to get this merged for LE13, b) potentially to backport for LE12.2.

DerDominik · January 12, 2025 at 6:10 PM

Quote from chewitt

See https://github.com/LibreELEC/LibreELEC.tv/pull/9587
You can replicate this locally by creating /storage/.config/udev.rules.d/98-eventlircd.rules with the same content as the PR.
I'm interested in testing/feedback a) to get this merged for LE13, b) potentially to backport for LE12.2.

Thanks for the link to that Pull Request.
After creating the file with complete content from https://github.com/Dashinginthe90…ventlircd.rules it is now working.

Absolut great and many, many thanks for it

**chewitt** · January 12, 2025 at 6:28 PM

I merged the PR to master. It will hopefully end up in LE 12.0.2 as well.