Page 1 of 1

Lighning sensor

Posted: Thu 02 Sep 2021 8:55 am
by HansR
I notice that the lightning sensor is not being logged (the only extra sensor not being logged?), at least the Extrafileheader has no fields for it.
I understand I can get the real time values from the webtags to determine its presence. Is that correct or is there another way?

The paragraph on Ecowitt Air quality, leak sensors, lighting detector, and extra temperature sensors tells me about a Leak sensor which also does not seem to be logged (is not in the header file).

I get the following order of values from the header file (I changed the header wording into variables without spaces, I assume it compares easily to the headerfile).
Is there anybody who can confirm this is correct?
In other words: does the header file contain the latest version of the extra sensors, nothing missing, the correct order?

Code: Select all

    internal enum ExtraSensorslogFieldName
    {
        // From the headerfile in the CMX distribution
        thisDate, thisTime, Temp1,Temp2,Temp3,Temp4,Temp5,Temp6,Temp7,Temp8,Temp9,Temp10,
        Humidity1,Humidity2,Humidity3,Humidity4,Humidity5,Humidity6,Humidity7,Humidity8,Humidity9,Humidity10,
        DewPoint1,DewPoint2,DewPoint3,DewPoint4,DewPoint5,DewPoint6,DewPoint7,DewPoint8,DewPoint9,DewPoint10,
        SoilTemp1,SoilTemp2,SoilTemp3,SoilTemp4,
        SoilMoisture1,SoilMoisture2,SoilMoisture3,SoilMoisture4,
        LeafTemp1,LeafTemp2,LeafWetness1,LeafWetness2,
        SoilTemp5,SoilTemp6,SoilTemp7,SoilTemp8,SoilTemp9,SoilTemp10,SoilTemp11,SoilTemp12,SoilTemp13,SoilTemp14,SoilTemp15,SoilTemp16,
        SoilMoisture5,SoilMoisture6,SoilMoisture7,SoilMoisture8,SoilMoisture9,SoilMoisture10,SoilMoisture11,SoilMoisture12,SoilMoisture13,SoilMoisture14,SoilMoisture15,SoilMoisture16,
        AirQuality1,AirQuality2,AirQuality3,AirQuality4,AirQualityAvg1,AirQualityAvg2,AirQualityAvg3,AirQualityAvg4,
        UserTemp1,UserTemp2,UserTemp3,UserTemp4,UserTemp5,UserTemp6,UserTemp7,UserTemp8,
        CO2,CO2Avg,CO2_pm2_5,CO2_pm2_5_avg,CO2_pm10,CO2_PM10_avg,CO2_Temp,CO2_Hum
    };


Re: Lighning sensor

Posted: Thu 02 Sep 2021 9:36 am
by Mapantz
I think it's by design.

The problem I see with it, what would the log info show? It would repeatedly show the same date of the last strike, and the same last strike distance.

I was sending my lightning data to an SQL table so that I could create a highchart graph showing last strike date/time, and the distance, but it just didn't work due to the limited data on offer..

For example; My last strike distance is 6.2 miles, 32 days ago. The graph would show a continuous line or column from that date.

In the end, I kept it simple, and that was to just show the total strikes for the day, up until the roll over time.

You'd need some fancy code to stop it from repeatedly showing the same value until the next strike occurs

Re: Lighning sensor

Posted: Thu 02 Sep 2021 12:49 pm
by HansR
Mapantz wrote: Thu 02 Sep 2021 9:36 am I think it's by design.

The problem I see with it, what would the log info show? It would repeatedly show the same date of the last strike, and the same last strike distance.

I was sending my lightning data to an SQL table so that I could create a highchart graph showing last strike date/time, and the distance, but it just didn't work due to the limited data on offer..

For example; My last strike distance is 6.2 miles, 32 days ago. The graph would show a continuous line or column from that date.

In the end, I kept it simple, and that was to just show the total strikes for the day, up until the roll over time.

You'd need some fancy code to stop it from repeatedly showing the same value until the next strike occurs
Hi, Thanks for the reply.
My first problem is : How do I easily detect a lightning sensor is present (if not present I don't have to do anything) and interpreting live data is not my favourite solution but OK, if need be. And for fancy coding... I have not decided on what my presentation will look like but I already am into fancy coding so who cares about a bit more :lol:
But thanks for the warning, I understand the problem.

You have no remarks on the correctness of the Extrafileheader? You did not experience any issues there?

Re: Lighning sensor

Posted: Thu 02 Sep 2021 1:56 pm
by philpugh
Yes it's a 'simple' device but it seems to work.. I log <#LightningStrikesToday> to my ExtraSensors table (it logs other sensors also) in my database and early morning I create a json file to display that last 31 days of strikes. I use the MySQL Custom Upload - Minute Interval to insert data into this table. I update every 5 mins as the data is not that dynamic.

See https://goosegate.uk/trends.htm#lightning for the result.

Re: Lighning sensor

Posted: Thu 02 Sep 2021 3:05 pm
by beteljuice
Question .....

Is there always a timestamp / distance for each strike, or can the count increase in the sample period but only have 'last strike' data ?

Just thinking if a distance / time scatter is viable.

Re: Lighning sensor

Posted: Thu 02 Sep 2021 3:12 pm
by mcrossley
beteljuice wrote: Thu 02 Sep 2021 3:05 pm Question .....

Is there always a timestamp / distance for each strike, or can the count increase in the sample period but only have 'last strike' data ?

Just thinking if a distance / time scatter is viable.
It's just the last strike data available.

Re: Lighning sensor

Posted: Thu 02 Sep 2021 3:48 pm
by HansR
Well, thanks for reply you all.
I think I'am gong to buy a GW1100 and some sensors just to play with it and then see what I can come up with.