One example is that I only want to set the level if the light is off and the door is opened. If I try to do the same in automations I’m not able to turn the light off when the door is open, because the automation will turn it back on since its a condition and not a precondition.
In fact, smart lighting cannot do the combination of sunset/sunraise and fixed time if you choose sunset/sunraise as activator.
But it would be nice this feature if possible:
6. Turn on a light at sunset and turn off at a fixed time. Now two automations are required, both with smart lighting and with automations.
Point 5 is a period filter, not sunset or sunraise activator.
@Brad_ST, on the topic of SmartThings possibly merging Smart Lighting Routines over to Automations in the future, what about SmartThings support advising me that their is a 250 Automation Behavior limit? (explained below from SmartThings support). Have the Automation Behavior limits been removed?
Because as far as this Behavioral limit in effect as recently as February 2021, if I had to take all of my Smart Lighting Routine Behaviors I have now and add them up with what I currently have in Automation Behaviors today, then I might be very close or even possibly over the 250 Behaviors limit.
Here is the SmartThings support reference about the ‘total number of Automation device/condition/action Behavior limits’.
Feb 19, 2021, 6:28 PM MST
Thanks for reaching out to Samsung SmartThings support.
We appreciate the opportunity to assist you.
I would also like to add:
The total number of automation behavior should be less than 250. Each device/condition/action in automation counts as a behavior. For example, one automation that controls 10 devices has 10 behaviors
Considering the above, please remove the unnecessary automation/s to reduce the number of automation behavior
I don’t know if it’s the behavior limit, but the number of automations limit has been raised. I used to hit it all the time and have to shift automations to webcore. But I’ve added several over the past month moving things off smart lighting and haven’t had any trouble.
For me No’s. 1&3 would take first place(s), I see potential if groups were available to routines (rather than scenes) but mirror is something I use a lot in conjunction with conditionals such as lux & movement…
The ability to perform an action across many things (lights/sockets off for ex.) outside of scenes and multiple target routines is invaluable, again something actionable groups would help address but all useless if routines/scenes remain limited to 200 - which I hit a while ago and use Smart Lighting to help mitigate…
Actually, I did not misunderstand. Your comment here:
This is what I thought it was doing which is not what I want. I want to be able to specify n minutes after motion has stopped. However, I’ve been testing this and I’m not convinced what you describe is actually happening. More to come.
UPDATE: Okay, so it looks like new activations of a motion sensor does basically trigger the automation again effectively restarting the auto-off timer. But I do think the timer is from the start of the trigger, not when motion stops for eg. That’s where I was getting mixed up.
My only complaint with this is that it still can do a delay for two things (two motion sensors, no motion, for 5 minutes), and if you do a delay, it’s no longer a local routine. Both were possible in SmartLighting. I’ve migrated, but I’ve had to do virtual switches as a workaround…