Very annoying inconsistency. **solved**

[krischj]

Reporting on sensors works really well with MeteoBridge.
Of course choices has been made, ex: when reporting on sensor and for a given timeframe, having several “max” values (several occurrences of the same max-value) within a given timeframe, it is always the first max-value that is reported (you can see that when also reporting on the max-time for that max sensor value). This is perfectly fine and is consistent thought-out all the sensors with one very annoying exception.
The wind0maxdir-sensor consistently reports the wind0maxdir:degress from the latest occurrence within a given timeframe, not the first.

Reporting on:
[wind0wind-max.1:--] [wind0wind-maxtime.ij:--]:[wind0wind-maxtime.kl:--] [wind0maxdir-max.0:--]

Given that you have 2 [wind0wind-max.1:--]=11,9 m/s first with [wind0maxdir-max.0:--]=281 deg and @ 17:09 hrs and the second one with [wind0maxdir-max.0:--]=303 deg @ 17:18 hrs,

the report would be:
11,9 17:09 303

Where it should be:
11,9 17:09 281

Would it possible change this and make [wind0maxdir-max] consistent with all the other sensors, meaning reporting on the first occurrence within a given timeframe instead of the last.

sensor.jpg (160.19 KiB) Viewed 2391 times

report.jpg (139.27 KiB) Viewed 2391 times

//kris

[admin]

Looks like this issue shows up when doing exports, not when using the template replacement. right?

I checked code and on template evaluation the first occurrence is selected while the export and graphing code selects the last one.
I will change to always first occurrence in next release.

Thanks for spotting this.

[Mattk]

Why should it be the first occurrence?

The last occurrence is really the most relevant one? OR am I missing something here?

[admin]

I don't have a bias on that. Can also make it the last occurrence.
Please try just released version.

[krischj]

Hi Boris,
It works perfectly, Thanks
All sensors incl wind0maxdir-sensor are now reporting consistently.

(@Mattk: As mentioned consistency across all sensor is the important issue, first or last is less important, - personally I prefer first)

//kris

[Mattk]

....(@Mattk: As mentioned consistency across all sensor is the important issue, first or last is less important, - personally I prefer first)

From a wind perspective the time and direction of say a peak gust of the day can be rather meaningless based on the first occurrence. For example a peak gust at say 12:01 being the first occurrence is flagged as the peak gust for the day then at say 18:00 hours that is still being reported as the peak gust details for the whole day when maybe at 17:00 hours there was an equal peak gust speed (and this scenario does occur quite a bit) and even being a totally different direction that has way more importance than the first so called gust occurrence at 12:01

[admin]

It is now reporting the last incident.

[krischj]

Hi Boris,
There was a perfect consistency across all sensor on the 23rd release, now the inconsistency has been re-introduced.
There is now no way to get the the wind0maxdir for the either the first or last wind0wind-max, since wind0wind reports first and wind0maxdir reports the last.

As long as as all sensors report the same (first or last) I am happy, bur all other reports on first, so...

/kris

[admin]

please try again with just released version.

[krischj]

just tried april 27th release, the export is still the same as in my april 17th post.
The april 23rd release reported 281 degrees @ 17:09 which was perfect and consistent

//kris