Simply changing to use the python logging module instead of the syslog module (aka changing to WeeWX v4 logging instead of WeeWX v3 logging) will not in itself enable log_success in a third party extension. log_success needs to be built into the extension (usually through use of conditional statements). Any well written driver/service should not be emitting routine data every loop period at the info level. Looking at your repo I don't think the solution is to use log_success but rather to change the log.info() call at line 69 to log.debug(). Then, if you run WeeWX with debug = 0 your logs will be silent (from this extension) and if you need to see the extension output during troubleshooting just restart WeeWX with debug = 1.
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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/ed6abc55-0276-45cf-9c33-09d3bae2a999n%40googlegroups.com.
