I have several places where I want the "on" command to switch on only some of the lights, but the "off" command to switch off ALL the lights. EG I have a basement with a workroom and a playroom. I want the basement keypad "on" to turn on the playroom only, but when if I turn on the workroom light manually, I want the keypad "off" command to turn off the playroom AND workroom.

I can't seem to get this to work with "scenes" I can get it to work if I add individual "workroom light 1 off" and "workroom light 2 off" in a program, but not if I create 2 scenes. "playroom" and "all basement" set the keypad to control playroom and write a program that says "keypad Status is Off then "set all basement off"

Why does this not work?

@scholarwarrior , what you are describing should work. I use something similar for my basement office that is controlled by a SWL Dimmer on the stairs.

• The SWL dimmer is the controller for the scene BSMT Entry. When turned on scene members BSMT Fam Sconce and BSMT Office activate.

• When I exit the basement I turn off the SWL dimmer which turns off the same two scene members.

• The SWL OFF also triggers a program that turns off the BSMT Scene. The 3 second wait is to prevent collisions between the ISY and scene cleanup requests being sent by the SWL Dimmer.

BSMT Off - [ID 0009][Parent 0004]
If
        'Basement / BSMT Stair' is switched Off
Then
        Wait  3 seconds
        Set 'Basement / SC BSMT' Off
Else
   - No Actions - (To add one, press 'Action')

Well, I don't know how to get the Admin Console to do 'Basement / BSMT Stair' is switched Off

I only see "status is" Not sure what selections to use which would result in "is switched off"

I have "sechedule" "condition" "action" and "comment" and none have "is switched off"

Ok, sorry. "Control x is On" translates to "is switched on" Now it works. Thanks!

So follow on question: there's a delay when I do this with an EISY program vs being part of the scene. Is there a way to eliminate the delay? It does not seem to be the "ramp" delay of the keypad. i.e. it behaves the same no matter what I set as "ramp rate" on the keypad. So I push on, light on keypad goes to on immedately, then there's an approximately .5 second delay and the green led at the bottom of the keypad flashes, and then the program executes the "scene on" command.

9 minutes ago, scholarwarrior said:

So follow on question: there's a delay when I do this with an EISY program vs being part of the scene. Is there a way to eliminate the delay?

That illustrates the benefit of the Insteon peer to peer commands through links. Otherwise the eisy has to receive a command, process it, and issue another command to the device. So scenes are always preferable for this reason.

34 minutes ago, scholarwarrior said:

So follow on question: there's a delay when I do this with an EISY program vs being part of the scene. Is there a way to eliminate the delay? It does not seem to be the "ramp" delay of the keypad. i.e. it behaves the same no matter what I set as "ramp rate" on the keypad. So I push on, light on keypad goes to on immedately, then there's an approximately .5 second delay and the green led at the bottom of the keypad flashes, and then the program executes the "scene on" command.

Using a device to trigger a program that in turn sends commands back to the trigger device, has been documented to cause collisions that can produce all-on/all-off events. In short, it's an ISY no-no. The 3 second delay that I show in my program is intended to eliminate the collisions. https://wiki.universal-devices.com/index.php?title=INSTEON_Random_All_On_Events

If you want to eliminate the program delays, I would suggest 2 separate KPL buttons controlling 2 separate scenes:

1. KPL button 1/scene 1. KPL button 1 is a "Non-Toggle" On button that is controller for your scene 1. It will ONLY send "on" commands to the scene. Include KPL button 2 in this scene as a responder.

2. KPL button 2/scene 2. KPL button 2 is a "Non-Toggle" Off button that is controller for your scene 2. If will ONLY send "off" commands to the scene. Include KPL button 1 in this scene as a responder.

This should eliminate the delays associated with programs while also preventing communication problems.

You can access the KPL "Buttons Toggle Mode" at the buttom of your KPL screen in the Admin Console. I have many instances where I use the Non-Toggle [off] on KPL's. I use them as monitors around the house (Outside, basement, 1st floor, 2nd floor and House). If the button is ON, pushing it sends an Off to all scene members (1st floor as an example). Helps when I leave something on in the basement and I'm going to bed. I can hit a button on my bedroom KPL rather than "running the stairs".