Simple Automation Rule 1.2 Bug

[ritchierich]

@bravenel @bobbyD I setup a new v1.2 Simple Automation Rule to control my holiday lights and it failed to turn off the lights at the specified time. I then cloned an existing v1.1 rule and setup the same parameters and it worked fine. I wanted to bring this v1.2 bug to your attention.

Here is the rule:

I was able to quickly reproduce on my dev hub by setting the off time to a few minutes from current time, leaving sunset as the on event. I enabled logging and I confirmed via app status there was a scheduled job to turn off the lights. Time passed, no log entries, previous run timestamp was set, switch remained on.

Also noticed no “doAction” scheduled job was set to turn on the lights at sunset like I have in my v1.1 rule. So bug there as well and the lights wouldn’t have turned on at sunset as specified.

Platform Version 2.3.6.146

[velvetfoot]

@ritchierich

I setup a new v1.2 Simple Automation Rule to control my holiday lights and it failed to turn off the lights at the specified time. I then cloned an existing v1.1 rule and setup the same parameters and it worked fine.

As a SA devotee, I'd thought I'd chime in.
I just confirmed this.
Didn't look at logs or anything.
1.2 seems to only do the second action if it has done the first action.
I tried time (vs sunset) in the past as well, and that too didn't work.
A cloned 1.1 rule does turn things off even if it didn't turn it on.

[bravenel]

@ritchierich

noticed no “doAction” scheduled job was set to turn on the lights at sunset like I have in my v1.1 rule

On at sunset (or sunrise) does not create a scheduled job. Instead, it subscribes to the hub event for sunset (sunrise).

@velvetfoot

1.2 seems to only do the second action if it has done the first action.

That's how it works.

I would suggest you import the SA rule in Rule Machine, so you can have more refined control. Or better yet, use Room Lights for lighting automations.