Modify StdPrint to not print loop packets?

[bdf0506]

My log file is far too noisy in my docker implementation of wee experience, so I’m looking for a quick and easy way to only print the archive packets with StdPrint and then only print loop packets if debug is enabled. Is this easily possible? Or will I have to create my own service to run, as described in the customization guide?

Thanks in advance!

[Tom Keffer]

Unfortunately, there are no options to do that. You'd have to replace StdPrint with your own service .

On Sat, Jan 2, 2021 at 9:12 PM bdf0506 <bdfu...@gmail.com> wrote:

My log file is far too noisy in my docker implementation of wee experience, so I’m looking for a quick and easy way to only print the archive packets with StdPrint and then only print loop packets if debug is enabled. Is this easily possible? Or will I have to create my own service to run, as described in the customization guide?

Thanks in advance!

--
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/75d759a9-9e93-4c8e-b6b9-e4a2ec8fe8f8n%40googlegroups.com.

[Brad Furman]

Thanks Tom. BTW, the example shown on the help docs for modifying an existing service is incorrect. http://weewx.com/docs/customizing.htm#Customizing_a_service

The print statement in this example needs to be encapsulated in parentheses.

You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/i1gVISpngc4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEByrhqfkQT6tKi7bznYPGRuCtNH2y_aOgZL6R7E1AkmJg%40mail.gmail.com.

--

Brad Furman
bdfu...@gmail.com

[Tom Keffer]

True. It would only work under Python 2.

Fixed in commit e12237c

-tk

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAEwo8bL05C-ce3ZMfLH_smsF_PKKfacPdwsBZ1pbB0oJDa2huQ%40mail.gmail.com.

[bdf0506]

So i've been banging my head against the wall trying to get the StdPrint service to only print archive packets, and I must be missing something. 

I modified bin/weewx/engine.py ---- yes, I am aware that long term I should create a new python script in bin/user but this was only for testing purposes at this point.

In https://github.com/weewx/weewx/blob/master/bin/weewx/engine.py I commented out lines 774, and then 777-781. But after doing that and restarting weewx, the loop packets no longer print to console, which is expected, but then the archive records do not print to the console either.

What am I missing with the way that this service works? It seems like the Archive record print service might somehow be dependent on the loop packet print?

[Tom Keffer]

You did it right (although, actually, you would need to comment out only line 774).

Remember: archive records are emitted only once an archive period, which is usually every 5 minutes or even longer, depending on your configuration. You'll have to be patient to see one.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/7fa4b3c7-12da-4f50-b3d1-ff6ca315b77cn%40googlegroups.com.

[bdf0506]

Thanks for the validation here Tom to make sure I wasn't missing something obvious - but still no luck here :(

I setup a brand new docker container with a simulator driver to test this out. With line 774 commented out, nothing is printed to console. It needs to print loop packets to be able to print archive packets. See details below:

WeeWX config: https://pastebin.com/ci2Ta1yL

With nothing commented out, running it normally, loop and archive packets printed: https://pastebin.com/b55mFkEW (line 113 and 254 shows the archive packet being printed)

With line 774 commented out, neither loop nor archive packets printed: https://pastebin.com/f7zwtdJr

[Tom Keffer]

I don't know what I'm looking at here. Why is the stdout stream being intermixed with the system log?

I tried commenting out line 774 on my own machine, and it worked as expected.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/41c99688-f562-4f26-b393-f22f978bd788n%40googlegroups.com.

[Brad Furman]

It's in a docker container, that's why the stdout is being mixed with the system log. So if it's working on your side, must be something with the docker container. I'm utilizing the following docker container: https://github.com/felddy/weewx-docker

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEBz9W2qJo8sVHt5481vde66RRVPvFP2Z5GK02OX7jOYqQ%40mail.gmail.com.

--

Brad Furman
bdfu...@gmail.com