Off the top of my head, there’s something else wrong with the system there, because… if you have a switch domain, the system should definitely have a switch/turn_off service.
That’s about as much as I can offer right now, but I’ll come back to this thread if nobody else can think of anything in the meantime.
The “condition: and” isn’t needed. If you list several conditions, they’re all “and”.
Likewise, if the trigger section has several, it’s like an “OR” option.
And while you can’t have an ‘AND’ trigger list, you can have an “OR” condition list, with the above syntax.
The “condition: and” statement now sees its use when nesting conditions, both OR and AND…
Example of the “OR” condition amongst default “AND” list :
This is the condition to turn off the central heating at home when the temperature is above the “eco/night” level: temperature AND (night OR nobody home)
I don’t have a sample of OR with nested AND conditions.