Hey, sorry to necro this thread, but I do have the exact same issue: I set up weewx for a klimalogg which was already running since end of 2013. Once I connected everything it started reading out the historical data:
Dec 26 20:52:25 raspberrypi weewx[8067]: KlimaLogg: RFComm: handleHistoryData: records cached=1782, records skipped=0, next=1783 Dec 26 20:52:25 raspberrypi weewx[8067]: KlimaLogg: RFComm: handleHistoryData: records cached=1788, records skipped=0, next=1789 Dec 26 20:52:26 raspberrypi weewx[8067]: KlimaLogg: RFComm: handleHistoryData: records cached=1794, records skipped=0, next=1795 Dec 26 20:52:26 raspberrypi weewx[8067]: KlimaLogg: RFComm: handleHistoryData: records cached=1800, records skipped=0, next=1801 Dec 26 20:52:29 raspberrypi weewx[8067]: KlimaLogg: MainThread: Records scanned: 1800 Dec 26 20:52:29 raspberrypi weewx[8067]: KlimaLogg: MainThread: Found 1799 historical records Dec 26 20:52:29 raspberrypi weewx[8067]: KlimaLogg: MainThread: Handle record 1: 2013-11-04 11:30:00 CET (1383561000) Dec 26 20:52:29 raspberrypi weewx[8067]: KlimaLogg: MainThread: Handle record 2: 2013-11-04 11:45:00 CET (1383561900) Dec 26 20:52:29 raspberrypi weewx[8067]: manager: Added record 2013-11-04 11 :45:00 CET (1383561900) to database 'weewx-kl.sdb' Dec 26 20:52:29 raspberrypi weewx[8067]: manager: Added record 2013-11-04 11 :45:00 CET (1383561900) to daily summary in 'weewx-kl.sdb' [...] after a few minutes: Dec 26 20:57:35 raspberrypi weewx[8067]: manager: Added record 2013-12-11 03 :00:00 CET (1386727200) to database 'weewx-kl.sdb' Dec 26 20:57:35 raspberrypi weewx[8067]: manager: Added record 2013-12-11 03 :00:00 CET (1386727200) to daily summary in 'weewx-kl.sdb' Dec 26 20:57:35 raspberrypi weewx[8067]: KlimaLogg: MainThread: Saved 1799 historical records; ts last saved record 2013-12-11 03:00:00 CET (1386727200 ) Dec 26 20:57:35 raspberrypi weewx[8067]: KlimaLogg: MainThread: Scan the next batch of 1800 historical records Dec 26 20:57:35 raspberrypi weewx[8067]: KlimaLogg: MainThread: The scan will start after the next historical record is received. Dec 26 20:58:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next batch of 1800 records will start within 5 minutes Dec 26 20:58:20 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next batch of 1800 records will start within 5 minutes Dec 26 20:58:35 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next batch of 1800 records will start within 5 minutes Dec 26 20:58:50 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next batch of 1800 records will start within 5 minutes Dec 26 20:59:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next batch of 1800 records will start within 5 minutes Dec 26 20:59:20 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next batch of 1800 records will start within 5 minutes Dec 26 20:59:35 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next batch of 1800 records will start within 5 minutes Dec 26 20:59:50 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next batch of 1800 records will start within 5 minutes Dec 26 21:00:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next batch of 1800 records will start within 5 minutes Dec 26 21:00:06 raspberrypi weewx[8067]: KlimaLogg: RFComm: handleHistoryData: request records since 2013-12-11 03:00:00 CET (1386727200 ) Dec 26 21:00:06 raspberrypi weewx[8067]: KlimaLogg: RFComm: Number of history records limited to: 51200 Dec 26 21:00:06 raspberrypi weewx[8067]: KlimaLogg: RFComm: handleHistoryData: records cached=0, records skipped=0, next=39180 Dec 26 21:00:20 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next batch of 1800 records will start within 5 minutes As you see on line with the time stamp 21:00:06 for some reason it now says "next=39180" and five more minutes of "the next batch will start in 5 minutes" messages: Dec 26 21:04:50 raspberrypi weewx[8067]: KlimaLogg: MainThread: The next batch of 1800 records will start within 5 minutes Dec 26 21:05:02 raspberrypi weewx[8067]: KlimaLogg: RFComm: handleHistoryData: records cached=1, records skipped=5, next=39181 Dec 26 21:05:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: Records scanned: 1 Dec 26 21:05:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: Found 0 historical records Dec 26 21:05:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: Handle record 1801: 2017-12-26 21:05:00 CET (1514318700) Dec 26 21:05:05 raspberrypi weewx[8067]: KlimaLogg: MainThread: Saved 0 historical records; ts last saved record 2017-12-26 21:05:00 CET (1514318700 ) Dec 26 21:05:05 raspberrypi weewx[8067]: engine: Starting main packet loop. Dec 26 21:10:16 raspberrypi weewx[8067]: manager: Added record 2017-12-26 21 :10:00 CET (1514319000) to database 'weewx-kl.sdb' Dec 26 21:10:16 raspberrypi weewx[8067]: manager: Added record 2017-12-26 21 :10:00 CET (1514319000) to daily summary in 'weewx-kl.sdb' Dec 26 21:10:17 raspberrypi weewx[8067]: cheetahgenerator: Generated 1 files for report kl in 0.89 seconds Dec 26 21:10:26 raspberrypi weewx[8067]: imagegenerator: Generated 44 images for kl in 8.24 seconds Now it just started with the 'live' data. Additional observation after running for a few days: If the service is stopped for a while it can recover all the recorded data. But if this period is too long (several hours) it just does not read the history data and just starts again with the live data. Is there any way I can reset the "next" setting back to 0 and start over? eddy On Sunday, 9 July 2017 01:35:15 UTC+2, Luc Heijst wrote: > > Hi Philipp, > > What is the value of your archive_interval in weewx.conf? > > [StdArchive] > archive_interval = 300 > Default it is 5 minutes (300 s). > > The next batch of 1800 records should start the next archive interval. > > As a work-around you also can increase the batch_size from 1800 to a > higher value.in the [Klimalogg] section of weewx.conf. > See example below. > > [KlimaLogg] > max_history_records = 51200 > batch_size = 51200 > > Luc > > On Wednesday, 28 June 2017 16:34:11 UTC-3, Philipp Gräser wrote: >> >> Hi, >> >> I have installed weewx on an BananaPi with Ubuntu 14.04.5 LTS as >> operating system. I am using a KlimaloggPro weather station. I have >> intalled the software over the DEB package and made the installation as >> descripted by Methew for this device. The communication works and the DB is >> filled with values.The reporting is also working fine. >> >> The problem are the historical values. The buffer is round about 85% >> filled. After pairing the device with weewx the vlaues are transfered into >> the db, but after 1800 values the import stops. The pronnounced next batch >> never starts. Please help me importing my historical Data into the db. >> Thanks in advance! >> >> Syslog: >> Jun 28 21:18:48 lemaker weewx[2128]: KlimaLogg: MainThread: Handle record >> 1794: 2016-04-14 12:45:00 CEST (1460630700) >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 12:45:00 CEST (1460630700) to database 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 12:45:00 CEST (1460630700) to daily summary in 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: KlimaLogg: MainThread: Handle record >> 1795: 2016-04-14 13:00:00 CEST (1460631600) >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 13:00:00 CEST (1460631600) to database 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 13:00:00 CEST (1460631600) to daily summary in 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: KlimaLogg: MainThread: Handle record >> 1796: 2016-04-14 13:15:00 CEST (1460632500) >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 13:15:00 CEST (1460632500) to database 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 13:15:00 CEST (1460632500) to daily summary in 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: KlimaLogg: MainThread: Handle record >> 1797: 2016-04-14 13:30:00 CEST (1460633400) >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 13:30:00 CEST (1460633400) to database 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 13:30:00 CEST (1460633400) to daily summary in 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: KlimaLogg: MainThread: Handle record >> 1798: 2016-04-14 13:45:00 CEST (1460634300) >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 13:45:00 CEST (1460634300) to database 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 13:45:00 CEST (1460634300) to daily summary in 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: KlimaLogg: MainThread: Handle record >> 1799: 2016-04-14 14:00:00 CEST (1460635200) >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 14:00:00 CEST (1460635200) to database 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 14:00:00 CEST (1460635200) to daily summary in 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: KlimaLogg: MainThread: Handle record >> 1800: 2016-04-14 14:15:00 CEST (1460636100) >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 14:15:00 CEST (1460636100) to database 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: manager: Added record 2016-04-14 >> 14:15:00 CEST (1460636100) to daily summary in 'weewx-kl.sdb' >> Jun 28 21:18:48 lemaker weewx[2128]: KlimaLogg: MainThread: Saved 1799 >> historical records; ts last saved record 2016-04-14 14:15:00 CEST >> (1460636100) >> Jun 28 21:18:48 lemaker weewx[2128]: KlimaLogg: MainThread: Scan the next >> batch of 1800 historical records >> Jun 28 21:18:48 lemaker weewx[2128]: KlimaLogg: MainThread: The scan will >> start after the next historical record is received. >> Jun 28 21:19:18 lemaker weewx[2128]: KlimaLogg: MainThread: The next >> batch of 1800 records will start within 5 minutes >> > -- 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]. For more options, visit https://groups.google.com/d/optout.
