Thank you from me aswell. I received my PWS yesterday, used the GW1000 driver and was about to ask the same question, then I found this.
I have one more question about pressure mapping. I noticed the driver maps "absbarometer" to "pressure" but the "relbarometer" to "relbarometer" aswell, which as far as I know is not used by default in Weewx. In the WeeWX wiki I found that it uses "pressure", "altimeter", and "barometer". Did you make these mappings so that you let the WeeWX recalculate the other parameters automatically from the "absbarometer"? This gives a different result then I have in WS View app (I guess the app only uses offset based on altitude, but weewx actually uses humidity and temperature aswell), now the problem is that the sea-level pressure is reported higher then other stations around me (including METAR), to correct this should I offset the absolute pressure in the WS View app? Or maybe used the corrections in weewx? I have problem with sending data PWSWeather, not sure what parameter for pressure it sends, but when I open the station on their website, open Observations, there is no reported pressure, then in the dashboard I see some pressure, but it is even higher than the one reported by WeeWX. Thank you On Thursday, December 17, 2020 at 11:31:35 AM UTC+1 [email protected] wrote: > Thanks, Gary > that was enlightening 😎 - and apart from planning to explain the details > more in the wiki (which is highly appreciated), > I suggest to include the above entries to the [[Corrections]] stanza also > in the readme file that comes with GW1000 API driver > and also include them - unless already done (I cannot tell as I did the > migration to the API driver manually) - in the install process which > updates the weewx.conf file. > Great to have knowledgeable people to explain and help ! > > On Thu, Dec 17, 2020 at 8:34 AM gjr80 <[email protected]> wrote: > >> 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 >> >> <https://groups.google.com/d/msgid/weewx-user/d085a7f5-f83a-445b-82dc-6cd826f25456n%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/42b9d5e0-0f57-4685-aece-440ecf183ec4n%40googlegroups.com.
