LeeG

It is normal for the ISY to write updates when changes are made. If something prevents all updates from being written (usually a comm issue) the update is queued and a Green Icon placed to the left of the node. Multiple nodes could have queued updates. When one device is told to update I think the ISY will try to finish anything queued. I have always used a Pro so not sure about this. There is no specific option to drive updates to All devices. Note that battery powered devices have to be updated one at a time. There is a new capability in 4.2.21 to update Motion Sensors under Program control which may work on other battery devices but this has to be determined.

If Control and if status have their own set of rules. If Control triggers the Program when the inbound command matches what is being looked for, On in this case. If Control does not trigger a Program when the device/button is turned On by something other than the device paddle/button being pressed On. If Status triggers a Program when the Current State changes to match the condition being checked for. If Status does not trigger a Program when Current State does not change states. Turning a device/button On twice in a row triggers the Program once when Current State changes to On. The Program(s) that are checking Responder Status of InlineLincs should be deleted. No need to monitor a Responder.

If Control and If Status are both triggers. Both can trigger a Program to Run If Control is looking at the commands flowing from the device. If Status is looking at Current State of the device.

If Control 'kpl 1 B' is switched On Or Control 'kpl 2 B' is switched On Or Control 'kpl 1 C' is switched On Or Control 'kpl 2 C' is switched On Then Set Scene 'Scene 3' On Else If Status 'kpl 1 B' is Off And Status 'kpl 2 B' is Off And Status 'kpl 1 C' is Off And Status 'kpl 2 C' is Off Then Set Scene 'Scene 3' Off Else

Those last two Icons are On an ISY Pro (see attachment) Right click on device node and select Write Updates ..... if there are pending updates (Green Icon with 1011 inside to left of node)

Sorry, what is part 1 problem?

Make sure Program is not in Folder with False State Make sure Program is Enabled Run Tools | Diagnostics | Event Viewer at LEVEL 3 Double tap Garage Light and watch event viewer for command sent by device. ToggleLincs can be tricky getting them to send a Fast xxxx.

If Control 'kpl 1 button H' is switched Off Or Control 'kpl 2 button H' is switched Off Then Set Scene 'Scene 1' Off Set Scene 'Scene 2' Off Set Scene 'Scene 3' Off Else

Using "If Status 'togglelinc' is On", Yes Using "If Control 'togglelinc' is switched Fast On" , No - this triggers when the ToggleLinc itself is turned Fast On, not when turned Fast On by something else

All the Controller buttons should be On. Also the 2477 should be a Controller so the KPL buttons turn On if the SwitchLinc itself is turned On. Click the Red Controller button below the ISY Scene name being used and check the On Levels of the other Controllers.

Chose which is most important to do directly with a Scene and which requires an ISY Program with another Scene. The KPL button that cannot be added as a Controller to the above Scene must now be a Controller of some other Scene. Remove it as a Controller from that Scene, add it as a Controller to the above Scene, use an ISY Program to monitor the new KPL button and have the Program control the Scene that was controlled by the new button. Without the ISY (all native Insteon) the above could not be done at all.

"the ISY will not permit you to add a scene to a scene" That is an Insteon limitation, the button/device can control one Scene only. Otherwise Scene loops could develop.

From an older KPL User Guide Local On-Level The Local On-Level is the brightness that the light(s) physically wired to KeypadLinc will come on at when turned on locally. The default is 100%. Local On-Level can be set to any one of 33 settings 32 fixed brightness levels (3% to 100%) Or “Resume Bright” • Previous brightness level is stored when turned off and recalled to that level brightness when turned back on Page 9 of 24 Rev: 12/22/2011 2:21 PM Page 10 of 24 Rev: 12/22/2011 2:21 PM To set KeypadLinc’s Local-On-Level: 1. Press & hold On and/or Off (or Main in 8-button configuration) until the connected light is at the brightness desired when turned on locally (turn the light off if you wish to use the “Resume Bright” feature) 2. Tap KeypadLinc’s Set button KeypadLinc will (Beep) 3. Test the Local On-Level settings by tapping the On/Off or Main There have questions on the forum about Resume Bright From SwitchLinc User Guide. 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). 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 Page 11 of 16 Rev: 3/29/2013 10:32 AM 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

What ISY release had KPL Options? This is 4.2.18 without Options button

Yes, but it has to be done with ISY Programs. The function you describe cannot be done with a single Scene. A Program will have to monitor the Status of the devices and turn On the KPL button as appropriate. Also the On and Off commands for a given button use the same Scene which can contain the common devices for On and Off. However, the additional devices for Off have to be in another Scene another Program turns Off.

Jumper 1, which reduces the motion sensor sensitivity, is the only jumper controlled option when Jumper 5 is in place. All the other jumper options are set with the ISY when Jumper 5 is in place.

Example of motion sensor link database. Link 0 is Controller link for Group 01 (sensor node) pointing to PLM as Responder Link 3 is Controller link for Group 01 (sensor node) pointing to another Responder

1. Should jumper #5 be on both pins? Yes. Jumper 5 is required to allow an application (ISY in this case) to set motion sensor options. 2. Should Jumper #4 be installed. No. Those options are handled by the application/ISY ewhren Jumper 5 in place. 3. Can I run a full report with my ISY to list and devise that is linked as a controller? Yes. Put the motion sensor into linking mode and run Tools | Diagnostics | Show Device Links Table. Link records that start with E2 are Controller link records. Regarding #1, a motion sensor in On Only mode will always show as On as that is the only command the Sensor node sends.

Ok, thanks. I would not put much expectation those functions actually exist in the KPL.

My assumption is these two options would affect the number of Group Broadcast messages (first message sent by device). Today the battery devices send two of these messages. Seems to go along with the option for the followup Group Cleanup Direct message which is also not reacted to by my v.43 Hidden Door Sensors.

"Program Lock, LED on TX," This will be the last time asking. Where are these discussed in KPL doc?.

Teken Sorry, I missed your previous post. I do not see any change using those options. My Hidden Door Sensors are v.43 so a later firmware version may honor those options.

The question by the original poster is why does ISY not cover these for KPL. I am asking where in the KPL documentation these options are covered. Not saying they are not in the doc but I did not find anything on these options for the KPL.

Where in the KPL documentation (Sales page, Quick Start Guide, Owner's Manual) is information on Program Lock and LED on Tx?

With the Fan, FanLinc and wiring judged good, what is left?