That's pretty much it. You'll get a lot more than three packets in a five minute interval, though. There's no way of knowing how many, though, so what's important is how many you get in the reporting interval (five minutes by default).Yes, it was just a theoretical example.
I use the naming convention lightningStrikesTotal, which matches that used in the existing weewx db schema.
Again, in the documentation I saw nothing about lightning, there's not a single mention of it. Not sure how we're supposed to know what to use.
In the default (wview I guess) schema, there's not lightning fields....
BTW: what happens when you do the delta when it wraps around? Do you just accept that one time the value will be wrong?
Matt suggested (and I used) the "Total" for the value from the sensor because it's the running of all time strikes modulo 128 received since the last time the sensor was reset (the same way the rain sensor works as a tip counter). This number is useless if not compared to previous values.
So, a further test, as we just had another nice storm.
I looked at the logs, and assuming the data which reads "lines=" is the data from the sensor, and "packet=" is the data used by weewx, the following occurred.
(I have all the log data if any further analysis is required)
* whatever the 433 read, was recorded in db, bar one missing strike number.
* the 433 was getting data every 20 seconds, I don't think anything was missed, and as it's a running total, it would be picked up anyway...
* most interesting, the strike_total that the 433 read and weewx stored in db went up from 17 to 46 (29 strikes), however, the console went from 82 to 121 (39) not accounting for strikes that fell off the 48 hour window.
So, the data from the sensor looks to be out, by quite a long way.