Well - here is something very strange.

Current setup:

I have two 2477S switches - each are in a "two way" with an I3 Paddle (each switch is in its own 2 way - so two separate circuits). So each has a scene where both are controllers (the load is connected to the I3 in each case, with the 2477S being the "distant" on/off). (its basically two rows of lights across a basement rec room - each row controlled by each 2 way setup).

All worked perfectly.

I later decided to add a 2487S keypad at the top of the basement stairs - and I wanted one of the buttons to be able to turn on and off the rec room lights (both rows) - simple enough. I realized that this would potentially have issues with keeping things "in-sync" - so I have a couple of programs that monitor all this and make sure the LED's etc. all stay in alignment.

In addition I created a scene where I added the keypad linc button as a controller - and all the other devices (2477S and I3 paddles) as responders in this scene - so the button at the top of the stairs would directly turn on/off all the lights in the rec room and control all the other devices (the individual devices if switched on or off would only impact the button at the top of the stairs via the programs mentioned earlier).

When I added the I3 Paddles - all good - everything still worked (except the 2477S switches did not appear "on" - until the programs monitoring status picked it up). I also wanted to add the 2477S switches so they would all respond instantly as appropriate.

So here is where it got weird.

Everything was working fine until I added the 2477S devices to this new "key pad linc all on/off" scene as responders - when I did this - the individual 2477S switches would no longer operate the lights themselves directly (the I3 paddles continued to operate as they have the load connected of course).

I could click on and off the 2477S switches - and no response from the lights.

I tried "restoring" each device - this had no effect.

The thing that worked - I had to remove the 2477S devices from their original scenes with the I3 Paddles - and then re-add them to those scenes. When I did that they all worked again.

So my question is this - has anyone had this issues where when you add a device to a scene - it suddenly stops another scene from operating (and even the retore function does not correct)?

Would be interested in any feedback - also - if this happens to anyone else - then hopefully this will provide guidance as to how to correct (note that I only found out about this when other folks in my family complained that the switches were not working......... and I then started to scratch my head about what could be the issue).

Thanks!

2 hours ago, SMonk said:

could click on and off the 2477S switches - and no response from the lights.

That sounds like they mistakenly got set to 0% for "On" for the device. That happens sometimes.

When you reinstalled them, the default is 100% on

@SMonk, Pauls' scenario is certainly plausible. God knows I've thumb fingered setting often enough and turned scenes off (0%) when I intended on. Unfortunately, from your description, the error would need to occur on multiple 2477S's.

Since a restore did not work, the eisy believed the switch programming was correct.

The only thing I can come up with is a eisy restore from a backup that dated prior to the switches being added to the original scene. The EISY device table would not have had the links to that scene. Adding the devices to a new scene would have over written the scene that the EISY didn't have knowledge of.

Have you performed any EISY restores lately?

On 5/8/2026 at 3:28 PM, IndyMike said:

@SMonk, Pauls' scenario is certainly plausible. God knows I've thumb fingered setting often enough and turned scenes off (0%) when I intended on. Unfortunately, from your description, the error would need to occur on multiple 2477S's.

Since a restore did not work, the eisy believed the switch programming was correct.

The only thing I can come up with is a eisy restore from a backup that dated prior to the switches being added to the original scene. The EISY device table would not have had the links to that scene. Adding the devices to a new scene would have over written the scene that the EISY didn't have knowledge of.

Have you performed any EISY restores lately?

Hi @IndyMike - I have restored devices in the admin console - is that what you mean by asking "have you performed any EISY restores lately?". If not and there is another type of restore - can you explain?

Thanks!

1 hour ago, SMonk said:

Hi @IndyMike - I have restored devices in the admin console - is that what you mean by asking "have you performed any EISY restores lately?". If not and there is another type of restore - can you explain?

Thanks!

@Smonk, I was referring to the Restore operation for the EISY itself (restore from backup). This is similar to restoring any computer system from backup. The difference in this instance is that your Insteon system is "distributed" with software in the ISY, PLM, and your devices. The ISY does a good job of coordinating things, buy they can get out of synch.

Here's the scenario -

1. I backup the ISY to file

2. At this point the backup file contains a copy of all device tables

3. I modify a device by adding (or deleting) it from a scene

4. I restore the ISY from the backup in step 1 (backup now invalid).

5. The ISY now believes the device in step 3 has a "different" link table. Any future operation (restore, add to scene, remove from scene) will cause the scene links to be overwritten.

The confusing factor here is that the device will operate normally (it has the correct link table) until you restore/add to a scene/ remove from a scene after which the link table will be overwritten with outdated information.

Step 1: Backup ISY

Step 2: contents of "test device" vs ISY table (things match")

Step 3: Add Device to scene - ISY and Device table match (links added)

Step 4: Restore ISY from earlier backup (backup now outdated)

Step 5: After restore, ISY device table no longer matches actual device. The device will operate properly, but future operations (add to scene, restore, etc) will overwrite links after the ISY end of record address (x0FD8)

4 hours ago, IndyMike said:

@Smonk, I was referring to the Restore operation for the EISY itself (restore from backup). This is similar to restoring any computer system from backup. The difference in this instance is that your Insteon system is "distributed" with software in the ISY, PLM, and your devices. The ISY does a good job of coordinating things, buy they can get out of synch.

Here's the scenario -

1. I backup the ISY to file

2. At this point the backup file contains a copy of all device tables

3. I modify a device by adding (or deleting) it from a scene

4. I restore the ISY from the backup in step 1 (backup now invalid).

5. The ISY now believes the device in step 3 has a "different" link table. Any future operation (restore, add to scene, remove from scene) will cause the scene links to be overwritten.

The confusing factor here is that the device will operate normally (it has the correct link table) until you restore/add to a scene/ remove from a scene after which the link table will be overwritten with outdated information.

Step 1: Backup ISY

Step 2: contents of "test device" vs ISY table (things match")

Step 3: Add Device to scene - ISY and Device table match (links added)

Step 4: Restore ISY from earlier backup (backup now outdated)

Step 5: After restore, ISY device table no longer matches actual device. The device will operate properly, but future operations (add to scene, restore, etc) will overwrite links after the ISY end of record address (x0FD8)

Ok - got it - thanks @IndyMike !