Re: [weewx-user] Re: Version 3.6.0 hits the streets

I must confess that initially the use of --date or --to and/or --from and the use of the "T" struck me as complicated and not very intuitive. As far as I am aware wee_import and wunderfixer are the only utilities that use a date or date-time parameter (wee_reports accepts a timestamp), though I

Re: [weewx-user] Re: Version 3.6.0 hits the streets

For separating date and time, one strategy I've seen is to use a "T". Then you don't need the quotes. So, a date range would be: --date=2016/09/28T03:00-2016/10/02T12:00 But I can see another issue. wunderfixer uses a different format: --date=-mm-DD Personally, I prefer this to /mm/DD

Re: [weewx-user] Re: Version 3.6.0 hits the streets

On Saturday, October 8, 2016 at 1:46:03 AM UTC-4, gjr80 wrote: > > >> >> Oh yes - somewhere in the instructions (or help, not sure which) - the >> time in the --date command is in brackets. I presume this is because the >> time is optional - but why the brackets? An option in syntax defini

[weewx-user] Re: Version 3.6.0 hits the streets

On Saturday, October 8, 2016 at 7:05:51 AM UTC-4, Peter_F wrote: > > Thanks Tom, Matthew and Gary, > I upgraded without any issues. One thing I noticed though is that the > Weather Underground RapidFire rest posts are now logged by default. I > added 'log_success = False' to my weewx.conf to di

[weewx-user] Re: Version 3.6.0 hits the streets

Thanks Tom, Matthew and Gary, I upgraded without any issues. One thing I noticed though is that the Weather Underground RapidFire rest posts are now logged by default. I added 'log_success = False' to my weewx.conf to disable it. I have a Davis VantagePro 2 and it was logging these every coup

Re: [weewx-user] Re: Version 3.6.0 hits the streets

Just seen an 'oddity' . accessing the rpi via ssh from windows via putty when the window is small I get two lines per period ... one line for first tranche of 250 records with last timestamp date and time one line for remaining records of period with last timestamp date and time In full scree

Re: [weewx-user] Re: Version 3.6.0 hits the streets

Square brackets perhaps?? For some reason the round brackets looks as though they should be included (to sill me at least)!! This may be helpful . http://pcsupport.about.com/od/commandlinereference/a/command-syntax.htm no doubt there is a definition for python somewhere too On Saturda

Re: [weewx-user] Re: Version 3.6.0 hits the streets

> > Oh yes - somewhere in the instructions (or help, not sure which) - the > time in the --date command is in brackets. I presume this is because the > time is optional - but why the brackets? An option in syntax definitions > is (I thought) indicated by | whilst the inclusion of brackets i

Re: [weewx-user] Re: Version 3.6.0 hits the streets

Gary My big bad OK - an import of 20 months is back under way . let's see if the result is better than last time as qc is now invoked!! Andrew phew good job this is just a test system I do wish we would go back to using the word 'bad' as an adjective rather than a noun!

Re: [weewx-user] Re: Version 3.6.0 hits the streets

Ok, that is a mess. Have another read at the dot point instructions I provided. On 8 October 2016 at 07:37, gjr80 > wrote: > Andrew, >> >> My bad, wee_import was being told to write to a US database irrespective >> of the underlying database units, the QC department is being fired as I >> wri

Re: [weewx-user] Re: Version 3.6.0 hits the streets

Gary I hasve got into a total mess now getting errors all over the place After the 3.6 instasll I had a file called wee_import in /bin which I renamed to wee_import.orig and moved the new wee_import.py in its place. THEN I saw there is also a weeimport directory, which contains wee_import.py

[weewx-user] Re: Version 3.6.0 hits the streets

Andrew, My bad, wee_import was being told to write to a US database irrespective of the underlying database units, the QC department is being fired as I write this. The attached weeimport.py should fix the issue, usual deal: - move the original weewx/bin/weeimport/weeimport.py aside by re

[weewx-user] Re: Version 3.6.0 hits the streets

Andrew, My bad, wee_import was being told to write to a US database irrespective of the underlying database units, the QC department is being fired as I write this. The attached weeimport.py should fix the issue, usual deal: - move the original weewx/bin/weeimport/weeimport.py aside by renam

[weewx-user] Re: Version 3.6.0 hits the streets

. not quite perfect .. Just upgraded, and thought I would correct some errors from a previous import by using wee_import from WU with full qc checking - as available in the now standard wee_import. Created a wuimport.conf, and modified the qc section of weewx.conf The --dry-run proceede

[weewx-user] Re: Version 3.6.0 hits the streets

. not quite perfect .. Just upgraded, and thought I would correct some errors from a previous import by using wee_import from WU with full qc checking - as available in the now standard wee_import. Created a wuimport.conf, and modified the qc section of weewx.conf went to do the import

[weewx-user] Re: Version 3.6.0 hits the streets

On Friday, October 7, 2016 at 5:12:02 PM UTC-7, Tom Keffer wrote: > > With this release we have rearranged the User's Guide, and broken out the > hardware-specific information into its own Hardware Guide > . > > > upgraded (debian setup.py method) from 3.5.