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.

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.

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.

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? Flirc v3.27.9 - Connected 2023-12-29 12-53-41.mp4

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

FINALLY! The program worked. Rebuilding it did the trick.

It is the new program, which is the same as the old program. I've not changed the time to test it, because I don't want to throw another variable in the mix, so we'll just have to wait until midnight to see if rebuilding it does the trick. Yes, unfortunately, because they are outdoor lights, they are on GFCI circuits. Nothing can really be done about that. Still, I've been controlling this same setup with my ISY 994 for years with no issues. I have been very careful to time my programs so they don't fire on top of each other. I'll let everyone know if the rewrite did the trick.

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: Installing the ISY FLIRC config created by gzahar (my Nevo mapped perfectly to it when plugged into my computer, triggering IR_001-IR_012) Plugging the FLIRC into all 3 ports on the eISY Uninstalling and reinstalling the eISY IR Node Server Updating the eISY 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.

Here's the program to shut them off. I added a notification, yesterday. It didn't work, so I know the program wasn't executing at all. Hopefully rebuilding it, today, will fix that.

My next move was to just rebuild the programs from scratch, which I just did since when they didn't work last night, I just manually triggered the "then" and it worked. Fingers crossed that does the trick. Thank you. This is some very useful information.

I thought about line noise, maybe even from the LEDs plugged into the switches, which would explain on working and off not working, but I can't explain why manual switching works from the interface if that is the issue.

Yes. Restore Device ran for both with no issues. I can also sit here and turn the devices on and off in the interface all day long and it works perfectly, so it's not a communication issue. The PLM and ISY are plugged into outlets that are around 4' apart. I know it's not the program for a couple of reasons. First, it turns the indoor lights off. Second, it's the same program that worked fine before I switched the controller. That being said, I've messed with it a lot to try to make it work. I just tried setting the retries. One of the devices throws a "request failed" error when I select a number of retries from the dropdown, but then appears to work when I hit done. I'll note that I tried the Advanced PLM settings on other switches, both plug and wired, just to see, and every single one throws that "request failed" error. The other outdoor switch said that it doesn't support PLM settings, so it's a little long in the tooth.

Just as an update, I've tried everything mentioned above and none of it has made a difference. The programs are still failing to turn off the lights, while manual control is working perfectly. I have to say that this is particularly frustrating considering the only variable that has changed in the whole system is moving from my old ISY 994 to the eISY. It all worked before that change.

Thank you. I just restored both to see if that helps.

Thank you. I'm trying a new program now that turns off the scene, then waits, turns off one switch, waits, and turns off the second switch. Fingers crossed that will do the trick.

The initial program uses scenes. The test 10 minutes later is individual.

I just moved to the eISY from a ISY 944. I have programs set to turn on and off Christmas lights using Insteon plug-in switches... several indoor and 2 outdoor. They worked nearly flawlessly on the 944. On the eISY, however, everyday at sunset, without fail, all of the lights turn on, but everyday at midnight, the indoor lights turn off but the outdoor lights stay on. I even have programs set to run 10 minutes later to check if they are off and, if not, turn them off. Those also always fail to turn them off. If, however I go to the mobile interface and manually tell them to turn off, they do, every time. I'm at a loss as to why they come on programmatically but will only shut off manually. Does anyone have any ideas for fixing this issue? Thanks.

Thanks!

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?

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.

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.