Your analysis is probably correct. You're setting a value for timeout and that time is expiring.
Rather than raise a WeeWXIOError, probably what you want to do is try again. After a few tries, maybe 3 or 4, then you raise WeeWXIOError. This is the way most other drivers work. -tk On Tue, Aug 30, 2016 at 9:56 AM, Pat O'Brien <[email protected]> wrote: > I'm using a custom driver I wrote for my socket server relay setup. > Basically the weather station posts to my server via URL, then PHP posts to > the socket. WeeWx is listening on the socket and uses the data as part of > the loop. (The driver is here: https://github.com/poblabs/ > weewx-socketlogger) > > It's about every minute to every 5 minutes now, I'll get an error like > below. I'm not sure of the pattern. Could it be that the socket doesn't > post data within a certain amount of time that weewx is looking for? > > engine: Shutting down StdReport thread > engine: Caught WeeWxIOError: timed out > **** Waiting 60 seconds then retrying... > engine: retrying... > > Is it possible to extend the WeeWxIOError? > > Thoughts? Thanks! > >
