I have released v0.1.0b12 on GitHub 
<https://github.com/gjr80/weewx-gw1000/releases/tag/v0.1.0b12>. 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

-- 
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/842fc068-0d19-4204-a582-ccc0dd890d13n%40googlegroups.com.

Reply via email to