Hi, The only way that something historical would be pulled from the console and placed in the archive would be if WeeWX was doing a catchup on startup, and then WeeWX would only catchup records timestamped after the most recent record in your archive and the catchup would only occur if your station had a logger/memory and supported a catchup. Catching up back to 2013 I would suggest is beyond all of the stations currently supported by WeeWX. Most likely what has happened is that the data appeared to be deleted but in fact it was not and when you subsequently made copies of your database you just copied a database that included the erroneous data.
I would suggest repeating the process this time screen capturing everything you do (and the responses as well). The broad process I would use is: 1. backup your database 2. query your database to find the erroneous data 3. run your update query to remove the erroneous data 4. query your database again to confirm you have indeed removed the erroneous data 5. if you wish make another backup/shuffle your databases 6. drop then rebuild your daily summaries (6.5 if really paranoid query your database again to confirm the erroneous data has been removed from the archive and the rain daily summary table archive_rain_day) 7. run wee_reports or start WeeWX normally and wait for the reports to be generated If the data is still there post all of your commands and the responses. Gary On Saturday, 4 April 2020 01:20:20 UTC+10, Muireadach O Connor wrote: > > Hi guys, > > I'm struggling to understand what I'm doing wrong here. > > I want to remove a daily reading of 134mm rain from February 2013 as its > bothering me in my records page. I had cleaned the rain gauge that day and > never got around to correcting it. > I'd previously amended a max rainRate figure from the database without too > much issue so thought this would be the same but its proving much more > troublesome. > > I removed it using : > > update archive set rain=NULL where rain > 4; (db in imperial) > > Next made a new copy of this new database > > Then.. > > sudo wee_database --drop-daily > sudo wee_database weewx.conf --rebuild-daily > > then ran : > > wee_reports --config=/etc/weewx/weewx.conf > > However the records webpage on my pi (reports folder) in still showed the > old value in there. > > At this stage I figured maybe its cached in memory so stopped the WeeWX > service and restarted the raspberry pi > > Now the old value is back in the database again (/shakes fist at cloud) > I've looked at my amended copy and the latest one and the old maximum > daily reading is definitely back and definitely was removed. > > I'm guessing this is being pulled from the console somehow, should I have > cleared it also there also before restarting? > If not, anyone any ideas how to fix this? > > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/5e1015fb-a912-459b-a14c-c7182b3d9302%40googlegroups.com.
