Not to nitpick... well, maybe I am nitpicking ... but I'd rather see the
loop and archive options listed separately, for several reasons.
1. It matches the model we use for other uploaders, in particular, the WU
uploader (options 'rapidfire' and 'archive_post').
2. In theory, it allows other options to be specified along with the
binding method.
3. It's hard to imagine right now, but it allows a more open-ended set of
selections besides 'loop' and 'archive'.
Something like
[MQTT]
loop_binding = true
archive_binding = true
or even
[MQTT]
[[loop_binding]]
enable = true
aggregation = individual
[[archive_binding]]
enable = false
aggregation = aggregate
-tk
On Wed, Mar 28, 2018 at 9:12 AM, mwall <[email protected]> wrote:
>
>
> On Wednesday, March 28, 2018 at 11:51:58 AM UTC-4, Pat wrote:
>>
>> Using loop is working as mentioned, but I'm missing the archive packet
>> (which contains dewpoint, humidex, windrun, etc.).
>>
>> Is it possible to have the binding for both loop and archive?
>>
>>>
>>>
> pat,
>
> please try the attached mqtt-0.18rc1.py
>
> it defaults to archive, but you can specify either archive, loop, or both.
> for example:
>
> [MQTT]
> binding = archive, loop
> aggregation = individual, aggregate
>
> use the aggregation parameter to control how observations are grouped.
> possible values are 'individual' or 'aggregate'
>
> apologies in advance - i have not tested 0.18 yet, so thanks for doing the
> testing!
>
> m
>
> --
> 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 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.
