aLf

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?

Upgraded from 994 to eisy recently. I have noted three Insteon 2477S switches with an issue. They along with any other Insteon switches are in a program that takes their "backlight" to 0 between sunset and sunrise, and back to 100% during daylight. All others are still doing what they should, but these three stay at 100% (quite bright). I have gone in and tried to manually change the backlight up or down and they refuse. I've waited until during the day to manually go in and try - same result - they will not move. Any suggestions? I'm not sure if this happened during the move into eisy, or just a coincidence.

I was able to experiment around with the AXIS camera settings and came up with a workable solution to the mess they made with Camera Station last year. If anyone wants the information let me know and I'll do a separate post. I'm amazed after just a week all the issues I had with my 994 are long gone (as is the 994). I'm so glad I was able to transition so easy.

Thanks everyone. I'll work on it.

Good morning. I have just upgraded from an old 994 to eisy. One of my needs is to bring the MyQ the eisy. I have two MyQ doors and would like to query the door positions in eisy for programs. Could someone give me a detailed instruction as to how to make this work. Other than this query, is there any other creative things to do with MyQ in eisy? I have not added any add-ons to the eiesy yet, so I need instructions on how to ad an add-on too.

Good morning. I have just upgraded from an old 994 to eisy. One of my needs is to bring the Hunter Douglas blinds to the eisy. I just ordered 4 HD blinds to get started, I was told I don't need to get a HD hub and that their (HD's app) would control them from my phone. What I'm hoping to do is to use your add-on to control the blinds from eisy. Could someone give me a detailed instruction as to how to make this work. I have not added any add-ons to the eiesy yet, so I need instructions on how to ad an add-on too.

Also, after many years of struggle with control of my AXIS cameras (turning motion on/off with ISY), I now have them working again too. Took just a little reprogramming the Network settings from the new eisy and sure enough they work again. This new eisy is the best thing.

Since the change over, every time I log in, I get the "Device Discovery" box saying "Add a device to the Z-wave network" box shows up. Is there a way to not have that happen? If I hit "Cancel" nothing happens. I have to "X" out to remove the box.

Thanks Guy

I just completed the transition from my old 994 to a new eisy. I have two Schlage locks which I was told would be problematic. They are older Schlage as well. My start-up in the eisy went well, the backup from my 994 updated beautifully. I then went to work on the Schlage locks. As per Schlage customer service, they mention that many ZWave folks have issues in getting new third party's like ISY to see them and that the solution is very simple. Their procedure is as follows: 1) Use the "Remove a Zwave device" for any and all previously used devices. 2) Factory reset the device removing all previously used data like codes, etc. 3) "Add a ZWave device" as the eisy calls for. The key here I believe was to factory reset the locks. I initially tried to just add them and got a continuous "writing" within eisy. After the factory reset and second removal from eisy, the locks came on line perfect. The only other bit of work was re-writing the programs I use to look for the new devices, ZYxxx rather than the 994's naming of ZWxxx. All is well and as of now I have zero issues. That said, my firmware is 6.0.4 and I see 6.0.5 is available. Tech said I should update it. The 994 had a dedicated upgrade option on the main page. I don't see that on the new eisy. Can someone give me directions or steer me toward the procedures to update this? I am a bit concerned to do it as there are so many temperamental issues associated with ZWave and eisy. Lastly, I would like to add the Hunter Douglas blind app to eisy. Has anyone done that and as it's my first add-on, how do I go about doing that? As a side question - Is there a way to control older Gen1 HD blinds, or just the new models? Thanks.

Just got a new unit ordered, they came in faster than expected. Unfortunately, the Z-Matter is still out of stock. When the new ISY arrives, should I wait to upgrade, or is the Z-Matter plug and play so as to pick up what it needs from the programs?

My programs and scenes are very simple ( I think), so that said, I guess I'll just backup and move to restore the eISY when I get it. Anything not working then can just be rebuilt. I'll get the eISY, the Z-Matter and a serial PLM kit. The Schlage lock program is the toughest thing I've got (multiple scenes and programs to make the keypad lights work proper), maybe someone will have a better way to skin that cat when I get there. Thanks for all the insight.