meteohub.de

Looks like "double reporting" the rain during the first hour of the day. Data stored in Meteobridge is fine, it is just that when being asked about current daily rainfall between 0:00 and 1:00 it reports two times of the true value. I will have a look.

Do you have per minute data-logging enabled?

admin wrote: ↑Tue Oct 08, 2024 12:47 pm Looks like "double reporting" the rain during the first hour of the day. Data stored in Meteobridge is fine, it is just that when being asked about current daily rainfall between 0:00 and 1:00 it reports two times of the true value. I will have a look.

Do you have per minute data-logging enabled?

Yes, of mapped data only.
Here are the data stored in my personal website. this seems to show that rainfall of more than 1.2 mm was recorded before 01:00

here is an export of my Weathercloud data

Do you think that using the ‘reboot’ script can have an influence on this problem?
I activated it every day at 00:15 during my holidays, so that in the event of a bug, the meteobridge could restart on its own (see the case in March: viewtopic.php?t=17829) now I've deactivated it

Maybe be some logic in that, auto reboot @ 00:15 and rainfall issue between 00:00 & 01:00?

Have you dropped the reboot out to confirm?

I tried with some simulated rain on my Meteobridge PRO2 and let it email "rain0total-daysum" every 5 mins. Unfortunately, it did not show inconsistencies for first hour of the day as you experienced.


Back to my question, do you have per-minute data storing activated?

Mattk wrote: ↑Wed Oct 09, 2024 8:53 am Have you dropped the reboot out to confirm?

Yes, now I have to wait for the next rainfall between 00:00-01:00 (maybe next night)

admin wrote: ↑Wed Oct 09, 2024 10:18 am Back to my question, do you have per-minute data storing activated?

Already answered it , but yes, of mapped data

I have corrected yesterday's rainfall data on the meteobridge because my manual rain gauge showed that the version with 2.4 mm between 00:00 and 01:00 is closer to reality than the version with 1.2 mm.

I now added the 00:15 backup to my MB PRO2, too. we 'll see tomorrow if that provokes the error you experienced.

There is a temporarily "0" while backup is running, but no false increased reporting between 0:00 and 1:00


As long as I cannot reproduce that, I am a bit out of clue...

admin wrote: ↑Thu Oct 10, 2024 7:03 am There is a temporarily "0" while backup is running, but no false increased reporting between 0:00 and 1:00

You mention a "backup". Is it the same as the script I used (reboot.sh)?

Ooops, my fault. Next night it will try reboot.

The reboot did it to make the issue reproducible.


Now I "just" have to understand why

on my side, deactivating the script reboot.sh worked!
The proof is in last night's data (no more jump at 01:00)

Just released update should have this solved.