The strikestotal is the value read from the packet. It's an intermediate value and is just the rolling count from the sensor. The deltas changes that to the change since the last time, and the accumulator totals all the deltas for the interval.
So, I get the premise behind it, however not how the naming convention works. E.g. yesterday I was told to use "rain_total" instead of "rain", even though rain_total is nowhere in all the documentation.... so how was I supposed to know!?
I have this now:
[[sensor_map]]
lightning_strikes = strikes_total.002D.AcuriteLightningPacket ## lightning detector
lightning_distance = distance.002D.AcuriteLightningPacket
where lightning_strikes and lightning_distance are the names of the fields in my db, as for some reason they don't exist in the default weather db schema.
I have now added to the end of the SDR section:
[[deltas]]
lightning_strikes = lightning_strikesTotal
However I don't just see why I wouldn't add the "lightning_strikes" to deltas, to tell the system I want deltas for this value.
Why does it get assigned the value of another field (lightning_strikesTotal), and how was that name arrived at?
Then, outside the SDR section, I have
[Accumulator]
[[lightning_strikes]]
extractor = sum
[[lightning_distance]]
extractor = min
but, I am not sure how this can work.
Apologies if I am being dense, I think the lack of documentation doesn't help!
If I understand, delta means the difference between the value and the previous value received from the sensor
So if I got
10 -> stored in db
10
14
17 -> stored in db as delta=3
when it should be 7
However, if I do the sum, I would get this scenario
10 -> stored in db
10 - sum = 20
14 - sum = 34
17 - sum = 51 -> stored in db as 51-34 = 17
which is also wrong.
Also, when I might get 10 readings in one interval, and 11 readings in another, the sum will be wrong quite often.
Yet, you say this is working for you, so I am not sure what I'm not understanding.
Apologies again if I'm just being thick!