Read the statement by Michael Teeuw here.
Default clock module accuracy?
-
@rtkeen every time it updates the ui it does this calculation
there could be a rounding error due to the removal of the 10s
ie, 6 instead of 60
but have never seen any other message about this
-
@sdetweil
Mine is off a full minute right now. Funny thing is it will usually catch up in a few minutes. I notice it most often around xx:45 to xx:49 in the afternoon, evening .
Not a big deal to me what is 30 to 45 seconds matter anyways.
Now as I am writing this it caught back up. I would not notice at all if I dd not have another clock running directly below it that gets it’s time from the network too. -
@plainbroke interesting
-
@sdetweil
I thought you would find that interesting, I never thought much about it until the previous post came about. Like I said it doesn’t bother us or cause any issues. They really are at least with in 45 seconds of each other. If I reboot the pi it will sync up for most of the day… Maybe that is his answer to restart his pi just before bed, assuming it is that important…Slow learner. But trying anyways.
-
@plainbroke i have a bedside clock, that gets its date/time from the signal in the ac powerline.
since i picked up an iphone , the bedside is 2 minutes behind
my android is ok… weird -
@plainbroke Out of interest and to see if you get the same issue, can you try my MMM-SweepClock and see if it has the same issue? Just want to see if it may be the module that is loosing time?
-
@mumblebaj
Sorry but no. I am out of pi’s to test on. And it is not something that matters to me .
What is a few minutes in the grand scheme of things.
