Actually, the log extract provided shows no information whatsoever regarding reports, just database updates. Though a report thread should be kicked off almost immediately after the database is updated.
Depending on the weather station capabilities and WeeWX configuration, you may well not see archive records being saved at the same time. It takes the arrival of a loop packet to cause WeeWX to check whether it is time to synthesise or request an archive record. So if you have loop packets coming in at irregular intervals, or there are long intervals between loop packets, it is quite conceivable you will see archive records being saved to database at different times each archive period and that the variation in seconds could be as much as the maximum loop packet interval. If your station has a very short loop packet interval you will find the archive record is synthesised/obtained from the hardware much closer to the same time each archive period. The key measure is the archive record time stamp which in your case is remaining hard and fast on the 5 minute boundary Gary On Wednesday, 22 May 2019 09:25:18 UTC+10, vince wrote: > > On Tuesday, May 21, 2019 at 1:04:19 PM UTC-7, wysiwyg wrote: >> >> >> But when looking my logs, I seems a bit irregular...(I considered " >> manager: Added record 2019-05-18 21:20:00 CEST (1558207200) to database >> 'weewx.sdb'" >> as starting point of 5 minute tasks). >> >> Is it expected? if not, what could cause this ? >> >> > What in particular do you think is wrong ? > The fact that it it's not literally a second or two after you expect > things ? > > Without your crontab entries and 'much' more info about your configs, > we're not going to be able to help much. > Looks like it's working to me. > > -- 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/fc91998f-8108-410f-92bd-a814a820f50a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
