Since it is working for you and now it is so easy to add columns to WeeWX DBs, I’m not going to pursue this further. Honestly, if someone had to have a separate DB I’d nudge the to running MQTTSubscribe as a driver in a separate instance…. rich On Saturday, 22 May 2021 at 16:39:21 UTC-4 vince wrote:
> On Saturday, May 22, 2021 at 1:22:31 PM UTC-7 [email protected] wrote: > >> re: logging >> I think you are looking for this, >> https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging#customizing-what-gets-logged >> So adding the following should work. >> [Logging] >> [[loggers]] >> [[[user.MQTTSubscribe]]] >> level = INFO >> Note, I usually do the reverse and only turn on 'DEBUG' for the modules I >> care about... >> >> > Yup - worked fine. Thanks. > > re: additional db/binding >> I hadn't thought of this use case, so currently you can't. Because the >> WeeWX aggregation of loop packets into archive records, is leveraged I >> don't think this would be easy. Unless writing the loop data to a DB is >> what you want. >> >> > In my case I'm emitting the MQTT data from the satellite sensors only once > every 5 minutes so I guess it is the same result either way re: loop or > archive and what goes into the database, but it's not a big deal. Those > particular sensors are just nice-to-have anyway, but I was curious because > I have my old secondary db (that can go away now) that I was thinking of > putting the new data into after I disable my more complicated setup from > fall 2014 (really). It'll be great disabling all that old stuff and doing > it the easy way now :-) > > > -- 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/4d7a2fbc-32f1-41bb-8243-4855a35282e1n%40googlegroups.com.
