With 1.3.0 and before this brought the shutdown menu and waits for user input
… but with 1.3.1 and the modified evmap this will introduce a hard shutdown. I feel this is the correct behaviour but in example all people using a Logitech Harmony and the Logitech’s Hama MCE Remote profile with their Harmony will wonder why their OSMC device is now shutdowning whenever they use the power button on the Harmony.
They have to explicitly change the Harmony’s configuration to let the “Hama MCE device always on” which is NOT the default.
I tried to replace KEY_POWER by system input event KEY_S … but this is ignored.
I’ll be creating a new PR to get things squared away, so would like to get things right for both our remotes in that PR.
I’ll make this change in the new PR I’m working on.
I currently remap this (and a couple of other buttons) using a combination of the kodi Lircmap.xml and remote.xml files. KEY_WWW doesn’t do anything by default in kodi, so happy to make this change. I can easily adjust my Lircmap.xml accordingly to accommodate.
I think this the the best we can do. The button name (e.g. KEY_POWER) comes out of Lirc and gets mapped by kodi using the linux-input-layer section in Lircmap.xml:
Unfortunately, there is no Lirc button name we can map to in that section for sleep.
However, it’s possible for the user to remap it to sleep using a keymap, and I think there’s even an addon which allows you to do this through a nice GUI rather than editing files via SSH. I can send more details on this if you’re struggling.
I built my changes ontop of a very old version of 03_05a4_9881.evmap which was already in the osmc repository but wasn’t being used as there was no entry in the rules.d file to get the remote recognised by Lirc. I think the file originally came from the Lirc google project. You need to bear in mind that Lirc is used for other applications, not just Kodi.
The changes are now built and in the staging repository. I’ve also moved all of the evmaps upstream; as it doesn’t make sense, and is confusing, to have some in the OSMC repository and some in the eventlircd repository.
The Hama MCE Remote Control does not behave the same on Pi3 v18 and Vero 4k v17:
pi3 v18 - all OK
Vero 4k v17:
– a lot of buttons do not get a mouse click sound
– alt+meta+KEY_ENTER (the green START button on the control) has no function at all (Pi3 v18 it is the KEY_MENU or context button)
– the asterix button behave like the info key
– the info button behaves like the menu/context key
– the power button brings the shtudown menu instead of a real power down, this behaviour was on pi3 v18 with the 1.3.0 version
– the hash key has no function (Pi3 v18 it’s the teletext while watching TV channels)
sam_nazarko just updated my Vero 4k to v18: All issues mentioned above with the Hama MCE Remote Control on Vero4k compared to Pi3 v18 remain.
All problems seem to be introduced if the RF USB dongle for the original OSMC remote and Hama MCE Remote Control IR USB receiver are connected the same.