I need to change the order of my triggers so that a window sensor becoming open is detected as priority over the same sensor registering vibration. Because a notification tells me the triggering device and type of trigger, and I'd rather be told straight away that the window has been opened rather than it just became active.
I'd be happy just to rewrite the line inserted before the existing top line but triggers only seem to want to be added at the bottom which could mean quite a bit of rewriting to get them into the order they should have been.
Any workaround?
The way I understand it is that there is no priority in Triggers. Any will trigger.
I think that you will have to manage the notifications in the rule itself. Only report vibration if window is closed.
1 Like
Well the triggers are evaluated in the order of listing in my experience. Now that I have rearranged the lines, opening the window that used to match and be reported as "active" now reports as "open" - bearing in mind the same sensor will sense activity at the same time as sensing contact opening.
When a trigger triggers, the rule will fire. No need to evaluate other triggers...
1 Like
Well I know what I can see happening. Not sure if you're agreeing with me or not, but rearranging the triggers has a significant difference to the output of this particular rule.
Strange... but I'm happy that it's working for you 
1 Like
Well to get back to my first post, I'd have been happier still if I could have rearranged the order of the triggers without rewriting
2 Likes
Triggers don't work that way, there is no order or logic to them. Not sure how the order could be evaluated if any really means any? It would be interesting to see logs of how rearranging triggers can make the rule act differently, and a screenshot of the rule in question. Maybe there is a bug somewhere?
2 Likes
Good point! I hope I had it logging... sadly no I didn't. I have turned logging on and can try both ways again to compare -
But in order to do that I now have to delete and rewrite lines to get the order different 
There isn't even a way to just disable trigger lines
Ok I actually got both events recorded (by my rule into my custom log file) with the new way around but only the active with the old way around. The active event comes slightly before the open event when opening the window
There is no order of evaluation of triggers. These are events in the hub. With multiple triggers and even nearly simultaneous events, there is no specific order in which they will trigger.
Re-ordering triggers in a rule has absolutely no effect on anything.
Expecting to depend on the order of events like this is not at all reliable, even if it seems to work.
3 Likes
Thank you for coming along with the definitive 
I'm going to guess here, I would consider the order only works for you because they are both from the same sensor.
Would be interesting if you had the same triggers but different sensors.
Having rethought this through, and taking Bruce as the ultimate authority on the topic, I am now thinking the rule must trigger once for each event both open and active. I think there must just be situations where there is a temporal clash and both outputs (ie the custom logging and the pushover notification) just can't happen for both runs of the rule in such a short space of time (fractions of a second) and so it appeared that only one of the events had actually triggered the rule.
