IndyMike

I'm thinking that the IF clause is re-evaluating to false after you have run the "Then section" of the program.  Your 20 second waits will allow the program to exit.
Try separating into two programs (1 program for IF and 1 for Then). 

I've never had issues fitting multiple Insteon switches side by side in a 3 gang box.  Since they should fit side by side, I assume your box does not have enough depth to accommodate the wiring.
The being the case, you should checkout switches that use screw terminal connections.  I like the Zooz Z-wave switches, but that would require you to purchase a new Z-wave stick (not recommended). 
I believe that the Phillips Hue line is Zigbee.  I normally try to stay within the same communication protocol when using motion sensors/switches.  I use Zigbee for sensors but have 0 experience with Zigbee switches.
Hopefully someone else with experience with screw terminal Zigbee switches can chime in.

Change your if statement from "switched on" to "status on".
The "switched on" statement is for manually activating a device on/off.  You are turning the device on using a scene.  It will not trigger the "switched on" if clause.

@carealtor,
This issue has been around for some time.  For some reason the IOLinc itself reports the incorrect status during a query when the trigger is reversed. 
I just replicated exactly what you are describing using my ISY994 and a old V.36 IOLinc.  Not sure why you would not see this issue with the Polisy.  It's possible that Smartlabs fixed the later versions of the IOLinc.
Easiest way to rectify is to replace the magnetic switch with one that doesn't require the reversed trigger - or better yet, replace the IOLinc.
From the archives:  Trigger Reversed Query

@Techman, I understand the thought process.  The fact that multiple (repetitive) on commands are NOT recorded in the logs is not intuitive.  Some would call it a bug (or a feature).
Regardless, I would encourage everyone to try this for themselves to understand how/what events are logged.  Events that show up in the "Event Viewer" do not necessarily show up in the logs.  It's confusing until you gain a knowledge of how the ISY treats events and triggers. 
...and I will confess to re-learning from time to time...

Having a spare KPL is never a bad idea.  I had considered that you might have a KPL with a failing power supply.  It's doubtful that you have have 4 devices failing in a similar manner at the same time - unless you had a recent power event.
I had also considered a failing PLM.  The fact that you can communicate with your other devices and the communication problems are sporadic make this unlikely as well.
You are correct that tracking does a noisy device can be difficult.  This is particularly true when it's an intermittent source.  I would start by looking at the devices that are being affected:
Are the devices all on the same circuit - or widely spaced.  If they are on the same circuit, begin disabling other devices on the circuit to eliminate possible offenders. Are the devices all on the same phase of your electrical system.  Running a 4-tap beacon test can help you determine this.  Noise will not normally cross an electrical phase - unless the offender is a 220V device like my A/C condenser.  If you find that your devices are on the opposite phase from the PLM you can move the PLM, Improve the RF phase coupling, or add a passive coupler. I'm assuming that your issues are due to intermittent noise on the powerline.  If you have plug-in LampLincs or range extenders, you could try to improve RF communication by moving one nearer to your problems device(s). Are your problem devices all dual band (I'm guessing they are since they appear to be I2 capable).  If not, absolutely move a RF device (range extender or Lamp Link) nearer to the device.  Alternatively, upgrade the device. Look at your PLM placement - are there noise generators/signal absorbers near by (UPS, PC, chargers).  An easy test would be to move your PLM to a different circuit. Ask your self what type of demand devices you have that operate automatically (HVAC, Vent Fans, Well Pumps, Sump pumps, outdoor photocells).  Look for correlation between the operation of these devices and your issues. There really aren't any great diagnostic tools for tracking down noise devices.  Most troubleshooting uses the process of elimination (unplugging devices, turning off breakers) and observation (correlating problems with other device operation).
 
 

A query to a scene will interrogate all of the scene members with one exception.  You cannot query secondary keypad buttons. 
DennisC answered your question on creating a device folder in the Admin tree.  Unfortunately, I don't know of a way to query a sub-folder, al least not with the ISY994.
You can absolutely use a program to query a scene and it will iterate through each member

