First off, I assume that you extended the WeeWX database schema to hold these values, since it does not have lightning data support out of the box.
WF sends two different UDP packets with lightning data. One is evt_strike, which is sent immediately whenever a lightning strike is detected:
distance.AR-00015732.evt_strike
energy.AR-00015732.evt_strike
The second packet is sent every minute as a summary in obs_air:
lightning_strike_count.AR-00015732.obs_air
lightning_strike_avg_distance.AR-00015732.obs_air
I have no idea how often the obs_air figures reset, be it every minute/packet, hourly, daily, etc. (Confession - I never extended my WeeWX database to try it out, since we don’t have frequent T-storms here to test it.)
I just pulled a few UDP obs_air packets from my two running Airs just now, and the two zeroes are the lightning data here:
{"serial_number":"AR-00012619","type":"obs_air","hub_sn":"HB-00001310","obs":[[1566510332,995.40,24.87,98,0,0,3.50,1]],"firmware_revision":20}
{"serial_number":"AR-00003375","type":"obs_air","hub_sn":"HB-00001310","obs":[[1566510354,995.50,25.10,89,0,0,3.50,1]],"firmware_revision":20}
{"serial_number":"AR-00012619","type":"obs_air","hub_sn":"HB-00001310","obs":[[1566510392,995.50,24.87,98,0,0,3.50,1]],"firmware_revision":20}
{"serial_number":"AR-00003375","type":"obs_air","hub_sn":"HB-00001310","obs":[[1566510414,995.50,25.11,89,0,0,3.50,1]],"firmware_revision":20}
{"serial_number":"AR-00012619","type":"obs_air","hub_sn":"HB-00001310","obs":[[1566510452,995.50,24.87,97,0,0,3.50,1]],"firmware_revision":20}
{"serial_number":"AR-00003375","type":"obs_air","hub_sn":"HB-00001310","obs":[[1566510474,995.50,25.13,89,0,0,3.50,1]],"firmware_revision":20}
{"serial_number":"AR-00012619","type":"obs_air","hub_sn":"HB-00001310","obs":[[1566510512,995.50,24.87,97,0,0,3.50,1]],"firmware_revision":20}
{"serial_number":"AR-00003375","type":"obs_air","hub_sn":"HB-00001310","obs":[[1566510534,995.50,25.14,89,0,0,3.50,1]],"firmware_revision":20}
I had suggested in the past to follow Matthew Wall’s AS3935 raw sensor driver’s database schema extensions and names, but have never looked at the driver code to see how he is calculating averages or if he is storing the raw strike data anywhere.
https://github.com/weewx/weewx/wiki/as3935
Long story short, both lightning observation types are commented out in the WF WeeWX driver’s sample sensor_map because I am not sure where to stick the data or where/how I would ever use it historically. From a SQL perspective, my thought is that throwing the evt_strike figures into a separate database/table might be useful in that you can compute your own averages from the raw data.
If anyone comes up with a solution to store/report on the data, please let me know and I’ll include it in the docs…