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.

Hope I’m recalling this correctly but some have mentioned that the memory where those settings are stored has a limited life of updates.

Your doing it manually supports this as a possible cause if by manually you mean at the switch.

Edited Saturday at 02:27 PM3 days by hart2hart

Did a quick bit of AI and the storage used for those settings is typically rated at 1.000 to 10,000 update cycles so at twice a day that would be 1.4 years to 10x that time.

I’m careful with AI but maybe not enough this time. Went deeper and got this:

“Insteon switches use EEPROM memory (often SST39VF040 or similar) for settings, with a guaranteed endurance of 100,000 write/erase cycles per sector.

Actual lifespan often exceeds this minimum in practice, as noted in general EEPROM discussions, though exact chip specs for all models aren’t always public.”

Edited Sunday at 01:37 PM2 days by hart2hart
Add and clarify

Can the memory be reset?

@aLf , the phenomena that @hart2hart is referring to is actually "wear out" of the memory location. If this is the case, a reset would not work.

It's always possible that the devices have been "upset" by a power anomaly. A quick power cycle could help.

It's also possible that the devices are not correctly linked after your transition to the EISY. If you could provide a Level 3 Event Viewer capture of the communication when you manually change the backlight we may be able to help diagnose.

The following is a capture from changing one of my 2477S to max backlight [7F] and back to min [00]. Memory location is 0x0264.

Sun 05/10/2026 06:24:44 AM : [All         ] Writing 1 bytes to devices
Sun 05/10/2026 06:24:44 AM : [INST-TX-I2CS] 02 62 1F BE 7A 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Sun 05/10/2026 06:24:44 AM : [INST-ACK    ] 02 62 1F.BE.7A 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
Sun 05/10/2026 06:24:45 AM : [INST-SRX    ] 02 50 1F.BE.7A 53.BC.3A 2F 2F 00           (00)
Sun 05/10/2026 06:24:45 AM : [Std-Direct Ack] 1F.BE.7A-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sun 05/10/2026 06:24:45 AM : [INST-ERX    ] 02 51 1F BE 7A 53 BC 3A 15 2F 00 00 01 0F FF 00 A2 00 53 BC 3A FF 1F 01 B8 
Sun 05/10/2026 06:24:45 AM : [Ext-Direct  ] 1F.BE.7A-->ISY/PLM Group=0, Max Hops=1, Hops Left=1
Sun 05/10/2026 06:24:45 AM : [1F BE 7A 1  ] Memory : Write dbAddr=0x0264 [7F] cmd1=0x2E cmd2=0x00
Sun 05/10/2026 06:24:45 AM : [INST-TX-I2CS] 02 62 1F BE 7A 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C
Sun 05/10/2026 06:24:45 AM : [INST-ACK    ] 02 62 1F.BE.7A 1F 2E 00 00 07 7F 00 00 00 00 00 00 00 00 00 00 4C 06        (00)
Sun 05/10/2026 06:24:46 AM : [INST-SRX    ] 02 50 1F.BE.7A 53.BC.3A 2F 2E 00           (00)
Sun 05/10/2026 06:24:46 AM : [Std-Direct Ack] 1F.BE.7A-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sun 05/10/2026 06:24:46 AM : [All         ] Writing 0 bytes to devices
Sun 05/10/2026 06:25:31 AM : [All         ] Writing 1 bytes to devices
Sun 05/10/2026 06:25:31 AM : [INST-TX-I2CS] 02 62 1F BE 7A 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Sun 05/10/2026 06:25:31 AM : [INST-ACK    ] 02 62 1F.BE.7A 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
Sun 05/10/2026 06:25:31 AM : [INST-SRX    ] 02 50 1F.BE.7A 53.BC.3A 2F 2F 00           (00)
Sun 05/10/2026 06:25:31 AM : [Std-Direct Ack] 1F.BE.7A-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sun 05/10/2026 06:25:31 AM : [INST-ERX    ] 02 51 1F BE 7A 53 BC 3A 11 2F 00 00 01 0F FF 00 A2 00 53 BC 3A FF 1F 01 B8 
Sun 05/10/2026 06:25:31 AM : [Ext-Direct  ] 1F.BE.7A-->ISY/PLM Group=0, Max Hops=1, Hops Left=0
Sun 05/10/2026 06:25:32 AM : [1F BE 7A 1  ] Memory : Write dbAddr=0x0264 [00] cmd1=0x2E cmd2=0x00
Sun 05/10/2026 06:25:32 AM : [INST-TX-I2CS] 02 62 1F BE 7A 1F 2E 00 00 07 00 00 00 00 00 00 00 00 00 00 00 CB
Sun 05/10/2026 06:25:32 AM : [INST-ACK    ] 02 62 1F.BE.7A 1F 2E 00 00 07 00 00 00 00 00 00 00 00 00 00 00 CB 06        (00)
Sun 05/10/2026 06:25:32 AM : [INST-SRX    ] 02 50 1F.BE.7A 53.BC.3A 2F 2E 00           (00)
Sun 05/10/2026 06:25:32 AM : [Std-Direct Ack] 1F.BE.7A-->ISY/PLM Group=0, Max Hops=3, Hops Left=3
Sun 05/10/2026 06:25:32 AM : [All         ] Writing 0 bytes to devices

