On Saturday, 7 March 2026 at 04:36:18 UTC+4 Conz wrote:

I have put 'weewx.engine.StdPrint' at the start of everything under 
[Engine] [[Services]] 


I don't know what you mean by this but if you are going to use StdPrint to 
display loop packets (and archive records) you really need to understand 
one thing about how WeeWX services are called - the various entries under 
[Engine] [[Services]] are processed in order left to right and top to 
bottom. So if you put StdPrint at the start of the prep_services line you 
will see loop packets (and archive records if applicable) straight from the 
driver. Put StdPrint as the first entry of process_services and you will 
see the same, but put it at the end of the process_services line and you 
will see loop packets (and driver emitted archive records) after 
StdConvert, StdCalibrate, StdQC and StdWXCalculate have done their thing to 
the packet/record. If you are using a driver that only emits loop packets 
(ie StdArchive creates the archive record) then you won't see any archive 
records from StdPrint unless StdPrint appears 'after' StdArchive. Think of 
the [[Services]] entries as an assembly line with loop packets (and driver 
emitted archive records) going in the front and each service doing their 
bit to the packets/records. At the end out pops a processed packet/record. 
Where you put StdPrint on the assembly line determines what StdPrint will 
produce.

Any services that don't change the loop packet /archive record (eg 
StdTimeSynce or any of the restful_services) have no effect on the StdPrint 
output.

Whilst 'moving' StdPrint around can aid in debugging putting multiple 
StdPrint entries in [[Services]] is probably only going to make for output 
that is very difficult to read/follow.

R 

-- 
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 visit 
https://groups.google.com/d/msgid/weewx-user/cadef698-b1b7-44a7-bf8f-b18c194b03c6n%40googlegroups.com.

Reply via email to