LeeG

Likely your not on the latest Official release 4.3.26. That device type is rather new and requires the latest Official release. Be sure to update Firmware and UI to 4.3.26. What is the current Firmware and UI level (Help | About)?

Not with a simple On press of paddle. The device that does not go to 100% is being turned On with a Scene. The Responder link record On Level does not change regardless of the number of On commands issued. A fast double tap to generate a Fast On command brings the Responder to full On.

Stu The Else does execute as the OP indicates. The Program is Triggered at Sunrise + 30.minutes. Once Triggered the Program must execute either the Then or Else. Since the If evaluation is False the Then execution is canceled because of the Waits and the Else executes. This leaves unexecuted statements in Then. If From Sunset To Sunrise + 30 minutes (next day) And Control 'Outside / Front Door Motion Sensor-Sens' is switched On

If interested in changing to a different device look at the Smartenit EZIO2X4. I've used one in a detached garage for over 5 years. It is not Dual Band but the I/O Linc is not Dual Band either. In my case the lack of Dual Band is not important because of the distance from the house. There are two Relays with built in timers and 4 Inputs. I have magnetic sensors for both fully closed and fully open positions as the doors are not visible from the house. KPL buttons show 'not closed' and 'fully open' for each door. There is a Simplehomenet (original company name) Utility (free) for setting up the timers and configuration. The Utility requires a separate PLM. The ISY supports the device as far as Scene creation, monitoring Inputs and Relay control. I have I/O Lincs as well that have not failed so no help there.

Sorry, must be that I am on a windows machine. I see various Scenes that have been expanded but there is no Managed Scene anywhere on the displayed image.

Something is out of sync as a see nothing that says Managed Scene in the screen image.

Is there any message when Delete Scene is clicked?

From the 2413S Quick Start Guide - accessed from Smarthome web site To reset PowerLinc Modem to its original factory settings, unplug from wall outlet and wait 10 seconds. Press and hold Set button; while continuing to press and hold, plug back in. A long beep will sound; continue holding Set button until beep stops, then release.

Refer to the Wiki link for procedure to replace PLM. http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_.28PLM.29 After the Restore Modem (PLM) completes (using correct sequence for powering ISY and PLM down) run File | Restore Devices. Note that battery devices are not updated either because the Pro Icon queues the updates or the updates fail and are queued if not using a Pro. Each battery device must be put into manual linking mode, the pending updates run, and the battery device taken out of linking mode before moving to next battery device. Only one battery device at a time can be updated. Putting multiple battery devices into linking mode at the same time links those devices together rather than doing the updates.

No need to link the Range Extenders. The 4 tap beacon test works with all the Dual Band devices that are in RF range. Although most interested to have Range Extenders on Opposite 120V legs, the beacon test will also show all the Dual Band devices in RF range and whether they are on the same or opposite 120V leg.

"If Control" is checking the command that is flowing from the device to the ISY. Same logic if it is a SwitchLinc, a KPL button, TriggerLinc, Motion Sensor, IO Linc, Leak Sensor, etc. If Control 'device' is switched On can be used on any device, battery or powerline powered, that sends an On command to the ISY. If Control is testing for the arrival of some specific command and as such the event has a short lifespan. If Control 'device1' is switched On Or Control 'device2' is switched On Then is a perfectly good If Condition. If Control 'device1' is switched On And Control 'device2' is switched On Then is a Condition that can never be True since a 'device1' On command cannot happen at the same time 'device2' On command happens. The PLM and therefore the ISY can process only one inbound command at a time. ------------------------------------------------------- If Status 'device1' is On is checking the Current State of device1. Device1 could be turned on by a Program, by another device (Scene), or turned On locally. Current State can be long lasting. If Status 'device1' is On Or Status 'device2 is On Then is a valid If Condition. If Status 'device1' is On And Status 'device2 is On Then is also a valid If Condition as both 'device1' and 'device2' can have a Current State of On at the same time.

