Did you get anything going on this? I have added 2 fields to record the data, however I can't make sense of them, nor be sure how to get weewx to use them.
in my sensor map I have ...
I think this is more of a WeeWX issue, but here's what I discovered a year or so ago when I was messing with this.
The value for lightning strikes is, as noted, a total count in seven bits, so it wraps from 127 to 0. That's from the sensor. If the value is the same in consecutive records there were no strikes during that loop interval.
If you put an entry in the [[deltas]] section of the [SDR] driver config that's something like this
Code: [Select]
[sdr]
...
[[deltas]]
lightningStrikes = lightningStrikesTotal you'll get just the number of strikes, not the internal running total.
But that just gives you the lightning strikes per packet received. Each packet will have a new value, and there are dozens of packets during the loop time before weewx writes to the database.
By default, for things it doesn't already know about, weewx averages the values received by packets, so you won't get the total lightning strikes for the reporting interval (usually five minutes) but an average of the strikes per packet.
To fix this you'll need to add or edit the Accumulator top level section in weewx.conf. I added it at the very end.
Code: [Select]
[Accumulator]
[[lightningStrikes]]
extractor = sum
[[lightningDistance]]
extractor = minThe distance extractor gives you the closest lightning strike during the interval. Without it it averages the values, so if you get two with a distance of 1 and eight with a distance of 20, you'd end up with a value of 18 or so. I want to record the smallest distance during the interval, not the average. If you want the average you can leave that out.
The "min" only works for weewx 3.7.2 or later. I got Tom to add it for this very reason.
I haven't looked at this in a year, but I got those lines from my weewx.conf.