meteohub.de

I've been observing several oddities with the lightening recording and its live and historical data
example see below
at some point in time I could see historical data in the history tab. Meanwhile the sensors have disappeared from the drop-down menu (Pic 3).

I think there is still some work to be done to have the lightening strikes documented and stored (in a retrievable and viewable manner).

Everything is properly shown in the WS View app (only for 24 h) and at Ecowitt.net (last occurence) (Pic4)
By the way - there was a FW update 1.6.1 two days ago - which causes Brian's Weather Display software to report weird rain and lightning data
who also uses the GW1000 API in my case.
Not sure to what extent this also influences the handling of lightning events by MB (it may add to it or may not).

Update:
meanwhile the lightning sensors have (following some logics unexplainable to me) re-appeared again in the view of the history database (history tab) - and even in the history view of the live data tab. I had a few reboots (without updates as the SW is already on the latest version 4.4) and somehow they are back again.
Still I am not happy with the depiction and still think that the display of the recording is faulty and data is missing (at least not visible in the web interface).
- Lightning total should show the number of days when lightening occurred/was recorded - this is not the case right now (see pictures)
- Lightning energy should be renamed to Lightning strikes or Lightning occur. (occurrences per day) - this sensor seems to be recorded partially correctly (OK in live data tab - NOT OK in history tab)
- Lightening distance: OK in live data tab, NOT OK in history tab)
a few examples below for each of the sensors in the history tab only the graph shows data - nothing is shown in the hourly table where per hour window the min and max values should show
the information from the graph should be transferred to the table view the information from the graph should be transferred to the table view
however an average doesn't make sense here in my opinion (in the example 2.5 is wrong for 3 strikes, it should be min=max=average=3) daily values can only 0 or 1, maybe shown as it does at the time of the first occurrence
HOWEVER when the monthly and yearly totals are created, they should be added which is obviously not done also it seems to have "forgotten" the strike 14 km distance (see picture 2 of the original post under the green arrow)
The live data look OK Anybody of the readers have similar observations ?