Thank you for the replies. Yes, as stated the"no_catchup" setting does not exist in my /home/weewx/weewx.conf file. Used the setup.py method of installation using latest weewx as of 10/5/2020. Therefore based on the replies no_catchup is already set to false by default somewhere in the weewx program and therefore should attempt to catch up when offline for several days. That would only leave the second reason stated in the first reply--that there is a time stamp already newer in my database that has prevented the catchup from reaching further back than this this newer time stamp. How could that be possible since the machine was started after 3 days without an ability to receive data that would include the newer time stamped data? I did stop weewx and invoke the wee_device --dump command but received the response of bash : wee_device command not found. I then tried the following command that did work: /home/weewx/util/scripts/wee_device /home/weewx/weewx.conf --dump I was then prompted for for a yes or no which proceeded with a yes it and it dumped data through 10/07/2020 which should include data through the offline time. This data is to be placed automatically into the database file according to the documentation when using the dump command. How long does it take to show on the plot graphs (/home/weewx/public_html/index.html) which would remove the blank data line of temp, humidity etc.? Does dumping the data clear the memory of the data logger or is it still there as well as now on my dump file? Incidentally, should the full paths have been needed to invoke the wee_device command. Thank you and my apologies for so many questions.
On Wednesday, October 14, 2020 at 3:43:26 PM UTC-5 gjr80 wrote: > No. no_catchup was implemented to give users the ability to turn off the > automatic catch-up/backfill that occurs on WeeWX startup. To *disable* > automatic > catch-up/backfill on WeeWX startup you need to set no_catchup = True; > if no_catchup is omitted or no_catchup = False (the default) automatic > catch-up/backfill on WeeWX startup will be enabled. A fresh WeeWX install > will not include the no_catchup setting in weewx.conf but automatic > catch-up/backfill on WeeWX startup will still occur due to the default > being False. > > I would expect not many folks would use no_catch to disable automatic > catch-up/backfill on WeeWX startup. > > Gary > > On Thursday, 15 October 2020 at 04:44:20 UTC+10 [email protected] wrote: > >> So to do the backfill, >> [StdArchive] >> no_catchup = True >> >> Thanks >> Greg >> >> On Wednesday, October 14, 2020 at 6:17:53 AM UTC-5 gjr80 wrote: >> >>> Hi, >>> >>> Whilst it's true the vantage driver will backfill records generated >>> during a WeeWX outage there are some conditions/limitations. Firstly, in >>> weewx.conf under [StdArchive] option no_catchup must either not exist >>> or must be set to False otherwise the hardware record catchup will not be >>> attempted (the no_catchup option is not included in weewx.conf for a >>> default install so likely it will not exist on your system). Secondly, and >>> what probably prevents most catchups occurring, is that the catchup only >>> downloads those records that are newer/younger/more recent than the >>> timestamp of the last good archive record in your database. Whilst your >>> missing data may well be in the data logger it could be the you have a >>> record in your archive that is timestamped after the logger data of >>> interest. In this case the easiest solution is to stop WeeWX and use the >>> wee_device utility with --dump >>> <http://weewx.com/docs/hardware.htm#vantage_dumping_the_logger_memory> >>> to dump all of the archive records stored in the logger to WeeWX. You can >>> check the WeeWX log to see what records were downloaded during the dump. >>> --dump will download all stored archive records but only those not >>> already saved in the WeeWX archive will be saved, those already in the >>> archive will generate a duplicate key error which can be ignored. >>> >>> Just for completeness there is one other situation where backfill of >>> logged data did not occur. WeeWX v3.9.0 introduced a change whereby >>> backfill was only attempted on startup if hardware record generation was in >>> use. This behaviour was changed as of v3.9.1 and backfill is now attempted >>> irrespective of whether hardware or software archive record generation is >>> used. >>> >>> Gary >>> >>> On Wednesday, 14 October 2020 12:39:48 UTC+10, [email protected] >>> wrote: >>>> >>>> Have a raspberry pi 3b running weewx 4.1 (thank you for a great program >>>> and so much hard work and the online support), but am curious as to why >>>> the >>>> data which should be up to 8 days for the data logger was not uploaded >>>> automatically when restarting the raspberry pi. There is a gap of 3 days >>>> that I don't understand if the logger keeps 8 days in memory. Apparently >>>> there is a setting that needs to be changed but am unsure of this setting. >>>> thank you for your time. >>>> >>> -- 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/f70983c7-928e-4ba0-b73c-276d0d6715a1n%40googlegroups.com.
