Meteobridge-GW1000 no lightning data recognized by MB

[wvdkuil]

My Meteobridge:
DIR-505 (no USB hub) RAM: 61556 kB total, 28020 kB free (54% used) SW Version: Meteobridge 4.3 (Apr 7 2020, build 13444), FW 1.3

The Metebridge contacts the GW1000 with correct IP-nr

Code: Select all

wnetd  (29.04.2020 09:34:32): process started.
system (29.04.2020 09:34:32): start of logging process initiated.
wnetd  (29.04.2020 09:34:32): send data thread started (pid:1711 tid:1713)
logger (29.04.2020 09:34:32): historical data loaded (32 records).
logger (29.04.2020 09:34:32): data logger (version 5.1d, build 13444) started.
logger (29.04.2020 09:34:33): connect station 0 (GW1000 via TCP/IP).
logger (29.04.2020 09:34:36): sensors are now providing data.
logger (29.04.2020 09:34:36): services started.

The live data tab does not show the lightning sensor => attached screenshot

The MB-template set uses following specifications

Code: Select all

#
|lightning|light|[lgt0total-act:--]|!
|lightningtime|light|--]|!
|lightningkm|light|[lgt0dist-act.1:--]|!

All lightning data is returned as -- Other extra sensors work correctly

TheGW1000 uploads all data correctly to my website and that data contains valid lightning data

Code: Select all

    [PASSKEY] => C58C98F4E7C3CD9832EB2BC68DFF2428
    [stationtype] => GW1000A_V1.5.7
    [dateutc] => 2020-04-29 07:38:16
    [tempinf] => 71.6
    [humidityin] => 56
    [baromrelin] => 29.554
    [baromabsin] => 29.554
    [tempf] => 54.0
    [humidity] => 79
    [winddir] => 297
    [windspeedmph] => 8.05
    [windgustmph] => 10.29
    [maxdailygust] => 12.53
    [solarradiation] => 143.13
    [uv] => 1
    [rainratein] => 0.000
    [eventrainin] => 0.240
    [hourlyrainin] => 0.000
    [dailyrainin] => 0.059
    [weeklyrainin] => 0.240
    [monthlyrainin] => 0.449
    [yearlyrainin] => 8.161
    [totalrainin] => 8.161
    [temp1f] => 55.94
    [humidity1] => 85
    [soilmoisture1] => 41
    [pm25_ch1] => 23.0
    [pm25_avg_24h_ch1] => 55.6
    [lightning_time] => 1588094357
    [lightning_num] => 0
    [lightning] => 34
    [wh65batt] => 0
    [batt1] => 0
    [soilbatt1] => 1.6
    [pm25batt1] => 3
    [wh57batt] => 4
    [freq] => 868M
    [model] => GW1000_Pro

If needed i can sent the log-in credentials.

Thanks in advance,
Wim

[admin]

A remote login would be fine.

[xannor]

I am curious of the status of this. I just got the ecowitt detector and I noticed the same. I waited until ecowitt.net showed an event in cause the meteobridge just didnt show when no data was avail. I agree it seems it is not recording the sensor data.

[wvdkuil]

I am curious of the status of this. I just got the ecowitt detector and I noticed the same. I waited until ecowitt.net showed an event in cause the meteobridge just didnt show when no data was avail. I agree it seems it is not recording the sensor data.

I have sent my credentials the same day via e-mail
But admin seems to be very busy.

Wim

[kd7eir]

They have known about this issue since April 29, roughly 40 DAYS and yet they have done NOTHING to resolve the issue. It's been 38 DAYS since they even addressed the issue, and all that inspiring communication said was "A remote login would be fine."

Face it folks, Meteobridge is fast becoming just another pile of abandonware. Meteobridge would like to thank all of the people that PAID THEM in exchange for nonexistent support.

[admin]

@kd7eir: Looks like you expect a personal assistent right at your command. May be you get better heard if you stop complaining that you are not number 1 in the queue.

@wvdkull: the listed data is interesting. Meteobridge has support for lightning sensor built in, so I wonder why it does not register anything. I will check a few things...

[wvdkuil]

Today there was lightning.

The GW1000 now runs with firmware 1.6.0
The "Custom upload" and wsView show same information

Code: Select all

    [lightning_time] => 1591990947
    [lightning_num] => 10
    [lightning] => 17

The Meteobridge uses version 4.3 (Jun 12 2020, build 13547), FW 1.3

The Meteobridge live-data tab shows lightning information

Code: Select all

Lightning	1 sec	distance 17.0km energy 10	distance 10.6mls energy 10

But not the last strike time?

The template file contains

Code: Select all

|lightning|light|[lgt0total-act:--]|!
|lightningtime|light|--]|!
|lightningkm|light|[lgt0dist-act.1:--]|!

The information does not arrive in the uploaded files
The returned data

Code: Select all

|lightning|light|--|!
|lightningtime|light|--]|!
|lightningkm|light|--|!

What am I doing wrong?

Wim

[admin]

