I have a rule that turns porch light on at sunset and supposed to turn them off at 11
The problem is that it turns them off one hour earlier
Hubitat time is correct
The log shows that they were turned off at 10 instead of 11
Are you able to show a screenshot of the rule as well?
1 Like
Hub time correct? Time zone correct?
1 Like
Yes the time is fine you can even see in the log it shows it’s turning it off at 10 instead of 11
Here is a screenshot of the rule
Sorry to labour the point re the time zone, but @neonturbo could be right, the log doesn't show the timezone and if the rule was created / last updated under a different time zone, e.g. in or out of any daylight savings, that could be the problem. RM may store the time zone with the value, and then convert this if the current time zone is different.
Have you checked the Hub settings page to confirm it is the correct timezone? E.g. Current Hub Time? In my case the time zone is Australian Eastern Daylight Saving Time (AEDT), this is the part we want to make sure is correct in your case I believe.
1 Like
The rule looks fine as far as I can tell btw....
In addition to that, I have seen where some time zones just do not seem to work correctly or there are alternative time zones for one location. I have 3 choices where I am at, and the one setting definitely matches my local time better than the other choices.
1 Like
Yep I think my time zone is ok
Plus the rule was created only a few months ago and winter time supposed to change in a week from now
Hmmm, that is weird then...
Perhaps you could try adjusting the hours and minutes in the rule to test it continues to exhibit the same 1 hour difference after being updated and / or at different times of the day. To make testing easier you could adjust the time to turn off to be throughout the day while testing and turn the light on manually beforehand to reproduce the "turn on at sunset" logic, if that makes sense. This won't necessarily solve the problem, but may help in understanding what's going on.
1 Like
I found a very similar bug that happened at midnight. Maybe adjusting even one minute either way would prove something?
I do like the idea of doing some testing like sburke outlines above.
1 Like
That's not necessarily the time zone. Your actual time zone is shown on the location settings page.
2 Likes
Yes I know it’s there
I double checked and it’s ok
Plus the turn on at sunset works actually at the correct time
I did a few tests creating a turn on rules at specific time and it worked correctly
Just in case I removed the existing rule and created a new one. Will see later today when it will actually work
Removing the rule and creating a new one helped
2 Likes
i wonder if daylight savings occurring had anything to do with the offset of the time
2 Likes
I have the same problem: the log records events one hour later than the actual time. Automated events happen at the correct time, but the log records them as happening 1 hour later. Time, date, time zone are all set correctly.
If I turn on/off a light by clicking the dashboard icon, the log will report it happened one hour in the future.
Again: Rules execute at the correct time, so the hub "knows" the correct time, but it records them in the log as happening one hour later.
Here's an example:
app:232020-10-31 11:00:00.458 pm infoLock Doors 10:00pm: Triggered at Certain Time
That app properly locked the locks at 10:00pm, but reported it in the log as happening at 11:00pm.
Hubitat Elevation® Platform Version 2.2.3.148
Hardware Version Rev C-5
Any ideas?
I noticed the same issue (fwd314-hubitat) just now while setting up a rule with specific time. Latest HE version.
