> On Nov 7, 2020, at 4:47 PM, vince <[email protected]> wrote: > > >> On Friday, November 6, 2020 at 10:53:12 AM UTC-8, Earl Baugh wrote: >> I see in the weewx db schema that there are: >> >> 'lightning_distance', 'REAL' >> 'lightning_disturber_count', 'REAL' >> 'lightning_energy', 'REAL' >> 'lightning_noise_count', 'REAL' >> 'lightning_strike_count', 'REAL' >> >> [...] > >> But how do I post a noise or disturber record? That isn't clear. Given I >> just see a count, I'm not sure what kind of data would be needed to cause >> that to increment. >> > > Some gear has noise+disturber info available. Some do not. > > All those elements are available if you choose to use them. > But they're not mandatory. > > You can use them, or ignore them, or use the available fiels in the db for > other uses (count every time your nest doorbell triggers and call it a > disturber event :-) > > >> I'm assuming weewx updates the strike count based on the new lightning >> record. But that's a guess... is that guess accurate? >> > > Not in the least. Your extension/service/driver would have to monitor some > sensor and choose to save it in those elements in the db. > > It's all up to the software developer who writes the extension or service or > driver or however you chose to read the sensor's available measurements and > get them into the db. After that weewx can handle the graphing and db > querying etc. kind of heavy lifting for you, but you kinda have to do the > low-level stuff to get the sensor info into the db.
Well in this case, I’m the SW developer :-) ( it’s my day job as well ). I’m just trying to understand the thoughts behind the “count” fields. I have access to disturber and noise events. Would it make sense to post an event that has a value of 1 for count every time? By the name, I was thinking that this was a running total, or number that occurred since last report. I’ve added a number of extra fields to my DB already (different pollution gases, uSieverts — have a Geiger counter feeding data :-) ) So I’m extending already, but trying to understand existing fields expected purpose. Most skins, etc. have very useful behavior already, so trying to leverage as much as possible. Aside from battery slots ( won’t ever use those, have everything on live power) I’m slowly trying to see what I can fill in. That’s been part of the fun. Earl -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/A39AB5D9-146C-4E44-8F99-97F72976B5CE%40baugh.org.