20A circuit with a small Refer and garage openers for a load - probably not a loading issue.
 
My experience has been with Insteon devices with "other" loads.  A HP printer/appliancelinc would cause trips in my basement when on the same circuit.  Remove either and the problem went away.
My Masterbuilt smoker will trip the GFCI without an Insteon load installed.  If I power the smoker up and communicate with anything in the house, the breaker trips.  I put a filter on the smoker to prevent trips.
As I said, I don't completely understand the Aeotec repeater. 
I get that.  I'm still happily running my 994i.  I'll give up on it when it gives up on me.
A friend on the forum recently shared his good experiences with YoLink.  Interesting devices that tout their long communication range.  Reasonably priced (requires a hub), I am looking at using sensors for my buddies outbuilding.  They do have temperature sensors that supposedly will work in refrigerators.   

@nil13,
The log for your BR light shows "classic" communication problems (low hops remaining) and timeouts (repeated requests from the ISY with no response from the BR Light)  After 3 timeouts the ISY declares a fault. 
 
BR Light Log:
Wed 01/17/2024 06:00:30 PM : [  1D B5 9A 1] Preparing Device 'Bedroom Swag Lights' for Restore
Wed 01/17/2024 06:00:30 PM : [  1D B5 9A 1] Device 'Bedroom Swag Lights' ready for Full Restore
Wed 01/17/2024 06:00:39 PM : [INST-TX-I1  ] 02 62 1D B5 9A 0F 0D 00
Wed 01/17/2024 06:00:39 PM : [INST-ACK    ] 02 62 1D.B5.9A 0F 0D 00 06                 (00)
Wed 01/17/2024 06:00:41 PM : [INST-SRX    ] 02 50 1D.B5.9A 70.8B.4D 27 0D 02           (02)
Wed 01/17/2024 06:00:41 PM : [Std-Direct Ack] 1D.B5.9A-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
Wed 01/17/2024 06:00:41 PM : [1D B5 9A 0  ] Calibrating engine version
Wed 01/17/2024 06:00:41 PM : [INST-TX-I2CS] 02 62 1D B5 9A 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Wed 01/17/2024 06:00:41 PM : [INST-ACK    ] 02 62 1D.B5.9A 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
Wed 01/17/2024 06:00:41 PM : [INST-SRX    ] 02 50 1D.B5.9A 70.8B.4D 23 0D 02           (02)
Wed 01/17/2024 06:00:41 PM : [Std-Direct Ack] 1D.B5.9A-->ISY/PLM Group=0, Max Hops=3, Hops Left=0
Wed 01/17/2024 06:00:50 PM : [INST-TX-I2CS] 02 62 1D B5 9A 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Wed 01/17/2024 06:00:50 PM : [INST-ACK    ] 02 62 1D.B5.9A 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
                        Timeout – No response from 1D.B5.9A
Wed 01/17/2024 06:00:59 PM : [INST-TX-I2CS] 02 62 1D B5 9A 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0
Wed 01/17/2024 06:00:59 PM : [INST-ACK    ] 02 62 1D.B5.9A 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06        (00)
Wed 01/17/2024 06:01:03 PM : [1D B5 9A 1  ] Memory : Write dbAddr=0x0264 [00] cmd1=0x2E cmd2=0x00
Wed 01/17/2024 06:01:03 PM : [INST-TX-I2CS] 02 62 1D B5 9A 1F 2E 00 00 07 00 00 00 00 00 00 00 00 00 00 00 CB
Wed 01/17/2024 06:01:03 PM : [INST-ACK    ] 02 62 1D.B5.9A 1F 2E 00 00 07 00 00 00 00 00 00 00 00 00 00 00 CB 06        (00)
Wed 01/17/2024 06:01:03 PM : [INST-SRX    ] 02 50 1D.B5.9A 70.8B.4D 27 2E 00           (00)
Wed 01/17/2024 06:01:03 PM : [Std-Direct Ack] 1D.B5.9A-->ISY/PLM Group=0, Max Hops=3, Hops Left=1
Wed 01/17/2024 06:01:03 PM : [1D B5 9A 1  ] Memory : Write dbAddr=0x0032 [7F] cmd1=0x2E cmd2=0x00
Wed 01/17/2024 06:01:03 PM : [INST-TX-I2CS] 02 62 1D B5 9A 1F 2E 00 01 06 7F 00 00 00 00 00 00 00 00 00 00 4C
Wed 01/17/2024 06:01:03 PM : [INST-ACK    ] 02 62 1D.B5.9A 1F 2E 00 01 06 7F 00 00 00 00 00 00 00 00 00 00 4C 06        
                        Timeout – No response from 1D.B5.9A
