Does anyone know how previous data is stored in weewx. I recently upgraded to a new Pi4 and to weewx4.0. I dumped my old data to the new database. I still only show recent data in my reports.
thanks
Weewx only updates the reports periodically, so wait a while. If the data is in the database, it will find it and eventually add it to the reports.
(It so happens I just went through the same process within the last few days.)
It has been about a week.
Again, these kind of app-specific questions should likely go to the app’s preferred support forums (for this kind of question that’s the weewx-users google group)
I don’t know quite what ‘dumped my old data to’ means, but if you mean you dumped the ‘archive’ table and added those records, you need to rebuild the daily summaries.
Also not sure what ‘my reports’ you are referring to. If you mean the graphs and week/month/year pages that’s one thing. If you mean the NOAA reports that’s a different thing.
Impossible to answer given the skeletal problem description.
A week is more than enough time, I think. Some of my older data showed up in the charts the next day, and quite a bit of it is there after a few more days.
One thing that might be different between us is that I didn’t “dumped my old data to the new database”. I simply crossed my fingers and put a copy of the old weewx.sdb into the new spot.
thanks I tried that. and got all kinds of errors. So I used this:
echo “.dump” | sqlite3 weewx3.92.sdb | sed -e ‘s/^CREATE TABLE//’ > weewx3.92.sql
Took the .sql file modified it to import into the new table header and executed.
it ran and inserted all the data.
If you installed weewx v4 from scratch ‘and’ just copied the db from a v3 instance, what is happening is you have the new bigger ‘extended’ schema defined yet your data uses the older wview-compatible schema, so weewx likely will barf with a syslog message on startup due to that mismatch.
Simplest workaround is to run “wee_database --reconfigure” to have it update old=>new schema and save a new copy for you. Then run “wee_database --rebuild-daily” to rebuild the daily summary tables. It’s all in the weewx-users group archives. You should shop there. The people are nice 
Always (ALWAYS) posting snippets from your syslog help. Weewx definitely logged the mismatch when it tried to start. Really.
I’m not sure if you are literally replying to me or actually replying to @ronselljr. I copied my database (is in copied weewx.sdb from one machine to another), and I don’t see any evidence of the weewx complaint you mention. Things seem to be working fine.
Here’s what I see in syslog on startup (irrelevant lines omitted):
May 27 18:23:30 000611694f7e weewx[28] INFO __main__: Initializing weewx version 4.1.0
May 27 18:23:30 000611694f7e weewx[28] INFO __main__: Using Python 3.8.2 (default, Apr 27 2020, 15:53:34)
[GCC 9.3.0]
May 27 18:23:30 000611694f7e weewx[28] INFO __main__: Platform Linux-5.4.0-1008-raspi-aarch64-with-glibc2.29
May 27 18:23:30 000611694f7e weewx[28] INFO __main__: Locale is 'en_US.UTF-8'
May 27 18:23:30 000611694f7e weewx[28] INFO __main__: Using configuration file /home/weewx/weewx.conf
May 27 18:23:30 000611694f7e weewx[28] INFO __main__: Debug is 1
May 27 18:23:30 000611694f7e weewx[28] INFO weewx.engine: Archive will use data binding wx_binding
May 27 18:23:30 000611694f7e weewx[28] INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
May 27 18:23:30 000611694f7e weewx[28] INFO weewx.manager: Starting backfill of daily summaries
May 27 18:23:30 000611694f7e weewx[28] INFO weewx.engine: Starting main packet loop.I’ll be happy to answer any weewx-related questions in the proper weewx-users forum, as will hundreds of other folks. Nothing you’re mentioning has anything to do with WeatherFlow. Right question, wrong place to ask it.