GW1000 + WH57 lightning sensor only - Lightning not showing in MB. **unsolved**

[jmontamat]

An RPI4 4g WS80 + WH57 + WH40 I don't know if it will work currently?

[Gyvate]

It should work perfectly. Look up my tests a few post above.
Test #4 - in red - is your constellation.
And I have a similar production constellation (more sensors).

[woolfg]

Hi

Do we have a timescale as to when this might be fixed ?

I see there have been numerous updates for the Pro recently but nothing for this

Regards

Graham

[jmontamat]

It should work perfectly. Look up my tests a few post above.
Test #4 - in red - is your constellation.
And I have a similar production constellation (more sensors).

Ok thanks I'll try.

[jmontamat]

Works well on:

Platform: Raspberry Pi 4 Model B

SW Version: Meteobridge 5.2 (Jul 15 2021, build 2427), FW 1.3

Sin título.png (31.25 KiB) Viewed 4349 times

[Gyvate]

Works well on:

Platform: Raspberry Pi 4 Model B

SW Version: Meteobridge 5.2 (Jul 15 2021, build 2427), FW 1.3

Sin título.png

This is only true in this context, if you have a GW1000 and a WH57 as the ONLY sensor.
Otherwise your statement is WRONG in the context of this post.
I can see in the picture that you have at least a solar radiation sensor active, and as they don't come alone, they will come with wind, outdoor temp and humidity sensors. That this works we know since long. See also tests above (#4).

The issue here is that MB does NOT records lightning strikes, when a WH57 is the ONLY sensor connected to a GW1000.
This has been tested and verified - see tests above - and it needs to be corrected in the logger software !


If you just wanted to show that your constellation works fine with MB and the RPi - that's great - but is a bit misleading in the context of this post.

[Bart]

