LeeG

Scenes are used for device to device control and normally do not require any Programs. Programs are required when special things have to be done as in this case. When a KPL button is pressed On (button LED lights up) an On command is sent. That is what you want for most situations but in this case the other KPL buttons in the "Group" need to be turned Off. Secondary KPL buttons cannot be turned Off with an On command thus a Program is needed to recognize the On command and issue a Scene Off to turn the other KPL buttons Off. The Lights that are being turned On to some bright level can be turned On with a Scene without Program activity. An ISY Scene is created with KPL button A as the Controller and whatever devices to be turned On are defined as Responders with whatever On Level is associated with the KPL button. Many devices can be turned Off with an On command simply by setting the Responder On Level to 0%. Secondary KPL buttons are the exception. They will not turn Off with an On command.

Denis There are a number of approaches depending on how many Programs and Scenes you want to produce and manage. Secondary KeypadLinc buttons cannot be turned On/Off with Direct commands, thus the need for Scenes. Lets use KPL Secondary buttons A,B,C,D as exclusive buttons. Scene X has all 4 KPL buttons as Responders. Scene X will be used to turn Off all the related KPL button LEDs. Scene A has KPL button B,C,D as Responders. Scene B has KPL button A,C,D as Responders. Scene C has KPL button A,C,D as Responders. Scene D has KPL button A,B,C as Responders. Program X triggers with Off commands from any of the 4 KPL buttons. The Then clause invokes Scene X with an Off command to turn Off all involved KPL button LEDs. Program A triggers with an On command from KPL button A. The Then clause invokes Scene A with an Off command to turn Off B,C,D. Program B triggers with an On command from KPL button B. The Then clause invokes Scene B with an Off command to turn Off A,C,D. Program C triggers with an On command from KPL button C. The Then clause invokes Scene C with an Off command to turn Off A,B,D. Program D triggers with an On command from KPL button D. The Then clause invokes Scene D with an Off command to turn Off A,B,C. Lee

If a single KeypadLinc is involved the KPL hardware Button Grouping can be used although the ISY recommends against using the feature. How many KPLs are involved? That is, are KPL buttons A,B,C,D (or whatever buttons are being used) to be linked to any other KPL. If so a Program is needed as KPL hardware button grouping only works where the KPL button is physically pressed. It does not apply to other KPLs that may be linked to those buttons.

jdheltne I suggest using the Event Viewer to positively determine what happens when a Harmony button is pressed. That should show whether there is an IRLinc question or perhaps how Programs are coded and reacting. Lee

Not sure if you noted during the button add process but each button can be defined to toggle On/Off, non-toggle On only and non-toggle Off only. Click on Add Button to IRLinc Receiver to bring up the pop-up. There is a Cancel button on the pop-up so nothing has to happen. There are instructions on how to set the button modes on the pop-up.

The Program examples have a problem. Both Programs will be triggered when an On command is received. Depending on which one is dispatched last that will be the resultant status. Condition the Programs with additional Status check. If Control 'AV-Dim Button' is switched On And Status "some light" is On Then commands to turn off the lights If Control 'AV-Dim Buttom' is switched On And Status "some light" is Off Then commands to turn on the lights Or you can do it with specific commands. The On command turns the lights On. The Off command turns the lights Off.

I think you are correct but cannot verify that from direct experience with the credit card. I think pressing A Up arrow likely sends an On command for that Scene and A Down arrow likely sends an Off command for the same Scene. This can be verified by running Tools | Diagnostics | Event Viewer and selecting Device Communications Events (important step). Press the A Up arrow and look at the Insteon command sent. I think it will be an On command. Then press the A Down arrow and look at the Insteon command sent. I think it will be an Off command.

The IRLinc sends Insteon On/Off commands to the ISY just like any other Insteon device. The Program can be triggered with If Control "IRLinc button" is switched On.

