If the Smart Lighting SmartApp days are numbered and my entire list of Smart Lighting Routines are combined with all of my Automations, that would make for a very long list which would be horrible to navigate and find anything on. In that case, I sure hope they bring some cosmetic changes to the Automation list if (or when) that happens because I’d at least need containers/subfolders/rooms/groups, etc (whatever you want to call them) to correlate/separate the long list of Automations.
BTW, SmartThings support once told me that their is a 250 Automation Behavior limit. And I’ve read throughout this message board that their is an Automation limit of 200 apparently. So if they merge the Smart Lighting Routines to Automations, then I’d imagine any Automations limits would need to change.
Another reason why we need the Shortcuts to device automations on the specific device page like we used to have in the old app
It used to be simple to locate/correct/change automations for devices, as it currently stands it is a disaster, and as @DaWeav says, is possibly set to get worse in the future
Until now I have not had a chance to test Beta local automations and this is what I have seen with devices using modified DTHs:
Automations work with the hub disconnected from the internet with these devices:
Multi open/close smartthings sensor (samjin). DTH “SmartSense multi sensor” modified to adjust temperature reports with variables and with the DTH name changed.
UPDATE-2 (Acceleration, vibration capability works with local automation with modified DTH only if the DTH name is same to stock)
Fibaro double switch 2, parent device DTH “Fibaro double switch 2 ZW5” modified for local execution “true” and DTH name changed.
Motion sensor Smartthings with DTH “SmartSense motion Sensor” modified to adjust temperature reports with variables and with the DTH name changed.
Local Automations with fibaro keyfob and modified DTH for local execution do not work.
Of course, devices with stock local DTHs work as local.
Can you share examples of what cannot be done with normal automations that is supported by Smart Lighting? The main one that I’m aware of is that controlling lights with motion can take two “new app” automations versus one Smart Lighting automation. This is due to how “Auto turn off” differs from “Turn off after motion stops”. I’ve flagged that as a missing feature but would be happy to flag others if you have them.
I went through mine and two items I spotted are 1) the one you mentioned- turn off lights automatically after motion has stopped for a generic period of time and 2) have a period of time that has one bookend be sunset/sunrise +offset and the other bookend a specific time.
I said “many” which seems I’ve overstated but the above two account for a big percentage for me.
Would obviously be nice to combine “or” and “and” conditions without webCoRE, but smart lighting can’t do that either.
As have said @William_Knecht, you cannot do automation with a period of time that starts at sunset or sunraise (+/-) x time and ends at a fixed time. The period (+/-) x time in automations is limited to (+/-) 60 minutes. In smart lighting you are not limited.
In smart lighting you cannot do the combination of sunset/sunraise and fixed time if you choose sunset/sunraise as activator. Do not copy this for automations.
UPDATE 1:
The option to imitate the behavior of another device that has smart lighting is also useful and to do it with automation, you have to do it with at least 2 additional ones.
Many of us might be using “mirror” function of Smart Lighting to associate ‘zigbee bulb’ to unwired ‘zigbee wall switch’.
I have 3 gang wall switch, and only 1 gang is wired to a physical traditional light bulb. Other 2 gang switches are “virtually” linked to zigbee bulbs using Smart Lighting mirroring.
To do this with the new app automation, I should make 4 automations.
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.
@William_Knecht@Mariano_Colmenarejo
Maybe I’m missing it but I don’t see how to combine sunrise/sunset and a specific time for Smart Lighting. I tried setting a specific time as the activator.
I cannot make any promises about them getting addressed but does this look like a consolidated list of features available in Smart Lighting that users would like to see in the automation rule builder?
Turn off device X amount of time after device event happens
example: Turn off backyard light 5 minutes after motion stops on backyard motion sensor.
Greater than 60 minute offset for sunrise/sunset events
example: Turn on backyard light 120 minutes after sunset.
Mirror behavior
example: Pool light mirrors the behavior of backyard light.
Additional preconditions
example: Turn on pool light at 8 pm only if backyard light is on.
Ability to mix sunrise/sunset and specific time as period of time filter
example: Turn on backyard light if motion is detected on backyard motion sensor and it is between sunset and midnight.
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.
Thanks
@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’.
(SmartThings)
Feb 19, 2021, 6:28 PM MST
Hello,
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 can try to inquire internally but you are only at about 120 combined automations between Smart Lighting automations and custom automations in the new app.
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.
