You have nothing to apologise over, you did exactly the right thing. Was just pointing out that the operation of log_success is independent of the logging system being used and in the case of a driver or service such as you are using using log.debug() is more appropriate.
Gary On Tuesday, 24 May 2022 at 07:16:12 UTC+10 [email protected] wrote: > On 23/05/2022 21:04, gjr80 wrote: > > 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 > > Apologies, I was only going by what it said at > https://github.com/weewx/weewx/blob/master/docs/logging.md and assumed > that is all I needed to do. > -- 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/44dde51a-af7a-447b-a6b2-571e64ab02abn%40googlegroups.com.
