wview_extended schema variable choice for temperature inside enclosure

81 views
Skip to first unread message

William Garber

unread,
Nov 1, 2022, 9:53:45 PM11/1/22
to weewx-user
It was recommended somewhere to stick with the wview_extended schema.  I used extraTemp1 ... extraTemp7 and extraHumi1 ... extraHumi7 for the conditions inside my 3 enclosures to check for overheating for example on extremely hot days; it seems that the barometer is wrong by a little now; I suspect that the temperatures inside the enclosures are being used for part of the calculation of the barometer as well as the pressure; it should only depend on the outside temperature I think !!!! 

I could always just modify the schema; I know how to do that; but could someone either explain why the wview_extended schema  is so special or point me to the right way to do this please?

William Garber

unread,
Nov 1, 2022, 9:55:20 PM11/1/22
to weewx-user
the weather station is custom built from arduinos; I wrote a driver;

vince

unread,
Nov 1, 2022, 11:29:08 PM11/1/22
to weewx-user
On Tuesday, November 1, 2022 at 6:53:45 PM UTC-7 william...@att.net wrote:
 explain why the wview_extended schema  is so special

Because for the vast majority of people there are enough fields of the usual types that most people don't need to modify the schema at all.

The extended schema has extraTemp1-8 and extraHumid1-8 already there, if that's what you're looking for.  You didn't really ask a particularly clear question about what 'this' you are asking for the right way to do...

Shorter answer - a clean v4 weewx uses the extended schema by default, as an added plus.

gjr80

unread,
Nov 2, 2022, 6:14:43 AM11/2/22
to weewx-user
Further to what Vince said there is nothing special about the view_extended schema; it merely has many more fields than the legacy wview schema and hence if a user adds more sensors or stations it is a simple matter to save the data from these sensors to the database. For this reason it is now the default schema for new installs, but there is absolutely no issue with continuing to use the legacy wview schema. As an aside, WeeWX only uses the schema definition when creating the database, once the database has been created WeeWX obtains the schema direct from the database when required.

In terms of pressures, WeeWX uses three pressure fields; pressure, altimeter and barometer. WeeWX is able to calculate any of these three pressure fields provided at least one of the three pressures is available (along with the other pre-requisites). By default, if all three pressures exist then WeeWX will calculate none of them as is the case if none of the three pressures exist. Again by default, if one or two pressures are absent WeeWX will calculate the missing pressures from the available pressure field(s) and one or more of the fields outTemp and outHumidity and the station altitude setting. So if you are storing your enclosure data in fields other than outTemp and outHumidity they will not be used in the calculation of barometer unless you have made modification to the WeeWX code. Is it possible your station is providing one of the three pressures, eg station pressure (aka pressure), but it is being fed to WeeWX and saved as barometric pressure (barometer). This would certainly cause WeeWX to miscalculate altimeter and pressure (and of course barometer would be incorrect as well). If you haven't read it already, you might find the What is the difference between barometer, pressure, and altimeter? wiki page useful in explaining what pressure is stored in each of the three fields.

Gary
Reply all
Reply to author
Forward
0 new messages