The EEprom where the data is stored can be written to over 1 million times.

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

Curious, when you said updating manually earlier in the thread, did you mean manually at the switch or from eisy console? Based on what you just posted, it does appear there might be an issue on eisy that @IndyMike csn help you understand

Also, I asked AI a different way and it said updates were minimum of 100,000 writes which I used to update my prior post.

Edited Sunday at 02:36 PM2 days by hart2hart

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

17 minutes ago, hart2hart said:

, did you mean manually at the switch or from eisy console

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?

35 minutes ago, aLf said:

Not really sure how you'd select backlighting at the switch?

FWIW This is what AI said:

Yes, you can set the LED backlight level on an Insteon wall switch, but the exact steps depend on whether it’s a SwitchLinc‑style paddle/dimmer or an Insteon keypad.[1][3]

### For Insteon SwitchLinc (paddle/dimmer)

On most Insteon SwitchLincs (toggle, paddle, or rocker‑style), the LED backlight defaults to about 50% brightness and is adjustable via the device itself:[3][1]

1. Enter LED‑adjust mode

- Press and hold the Set button about 3 seconds until it beeps and the LED starts blinking.[1][3]

2. Adjust brightness

- Use the On/Off (or top/bottom) paddle to brighten or dim the backlight to your desired level.[3][1]

3. Save

- Tap the Set button once; the unit will double‑beep and exit, saving the new LED level.[1]

### For Insteon Keypad (6‑ or 8‑button)

KeypadLinc LEDs can be set to any of 32 brightness levels from the device:[2][3]

- 6‑button layout:

- Simultaneously tap A and D to start adjustment.

- Use On/Off to brighten/dim, then tap A and D again to save.[2]

- 8‑button layout / i3 Keypads:

- Either tap C & F (or predefined buttons) to enter adjust mode, then hold On to brighten/dim.

- Tap C & F again (or the designated save button pair) to store the level.[2][3]

### If you use a hub or ISY / Home Assistant

Some hubs (e.g., ISY‑series, Home Assistant with Insteon integration) expose a “backlight” or “LED brightness” slider; you can set the level there instead of via the physical buttons, then “write changes” to the device.[4][6][3]

If you tell me the exact Insteon model (for example “2477D paddle switch” or “2334‑2xx Keypad”), I can give you the precise button‑sequence for that unit.

Hey @aLf ,

The on thing that jumps out is the following error from your event viewer -

Sun 05/10/2026 09:26:30 AM : DB: Cannot load ./FILES/CONF/3BDFFC.REC

I've seen this error reported on the forum, but have not experienced it myself. Seems to be a missing "REC" file for your device at address 3BDFFC.

Ive seen forum posts where this error was associated with writing "Scene level commands" to devices. I haven't seen it associated with writing LED backlight levels, but that is a very similar operation.

Solutions that I've seen on the forum involve deleting the device and re-adding to recreate the file structure.

If you have a recent EISY backup that should restore the file system.

Past that, you may want to consider opening a ticket.

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 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.

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!

On 5/9/2026 at 9:43 AM, hart2hart said:

Did a quick bit of AI and the storage used for those settings is typically rated at 1.000 to 10,000 update cycles so at twice a day that would be 1.4 years to 10x that time.

I’m careful with AI but maybe not enough this time. Went deeper and got this:

“Insteon switches use EEPROM memory (often SST39VF040 or similar) for settings, with a guaranteed endurance of 100,000 write/erase cycles per sector.

Actual lifespan often exceeds this minimum in practice, as noted in general EEPROM discussions, though exact chip specs for all models aren’t always public.”

Or....

Use a bit of "RI". Open a 2413S PLM and notice the 24FC64 EEProm used. Then download the Microchip data sheet and confirm "• More than 1 Million Erase/Write Cycles"

5 hours ago, ELA said:

Or....

Use a bit of "RI". Open a 2413S PLM and notice the 24FC64 EEProm used. Then download the Microchip data sheet and confirm "• More than 1 Million Erase/Write Cycles"

LOL no argument here. I’m gonna start using the term RI.