Cumulus Support

I am using rtl_433 to read various sensors including the WH57C Thunder and Lightning sensor.
RTL_433 publishs the data on my HiveMQ broker but I am puzzled by the data (or lack thereof) and wonder if someone can tell me what data
turns up (preferably before the next lightning strike!! )

My unit sends the following amongst other data:
state= reset
flags = 83
strike_count = 0

So strike _count is obviously the Number of strikes today (using the nomencleture of the CMX extra sensor data but:

1: what do "flags" mean?
2: what does "state" mean?
3; Where is the distance to strike?

Also a bit puzzled as to why it tx's on two frequencies...

Grateful for any help/pointers...

For anyone wanting the same information this is what I have discovered so far:

I have seen several changes to the state:

state = "reset" (on power up of the WH57)
state = "interference" (when I was trying to emulate a strike)
state = "strike" (possibly a false positive in my case but assume this is what it changes to for real lightning strike)

strike_count = an integer that slowly increments as a strike occurs. This is a best guess as I haven't
seen any lightning yet and after my initial count of 1 it stayed at 1 . So I guess a bit
like the rain ticks that never goes down.

storm_dist_km = an estimate of the distance to the strike.
flags = haven't worked these out but I have seen changes...

Yes, that might be interesting. Never worked wit rtl_433. Might be a logging possibility for the lightning detector?

Hans,

Yes I am now logging the data to an sql database along with temp, rain last hour and humidity ...

(waiting for a way to input this to cumulusutils..! )

If you log it to a CSV file in a continuous timeseries you already can chart it in CUtils (after some additional work on my side). See the most recent release. If you publish the hardware part and the rtl_433 part as a total setup you may attract some attention from those who wish to log the Ecowitt lightning sensor.

according to one of the other forum members: (with thanks)

The strike_count rolls over @ 255 and start over @ 0.

For information on the AS3935 sensor is found here: https://www.mouser.com/pdfdocs/AMS_AS39 ... eet_v4.pdf