Thanks a lot for your support. I am currently far away from my weather station and my remote login does not work :-( Will look into it when I am back in my cabin (which is closed down for the winter).
Rune. mandag 6. november 2017 04.32.50 UTC+1 skrev gjr80 følgende: > > Hmm, did post a reply this morning but it seems to have disappeared > somewhere into the ether.... > > As long as you can handle a few command line operations you will be fine. > Merging data from a SQLite database has been covered in the forums at least > once, this post > <https://groups.google.com/d/msg/weewx-user/T2VuiIkcAEM/wZzemNzWknQJ> > provides details but at the time it was written weeWX was at v2.x and there > are 1 or 2 extra steps required under weeWX v3.x. To merge data from a > SQLite database, say old_database.sdb, into the existing weeWX SQLite > database, say weewx.sdb: > > 1. make a copy of the old database file old_database.sdb > 2. if necessary, deal with any bogus data that may be in the old database, > this > wiki entry > <https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data> may be > of help (probably does not apply in your case) > 3. if not already installed install the sqlite3 command line utility: > > $ sudo apt-get install sqlite3 > > 4. open the old database using sqlite3 and dump its data: > > $ sqlite3 /home/weewx/archive/old_database.sdb > sqlite> .output /home/weewx/archive/old_database.dump > sqlite> .dump > sqlite> .quit > > 5. stop weeWX > 6. make a backup copy of the weeWX database file weewx.sdb > 7. open weewx.sdb using sqlite3 and import the dumped data: > > $ sqlite3 /home/weewx/archive/weewx.sdb > sqlite> .read /home/weewx/archive/old_database.dump > sqlite> .quit > > 8. rebuild the weewx.sdb daily summaries using the weeWX wee_database > utility (The following wee_database commands assume the data_binding > config option under [StdArchive] in weewx.conf is set to a binding that > uses weewx.sdb, this is the default setup. If this is not the case you > will need to specify the binding to be used by wee_datbase by using the > --binding command line option). If using weeWX v2.6.3 or earlier you need > to drop the daily summaries first: > > $ /home/weewx/bin/wee_database --drop_daily > > Once the daily summaries have been dropped, or if using weeWX v3.7.0 or > later, rebuild the daily summaries: > > $ /home/weewx/bin/wee_database --rebuild_daily > > 9. start weeWX taking note of the log for any errors > 10. weeWX should now be using the merged database, note that any 'to date' > reports or plots will not reflect the merged data until they are > re-generated which can take up to 24 hours. Previous months/years 'by > month' and 'by year' reports such as the NOAA report may need to be deleted > to force regeneration with the updated data. In all cases deleting the > report/plots will force regeneration with the new data on the next report > cycle. > > Merging your weeWX-WD data should follow the same process but when > dropping/rebuilding the weeWX-WD daily summaries you will need to specify > the binding to be used, check the data_binding config option under the > [Weewx-WD] stanza in weewx.conf but something like the following should > work (not tested): > > $ /home/weewx/bin/wee_database --drop_daily --binding=wd_binding > > and/or > > $ /home/weewx/bin/wee_database --rebuild_daily --binding=wd_binding > > Gary > > On Monday, 6 November 2017 06:42:51 UTC+10, Rune Lægreid wrote: >> >> Hi, >> >> The station is again generating images (after clearing Vantage memory) >> Thanks for your assistance. >> >> Is there any way to restore the historic data in weewx (that even I could >> manage)? >> >> Rune. >> >> søndag 5. november 2017 13.17.08 UTC+1 skrev gjr80 følgende: >>> >>> Yep, it all points to corrupt station memory; Vantage, hardware record >>> generation, no archive records being saved and one (or more) power >>> interruptions. >>> >>> 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]. For more options, visit https://groups.google.com/d/optout.
