Logical operators in Triggers and Conditions

  • 78 Views
  • Last Post 10 March 2014
n0vtn posted this 08 February 2014

I for one could cut way down on the number of scenes I have if the three basic logical operators "AND", "OR", and "NOT" were available in scene triggers and conditions.

For example; currently if there are two triggers, a scene will run if either trigger A "OR" trigger B are true. But it requires more work to get a scene to run if I want it to run only if trigger A "AND" trigger B are true at the same time.

Currently, with multiple conditions, both Condition A "AND" Condition B must be true for a scene to run. It would be useful to be able to structure condition A "OR" condition B. Or possibly condition A "AND NOT" condition B.

I have been able so far to accomplish the same things but it requires additional scenes and virtual devices to make it work.

N0VTN

Order By: Standard | Newest | Votes
Ryan-Scott posted this 08 February 2014

I for one could cut way down on the number of scenes I have if the three basic logical operators "AND", "OR", and "NOT" were available in scene triggers and conditions.

For example; currently if there are two triggers, a scene will run if either trigger A "OR" trigger B are true. But it requires more work to get a scene to run if I want it to run only if trigger A "AND" trigger B are true at the same time.

Currently, with multiple conditions, both Condition A "AND" Condition B must be true for a scene to run. It would be useful to be able to structure condition A "OR" condition B. Or possibly condition A "AND NOT" condition B.

I have been able so far to accomplish the same things but it requires additional scenes and virtual devices to make it work.

N0VTN


I agree... any thoughts on how this could be accomplished in the interface? How could you group certain conditions together and make the UI simple enough to work through it?

Axial-User posted this 08 February 2014

Maybe not the simplest for everyone, but those with a bit of Microsoft experience would be able to get the hang of using the standard expression builder functionality (often used when building a select statement on a database).

http://office.microsoft.com/en-us/access-help/using-the-expression-builder-HP005186638.aspx

monkey-magic posted this 08 February 2014

[quote=Ryan Scott]I for one could cut way down on the number of scenes I have if the three basic logical operators "AND", "OR", and "NOT" were available in scene triggers and conditions.

For example; currently if there are two triggers, a scene will run if either trigger A "OR" trigger B are true. But it requires more work to get a scene to run if I want it to run only if trigger A "AND" trigger B are true at the same time.

Currently, with multiple conditions, both Condition A "AND" Condition B must be true for a scene to run. It would be useful to be able to structure condition A "OR" condition B. Or possibly condition A "AND NOT" condition B.

I have been able so far to accomplish the same things but it requires additional scenes and virtual devices to make it work.

N0VTN

I agree... any thoughts on how this could be accomplished in the interface? How could you group certain conditions together and make the UI simple enough to work through it?[/quote]

Not sure what people think but maybe 2 options: 1) Where the add device option is, change it to add command. When an operator is placed any commands are indented/tabbed to show they are running under the operator. Like my uservoice: http://incontrolha.uservoice.com/forums/218427-general/suggestions/5390053-add-actions-to-incontrol-http-get-post-run-file 2) Separate drop down box for operators like the actions suggestions for above. Operators get placed in separate column. Like this: http://imgur.com/QAjdWWR

Josh

n0vtn posted this 09 February 2014



I agree... any thoughts on how this could be accomplished in the interface? How could you group certain conditions together and make the UI simple enough to work through it?


Perhaps an additional dropdown list for "add operator" to choose the operator. The choices might be "AND", "OR", "NOT, and "CLOSE OPERATOR".
This way the operator could be on a line by itself. and everything affected by the operator contained between braces {} or parentheses () on the next line or lines.
Indentation wouldn't hurt either.

Example:

Condition A
AND
(
Condition B
OR
(
Condition C
)
)

N0VTN

Ralf posted this 10 March 2014

+1

I'm creating a lot of scenes and virtual devices to accomplish my tasks which could be avoided with these logical operators.

Close