I have started setting up simple routines using the native commands in the ST automation in the app. I have the V3 hub, latest app and running wifi, Zigbee and Z-wave devices. Most are working as designed but some times a particular automation which has been running good will suddenly have multiple devices not executing. For example I have a Bedtime automation that at a specific time locks the front door (Zigbee lock), turns off the porch light (wifi switch), turns off a Zigbee bulb and turns on another Zigbee bulb. Last night only one of the devices (turned off the Zigbee bulb) executed. Since this all worked before and I did not make any changes what could have happened? Does the order of the devices or their current status play a role in automations that involve multiple devices?
Also a few questions about how the native automation work.
Do you need to add a condition as a check before selecting the Then device action? For example, IF at 11pm (Condition 1), Door Lock status unlocked (Condition 2) THEN Lock Door. Or can you just ignore the checking status before executing your THEN action and just say IF at 11pm THEN Lock door (even if the door is already locked).
What is the difference and use of the ALL CONDITIONS or ANY CONDITIONS under the IF command?
Thanks much for helping me understand this.
Sadly, this has been an issue with smartthings since it was first released. You have everything set up exactly the way you like it, it runs fine for months or even years, then you get up one morning and things aren’t working. You didn’t change anything: smartthings did. Somewhere. It might have been a DTH, it might have been a hub firmware update, it might just have been something in the cloud. They don’t document their changes and they don’t usually announce them in advance. So you end up just having to come to the forum and see if other people are having issues (after checking the status page, of course).
There are some changes that can happen locally, anything from buying a new refrigerator to a neighbor getting a new boosted Wi-Fi system, that might also impact an otherwise working set up. But usually it’s a smartthings change.
What @JDRoberts say, seems very accurate to me.
In this specific case, you could ignore condition 2, check the current state. If the close command is sent and it is already closed, nothing happens.
In this case, either way should work fine.
Since automations work with triggers for event or state changes, you have to take this into account and simplify everything you can to avoid errors:
Whenever you add to a condition, Device is in a certain state, closed or open, for x time, that time does not start counting until the selected event is received, open or closed …
Exsmple: If you do an automation like the one that you have, IF at x time AND the lock is open for 1 minute, it will not work fine.
Thanks. Sounds like it is easier just to ignore the checking of a device before triggering and just execute the command regardless of the current state of the device. Sounds like this does not mess up ST logic and it will still try to trigger the action regardless.
In some cases is useful to check the status as a condition, For example:
An automation that turns “on” the garage light when the door is opened and turns off the light 5 minutes later.
If you are in the garage doing something with the light “on” and someone opens the door, after 5 minutes light will be “off”.
To avoid this, the condition “If the garage light is off” is added to automation. So, don’t starts the countdown clock to turn off the light.
It would also work in automations that turn on lights with motion sensors and turn off when movement stop.
If you add, IF the light is off. You could temporarily override the automation, if you wish, just by turning on the light from the app button.
Automations give a lot of flexibility and possibilities.
