Hey Luc, yes, that's also the idea I came up with. I set the batch length to 51.200 as you suggested in your older post and it is populating a new database as we speak. I hope it will work :)
Any idea why it failed in the first place? or the reason why it sometimes failes to read historical data properly? On Saturday, 30 December 2017 00:52:50 UTC+1, Luc Heijst wrote: > > Hi Eddy, > > At startup the klimalogg driver reads the timestamp of the most recent > record in the weewx database. > It then tries to read all records in the klimalogg memory with a bigger > time stamp until no newer records can't be found. > Then the driver starts collecting the recent data each five minutes. > When you want to start all over with reading all records of the klimalogg > (this can be as many as 51.200 !!) you will have to stop weewx, delete or > rename your weewx database file and start weewx. This process can take many > hours, sometimes several days, to complete depending of the speed of your > computersystem. > > If you don't want to start all over, but read the data back since a > certain date, you need to delete all newer records in the weewx database > and then restart weewx. > > Luc > > -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