The lack of Motion Sensor traffic in the event trace is not informative. If it is the PLM that cannot be reached the event trace would not show traffic that does not reach PLM. if the Motion Sensor is not reaching some other device (and is retrying during the 20 seconds) that traffic never shows in the event trace because that traffic is being sent to an Insteon address other than the PLM. After putting Motion Sensor into manual linking mode do a Show Device Links Table. Look for all link records with E2 01 xx.yy.zz .. .. .. where xx.yy.zz will be the Insteon devices that receive the motion messages. By checking Current State of each device with a link record it should show which device(s) are not ACKing the motion message. Could be a comm issue or the Responder device may have lost the corresponding Responder link record.pointing bac to the motion sensor.

If Control and If Status for a TriggerLinc (or Motion Sensor) have the same meaning as they do for a SwitchLinc. Being battery devices the state of the TriggerLinc is lost across an ISY reboot because the TriggerLinc cannot be queried as part of the ISY restart. Once the TriggerLinc is operated the state of the TriggerLinc is like a SwitchLinc Relay. Are there specific questions?

Is the OutletLinc the old version where only one outlet is Insteon controlled or the newer OutletLinc version where both outlets are under Insteon control?

I agree with jerlands that comm is marginal. Also the flood of Motion Sensor messages makes the comm more difficult. Here is what the first part of the trace should look like when adding an I2CS Keypad. The message activity in Red is missing in your trace. Sat 12/12/2015 07:46:07 PM : [33 14 c5 ] Added to list of devices to link to ISY Sat 12/12/2015 07:46:07 PM : [iNST-TX-I1 ] 02 62 33 14 C5 0F 0D 00 Sat 12/12/2015 07:46:07 PM : [iNST-ACK ] 02 62 33.14.C5 0F 0D 00 06 (00) Sat 12/12/2015 07:46:07 PM : [iNST-SRX ] 02 50 33.14.C5 22.80.0B AB 0D FF (FF) Sat 12/12/2015 07:46:07 PM : [std-Direct Nack] 33.14.C5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/12/2015 07:46:07 PM : [iNST-TX-I2CS] 02 62 33 14 C5 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Sat 12/12/2015 07:46:07 PM : [iNST-ACK ] 02 62 33.14.C5 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01) Sat 12/12/2015 07:46:08 PM : [iNST-SRX ] 02 50 33.14.C5 22.80.0B 2B 09 01 LNK-ON (01) Sat 12/12/2015 07:46:08 PM : [std-Direct Ack] 33.14.C5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/12/2015 07:46:08 PM : [LNK-BGN ] 02 64 01 00 06 Sat 12/12/2015 07:46:09 PM : [LNK-STAT ] 02 53 M(01) gid=00 33.14.C5 0141 43 Sat 12/12/2015 07:46:09 PM : [iNST-TX-I1 ] 02 62 33 14 C5 0F 0D 00 Sat 12/12/2015 07:46:09 PM : [LNK-END ] 02 65 06 Sat 12/12/2015 07:46:09 PM : [std MH ] Unexpected Ack imCmd=65 cmd1= 0xC5 Sat 12/12/2015 07:46:09 PM : [iNST-ACK ] 02 62 33.14.C5 0F 0D 00 06 (00) Sat 12/12/2015 07:46:09 PM : [iNST-SRX ] 02 50 33.14.C5 22.80.0B 2B 0D 02 (02) Sat 12/12/2015 07:46:09 PM : [std-Direct Ack] 33.14.C5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/12/2015 07:46:14 PM : [iNST-TX-I1 ] 02 62 33 14 C5 0F 0D 00 Sat 12/12/2015 07:46:14 PM : [iNST-ACK ] 02 62 33.14.C5 0F 0D 00 06 (00) Sat 12/12/2015 07:46:14 PM : [iNST-SRX ] 02 50 33.14.C5 22.80.0B 2B 0D 02 (02) Sat 12/12/2015 07:46:14 PM : [std-Direct Ack] 33.14.C5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/12/2015 07:46:14 PM : [iNST-TX-I1 ] 02 62 33 14 C5 0F 10 00 Sat 12/12/2015 07:46:14 PM : [iNST-ACK ] 02 62 33.14.C5 0F 10 00 06 ID-REQ (00) Sat 12/12/2015 07:46:14 PM : [iNST-SRX ] 02 50 33.14.C5 22.80.0B 2B 10 00 ID-REQ (00) Sat 12/12/2015 07:46:14 PM : [std-Direct Ack] 33.14.C5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/12/2015 07:46:15 PM : [iNST-SRX ] 02 50 33.14.C5 01.41.43 8B 01 73 (73) Sat 12/12/2015 07:46:15 PM : [std-Broadcast] 33.14.C5-->01.41.43, Max Hops=3, Hops Left=2 Sat 12/12/2015 07:46:15 PM : [33 14 C5 0 ] Calibrating engine version Sat 12/12/2015 07:46:15 PM : [iNST-TX-I2CS] 02 62 33 14 C5 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Sat 12/12/2015 07:46:15 PM : [iNST-ACK ] 02 62 33.14.C5 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Sat 12/12/2015 07:46:15 PM : [iNST-SRX ] 02 50 33.14.C5 22.80.0B 2B 2F 00 (00) Sat 12/12/2015 07:46:15 PM : [std-Direct Ack] 33.14.C5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/12/2015 07:46:16 PM : [iNST-ERX ] 02 51 33 14 C5 22 80 0B 11 2F 00 00 01 0F FF 00 AA 00 22 80 0B 00 1C 01 4E Sat 12/12/2015 07:46:16 PM : [Ext-Direct ] 33.14.C5-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/12/2015 07:46:16 PM : [33 14 C5 0 ] Using Database Link Table offset 0x0FF8 (reported 0x0FF8) Sat 12/12/2015 07:46:16 PM : [33 14 C5 1 ] Start : Adding device to ISY Sat 12/12/2015 07:46:16 PM : [33 14 C5 1 ] Finish : Adding device to ISY was Successful Sat 12/12/2015 07:46:16 PM : [33 14 C5 1 ] Link 0 : 0FF8 [A20022800BFF1F01] Saving [A20022800BFF1F01] Sat 12/12/2015 07:46:16 PM : [33 14 C5 1 ] Link 1 : 0FF0 [E20122800B010001] Saving [E20122800B010001] Sat 12/12/2015 07:46:17 PM : [iNST-TX-I2CS] 02 62 33 14 C5 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 Sat 12/12/2015 07:46:17 PM : [iNST-ACK ] 02 62 33.14.C5 1F 2E 00 01 00 00 00 00 00 00 00 00 00 00 00 00 D1 06 (00) Sat 12/12/2015 07:46:17 PM : [iNST-SRX ] 02 50 33.14.C5 22.80.0B 2B 2E 00 (00) Sat 12/12/2015 07:46:17 PM : [std-Direct Ack] 33.14.C5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/12/2015 07:46:17 PM : [iNST-ERX ] 02 51 33 14 C5 22 80 0B 11 2E 00 01 01 00 00 20 20 1C FE 05 00 00 00 00 00 Sat 12/12/2015 07:46:17 PM : [Ext-Direct ] 33.14.C5-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Sat 12/12/2015 07:46:17 PM : [D2D EVENT ] Event [33 14 C5 1] [OL] [255] uom=0 prec=-1 Sat 12/12/2015 07:46:17 PM : [ 33 14 C5 1] OL 255 Sat 12/12/2015 07:46:18 PM : [D2D EVENT ] Event [33 14 C5 1] [RR] [28] uom=0 prec=-1 Sat 12/12/2015 07:46:18 PM : [ 33 14 C5 1] RR 28 Sat 12/12/2015 07:46:18 PM : [iNST-TX-I1 ] 02 62 33 14 C5 0F 1F 00 Sat 12/12/2015 07:46:18 PM : [iNST-ACK ] 02 62 33.14.C5 0F 1F 00 06 GOF (FLAGS) Sat 12/12/2015 07:46:18 PM : [iNST-SRX ] 02 50 33.14.C5 22.80.0B 2B 1F 08 GOF (08) Sat 12/12/2015 07:46:18 PM : [std-Direct Ack] 33.14.C5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Sat 12/12/2015 07:46:18 PM : [33 14 C5 2 ] Start : Adding device to ISY Sat 12/12/2015 07:46:18 PM : [33 14 C5 2 ] Finish : Adding device to ISY was Successful Suggest connecting KPL to extension cord and plug into PLM circuit for test purposes.

