I am looking for a way to disable a scene (or at least prevent a controller from activating a scene) by the use of programs.

 

For example, with the use of conditionals on the folders in programs, I can simple disable a whole set of programs by setting the value of a 'flag' program to false.

 

If not, any ideas for the following scenario:

I have a keypadLinc2 remote that controls many scenes, I want to simply disable some of the buttons on that RL2 that control scenes when I give it to a family member who maybe sleeping in the guest bedroom. I could wire up buttons to control scenes via programs, however I cant find a way to implement the dim/bright capability programatically.

OK, just figured out how to implement scene control dim/bright/on/off with programs, but I will have to make seven? programs to do this:

 

Button Fade Down=Scene/device fade down

Button Fade Up=Scene/device fade up

Button Fade Stop=Scene/device fade stop

Button On=Scene/device on

Button Off=Scene/device off

Button Fast On=Scene/ fast on

Button Fast Off=Scene/device fast off

 

Seems like a lot, huh? So this still leads even more to my question, can I simply disable a device (RL2) from controlling a scene with the use of programs?

 

Thanks in advance.

There is nothing in the Insteon architecture that supports enable/disable of a Controller button. Once a Controller button/paddle and related Responders have been defined in a device the operation is independent of the ISY. Various Responders could be removed from some Scenes or the Controller button removed as a Controller of a particular Scene but this would have to be done through the Admin Console rather than an ISY Program.

 

Performing all Scene actions with ISY Programs can be done but it adds some latency to the action. Particularly the dim/bright actions are slow to stop because of the delay in issuing the Fade Stop. Takes some practice as the Stop Manual Change (Fade Stop) has to be initiated prior to where the dim/bright ramp should stop. As the homeowner you can do it with practice. Not sure a guest will handle it well.

 

How about dedicating a RemoteLinc2 specifically for guest use.

Thanks for detailed response. Dedicated remote sounds like best idea.