Author Topic: a list of possible WeeWx field names  (Read 657 times)

0 Members and 1 Guest are viewing this topic.

Offline speerwerfer

  • Member
  • *
  • Posts: 7
a list of possible WeeWx field names
« on: September 04, 2021, 01:57:48 AM »
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

Offline vreihen

  • El Nio chaser
  • Forecaster
  • *****
  • Posts: 1181
  • K2BIG
Re: a list of possible WeeWx field names
« Reply #1 on: September 04, 2021, 09:57:35 AM »
WU Gold Stars for everyone! :lol:

Offline Gyvate

  • Forecaster
  • *****
  • Posts: 1550
Re: a list of possible WeeWx field names
« Reply #2 on: September 08, 2021, 03:18:18 AM »
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)
Froggit WH4000SE (=EW 2320E) 1.6.4/GW1100 2.1.4/Froggit DP1500 1.6.8 (+EW GW1000 (4) 1.6.8/7.2 test/backup)/HP1000SE Pro (HP2551) 1.6.4/1.7.8, WH2650 WiFi (2) 1.7.2,GW2000 2.1.4;
Ecowitt WS90-,WS80,WH40,WH65,WH31(5),WH31-EP(1),WN30/DP30 (1),WH32(1),WH32-EP(1),WH32B [T/H/P] (1), WH57 [Lightning] (1), WH41 [PM2.5] (2), WH51 [SoilMoisture] (5), WH45, WH55 (2)
MeteobridgePro(2)[test,prod 5.4 May 07 2022, 14745 - Blake-Larsen Sun Recorder - RPi4/weewx 4.8.0/CumulusMX 3184/MB RPi4(2671)
Barani Meteoshield Pro, MetSpec Rad02
Ecowitt 5763,34418;WU ISAARB3(WH4000SE), ISAARB22(HP2553), http://meshka.eu

Offline speerwerfer

  • Member
  • *
  • Posts: 7
Re: a list of possible WeeWx field names
« Reply #3 on: September 09, 2021, 02:43:35 PM »
Sorry for the late feedback!

Quote
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
Quote
- fields weewx saves (archives) data in its archiving cycle
I call these fields database fields
Quote
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
« Last Edit: September 09, 2021, 02:46:01 PM by speerwerfer »

 

anything