Remove LIRC configuration

I’m sorry if there is any other topics regarding this, but I couldn’t find anywhere.
I was having problems configuring my remote (old samsung remote) via the user interface and everything I tried didn’t work. Finally I found a solution using my own config and running ir-keytable on startup by adding this on rc.local:

/usr/bin/ir-keytable -c -p nec -w /etc/rc_keymaps/samsung

The problem I’m having now is that OSMC is apparently doing something after rc.local runs and my config is not being used. So my question is:
Is there a way to disable this behaviour and let my rc.local take care of the remote configuration?

I’d suggest checking ir-keytable status after boot and seeing if your keymap is actually overriden

Thanks for the suggestion. It seems I was wrong, it is not being overridden.

Then my question changes a bit:
Why does the remote only work after typing the command mentioned previously in the terminal and not when it starts?

Because that ir-keytable command isn’t persistent across reboots.

I know it’s not. That’s why I added it in rc.local.
Isn’t it supposed to be re-configured automatically then if it runs during every boot?

Not to my knowledge.

Device Tree can inform the kernel of what remote to expect (i.e. protocol) and sometimes a keymap; but usually rc.local or some start script is used to inform the kernel of the profile to use.

@dbmandrake and I were discussing fully moving away from LIRC to ir-keytable in the near future. Part of this would be including a systemd unit which would activate the chosen ir-keytable profile selected in My OSMC on boot.