-
Notifications
You must be signed in to change notification settings - Fork 652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Round 1 begins before NTP is called (wrong timestamp) #2287
Comments
Addendum: ''' 2023-04-03T20:52:07+0200,main,0440.14046,440.14046,440.14046,0.000000,0.00000,no error,0.0,4.0,3.8,0.0,1.2,3.9,0.5,4.6 Messagelog after changed TZ-data to CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00 [0d02h38m30s] 2023-04-03T20:55:03 [OTA] Reboot in 5sec ''' |
This is already adressed and solved in the currrent rolling. Will go to the next release. |
The Problem
After update to V 15.1.1, the first Data entry has a wrong Timestamp (see data- / message log). After changing the time settings (CET / CEST) for Berlin / Germany (long notation) nothing improved. The problem can be reproduced.
In my case, the time is only displayed correctly after synchronization with the NTP server (de.pool.ntp.org). If data is created beforehand with a timestamp, the time will be wrong.
Version
Release: v15.1.1 (Commit: 03c84a1+)
Logfile
Expected Behavior
No response
Screenshots
No response
Additional Context
Current Config.ini
[System]
TimeZone = CET-1CEST,M3.5.0,M10.5.0/3
TimeServer = de.pool.ntp.org
Default Setup watermeter SD-Card config.ini
Warsaw, Poland CET-1CEST,M3.5.0,M10.5.0/3
Correction to:
Berlin, Germany CET-1CEST-2,M3.5.0/02:00:00,M10.5.0/03:00:00
The text was updated successfully, but these errors were encountered: