Master Condition

[pseudocode]

With the addition of conditional processing the events in HS are definitely more powerful and have less repetition.

If you're working on this area, another suggestion would be a master condition that turns the whole event on or off.

I have quite a lot of automation which is enabled or disabled by device status (e.g. Manual disables the events, Summer/Winter enable or disable different events), I'd guess this is a common pattern - with the conditional actions I can now put the check in just once, but it would probably be better for performance if that one-time check was at the top.

[randy]

You can put a condition following each of your Triggers using a Virtual Device to enable/disable the Event.
You can use Easy Trigger or an immediate script to disable the Event.
You can manually disable an Event.

What would you want in addition?

[claude]

I personally use group conditions where the condition is a flag, but then I do need to repeat the event condition "The Group Conditions are all TRUE".

[jhopple]

You can put a condition following each of your Triggers using a Virtual Device to enable/disable the Event.

I use a similar method to enable/disable logging for an event.
I create a virtual device/features that act as flags for logging during an event.
In the first Then block I use the condition to control dumping device values to the log.

I can then enable/disable logging for an event while it is running.

[pseudocode]

You can put a condition following each of your Triggers using a Virtual Device to enable/disable the Event.
You can use Easy Trigger or an immediate script to disable the Event.
You can manually disable an Event.

What would you want in addition?

Yes but then you have to repeat it if you have multiple WHEN clauses or multiple actions, and the WHEN checks are always being processed. It would be more efficient to have one condition that is only checked once to enable/disable the whole event.

I'm considering the easytrigger option to enable or disable the events, but then you need another event to do it and you need to handle scenarios like the control device changing while HS is down.

[pseudocode]

I personally use group conditions where the condition is a flag, but then I do need to repeat the event condition "The Group Conditions are all TRUE".

Yes I do this, but I don't want to create extra groups just because one of my group conditions needs to be a little different.

[pseudocode]

I use a similar method to enable/disable logging for an event.
I create a virtual device/features that act as flags for logging during an event.
In the first Then block I use the condition to control dumping device values to the log.

I can then enable/disable logging for an event while it is running.

Yes I also do this, but I see a lot of events triggering but doing nothing due to the action condition. That seems inefficient - events in HS aren't as responsive as I'd like or in some other systems, maybe having one condition being checked before a more complex set of WHEN and action blockers would be better.