Hi Gary,
I think you know that by saying that your driver were "dump" I didn't
want to discredit your work. 😉 - Just that the work is done by the
console (or earlier in the chain).
The WH57 provides only the number of strikes since the last reporting
including the distance of that last strike. In an interval of 79 seconds
which starts with the first detection.
It's the console which does the counting and adds the EPOCH time stamp
as the WH57 has no internal clock which is gauged against current real time.
From there the API response from the console is number of strikes, time
stamp of last strike, distance of last strike (which will be saved in
the console after a thunderstorm until the next lightning detection).
The number of strikes (strike count) is reset to zero by the console at
midnight. That's why it keeps on sending, count 0, distance last strike,
time stamp last strike after a day with lightnings and no new lightning
detected past midnight.
The detection, counting etc. is done by the AS3935 IC inside the WH57
(https://www.sciosense.com/products/wireless-sensor-nodes/as3935-franklin-lightning-sensor-ic/
<https://www.sciosense.com/products/wireless-sensor-nodes/as3935-franklin-lightning-sensor-ic/>
).
As for weighting, I don't see a reason for that either.
Rainer
On 21.06.2023 22:32, gjr80 wrote:
I really don't see the point of trying to weight lightning strike
distance from a WH57. In essence the WH57 reports three things; the
number of lightning strike detected today, the time of the last
detected lightning strike and the distance of the last lightning
strike. This is clearly stated in the WH57 manual. The Ecowitt Gateway
API is not so specific (it omits the word 'last'), but the API reports
the same data as displayed by the Ecowitt's WSView Plus app so I think
it is safe to assume the API reports time and distance of last strike.
So if a given number of lightning strikes occur in a period the
Ecowitt gateway driver and any connected console/app will only see
time and distance data for the last detected strike, nothing for any
earlier strikes.
The referenced PR does not state what type of lighting detector is
used, but the code looks suspiciously Ecowitt gateway driver'ish and
for the reasons outlined above I really don't see any value in
weighting light strike distance.
Gary
--
You received this message because you are subscribed to the Google
Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/bcd2d06b-bfb6-48bd-b290-d8710a869ddan%40googlegroups.com
<https://groups.google.com/d/msgid/weewx-user/bcd2d06b-bfb6-48bd-b290-d8710a869ddan%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/fad4a170-3b44-505d-4d25-cfbb01df3c9d%40gmail.com.