Last strike time should be accessible als "lgt0total-nonzerotime".

Currently data is only recorded when fresh lightning appears. So when hold time is passed "-act" will not report anything. asking for min/max/average data should produce something, when there has been a lightning event in the requested time frame. You can also ak for time of min/max lightning event (in terms of distance). But I have not tested this as I neither have this sensor nor do I have lightning right now.

[wvdkuil]

Last strike time should be accessible als "lgt0total-nonzerotime".

Currently data is only recorded when fresh lightning appears. So when hold time is passed "-act" will not report anything. asking for min/max/average data should produce something, when there has been a lightning event in the requested time frame. You can also ak for time of min/max lightning event (in terms of distance). But I have not tested this as I neither have this sensor nor do I have lightning right now.

I am stuck.

Live-data shows yesterdays lightning

Code: Select all

Lightning	0 sec	distance 17.0km energy 0	distance 10.6mls energy 0

I tried the three lightning sensors lgt0total lgt0dist lgt0energy with different selectors in https://pwsdashboard.com/extra_mb.txt

Code: Select all

#
|lightning|light|[lgt0total-dmax:--]|!
|lightningtime|light|[lgt0total-nonzerotime:--]|!
|lightningkm|light|[lgt0dist-dmin.1:--]|!
#
|lightning_y|light|[lgt0total-ymax:--]|!
|lightningtime_y|light|[lgt0total-ymaxtime:--]|!   
|lightningkm_y|light|[lgt0dist-ymin.1:--]|!
#
|lightning_unknown_0|text|lgt0energy-daysum:--]|!
|lightning_unknown_1|text|lgt0energy-ymax:--]|!
|lightning_unknown_2|text|lgt0energy-dmax:--]|!   
|lightning_unknown_3|text|lgt0energy-nonzerotime:--]|!   

But no data is returned at all https://pwsdashboard.com/extra.txt

Code: Select all

#
|lightning|light|--|!
|lightningtime|light|--|!
|lightningkm|light|--|!
#
|lightning_y|light|--|!
|lightningtime_y|light|--|!   
|lightningkm_y|light|--|!
#
|lightning_unknown_0|text|lgt0energy-daysum:--]|!
|lightning_unknown_1|text|lgt0energy-ymax:--]|!
|lightning_unknown_2|text|lgt0energy-dmax:--]|!   
|lightning_unknown_3|text|lgt0energy-nonzerotime:--]|!   

The GW1000 is still delivering its data

Code: Select all

    [lightning_time] => 1591990948
    [lightning_num] => 0
    [lightning] => 17

As the data is visible in the Meteobridge Live-data tab, there must be some kind of typing error or misunderstanding with the sensor-selector specification. Also the template sensor lgt0energy is not recognized by the meteobridge.
Any ideas?

[_John C]

Today was the first day with lightning in the area since I got the lightning detector. The meteobridge registered the lightning but nothing sent to Ambient. At least I know the meteobridge is reading lightning data from the GW1000. The lightning sensor only appeared in the meteobridge live data when there was lightning.

[xannor]

I have to agree that the meteobridge is not logging correctly. I finally got it to display a strike, but if I run a template with:

Code: Select all

[lgt0total-ymax:--]

it just gives --, it should at least report 1 strike for the year. I have also tried the others and no results.

I even tried:

Code: Select all

[DD]/[MM]/[YYYY];[hh]:[mm]:[ss]; [lgt0energy-act:--] [lgt0dist-act:--] [lgt0dist-age:--] [lgt0total-daysum.0:--] [lgt0total-monthsum.0:--] [lgt0total-yearsum.0:--]

and it just outputs:

Code: Select all

13/06/2020;17:52:38; -- -- -- -- -- --

but the live data page report:

Code: Select all

Lightning	7 sec	distance 24.0km energy 1	distance 14.9mls energy 1

unfortunately, right now, not having much in storms, if this was working a week ago I would have a lot of data to test with.

[admin]

ok, I will test with simulated strikes. stay tuned.

This is how you get the logged lightning data. Assume we have this status on "Live Data" tab. Lightning total and energy are cumul sensors (like rain total), which report sums.

Bildschirmfoto 2020-06-14 um 10.29.50.png (24.73 KiB) Viewed 5461 times

yesterdays total: [lgt0total-ydaysum:--]
this months total: [lgt0total-monthsum:--]
date/time of last strike: [lgt0total-nonzerotime:--]
min distance of today: [lgt0dist-dmin:--]

Distance looks odd to me, as it should do "--" when no strike in the selected time frame. Another thing to look at...

[admin]

Just released update should do better on counting strikes (lgt0total) and can report last event, even when outdated regarding to hold time settings (lgt0dist-lastval) and also tells time of last recording (lgt0dist-lasttime).

Please give it a try.

[_John C]

Thank you. Does this update address the not uploading lightning data to AmbientWeather ? I'm expecting lightning this evening.

Thanks

[admin]

Good point, that was not yet included, but I just added it as well. Please reboot to give it a try.