I think I mentioned the WN34 sensor mapping to extraTemp9-16 earlier ...
and
I would not map extraTemp9 to extraTemp1, because then you risk to mess
up your database in case you start adding WH31 sensors 1-8 later which is
something many Ecowitt users do.
there is a imho better way for mapping using the wxview-extended
database schema: using the 4 unused soilTemp database fields
so I would add in weewx.conf in the stanza
[StdCalibrate]
[[Corrections]]
soilTemp1 = extraTemp9
and add soilTemp1 to the [DisplayOptions] stanza in the Sesons skin
skin.conf
that would then make weewx save/archive the WN34 Ch1 sensor values to
soilTemp1 and keept the extraTemp1-8 free for the WH31 sensors.
That works perfectly for me
soilTemp in the Ecowitt ecosystem are sensors (8 though) which are
related to the WN34 soil temperature or WN34 liquid (e.g. water)
temperature.
The WN34 sensors don't provide humidity values whereas the WH31 sensors
(extraTemp1-8) do. Once more reason to better use soilTemp1-4 for the
first four WN34 sensors.
On 25.02.2023 03:33, gjr80 wrote:
Just to be clear about relbarometer. Ecowitt gateway devices provide
two pressure values, the first is what Ecowitt refers to as /absolute
barometer/ which is what we know as gauge or station pressure (what
the driver refers to as absbarometer and what WeeWX knows as the WeeWX
field pressure), the second is what Ecowitt refers to as /relative
barometer/. /relative barometer/ (what the driver knows as
relbarometer) is an approximation to barometric pressure (what WeeWX
knows as WeeWX field barometer) as it does not correct for
temperature. The default mapping used by the Ecowitt gateway driver is
to map the device absbarometer field to the WeeWX field pressure, the
device field relbarometer is not mapped to WeeWX field barometer,
rather it is mapped (or passed through) as relbarometer (this way
WeeWX calculates barometer using a more sophisticated formula that
does compensate for temperature and altitude and at the same time
gives the user access to the Ecowitt approximated /relative barometer/
field). The price you pay for this is that WeeWX needs 12 hours of
pressure data before it can calculate barometer. Since barometric
pressure is what most weather reports use and also what most folks
display on web pages, you probably don't want to display pressure or
relbarometer, just be patient and barometer will appear once you have
12 hours of pressure data.
You may find the WeeWX wiki page What is the difference between
barometer, pressure and altimeter ?
<https://github.com/weewx/weewx/wiki/Barometer,-pressure,-and-altimeter>
provides useful background.
By all means adjust the Ecowitt relative barometer value to suit,
though for all intents and purposes this value is only used by
Ecowitt, it is not used by WeeWX.
In terms of extraTemp9, Vince is correct in that this is your first
WN34x sensor temperature data. This is indeed by design. The Ecowitt
gateway devices support many different sensor types and then on top of
this multiple sensors (or channels) of most types. The driver could
certainly attempt to automatically map these sensors/channels to the
fields in the WeeWX schema, but this would have lead to some quite
complex code as well as causing a support nightmare. Instead I decided
to default map sensors to a fixed WeeWX field (eg the first WN34
channel is always mapped to extraTemp9) and give the user the ability
to alter this default mapping by defining a new field map or
extending/altering the existing field map. In the OPs case WeeWX is
most likely using the wview_extended schema which only includes
extraTemp1 to extraTemp8. You essentially have two options; either
change the default mapping to map the WN34 data to some other WeeWX
field in the wview_extended schema (using a [[field_map_extensions]]
entry) or adding the extraTemp9 field to the database. In either case
you may or may not need to make changes to the [DisplayOptions] stanza
in the Seasons skin config file (skin.conf). Just remember, for WeeWX
to save data to database two basic conditions must be met; first the
data must exist in a field in WeeWX generated archive records and
second the same field name must exist in the in-use database schema.
A similar situation exists with sensor battery and signal state data
as does with extraTemp9, though is the case of sensor battery stay and
signal data the field names used in the default field map are more
self evident due to the use of sensor model and channel number in the
field name in most cases.
The Ecowitt gateway driver wiki is far from complete, but if your
system includes more than just the gateway device and an x-in-1 sensor
suite I would suggest you become very familiar with the default field
map used by the driver. This is covered on the Field map page
<https://github.com/gjr80/weewx-gw1000/wiki/Field-map> in the driver wiki.
Gary
--
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/651965b7-f7f2-43eb-8ea6-803deb8c2c51n%40googlegroups.com
<https://groups.google.com/d/msgid/weewx-user/651965b7-f7f2-43eb-8ea6-803deb8c2c51n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
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/0ecea220-c03a-46d6-84bf-022f8e5473a3%40gmail.com.
