Thanks, but unfortunately it didn't help. I think the problem is the differences between archive record timestamps:
Jan 3 21:05:24 raspberrypi weewx[325]: manager: Added record 2020-01-03 21:03:23 CET (1578081803) to database 'weewx.sdb' Jan 3 21:05:24 raspberrypi weewx[325]: manager: Added record 2020-01-03 *21:03:23* CET (*1578081803*) to daily summary in 'weewx.sdb' Jan 3 21:10:26 raspberrypi weewx[325]: manager: Added record 2020-01-03 21:08:25 CET (1578082105) to database 'weewx.sdb' Jan 3 21:10:26 raspberrypi weewx[325]: manager: Added record 2020-01-03 *21:08:25* CET (*1578082105*) to daily summary in 'weewx.sdb' *1578081803 - *1578081803 = 302 sec > 300000 (gapsize). But sometimes is less than 300 sec. 2020. január 3., péntek 11:06:15 UTC+1 időpontban gjr80 a következőt írta: > > I question the wisdom of specifying a report_timing option setting of */5 > * * * * on a system with a five minute archive interval. I am not sure what > effect you are trying to achieve but the cron like report_timing option > works off the timestamp of the latest archive record, if the difference > between successive timestamps is very close to the report_timing value I > would not be surprised to see some report cycles being skipped. This would > be even more likely to occur if your archive records are consistently > coming in less than five minutes apart (as many of yours are). > > It may have no affect on your go problem, but it might be worth removing > your report_timing setting and restarting WeeWX. > > Gary > > -- 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/b505e4f7-2e6f-4460-9230-2a77f97e40db%40googlegroups.com.
