Records not updating from loop hilo

[Praveen Chandrasekaran]

I have Davis Vantage vue with belfryboy data logger. Archive interval set to 5 minutes.
Record generation set to hardware in weewx.conf
Loop_hilo set to true.

However records still seem to built only from archives. I see that all max min times are at 5 min boundary.

Today my console shows max 34.7c but weewx db shows 34.5c. WU also shows 34.7c.

I added record augmentation to true. Earlier it was unspecified. But it's default is true. So that shouldn't matter right?

What else could be the issue?

[Andrew Milner]

did you stop/start weewx or restart it after changing loop_hilo to true??

can you attach your weewx.conf??

[Praveen Chandrasekaran]

Loop Hi-Lo was always true. I did kill hup after updating record augmentation

Will attach conf in a while. 

--
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/YpPW5KxrCA0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Andrew Milner]

Personally I always prefer to stop and start weewx rather than just re-reading the conf - but that is my preference!!

What are you using to display the max values? ie what is actually in the template for displaying the max fields??  The wrong syntax/dot code could result in an archive search rather than a stats search, and thus would yield an archive time rather than the max/min loop time!!

[Praveen Chandrasekaran]

Loop Hi-Lo has been true since installation. I m just viewing the StdReport. I always used to look at WU and never bothered about StdReport. Only now I noticed that StdReport max min are a tad off due to 5 minutes sampling. 

Wouldn't changing record generation to software solve the issue?

[Praveen Chandrasekaran]

Not able to copy weewx.conf and attach as I dont have a good USB drive to copy it to my laptop. Just attaching relevant section of weewx.conf snippet

[Praveen Chandrasekaran]

The other issue I can think of is I had disabled TimeSynch. Hence if there was mismatch between timestamp from station and the raspberry time, I think the python code discards the loop data it is outside timespan of accumulator (not entirely sure what it means!). I ahd disabled TimeSynch when I did not have RTC and did not want pi to mess up my console time. Now I anyway have RTC, so renabeld TimeSynch and restarted weewx.

Let me see tomorrow how the record generation goes.

[Praveen Chandrasekaran]

The issue seems to be resolved now. I think enabling TimeSynch helped.