Segfault

RPi in idle mode does not draw any power. If it was the only load in your house it wouldn't move your meter.

I fought my problem for a long time, years, erratic response to key presses. I thought distance was the culprit, although 12 ft shouldn't be a problem. I used a USB extension to connect Flirc to mitigate this issue. Until I finally found the source of problem - an 8-port network switch. Both the Kodi frontend and the switch are mounted to the wall, about 2 ft apart. Flashing LED-s of switch were the source of "noise" which obviously interfered and saturated my Flirc adapter. After I turned the switch 90 degrees so the LED-s no longer shine into my Kodi frontend the problem was completely gone.

I don't think it is possible without CEC. You may want to get one of those external CEC modules from Pulse Eight.

Actually it works great. Seldom misses a keypress, but who knows why. Perhaps Kodi is to blame.

Thanks. Let me refine my question. I currently have an Intel NUC mounted on the wall next to the TV set. Flirc is plugged in and "looking down". Could I benefit from one of those 90 degrees USB adapters? Then the dongle would face the remote. Isn't it always better to have more straight signal and less reflected signal?

Digital things just seem to work, or not. However, getting clear signal is still important, weak signal can cause erroneous reception. Thus, my question is what does the sensitivity diagram look like? In other words, how to position the sensor to get the best signal from remote?

No problem with me, I downloaded and installed it by hand. Just wanted to give you heads up.

What is the latest location? Anyhow, if I'm using old repo I shouldn't get any updates, correct? But I do, and install fails with download error.

I'm using Mint to run Flirc software, latest upgrades seem to have wrong path for deb download.

OK, I found there is a command line utility in your software package, I thought maybe I can run it in my Kodi box to debug the issue. No go. My Kodi box has no 32-bit support and the executable is 32-bit. Amen. The only OS I can run it on is my VBox Linux Mint. Every freakin' flash utility I've used in my life offers old firmware backup in case the new one has a problem. This is the first case I experience downgrading the firmware is literally denied. Your software, your policies. For me it is time to look for a different solution, methinks. Getting frustrated, yes, sorry.

Can I have older working firmware back, please? Do you have #flirc IRC channel?

No telling. I have just one Kodi box currently. My home was flooded last year, I lost all my frontends. My desktop has no Kodi installed. I have Linux Mint in VirtualBox to support my friends who use it, I have your software installed in Mint. Desktop itself is Gentoo. All I can tell it worked alright until I upgraded the firmware. :( Of course, there is a possibility it is just a coincidence and something happened to my remote same time. But the odds are very low. Please let me know if there is a way to debug it using my existing equipment and I'll do it. I have to admit the problem is quite irritating right now.

Alright, you lost me. Do you want me to use your software to log in my Kodi box? It cannot be done, I do not have any Window Managers installed, just Kodi running on Xorg. Additionally, my Kodi box is running on Gentoo, installing your software on Gentoo is not easy. I think I tried once but gave up.

My remote is described earlier in this thread. Not sure how you exactly want me to get the log. I plugged it into my desktop and pressed a few keys on remote, mostly the keys that give me trouble. Some I need to press twice sometimes (not always) and some - like arrow down seem to send two commands in one keypress, but again, not always. It was working much better with previous firmware. Normally I'm using it with an Intel NUC, Kodi. The debug log is attached. my_flirc_config

Thanks, here it is. my_flirc_config