Would appreciate some more info on this, I just used 4.0 wee_debug it it obfuscated a new WU API key as expected. The obfuscation code is pretty basic, for WU it is if key name == 'api_key' then value with 'XXX obfuscated by wee_debug XXX'. I seem to remember you changing WU config option names some time ago, what is the config option name that failed, I'm betting it was not 'api_key'.
Gary On Sunday, 17 November 2019 11:37:24 UTC+10, Leon Shaner wrote: > > > BTW, wee_debug is not obfuscating the new WU apikey property. > -- 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 weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/b762f6cd-7e78-444e-b80c-e8009f003b7c%40googlegroups.com.
