Setting this to confirmed since the remote definition differs from the sort-of-upstream lirc-remotes.
Basically this is a Kodi bug since Kodi (as the only major client) does not respect the mappings done by lircrc but instead reads the raw codes from lircd. One of the purposes of lircrc is to handle problems like this, and so it does - when used.
Since re-mapping this key according to the patch would break configurations for other users which have handled this using .lircrc I'd recommend closing this bug as wontfix.
Someone should file a bug against Kodi for bad behaviour. It's too late to skip the raw reads from lircd, but adding an option to use lircrc is IMHO the right path. Kodi does some mapping, but lircrc is more than mappings: modes, repeat suppression, long keypresses and so on.
Setting this to confirmed since the remote definition differs from the sort-of-upstream lirc-remotes.
Basically this is a Kodi bug since Kodi (as the only major client) does not respect the mappings done by lircrc but instead reads the raw codes from lircd. One of the purposes of lircrc is to handle problems like this, and so it does - when used.
Since re-mapping this key according to the patch would break configurations for other users which have handled this using .lircrc I'd recommend closing this bug as wontfix.
Someone should file a bug against Kodi for bad behaviour. It's too late to skip the raw reads from lircd, but adding an option to use lircrc is IMHO the right path. Kodi does some mapping, but lircrc is more than mappings: modes, repeat suppression, long keypresses and so on.