Can you please enable the Debug NTP option in your Config_Options and post here what you get on the Serial Monitor when the system starts.
Do you have the hardware RTC installed?
Also check if the PI have the the correct Date and Time, when Weewx starts its possible that it syncs the receiver clock with PI clock (that is part of the Davis protocol, however I'm not sure if that is implemented on Weewx, on Cumulus it is).
At last check if you are using the RTClib library that is distributed in the software package and no other, be it older or newer (this is the most probable cause of the issue).
(This post was last modified: 29-10-2018, 05:43 by 41south.)
Here is the debug output, all looks well.
ESP8266 FW Version: AT+GMR
AT version:1.3.0.0(Jul 14 2016 18:54:01)
SDK version:2.0.0(5a875ba)
Farylink Technology Co., Ltd. v1.0.0.2
May 11 2017 22:23:58
OK
RTC current date: Oct 29 2018
RTC current time: 17:39:51
Sending NTP request to sync clock...
NTP replied
UTC time from NTP server: 04:39:52
RTC adjusted to local time: 17:39:52
WiFi connection is ON
The Weewx Pi was not connected this afternoon and the problem still exists, so it isn't coming from there
Yes hardware RTC is installed
Yes this is with the latest libraries, I delete the old folder entirely and copy the new one
Indeed there is a bug in v7.0 b006, it's now fixed. Please download and install latest release (v7.0 b007 - 2018-10-29).
Please report back if the problem is solved.
Thank you.
(This post was last modified: 29-10-2018, 22:19 by engolling.
Edit Reason: Update
)
(29-10-2018, 18:25)Werk_AG Wrote: Hi,
Indeed there is a bug in v7.0 b006, it's now fixed. Please download and install latest release (v7.0 b007 - 2018-10-29).
Please report back if the problem is solved.
Thank you.
Hi Werk,
I had the same problem and updated to b007 but the issue still exists for me but now my time jumps to the 11th of November 2019.
From my logging script, date changed at 20:58 and changed back at 21:27.
Synchronisation at startup works:
Code:
ESP8266 FW Version: AT+GMR
AT version:1.2.0.0(Jul 1 2016 20:04:45)
SDK version:1.5.4.1(39cb9a32)
Ai-Thinker Technology Co. Ltd.
Dec 2 2016 14:21:16
OK
RTC current date: Oct 29 2018
RTC current time: 21:41:57
Sending NTP request to sync clock...
NTP replied
UTC time from NTP server: 20:41:57
RTC adjusted to local time: 21:41:57
RTC current date: Oct 29 2018
RTC current time: 21:41:57
Update: Date still jumps, but when i reset the meduino the RTC has the correct time and date. So I assume strange things a happening while the program is running.
when we try to do things in a rush, most of the times we don't save any time. I did a mistake on last release, can you please try it again (it was updated right now - same build number).
However the truth is that I don't know why this problem was recently started to happen on some systems. Up to know I wasn't unable to fully reproduce it, so I'm just replacing some of the RTC sync code with more "safe" commands.
I really would like to have more feedback, as it seems to not be affecting all systems.
Sometimes there are problems you never thought to be possible.
Those kind of problems caused me to stop developing my own system .
If you tell me the code passage where you assume the bug I will try to reproduce the error by changing the code that the command is executed more often.
Perhaps I have found a condition where the problem can occur. I will test that tonight.
I'm using an NTP server located in my local network, this can be the reason why I never was able to reproduce de problem...