eISYIR not receiving remote signals reliably

[lionheartkc]

I followed the instructions here (https://www.universal-devices.com/eisyir-flirc/) and was able to properly setup the FLIRC, but when I plugged it into the eISY and sent IR signals to it, it took repeated presses of any button for it to register (even with the remote right next to the unit). After quite a significant amount of time, I was able to get all 12 buttons I wanted registered, and I have tested a few to see that they do work, but it can take a significant amount of repetitive button pressing for it to trigger, sometimes taking long enough that I give up. Obviously, that is not performing at a functional level.

I'm using a Nevo SL remote (yes, I've kept 2 of them limping along). The FLICR has no issue reading signals from it when I have it plugged into my PC docking station, reading them instantly, every time. For some reason, however, they are not reliably translating to triggers in the eISY.

Any advice on making it work would be greatly appreciated. IR is an important part of my home control system, so not having it is a significant issue.

[firstone]

On 12/10/2023 at 10:12 PM, lionheartkc said:

I followed the instructions here (https://www.universal-devices.com/eisyir-flirc/) and was able to properly setup the FLIRC, but when I plugged it into the eISY and sent IR signals to it, it took repeated presses of any button for it to register (even with the remote right next to the unit). After quite a significant amount of time, I was able to get all 12 buttons I wanted registered, and I have tested a few to see that they do work, but it can take a significant amount of repetitive button pressing for it to trigger, sometimes taking long enough that I give up. Obviously, that is not performing at a functional level.

I'm using a Nevo SL remote (yes, I've kept 2 of them limping along). The FLICR has no issue reading signals from it when I have it plugged into my PC docking station, reading them instantly, every time. For some reason, however, they are not reliably translating to triggers in the eISY.

Any advice on making it work would be greatly appreciated. IR is an important part of my home control system, so not having it is a significant issue.

Number one thing to try is to use another simpler remote - like TV remote, and see if this clear things up. Some code sets do not send key press finish events and it breaks things. On PC it reacts but doesn't necessarily send all correct signals. 

 

Next step, if you're comfortable doing it, I can give you a test program in python that you can run on a pc or eisy. That will show exact signals your remote is sending.

[lionheartkc]

On 12/12/2023 at 9:49 PM, firstone said:

Number one thing to try is to use another simpler remote - like TV remote, and see if this clear things up. Some code sets do not send key press finish events and it breaks things. On PC it reacts but doesn't necessarily send all correct signals. 

 

Next step, if you're comfortable doing it, I can give you a test program in python that you can run on a pc or eisy. That will show exact signals your remote is sending.

Thanks @firstone.

I'll play with a different remote and see what happens. It will be very disappointing if the Nevo is the issue. I've yet to find a universal remote that I like as much as their design.

As for the python script... I'm not a developer, per say (I write HTML, CSS, some java, coldfusion back in the day...), but I can try to muddle through it if it will help fix the issue.

[firstone]

On 12/15/2023 at 3:48 PM, lionheartkc said:

Thanks @firstone.

I'll play with a different remote and see what happens. It will be very disappointing if the Nevo is the issue. I've yet to find a universal remote that I like as much as their design.

As for the python script... I'm not a developer, per say (I write HTML, CSS, some java, coldfusion back in the day...), but I can try to muddle through it if it will help fix the issue.

If it's universal remote, then it's not a function of a remote but rather specific code set you're using. Changing to different code set should fix things.

If you're comfortable ssh-ing into eisy and running python script, you will be ok.

[lionheartkc]

5 hours ago, firstone said:

If it's universal remote, then it's not a function of a remote but rather specific code set you're using. Changing to different code set should fix things.

If you're comfortable ssh-ing into eisy and running python script, you will be ok.

That's convenient because with the Nevo I can literally make each button whatever code I want it to be, so maybe the best move would be to find a code set I know works well with the eISY. 

Any idea where I might find that?

[gzahar]

3 hours ago, lionheartkc said:

That's convenient because with the Nevo I can literally make each button whatever code I want it to be, so maybe the best move would be to find a code set I know works well with the eISY. 

Any idea where I might find that?

Most Philips devices should use standard RC5 codes.  I would start there.

[lionheartkc]

On 12/18/2023 at 8:00 PM, gzahar said:

Most Philips devices should use standard RC5 codes.  I would start there.

Thanks!

[firstone]

On 12/18/2023 at 5:24 PM, lionheartkc said:

That's convenient because with the Nevo I can literally make each button whatever code I want it to be, so maybe the best move would be to find a code set I know works well with the eISY. 

