When you say “it didn’t work for you” do you mean using —rebuild-daily only (ie no —drop-daily first) or using —today? I don’t know why, rebuilding just the affected day(s) is useful for retaining loop high/low value and time stamps for unaffected days. Also, sometimes the daily summary tables need to be dropped first (using —drop-daily) before you rebuild them.
The daily summary tables are named ‘archive_day_xxxx’ where xxxx is an observation field in the archive table schema. So the outTemp daily summary table is archive_day_outTemp. Each table consists of a single row per day, the dateTime field for each row holds the midnight (local time) timestamp. If I read your post correctly you mention the max outTemp timestamp for 1 August 2019 is midnight. That could be the case (unlikely but possible for a day in the past also possible for the current day if you view the data before sunrise). If you have concerns about the integrity of your data in the daily summary the best approach is to check the archive table data for that observation for that day and see whether the daily summary entry is consistent with the archive data (eg when was the outTemp max on 1 August according to the archive). During a rebuild the daily summary data is derived from the archive so there should be no disagreement. 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/ac263d20-628a-4389-94b6-6b1e982b8f05%40googlegroups.com.
