I've been utilizing James' Date and Time parser app to control some automations based on daylight savings time - in particular, whether to extend my patio awning or not. I'm based in California and DST ended overnight Saturday/Sunday. Today, my awning extended and, when I opened up the Date & Time Parser, it was still showing "IsDSTActive = True. Only after I clicked the "Refresh" button did it then update and correctly reflect isDSTActive=False.
I had assumed it was refreshing itself given the "Auto Update Interval" is set to every five (5) minutes. Any ideas on what might be causing the app to not auto update.
I should add that I installed the Date & Time Parser and created the condition on my rule while DST was active so, this was the first time it would have been tested.
I admit I have no code to check if DST was/is active at initialization. Unsure if I should given the default of HE is not to use DHCP ntp server hourly updates. Tough one. I've noted the issue and if I return to that code (full disclosure I've another bug I know of in that code as well which I'd like to address someday) I'll run down this issue as well.
I want to add that it didn't happen to me - I rebooted my HE BECAUSE of the time change the morning after just to force updates to variables I run for civil twilight.
Thanks @ogiewon . I did do a search on a few different terms and only came across a post (in which I had previously inquired about an app like this) that had been closed due to inactivity. I missed this one. Will post my question there as you suggest.
Thank you @jshimota. I obviously won't have to worry about it again for another 4-5 months, so not a big deal. I do re-boot my HE weekly, but overnight on Fridays/Saturdays, so the DST changeover happened after that reboot. Since these changeovers always happen overnight on Saturdays/Sundays, perhaps I'll just change my auto-reboot to occur right after that to ensure there's a clean start to the time change.
I'm just being silly - but we could just write a rule using date/time parser to determine the change PDT / PST and cause a reset to the hub! .... the circular logic of that just broke my brain.
Just bumping this thread...as DST flipped last night, once again the Date and Time Parser did not refresh. I've written a simply rule that forces a device refresh every day when mode switches to "Day" so, hopefully that will band-aid the issue going forward. But am still curious, @jshimota, why the Auto Update feature in the device isn't working.
I watched it closely this time. The change occurred at 12:00am (just after) when the scheduled job ran. The failure is once run, it has no reason to return to that section and to keep chatter down I only update other date values - not time (I think).
so for the day of occurrence it misses the boat. I think if I change the daily update to 3:05am gmt it should catch the change within one hour of occurence. I dislike scheduled jobs in the middle of the night as backups and HE funky happens durring that period but I guess I have no choice. I'm loathe to run tests on that since it blows up all cookies if you toy with time/date actual values in your machine. I guess I could build a VM but thats a crap-ton of work. I'd rather just take a stab and wait 6 months :).
I've put it on my list.
