Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconistent handling of errors when interrogating the GW1000 #15

Open
gjr80 opened this issue Aug 29, 2020 · 0 comments
Open

Inconistent handling of errors when interrogating the GW1000 #15

gjr80 opened this issue Aug 29, 2020 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@gjr80
Copy link
Owner

gjr80 commented Aug 29, 2020

There appears to be inconsistent behaviour when errors are encountered obtaining a response/data from the GW1000. Expected behaviour will be different whether the GW1000 driver is being used as a WeeWX driver or as a WeeWX service. In simple terms when run as a driver failure to communicate with the GW1000 should result repeated attempts to connect to the GW1000 every 60 seconds. Behaviour on startup is determined by loop_on_init config setting. When operated as a service failure to communicate with the GW1000 should again result in repeated attempts to connect to the GW1000 but the failure to establish a connection with the GW1000 should not cause WeeWX to crash or interrupt WeeWX operation in some other way. In both cases recovery (if possible) should be seamless without the need for user intervention.

This weewx-user thread (driver) and this weewx-user thread (service) highlight unrecoverable errors as a result of lost communication with the GW1000.

@gjr80 gjr80 added the bug Something isn't working label Aug 29, 2020
@gjr80 gjr80 self-assigned this Aug 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant