Thanks Tom. I did end up using leafWet2, and there are minor issues with
ints verses floats in what weewx
gets sent, but it all seems good at this point. Nope this was my fault
too... :^)
File "/home/weewx/bin/user/aclogger.py", line 405, in decode_data
pkt[pairs[0]] = int(pairs[1]) # make
count of cycles (leafWet2)
ValueError: invalid literal for int() with base 10: '1.000000'
To keep the charts alike, I also re-scaled the original two pumps to also
return counts
instead of (0.1 * count) and stop treating those as rates (using hailRate,
rainRate).
Thx, Chris
On Mon, Nov 13, 2017 at 6:57 AM, Thomas Keffer <[email protected]> wrote:
> Hi, Chris
>
> You're on the right track. Generally, the database should store the number
> of counts in the archive interval. So, each loop packet should contain the
> number of counts since the last loop packet --- generally a small number.
>
> To plot, aggregate over a time period, using aggregation type 'sum', so
> you're plotting, say, the number of counts per hour.
>
> This is much like the way rain is treated, except it's unit-less.
>
> As for which observation type to use, you can use any of the free types.
> The unit group is just used to pick appropriate unit labels in the plots
> and templates. But, you can always override that either in skin.conf, or in
> the template.
>
> Hope this helps.
>
> -tk
>
> -tk
>
> On Sat, Nov 11, 2017 at 4:05 PM, <[email protected]> wrote:
>
>> Hi All,
>>
>> I'm back working on my crawl space 'weather' system, and trying to
>> figure out how to map another
>> value. It's a sump pump activation count, so it doesn't have an analog
>> value like much of the items
>> that weewx normally deals with. This is a third pump, and the first two
>> got mapped to rainRate and
>> hailRate, but there aren't any more rate type values to hijack. Those
>> aren't count types, but I did find
>> these in bin/weewx/units.py:
>> "leafWet1" : "group_count",
>> "leafWet2" : "group_count",
>>
>> Not suite sure how these are used in terms of values expected in the loop
>> data. I also pulled
>> down the lightening detector driver (weewx-as3935-0.6.tgz), and that also
>> counts, but for me,
>> I'm adding something to an existing setup, so that's not quite right
>> either.
>>
>> I'm looking for suggestions on how to map event data (once/day, one/week,
>> not sure) into
>> something weewx can plot. I'm trying to avoid DB schema changes some my
>> grasp on those
>> sorts of things is pretty weak, but I'm game if that's the way to go.
>>
>> Thx, Chris
>>
>> --
>> 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].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/weewx-user/Ybufg96m950/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
--
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].
For more options, visit https://groups.google.com/d/optout.
