GW1000 driver v0.2.0 release

[gjr80]

I have released v0.2.0 on GitHub.

This main feature of this release is support for the WH45 Indoor CO2 PM2.5 PM10 Temperature and Humidity 5-in-1 Air Quality Sensor. If you have a WH45 sensor and it has been linked to your GW1000 v0.2.0 of the driver should automatically pick up and emit the WH45 sensor data.

v0.2.0 also sees changes in the naming of the 24 hour average particulate concentration fields. Unfortunately this will mean anyone that is using these fields will need to make one or more changes to their WeeWX installation. I have outlined the changes and which users need to make changes and how to make the necessary changes in a wiki article Changes to 24 hour average particulate concentration field names. If you have a WH41, WH43 or WH45 sensor and use the 24 hour average particulate concentration fields in any way I strongly suggest you thoroughly read the linked wiki article.

The majority of the other changes in v0.2.0 relate to running the driver directly, in particular displaying the GW1000 and sensor configuration information currently only available through the WS View app.

Those that installed v0.1.0 via wee_extension can upgrade to v0.2.0 as follows:

$ wget -P /var/tmp https://github.com/gjr80/weewx-gw1000/releases/download/v0.2.0/gw1000-0.2.0.tar.gz

$ wee_extension --install=/var/tmp/gw1000-0.2.0.tar.gz

Note: wee_extension may require the use of sudo the path to wee_extension as applicable.

Gary

[vince]

Works great here, thanks.   Also liked the wiki pages.

I noted the new (?) _sig values in --live-data

Mine all show a value of 4

I'm assuming the values are 0-4 where 4 is best (???)

What else is now available that was previously only in the WS View app ?

unrelated - I have a minimalist skin for EcoWitt at https://github.com/vinceskahan/weewx-ecowitt-skin if anybody is interested...

[gjr80]

On Sunday, 10 January 2021 at 05:44:27 UTC+10 vince wrote:

Works great here, thanks.   Also liked the wiki pages.

I noted the new (?) _sig values in --live-data

Whoops, included in the release notes but forgot to mention that one here.

Mine all show a value of 4

I'm assuming the values are 0-4 where 4 is best (???)

The Sensor battery states wiki page provides details on sensor battery states reported by the driver; basically the meaning depends on the sensor concerned.

What else is now available that was previously only in the WS View app ?

Essentially the supported weather service settings and sensor calibration settings, specifically PM2.5 sensor offset settings, multi-channel TH sensor calibration settings, soil moisture sensor calibration settings and sensor calibration settings. I think most if not all of the things you see under ‘More’ menu in the top right corner of app when looking at a GW1000 can now be displayed. And due to the nature of the API and the link to the GW1000 these can all be accessed by running the driver directly while WeeWX and the driver are also running.

Gary

[Rainer Lang]

Hi Vince,

as far as I can tell there is no gap between WSView app (FW 1.6.3) and the data provided by the new driver.