Any idea where I might find that?

Before you start playing around with code sets, I'd still recommend trying some tv remote  - just to see if it fixes things. Also, maybe try rebooting eisy just in case. If you haven't rebooted since you've installed, it could be permissions issue that would also cause lost signals.

[lionheartkc]

On 12/20/2023 at 8:25 PM, firstone said:

Before you start playing around with code sets, I'd still recommend trying some tv remote  - just to see if it fixes things. Also, maybe try rebooting eisy just in case. If you haven't rebooted since you've installed, it could be permissions issue that would also cause lost signals.

Ok.. I've now tried my Nevo, a Vizio remote and a Denon remote and I'm getting the same result. Everything is reading consistently when the FLIRC is plugged into my computer for programming, but when I move it to the eISY it takes a large and inconsistent number of button presses for it to register... if it ever does. So far I've been able to get it to register 2 buttons from the Vizio and 1 from the Denon, and had one of the Vizio buttons actually record a press after it was registered.

I have tried:

1. Installing the ISY FLIRC config created by gzahar (my Nevo mapped perfectly to it when plugged into my computer, triggering IR_001-IR_012)  
2. Plugging the FLIRC into all 3 ports on the eISY
3. Uninstalling and reinstalling the eISY IR Node Server
4. Updating the eISY
5. Rebooting the eISY multiple times

At this point, I'm at a loss. The only thing I haven't done is buy the node server to see if there is a difference between the trial and the purchased version since I don't want to pay for it if I can't get it working.

Edited December 29, 2023 by lionheartkc

[lionheartkc]

I'm not sure if this will help in the diagnosis, but here is the event viewer log as I repeatedly push a button on the remote about once a second...

You'll see that it finally registers after 3.5 minutes (note: this was the first registration of that button).

The error log during that same period has this one anomaly about 11 seconds before the IR registers

[lionheartkc]

Also, here is a video of the FLIRC app reading my remote sending the codes in gzahar's configuration (note... the standard Windows video capture is less than quality. I pushed each button 3 times and it showed a clean registration 3 times except for a hiccup on F when I caught it a 4th time). this shows that the connection between the remote and the FLIRC is solid, and the codes in the FLIRC are the ones gzahar uses, so the issue has to be the eISY reading the signals from the FLIRC.

Ideas?

Edited December 29, 2023 by lionheartkc

[firstone]

On 12/22/2023 at 11:35 AM, lionheartkc said:

At this point, I'm at a loss. The only thing I haven't done is buy the node server to see if there is a difference between the trial and the purchased version since I don't want to pay for it if I can't get it working.

Are you capable to ssh-ing into eisy and running commands? I can PM you test program. You're a second person having this issue - the only thing I'm thinking about is that Flirc changed firmware or hardware somehow and it doesn't function as expected.

[lionheartkc]

On 1/2/2024 at 9:57 PM, firstone said:

Are you capable to ssh-ing into eisy and running commands? I can PM you test program. You're a second person having this issue - the only thing I'm thinking about is that Flirc changed firmware or hardware somehow and it doesn't function as expected.

I never have, but I'm pretty technical, so I'm sure I can figure it out.

And my trial of the node expired, so there's that too.

Edited January 10 by lionheartkc

[Scott MS]

Just finished setting up Eisy and FLIRC and seeing some delays and some scenes turning on and then immediately turning off.  I upgrade firmware on the FLIRC once installed.

Edited January 12 by Scott MS

[gzahar]

8 hours ago, Scott MS said:

Just finished setting up Eisy and FLIRC and seeing some delays and some scenes turning on and then immediately turning off.  I upgrade firmware on the FLIRC once installed.

Post your program that is controlling the scene(s).

[firstone]

On 1/6/2024 at 7:05 PM, lionheartkc said:

I never have, but I'm pretty technical, so I'm sure I can figure it out.

And my trial of the node expired, so there's that too.

Test program is separate from node server. We can use it to rule out remote code set issues, communication issues, etc. Basically if test program will work, node server will also work. So if you still want to give it a shot, PM me.

[lionheartkc]

Update for anyone checking this thread. Firstone has found that my issue appears to be due to the FLIRC conflicting with the eisy connecting via Serial PLMs. He's working on determining what options there might be for a fix.

[lionheartkc]

Another update for followers. Firstone further determined that the root of the issue is line noise from the eisy power supply. I reached out to UD and they acknowledged the issue and said they were working on a solution to be delivered in around 2 weeks. That was 2 weeks ago, so I'm hoping to hear something soon.