Topic: a list of possible WeeWx field names

[speerwerfer]

Hello,

I would like to use the WeeWX-MQTTSubscribe service (https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/). In the configuration I have to specify which value I want to use in WeeWx and where I want to save it. I have to map the MQTT field name into the WeeWx name. Where can I find a list of possible WeeWx field names?

Martin

[vreihen]

Does this help?????

http://www.weewx.com/docs/customizing.htm#archive_database

[Gyvate]

There are two types of fields if you may say so:
- fields available to weewx (they depend on the driver you are using, e.g. GW1000 API driver)
- fields weewx saves (archives) data in its archiving cycle
(they are defined in the database schema - usually the extended wview schema - /usr/share/weewx/schemas/wview_extended.py)
Usually the driver assigns values it collects to the corresponding database field.
If this is not so, for whatever reason, you have several options to get the wanted data archived
- re-purpose an existing but unused database field (by preference with the same units) and assign your observation to the chosen database field in the [StdCalibrate] [[Corrections]] section/stanza
e.g.
extraTemp8 = extraTemp17 
or
no2 = pm2_55
  - if you can't find a field of the same units, you will have to assign the field to the unit group in extensions.py (/usr/share/weewx/user/extensions.py).

- add a new database field to your schema (see weewx customization guide)

The paths mentioned may be different in your installation (the ones shown here refer to a Debian [RPi] installation; for other installation types with e.g. setup.py, see weewx user guide)

[speerwerfer]

Sorry for the late feedback!

There are two types of fields if you may say so:
- fields available to weewx (they depend on the driver you are using, e.g. GW1000 API driver)

I call these fields input fields

- fields weewx saves (archives) data in its archiving cycle

I call these fields database fields

Usually the driver assigns values it collects to the corresponding database field.

That is what I have to do in the weewx.conf for the MQTTSubscribe extension. I assumed there was a list of "database fields" in the documentation. Now I know it's the database schema.
Is it theoretically possible that there are input fields that are not mapped to database fields but are still used in an html template? How are such Input fields of a driver made available to WeeWx and the templates?
With MQTTSubscribe, I can only assign these input fields to the database fields directly in the configuration. Without this assignment to database fields, the input fields are not available in weewex, right?

Martin