Scheduled time events do not work, particularly in the AM

#1

1) Give a description of the problem
If I have an action that is set to occur at 5:58 am it usually does not execute properly

2) What is the expected behaviour?
At 5:58am I want to change the house temperature to the usual daytime settings.

3) What is happening/not happening?
The piston does not show in the logs as starting at 5:58. Instead I see a “recovery” item that starts sometimes as much as 90 seconds later. However, when that second instance gets to the 5:58 am statement it fails because it is now 5:59:30. I can’t be the only person having this problem. Has anyone else worked a solution? I am sorry I don’t have the image of the piston script, but I have re-edited it so many times trying other ideas. However the faulty statement is simply a "if happens daily at 5:58am then " set the temperature.

You can see from the log snippet that not only is there no entry at 5:58am, but the 5:59:30am recovery instance fails because 5:58 has passed.

** 5) Attach logs after turning logging level to Full**
╔Received event [Jeppsen Home].execute = recovery with a delay of 62ms
+185ms ║RunTime Analysis CS > 20ms > PS > 109ms > PE > 55ms > CE
+188ms ║Runtime (49873 bytes) successfully initialized in 109ms (v0.3.110.20191009) (186ms)
+189ms ║╔Execution stage started
+197ms ║║Comparison (time) 21563254 happens_daily_at (time) 21480000 = false (0ms)

#2

Think the green snapshot will give a better idea if anything else is impeding or delaying this trigger. If you can post one please do so.

Separately from that, have you tried putting time as a range for example between 5:58AM and 6:00AM. if anything is delaying the action, having a wider window might help at least to trouble shoot.

#3

Unfortunately, there isn’t a trigger for a time range. The only choice given is “happens daily at”.

#4

Correct, it would be a condition. Again if you could post a green snapshot it would add greatly to being able to help