LeeG

Happy to help. Thanks for posting back the results.

Repeat and Wait statements can be interrupted by another Program trigger. If Control 'LL - Stairs / Call Upstairs' is switched Off And Status 'Great Room - Sconces (North)' is Off Then Run Program 'Program2' (Then Path) Else - No Actions - (To add one, press 'Action') Program2 If Then Repeat 3 times Set 'Great Room - Sconces (North)' On Wait 1 second Set 'Great Room - Sconces (North)' Off Wait 1 second Else

As soon as the Program changes the Status of 'Great Room - Sconces (North)' the Repeat is terminated by the Program being triggered with a False state running the Else. One approach is to put Repeat loop in second Program so the trigger of the first Program does not affect the Repeat.

The SwitchLinc Local On Level has two modes of operation that are set with the SwitchLinc itself. Local On-Level Default = 100% (fixed brightness) The local on-level is the brightness that SwitchLinc’s connected load will come on when turned on at SwitchLinc paddle. Local on-level can be set to any one of 32 fixed brightness levels (3% to 100%) or “resume bright” (brightness prior to last being turned off). Page 12 of 17 Rev: 7/24/2012 10:26 AM To set local on level to a fixed brightness level 1) Adjust SwitchLinc to desired brightness when controlled locally 2) Tap Set button SwitchLinc will beep 3) Test by turning SwitchLinc off and then back on (via the paddle) SwitchLinc will turn on to new local on-level To set local on level to the brightness level prior to being turned off 1) Turn SwitchLinc off 2) Tap Set button SwitchLinc will beep 3) Test: a. Brighten SwitchLinc to a random brightness level (e.g. 75%) b. Turn SwitchLinc off c. Turn SwitchLinc back on Light will turn on at the defined brightness level

First look at the Green LED next to the wire connections. Is LED turning On and Off in sync with door movement? If Green LED indicates door movement correctly, right click on Sensor node and select Restore Device. This will rebuild device link database. If that does not resolve the problem select Files | Restore Modem (PLM) to rebuild the PLM. The older PLMs tend to fail around the two year mark. If the I/O Linc still does not report status changes either it has failed or a comm problem exists between I/O Linc and PLM (more likely than I/O Linc failure).

tome The Leak Sensor is not sealed. Flip it over and look for a slot along the outer edge of the bottom section. A Leak Sensor battery is expected to last 10 years so it is not likely to need a new battery. If you do take it apart be sure the top, which holds the battery in place, is correctly positioned relative to battery location.

The PLM connects to the ISY with the cable that has RJ-45 connectors. The ISY should be powered Off when the PLM is connected. If the ISY boots up without the PLM it enters Safe Mode. Connecting the PLM at this point is not detected by the ISY because the PLM does not identify itself.

Good to hear problem is solved.

A Range Extender can be plugged in almost anywhere. Did you determine that was the problem? A subpanel itself does not cause problems. I have two subpanels neither of which cause problems. Adding a Range Extender will not cause a problem so there is no harm in trying that solution.

jmed999 Move the old EZFlora's out of Folders, run Replace ......., move the old EZFlora names back to the Folders after the reboot of the Admin Console. The Admin Console closes at the end of a Replace so that two EZFlora devices do not have the same Insteon address. I would also suggest moving to 4.2.30 which is an Official release. Thanks Jimbo

Many devices no longer support a 9 minute ramp rate because that would be a 0x00 value. The equivalent of not setting a Ramp Rate value. Set the Ramp Rate to 8 minutes. EDIT: from the KeypadLinc Specs 0.125 to 9 seconds if programmed locally, 0.125 seconds to 8 minutes if programmed remotely via software

First thing to verify that the two 120v legs are properly coupled. Tap the PLM Set button 4 times and verify that the Range Extenders/Access Points are on opposite 120v legs. Then see if there is something common about the devices that show a delay in turning On. Are they on the same circuit, same room or area of house. What else is powered by that circuit, a TV, an appliance that is generating noise, something that requires a FilterLinc to isolate it. Identifying comm issues is a process that may take some time to identify the cause.

Waiting for information on how the 2 KPL's are actually wired. Recollection does not help. Are both KPL's, Black to Line and White to Neutral and with one with Red wire connected to Load.

