meteohub.de

Thanks, updated, just need to wait for the lightning now.

Rebooted the Meteobridge to SW Version: Meteobridge 4.3 (Jun 14 2020, build 13564), FW 1.3

Live data tab shows last measurement + last time in red color Template file: https://pwsdashboard.com/extra_mb.txt All lightning lines return -- in the uploaded file https://pwsdashboard.com/extra.txt But I wonder why last time is in red as it should always be transmitted by the GW1000.
A value of zero is needed to signal that there is no lightning detected.

Just wait for new lightning events to show more data.

Wim

I have something I'm able to trick the lightning detector into thinking there is a lightning strike. It's registering on the app for the GW1000. I can get it to appear in the live data page on the meteobridge. However it's registering stikes as energy instead of total strikes. Shouldn't the strike count come in as total strikes instead of energy?

_John C wrote: Sun Jun 14, 2020 1:16 pm Thanks, updated, just need to wait for the lightning now.

Just had first lightning event since updating but no lightning has appeared on Ambientweather.

The lightning did register on the Meteobridge.
Lightning 7 min distance 34.0km energy 1
distance 21.1mls energy 1

Had a decent amount of lightning the past couple of days. I even had a small storm roll through today and ecowitt.net reports

The only information present on the meteobridge live data tab is the last recorded strike and info. I get no historical data, so I do not think it is actually logging anything, which I believe is why the templates do not work.

xannor wrote: Sat Jun 20, 2020 1:49 am Had a decent amount of lightning the past couple of days. I even had a small storm roll through today and ecowitt.net reports
The only information present on the meteobridge live data tab is the last recorded strike and info. I get no historical data, so I do not think it is actually logging anything, which I believe is why the templates do not work.

Same here only lightning with the count of strikes labeled as energy in the LiveData tab, time always in red.
None of the template-labels give any data.
There is also no "energy" label known.

Is is sad as the GW1000 added to a Meteobridge is a very interesting setup due to all the different sensors available.

Wim

That entries are marked red is to be expected, as Meteobridge does only register new lightning events. Nevertheless, "lastval" and "lasttime" selectors should give that data. Whether what Meteobridge reports as energy is energy or lightning count (of what period?) is totally unclear from the very poor and inconsistent docs from the manufacturer that I could have a look on by kind intervention of a user.

@wvdkull: when you send me your remote login details I will have another look.

admin wrote: Sun Jun 21, 2020 9:39 am That entries are marked red is to be expected, as Meteobridge does only register new lightning events. Nevertheless, "lastval" and "lasttime" selectors should give that data. Whether what Meteobridge reports as energy is energy or lightning count (of what period?) is totally unclear from the very poor and inconsistent docs from the manufacturer that I could have a look on by kind intervention of a user.

@wvdkull: when you send me your remote login details I will have another look.

The number that Meteobridge is showing as "energy" matches with the strike count on the GW1000's app and that number is for the day as it looks like it resets everyday to 0. So I would say that number should be reported as lightning count instead of energy.

The energy misunderstanding is probably a translation issue. They probably meant frequency as in occurrence, but it ended up as energy when translated.

AB3WX wrote: Tue Jun 23, 2020 1:19 am

funny side note, your link says Reinerton PA, I am originally from Tioga bout a hundred miles NNW of you near the NY border, though I have lived in Central Florida for the majority of my life.

Have any of you (who have the lightning detector) used it on the Meteobridge services page? IE: Have you set up email, text orTwitter alerts for local lightning? And if so, how well did it work?

I'm trying to get the lightning data imported into Meteotemplate, but after editing the api files it is not finding any lightning data per the three sensor names in the meteobridge template file. Has anyone succeeded in getting the lightning info out of Meteobridge? It shows on my live data tab like others have shown earlier.

hx

Mike

