GW1000 driver not reading data from a GW1100/GW2000 console/hub with an Ecowitt WS90 connected

[Rainer Lang]

Hi Gary,

I have weewx 4.5.1 with a GW1000 driver 0.4.2 connected to a GW2000 with a WS90 and a WH40 rain gauge attached.
The GW2000 and the GW1100 consoles support since firmware 2.1.2 two rain gauges being connected in parallel and they show the data of both rain gauges (if both connected to the console) synoptically in the WS View Plus app or in their WebUI (and on the ecowitt.net dashboard).
When both rain sensors, the traditional WH40 and the haptic ("piezo") WS90, are connected weewx via the GW1000 driver only picks up the WH40 data.
If only the WS90 is connected, weewx doesn't pick up anything for rain.
See below the output from the GW1000 driver - no rain contained.
It looks as if the new WS90 array with its haptic/piezo rain gauge hasn't been considered yet in the GW1000 driver 0.4.2 coding.
The WS90 data is obviously received from the GW1000 API as the WS View Plus app receives it using the same API.

When can the WS90 rain data or maybe even both raingauges connected to a GW1100 or GW2000 be received and processed by weewx via an ipdated GW1000 driver ?

By the way, the custom server http post from the consoles contains five extra variables for the WS90 rain data, like erain_piezo, hrain_piezo, drain_piezo, mrain_piezo and yrain_piezo (for event, hour, day, month, year) in addition to the classic eventrainin, hourlyrainin, dailyrainin, monthlyrainin and yearlyrainin variables (or observations if you prefer that term) when both rain gauges are connected and the piezo only if only a WS90 is connected.

cheers
Rainer

2022-04-04 22:57:44 CEST (1649105864): UV: 0, co2: 735, co2_24h_avg: 807, dateTime: 1649105864, daymaxwind: 13.7,
extraHumid1: 67, extraHumid17: 41, extraHumid2: 64, extraHumid3: 67, extraHumid4: 70, extraHumid6: 47, extraHumid7: 66, extraTemp1: 5.6,
extraTemp17: 20.1, extraTemp2: 6.4, extraTemp3: 5.7, extraTemp4: 5.7, extraTemp5: -12.9, extraTemp6: 6.3, extraTemp7: 4.7,
inHumidity: 42, inTemp: 19.0, leak2: 0, lightning_distance: 17, lightning_last_det_time: 1645806203,
lightning_strike_count: None, lightningcount: 0, luminosity: 0.0, outHumidity: 65, outTemp: 5.7,
pm10: 27.6, pm10_24h_avg: 20.1, pm2_5: 28.0, pm2_51_24h_avg: 23.3, pm2_52: 15.0, pm2_52_24h_avg: 20.5, pm2_55: 27.0, pm2_55_24h_avg: 19.6,
pressure: 983.1, relbarometer: 1012.2, soilMoist1: 7, soilMoist2: 16, soilMoist3: 27, soilMoist4: 19, usUnits: 17, uvradiation: 0.0,
wh31_ch1_batt: 0, wh31_ch1_sig: 4, wh31_ch2_batt: 0, wh31_ch2_sig: 4, wh31_ch3_batt: 0, wh31_ch3_sig: 4,
wh31_ch4_batt: 0, wh31_ch4_sig: 4, wh31_ch5_batt: 0, wh31_ch5_sig: 4, wh31_ch6_batt: 0, wh31_ch6_sig: 4, wh31_ch7_batt: 0, wh31_ch7_sig: 4, wh41_ch1_batt: 3, wh41_ch1_sig: 4, wh41_ch2_batt: 5, wh41_ch2_sig: 4, wh45_batt: 6, wh45_sig: 4,
wh51_ch1_batt: 1, wh51_ch1_sig: 4, wh51_ch2_batt: 0, wh51_ch2_sig: 4, wh51_ch3_batt: 0, wh51_ch3_sig: 4, wh51_ch4_batt: 0, wh51_ch4_sig: 4, wh51_ch5_batt: None, wh51_ch5_sig: 0, wh55_ch2_batt: 4, wh55_ch2_sig: 4, wh57_batt: 3, wh57_sig: 4,
windDir: 353, windGust: 2.8, windSpeed: 1.9

