FWIW - I didn't do it via wee_config here, which likely explains what I got as a result.
I tend to install weewx with --no-prompt which defines using the simulator, then add the extension/driver, then hand-edit weewx.conf to point to the other driver once I get everything else edited in there. Admittedly, that's not following the expected procedure I guess, but it does explain how I got my result here. On Sunday, December 27, 2020 at 4:01:51 PM UTC-8 gjr80 wrote: > > loop_on_init hadn't been set by the install script... > > Did you run wee_config —reconfigure to reconfigure WeeWX to use the GW1000 > driver after installing the driver? wee_config —reconfigure will ask if you > want to set loop_on_init. If you did run wee_config —reconfigure did you > set loop_on_init or not? Did the resulting setting in weewx.conf agree > without you4 selection? > > loop_on_init is a general WeeWX option set in the top level of weewx.conf. > It is covered under General <http://weewx.com/docs/usersguide.htm#General> in > The configuration file weewx.conf section > <http://weewx.com/docs/usersguide.htm#weewxconf> in the Users Guide. > Placing it in [GW1000] will have no effect. > > Gary > On Monday, 28 December 2020 at 09:36:33 UTC+10 [email protected] > wrote: > >> I had the same issue like Vince the other day - and .... loop_on_init >> hadn't been set by the install script... >> I assume it's to set in the [GW1000] stanza - that's where I added it now. >> >> >> -------- Forwarded Message -------- >> Subject: [weewx-user] Re: gw1000 driver fail on wifi loss >> Date: Sun, 27 Dec 2020 13:12:19 -0800 (PST) >> From: gjr80 <[email protected]> >> Reply-To: [email protected] >> To: weewx-user <[email protected]> >> >> That would explain the behaviour then, if loop_on_init is not set the >> loss of connectivity with the station (for whatever reason) will cause >> WeeWX tobeen exit as it does with any other driver. I will make a point of >> pulling the network on my GW1000 and confirming the driver and loop_on_init >> work as expected. >> >> Gary >> >> On Monday, 28 December 2020 at 07:08:28 UTC+10 vince wrote: >> >>> (unsure if this blasted google groups new interface ate my draft reply - >>> grrrrrr...) >>> >>> loop_on_init was not set at all, so it's sure acting like the default is >>> False. >>> I'll define it as True for the next time, which hopefully won't need >>> testing for a long time.... >>> >>> Thanks. >>> >>> On Sunday, December 27, 2020 at 11:53:08 AM UTC-8 gjr80 wrote: >>> >>>> Vince, >>>> >>>> Thank you. From memory the driver should retry continuously when the >>>> network returns if loop_on_init = True in weewx.conf (though I am not sure >>>> I tested this by turning of my network). Can you confirm the loop_on_init >>>> setting at the time? >>>> >>>> Gary >>>> >>>> On Monday, 28 December 2020 at 03:54:33 UTC+10 vince wrote: >>>> >>>>> Gary - I wanted to pass along some logs from a gw1000 driver abort >>>>> yesterday. >>>>> >>>>> I had my home network down for a bit yesterday to do some firmware >>>>> updates on my Ubiquiti USG, Switch and AcLite access point and weewx >>>>> aborted rather quickly. >>>>> >>>>> The external, wired, and wifi networks were indeed down for some >>>>> minutes so missing some readings was expected, but I was hopeful that the >>>>> driver would recover gracefully after things were back up, however weewx >>>>> totally aborted and the process was gone. >>>>> >>>>> Just passing along the logs in case you wanted to take a look. Thanks. >>>>> >>>>> >>>>> >>>>> Dec 26 16:26:16 pi3jr weewx[18939] ERROR user.gw1000: Failed to obtain >>>>> response to command 'CMD_GW1000_LIVEDATA' after 3 attempts >>>>> Dec 26 16:26:16 pi3jr weewx[18939] ERROR user.gw1000: Unable to obtain >>>>> live sensor data >>>>> Dec 26 16:26:16 pi3jr weewx[18939] INFO weewx.engine: Main loop >>>>> exiting. Shutting engine down. >>>>> Dec 26 16:26:16 pi3jr weewx[18939] INFO weewx.engine: Shutting down >>>>> StdReport thread >>>>> Dec 26 16:26:36 pi3jr weewx[18939] ERROR weewx.engine: Unable to shut >>>>> down StdReport thread >>>>> Dec 26 16:26:43 pi3jr weewx[18939] ERROR user.gw1000: Failed to obtain >>>>> response to command 'CMD_GW1000_LIVEDATA' after 3 attempts >>>>> Dec 26 16:26:43 pi3jr weewx[18939] ERROR user.gw1000: Unable to obtain >>>>> live sensor data >>>>> Dec 26 16:26:44 pi3jr weewx[18939] INFO user.gw1000: Gw1000Collector >>>>> thread has been terminated >>>>> Dec 26 16:26:44 pi3jr weewx[18939] CRITICAL __main__: Caught >>>>> WeeWxIOError: Failed to obtain response to command 'CMD_GW1000_LIVEDATA' >>>>> after 3 attempts >>>>> Dec 26 16:26:44 pi3jr weewx[18939] CRITICAL __main__: **** >>>>> Waiting 60 seconds then retrying... >>>>> Dec 26 16:27:44 pi3jr weewx[18939] INFO __main__: retrying... >>>>> Dec 26 16:27:44 pi3jr weewx[18939] INFO __main__: Using configuration >>>>> file /etc/weewx/weewx.conf >>>>> Dec 26 16:27:44 pi3jr weewx[18939] INFO __main__: Debug is 0 >>>>> Dec 26 16:27:44 pi3jr weewx[18939] INFO weewx.engine: Loading station >>>>> type GW1000 (user.gw1000) >>>>> Dec 26 16:28:08 pi3jr weewx[18939] ERROR user.gw1000: Failed to obtain >>>>> response to command 'CMD_READ_STATION_MAC' after 3 attempts >>>>> Dec 26 16:28:08 pi3jr weewx[18939] ERROR weewx.engine: Import of >>>>> driver failed: Failed to obtain response to command >>>>> 'CMD_READ_STATION_MAC' >>>>> after 3 attempts (<class 'user.gw1000.GW1000IOError'>) >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> Traceback (most recent call last): >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> File "/usr/share/weewx/weewx/engine.py", line 109, in setupStation >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> self.console = loader_function(config_dict, self) >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> File "/usr/share/weewx/user/gw1000.py", line 1293, in loader >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> return Gw1000Driver(**config_dict[DRIVER_NAME]) >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> File "/usr/share/weewx/user/gw1000.py", line 1568, in __init__ >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> super(Gw1000Driver, self).__init__(**stn_dict) >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> File "/usr/share/weewx/user/gw1000.py", line 767, in __init__ >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> debug_wind=self.debug_wind) >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> File "/usr/share/weewx/user/gw1000.py", line 1870, in __init__ >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> lost_contact_log_period=lost_contact_log_period) >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> File "/usr/share/weewx/user/gw1000.py", line 2276, in __init__ >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> self.mac = self.get_mac_address() >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> File "/usr/share/weewx/user/gw1000.py", line 2407, in get_mac_address >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> return self.send_cmd_with_retries('CMD_READ_STATION_MAC') >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> File "/usr/share/weewx/user/gw1000.py", line 2532, in >>>>> send_cmd_with_retries >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> raise GW1000IOError(_msg) >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL weewx.engine: **** >>>>> user.gw1000.GW1000IOError: Failed to obtain response to command >>>>> 'CMD_READ_STATION_MAC' after 3 attempts >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL __main__: Unable to load >>>>> driver: Failed to obtain response to command 'CMD_READ_STATION_MAC' after >>>>> 3 >>>>> attempts >>>>> Dec 26 16:28:08 pi3jr weewx[18939] CRITICAL __main__: **** >>>>> Exiting... >>>>> >>>> -- >> 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/230141dd-4b09-4fab-8798-776d46028592n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/230141dd-4b09-4fab-8798-776d46028592n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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/3ba40046-ccd6-4953-9cdc-457a0d96b207n%40googlegroups.com.
