I happened to be awake as the time approached 2am (EDT) early this morning, and watched as my clock went from 1:59am back to 1am due to Daylight Savings Time ending. I thought I would check my cameras to see if they correctly switched as well. What I discovered was that they did… Except in every case of 4 of 5 of my cameras - all with updated firmware - the time skipped from 1:59:59 am back to 1:00:00 am, and then to 1:01:02 am… Skipping a minute of video recording to SD card. I thought at first it may just be a time stamp glitch… but when checking the camera where I was in the room, I could actually see the minute glitch. That first minute of the fall back was not recorded.
My 5th camera is a Wyze Cam Pan v3, and did not have this problem.
The time changing event twice a year is the bain of all programmers. You haven’t lived until you have had to figure out Arizona.
Almost all networking devices, Wyze included, have an internal clock. A program in the device institutes a time change routine, that determines where the device is located and how it should adjust the time. The program runs, time is adjusted
and then
a network time site is contacted and the internal clock is synchronized. Depending on the device and it’s programming this can be checked from every minute to days.
The minute in doubt is probably this network adjustment. Why did one camera get it perfect?
There are multiple time servers spread around the world. I can imagine that at 1:59 last night the time servers were loafing around. At 2am onward the servers were inundated with thousands/millions of requests. Maybe your good camera was first in line.
The fact that after a few minutes you were back to normal is a good thing.
Your post got me to thinking “how did my wyze app do when the time change occurred, especially on the SD cards?”
I’m going to call these anomalies.
On my V3 pro, OG, and OGG-T. At first blush perfect. The transition was from 1:59 to 1:00. No break in the SD green timeline.
On my pan Scan v3’s and doorbell v2, slightly different. At 2am the SD card green timeline went blank. The time shown on the left adjusted properly and the SD playback continued playing properly. Then at 2am (again) the green timeline reappeared.
Not sure why these these cameras show slightly different information and I may not want to know.
No data was lost, within an hour everything was back to normal.
I did check Recent Events to see if I could see the transition. Not enough events to see it.
FWIW. I’m in the camp that wants to get rid of DST.
If you want to start a riot, count me in! DST is ridiculous. Here in Ontario, they’ve been trying to get rid of it for quite some time now, but from what I understand they’re not doing it because New York doesn’t want to do it. Trading and all that.
Thank you and great explanation of the possible network time server issues. Absolutely could be the reason… But still interesting that 4 cameras suffer the exact same glitch.
And I whole heatedly agree on DST! I grew up in Indiana… So I feel you because the TV schedules use to change in the summer! And thank God! I might have never otherwise stumbled onto Letterman and all sorts of other things that have shaped my personality!
BTW - I’m a long time Mac user… So I’m unfamiliar with a lot of these crazy clock issues. Y2K was just another day!
Last year, there was an issue with v3 firmware that caused the camera to skip the first minute of SD card playback except for at midnight. I thought the issue was fixed but looks like it has resurfaced.
Forum - Wyze Cam v3 microSD card Playback is skipping the first minute of every hour (excluding midnight)
I don’t have a lot to add to the above discussion, but I will mention one thing. If you pull the SD card out of a camera and look at the contents, you will see that the recordings are saved as one minute files in hourly and daily folders. This explains why it was a period of one minute that was missing; one of the minute files didn’t get saved. @ronl4625’s explanation as to why is as good as any.
If you are so inclined, you could submit a support ticket on this by clicking the Support link at the top of this page. But to be honest, I doubt the developers will spend much time on it given that it is a one (or maybe twice) a year issue that occurs at a time when most people are not checking their recordings.