2022-04-04 22:57:54 CEST (1649105874): UV: 0, co2: 735, co2_24h_avg: 807, dateTime: 1649105874, daymaxwind: 13.7,
extraHumid1: 67, extraHumid17: 41, extraHumid2: 64, extraHumid3: 67, extraHumid4: 70, extraHumid6: 47, extraHumid7: 66, extraTemp1: 5.6,
extraTemp17: 20.1, extraTemp2: 6.4, extraTemp3: 5.7, extraTemp4: 5.7, extraTemp5: -12.9, extraTemp6: 6.3, extraTemp7: 4.7,
inHumidity: 42, inTemp: 19.0, leak2: 0, lightning_distance: 17, lightning_last_det_time: 1645806203,
lightning_strike_count: 0, lightningcount: 0, luminosity: 0.0, outHumidity: 65, outTemp: 5.7,
pm10: 27.6, pm10_24h_avg: 20.1, pm2_5: 28.0, pm2_51_24h_avg: 23.3, pm2_52: 15.0, pm2_52_24h_avg: 20.5, pm2_55: 27.0, pm2_55_24h_avg: 19.6,
pressure: 983.1, relbarometer: 1012.2, soilMoist1: 7, soilMoist2: 16, soilMoist3: 27, soilMoist4: 19, usUnits: 17, uvradiation: 0.0,
wh31_ch1_batt: 0, wh31_ch1_sig: 4, wh31_ch2_batt: 0, wh31_ch2_sig: 4, wh31_ch3_batt: 0, wh31_ch3_sig: 4,
wh31_ch4_batt: 0, wh31_ch4_sig: 4, wh31_ch5_batt: 0, wh31_ch5_sig: 4, wh31_ch6_batt: 0, wh31_ch6_sig: 4, wh31_ch7_batt: 0, wh31_ch7_sig: 4, wh41_ch1_batt: 3, wh41_ch1_sig: 4, wh41_ch2_batt: 5, wh41_ch2_sig: 4, wh45_batt: 6, wh45_sig: 4,
wh51_ch1_batt: 1, wh51_ch1_sig: 4, wh51_ch2_batt: 0, wh51_ch2_sig: 4, wh51_ch3_batt: 0, wh51_ch3_sig: 4, wh51_ch4_batt: 0, wh51_ch4_sig: 4, wh51_ch5_batt: None, wh51_ch5_sig: 0, wh55_ch2_batt: 4, wh55_ch2_sig: 4, wh57_batt: 3, wh57_sig: 4,
windDir: 338, windGust: 2.8, windSpeed: 1.9

[gjr80]

Rainer,

Yes I have been following the wxforum posts re the GW2000 and rain gauges. The current driver release (v0.4.2) does not support any WS90 specific rain fields, in fact the current Ecowitt API release, v1.6.3, whilst containing reference to the WS90 (also referred to as the WH90) provides no detail what WS90 rain data is provided in what bytes of the relevant API response(s). I don't expect this will be too much of a hindrance though provided Ecowitt sticks to the same data formats as used for previous rain gauges. As an aside WS90 battery state data is documented in the API so it should be easy to implement. However, there is nothing in the API control/config functions to indicate any support for the WS90 config/calibration so those aspects of the driver, although seldom used, may take longer or more effort to implement. I appreciate the additional WS90 data available via the various Ecowitt apps and the additional fields in the Ecowitt format messages; however, that only tells us the data is available not how to access it via the API.

My Wittboy is in transit, I expect things to clear up once it arrives and I have a chance to get it online with the driver.

Gary