Re-evaluate conditions to trigger action only when overall result changes

[maricn]

Checklist

• I checked for similar existing requests (both open and closed) before posting.
• My request is generic, other users may benefit from it too.
• I will participate in further discussion about this feature and can test it (if requested) once it's done.

Proposal

At the moment Re-evaluate Conditions will trigger action if any of the individual conditions in the multiple condition schedule change state.

I would be happy to have the evaluation not triggering the action unless the total result of all the conditions (after applying AND or OR operations) is changed.

My proposal is

1. to change the behaviour (breaking backward compatibility) and document it or
2. to introduce a config checkbox to toggle whether individual condition change should trigger action (too convoluted in a single view, could be moved to the component config)
3. to allow a new type of complex condition evaluation also involving combining AND and OR operations
4. idk?

Additional info

For example see my config here:

and

What happened today (and not the first time) is:

1. I am home, person B is not. I manually lower the temperature at 01:05
2. Person B arrives at 01:09, causing the revaluation to happen. Result of conditions was true OR false = true, and after reevaluation becomes true OR true = true. The reevaluation triggers the temperature change to 21 degrees.
3. I notice the change and again lower the temperature at 01:17. No change in conditions.
4. I leave home at 02:48, the reevaluation happens again, true OR true = true becoming false OR true = true, again triggering the action, raising the temperature to 21 as per the schedule.
5. I finally get back home at 03:29 and upon finding the scheduler triggered as I was leaving, decide to open this ticket.

What I would like is that the fact one of us is coming and leaving home - doesn’t cause the scheduler to trigger the action when "Any" condition setting is selected. Similarly for "All" setting, if the result of evaluating conditions doesn't change (at least one false remains at least one false), so shouldn't the scheduler trigger action.