Sub-Routine

Burak, are you right clicking the device and selecting Remove? Not from a scene, but from My Lighting? There should not be any failures then as the ISY should ignore the device itself and just delete any other links from/to it. Rand

Exactly. Rand

If you are having issues only since installing the KPL I would have to imagine the KPL is not playing well. Pull the set button on the KPL to remove it from the circuit. If your other devices then communicate properly we will have to blame the KPL. Rand

Hello Burak, This will be useful for anyone who uses Local Control with a LampLinc. With this feature implemented the ISY will be aware when someone uses local control. Devices can be linked to the LampLinc as responders, so one lamp plugged into a LampLinc could turn on a scene. Rand

Hello cnutco, Just to add to what you will find in that link, since you moved one Access Point you should be sure to re-sync AP #2. That made a difference in my home. Rand

It could well be. You can test by using an extension cord. Do you have Access Points? Here is another page that may help: Communication Troubleshooting. Rand

I'm not sure but it may be the NTP sync. I can't find it in my Log file, but I have also seen it in the Event Viewer. Rand

There are a couple of ways to accomplish your goal Joe. You could make a new scene for the motion sensor that doesn't include the KPL button and check the status of that button. You could add a different KPL button to the motion sensor scene for an indication of motion. If Control 'Garage Motion Sensor' is switched On And Status 'Garage KPL' is Off Then Set Scene 'Garage Lights Motion' On Else - No Actions - (To add one, press 'Action') If Control 'Garage Motion Sensor' is switched Off And Status 'Garage KPL' is Off Then Set Scene 'Garage Lights Motion' Off Else - No Actions - (To add one, press 'Action') Or You could use different levels for your light, for example, the switch could set it to 90% and the motion sensor, 85%. Then, unless you happen to dim the light to exactly that level, you could check that to determine if the MS should turn the scene off. If Control 'Garage Motion Sensor' is switched On And Status 'Garage Light' is not 85% Then Set Scene 'Garage Lights Motion' On Else - No Actions - (To add one, press 'Action') If Control 'Garage Motion Sensor' is switched Off And Status 'Garage Light' is not 85% Then Set Scene 'Garage Lights Motion' Off Else - No Actions - (To add one, press 'Action') Rand

As long as you have more than one line in the 'If' section of the program, and the 'If' section is selected, you should see Add... Thank you! You're welcome! Rand

Hello strahan001, Depending on the Schedules, Conditions, and Actions selected various applicable commands are displayed. Add And (...) and Add Or (...) are available when multiple conditions are used in a program. These are used to add parenthesis, allowing you to group conditions. Set is automatically prepended to any Insteon command. Rand

I touch the Dim. Rand

RLAV is correct, the difference between tap-linking and using the ISY (besides the ease) is that the ISY becomes a member of every scene. This allows the ISY to track the status of the devices in the scene as well as control the scene. Rand

Hello cnutco, This sounds very much like a communication issue. Please use the Event Viewer to see if the switch presses are being noticed by the ISY. ISY-99i/ISY-26_INSTEON:Using_the_Event_Viewer. Can I phone or email you tomorrow? Contact Rand

Is this really true? It seems that a given program would only be reevaluated when a device or control which is included in that program's if clause changes. Otherwise a program like the following would not work correctly. (And it does work correctly!) To follow up on Michel, again, as far as I know, all programs are parsed for Conditions that match a change. So when your kitchen light is switched your example would run. If your hallway light changed your example program would be considered (reevaluated) by the ISY and not run because the hallway light is not in it's Conditions. Consider a program based on a Schedule. Every time the clock changes in the ISY every enabled program will be reevaluated. If the time change has no effect the program is not run. If the program is sensitive to that time then it is run. Please see this Wiki page: ISY-99i/ISY-26_INSTEON:Scope%2C_Precedence_and_Execution_Order Rand

I think this is it: ISY-99i/ISY-26_INSTEON:Linking_a_KeypadLinc#KeypadLinc_Faqs Rand

