gjr80 <[email protected]> writes:

> The impetus that caused LOOP2 support to be added to WeeWX was due in part 
> to being able to access THSW. For the average user THSW is probably the 
> only real point of difference driving the use of LOOP2.

It would be nice if when one specified loop_request=3 to alternate, then
the software calculation for Observation A would be disabled on loop
packets without A, if a packet with A has been seen recently.  That sort
of automates how you have to "prefer hardware".

My other question is if these are in archive records, but I can go look
that up and read the code and/or logs...

-- 
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/rmizh3urrbk.fsf%40s1.lexort.com.

Attachment: signature.asc
Description: PGP signature

Reply via email to