I'm certainly no expert on the IP logger but I wouldn't have thought a dynamic WAN IP would be affecting the logger when used with weeWX. I thought the typical use case of the logger with weeWX was to connect both the IP logger and the weeWX device to a local router or switch and the IP logger communicates solely with the weeWX device with no knowledge of the WAN. If however, the IP logger was being used to talk to WeatherLink.com I could see a dynamic WAN IP maybe causing an issue. But as far as I know it's either weeWX or WeatherLink.com but not both. Will be interesting to hear Tom's view.
Um, your IP logger is not somehow still trying to connect to WeatherLink.com is it? When set to True loop_on_init simply catches any console/station initialisation failures (ie failure to load the station driver) and forces a retry (ie reload the driver) after 60 seconds. This will happen forever rather than just causing weeWX to exit. Looking at the history it seems loop_on_init was added as an option to weewx.conf in v3.5.0 (March 2016) to mimic the weewxd command line --loop-on-init option (which was previously the --retry option). This might explain why the documentation slipped through the cracks. Am sure Tom will shed some more light in this. Gary -- 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]. For more options, visit https://groups.google.com/d/optout.