I already had a pre-release version installed as my weewx installation crashed with my new WH45 sensors.
(That's the last line in the wiki update by Gary - the program shouldn't crash when meeting a sensor it doesn't know).

And the pre-release worked fine. Haven't tried the final release yet.

--
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/12972026-34e3-4f8f-ab50-e9309c706fa7n%40googlegroups.com.

[vince]

On Saturday, January 9, 2021 at 12:20:38 PM UTC-8 gjr80 wrote:

On Sunday, 10 January 2021 at 05:44:27 UTC+10 vince wrote:

Works great here, thanks.   Also liked the wiki pages.

I noted the new (?) _sig values in --live-data

Mine all show a value of 4

I'm assuming the values are 0-4 where 4 is best (???)

The Sensor battery states wiki page provides details on sensor battery states reported by the driver; basically the meaning depends on the sensor concerned.

Yes, saw that...but I was asking about the sig(nal?) status fields in the new version.

And are the calibration things available in the --live-data information ?

I have my sensors slightly calibrated, but don't see any of that info in the --live-data output.

GW1000 live sensor data: absbarometer: 1014.3, datetime: 1610218338, humid1: 38, humid2: 41, inhumid: 39, intemp: 21.1, outhumid: 98, outtemp: 1.4, relbarometer: 1025.8, soilmoist1: 38, temp1: 20.7, temp2: 19.7, wh26_batt: 0, wh26_sig: 4, wh31_ch1_batt: 0, wh31_ch1_sig: 4, wh31_ch2_batt: 0, wh31_ch2_sig: 4, wh51_ch1_batt: 0, wh51_ch1_sig: 4

I guess I'm struggling a little with how to display all the new cool stuff and what the units are, especially since the API isn't public yet it seems.

[gjr80]

On Sunday, 10 January 2021 at 07:37:10 UTC+10 vince wrote:

On Saturday, January 9, 2021 at 12:20:38 PM UTC-8 gjr80 wrote:

On Sunday, 10 January 2021 at 05:44:27 UTC+10 vince wrote:

Works great here, thanks.   Also liked the wiki pages.

I noted the new (?) _sig values in --live-data

Mine all show a value of 4

I'm assuming the values are 0-4 where 4 is best (???)

The Sensor battery states wiki page provides details on sensor battery states reported by the driver; basically the meaning depends on the sensor concerned.

Yes, saw that...but I was asking about the sig(nal?) status fields in the new version.

Yes you did, sorry too early here. The API documentation provides no real info on what signal level means, my understanding is it is not a true signal level like we normally understand signal level to be, but rather it is an indicator of whether the most recent broadcasts have been received from the sensor. But yes more is better.

And are the calibration things available in the --live-data information ?

I have my sensors slightly calibrated, but don't see any of that info in the --live-data output.

GW1000 live sensor data: absbarometer: 1014.3, datetime: 1610218338, humid1: 38, humid2: 41, inhumid: 39, intemp: 21.1, outhumid: 98, outtemp: 1.4, relbarometer: 1025.8, soilmoist1: 38, temp1: 20.7, temp2: 19.7, wh26_batt: 0, wh26_sig: 4, wh31_ch1_batt: 0, wh31_ch1_sig: 4, wh31_ch2_batt: 0, wh31_ch2_sig: 4, wh51_ch1_batt: 0, wh51_ch1_sig: 4

I guess I'm struggling a little with how to display all the new cool stuff and what the units are, especially since the API isn't public yet it seems.

Calibration data is not explicitly included in the —live-data output, though any relevant calibration data should have been applied to sensor data in the —live-data output. I have not explicitly tested that though. What units do you have a problem with?

 

Gary

[vince]

My gear is all working fine.  I probably misread your note a bit, thinking that "displaying the GW1000 and sensor configuration information currently only available through the WS View app" included seeing the calibration offsets we do in their app after finding them buried down in that brutal GUI they provide.   I did see the --sensors option which was pretty interesting though.  No problems here at all.  Works great.  Thanks.

[gjr80]

OK, maybe I am mis-reading your post and what you want/expect to 'see'. When I said "displaying the GW1000 and sensor configuration information currently only available through the WS View app" I meant everything you can access under the menu in the top right hand corner of the WS View App (believe that is the 'More' menu in both the Android and Apple apps). The --get-xxxx command line options should correspond closely to the item names under the 'More' menu and each should present the same info on screen as fund under the respective 'Menu' sub-menu. You certainly should be able to see calibration offsets but of course not in --live-data or loop packets.

The release notes from the v0.2.0 release on GitHub gives a better run down:

• added --get-services command line option to display GW1000 supported weather services settings
• added --get-pm25-offset command line option to display GW1000 PM2.5 sensor offset settings
• added --get-mulch-offset command line option to display GW1000 multi-channel TH sensor calibration settings
• added --get-soil-calibration command line option to display GW1000 soil moisture sensor calibration settings
• added --get-calibration command line option to display GW1000 sensor calibration settings
• renamed --rain-data command line option to --get-rain-data

Gary

[vince]

Perfect.  Thanks.  That's what I was looking for.

[Steven Sheeley]

The newly displayed "sig_" values, i.e "  wh??_ch?_sig ", etc, indicate signal strength between the GW1000 and the sensor in "Bars" from 1 to 4 bars of "strength" as seen on the wsview app when looking at the sensor page.

[Paul Ward]

I've just got my WH45 and its working great with new driver thanks Gary. I've noticed that the CO2 internal temp & humidity are coming through as the curiously named "extraTemp17" and "extraHumid17" does that sound right? Also FYI at some point wiki sensor map page will need updating :-)

[gjr80]

On Tuesday, 19 January 2021 at 09:42:36 UTC+10 ward...@gmail.com wrote:

I've just got my WH45 and its working great with new driver thanks Gary. I've noticed that the CO2 internal temp & humidity are coming through as the curiously named "extraTemp17" and "extraHumid17" does that sound right?

Correct, that was intentional. As you would be aware the GW1000 (and of course the API) supports up to eight WH31 TH sensors. These are referred to as temp1-8 in the API. The API also has provision for an additional eight temperature fields which are referred to in the API documentation as temp9-16 and consequently I have provided for them as temp9-16 in the GW1000 driver. The WH45 provided temperature data is referred to as 'tf_co2' in the API but to avoid confusion and keep some consistency I have allocated the WH45 temperature field as temp17. Of course all of these tempx fields map to extraTempxx in the default field map. Interestingly, the GW1000 API does not support a second block of humidity fields (humid9-16). Again for consistency I have allocated the WH45 humidity field to humid17 (extraHumid17), this may cause some confusion but I felt it better to keep aligned with the approach used with the temperature fields.

 

Also FYI at some point wiki sensor map page will need updating :-)

Thanks. Actually thought I had done that but it appears I did not. The tabulated field map on the Field map wiki page has now been updated to reflect v0.2.0 of the driver. 

Gary