"the IRLinc starts blinking, and when I try to add button, " Do you mean when you click OK on the Add Button to IRLinc Receiver popup? The sequence is to click on the Add Button to IRLinc Receiver first, then press the IRLinc Set button for 5 seconds, and so on. When the IRLinc LED is blinking click the OK button.

That will work. Did not realize Harmony had a specific automation entry for the IRLinc credit card buttons. If you want more buttons you can define a device to Harmony that is known to use NEC codes which is what the IRLinc is looking for. That would provide many more buttons to use on the Harmony remote than the credit card buttons provide. Whichever you chose then perform the Add Button to IRLinc Receiver. According to the IRLinc user guide the LEDs on the IRLinc will indicate when it recognizes an IR code.

philipx What you are observing is normal Insteon operation. When devices are cross-linked (one ISY Scene with both devices as Controllers of the Scene) pressing the paddle on either switch causes Scene (Group) commands to flow to all the linked devices. Individual Insteon devices do not have the capability to send Direct commands to another device. Only when an automation application is involved is it possible to send Direct commands. Direct commands do not use or require device linking. Direct commands work only on the device they are sent to. That is why when switch A is turned on with a Direct command switch B does not react even though switch A may be a Controller of switch B. Use Direct commands when individual device control is desired. Use the ISY Scene when all devices in the Scene should respond. This is Insteon architecture, not an arbitrary decision by the ISY. Lee

mielcarek Glad to hear it is working. I am assuming the ICON Dimmer is relatively new. What does the Admin Console show as the firmware level of the ICON Dimmer. Left click on ICON Dimmer in My Lighting tree. The top lines on the right show v??. Does this display as v00 or some number v39 for example. Just my curiosity. Thanks Lee

mielcarek Rather than use an ISY Program I suggest creating an ISY Scene. Disable the Program for now. Likely it will be deleted later. Under Link Management | New Scene define an ISY Scene. Under the My Lighting tree right click on the ICON Dimmer and select Add to Scene ...., adding the ICON Dimmer as a Controller of the Scene. After the ICON Dimmer has been added to the Scene as a Controller set the ICON Dimmer (Applied Locally) On Level to 40%. The Applied Locally values are in effect when the ICON Dimmer paddle is pressed On. In the My Lighting tree right click on the LampLinc and select Add to Scene ....., adding the LampLinc as a Responder to the Scene. Under the Scene name in the My Lighting tree, left click on the Red ICON Dimmer name. Set the LampLinc On Level to 40%. Now when the ICON Dimmer On paddle is pressed the ICON Dimmer will turn On to 40% as a result of its On Level (Applied Locally) field and the LampLinc will turn On to 40% as a result of the LampLinc as a Scene Responder On Level being set to 40%. There is no latency when using a Scene. When done with a Program there will be a slight delay as the ICON Dimmer On paddle press triggers the Program which then sends a command to the LampLinc to turn On at 40%. Both the Scene technique and the Program approach work. I think most folks will use a Scene in this case. If the Program approach is used, left click on the ICON Dimmer in the My Lighting tree and set the On Level (Applied Locally) field to 40%. Remove any Program initiated commands to the ICON Dimmer as they are not needed. Note: If the ICON Dimmer does not turn On to 40% after setting the On Level (Applied Locally) field (either with the Scene or the Program), power cycle the ICON Dimmer. Some devices must be power cycled for the Applied Locally value change to take effect. It is not necessary to power cycle the LampLinc for the Responder On Level to take effect. Lee

An I/O Linc Sensor requires GND to activate the sensor. The projector trigger could be hooked to a 12V relay. Then use the relay contacts to apply GND to the I/O Linc Sensor. Do not know if the projector trigger can energize a relay. The projector spec's should provide that answer. An alternative would be to use a Simplehomenet EZIO2X4. It has opto=isolated Inputs which will trigger with clean 12V DC. Again it depends on what the projector 12V trigger really is. The I/O Linc would be the less expensive approach if the projector trigger will energize a relay.

