aLf

Figured it out. I think along with the many "glitches" I've experienced in the transition from 994 to eISY, I think that some of the Scenes also were corrupted in the move. I deleted this particular scene and rebuilt it and just like that it works. Moral of my story is a complete audit of all the remaining scenes and programs. This whole thing started with the backlighting not responding. That issue required each and every switch needing to be factory reset, deleted from eISY and then re-added back in. After that the backlighting adjustments worked perfect. I'm appreciative that everything works now, or will as soon as I get through the rest. I'm thrilled with my new eISY, and it's worth the minor inconvenience of these issues.

Let me try and elaborate. I have a scene, "NIGHT" which I push button "F" and the scene has a half dozen SWL's in it. Some dimmers, some just switches. I have set the ramp and % brightness in the scene under each unit. I push the button and they all go to rogue settings. In addition I have a dimmer mated with a KPL button that when the button is pushed would likely go to 33%. It goes full bright even though I have the level set to 33%. I know I'm missing something simple

I've had a boatload of issues with backlighting and today one thing led to another and many switches needed to be reset. I reset them to factory and then reloaded them into the eisy. A single lone switch was Ok , but scenes were all in need of reprogramming. I got the main backbone done, then I noticed that the scenes when triggered by a KPL button were not setting SWL's t the proper level. Can someone tell me how to program the ramp rates and brightness for each SWL in a scene. Also I thought by simply entering ramp/brightness in a SWL would tell the switch how to perform when the switch rather than a KPL button was pushed.

For what it's worth - I posted on the ISY site as well...

I started with UD back in the early 2000's with a an ISY-26. I think I paid <$200 for it. It served me very well for better than a dozen years. I then moved into the 994, it too served well only and until the mail notification stopped (not due to anything UD did wrong). The 994 cos around $200. When it became apparent that the 994 was going to be sidelined - I procrastinated for months. I finally, even though advised by UD to just hang on to it and give up on the email notifications, and knowing of possible issues I might have integrating my Schlage locks into a new eisy, I bought a new eisy for ~ $400 something. I even sold the old 994 for $100 to a guy who needed it for what it was! The transition from 994 to eisy could not have gone better. No issues - and I mean NO ISSUES. The locks were seamless and other than a few switch(s) that have had to be factory reset and restored my system has been 100%. Granted, I don't have a huge setup, < 50 total switches. My point being that I feel that UD (and more importantly Michel) are worth every penny I ever paid them. Their product works as advertised and support is second to no one. I will never utilize the eisy for 5% of its capability, but that's OK. I like stuff that works and my ISY(s) have always done that.

Thanks Indy. I'm on it

Thanks Dennis

A few weeks have passed and this morning I noticed two more switches are full bright back light all night. I'll remedy the same way, but not sure why (or how) they are changing. Any ideas? It has to be the new eisy and firware. The backlighting was rock solid for many years on the 994. Not a problem, but just extra work.

Could someone provide a link to directions on how to add a plugin and then configure it for use?

They told me that the "hub" would run ~ $210. Sound about right? Also, could you post a link to how to install an eisy plugin. I searched and can't find the step by step. This will be my first, so I'll be a pro after the HD. Thanks

Today I installed my first 4 HD blinds that utilize Gen 3. I wanted to wait until they were installed to see exactly what the HD app would provide and then ask questions. What has anyone using the eisy add-on do through eisy that benefits from the integration? The HD app allows for schedules to run locally so other than schedules how has anyone used it to tie into Insteon, etc.? I was told the built in schedules would not run unless my phoe or ipad were not present. I have an ipad that stays home always. Thanks for the insight.

24 hours in and the programs are all working as should. I'm thrilled that the internal memory was not the issue. I'm no expert, but I'm guessing that this was a glitch in the backup used from 994 to eisy and some sort of bug related to the backlighting. In the end, removing and factory reset was the best answer. All the switches involved were reset the same way and all are working as advertised. Thanks to al for your help!

24 hours in and the programs are all working as should. I'm thrilled that the internal memory was not the issue. I'm no expert, but I'm guessing that this was a glitch in the backup used from 994 to eisy and some sort of bug related to the backlighting. In the end, removing and factory reset was the best answer. All the switches involved were reset the same way and all are working as advertised. Thanks to al for your help!

I just got it back online and will monitor it for 24 hours through the dim/brighten sequence tonight.

No, I don't leave I open normally. Forgot it after I go it working the first time. It was open ~ 1:30. It will not re-register no matter what I try. Tried re-booting eisy - no joy.

