The line you highlighted is a consequence of the error rather than the cause. When WeeWX reloads the driver WeeWX essentially does a soft restart, it shuts everything down beforehand.
Here is you error: Jul 4 18:42:50 celsius weewx[900] CRITICAL __main__: Caught OSError: timed out Jul 4 18:42:50 celsius weewx[900] CRITICAL __main__: **** Traceback (most recent call last): Jul 4 18:42:50 celsius weewx[900] CRITICAL __main__: **** File "/home/weewx/bin/weewxd", line 154, in main Jul 4 18:42:50 celsius weewx[900] CRITICAL __main__: **** engine.run() Jul 4 18:42:50 celsius weewx[900] CRITICAL __main__: **** File "/home/weewx/bin/weewx/engine.py", line 188, in run Jul 4 18:42:50 celsius weewx[900] CRITICAL __main__: **** for packet in self.console.genLoopPackets(): Jul 4 18:42:50 celsius weewx[900] CRITICAL __main__: **** File "/home/weewx/bin/user/weatherlinkliveudp.py", line 414, in genLoopPackets Jul 4 18:42:50 celsius weewx[900] CRITICAL __main__: **** data, wherefrom = comsocket.recvfrom(2048) Jul 4 18:42:50 celsius weewx[900] CRITICAL __main__: **** socket.timeout: timed out Jul 4 18:42:50 celsius weewx[900] CRITICAL __main__: **** Waiting 10 seconds then retrying... Jul 4 18:43:00 celsius weewx[900] INFO __main__: retrying... If you don’t want a driver reload you need to alter weatherlinkliveudp.py to tolerate a socket.timeout error. This is a common requirement when you have a driver (or for that matter a service) that relies on an external system; your driver/service needs to be able to handle the case where the external service does not respond. Gary -- You received this message because you are subscribed to the Google Groups "weewx-development" 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-development/d4c39ac1-6b6f-4c2b-9548-45e150f47a86o%40googlegroups.com.
