I'm trying to streamline my rules to A make thing clear and easier to read/ change, B make the different apps IE RM and motion lighting work better together and C hopefully take less resources from the hub. From what @bravenel says it may not make a difference in my case but before I had something like this
modes and if switch came on
only when the switch is on
set the dimmer level/ temperature level per mode
I would have one of these per light so if the mode changed and the light was ON the lighting output would change or if i turned them on they would match correctly to the level. The problem i suspected was that this rule was running in the logs on each mode change, so in my mind not ideal?
Today I tested and changed it to a trigger (rather than trigger rule) and set the restriction to be only when the light switch was ON (no logs when mode changes now unless the light is on) I was worried it wouldnt evaluate when you turned the light on but the hub is so fast it unrestricted it and uses it as a trigger all at once, great! So 1st question is this a efficient good/ correct way of doing things?
next point, I have motion sensors and switches and I was using motion lighting to change the light level/ colour depending on mode with mixed results (SM Lamps, Dimmers and RGBW controllers inconsistencies in all of them) during this time i had the original rules paused. So now going back to the triggers and just getting the motion lighting app to turn ON the lights and letting the trigger to do the rest (still to test). The problem I have is two fold 1. RM currently does not support colour per mode (hopefully soon ) and 2. I will also have a switch trigger rule that will turn on or off the light if the switch position is changed. Now in the day it's fine because I use colour temperature and this would be in my trigger mode On set up, but at night from the motion app i have the SM Lamps come on RED and at 1% so not to fully rouse the baby as we carry her around. What I want to be able to do though is if i use the switch at night I want it to come on a temperature value for a emergency for example. So i'm essentially using the ON state of the lamp/ dimmer as a variable which is not what I need in this case. So with my "more efficient rules" is there a way in RM to essentially ignore my normal rule and use another at night when a contact or button is used?
Edit: I essentially need a virtual switch then a option for another restriction of that switch which would need to toggle if i use the light switch in mode night-sleep and only in night sleep have the values i want it to go to in the switch rule. The problem with that is there is no way to order in RM so I can't say if in this mode do this V switch before turning on the light it also won't let you have more than one switch as a restriction, meaning more V switches and rules. I miss WC