BUG Simple Rule Turn on lights Sunset -30m (executed @ ~ -90m)

[moylanj]

So, I set up a 'simple' rule some months ago (post switch to EDT), turn a few lights on all of the time at sunset -30m. This worked fine UNTIL TODAY.

Today I come in at c. 420p EST and those LIGHTS are ON already. Sunset is still an hour AWAY.

Look at log, they turned on at c. 354p EST (or ~ -90m BEFORE sunset).

Looks to me like there is some kind of EDT/EST/timezone bug.

Location is CORRECT.

HE time is CORRECT.

Cannot explain otherwise, I see no errors in the brief glance that I gave to the logs to check the time they came on. AND it is ONLY the lights that this simple -30m before sunset rule APPLIES to that turned on...

[EDIT]
I have a VERY SIMPLE setup ATM of c. 15 zigbee lights (IIRC), so it's not a case of an overloaded 'server' going ape----...

Also might merge with the other identical topic...
[/EDIT]

[EDIT2]
I have the Alexa skill and Google home integration installed.

I have the dashboard and simple Android 'app' installed.

simple rules machine, rules machine, mode manager, and groups and scenes...

fw v. 2.1.6.113
[/EDIT2]

[EDIT3]
This

Time change not reflected in rules

I think that it's the way that they're handling timezones in their applications or the OS setup, personally, but my personal -90m, but wait a minute since the rule is -30m, the -90m WOULD me -60m off, so... yeah they're handling timezones poorly...

is the suggested merge target... thanks
[/EDIT3]

[starcom]

Time change not reflected in rules

With yesterday’s time change I noticed an interesting issue. All of my rules today based on sunrise/sunset are off by one hour as if the Hubitat didn’t change for daylights savings time. If I go to setting and look at the time it shows correctly.