I have delete my /var/www/html/weewx directory and then run wee_reports and everything gets recreated. I usually have weewx stopped when doing stuff. It catches up eventually with new records. wee_database /etc/weewx/weewx.conf --drop-daily wee_database /etc/weewx/weewx.conf --rebuild-daily
My Cumulus was the old Cumulus so hopefully your log files are the same? http://www.weewx.com/docs/utilities.htm#Importing_from_Cumulus I converted ages ago and it work fine. The conf file tells where you have placed all the cumulus log giles. EG Feb17log.txt etc The conf file also tells the converter what units to use: [[Units]] temperature = degree_C # options are 'degree_F' or 'degree_C' pressure = hPa # options are 'inHg', 'mbar' or 'hPa' rain = mm # options are 'inch' or 'mm' speed = km_per_hour # options are 'mile_per_hour', # 'km_per_hour', 'knot' or # 'meter_per_second' I wrote a script to do it I use mysql as I like it better than mysqlite: #!/bin/bash #this is to import my Cumulus data into weewx echo number of records to be processed: mysql -u weewx -pweewx << EOF use weewx; select count(*) from archive; EOF echo backup weewx just in case sudo /usr/bin/mysqldump --user=root -p weewx > /tmp/weewx-$(date +%T).sql echo press enter to continue next line is dry run option first read answer sudo wee_import --import-config=/home/user/cumulus.conf #sudo wee_import --import-config=/home/user/cumulus.conf --dry-run echo "After running this then do this: UPDATE archive SET rain=0 WHERE ( rain > 700) ;" echo then run a drop daily and a rebuild daily On Wednesday, 2 January 2019 08:36:46 UTC+11, MikeQ wrote: > > I am moving over from Cumulus to weeWX both running on a RPi, both talking > to a VP2 Console, and both ftp'ing the generated web pages to my Web Server > on another box.. I had no problems getting weeWX running on the RPi with > the standard options. > > Now I am trying to import my old Cumulus data (going back to 2011) to the > SQLLite DB and causing myself much confusion. After several hours, I > believe I have the process squared away now, but I still have a couple of > questions that I am not sure about. Part of my confusion came from not > running wee-import as sudo initially and generating thousands of read-only > database errors in syslog. After figuring that out, I narrowed down what I > was trying to import and then using NOAA reports to verify that the data > was properly imported. This caused more confusion as some of the reports > were completely blank and some only had partial data even though it > appeared all the records had been imported to SQLLite without any errors. > > While reading another group post, I found that someone deleted their NOAA > files and let weeWX regenerate them. After doing the same thing on my RPi, > I fixed my missing NOAA report info issue. So that leaves my two questions: > > 1. I assumed (we all know that didn't go well) that weeWX would recognize > there was new info added to the DB and regenerate the previous NOAA > reports. Apparently though, those files are only generated if they are > missing. Is that correct? So if I wanted to regenerate the entire > /var/www/html/weewx directory, I could just delete the files from it and at > the next archive interval weeWX would regenerate it? > > 2. I also read in another post about importing Cumulus files in ascending > date order and running 'wee_database --drop-daily' if that was not done. In > reviewing wee_database I see there is also a --check option and a > --rebuild-daily option. Since I have been bouncing around chronologically > doing my imports (I thought there might be an issue with Cumulus v1.9.1 -> > v1.9.4 log files which I have), should I run one or more of the > wee_database options after my imports are completed to verify there are no > issues with the DB? Does weeWX need to be stopped when running > wee_database? > > Thanks > -- 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.
