Caver01

I just got a flirc 2. Using it on a PI 3 running Kodi 18. I have successfully mapped buttons that are working in Raspbian Pixel desktop. They also seem to work in Kodi—except ENTER. Nothing I map to ENTER in the FLIRC GUI will send an ENTER command to Kodi correctly. it is crazy because I can see ENTER working fine in a terminal window. I open a command prompt, press my enter key on my remote, FLIRC receives this and lo and behold, I see the command prompt go to a new line. By that account it seems to work. So I launch Kodi and my other nav buttons work, but ENTER does not. Yet, I know Kodi is ready for ENTER because I have a physical keyboard connected for testing and I can press enter on it and it works in Kodi. i have tried disabling the built in profiles in the GUI, I have remapped other remote buttons to enter, tried it on the full keyboard module, I even tried loading the Kodi key mapper add-on to attempt a workaround, but even this does not work. I can map the button press with Kodi key mapper (it registers receiving it) but it does not work when I try to use it. I am stuck. What is going on with the ENTER key in Kodi 18 on the Pi? This is useless if I cannot get ENTER to work. Other than that, it is really cool! <EDIT> Well, I think I may have solved my own problem here. The IR command I was issuing for the ENTER key was getting sent as a 3x repeat. FLIRC must have been recording this in some odd manner and when issuing the ENTER, it would sometimes rapid-fire a string of them, four in a row for example. Changing the IR repeat to 1, re-recording/learning the command seems to have fixed the problem. At least I am able to generate ENTER commands in Kodi now. I have some reconfiguring as a decide how to orient IR blasters etc, but I think my issue was the multiple sends, the recorded result, and further multiplying the effect when re-sending the command once learned (Kodi was often getting a contextual menu "c" command instead of enter, but BASH would show four enters in a row most cases).