Ambient has released their lightning detector and the info is available in the api, although as yet undocumented. It appears within the api data set as: “lightning_day”:2,“lightning_time”:1594156540000,“lightning_distance”:14.91,“batt_lightning”:1,“lightning_hour”:2,
I tried mapping it to existing custom tags, but they don’t seem to be picking it up. Might we please have access to these for the main page. I would at least like to add strikes in the last hour and distance. Distance unit is the same as wind, in my case miles. batt_lightning is the battery state 1 for good, 0 for bad. I can send the whole data set if that’s need for position within.
use a new .zip update of WD
then you will see the counts on the main screen
click on that to go to the lightning count screen or get there via view panel…lightning counts
Was coming to the forum to check on support for the new Ambient Lightning Detector given they just started delivering a new batch of orders. Figures Brian was already all over it. WD is the best. Now I just need some lightning!
The counting is somewhat messed up, i have had 34 strikes in the last couple hours. WD says 45 in the 30 and 60 minutes and last 12 hours, but correctly 34 in total since noon and midnight. This month and year are also correct at 42 (8 yesterday). Also, client is not getting any data from server. I like the lightning sound.
Down near the time and data count is the little red lightning strike counter. I cannot find where to control the font size of that number. Its miniscule and i can barely see it. I have diligently looked all about.
More info, i have some more of the tags working, time/date of last strike, hourly counts, monthly counts. Distance to last strike works on the server, but doesn’t pass to the client machine.
Complete clientraw checked. Mother Nature very compliant. Ambient panel says 8 in the last hour, 12 miles last strike. WD Server says 8 in the last hour 12 miles away, WD client says 5 in the last hour and still 0 on miles away.
Its hard to keep up with the changes (storm a few miles north) they are so fast, but server pretty much matches ambientdata.txt and client lags in both count and distance.