Here a snippet of the data inspection:
20140620054534 rain0 0 0 3678
20140620054636 rain0 0 0 3678
20140620054740 rain0 0 0 3678
20140620054844 rain0 0 0 3678
20140620054911 rain0 0 0 3678
20140620055014 rain0 0 0 3678
20140620055118 rain0 0 0 3678
We had Rain yesterday and we have had rain this whole month.
The console shows it and my meteobridge can read it.
You are just starting with Meteohub? Dit Meteohub already run BEFORE the rain occured? Wim
That is right this is the first time I am running meteohub.
It occurred after.
So differences between the console and a Meteohub in displayed rain values:
1. Meteohub did not see the rain because it was not connected
2. The recomputation for this month/year data did not run yet
3. No "yesterday" value saved
4. Console displays 24 hour rain, MH not.
1. Did MH get the sensor data?
What I tried to ask in my previous post, was Meteohub operational and listening to the VP sensors and started it to rain then?
The sensor readings you show in your post cleary state
that it is not raining.When it is raining, you will see values in the sensors reading where now only zeros are displayed and the last total field will increase.
2. Normally MH displays the rain in the today values. During the day/night recomputations are run (cronjobs) to compute month and year values.
3. There is no yesterday tag so you have to take care of that yourself. The Saratoga and Leuven templates run a scheduled job at 23:55 every day yo copy the today values to yesterday values.
4. The console has a wider memory compared to a just started Meteohub. It "knows" all rain in the past 24 hours, so also the rain before Meteohub was started.
You have to feed Meteohub with this years and this month data data to get the same readings as the console.
===
Wim
