I use rules to manage porch light. I have a rule that was set to turn off the porch at 12:01am OR if I went to bed.
This AM, HE updated the date/time correctly - however. a setting on the time stamp changed itself without me interacting for the value of 12:01
.
This is a virgin snap, I did NOT touch this rule - just looked at it. As you see, the 'OR' is now 1:01am but the rule details below it say 'at this time 12:01am'. I will be hand adjusting this today but be aware.
edit ** I can't fix it. HE wont let me put the time to 12:01a
I would suspect this is a daylight savings time end issue. There are actually 1:01s today since 2 fell back to 1.
4 Likes
Almost certainly a DST issue - it should correct itself. But these DST kerfuffles are why I don't ever trigger any rules anywhere in the time window 1:00 - 3:00 am.
4 Likes
I moved the rule to alexa - problem solved.
I have a couple room lighting rules that are not triggering correctly due to the time change.
The rule itself got modified to say turn off lights at 1:00 AM instead of midnight.
Editing the rule has no effect.
Going to reboot and see if that fixes it.
Edit: reboot did nothing, all of my "means to turn off lights" that were set to midnight still have 1:00 AM. Had to change the off time to 11:59 PM to fix it.
Room lighting is confused by 00:00 as an off time.
I remember this happened last time the time changed. I have some lights following a night mode and they were reacting an hour earlier last night. Last time it corrected itself, just a day behind somehow.
I had some anomalies yesterday and this morning, specific to webCoRE. My best guess is that certain events were scheduled before the time change and simply did not account for it.
For instance, certain automations look at my alarm time. The alarm was not set over the weekend, so it probably scheduled events on Friday to take place on Monday. This morning was scheduled incorrectly, but it is showing the proper "next scheduled" time for tomorrow.
My Webcore pistons are also running an hour off. The hub shows the correct time and time zone but my pistons are still off. I figured they would correct themselves today but they haven't. I seem to remember that I had to pause and resume each of them last year. Which is aPITA with 40+ pistons. I guess I'll try that tomorrow.
It's a shame we still have to deal with this year after year. And it would be helpful if a dev could chime in on this one.