jdheltne The IRLinc does not support the ISY codes. The IRLinc supports the NEC IR code format. The ISY supports the RC5 IR code format. Sending an ISY RC5 IR format code would not be recognized by the IRLinc. You need to define a device on the Harmony remote that uses NEC codes. Then select that device to send IR codes to the IRLinc. The ISY default codes which are based on RC5 IR format play no role and cannot be used on the IRLinc which requires NEC codes. Lee

jdheltne I noticed the forum post on the Smarthome forum. Makes me think we have to go back further. First the IR definitions established for the ISY IR feature itself have nothing to do with the IRLinc. For each Harmony button used with the IRLinc, use Link Management | Add Button to IRLinc Receiver. This process will define an ISY node in the My Lighting tree for each Harmony button used with the IRLinc. Once that step is done the node can then be used in the Program If statement I described in my previous post. The ISY IR feature that allows the ISY to "see" IR commands with the IR sensor on the ISY itself is totally independent and unrelated to the IRLinc. To use the IRLinc, IR buttons must be defined which define ISY nodes. These IRLinc nodes are then used in Programs or as Controllers of ISY Scenes. Again, the IRLinc definitions work independent of the ISY IR feature. The ISY IR feature is not required and is not used in supporting the IRLinc. Lee

All Insteon devices communicate with the ISY/PLM using Insteon messages. IR messages are not sent over the powerline. For each IRLinc button defined there is a node in the My Lighting tree. That node will receive Insteon On/Off commands when the IR remote button is pressed. To trigger a Program the If Control “IRLinc button node†is switched On/Off statement can be used. The If IR Program variant is used for IR messages received directly by the IR feature of the ISY.

aweaver ISY Programs are generated using the ISY Admin Console GUI by selecting items from selection lists and data from input fields. There is no underlying programming language per se. What type thermostat is the App controlling? Lee

jdheltne What are you looking for/expecting from the IRLinc. It sends an Insteon command to the ISY, not an IR command. Lee

Don't see a way to do that directly. Will do more testing later today. What is a bit messy but works is use a Program True/False state. This Program True/False state represents the 5 minute time period from Program2 Last Run time for 5 minutes. Program is True during the 5 minute time period, otherwise False. Use this Program True/False state rather than checking directly for the 5 minute window. Messy for sure but functional. I have run this and the Program True/False state reflects the 5 minute window of Program2 Last Run Time. If From Last Run Time for 'Program2' For 5 minutes Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

I think the If variant for a condition would be as follows ..... If Control 'ICON ON OFF' is switched On And From Last Run Time for 'Program2' + 5 minutes For 5 minutes Then Run Program 'Program3' (Then Path) Set Scene 'SceneKPLBOnly' On Else In Scene 'SwitchLinc Dimmer' Set 'SwitchLinc Dimmer' 50% (On Level)

Variables were introduced in the first Version 3 image. See the following list of Topics dedicated to Variables. viewforum.php?f=68

Illusion You might think about doing a random check of 6-8 devices. Run a Show Device Links Table and then Compare to see that everything is in sync with a sampling of devices. The situation where it appears that the ISY has gotten out of sync with Scenes and link records could have happened several builds back, with no visible symptom until a device loses its link database and has to be restored. In this case the device could have more links than the ISY shows because the sample devices are still intact. Lee

Jsveom There is another thread reporting that depending on where a particular statement is located in the If construct the Program is either reporting True or False simply due to a different position of the single statement. That If is very complex and may have no relation to this question. Try adding the check for not 30% near the top, after the time definitions and see if that works. If not post the Motion Program with the not 30% statement in place. Lee

Jsveom When the backyard Scene has run does the Admin Console show 'Front Porch Light Switch' at 30%? Was this line removed "Status 'Front Porch Light Switch' is not On", or changed to not 30%? Lee