1 hour ago, oberkc said:

Allow me to offer further clarification.  The fact that this KPL controls a scene does not preclude putting it into another scene (as responder).  I believe the correct thing to do would be, as suggested, to put this button into a newly created scene.  Turning that scene on/off will turn the KPL button on/off.  If you turn off the button, the next time you press it will be to turn it back on, which will initiate the scene.

I have the KPL that controls the scene to non toggle on, which makes the KPL always on. If I set to non toggle off, then when I press the KPL, it turns off the lights set to be off but doesn't turn on the lights set in the scene to be on. 

6 hours ago, smarthome_newbie said:

If I set to non toggle off, then when I press the KPL, it turns off the lights set to be off but doesn't turn on the lights set in the scene to be on. 

Yes, that is what I would expect to happen.

9 hours ago, smarthome_newbie said:

I have the KPL that controls the scene to non toggle on, which makes the KPL always on. If I set to non toggle off, then when I press the KPL, it turns off the lights set to be off but doesn't turn on the lights set in the scene to be on. 

As a suggestion try this:   Set the button to "non-toggle off", don't include the button in any scene.  Then make a program that has:

---------------------------

If CONTROL {your button} is Off

then

Whatever you want to do when that button is pushed.

Else

--Nothing-- (there is no path to else in this case)

-----------------------

this keeps the button light off all the time.  When you press the button the light will briefly flash on then go right back off.

 

EDIT TO ADD:  Just because the button is send OFF to the ISY to trigger the program doesn't mean that you are limited to OFF functions.  the THEN body of the program can be used to do anything, including turning devices on or off, scenes on or off, setting varriables , enabling/disabling other programs, etc.

Edited August 30, 20205 yr by MrBill