GW1000 driver b12 release

127 views
Skip to first unread message

gjr80

unread,
Aug 30, 2020, 10:27:19 PM8/30/20
to weewx-user
I have released v0.1.0b12 on GitHub. In this release I have focussed on improving the handling and logging of lost GW1000 contact. The changes include:

- 'debug_rain' now accepts True/False values rather than 0/1/2/3
- when run as a service the GW1000 'datetime' field is mapped to the WeeWX 'dateTime' field when producing the GW1000 mapped packet. If the GW1000 'datetime' field does not exist a timestamp is assigned by the system. This effectively means when operated as a service there is a permanent mapping from 'datetime' to 'dateTime'. this means that when operated as a service and a custom field map is defined there is no need to include a 'datetime' to 'dateTime' field map entry.
- the default poll interval is now 20 seconds, this means that all default installs will see at least two GW1000 polls per archive interval
- the handling of loss of GW1000 contact has been refactored. Lost contact handling is now common across when operated as a driver or as a service
- to prevent log flooding when operated as a service lost contact logging is now controlled by the `lost_contact_log_period` config option. The default value is 21600 seconds or six hours. This applies when operating as a service only, when operated as a driver 'lost_contact_log_period' is ignored and all lost contact is logged.

The changes to lost contact handling and logging are complex and extensive. I have spent quite a bit of time testing and debugging the new driver both as a service and as a driver under both Python2 and 3. I am sure there will be some corner cases I have missed, so if you do notice something odd/not right please let me know.

Gary

Graham Eddy

unread,
Aug 31, 2020, 10:01:18 AM8/31/20
to weewx...@googlegroups.com
oops, poll_interval default not changed in b12:
self.poll_interval = int(gw1000_config.get('poll_interval', 60))
but otherwise b12 is chugging along happily thus far (haven’t tried pulling the plug on it yet - making sure it runs normally first)

gjr80

unread,
Aug 31, 2020, 7:30:44 PM8/31/20
to weewx-user
On Tuesday, 1 September 2020 at 00:01:18 UTC+10 graha...@gmail.com wrote:
oops, poll_interval default not changed in b12:
self.poll_interval = int(gw1000_config.get('poll_interval', 60))

Yes, in my haste it seems that only folks that install via wee_extension will get 20 seconds as the default. To be fixed in b13.

Gary 

Graham Eddy

unread,
Aug 31, 2020, 11:57:26 PM8/31/20
to weewx...@googlegroups.com
in case it is important, i should mention that i used wee_extension

--
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/4e78099e-efa2-4533-bfa4-b7d6be1a59bfn%40googlegroups.com.

gjr80

unread,
Sep 1, 2020, 12:48:51 AM9/1/20
to weewx-user
Not having a good day, I should have said those who use wee_config to reconfigure the driver as part of installation (by any method) will get the default 20 second polling interval, anyone else will get the default 60 seconds. wee_extension will not alter an existing config setting in weewx.conf, so if a poll_interval has been explicitly set in [GW1000] then installing (or upgrading by installing a later release) will leave poll_extension unchanged.

Gary
Reply all
Reply to author
Forward
0 new messages