I'm going to look at the other issue about multiple triggers on same device/attribute. Maybe that could be improved to look at multiple candidates instead of just the first one.
4 Likes
I have slightly different triggering related question.
For the multiple triggers is it possible to have a predefined condition per triger?
Currently I am using separate rule which sets virtual device according to the
triggering device if predefined condition is true for this virtual device. And than
this virtual device is used as a conditional trigger in a main rule.
If this is not a big deal to implement it will be a valuable improvement for the triggers.
I don't know what this means. Show an example.
Current triggering implementation is:
Predefine Expression for all Triggers
Trigger-1
Trigger-2,
......
Trigger-N
Suggestion is to have a Predefine Condition per each Trigger:
Predefine Condition for Trigger-1
Trigger-1
Predefine Condition for Trigger-2
Trigger-2
.....
Predefine Condition for Trigger-N
Trigger-N
One of the use case: For Dining Table Lighting I have two Motion Sensors strategically
placed under Dining Table. Only one MS is allowed to to initiate a rule. But once rule is
running both MSs must re-trigger the rule. This is done with one extra rule which is
basically a conditional trigger:
Than main rule is using the above conditional trigger:
I have few more rule using the same approach.
It will be nice to have a predefined condition per each trigger (if there is a multiple triggers
defined) but only if this is relatively easy to implement.
Otherwise please forget about this idea.
Just to clarify, you are thinking of a single condition, right?
Something like exciting predefined condition for entire rule plus single extra
condition per triger if there is more than one triger should be OK.
I'm looking at it.
I think it will be easiest to do if I separate out creating and editing Conditions, as they are now for Actions. So you'd first create the conditions, and then use them for a Conditional Trigger. I can't tell yet if this is easy or hard to do.
2 Likes
This is a modified Triger selection section. Right?
And the Predefined Condition section remains the same.
Looks good.
And Thank you very much for this improvement.
By no means there yet. Exploring the possibility.
2 Likes
This seems to work, and is a cool extension for Triggers:
Added Manage Conditions to main rule page to support Conditional Triggers:
3 Likes
Thank you very much. This was very fast.
Here's how it looks now, and the logs:
Logs -- I edited the Condition in between the two trigger events, so it was false the fist time, and true the second time:
Looks Good. Thank you very much for this triggering improvement.
Will it be in next release?
Yeah, but that may be a while. We just finished up 2.3.5 ( 
), so this will be in 2.3.6.
1 Like
No problem. I can/will wait for the 2.3.6.xxx release
I also have a fix for this issue, allowing multiple triggers on the same device attribute for tests such as *increased*, *decreased*, *increased by over*, or *decreased by over*.
2 Likes
Very nice.
And again - many BIG Tanks.
1 Like
