[weewx-user] Re: Porting data from WVIEW

2019-08-01 Thread Andrew Milner
the simplest thing is to install sqlite3 https://sqlite.org/cli.html and give a command such as sqlite3 fullpathtosdbfile then select * from archive order by dateTime desc limit 10; should give you the last 10 entries On Thursday, 1 August 2019 15:19:49 UTC+3, Richard Rosa wrote: > > What

[weewx-user] Re: Porting data from WVIEW

2019-08-01 Thread Richard Rosa
What the manual says and what is available on my system don't quite jive. The ONLY wview-archive.sdb that I can find was last updated 5 years ago. It has been running for the past 5 years WITHOUT generating this file. Unless the file has been rendered invisible, it does NOT exist on my current

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Graham Eddy
The NOAA files contain data only of interest to US govt so miss extra sensors etc _ Graham Eddy via phone: forgive brevity On Thu, 1 Aug. 2019, 8:31 am Richard Rosa, wrote: > It looks like I have an alternative: > > Thankfully, WVIEW saved a bunch of .txt files for every logged

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Graham Eddy
It is wview-archive.sdb. The other dbs are generated from wview-archive.sdb if absent. wview cannot run without wview-archive.sdb. If absent from backups, the backups were not done correctly (from phone -> forgive brevity) GE On Thu, 1 Aug. 2019, 5:28 am Thomas Keffer, wrote: > Take a look at

[weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Andrew Milner
I don't think you have an alternative, you have something different. >From wview manual: *Day history Table (wview-history.sdb)* *Overview* This table is generated internally by wview to avoid having to compute the daily summary records used for the yearly charts every time wview starts. This

[weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread vince
On Wednesday, July 31, 2019 at 3:31:01 PM UTC-7, Richard Rosa wrote: > > It looks like I have an alternative: > > Thankfully, WVIEW saved a bunch of .txt files for every logged day > (almost 4k). Although I know very little about SQL databases, I am pretty > decent at converting text file

[weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Richard Rosa
It looks like I have an alternative: Thankfully, WVIEW saved a bunch of .txt files for every logged day (almost 4k). Although I know very little about SQL databases, I am pretty decent at converting text file formats to CSV files. I picked the OLDEST text file, created a script to convert

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Thomas Keffer
Take a look at chapter 7 of the wview users guide ( http://www.wviewweather.com/release-notes/wview-User-Manual.html#Advanced-wlk ). I'm pretty sure it's called wview-archive.sdb. Or, ask Graham Eddy. On Wed, Jul 31, 2019 at 2:46 PM Richard Rosa wrote: > > There is NO current

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Richard Rosa
There is NO current *wview-archive.sdb*. I only have one from an old backup from 5 years ago. Recent archive database files are *wview-hilow.sdb* and *wview-history.sdb*. Richard Rosa On Wednesday, July 31, 2019 at 2:34:17 PM UTC-4, Thomas Keffer wrote: > > I believe you copied the wrong

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Thomas Keffer
I believe you copied the wrong file. You want wview-archive.sdb. I'm on an iPhone right now, so it's hard for me to give any more details. On Wed, Jul 31, 2019 at 12:46 PM vince wrote: > On Wednesday, July 31, 2019 at 8:54:03 AM UTC-7, gjr80 wrote: >> >> Hmmm, seems your wview database is

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread vince
On Wednesday, July 31, 2019 at 8:54:03 AM UTC-7, gjr80 wrote: > > Hmmm, seems your wview database is indeed different. You might need some > input from Tom or another wview user. I was under the impression the wview > database contained a table named ‘archive’ that is identical in structure >

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Richard Rosa
Looking through some old backups, it seems that there WAS a* wview-archive* file from about five years ago. It would appear that there was a format change (at least in the version I was running) around the beginning of 2015. The two .sdb files that I have that were updated recently (the last

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread gjr80
Hmmm, seems your wview database is indeed different. You might need some input from Tom or another wview user. I was under the impression the wview database contained a table named ‘archive’ that is identical in structure to the archive table in the WeeWX database. Many wview users have changed

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Richard Rosa
Almost the exact procedure followed. Not that it should matter, /var/lib/weewx is symlinked to a different location (to make backups a bit easier). A Config file change also sets SQLITE_ROOT to that location as well. Retrying again (with wee_debug before start) Commands issued (as root):

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread gjr80
Ok, so wee_ debug says there is only 54 odd days of data in your archive, expect these records are the history downloaded from the logger. So we are not going to get any reports using your historical wview data from that database. Not convinced this a schema issue. Just to step back a bit,

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Richard Rosa
Debug file attached. Ran : * wee_database --drop-daily wee_database --rebuild-daily* Again, removed all generated files. Waited for reports to be generated. Same issue. No data except what is stored in the Davis Vantage Pro. I'm pretty sure the issue is that the database 'schema' used by

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread vince
On Wednesday, July 31, 2019 at 2:29:49 AM UTC-7, Richard Rosa wrote: > > > > > *sqlite3 wview-history.sdb SQLite version 3.28.0 2019-04-16 19:49:53Enter > ".help" for usage hints.sqlite> .schemaCREATE TABLE **dayHistory** ( date > INTEGER ,barometer REAL ,pressure REAL ,altimeter REAL ,inTemp

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread gjr80
Ok, a couple of more things to do/try. First run wee_debug and post the output here. Just make sure you check the wee_debug output for any sensitive info such as user names, passwords, keys etc before posting; wee_debug should obfuscate such info but it’s not perfect. The wee_debug report

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Richard Rosa
Ran *wee_database --rebuild-daily.* Deleted ALL generated reports. Started the service. Waited one hour for reports to appear. Still only a few weeks of info (what is stored in the Davis). The data from WVIEW is NOT being processed.. Richard Rosa. On Wednesday, July 31, 2019 at 6:40:23 AM

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread gjr80
If just copying and renaming the archive database then you likely need to build/rebuild the daily summaries using wee_database (http://weewx.com/docs/utilities.htm#wee_database utility). Once done don't forget to delete all NOAA format reports to force generation of the older reports. Gary

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-31 Thread Richard Rosa
To be on the safe side, I decided NOT to change the interval (at least for now). I started WEEWX using the weewxd command (rather than the SYSTEMD service) and let it run for about 2 hours. At the end of the two hours I have reports for the past month and a half of data, but no more. My

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-30 Thread Graham Eddy
i did this about 6 months ago with 12 years of wview data, “this” being copying wview db into weewx space and changing vp2’s interval from 30 mins to 5 mins. the old data on 30 mins archive interval freely mixes in reports with newer data on 5 min interval the only problem i struck was some

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-30 Thread vince
On Tuesday, July 30, 2019 at 5:23:58 PM UTC-7, Richard Rosa wrote: > > Is there any downside (or possible loss of data) with changing the > interval? I vaguely remember something in the WVIEW setup about changing > the interval would make for data incompatibility issues. I don't want to > lose

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-30 Thread Thomas Keffer
Your VP2 has an archive interval of one hour, so it will take that long to generate an archive record, and kick off a reporting cycle. If you want something more often, change the interval to, say, 5 minutes. See the section *Archive interval

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-30 Thread Richard Rosa
The main program IS running. How do I tell it to generate reports? When the program started, no reports were generated until the 'wee_reports' command was issued. System Log (journalctl): Jul 30 19:39:54 rubberducky.rbm systemd[1]: Started weewx weather system. Jul 30 19:39:54

Re: [weewx-user] Re: Porting data from WVIEW

2019-07-30 Thread Thomas Keffer
wee_reports is for generating reports only. It is a standalone program, mostly used for testing purposes. You want weewxd: the main weewx program. Take a look in the section *Running weewx * in the manual. If you still have questions, come on back,

[weewx-user] Re: Porting data from WVIEW

2019-07-30 Thread Richard Rosa
Other than NOT changing to MYSQL, those were the instructions I followed. Using *sqlitebrowser,* it appears that the records from WVIEW are in this file, but not being a DB expert, I'm not sure if they are in the right place. I DID set debug on, and follow the log messages (journalctl -f).

[weewx-user] Re: Porting data from WVIEW

2019-07-30 Thread vince
On Tuesday, July 30, 2019 at 2:04:43 PM UTC-7, Richard Rosa wrote: > The problem I have is porting 10+ years of WVIEW logs > Following the manual's instructions, I copied archive databases from > wview/archive -> weewx.sdb > you'd have to point us at which instructions you followed perhaps -