Observation Type

[Wes Witt]

maybe i missed it in the docs, but i've looked and can't find it.  is there a list somewhere on all the observation types that can be used in loop packets? i'd also like to have that list include the required values such as fahrenheit or celcius, etc.

[Pat]

Anything in the database schema (or archive table columns) can be used as an observation for the loop and archive events

weewx 3 uses the wview schema

weewx 4 uses the wview extended schema (and those who may have upgraded their weewx 3 schemas to this new extended version)

[Tom Keffer]

Don't know exactly what you mean by "can be used in loop packets." If you mean whether they get emitted in a LOOP packet, it depends entirely on your hardware. The easiest way to find out what's getting emitted, is to run weewxd directly, then watch the console. It will print out all types it sees, plus any derived types (such as wind chill).

All types get "accumulated" and turned into archive records. If they appear in the database schema, they also get stored in the database. 

Don't know what you mean by "include the required values such as fahrenheit or celsius".

-tk

On Wed, Jun 3, 2020 at 9:26 AM Wes Witt <wes...@gmail.com> wrote:

maybe i missed it in the docs, but i've looked and can't find it.  is there a list somewhere on all the observation types that can be used in loop packets? i'd also like to have that list include the required values such as fahrenheit or celcius, etc.

--
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/67680f94-4899-49d9-bf0b-a23c2b593925%40googlegroups.com.

[Wes Witt]

thanks to both of you for the responses.

it seems that any of the database fields can be included in loop packets -- perfect.

@tom my weather station is a custom design so i have written my own driver that emits loop packets.  my question about expected values in the loop packets can be rephrased more specifically.  for outtemp packet values it seems that this is expected to be fahrenheit -- is this documented somewhere or can i configure this field to be fahrenheitor celcius??

[Tom Keffer]

Be sure to read the section Porting to new hardware in the Customizing Guide. It answers your question. Let me know if anything is unclear.

-tk

--

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 weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/01eda6d7-1b7b-453e-a04e-382048313a33%40googlegroups.com.

[William Burton]

Hello Wes,

It seems you're missing some basic information on writing a driver. Be sure to review the docs at http://www.weewx.com/docs/customizing.htm#porting (same link Tom just sent). Scroll down to the Implement a Driver section, then look for the Required Keys table. You need to always include the usUnits field where you specify the units for the LOOP packet. So if your hardware temperature for outTemp natively returns in celcius, then you need to set usUnit to METRIC or METRICWX depending on what other observations are also included.

Note that there's no requirement to have all observations in each LOOP packet. You can return LOOP packets based on the frequency of the observations, usUnit type or other logical grouping.

Hope this helps,

-Bill

[Wes Witt]

thanks. i'm actually doing that and everything is working well. i think i fully understand how this works now.