Yes. A 6 button dimmer can be configured as 8 button and visa versa. It has to be done manually using procedure in KPL User Guide. If currently defined to the ISY, delete the KPL, change the button configuration and add the KPL back.

Here is the event trace for a Program issuing a "Set 'Garage / Opener-Relay' On". The Blue 0x02 indicates Relay Wed 12/09/2015 07:38:12 PM : [iNST-TX-I1 ] 02 62 1C FD D5 0F 11 02 Wed 12/09/2015 07:38:12 PM : [iNST-ACK ] 02 62 1C.FD.D5 0F 11 02 06 LTONRR (02) Wed 12/09/2015 07:38:12 PM : [iNST-SRX ] 02 50 1C.FD.D5 22.80.0B 2B 11 02 LTONRR (02) Wed 12/09/2015 07:38:12 PM : [std-Direct Ack] 1C.FD.D5-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 I'll go through the other data and post conclusions. The Identical/ignored link records are three link records that have been deleted (start with 0x22) and the End of List entry (starts with 0x00). The link records are fine.

Thanks for the additional trace data. The I/O Linc Relay is not in the event trace. Since the I/O Linc Relay was a Responder at some point I would check the I/O Linc link table for a half link. Right click on I/O Linc Sensor, click Diagnostics | Show Device Links Table. Post the Show popup or the .xml file from the Show "Save" button. Could be a wiring problem where the wires between I/O Linc and garage door opener short out. If the I/O Linc Relay is connected to a multi button garage door opener those connections could be an issue. Also possible an RF remote garage door opener is activating the door movement.

