Hi,
The short answer is that radiation (aka solar insulation) or an equivalent
is not available via the GW1000 API so the GW1000 driver does not emit it.
The reason you see it on Ecowitt pages and WU is that the GW1000 takes what
the GW1000 API refers to as 'light' in lux and approximates solar
insolation by dividing by 126.7. The GW1000 then uploads this derived value
to Ecowitt and WU (and to anywhere else the GW1000 is configured to
upload). A similar result can be achieved with WeeWX by having the WeeWX
StdCalculate service calculate WeeWX field radiation. This is done by
adding an entry for radiation under [StdCalculate] [[Corrections]] in
weewx.conf:
[StdCalibrate]
....
[[Corrections]]
....
radiation = luminosity/126.7 if luminosity is not None else None
The reason the interceptor driver picked up radiation is that the
interceptor driver intercepts the the same data the GW1000 uploads to
Ecowitt or WU, so the interceptor driver sees the radiation field that was
calculated by the GW1000. WeeWX drivers do not calculate/derive
observations; rather they decode/unit translate data provided buy the
station/sensors only. Calculation of derived observations is taken care of
by other WeeWX services, typically the StdCalculate service.
I can't speak for what Cumulus does but I know Cumulus obtains the exact
same data from the API that the GW1000 driver does. Cumulus must be set to
automatically derive solar insolation from luminosity.
As further background, the GW1000 API emits three 'radiation' related
observations; what the API refers to as 'light' in lux, 'UV' in
microwatts/square metre and 'UVI' an index from 0-15. Of these observations
'light' corresponds to the WeeWX extended schema field luminosity and 'UVI'
corresponds to WeeWX field UV. Consequently, (and by default) these
observations are mapped to the equivalent WeeWX field. There is no
equivalent to the GW1000 API field 'UV' so the GW1000 driver passes this
field through as uvradiation (uvradiation was chosen to distinguish it from
WeeWX field UV). Note that uvradiation is not equivalent to WeeWX field
radiation.
I am in the process of producing a wiki page for the driver repo to explain
this.
Gary
On Thursday, 17 December 2020 at 09:41:03 UTC+10 [email protected]
wrote:
> I was running Weewx with the GW1000 interceptor and everything ran
> smoothly. After downloading and installing the GW1000 API driver v.
> 0.1.012b and meticulously following the readme instructions, I got the
> system running - with ONE issue - the solar radiation data had disappeared
> and would no longer be displayed.
>
> (they are there and sent to Ecowitt.net, WU etc. and are captured by
> CumulusMX and Meteobridge => it's not a GW1000 console issue, it's
> obviously a weewx (configuration ?) issue. I have 4 GW1000 type consoles
> and switched between them to make sure it's not due to the console [with
> weewxd].
>
> Since midnight the solar radiation picture/graph has completely
> disappeared.
> So I'm wondering what went wrong here ...
> Anyone can advise ?
> attached the syslog of the driver switch time window and some debug=1
> output at the end, the weewx.conf, a screencopy of the missing or mutilated
> graph and the output of weexd as screencopy and text.
>
--
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/d085a7f5-f83a-445b-82dc-6cd826f25456n%40googlegroups.com.
