LeeG

It is the occurrence of a condition that triggers a Program, not a change in Program True/False status. In this Program the Wait is terminated if the Motion Sensor - Sensor senses motion within the 5 minute Wait and the Then clause restarted even though Program Status is always True. AAAA4 - [iD 006C][Parent 0001] If Control 'MS I2CS-Sensor' is switched On Then Wait 5 minutes Set 'SwitchLinc Dimmer 1' Off Else - No Actions - (To add one, press 'Action')

jerlands Can you point me to the Wiki section that has that information. I got this from Wait/Repeat description. http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Action Wait Waits for the specified amount of time. If the Random checkbox is checked, then a random value from 0 to the specified time is used. A wait stops when the conditions change. Repeat Continuously repeats at this interval, as follows: A repeat stops when the conditions change. To break a Repeat sequence, add a "Repeat 1 times". Actions after this Repeat will only run once (that is to say, they won't repeat at all). This is useful when you want some Actions repeated, but then want to continue on with more Actions that should not be repeated. The Repeat and Wait actions have a "Random" option. This is set by selecting the Random check box. A Random value from 1 to the entered value will be randomly chosen each time the action is run.

The Wait and Repeat do not cause the If to be reevaluated. The Wait and Repeat allow the If to be reevaluated. Normal rules for what triggers an If apply.

In the following Program the If is NEVER True. If Control 'KPL Test2 - C' is switched On And Control 'KPL Test2 - D' is switched On Then Send X10 'A1/On (3)' Else Send X10 'A1/Off (11)' As far as how the ISY internally selects Programs to evaluate If clause will have to come from UDI.

bdawson You found the solution, well done. As far as Insteon is concerned the ISY Scene and each KPL button added as a Controller are separate, independent Insteon Scenes. Each Insteon Scene can have unique Responder On Level and Responder Ramp Rate values for each Responder.

X10 addresses are not in the link table. A Program is triggered whenever a Condition the Program checks occurs. (and triggers a Program. If integer variable does not trigger a Program) Some trigger examples (not all inclusive) A change of Status A command defined in "If Control" is received Change in State Variable An X10 address receives checked command ELK State change Once a Program is triggered the If clause is evaluated for True or False. When the If is True the Then clause executes. When the If is false the Else clause executes. The order in which Programs run is controlled by ISY

shadowb Independent of the terminology, you have the correct idea. From an Insteon perspective the "Scene" is one Insteon Scene. Each Controller (show in RED) is another Insteon Scene. The example below is actually defining three Insteon Scenes, each with independent characteristics. Of course they can be set to the same Insteon Scene characteristics but each can have its own Scene reaction. Scenes are simple but very powerful. Sceneabc Controller1 Controller2 Responder1 Responder2 Being interested in understanding Scenes is really great.

I think #2, Scene folder, is likely a terminology question. A Scene in an ISY Folder, the folder has no device properties. An ISY Scene does have device properties (On Level, Ramp Rate) for the Scene responders.

mykanderson Does the query all have to b be at 3am No. Could be 2AM, 3:10AM, 4AM. 3AM was picked because it is in the middle of normal sleep time where the Query activity would not interfere with other activity

The ISY PLM does not appear in the normal device list. Tools | Diagnostics | PLM Info/Status has basic PLM info. Direct manual links between devices should never be done. Create ISY Scenes to link devices. Example SceneSwitchLincs SwitchLinc1 - Controller SwitchLinc2 - Controller ApplianceLinc - Responder These Scenes do not require the ISY for the Scenes to be functional. However, the ISY is not an application running on a PC. It is not normal to run without the ISY. The device(s) Quick Start guide does not assume an application such as ISY is available. Creating Scenes and device configuration is usually easier with the ISY.

Great job analyzing the situation.

Grouping the KPL nodes does not change the way the KPL nodes work. However, Grouping the nodes together avoids losing track of one or more nodes because of how the node names are sorted in the "Network". Can you post the names on the 5 KPL nodes?

stillen_i30 This event trace shows 18.EC.C8 turned Off, then On successfully. Hops Left=2 for both operations is fine. Then the next Off failed to get a response from the device. Because it was an Off that failed it could be the load that 18.EC.C8 is driving or it could be powerline comm issue. The Off command that got no response was close in time (4-5 seconds) to the previous On so it could be the load of the device. Unfortunately it will take more analysis on your end (some good suggestions already posted) to get get more data. Wed 12/02/2015 09:56:03 PM : [iNST-TX-I1 ] 02 62 18 EC C8 0F 13 00 Wed 12/02/2015 09:56:03 PM : [iNST-ACK ] 02 62 18.EC.C8 0F 13 00 06 LTOFFRR(00) Wed 12/02/2015 09:56:04 PM : [iNST-SRX ] 02 50 18.EC.C8 34.E8.89 2B 13 00 LTOFFRR(00) - good response Wed 12/02/2015 09:56:04 PM : [std-Direct Ack] 18.EC.C8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 12/02/2015 09:56:04 PM : [D2D EVENT ] Event [18 EC C8 1] [sT] [0] uom=0 prec=-1 Wed 12/02/2015 09:56:04 PM : [ 18 EC C8 1] ST 0 Wed 12/02/2015 09:56:06 PM : [iNST-TX-I1 ] 02 62 18 EC C8 0F 11 FF Wed 12/02/2015 09:56:06 PM : [iNST-ACK ] 02 62 18.EC.C8 0F 11 FF 06 LTONRR (FF) Wed 12/02/2015 09:56:07 PM : [iNST-SRX ] 02 50 18.EC.C8 34.E8.89 2B 11 FF LTONRR (FF) - good response Wed 12/02/2015 09:56:07 PM : [std-Direct Ack] 18.EC.C8-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Wed 12/02/2015 09:56:07 PM : [D2D EVENT ] Event [18 EC C8 1] [sT] [255] uom=0 prec=-1 Wed 12/02/2015 09:56:07 PM : [ 18 EC C8 1] ST 255 Wed 12/02/2015 09:56:12 PM : [iNST-TX-I1 ] 02 62 18 EC C8 0F 13 00 Wed 12/02/2015 09:56:12 PM : [iNST-ACK ] 02 62 18.EC.C8 0F 13 00 06 LTOFFRR(00) - no response Wed 12/02/2015 09:56:16 PM : [D2D EVENT ] Event [18 EC C8 1] [ERR] [1] uom=0 prec=-1 Wed 12/02/2015 09:56:16 PM : [ 18 EC C8 1] ERR 1

Some information the LampLinc was not seen because of a half link. LampLinc has Responder link, SwitchLinc is missing Controller link the 3D.C7.BE is likely the ISY PLM from the A2 and E2 link records at 0FE8 and 0FE0 With the number of issues with so few devices the best approach would be to Delete all devices from ISY, Factory Reset all devices, add devices back using Link Management | New INSTEON Device with Auto Discover and 'remove existing links'. If not on 4.3.26 update ISY Firmware and UI to 4.3.26

Stu My post was in response to Blackbird question.

The Repeat range is to the end of the clause (Then or Else), or to the next Repeat. In this example the Set, and all statements after that are repeated Then .... Repeat 3 times Set 'ICON Relay 2' Off statement 1 statement 2 Else In this example the Set is the only statement that is repeated Then .... Repeat 3 times Set 'ICON Relay 2' Off Repeat 1 time statement 1 statement 2 Else

Perhaps that was not the question. All statements after Repeat 3 times to end of clause are in the Repeat 3 times loop. Then .... Repeat 3 times Set 'ICON Relay 2' Off .... .... Else The Repeat statement is covered in the Wiki http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Action

The Repeat 1 time ends the Repeat loop above. It allows other statements to be coded after the Repeat 1 time that do not participate in the Repeat 3 times loop.

The statement(s) after the Repeat until next Repeat Then .... Repeat 3 times Set 'ICON Relay 2' Off Repeat 1 times Else

Both sides of the "And" will not be True. When the Program is triggered by receiving "Control" events the "Status" is Off. When triggered by "Status" the "Control" events are false.

I have found a v.43 KPL that also has incorrect non-toggle On button LED response. It does send an On command each time pressed but the LED goes to Off setting after blinking twice. The 2E command that sets the non-toggle On/Off setting is the same command that works with the older KPLs. Since v.43 is sending an On command that part makes sense. There is another variant of the 2E command (D2=09) that speaks to controlling the non-toggle button LED that is not needed by older KPLs but may be required by the later ones. It will take some time to test the 2E 09 variant because the PLM address must match (I2CS device).

The Icon Dimmer is having significant comm problems during restore. Mon 11/30/2015 11:28:22 PM : [1A 28 12 1 ] Link 0 : 0FF8 [A20034E889FF1F01] Writing [A20034E889FF1F01] Mon 11/30/2015 11:28:22 PM : [iNST-TX-I1 ] 02 62 1A 28 12 0F 28 0F Mon 11/30/2015 11:28:22 PM : [iNST-ACK ] 02 62 1A.28.12 0F 28 0F 06 SET-MSB(0F) - no device response Mon 11/30/2015 11:28:30 PM : [iNST-TX-I1 ] 02 62 1A 28 12 0F 28 0F Mon 11/30/2015 11:28:30 PM : [iNST-ACK ] 02 62 1A.28.12 0F 28 0F 06 SET-MSB(0F) - no device response Mon 11/30/2015 11:28:39 PM : [iNST-TX-I1 ] 02 62 1A 28 12 0F 28 0F Mon 11/30/2015 11:28:39 PM : [iNST-ACK ] 02 62 1A.28.12 0F 28 0F 06 SET-MSB(0F) - no device response Mon 11/30/2015 11:28:43 PM : [1A 28 12 1 ] Link 0 : 0FF8 [A20034E889FF1F01] *Failed Writing [A20034E889FF1F01] I have a house full of Icon devices installed some 10 years ago. Not uncommon for a device to have comm issues after losing power. Mine occur after power outage from storms. For those that do not recover with Factory Reset I've had to replace with SwitchLincs.

Thanks. Secondary Button A (03) is sending On command (11), regardless of final button LED level. Mon 11/30/2015 06:51:07 PM : [iNST-SRX ] 02 50 3B.8E.85 00.00.03 CB 11 00 LTONRR (00) Although running 4.4.1 which should have no affect on result, I am going through all my KPLs to see if I can find a difference in button LED levels. This will take some time. I'll post back when tests are complete.

"Perhaps the code to update the KeyPadDimmer is missing the "turn the state to On' when setting the button to Non-Toggle On." Changing the button mode does not change the state of the button. It takes an activity, Scene On/Off, button press, etc to affect button state.

With the buttons being in Off state the LED Brightness is correct. Suggest running Event Viewer at LEVEL 3. Press one of the A-D buttons and post the event trace.