IndyMike

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

As a quick test, I got out my old Remotelinc to use as a jammer. Ran a standard "scene test" on my basement lighting (100% success). Ran the same scene test while holding a on button on the Remotelinc (bright command). 4 out of 18 Pass (22%). What's interesting about this test: The remotelinc is not linked to the system. Nothing shows in the event viewer. Since every Insteon device is a repeater, it is still flooding RF and powerline. I effectively hung the PLM/ISY while I was holding the Bright button. The ISY didn't appear to progress until I released the button. Event viewer was hung in mid-test. Standard Scene Test: Scene Test Jammed Using Remotelinc (Bright)

@Guy Lavoie, hard to know which operation corrected things (PLM restore or controller power cycle). What specific mini controller are you using? If the mini controller were flooding your system with communications (RF or Powerline?), it could effectively jam your motion sensors. The motions won't necessarily be aware of the communication resulting in a collision. On the other hand, the PLM/Admin console would wait for and open communication window and therefor might be able to send commands. If your PLM link table was "upset", you would be able to send commands to devices but not receive. Since you just recently added the mini controller, that's where I'd put my bet.

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

When you execute a scene from the ISY (admin console or program) it does not verify that scene members received the communication. It assumes that the scene was executed properly. If you have noise or signal absorption, scene member may not respond. The ISY will still show these devices as having responded. When you re-boot the system, the ISY queries devices and restores the correct status. Queries are performed using retries and are normally very reliable. The ISY will normally Query your system in the off-hours (3 AM?) to re-synch things. This is a system installed program that runs nightly. If you have persistent issues with a few devices you may have noise/absorption issues on the related electrical circuits. Inspect for chargers, PC's, etc. If you have problems with MANY devices, the issue may be near your PLM. Perform the same inspection. By opening the event viewer on level 3 and performing device queries from the admin console you can observe communication with your devices. Communication from the device to the PLM will be summarized in the "[Std-Direct Ack] Entry" and will show Max Hop and Hops Remaining. Hops Remaining of "3" is as good as it gets. Lower is less desirable. Device Query Communication in Event Viewer. Device address 1A.5D.C7 to PLM Address 53.BC.3A.

@sbooke, your motion sense is working. Your event viewer is showing EXACTLY what I posted above. Your last program you posted is incorrect. You are using a time trigger, not a motion trigger. The THEN statement is also incorrect. However, your original program should work. As @Guy Lavoie indicated, this would perform better if you used a "control" vs "status" qualifier. Not sure how, but we seem to have come full circle. Event Viewer Showing MS-II Communication Original Program Motion Program

That worked, and your PLM does have the link records for your device. If your MS II is communicating (you said you were able to trigger scenes with it), your PLM should see group 1 communication from this device. Your event viewer should show the following when triggered (updated with your device address). Make sure that the Event Viewer is set to level 3. If you cannot see the communication in the event viewer either you have communication issues with that device (noise, etc) or the device itself isn't programmed correctly. If you changed PLM's recently, it's possible that the Motion Sensor does not have the correct PLM address in it's link memory. To verify, place the Sensor in programming mode and perform a Link Table Read + compare. It's possible that the MS-II Options are not set correctly. Verify that "Conditioin, Report, and Sensitivity" are set correctly (see below) Event Viewer Showing MS-II on trigger [INST-SRX ] 02 50 4D.EF.5F 00.00.01 CF 11 01 LTONRR (01) [Std-Group ] 4D.EF.5F-->Group=1, Max Hops=3, Hops Left=3 [D2D EVENT ] Event [4D EF 5F 1] [DON] [1] uom=0 prec=-1 [ 4D EF 5F 1] DON 1 Your PLM link record for the Motion Sensor Motion Sensor Link Table Read + Compare MS-II Device Options