As of today both my hubs C5 and C7 are showing Sunset is 12:13pm it should be 6:13pm so this mean all my rules with a Sunset trigger ran 13min after noon. The sunrise time is correct.
It's been working correctly for years and just started today.
Anyone else seeing this?
I updated the hubs to the latest version after seeing this but it's still the same post update.
My longitude and latitude are correct.
-34.920000, 138.510000 (Note I've modified this slightly for security)
I can set the time and time zone manually on the hub itself. We got fully open engineering hubs to play with here
What I found is that sunset time that comes out of the calculation is wrong for one particular day of the year. And it only happens on the hub and not in a development environment. And it only happens in the morning (until exactly 12 noon), and only in one particular time zone (haven't tested all of them, to be fair). So the workaround is to run calculations again in the afternoon, which produces correct results and schedules sunset job/trigger at the right time. That worked for me, but again, this is such a weird issue that I can't be sure the fix works until it's out there and is confirmed to work for the end users next year.
