Logitech K400 Volume Key

Would you like to confirm that @Dilligaf’s xml file above does indeed work for you ?

We’re not going to include anything which hasn’t been tested and confirmed to work and the original posters didn’t bother to reply to say whether this file worked or not.

Two buttons on one particular remote not working (out of thousands of remotes that exist) that can be fixed by copying/editing a file is a “showstopper” ? Not really…


Reasons for declaring it ShowStopper:
1) EndUser vs Experts
I am very sorry, but I am just an avarage end user loving its RaspberryPi 1+2.
But I am without linux knowledge. While my Raspi is in use as MediaCenter its vital functions are playing Video and Music to my Beamer and SoundStation controling all by Remote Keyboard and App (Logitech K400 and Android/iPhone App).
So Volume up/down are main vital functions… using my Pi as MediaCenter.
2) Complaint on Incident and Release Management
If an fix is available since 3 monhs - I would expect to get this implemented asap regarding impact and severety.
That means, is it really more important to release “Redesigned the OSMC skin to provide better colours” - instead of “Volume up/down” functions? Dont agree.
3) Customizing OSMC
I dont want to focus on customizing the OS.
I would need to concern about “Backup the System”, maybe using Test and Production Environment. Testing what happens when updating the OSMC… isn’t it?

But back to topic - I want to give it a try as recommended.

Requested Customisation:

  • OSMC running on Raspi2 sending AV to Beamer, SoundStation while using
    Keyboard Logitech K400 / iOS app / AndroidApp

How can I copy this xml-file from Windows (XP, Win7 or Win 10 available)
to SD Card my Pi2 is using with OSMC installed?


  • using Linux Reader ?
  • try using WinSCP ?
  • Dropbox File exchange ?
  • OCMC web browser if existing?

Thanks for guidance/advices. Yours, Sepp

if we know that that fix actually fixes things, then sure, we would have, but I don’t have a Logitech K400 and I still don’t know if the fix we have resolves anything…

You are aware of these things, and presumably their function, but are waiting for us to advise you to use them?

Good question ActionA. I am absolutly not aware, but looking for one easy way to get this sorted.

Maybe an older post I read before?

Functionality was confirmed in 11 Apr 2015 (3 months ago):

Edit: Location - /home/osmc/.kodi/userdata/keymaps

Now, go forth and use your WinSCP to put the file into the mentioned directory. Or put it on one of your external drives or shares or whatever and copy it from there. The file will be eventually delivered, until then use the manual workaround.

The EXACT commands required to resolve your issue are provided IN that thread that you just linked as having read before!

1 Like

And here, in our wiki, provided freely to all users, are the instructions for getting to a command line by several different methods…


Just found it 2mins earlíer . But Thanks a lot. Going to test.

Great. 1000 Thanks for great and very quick help. I didn’t want to invest more than one hour, but this makes fun, too.

OSMC on Raspi2 while using Keyboard Logitech K400 is working fine now (also the Volume up/down keys)!

Tested both ways that brought
Quick Workaround:

A) Used the Filemanager (Settings > File manager) and copy xml-file from USB device to /home/osmc/userdata/keymaps (thanks for that easiest idea @srmo)
(action requires Master User access to enter Root pathes)

… or…

B) Comandline

  • Navigate to the power icon in OSMC
  • Select Exit
  • Press ESC on your keyboard
  • Login to your device (default is username: ocmc and pw: osmc)
  • Execute following command line steps:

This enables the mute and volume down key, but there’s still an issue whereby holding these keys only causes a single keystroke.

If I remember correctly this is a shortcoming of the Hama Remote volume keys. If you put volume up and down on for example the number keys they repeat but on the volume keys they do not repeat

FAIL: Using keyboard.xml from RaspBMC device (K400 keyboard volume long-press works), does not work in the OSMC device.

From the RaspBMC rPi, (who’s K400 sounds keys work as expected when held down), I copied:


to dropbox and then to my Kodi rPI

sudo wget Dropbox - keyboard_raspBMC_WORKING.xml - Simplify your life

I then copied this file over the existing keyboard.xml:

osmc@osmc:/usr/share/kodi/system/keymaps$ sudo cp keyboard_raspBMC_WORKING.xml?dl=0 keyboard.xml
osmc@osmc:/usr/share/kodi/system/keymaps$ md5sum keyboard_raspBMC_WORKING.xml?dl=0
ea89f902d4c03cf759ed66bd6f812e07 keyboard_raspBMC_WORKING.xml?dl=0
osmc@osmc:/usr/share/kodi/system/keymaps$ md5sum keyboard.xml
ea89f902d4c03cf759ed66bd6f812e07 keyboard.xml
osmc@osmc:/usr/share/kodi/system/keymaps$ sudo reboot

I also verified that the file was overwritten by checking the md5sum and rebooted.

Great - for now.
Next kodi update and you’ll have lost it again!
You should leave the system version alone, and put your working version in /home/osmc/.kodi/userdata/keymaps/keyboard.xml


If we can merge the keyboard.xml with the one we currently use without any conflicts, then I’m happy to include this in OSMC.

@Dilligaf may be able to take a look here


My apologies! I neglected to state that it was a disappointing failure that keyboard.xml transplant did not resolve the problem:

FAIL: Using keyboard.xml from RaspBMC device (K400 keyboard volume long-press works), does not work in the OSMC device.

Not sure if put the file in the right location based on previous comment.

OK, so it’s back to square one with the RaspBMC device and pose the question: what file needs to be configured? If anyone can suggest a list of files to publish from the good RaspBMC device, please state them and I will make them available for analysis.

I am wondering if it is possible to infer the syntax (of keyboard.xml) that would allow one to specify that ‘long press’ of the volume keys (F11, F12). If this is the case then the issue can be resolved by changing keyboard.xml. That being said, the more I think about it: it would seem that the long-press( to invoke sending multiple instances) of a keystroke does not work. If this is the case, then the root cause must be addressed before making changes to keyboard.xml. In this case, I am interested in suggestions for determining a test to diagnose where in the scheme of things the process fails. Long-keypresses of the enter key work fine on OSMC so, hopefully this lengthy comment will help arrive at a diagnosis.

I think these changes are caused by the kernel, rather than missing keymaps


@sam_nazarko: I am also arriving at a similar conclusion. If there is any test that I can perform that would help to confirm / refute this hypothesis, let me know. I am will consider testing from all concerned / participating.

Works also with the Microsoft All-In-One Media Keyboard