Simple piston triggered after Sunrise not working


A few days ago, this piston stopped working for no apparent reason. Looking at the logs (below), I assume this is because condition #11 is evaluating to false, but I’m not sure what that condition is when this is a simple time-triggered pistion. Any help would be appreciated.

> 6/23/2020, 6:43:27 AM +669ms
> +0ms ╔Received event [Home].execute = recovery with a delay of 74ms
> +100ms ║RunTime Analysis CS > 21ms > PS > 70ms > PE > 10ms > CE
> +102ms ║Runtime (38062 bytes) successfully initialized in 70ms (v0.3.110.20191009) (101ms)
> +103ms ║╔Execution stage started
> +123ms ║║Comparison (time) 24207776 happens_daily_at (time) 1592908680000 = false (0ms)
> +125ms ║║Condition #11 evaluated false (18ms)
> +126ms ║║Cancelling statement #11's schedules...
> +130ms ║║Requesting time schedule wake up at Wed, Jun 24 2020 @ 6:38:00 AM CDT
> +132ms ║║Condition group #1 evaluated false (state did not change) (25ms)
> +134ms ║╚Execution stage complete. (31ms)
> +135ms ║Setting up scheduled job for Wed, Jun 24 2020 @ 6:38:00 AM CDT (in 86072.196s)
> +143ms ╚Event processed successfully (143ms)


You can identify condition #11 by turning on your Trace.

What likely happened is, your piston missed the schedule, but tried to run a recovery a few minutes later. When it checked the time condition, the time had already passed, so no action was taken.


There have been many users in the ST forum reporting issues with automations using sunset and/or sunrise over the past few days. Moments ago, an ST staff member reported the issue was located and resolved. Not sure if this was related to your issue.


By turning on trace, I see that Condition #11 is the ‘1 hour past sunrise’ statement. And looking at the timestamp in the logs, I see that it did run a few minutes after it should have run. So I guess this is related to the issue with the sunset/sunrise mention by @jkp.

Today it ran normally for the first time in several days so hopefully the issue is resolved.