The properties are stored in the Responders. A Controller only knows which devices are in a scene. This is why many devices can respond at once to a scene command (Insteon). After the scene command is sent the controller sends individual commands to the devices in the scene in case one (or more) of them didn't hear the scene command. Those are called clean-up commands. Rand

AFAIK, every program is reevaluated any time the ISY sees a change in any device. Using a Query would be the only way ISY would know if a device was changed in some other manner. If you post your program(s) we can better analyze the problem. Right click on the program, Copy to Clipboard, Paste between Code tags here. Thank you, Rand

I see the requester to put the MS in linking mode is not called for the Links Table function. I will enter this as a bug. To read the Links Table the MS must be in linking mode. If you linked the Motion Sensor in one of the 2.6.x betas you will most likely have to Remove the MS from the ISY and re-link it rather than Replace it. Rand

Hello KEoqgtkQ, If you added the device to the ISY using option 3, keep existing links, then the tables will match although the links are broken. I'm afraid the only way to then remove the links is to remove the device from ISY, factory reset it, and add it back to ISY. Please use option 1, remove existing links. Creating a topography (Tools menu) before removing the switch will allow you to view a record of the scenes it was in. That should make it easier to add the switch back to the way you had it. Rand

Are you saying the CL is not in the tree view of the scene? A ControLinc will not be in the list of responders because it is only a controller. Other Controller only devices are RemoteLincs and MotionSensors. The sensor does not have any separate options, the Option button is there so the function can be called when viewing either the sensor or relay. Rand

I'm glad the program works for you Devon. I almost put this in the program yesterday. You just need a condition to check the dining room switch: If ( Status 'Kitchen Motion Sensor' is Off And Status 'Motion Sensor 2-Sensor' is Off ) And ( Control 'Kitchen Motion Sensor' is not switched On Or Control 'Motion Sensor 2-Sensor' is not switched On ) And Status 'Dining Room' is Off Then Wait 1 minute Set Scene 'Kitchen Low' Off Else - No Actions - (To add one, press 'Action') You may need to make some changes to this: If Status 'Dining Room' is not Off And Control 'Dining Room' is not switched On Then Wait 1 hour Set Scene 'Dining Room Low' Off Else - No Actions - (To add one, press 'Action') Our best guide is the Wiki, the User_Guide and the How-To_Guide contain some step-by-step examples. Rand

On means 100% or are you comparing actual levels? The ISY anticipates target levels, but if a Query is performed during a level change the actual level is reported and evaluated. I think all you need to add to your program is a Wait before you switch the KPL buttons. You should allow ~1 second for every 4-5 devices. The ISY runs programs based on events. An event occurs when any Schedule or Condition changes. A Condition can be any of the selections available: Status, Control, etc. When a program sees an event included in it's Conditions it is evaluated and runs the Then or Else. So it could be a switch or a schedule or a program, etc. that activates a program. Rand

Hello Devon, I have two motion sensors and did some experimenting. Finally a use for the parenthesis You should use two programs. If Control 'Kitchen Motion Sensor' is switched On Or Control 'Kitchen Sensor 2' is switched On Then Set Scene 'Kitchen Motion Fast' On Else - No Actions - (To add one, press 'Action') If ( Status 'Kitchen Motion Sensor' is Off And Status 'Kitchen Sensor 2' is Off ) And ( Control 'Kitchen Motion Sensor' is not switched On Or Control 'Kitchen Sensor 2' is not switched On ) Then Wait 1 minute Set Scene 'Kitchen Motion Slow' Off Else - No Actions - (To add one, press 'Action') I use 2 different scenes; the On scene has a quick ramp rate and the Off scene has a longer ramp rate. This gives one a chance to move if the lights begin to fade. The motion sensor will only fire an On after it has sent an Off. The timeout can be adjusted using the motion sensor options: Linking_a_Motion_Sensor. I have mine set to 30 seconds but of course you should use the parameter that best fits your needs. Rand

If the removed device is still in the ISY right click it and select Remove. Create a Scene with the two devices in it and then remove them. Rand

AFAIK Gary has this working by keying off a KPL button: viewtopic.php?t=2305&highlight=garage+door. Rand