meteohub.de

Hi lorenz1982

I confirm I've the same issue.

it's occurs sometime...

check your raw sample (for this timeline), they have been corrupted as meteobridge is not aware it's not synced yet with the right time

cheers

jpouyaud2 wrote: ↑Wed Jan 26, 2022 11:54 pm Hi lorenz1982

I confirm I've the same issue.

it's occurs sometime...

check your raw sample (for this timeline), they have been corrupted as meteobridge is not aware it's not synced yet with the right time

cheers

Yes the old data is overwritten.

What HW platform are you operating on?

admin wrote: ↑Thu Jan 27, 2022 2:23 pm What HW platform are you operating on?

I have a meteobridge installed on Raspberry Pi 3 Model B +. First I had the TP-LINK and I have recovered the settings.

Today I rebooted to install the update and the date went back to January 12, 2022.

This is also what I've reported.
The jump in the past was related to previous reboots. (nothing more consistent).
After each jump in the past, the DB was corrupted and I've spend 1h to find and erase the wrong minute record
cheers

This is why I've requested a feature where the Meteobridge SW start to record RAW only when an ntpq confirm the ntp client is synced to an NTP server with a "*"

after the boot, we should start with "ntpdate" then "ntpd" sync to 2 servers min

I don't know the feasibility with OpenWRT.

if it works it will be much more rock solid

just released update should have the issue fixed.

cool !!

thank you

ok
I've just upgraded
Reboot
and all green

first time I've a clock synchronized after the first reboot

looks promissing

Hi

problem still present
did a reboot this evening for a maintenance

unfortunately the meteobridge reboot at the time of the last reboot (yesterday -24h) and wrote the DB in the past

after a second reboot. prb solved

please, before write the DB, check if the time is accurate

Version 5.3 should have this solved. If not please send credentials for remote login again to "into(at)meteobridge.com".

Oki,

I've activated the remote login

looks like this issue occurs when the reboot is after let's say 1 day after the previouvs reboot but It's not 100% the case..

I still think this is solved. But lets wait a few days if newest version still show issues.