The catch up is built in to WeeWX and automatically occurs when WeeWX starts up. There are a few ifs buts and maybes though.
First up your driver and hardware needs to support it. I assume you are using the fousb driver which does support catchup, your station also appears to support it. What WeeWX does during the catchup is ask the driver to provide any records since the timestamp of the last good record in your archive. The driver then does what it needs to obtain these records from your station. If the missing data in your database has good records after the period of missing data (eg you have no data from 9am to 10am but there is data from 10am onwards) then that period of missing data will not be filled, even if the records are in the stations logger. So generally speaking there is one chance to catchup, and that is on the first WeeWX startup after an outage. Once WeeWX starts adding records after the outage backfill of that outage will not occur. If you look at the log during startup you will see the catchup just before startup is complete. I don't believe there is any detail of the outcome in the log though. That fairly much covers the automatic catchup. There are a few things you can try to force a backfill. Firstly, if there are records in the archive after the period of the outage then try stopping WeeWX, backup you database just in case, delete the records after the outage and then restart WeeWX. This will trigger the automatic backfill again and you may or may not have success. Check the archive afterwards to see if the data was restored. The other thing you can try is using wee_device <http://weewx.com/docs/utilities.htm#wee_device_utility> to somehow dump the contents of your logger. wee_device capabilities in this regard are dependent on the capabilities of your driver and station. When used with the vantage driver wee_device has the --dump command line option that dumps all logger records to database, the result is that any gaps in the archive are filled if the corresponding record is in the logger. Looking at wee_device, when used with the fousb driver the --dump option is not available but the --history option <http://weewx.com/docs/hardware.htm#Action_--history> is. --history appears to dump the logger contents to console not the database, not sure why not, that is one for the fousb driver author. At least this will let you see what is in your stations logger. If the missing data is there you may be able to find a way of dumping the data to file and then importing with wee_import <http://weewx.com/docs/utilities.htm#wee_import_utility> or the like. Finally, remember that the 1080 uses a circular buffer, once it is full the oldest data is overwritten. It appears the 1080 has 4080 buffer locations, how long that covers in time depends on the interval. The default 30 minutes will give you about 85 days of coverage, something like 5 minutes will give you around 14 days. So I wouldn't leave it for a few months to sort out! Gary On Sunday, 27 June 2021 at 06:22:27 UTC+10 [email protected] wrote: > Vince, > The wh1080 has a battery backup and runs if it's out of power via usb. So > I'll wait and see if the rain gets into the database! > Do you know how this is done? And when? > Thanks for your answer! > /Mikael > > lördag 26 juni 2021 kl. 21:59:27 UTC+2 skrev vince: > >> Does the WH1080 have a logger that works if the power is out ? If so, >> weewx should gracefully catch up. >> >> FWIW, a Davis VP2 has a battery backed up console which is where the >> logger is physically, so the console has to have good batteries (or UPS) >> for data to be saved while the power is out. Sorry but I don't know enough >> about the WH1080 to help more. >> >> -- 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/9b813070-43a1-4a8c-b97d-3b58ea58e324n%40googlegroups.com.
