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.

I skimmed the other tread and it seems more than coincidence that this happened after you migrated.

I didn't see that you tried the factory reset and restore device? For switches that old, losing its memory marbles is "a thing" due to running a long time or electrical events like brown/black outs, I've had luck with this wokring on my older, long time running insteon devices.

Edited Sunday at 02:30 PM2 days by paulbates

23 minutes ago, paulbates said:

I didn't see that you tried the factory reset and restore device?

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

Don't remove! This is easy to do:

• Pull the tab on the bottom out

• Push all the way in for ~10 seconds and beeping starts or it stops

  • This part can be different by switch, but waiting ~10 seconds until a sound change generally works

• Go to iox, right click on the device and pick restore device

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]"

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.

21 minutes ago, aLf said:

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]"

I think you recently migrated from a 994?. That's a sign that the SD card in the 994 you came from was failing and the file was damaged. In that case symptoms like these are plausible, and remove/reset/rebuild is the answer

Glad you got it working.

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?

2 minutes ago, aLf said:

Came back after lunch and the RED "!" was back on the switch.

Are you leaving admin console open 24/7? Don't! It's not meant to be open all the time. Open only when you need to adjust something then close it.

The Red "!" means communication is lost to the device. Could indicate PLM issues. Be sure if you're trying to add it back that you have the correct address or use the auto linking process. Sometimes B/8 D/0 and S/5 can look alike.

Try operating the device in UD Mobile or even in Admin Console (and/or even in eisy_UI). More than likely you're having some noise issues if this just randomly started happening if the PLM is new.

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.

That is a sign of fading away. I've had cases where a device worked fine until I went to manage, like change a scene it was in, and it would beep and not cooperate. I'm guessing it's dying.

You could open the event viewer level 3, exercise it from the switch and then try what ever is failing from iox and post it. There are members that are good are deciphering those that might help validate the dying assertion.

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

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!

20 hours ago, Geddy said:

Are you leaving admin console open 24/7? Don't! It's not meant to be open all the time. Open only when you need to adjust something then close it.

The Red "!" means communication is lost to the device. Could indicate PLM issues. Be sure if you're trying to add it back that you have the correct address or use the auto linking process. Sometimes B/8 D/0 and S/5 can look alike.

Try operating the device in UD Mobile or even in Admin Console (and/or even in eisy_UI). More than likely you're having some noise issues if this just randomly started happening if the PLM is new.

I have to say that it has never been a problem for me to leave the admin console open 24/7. Yes, after a few days it stops working, but I simply close Java via Task Manager and then start it up again. To my knowledge, leaving it open has never affected anything adversely. I like having it open so I can tinker whenever I want.

On 5/11/2026 at 9:46 AM, Ross said:

I have to say that it has never been a problem for me to leave the admin console open 24/7. Yes, after a few days it stops working, but I simply close Java via Task Manager and then start it up again. To my knowledge, leaving it open has never affected anything adversely. I like having it open so I can tinker whenever I want.

I agree. The java admin console has all kinds of bugs in it that cause it to lock-up, have hidden windows, and generally just stop working when you leave it open. But never have I seen it do bad things to eisy/polisy/isy. In the very very old days of windows, ctrl-alt-delete /end program was just a thing you had to do for lots of stuff. But for the last 15 years or so, only with java.