Not all IR commands recieved

[AceRoehrborn]

I am having an issue with inconsistent IR commands. 

It seems like about every other command/button press is received by eISY.  Often I press a button on the remote and nothing happens sometimes it takes another press or two for the lights to respond.  Other times it seems like it takes a few presses for the lights to respond.
If I look at the event viewer in Admin Console I see the following results when I get a successful button press. 

The next button press (of the same button on my remote) results in no events in the admin console event viewer.  The following button press gets the same results below.  It seems like "about" every other button press is unsuccessful.  If I alternate between buttons it seems better but not perfect.

I am using a harmony remote with a hub, with the old ISY994I Ir command set.

I just updated to the latest eisyir Version (1.3.1).  But, I had this issue before upgrading as well. 

I am pretty confident my IR commands are successfully reaching the flirc consistently.  It seems like there is some sort of reset the eISYIR needs in order to receive another command and pass it to the eisy.

Any recommendations to solve this would be appreciated.

 

Additional questions:

I don't think these are related to my IR issue but kind of just for my knowledge.

1)What do the Short poll and long poll values do?  Not sure if any adjustments here would help me?

2)What are the current default recommended values for:

Idle threshold:

Press Threshold:

Release Threshold:

3) In my event viewer it appears that Press=GV1, Held=GV2, Release=GV3.  Not sure if that is correct? 

I can't seem to find a combination of timing that will show all three statuses on one button push.  I have built all my programs to activate on "held" status and am currently using these values:

Idle:800

Press:250

Release:250

It did trip me up when I first set this up that I could not trigger a program based on pressed (GV1).  About the only timing I can find that makes Pressed/GV1 appear is to make the press significantly longer than released. Example: Idle:800, Press:600, Release 50.  However in the event viewer only GV1/Pressed state ever appears, GV2/3 (held/released) never appear.

Again, this is just for my knowledge.  As long as any code gets passed to eisy successfully and consistently I can adjust my programs as necessary for whatever status I receive.

Thank you for any help or info you can provide.

 

Edited Sunday at 06:06 PM by AceRoehrborn

[firstone]

Default timings are 500, 500, 50. Long poll and short poll are not used.

 

To troubleshoot reliability, put plug in into Debug mode, do 5 quick presses, then 5 press and hold. Send log package to me, I will take a look.

[gdavis]

First, many thanks to @firstone for this plugin.  eISYIR has the honor of being in slot #1 on my eisy.

I have the same setup as you, a Harmony Elite remote and hub, with one of the ISY994 IR command sets installed and had the same issue.

After doing some research on the FLIRC forums, I found this is a common issue where remotes will alternate two (or more) different codes for the same button.  For example, first button press sends code X, second press send code Y, and then repeats.  This is apparently the case with the Harmony ISY994 command set used.

The fix for me was to record both codes for each letter (key) on the FLIRC keyboard device by doing two record operations using the same FLIRC key and the same remote button, thereby sending both codes to FLIRC.  (FLIRC can hold multiple codes for each key.)  I have had zero issues with eISYIR since.  

I did this set up early on, before anyone had posted the FLIRC command set files that can just be uploaded.  Others have had success with that method.

Hope this helps.

-George

[CoolToys]

@gdavis is correct, since Harmony was designed to work with any system they were programmed to allow for Phillips toggle codes.  This was Phillips solution to discrete codes, saving a separate Power On and Power Off button on the remote among other things.  

Wherever the database came from for the IR codes could be the issue.  The second button press could be blank or some code unknown to the ISY/Eisy.  I have a Request Video Server and had similar issues.  Harmony only programmed the "A" codes, leaving the "B" codes blank, which would do odd things if there were codes on the "B" pages.  The off command for my TV was hiding under the FF command for the request.  So instead of stopping the FF operation it turned off the screen with the second press.  Manually programming (learning) the button twice from the Request remote solved it.

99% of the time Harmony just pasted the A codes in the B page unless the device had discrete A/B Phillips style codes.