You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered: