Scene or Program

[jmed999]

If I want remotelinc button A to turn a light on and B to turn it off I can use a scene with the remotelinc buttons and the light or I can just do it via a program...what's the difference?

 

Thanks!

[Michel Kohanim]

Hi jmed999,

 

Scene is always better since it's native to devices. This said, for your requirement, you need non-toggle RL buttons and I am not sure how to do that.

 

With regular toggle buttons, your off scene will still turn the light on.

 

With kind regards,

Michel

[jmed999]

I know how to make them non-toggle. What do you mean by "native"?

 

Thanks!

[Brian H]

Page 9 of the RemoteLinc 2 manual shows how to set it to non toggle 8 button.

Always sends an On and not an alternate of an On then an Off.

Older Remotelinc doesn't have any non toggle modes that I can see.

[jmed999]

Page 9 of the RemoteLinc 2 manual shows how to set it to non toggle 8 button.

Always sends an On and not an alternate of an On then an Off.

Older Remotelinc doesn't have any non toggle modes that I can see.

 

Yeah this I know how to do. I was just wondering if a scene was better or a program and I'm not sure what native means. Thanks for the response!

[oberkc]

I assume "native" refers to the fact that scenes work bteween devices withou need for intervention by the isy. This can tend to be a little faster reponding.

[BobH]

You are correct -- native mode means that all of the control and response is done by the devices based on device links.

 

There are pros and cons of the "scene" vs. "program" question. As Michael points out, the scene offers the advantage of direct (native) action between the controller (the Remotelinc2) and the light. This eliminates any time delay and dependence on the ISY as the controller. The down side of the scene is that it offers no other means of adding intelligence to the activity. Using a program provides flexibility and allows more control of the results.

 

The original post indicated a desire to use non-toggle buttons to allow one button (A) to turn the light on and another button ( to turn the light off. Since the non-toggle mode for the Remotelinc2 appears to always provide an "ON" action, the easiest way to implement the second part of the desired control would to use a program looking for the "button B ON" to initiate the OFF command to the scene via the ISY. The button A control action (turn the light on) could either be performed by a similar program looking for the "button A ON" to initiate the ON command to the scene via the ISY or alternatively the ON could be performed by a scene linking the light with button A as the controller. I think that most people use the hybrid approach (scene + program) for this type of control, using the direct link (native mode) for ON (similar to allowing a motion detector to turn a light scene ON) and a program to manage the OFF control (for motion detectors, typically after some delay or in this case based on another input from the Remotelinc2).