I have been using my Flirc for a month or so and it has worked brilliantly, except...
My problem is double key presses.
My configuration won't help any as I am using a Skippa remote to control an IceBox. What's a Skippa and an Icebox, I hear you say?
The Skippa is a PVR (now dead) that is unique to an Australian company called IceTV that provides a unique EPG service that allows you to set recordings on the PVR from anywhere with cellular service. The IceBox is a later version that is based on a NUC running LIBREelec and Kodi software as well as an IceTV plugin that allows the IceBox to communicate with the IceTV service. The IceBox came with an RF remote out of the box, which didn't suit my setup which uses InfraRed extenders to allow the various entertainment devices to controlled throughout the house. It's all actually more complex than that, but I doubt anyone will make sense of the setup.
My solution to integrate the IceBox into the setup was to record the keys from the Skippa remote to a Flirc and use a plug it into the IceBox.
A key point is that the Skippa remote I am using is not configurable. It is an out of the box remote, i.e. not a programmable device.
As I said it all works brilliantly, except for the double key presses. When I press the '2' button on the remote the IceBox sees '22'.
I immediately recognized the problem. The Flirc was responding to the multiple '2' pulses, that the remote generates with a single press of the key, and pushes out what it receives.
The biggest problem is the Pause/Play button, i.e. a Pause is immediately followed by a Play.
I have researched the issue in the forum and quickly found threads where the problem was discussed, and the solution was to adjust the Interkey delay on the Flirc.
Unfortunately, in the current version (Build 2?) this adjustment of the Interkey Delay is no longer available.
I saw a suggestion to use the Command Line "interkey_delay" command available with "flirc_util.exe", so I hunted around and found out how to do this but got the response "inter-key delay: N/A for current firmware".
Can anyone explain why the Interkey Delay capability has been dropped?
It seems to be such a logical function to have. I also note that every time someone raises interkey delay for Build 2 Flircs, all conversation stops.
This makes no sense to me. I can understand that the function has been withdrawn for some reason, but why not just say so? I have yet to find a thread where the withdrawal has been explained.
Of course, if someone can point me to a solution that would be greatly appreciated, but I have little expectation of one.