Add the new EZFlora's to ISY using dummy names. Right click on Zone 1 of one of the failed units and select Replace 'oldezflora' with ...... which produces a list of EZFlora's to select from. Select one of the new EZFlora devices. The old EZFlora under the old EZFlora name will have the Insteon address changed to the selected new EZFlora. The new EZFlora dummy name will be deleted and the Admin Console closed. The existing Scenes and Programs using the old EZFlora name remain, using the new EZFlora Insteon address. I believe the old EZFlora and new EZFlora cannot be in a Folder during the Replace function.

This is a 3 way switch configuration. If the Red switch wire of both switches are connected to the same load it does matter.

The event trace shows good comm to 34.DD.42 so hard to explain the previous error.

What ISY firmware and UI is in use? Use New INSTEON Device. Enter Insteon address, Name of choice and Auto Discover. Run Tools | Diagnostics | Event Viewer at LEVEL 3 while using New INSTEON Device. Post the event trace.

The non-load KPL requires a Line and Neutral connection with the Red load wire capped. The load KPL requires a Line and Neutral connection with the Red wire powering the load. Be sure this KPL is not replacing a two wire switch. What type load? The KPLs need to be cross linked. Define a single ISY Scene Add the two KPL buttons as Controllers

doctorjerry I was a little confused about which message should be suppressed, first thought Closed message but detail about Wait sounds more like the Open message (and Closed message) should be suppressed. Also need to know if the I/O Linc Sensor is On or Off when Open and if Trigger Reverse is used. Suggest posting the current Open and Closed message Programs along with which message should not be issued as well as info on I/O Linc Open/Close Sensor state and use of Trigger Reverse.

I tested on 4.3.1 before my post. The Program triggers when the Folder becomes True. The Variable becoming > 0 makes the Folder True. My test Program turns on D1. Fri 05/08/2015 05:28:31 PM : [VAR 2 6 ] 0 Fri 05/08/2015 05:29:19 PM : [VAR 2 6 ] 10 Fri 05/08/2015 05:29:19 PM : [ X10] D1 Fri 05/08/2015 05:29:19 PM : [X10-RSP ] 02 63 A6 00 06 Fri 05/08/2015 05:29:19 PM : [ X10] D1/On (3) Fri 05/08/2015 05:29:20 PM : [X10-RSP ] 02 63 A2 80 06 Fri 05/08/2015 05:29:20 PM : [X10-RX ] 02 52 A6 00 Fri 05/08/2015 05:29:20 PM : [ X10] D1 TestFolderVar - [iD 002A][Parent 0029] If Folder 'Folder2' is True Then Send X10 'D1/On (3)' Wait 5 minutes Send X10 'D1/Off (11)' Else - No Actions - (To add one, press 'Action') =================================================================================== Folder2 - [iD 0029][Parent 0001] Folder Conditions for 'Folder2' If Status 'KPL 8 Dimmer v40 / KPL 8 Dimmer v40 - G' is 100% Or $State_6 > 0 Then Allow the programs in this folder to run.

The Folder Status can be checked in the Program. This check can be Ored or Anded with existing Program checks. TestFolderVar - [iD 002A][Parent 0029] If Folder 'Folder2' is True Then Else - No Actions - (To add one, press 'Action')

I am happy with my Insteon system, about 10 years now. Found out early that analyzing and correcting problems was the only way to go. The band-aids I tried in the early years caused more issues than taking time to learn the Insteon protocol so the problem could be fixed. Insteon is DIY which does take time to learn. If not able to do that Insteon will likely be a frustration for ever. The EZFlora is likely the same issue as the PLM. The Smartenit devices are built around what would be a SmartLabs PLM with a Smartenit daughter card. Have not had to purchase any new Smartenit devices for some time. Suspect my Smartenit devices were built around a PLM that was manufactured before the cap issue surfaced.

Should not be related to how the devices were originally located. Insteon Scenes do not work that way. The Scene devices should respond at the same time. The 1-2 second delay indicates one or more devices in the Scene did not "hear" the initial Scene command (Group Broadcast message) which is not ACKed and not retried. After the Group Broadcast message each Scene device is sent a device specific Group Cleanup Direct message which is ACKed and retried as needed. Normally this followup Group Cleanup Direct message is redundant but does insure all devices react to the Scene even when the Insteon network is not working well. The delay indicates some devices are not hearing the initial Scene message. Could be noise where a filter(s) is needed, lack of good coupling, something that is degrading the Insteon network.

Post # 5, Program Heartbeat.

Sorry but I don't understand the problem. "is switched On" and "is switched Off" are part of every ISY. Maybe your ISY Heartbeat Program is using "If Status" rather than "If Control"? Do not use If Status because the Wait will timeout.