meteohub.de

Hello,

means the update of 27 June goes on under standing parameter is wrong

[rain0total-sum60.1:0]

Below additional information about the bug I've discovered.

So all 5 10 15 30 60 min rain values are wrong.

So not only the 60min rain the homepage of error passed but all sumXX rain values.


in most data update runs counter while it is dry.
This means the update is done on 27 June.
Look at me website

http://www.meteooudkarspel.pd0rok.nl/we ... MB&lang=en


Like to solve quickly.

Thank my thanks.

I have also updated my MeteoBridge software, I have not the mentioned issue luckly.
I notice only that the support for 'windguru' not available is.

After the update yesterday the running version is.
SW Version: Meteobridge 2.5 (Jun 12 2015, build 2814), FW 1.2

Running on as Asus WL330

MeteoOudkarspel wrote:Hello,

means the update of 27 June goes on under standing parameter is wrong

[rain0total-sum60.1:0]

Below additional information about the bug I've discovered.

So all 5 10 15 30 60 min rain values are wrong.

So not only the 60min rain the homepage of error passed but all sumXX rain values.


in most data update runs counter while it is dry.
This means the update is done on 27 June.
Look at me website

http://www.meteooudkarspel.pd0rok.nl/we ... MB&lang=en


Like to solve quickly.

Thank my thanks.

Sincerely,

Ron C.P.J Overtoom Meteo Oudkarspel

I don't have that issue, I see you are running the new Leuven Template (2.7a), I'm running still version 2.6.

assenzuid wrote:

MeteoOudkarspel wrote:Hello,

. . . shortened . . .
Sincerely,

Ron C.P.J Overtoom Meteo Oudkarspel

I don't have that issue, I see you are running the new Leuven Template (2.7a), I'm running still version 2.6.

This has nothing to do with any template. Saratoga or Leuven or any release.

The same tags are used as from the first releases of Meteobridge with this facility.

The errors seems to have started AFTER the code for these tags has changed. Until 2.5 there were only fixed number of minutes.
Now one can specify all minutes between zero and 60. For rain even multiple hours.

But the tags which were fine until 2.5, they now return errornous data at this users site.
[rain0total-sum2.1:0]
[rain0total-sum5.1:0]
[rain0total-sum10.1:0]
[rain0total-sum15.1:0]
[rain0total-sum30.1:0]
[rain0total-sum60.1:0]
Using latest release of Meteobridge (2.5-6582) for TP-LINK TL-MR3020
To see the errors, just check the trends page:
http://www.meteooudkarspel.pd0rok.nl/we ... #data-area

I checked multiple sites I have acces to.
They all use the Asus with a 2.5 release, and that release has totally different build numbers such as Meteobridge (2.5 b 2814).

So it seems to be only in that specific build 6582 for that specific device MR3020.
And I have run out of weather-stations to connect, so I can not setup another Meteobridge at the moment to check.

The user says it occured since a new load of Meteobridge. And since Boris seems to be on vacation, a new release is what we have to wait for.

Wim

I did some more digging for the sum** "problem" with Meteobridge (2.5-6582)

OK: Multiple sites with different other builds, example
Meteobridge (2.5-6387) http://www.gateway2capecod.com/weather2 ... #data-area

ERROR with another 65** build
Meteobridge (2.5 b 6527) http://www.n4gd.net/weather2/
141 | $ws['rainHour'] = wsConvertRainfall('[rain0total-sum60.1:0]',$from);
| $ws['rainHour'] = wsConvertRainfall('36354.6',$from);


And another error I found which looks OK and is reporting 2.5 b 6582, but it is using that tag on a different place
Meteobridge (2.5 b 6582) http://www.meteostroncone.altervista.or ... x.php?p=61
$ws['rainHour'] = wsConvertRainfall('[rain0total-sum60.1:0]',$from);
Printed on the trends page at the rain block as (18285,6 mm ultima ora)

CONCLUSION: Version 2.5-6582 / 6527 which seems to be used for the MR3020 only, shows these errors.

Wim

I can confirm problem with rain values since upgrading to Meteobridge 2.5 Build 6582 this morning. An hourly email I send with the template [rain0total-sum60=in.2:--] has returned the following values over the past few hours even though there has been NO rain...

06:00: 36.68
07:00: 282.97
08:00: 282.97
09:00: 288.21
10:00: 282.97

Oddly, [rain0total-daysum=in.2:--] returns 0.00 every hour as it should.

I can confirm the bug, which should be solved with the update just released.
So please do a reboot and the problem should be solved.

Super thanks for solving the bug.
He is indeed, and there is no rain dates more embarrassed if not rained.

Names me and other leuven-template users, thanks.