11 February 2019
- Last edited 11 February 2019
if condition groups are AND then it defeats the purpose of grouping them since within the group it's AND too. making them OR would really get confusing in my opinion.
tying in the group to the trigger allows for a scene to be activated on multiple triggers based on their related conditions so i would not have to duplicate the scene for each trigger/condition scenario.
IE. i control baseboard heaters around the house on a schedule for different rooms at 5am, 9am, 3pm, 9pm and midnight when the heatpump is turned OFF. when the heatpump is turned ON, i set the baseboards to below the heatpump temperatures and leave them low.
if the outdoor temperature goes below 5 degrees, i want to turn the heatpumps off and start the baseboards according to the time of day.
so each baseboard time setting has 2 triggers:
the time of day that the temperatures should be set where i set the temperatures if the heatpump is off.
if the heatpump is turned off, then set the temperatures according to if the time is between x and y.otherwise i would have to wait for a time event to arrive to set the rooms to the appropriate settings.
in my case, the conditions are the same for either trigger, but i duplicated the conditions for 2 groups to make sure.
But you can see the opportunity here....Along with the coding, you would have to also display the groups like you do with triggers.