M1 Time-of-Day Clock Daylight Time issue?

[Lagerhead]

Has anyone else noticed that their M1 clock is fast by exactly one hour, begnning today (sometime overnight on the morning of Monday, March 8th)?

I would expect this to happen in 6 days' time, at 02:00 on Sunday, March 14th. My M1 does an overnight sync with sundial.columbia.edu, which I cannot believe has the wrong time. Puzzling.

 

[Digger]

Mine was ok at 7am. Tonight it is ahead one hour.

 

[electron]

Now that I think of it, my lights didn't turn on around the same time last night, so sounds like there is still some DST bug.

 

[Digger]

I have mine reset the time everyday around 2 pm. I think thats when it happened.

 

[Smarty]

Mine too is also one hour ahead of where ity should be...not sure when it exactly happened (sometime within the last day or two).

 

[CORT]

I'm having the same problem too with my M1. It has sprung forward prematurely. My M1 is running firmware 5.1.24 and using time server rolex.usg.edu. Suspect this is a firmware glitch.

 

[pete_c]

Curious how the M1 gets its time sync? Is it a non user editable function or can the user modify settings?

 

[Lagerhead]

Curious how the M1 gets its time sync? Is it a non user editable function or can the user modify settings?

NTP support is a feature of the M1XEP Ethernet expander. When enabled, time synchronization is done once a day. You can specify the NTP server name and at what time each day to perform the sync.

BTW, Elk confirms that they are aware of the issue and are investigating.

 

[Digger]

I reset my system clock last night. This morning it was fine. Tonight it is off by an hour again.

Strange but if Elk is already working on it then no big deal.

 

[Lagerhead]

Try setting the "Daylight Savings Time Start/End Dates" to "On a specific date" of March 14. I did this and the issue has not reappeared.

(This is temporary, of course. I expect Elk to fix the problem, and not have to set these dates every season. Reminds me why I joined CT in the first place: back when the incompetents at SmartHome lied about DST support on the 1132U. Which is now a forgotten brick in a cabinet.)

 

[dBeau]

Time can be a fun concept to wrap your mind around. You need to make the distinction between what time it is and what words you use to describe it. Where you are has everything to do with how you describe it and nothing to do with what time it is. Timezones are a political concept used to help you describe the time.

The NTP server only knows what time it is. It doesnt know where you are or what time zone you use to describe the time. It's up to the Elk to do that. If your firmware is not up to date with respect to the current thinking (law) on day light savings time (which is really part of the timezone) you'll "see" the wrong time even though the Elk has the correct time.

I find it interesting that sunset events still happen at sunset even though my Elk shows the time as being 1 hour past sunset. But, I guess that shouldnt really be a surprise. The Elks notion of sunset/sunrise is not based on the timezone.

For me, having incorrect timezone information isnt a big deal. All of my time based events (in the Elk) are relative to sunset or sunrise.

 

[Digger]

Good idea. My brain is fried lately and really didnt put any thought into a work around.

SH lie?????? LOL

 

[dBeau]

I reset my system clock last night. This morning it was fine. Tonight it is off by an hour again.

Strange but if Elk is already working on it then no big deal.

As a workaround, try changing your timezone to make the time "look" right. You'll have to change it back again in a week but it might get you through. The other option would be to turn off updates for a week.

 

[Monk]

Same here (hour fast) - Fortunately I have no "important" automation tied to (Elk) time.

 

[gatchel]

Off here too. Spanky where are you...