The same general approach can be applied to any driver; (1) configure the
driver to provide whatever observations you require (in the case of SDR
this involves setting up the sensor map, likewise for the interceptor
driver, other drivers you may need to do nothing) (2) if WeeWX cannot
Thanks a lot Gary, this was somehow better to understand for me than in the
Customization Guide.
And it works, now the zeros behind the dot are gone. My SDR setup is
displaying both lx and w/m2 fine now. This was rather easy to do with just
adding it a second time to the sensor map and adding
Before I answer a quick WeeWX units 101. The WeeWX unit system is the core
that allows WeeWX to convert between units (eg C to F), format observation
data in reports and add unit labels. The system is predicated on each
observation being allocated to a unit group (eg outTemp, inTemp, dewpoint
It was the skin.conf, now they appear, thanks!
Is there a way to add "lux" to the lux reading in the graph and current
conditions list? Could i just add it in weewx.conf?
In the current conditions list, the lux number reads like this "70070.00".
Can i add something like lux = %.1f to
The only real definitive way of determining what schema you are using is to
access the database and check what fields are there. If you have only ever
installed v 4.0.0 or later and did not explicitly change the schema you are
almost certainly using the extended schema. If you have upgraded a
I'm currently only using the standard Seasons skin. How do i find out which
schema weewx uses? I never really changed this setting so what would be the
standard weewx installation schema? I thought it was the extended one but
as it seems i'm not getting any luminosity plots in the Seasons skin,
The short answer is yes, it is possible. However, what you need to do
depends. I assume you are using the SDR driver, if that is the case it
should be providing you with the 'light' reading in Lux mapped to whatever
WeeWX field you have specified in the sensor map (the usual mapping would
be
