Hi, I have a C7 hub with platform 2.4.3.171. The Lat/Long and TZ settings are correct.
I had setup a rule to trigger a light at sunset in RM. This was done back in sept/oct time frame when the sunset was later (6:20pm or so). Now, the sunset is much earlier (4:50pm or so), but I find that it is still triggering at the later time. When I go into the Rule Machine and just "update" the rule, without changing anything, it sets itself to the correct sunset time for now, so I know it knows the current sunset time for my location.
Is this the way it is supposed to behave? In other words, do I have to go manually "update" the rule periodically, changing nothing, to track the correct sunset time? I have the screenshot below for the very simple rule.
Please provide your hub model (C7, C8, etc.) and its platform version from Settings>Hub Details.
Check out the following post for help troubleshooting problems and gathering details that will help others to identify and solve the problem you are experiencing: ‼ READ FIRST - Before Posting in Get Help
This looks like a Holiday lighting rule -- after you created it this past fall, did you Pause or Stop it until just recently, or has it been running this whole time?
If it was paused/stopped, then it likely just needed and Update/Done to restart its scheduled actions. Otherwise, there should be no need to do anything to ensure the correct SS/SR time is being used in any active rule.
Not that you asked, but you could simplify your Trigger to just Time = SS -- since you're using every day, there's no need to also specify Days in the trigger too. But it's not hurting anything, so no big deal either way.
Are the Time Zone settings definitely correct? I'm in the UK and when I first started with Hubitat had mine set as 'GMT' rather than 'Europe/London'. That was incorrect as daylight savings time wasn't adjusted when using 'GMT'
@hydro311 : The rule was not paused or stopped. I had unplugged the lights from the Diwali holidays at that time, and now I plugged in Christmas lights, and expected it would just work from the same rule. As I said, it was still turning on on at the old sunset time, until I updated the rule.
@johnwill1 : I double checked, and the Time Zone is set correctly for my time zone.
Any other ideas? Is the "delay off" part of it screwing something up?
I can't imagine any way the Delay is impacting anything here. I too am generally a fan of using Waits instead of Delays, but this is one of the cases where it should make no difference whatsoever...
The rule Trigger is an absolute (and singular) time event, and there's nothing event-wise or condition-wise that could interrupt the rule's actions in a way where the distinction between Wait vs Delay becomes a factor.
As you have it now, that Delay should be totally fine.
Did you happen to look at the Sunrise and Sunset times when you were checking the location in your settings? Were the times shown there correct? Or did they also lag?
Sunrise/Sunset times are correct, but when I checked, I noticed a problem. I had "reset" the rule when sunset was at 4:50pm. But in the subsequent days, the sunset has updated to 4:51pm, but the rule machine rule is still stuck at 4:50. So, I believe it will just stay at 4:50pm, until I "reset" the rule again, as it had done before. Here are the screenshots:
Will see if "sunsettime" changes tomorrow as it should.
Edited to add that I changed the triggers from the conditional shown below to be exactly what the OP has in their rule. On certain days (all of them) at Sunset
Just out of curiosity, if you open the rule, and click the "i" at the top right, you should see a scheduled job to update just after midnight (waaaay down at the bottom of the page after you click the "i"). This is how it is supposed to update sunrise/sunset every day if you are using those as a trigger. If you do not see the scheduled job, you may just have a corrupted rule. I will still report back with my test results. But I expect it to work on my end since I have the job scheduled.
I deleted that rule and setup a new one without the days of the week. I also split the OFF into a new rule, because, really, I want the OFF time to be independent at a fixed time of day, not a fixed number of hours later. I did verify that the midnight job is on the schedule for the new rule. Keeping fingers crossed.
Also, curious, in addition to the midnightHandler scheduled daily, there is a allHandlerT process scheduled once for 4:52pm today. Does anyone know what that is for?
Just a follow up. The rule fired correctly, and according to the logs, it changed the sunset time for the rule for today. I am thinking something just happened with your specific rule.