Came back after lunch and the RED "!" was back on the switch. Did a repeat of the original reset and now when I go back to add it back in, I get "Connot determine Insteon Engine". Now what?

I totally reset to factory, removed from eisy, reinstalled, named it back and re-included it into the scene. I now have control of the backlight via the iox app. I'll see tonight if eisy does the program successfully. I suspect problem fixed.

I totally reset to factory, removed from eisy, reinstalled, named it back and re-included it into the scene. I now have control of the backlight via the iox app. I'll see tonight if eisy does the program successfully. I suspect problem fixed.

As someone on the Insteon side suggested. I pulled the button out and reste until the beep started and stopped. Then went into iox and "restore device". I did this and now the switch returns this: "Could not read config file" - "[./FILES/CONF/3B DF FC.REC]" So the switch is now unresponsive. What is the best course to take removing it now and reinstalling it? It is only scened to a mate at the top of a staircase and is in the dim program.

I did this and now the switch is not seen and when I try to "restore device", I get an error message "Could not read config file" - "[./FILES/CONF/3B DF FC.REC]"

Refresh my "memory" as to how to safely remove - factory reset- and reinstall it. It's been a long time. Thx.

This is what the mate to it that still changes shows when I send a command: Sun 05/10/2026 09:30:18 AM : Create REST U7 [/rest/status/3B%20D7%2097%201] Sun 05/10/2026 09:30:24 AM : Create REST U7 [/rest/nodes/3B%20D7%2097%201/cmd/BL/100/51] Sun 05/10/2026 09:30:24 AM : U7 Rest: submitCmd([3B D7 97 1],[BL],[<NULL>]) Sun 05/10/2026 09:30:24 AM : [All ] Writing 1 bytes to devices Sun 05/10/2026 09:30:24 AM : [3B D7 97 1 ] Memory : Write dbAddr=0x0264 [7F] cmd1=0x2E cmd2=0x00 Sun 05/10/2026 09:30:24 AM : [INST-TX-I2CS] 02 62 3B D7 97 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C Sun 05/10/2026 09:30:24 AM : [INST-ACK ] 02 62 3B.D7.97 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C 06 (00) Sun 05/10/2026 09:30:24 AM : [INST-SRX ] 02 50 3B.D7.97 71.18.CA 2F 2E 00 (00) Sun 05/10/2026 09:30:24 AM : [Std-Direct Ack] 3B.D7.97-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Yes via the UD app. Use the "Backlight" option and select 0 or 100% Not really sure how you'd select backlighting at the switch?

Sun 05/10/2026 09:26:30 AM : U7 Rest: submitCmd([3B DF FC 1],[BL],[<NULL>]) Sun 05/10/2026 09:26:30 AM : DB: Cannot load ./FILES/CONF/3BDFFC.REC Sun 05/10/2026 09:26:30 AM : [All ] Writing 0 bytes to devices This is what I received after asking it to go low light. Sun 05/10/2026 09:28:20 AM : Create REST U7 [/rest/nodes/3B%20DF%20FC%201/cmd/BL/0/51] Sun 05/10/2026 09:28:20 AM : U7 Rest: submitCmd([3B DF FC 1],[BL],[<NULL>]) Sun 05/10/2026 09:28:20 AM : DB: Cannot load ./FILES/CONF/3BDFFC.REC Sun 05/10/2026 09:28:20 AM : [All ] Writing 0 bytes to devices This is what the communication event showed

I posted on the eisy forum as I thought it might be an issue with it. Two folks advised me that there is a "memory limit" on these switches that will cause them to stop certain functions after "1000 - 10,000" cycles. Her's my issue - I just converted from a 994 to eisy. Shortly after, three of my 2477S switches stopped dimming the back light on a program I've had for years (dozens of others still dim at sunset and go 100% at sunrise). All of a sudden after the switchover to eisy I noticed these switches are full bright at night. I use the UD app in conjunction with the eisy and have gone into each switch and tried to manually adjust the back light with no response from the app or switch. They seem locked at 100%. Is there really a limit on these? Is there a way to reset that memory to allow functionality again? There is NO othe abnormal behavior from the switch. If this truly is a built in planned obsolescence, I will begin to see others show the same trait! The entire house is coming up on 10 years old this summer and I've had the program running from day 1, so I'd estimate that they have dimmed 3,500 times and been asked to go back to bright the same.

Can the memory be reset?