IndyMike

@rwsani99, Your log from the "show device links" is showing evidence of communication timeouts (no-response from the target device). If things were working properly, you would see a "[INST-SRX ] 02 50 4E.7D.16 71.17.44 XXXXX" after the [INST-ACK}. In the above, the PLM is re-trying communications up to 5x per request, and the ISY is re-trying 3x (15x total). That's rather bad. Since you indicated that you are having issues with multiple devices, I'm am going to guess that you have a rather strong noise source near the PLM. I say near the PLM because you are having problems with multiple devices. I am guessing that it's a noise source, rather than a signal absorber, because it's rather intermittent. Your second log section showed sections of total failure, followed by rather good communication (hops remaining = 2). Inspect the circuit where the PLM is installed for problem items (Pc's, UPS, Printers, etc). Alternatively, you could try moving the PLM to another circuit. Let us know how things are progressing

@alixer, when you performed the "restore device", was the ISY able to complete write the link table (no errors)? If this is the case, then your device has the correct PLM address and the scene information is incorrect. I say this because newer devices (I2CS units produced after 2012) will not allow the ISY to read/write to them unless the PLM address is in their link table. It may still be helpful is you could post your device link table, ISY device link table, and PLM address. The membership tree on the right is also helpful since it shows how many scenes the device is associated with. If your link table compare looks similar to mine above (no missing or mismatched entries) then the ISY believes the device has the correct link table/scene information. If the device does not respond correctly to a scene command (assuming that it received the command), then the ISY Link Table for the device is incorrect. The ISY maintains link tables for each Insteon device and for some reason, yours may have been corrupted. You can correct this by manipulating the device settings within the scene, causing a re-write to the device (as you are doing) OR your can restore the ISY from backup. Obviously, the backup may also have incorrect information, or be missing information on your more recent devices. If you do choose to restore a ISY backup, please follow with the process that @lilyoyo1 outlined above.

That's unfortunate. It indicates that the ISY does not have the correct scene information. You could try installing an ISY backup (restore ISY, restore modem, restore devices) , but that may be more work than "refreshing" you scene devices.

To be clear, my system failure was two fold: Poor programming on my part that led to a program cycling the system on/off causing water hammer. Poor irrigation design causing excessive main pipe flow (erosion). Pipe erosion occurs when you have large zones (high flow) and a capable supply. It's not that hard to avoid as long and you understand the pressures and flows in your system. I found the following site helpful. It includes spreadsheets for calculation pressure loss (friction) in various types of irrigation plumping. For reference, I was just below 7 ft/sec in my system mainline with certain zones operating. https://www.irrigationtutorials.com/#gsc.tab=0

It sounds like your new PLM address did not get written to your older devices. Not quite sure why. When you adjust the parameters of scene devices you are re-writing the scene AND the PLM address. That's why things work properly after the update. I can understand why you wouldn't want to do this for all of your scenes - you probably have a life. Could you try performing a Link Table Read/compare on one of your problem devices and posting the results? Please also post the new/old PLM address. This will tell us if the ISY contains the correct information. If it does, a simple "restore device" should correct the problem. If it doesn't, things get a bit more complicated...

@rwsani99, could you post a copy of the event viewer for when this occurs? There are a number of possible issues that could cause this (serious noise issues, PLM address change, PLM failure). Need to see the event viewer to determine which path to send you down.

@hart2hart, I'd say you've got the gist of the repeat loop. Please do pay attention to @dbwarner5's cautions on irrigation. They don't only apply to well fed systems. Cycling solenoid valves on irrigation should not be taken lightly. Rapid cycling and water hammer can destroy pipes - ask me how I know... At one time I tried to integrate my Evapotranspiration calculations, current weather conditions, and my irrigation. It didn't go well and I burst a 2" line. Caught my attention. I don't do that anymore.

@hart2hart, I'm not sure where your "zones" are in the program. I do see the "25 minute waits" at numerous places in the program. If this is where the Zones are, your could insert the code at each "25 minute wait". I think your program would resemble the following. That doesn't look crazy unmanagble. If you want to change all of the waits over to programmable delays, that would get rather confusing. At that point multiple zone programs/delay programs would become more "readable". Then $Water_Today_Start_I = 'Flume Water / FlumeWater / Flume Sensor' Today US gallons Set 'Yard / Yard:Front Mulch Beds' Start '$Irrigation_Run_Minutes Minutes' $I.MinuteCount = $Irrigation_Run_Minutes Minutes Repeat While $I.MinuteCount > 0 $I.MinuteCount -= 1 Wait 1 minute Repeat 1 times Set 'Yard / 2Yard:Front Mulch Beds' Off Wait 1 minute Set 'Yard / 2Yard:Front Left' On $I.MinuteCount = $Irrigation_Run_Minutes Minutes Repeat While $I.MinuteCount > 0 $I.MinuteCount -= 1 Wait 1 minute Repeat 1 times Set 'Yard / 2Yard:Front Left' Off Wait 1 minute Set 'Yard / 2Yard:Front Right' On $I.MinuteCount = $Irrigation_Run_Minutes Minutes Repeat While $I.MinuteCount > 0 $I.MinuteCount -= 1 Wait 1 minute Repeat 1 times Set 'Yard / 2Yard:Front Right' Off Wait 1 minute Set 'Yard / 2Yard:Back Fountain Driveway' On $I.MinuteCount = $Irrigation_Run_Minutes Minutes Repeat While $I.MinuteCount > 0 $I.MinuteCount -= 1 Wait 1 minute Repeat 1 times Set 'Yard / 2Yard:Back Fountain Driveway' Off Wait 1 minute Set 'Yard / 2Yard:Back Front Left' On $I.MinuteCount = $Irrigation_Run_Minutes Minutes Repeat While $I.MinuteCount > 0 $I.MinuteCount -= 1 Wait 1 minute Repeat 1 times Set 'Yard / 2Yard:Back Front Left' Off Wait 1 minute

Single program version using a Repeat - While Loop The second "Repeat 1 times" is required to end the loop if you wish to have follow on statements. Not required if nothing follows. You can decrease the wait time to gain granularity, but it comes at the expense of overhead. A 1 second wait loop requires roughly 2 seconds to execute and is working the ISY994 rather hard. Variable Minute Wait Test Program - [ID 0060][Parent 0004][Not Enabled] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $I.MinuteCount = 2 Repeat While $I.MinuteCount > 0 $I.MinuteCount -= 1 Wait 1 minute Repeat 1 times Set 'Basement / SC BSMT Entry' Off Else - No Actions - (To add one, press 'Action')

@jaysmc, do you see activity in the Event Viewer when this occurs? Can you post?

As luck would have it, I did something very similar to myself some time back. I was playing with ISY Scenes on Home Assistant. I had set up a program to trigger on a ISY scene (my basement) and immediately turn the scene off. Unlike the ISY, Home Assistant views an ISY scene as "ON" if any member of the scene is on. The HA program would turn off my entire basement (13 lights) if any light were activated. For this to function both the ISY and HA had to be operating. After playing with the program, I disabled it on HA. Fast forward a year or two, and I inadvertently re-enabled the program. Took me quite awhile to figure out what was going on. The event viewer would show my basement scene being triggered off. I figured I had a rogue ISY program being triggered. Disabled all programs, deleted all programs, and it refused to go away. Then I remembered Home Assistant - Homer Slap.

@abrayshaw, you mentioned that you've been unsuccessful loading from Lan. Have you tried loading from the cloud?

@abrayshaw, If you know the IP address for your ISY you can enter it directly by clicking the "Add" button. Use the format shown below. If you do not know the IP address, log into your router and locate it. At this point you should also "reserve" the IP address for the ISY (if you haven't already). You don't want the complications of having DHCP move this address around. Assuming you can find the address and "Add" it successfully, "Save" the configuration to a file on your computer. Choose a location that's easy to locate (desktop, etc). The next time you can't "refresh" the configuration, use the "Load" button to load the configuration file. I created my file in 2022 (it's been working awhile now). @Geddy's approach is the correct one. This is merely a workaround.

A word of caution when using the "My Lighting" query. I'll qualify this by saying that my experience is with the ISY994. The PolISY and EISY may be different. For the ISY994, a "My Lighting" query hit everything. Some things that you may not wish to have queried: All Insteon devices, Including MS-II sensors (bug). You can disable MS-II sensors to get around this. Note that the query is also a problem for IOLinc devices with "trigger reversed" set. All X10 devices, including receive only devices (bug) Z-wave devices - from memory, this includes battery devices. I do not know how Zigbee/WiFi/matter devices are handled on the newer systems. On the ISY994, I created a "House Query" scene that had ONLY the devices that I wanted updated and used that for the 3AM program query. This is a maintenance item as you need to keep adding new devices to the scene.

@sbooke, your event viewer shows communication from your motion sensor, but it's from group 13. Motion is from group 1. I can't see enough from the event viewer to tell if you got a group 1 communication like you had previously. Regardless, your program should run as you have it written: Make sure you have saved the program. Look at the program summary to see the "last run" for the program. It should be triggering within the time window. If it has triggered, try performing a "run then" on the program to see if your device responds correctly. If none of the above works, delete the time constraint and check to see if the motion trigger alone works.