Hi "WA4OPQ"
it appears to me that the lightning sensor(s) in MB are still a place under construction.
I've opened a "ticket" (thread) in the MB Pro section as I own a MB Pro - topic "MB-Pro/GW1000 FW 1.6.1 lightning recording and depiction faulty ? - data disappear" - I will add some more observations today.
The lightning sensor variables (3) had disappeared from my history view, also from the history tab in the web interface, and following some for me not understandable logics have reappeared meanwhile. Their depiction in the history tab is sort of strange - graphically they appear but as values/figures in the hourly table only for one of them. Also the counting of totals is in my opinion faulty. I have had 3 recorded days with lightnings, but the total indicator in the live data history section for month and year still shows only "1" where in my understanding it should be "3". (my understanding of "lightning total" is the number of days where lightning occurred, imho the only thing that makes sense in this context for total unless the # of strikes are meant, but they are already there for each day). Funnily it shows a min and max value, so the total should at least be "2". If you are interested in more details, look up my thread mentioned above which has been visited quite often but no comment so far from anyone.

@ Post by WA4OPQ » Tue Jul 07, 2020 12:50 am
Have any of you (who have the lightning detector) used it on the Meteobridge services page? IE: Have you set up email, text orTwitter alerts for local lightning? And if so, how well did it work?

I'm extracting the database on an hourly basis, meanwhile also including the lightning values - they come out as recorded in the DB (which I still think is inconsistently implemented (see my post in the MB Pro section) - at the least for the min/max of month/year total the "energy" (daily occurrence) and total (in my understanding either the number of days with lightning or the addition of the daily "energies" (occurrences) the recorded data are messed up and reflect neither of what I would expect. (see also below highlighted bold/underlined in the export) - how can there be "0" after an "1" .... ?

the export definition (.exp file/script/report) is such:
[YYYY]-[MM]-[DD],[hh]:[mm],[th0temp-avg.1:],[th0hum-avg.0:],[th0dew-avg.1:],[thb0seapress-avg.1:],[wind0avgwind-avg.1:],[wind0wind-max.1:],[wind0dir-avg.0:],[rain0total-sum.1:], [sol0rad-avg.2:], [air0pm-avg.1:], [air1pm-avg.1:], [th1temp-avg.1:], [th1hum-avg.0:], [th20hum-avg.0:], [th21hum-avg.0:], [th22hum-avg.0:], [th23hum-avg.0:], [th24hum-avg.0:], [lgt0total-avg.0:], [lgt0dist-avg.0:], [lgt0energy-avg.0:]
the result for two occurrences:
2020-08-03,15:12,23.5,52,13.1,1010.2,0.3,0.5,94,0.0, 296.00, 10.0, 9.0, 23.8, 51, 37, 59, 60, 23, , 1, 24, 1
2020-08-03,15:13,23.5,52,13.1,1010.2,0.3,1.0,90,0.0, 283.25, 10.0, 9.0, 23.9, 51, 37, 59, 60, 23, , 1, 24, 1
2020-08-03,15:14,23.5,52,13.1,1010.2,0.2,1.0,120,0.0, 253.75, 10.0, 9.0, 23.9, 51, 37, 59, 60, 23, , 1, 24, 1
2020-08-03,15:15,23.5,54,13.6,1010.2,0.7,1.5,110,0.0, 222.00, 10.0, 9.0, 23.9, 51, 37, 59, 60, 23, , 1, 24, 1
2020-08-03,15:16,23.5,55,13.8,1010.2,0.5,1.0,132,0.0, 198.00, 10.0, 9.0, 23.9, 51, 37, 59, 60, 23, , 1, 24, 1
2020-08-03,15:17,23.3,55,13.8,1010.3,0.0,0.0,111,0.0, 194.00, 10.0, 9.0, 23.9, 51, 37, 60, 60, 23, , 1, 24, 1
2020-08-03,15:18,23.2,56,13.8,1010.3,0.5,1.5,162,0.0, 161.50, 8.5, 9.0, 23.9, 51, 37, 60, 60, 23, , , ,
2020-08-03,15:19,23.0,56,13.7,1010.3,0.1,0.5,120,0.0, 122.50, 7.0, 9.0, 23.9, 51, 37, 60, 60, 23, , , ,
2020-08-03,15:20,22.8,56,13.6,1010.3,0.4,1.0,109,0.0, 110.00, 7.0, 9.0, 23.8, 52, 37, 60, 60, 23, , , ,
2020-08-03,15:21,22.8,56,13.6,1010.3,0.1,0.5,118,0.0, 102.67, 7.0, 9.0, 23.8, 52, 37, 59, 60, 23, , , ,
2020-08-03,15:22,22.7,56,13.5,1010.3,0.3,1.0,111,0.0, 98.33, 7.0, 9.0, 23.8, 52, 37, 59, 60, 23, , 1, 20, 2
2020-08-03,15:23,22.6,56,13.4,1010.3,0.5,1.0,99,0.0, 98.00, 7.0, 9.0, 23.8, 52, 37, 60, 60, 23, , 0, 20, 2
2020-08-03,15:24,22.5,56,13.1,1010.3,0.7,1.0,100,0.0, 100.50, 7.0, 9.0, 23.8, 52, 37, 60, 60, 23, , 0, 20, 2
2020-08-03,15:25,22.4,56,13.2,1010.2,0.7,1.5,83,0.0, 103.50, 7.0, 9.0, 23.7, 51, 37, 59, 60, 23, , 0, 20, 2
2020-08-03,15:26,22.2,55,12.7,1010.1,0.7,1.5,124,0.0, 101.00, 7.0, 9.0, 23.7, 51, 37, 59, 60, 23, , 0, 20, 2
2020-08-03,15:27,22.1,56,12.9,1010.2,0.3,0.5,129,0.0, 95.00, 7.0, 9.0, 23.7, 51, 37, 60, 60, 23, , 0, 20, 2
2020-08-03,15:28,21.8,56,12.6,1010.3,0.2,0.5,119,0.0, 87.50, 9.0, 9.0, 23.6, 50, 37, 60, 60, 23, , , ,
2020-08-03,15:29,21.8,56,12.6,1010.3,0.6,1.0,101,0.0, 84.00, 9.0, 9.0, 23.6, 50, 37, 59, 60, 23, , , ,

Is this what you were looking for ?

@michaeljwestii

I'm facing the same (plus another) issue in the meteotemplate fed by MB.
The Meteotemplate-API provides for 4 Soil-Moisture (default), 1 Lightning and 4 particulate matter (PM2.5 or PM10) sensor values.
I have 5 Soil-Moisture, 2 PM2.5 and 1 lightning sensors - all shown in the live data in MB and in the database (Pro) What arrives at the meteotemplate is:
4 Soil-Moisture (as per Meteotemplate API description the number of sensors is not limited here, but MB sent only 4)
1 PM2.5 (should be 2 and 4 could be sent in the standard/default database definition; MB just sends one)
0 Lightning (where meteotemplate expects the strikes per day; MB sends nothing, no value with the header L: to be found).

=> Meteobridge doesn't send the 2nd PM2.5 and the one and only lightning sensor value(s).
The missing sensors should be included at the MB side.
Some more work for Boris to do !

here the respectively meteotemplateLive.txt file content: (underline and bold by me)
{"U":1596801785,"SW":"meteobridge","T":33.7,"TMX":33.7,"TMN":33.7,"H":35,"P":1018.5,"W":0.4,"G":1.8,"B":96,"R":0,"RR":0,"S":769,"UV":7,"TIN":30.5,"HIN":40,"T1":34.4,"H1":35,"SM1":35,"SM2":35,"SM3":31,"SM4":41,"PP1":7,"UTime":1596801785,"SWTime":1596801785,"TTime":1596801785,"TMXTime":1596801785,"TMNTime":1596801785,"HTime":1596801785,"PTime":1596801785,"WTime":1596801785,"GTime":1596801785,"BTime":1596801785,"RTime":1596801785,"RRTime":1596801785,"STime":1596801785,"UVTime":1596801785,"TINTime":1596801785,"HINTime":1596801785,"T1Time":1596801785,"H1Time":1596801785,"SM1Time":1596801785,"SM2Time":1596801785,"SM3Time":1596801785,"SM4Time":1596801785,"PP1Time":1596801785,"D":16.2,"DTime":1596801785,"A":35.6,"ATime":1596801785}

Gyvate wrote: Tue Aug 04, 2020 10:43 am I'm extracting the database on an hourly basis, meanwhile also including the lightning values -
Is this what you were looking for ?

Actually, no.
I have a remote, unmanned site that sends out weather alerts via Twitter. I'd love to be able to have it send out a Tweet such as: "Lightning detected within 10 miles of Pleasantville, take cover now"