Wed 01/17/2024 06:01:12 PM : [INST-TX-I2CS] 02 62 1D B5 9A 1F 2E 00 01 06 7F 00 00 00 00 00 00 00 00 00 00 4C
Wed 01/17/2024 06:01:12 PM : [INST-ACK    ] 02 62 1D.B5.9A 1F 2E 00 01 06 7F 00 00 00 00 00 00 00 00 00 00 4C 06        (00)
                        Timeout – No response from 1D.B5.9A
Wed 01/17/2024 06:01:21 PM : [INST-TX-I2CS] 02 62 1D B5 9A 1F 2E 00 01 06 7F 00 00 00 00 00 00 00 00 00 00 4C
Wed 01/17/2024 06:01:21 PM : [INST-ACK    ] 02 62 1D.B5.9A 1F 2E 00 01 06 7F 00 00 00 00 00 00 00 00 00 00 4C 06        (00)
                        Timeout – No response from 1D.B5.9A
Wed 01/17/2024 06:01:25 PM : [1D B5 9A 1  ] Memory : Write dbAddr=0x0032 [7F] cmd1=0x2E cmd2=0x00 - Failed
 
The Log for your LR light is confusing.  The ISY did not attempt to send anything to the PLM.  I'm honestly not sure what the issue is here.  You might try power cycling the ISY and PLM.
LR Light Log
Wed 01/17/2024 05:53:50 PM : [  1B 93 CD 1] Preparing Device 'Living Room Swag Lig' for Restore
Wed 01/17/2024 05:53:50 PM : [  1B 93 CD 1] Device 'Living Room Swag Lig' ready for Full Restore
Wed 01/17/2024 05:55:01 PM : [1B 93 CD 1  ] Memory : Write dbAddr=0x0032 [9E] cmd1=0x2E cmd2=0x00
Wed 01/17/2024 05:55:23 PM : [1B 93 CD 1  ] Memory : Write dbAddr=0x0032 [9E] cmd1=0x2E cmd2=0x00 - Failed
 

Sounds more like a communication issue.  Garages can be very problematic with all the devices that are plugged into outlets (chargers, etc).
Since the 2450 is a plug-in device, try moving it closer to your PLM to check communication.  If it works, you need to look for signal absorbers/noise generators on the garage circuit.

Hey Jeff,
The most recent table is "better".  The first link @address 0FF8 shows that your device is a responder(A2) to group 0 device 70.1A.5A - your PLM I presume.
What I don't see is a corresponding link where your device is listed as a Controller to the PLM.  This would be
 0XXX: E2 XX 70.1A.5A.
What you have in the table is a HALF link.  The PLM can control your device, but the device can't issue control events back.
Again, you can probably rectify this by deleting/resetting/relinking your device.  If you have many devices that fall into this category, a ticket might still be a wise course of action. 

Hey bmarsh,
I'm a windows user that hasn't played with Linux for years.  My Win10 system does regularly "forget" the ISY location.  I normally "Load" from a saved file, or "Add" the location manually.
Assuming you know the local IP address for the ISY, you can simply "Add" as follows as shown below (use your own IP address of course).  Note that the "HTTP://" is mandatory.  If you want to add with security, simply use "HTTPS://"
If this works, save yourself some headaches in the future by using the "Save" button to save the file to a convenient location.  You can then "Load" at some point in the future when the loader forgets the settings.