Setup

Assume we've got a pair of KeypadLincs (husband & wife), and a SwitchLinc controlling the Master Bedroom fan. Setting them up in a scene with the ISY yields the following partial device tree...

 

...

SceneCtl: MasterBR Fan

|___ KPLH-D:MasterBR Fan

|___ KPLW-D:MasterBR Fan

...

(Yes, the code can be refined by throwing the fan into the same scene, but that's not the point of this example. The example has been dumbed down substantially, and doesn't involve fans. *big smile*)

 

I frequently write programs like the following:

If

Control 'KPL Husband / KPLH-D:MasterBR Fan' is switched On

Or Control 'KPL Wife / KPLW-D:MasterBR Fan' is switched On

 

Then

Set 'MasterBR Ceiling Fan' On

 

Else

- No Actions - (To add one, press 'Action')

Obviously, if one had a lot of switches controlling the same device, the length of devices to check can get long and error-prone to maintain.

 

My question is this...

Why can't I use the ISY's view of the scene when programming If conditions? Specifically, I'm looking to do this:

If

Control 'SceneCtl: MasterBR Fan' is switched On

 

Then

Set 'MasterBR Ceiling Fan' On

 

Else

- No Actions - (To add one, press 'Action')

or perhaps...

If

Status 'SceneCtl: MasterBR Fan' is On

 

Then

Set 'MasterBR Ceiling Fan' On

 

Else

- No Actions - (To add one, press 'Action')

 

If we could do this, then as we add or remove controllers to a scene, no Program Details would have to be changed or maintained.

 

I am certain that when someone points out why, I'm going to blush with embarrassment at missing the obvious. But for right now, I'm just not seeing why, and am frustrated enough to ask.

Hi mrp,

 

Good question! From a logical perspective, a device's status is global and irrespective of the scene it belongs to.

 

If you are suggesting conditions based on ISY scenes, well, we do have plans of supporting binary scene statuses (on/off) simply because we never managed to agree on what is the status of a scene.

 

With kind regards,

Michel