Using scene status in programs

[bsobel]

I realize there is not a direct way to use scene status in programs since the status of scene members can change after a scene is activated. What I'd like however is the ability to use a scene NAME in an IF statement and then (internally) have the ISY explode that into a series of AND or a series of OR statements. E.g. I'd like to say:

 

if status AND INDICATOR_LIGHTS_SCENE is ON then

 

that would automatically translate to

 

if status scene member 1 is ON

and status scene member 2 is ON

etc

 

Same idea with 'or'. I don't like the current fact the that a scene is a quasi container, but I still must manage the container (in scenes) and not sue that container in programs where I need to remember what items the scene contains.

 

Make sense to anyone else besides me?

Bill

[LeeG]

Some of the questions that come up whenever this feature is suggested is what does ON mean.

 

Scenes often have different values for responders.

 

Responder A= 20%

Responder B = 50%

Responder C = 100%

Responder D = Off

 

What should the If Scene be checking for?

 

Also, since whatever the checks, they can be done today it has not had a high priority.

[apostolakisl]

How about this?

 

Allow a program to be a member of a scene as a responder. Following the same rules as a device would follow for activating a scene on/off.

 

It would function as a "control" statement rather than a "status" statement. You could do it already if you had an unused kpl button that you put as a responder to the scene, and then had the program follow that kpl button. But who wants to waste a kpl button?

[bsobel]

Some of the questions that come up whenever this feature is suggested is what does ON mean.

 

Scenes often have different values for responders.

 

Responder A= 20%

Responder B = 50%

Responder C = 100%

Responder D = Off

 

What should the If Scene be checking for?

 

Also, since whatever the checks, they can be done today it has not had a high priority.

 

Lee, I would say that it would check whatever the IF condition is set to. E.g. if the statement is SCENE_X ON then any of those devices in ON state would trigger. The idea here is to better couple scenes/programs as today if I add/remove an item from a scene I need to possibly go update a program as well.

 

The other suggestion given of letting a program be a responder to a scene is interesting as well, but the program would need a way of receiving 'why' it was run (on, off, etc). Given the current design I suspect the logical exploding of a group into a series of in and/ors is more inline.

 

And while I realize this can be done in other ways, I'd really respectfully ask that you do consider easy of programming/ease of use when considering features.

 

Best,

Bill

[LeeG]

I'm not trying to dismiss the idea. Only to define the requirement. In the example

 

SCENE_X

 

Responder A= 20%

Responder B = 50%

Responder C = 100%

Responder D = Off

 

"E.g. if the statement is SCENE_X ON then any of those devices in ON state would trigger."

 

this seems to have no relation to the Scene except a way of listing the devices in the Scene. ON means the device is 100%. For If SCENE_X is ON to trigger True then any of the 4 devices that is turned On to 100% would trigger the Program (Ored) or all 4 device are turned On 100% (Anded). Either way I do not see result having any relationship to the Scene definition in the above example.

 

 

If Status Responder A is On

or Status Responder B is On

or Status Responder C is On

or Status Responder D is On

 

is this the functional suggestion being asked for?

[LeeG]

Is it correct to state the requirement is simply an alternative method of listing a set of devices. That is, the objective of using a Scene name in an IF is an alternate way of listing a set of device names and the original Scene Responder values, % On or On/Off, is not relevant.

[bsobel]

Is it correct to state the requirement is simply an alternative method of listing a set of devices. That is, the objective of using a Scene name in an IF is an alternate way of listing a set of device names and the original Scene Responder values, % On or On/Off, is not relevant.

 

Yes, just simplifying the listing of devices so if scene membership changes programs don't need to be updated.