So, this is my test rule. It's whole function is to take a time variable, set it to "now" then increment it by one minute. The trigger is based on that time variable.
Works for me. Keep in mind that you will not see it increase dynamically when the rule is open and you're viewing it. You will only see it when you click Run Actions, and then Update Rule
It "works" when I update the time variable via a dashboard, and if I hit update, but if I have to hit update everytime, it's not automated. It's not scheduling the next trigger event when the time variable updated through the rule, only when through the dashboard via a connector.
I have my hydro lights scheduled to go off at sunset, so my window doesn't glow pink all night. So, I take sunset time apply a negative offset for 16 hrs in minutes.
When sunset changes, it updates the rules, but does not update the scheduled task. I check about 9AM, and the light is off, but should have came back on at 1 AM.
I have a task that uses a time variable as a trigger and it seems to be working for me, but I am using a global variable, so maybe there is an issue with local.
I just switched it to global, not ideal, but workable. I did find out what was happening. With a local variable, it WAS scheduling the next event, but for the next day. With global, it doesn't do that.