I have my doubts about that Ecowitt setup of the GW1000 with a WH51 soil (and maybe the WH57 Lightning), sensor without outside temp sensor. What I have done after I received the GW1000 and the soil sensor (see the post before ..I have added the GW1000 in my MB RPI as an extra "station". That resulted in my original question that hooked up to what is being discussed here. That day I suddenly had a problem with my AirLink, which fell out of the network.
Can happen, so power off and power back on. That night my RPI turned out to be offline. Strange, its UTP connected. The AirLink went out again. I then tried (ceteris paribus) solutions one by one to solve the problems. Nothing seemed to work for both at the same time. Until I disconnected the extra station (the GW1000) from the MB RPI. The AirLink came online and stayed online and the MB RPI, which dropped out of my network a few more times, stayed online.
Incidentally, the AQ part of my AirLink is now defective, why is still unknown. Because I assumed that it might still be a network setting, I resigned.

Until I saw Weatherist34, Brian's, post on the Weather34 forum on various sub topics including a paragraph Among other things, he wrote: "...Ecowitt users ...... this brand is extremely confusing .... ....,look around the various forums you will see the word "confused" mentioned frequently well that's the same for me when I attempt to develop for it "CONFUSED IS AN UNDERSTATEMENT" ..."

I cannot judge whether there is a causal link with the problem I experienced, I know that coincidence doesn't exist. I'm slowly starting to seriously doubt whether I'll still buy that Lightning Sensor. At least I won't connect it via the bridge to a Meteobridge. So Gyvate, I'm not going to try the GW1000 on the NanoSD link like I said earlier.

[Gyvate]

So we have two different things/issues here:
1. the logger not recognizing an only-sensor with a GW1000 (GW1000 + WH57, GW1000 + WH51, maybe also GW1000 + WH45 only [to be tested]) - that's the OP

2. a possible interference between a GW1000 and your AirLink (even though I recall that there are people in this/the wxformum.net forum who have your constellation or a similar one without issues).

Did you try to reverse the station sequence ? Meaning setting the GW1000 as primary station and the AirLink as 2nd station ?
If you have only a production system, this may not make sense as you would mess up the database entries.
But if you have test system/installation, you could find out

Regarding Brian's (weatherist34) statement:
as much as I appreciate his work, but I can't keep from thinking that he is not in-biased here:
Davis +++++, Ecowitt ------
If you only look at (justified or unjustified) negative posts regarding Ecowitt station's "misbehaviour", you can of course get that impression.
Very few of them are really Ecowitt station/system caused, and much has been corrected by firmware updates or application software updates (weewx, CumulusMX, Meteobridge to name a few) lately.
And there can be Friday models with any brand.
Those who are more familiar with the Ecowitt world (and Brian is not), would rarely share his opinion (unless you are just looking for a projection screen for your understandable frustration when your station or software doesn't behave as expected).
I consider myself as an extensive Ecowitt user and am also critical where imo appropriate.
But there are in my observation only few things which are not optimal in the Ecowitt (and clone) world.
Of course there's always still improvement potential.
Most issues are either users lacking knowledge (and often not reading manuals, WiKis etc. but complain) or application software based.
You can easily see that in this forum and in the wxforum.net.
I personally prefer fact-based discussions.

[woolfg]

Hi Bart

I have a Davis Air Quality sensor and an Ecowitt lightning sensor

I havent had any instance of my AQ sensor dropping out - it has run perfectly with my Meteobridge Pro and Weatherlink

I would suggest the fault is elsewhere

Regards

Graham

[Bart]

I personally prefer fact-based discussions.

I totally agree with you. Fact-based. That's exactly why I shared my experience with the Airlink and the MB RPI that went offline and (both simultaneously and individually at times). Twice a fact. In a network where I had 34 devices online at that time of which exactly these were "confused" I see that as a very clear signal.

For the rest, I would like to emphasize that I only have the Ecowitt GW 1000 and the accidentally obtained soil sensor of that brand. So no complete weather station from Ecowitt. I'm certainly not an expert on that brand, nor am I a critic.
I just want to share that this happened to me. That in conjunction with what has been discussed here had that not been the case, I would have seen what happened to me as a separate issue. As an unfortunate fact.
I don't have a test environment (yet..). Otherwise, I'll definitely try that. For the complete picture: now a WLL on the MB RPI is the primary, the Airlink 2nd and the GW 1000 (was) extra.
To make it complete and correct I made a small correction in the 1st sentence of my previous post.

Yours faithfully,
Bart

[weatherist34]

So we have two different things/issues here:
1. the logger not recognizing an only-sensor with a GW1000 (GW1000 + WH57, GW1000 + WH51, maybe also GW1000 + WH45 only [to be tested]) - that's the OP

2. a possible interference between a GW1000 and your AirLink (even though I recall that there are people in this/the wxformum.net forum who have your constellation or a similar one without issues).

Did you try to reverse the station sequence ? Meaning setting the GW1000 as primary station and the AirLink as 2nd station ?
If you have only a production system, this may not make sense as you would mess up the database entries.
But if you have test system/installation, you could find out

Regarding Brian's (weatherist34) statement:
as much as I appreciate his work, but I can't keep from thinking that he is not in-biased here:
Davis +++++, Ecowitt ------
If you only look at (justified or unjustified) negative posts regarding Ecowitt station's "misbehaviour", you can of course get that impression.
Very few of them are really Ecowitt station/system caused, and much has been corrected by firmware updates or application software updates (weewx, CumulusMX, Meteobridge to name a few) lately.
And there can be Friday models with any brand.
Those who are more familiar with the Ecowitt world (and Brian is not), would rarely share his opinion (unless you are just looking for a projection screen for your understandable frustration when your station or software doesn't behave as expected).
I consider myself as an extensive Ecowitt user and am also critical where imo appropriate.
But there are in my observation only few things which are not optimal in the Ecowitt (and clone) world.
Of course there's always still improvement potential.
Most issues are either users lacking knowledge (and often not reading manuals, WiKis etc. but complain) or application software based.
You can easily see that in this forum and in the wxforum.net.
I personally prefer fact-based discussions.

unfortunately your very wrong im not bias at all , simply davis + meteobridge works as expected if it didnt i wouldnt develop a template for many years now id simply use what davis offers with WLL today,if owned an ecowitt id simpy use what they offer in there dashboard because it works and doesnt require any website costs or overhead support , i just want to see the data in a clean way .at present for me i dont see a common configuration with ecowitt or alike when tied to a meteobridge , occasionally it occurs with davis hardware i.e an extra leaf sensor i can adapt to that easily for individuals but throw 8 or more sensors at me and no guarantee users are going to run it an identical setup then Im lost how to easily have this manageable without encouraging end users to hard code various areas of the template this when things get messy and unmanageable.i would like to see a common form across end user setups then its easily to implement and develop around without continuously going back and forth . so im not bias just want to see some form of common use. if that cant happen then im not really interested as it makes no odds to me but ill always try and help individuals if it’s manageable.

@graham so do you have lightning sensor working with meteobridge ? if so drop me an email im here for the next 10 days so could probably get it all working as expected or like how myself and chuck use it in the template then we are on the same boat going forth..

[Gyvate]

The trouble and the reason for @woolfg's OP is that the Meteobridge logger does NOT (yet, but when ....?)
provide the lightning sensor data from the GW1000 as it is not (yet) programmed for a GW1000 with the WH57 (lightning sensor) as the only outdoor sensor. The above tests done by me confirm his findings and Boris has to do something here.
viewtopic.php?p=40090#p40090
And that's not an impossible task as other programs like weewx or CumulusMX or WeatherDisplay can handle this constellation.

[Andyk1]

I have never been able to get the GW1000 lightning sensor to work since after version 4.5 something. Have tried many different ways (remapping) etc. but no luck. Works in ECOwitts site but never in MB Rpi 4.

[Gyvate]

what's your sensor constellation ?
GW1000 + WH57 (lightning) + which other sensors, sensor arrays ?
Is your GW1000 on firmware 1.6.8 ?
It works fine (notwithstanding some still pending "beauty work") for me ever since I got the WH57.
So far, the GW1000 + extra-sensor-only constellations do not work.

[woolfg]

Hi

I dont know if the latest build Aug 8th is supposed to fix this but my WH57 Lightning sensor are still not showing

Regards

Graham