"The other Switchlinc will go from zero to the preset Dim level on the first press but on the second press only the LED's go to Full on, the lamps stay at the Dim level. " Is this when the "other" SwitchLinc is pressed On? If so the described action is normal Insteon operation. The non-load SwitchLinc turns the load SwitchLinc On because it is a Responder to the non-load SwitchLinc. The load SwitchLinc turns On to the Responder On Level. The Responder On Level does not change regardless of the number of times non-load SwitchLinc is turned On. For the non-load SwitchLinc to turn the load SwitchLinc full On requires a fast double tap of non-load paddle to generate a Fast On.

What is 36.88.5E? What turns On I/O Linc Relay? Nothing in event trace shows I/O Linc Relay activity. If the I/O Linc Relay moved the door it happened earlier in trace. Could be an RF remote signal from a garage door remote. Need more of earlier trace.

Just to be clear, there are no "terminate" conditions or Then/Else clause actions.

Any Time. Since a Scene is not invoked from KPL changing to non-toggle Off and the Program trigger to Off is easiest. However, either approach will work. Post back if you have trouble.

The KPL button can be set to non-toggle Off mode. The button blinks twice and ends in the LED Off state. The Program must be changed to trigger with an Off command rather than an On command. EDIT: this does not work if "good bye" is dependent on a Scene On invoked by the KPL button. Then have the Program turn the KPL button Off with a Scene Off that has KPL button as Responder. Set Scene 'kplbuttonasresponder" Off

jerlands When a Program's trigger conditions change/occur, the If is evaluated. When the If evaluates is dependent on whether there is an active Wait/Repeat. When the Program is in a Wait or Repeat the If is evaluated immediately. When the Program is executing an Then/Else clause without Wait/Repeat the If is evaluated when the current executing clause completes.

jerlands "What I'm trying to clear up in my thick skull is how Wait and Repeat interact with the conditions of the program, and right now I don't think they do. Should Wait or Repeat be active and the program status change to false (in the case of Else usage) I don't believe the conditions are reevaluated but rather the program terminated as though it had completed the Else structure because Wait and Repeat are acting more like placeholders that allow termination at that point if there is a status change." Not correct. When a Program is in a Wait or Repeat and the trigger conditions change/occur, the Wait/Repeat is terminated and the If clause evaluated. When the If evaluates to True the Then clause executes (as in my post #30 Program). When the If evaluates to False the Else clause executes. What happens when the If reevaluation invokes the Then or Else clause depends on the statements in the respective Then/Else clause.