Re: [weewx-user] No data to Weewx from VantageVue, but data to weather display

[Thomas Keffer]

Impossible to say without actually seeing the log. See the Wiki article *Help!
Posting to weewx-user
*.

-tk

On Tue, Nov 12, 2019 at 6:00 PM Dan Sealy  wrote:

> Hi,
>
> I'm new to this, and to Raspberry Pi.
>
> I'm trying to use Weewx and a RPi to generate a webpage with the station
> data.
>
> I tried using Weather Display console for RPi and it works fine. Data
> comes through and the screen updates.
>
> I want the flexibility of the different reports offered by Weewx.  I
> installed Weewx using the Debain install.  Everything went ok.
>
> The problem is that wehn I look at the system log using sudo tail -f
> /var/log/syslog it It just sits there waiting for data.
>
> I've checked the config file and it appears correct.  I've checked the
> baud rate and it matches.  The index file that is supposed to be available
> to view the station is not there.
>
> Any help is greatly appreciated.
>
>
> \
>
> --
> 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/31b895c6-14e4-43b4-b941-95abdeba6016%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zECEx_q%3DgZfjpwRf4E8nhU75-_XCZFSM%3DWw2oS9tGnLN_Q%40mail.gmail.com.

Re: [weewx-user] Sun & Moon sine plot/graph

[Xant]

Thank you Gary, as your feedback always appreciated.

Yes! That's the thinking... although I tweak here and there, and I'm not a 
programmer sort to say but hobbyist, and still searching for an "easy 
recipe" :P

Ideally, its something as the following for Sun/Mon:



In a veeery non-scientific way (I recognize), as sunrise/sunset most 
available, could [(sunrise + sunset)/2] to 'y= +1', [(sunrise(i+1) + 
sunset)/2] to 'y= -1' and "spline"... no sine perfection here, but a sun 
cycle graph sort to say.

Meanwhile, I'm playing with Belchertown skin and highcharts:



As winter almost here in upStateNY, the above shows freeze temp and 
Illuminance on top, so one can immediately verify day-time from visual. 

Tried to make right yAxis "invisible" as just to be "day-light", but not 
working somehow.

[[chart1]]
title = Temperature
type = spline
time_length = 9 # Last 25 hours
[[[outTemp]]]
zIndex = 1
type = areaspline
threshold = 32
negativeColor = '#A0A0A0'
[[[windchill]]]
[[[heatindex]]]
color = "#f7a35c"
[[[dewpoint]]]
name = Temperature
color = purple
yAxis_tickInterval = 8
yAxis_softMin = 32
[[[maxSolarRad]]]
name = Illuminance
yAxis = 1
color = "#f7f2b4"
yAxis_visible = false
observation_type = 120.0*maxSolarRad

Xant

-- 
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/34c11bf0-4fbf-40db-b98a-e7e6c9979cc6%40googlegroups.com.

[weewx-user] Re: Can't get rid of 'demo data' from weewx.sdb

[Alex Edwards]

Hi Gary,

Thanks for answering.  How embarrassing - yes, just needed to SHIFT+Refresh 
the web page.  I presumed the 'large' 450k weewx.sdb must be containing 
demo data each time it was created.  A bit surprised the demo images 
survived in the cache that long after some of the stuff I've been doing 
though.  It got me suspicious too when I realised they were 3 weeks old :) 

Cheers!

Alex

-- 
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/88ffbcee-387f-471d-8a6f-7546730c46a6%40googlegroups.com.

[weewx-user] Re: Can't get rid of 'demo data' from weewx.sdb

[Alex Edwards]

Hi Gary,

Thanks for answering.  How embarrassing - yes, just needed to SHIFT+Refresh 
the web page.  I presumed the 'large' 450k weewx.sdb must be containing 
demo data each time it was created.  A bit surprised the demo images 
survived in the cache that long after some of the stuff I've been doing 
though.  It got me suspicious too when I realised they were 3 weeks old :) 

Cheers!

Alex

-- 
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/09c92a4d-34b7-4afb-8927-cf80244f4b51%40googlegroups.com.
Nov 13 11:17:08 raspberrypi-zero weewx[18341]: engine: Initializing weewx 
version 3.9.2
Nov 13 11:17:08 raspberrypi-zero weewx[18341]: engine: Using Python 2.7.16 
(default, Apr  6 2019, 01:42:57) #012[GCC 8.2.0]
Nov 13 11:17:08 raspberrypi-zero weewx[18341]: engine: Platform 
Linux-4.19.58+-armv6l-with-debian-10.0
Nov 13 11:17:08 raspberrypi-zero weewx[18341]: engine: Locale is 'en_GB.UTF-8'
Nov 13 11:17:08 raspberrypi-zero weewx[18341]: engine: pid file is 
/var/run/weewx.pid
Nov 13 11:17:09 raspberrypi-zero weewx[18345]: engine: Using configuration file 
/home/weewx/weewx.conf
Nov 13 11:17:09 raspberrypi-zero weewx[18345]: engine: Loading station type 
FineOffsetUSB (weewx.drivers.fousb)
Nov 13 11:17:09 raspberrypi-zero weewx[18345]: fousb: driver version is 1.10
Nov 13 11:17:09 raspberrypi-zero weewx[18345]: fousb: polling mode is PERIODIC
Nov 13 11:17:09 raspberrypi-zero weewx[18345]: fousb: polling interval is 60
Nov 13 11:17:09 raspberrypi-zero weewx[18345]: fousb: found station on USB bus= 
device=
Nov 13 11:17:09 raspberrypi-zero weewx[18345]: engine: StdConvert target unit 
is 0x11
Nov 13 11:17:09 raspberrypi-zero weewx[18345]: wxcalculate: The following 
values will be calculated: barometer=prefer_hardware, 
windchill=prefer_hardware, dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, heatindex=prefer_hardware, 
maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Nov 13 11:17:09 raspberrypi-zero weewx[18345]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Nov 13 11:17:09 raspberrypi-zero weewx[18345]: engine: Archive will use data 
binding wx_binding
Nov 13 11:17:09 raspberrypi-zero weewx[18345]: engine: Record generation will 
be attempted in 'hardware'
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: engine: Using archive interval 
of 1800 seconds (specified by hardware)
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: manager: Created and initialized 
table 'archive' in database 'weewx.sdb'
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: manager: Created daily summary 
tables
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: manager: Starting backfill of 
daily summaries
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: restx: StationRegistry: 
Registration not requested.
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: restx: Wunderground: Posting not 
enabled.
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: restx: PWSweather: Posting not 
enabled.
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: restx: CWOP: Posting not enabled.
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: restx: WOW: Posting not enabled.
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: restx: AWEKAS: Posting not 
enabled.
Nov 13 11:17:10 raspberrypi-zero weewx[18345]: engine: Starting up weewx 
version 3.9.2
Nov 13 11:17:11 raspberrypi-zero weewx[18345]: fousb: synchronising to the 
weather station (quality=0)
Nov 13 11:18:13 raspberrypi-zero weewx[18345]: fousb: unstable read: blocks 
differ for ptr 0x0002e0
Nov 13 11:19:02 raspberrypi-zero weewx[18345]: manager: Added record 2019-11-12 
20:13:46 NZDT (1573542826) to database 'weewx.sdb'
Nov 13 11:19:02 raspberrypi-zero weewx[18345]: manager: Added record 2019-11-12 
20:13:46 NZDT (1573542826) to daily summary in 'weewx.sdb'
Nov 13 11:19:03 raspberrypi-zero weewx[18345]: manager: Added record 2019-11-12 
20:43:46 NZDT (1573544626) to database 'weewx.sdb'
Nov 13 11:19:03 raspberrypi-zero weewx[18345]: manager: Added record 2019-11-12 
20:43:46 NZDT (1573544626) to daily summary in 'weewx.sdb'
Nov 13 11:19:03 raspberrypi-zero weewx[18345]: manager: Added record 2019-11-12 
21:13:46 NZDT (1573546426) to database 'weewx.sdb'
Nov 13 11:19:03 raspberrypi-zero weewx[18345]: manager: Added record 2019-11-12 
21:13:46 NZDT (1573546426) to daily summary in 'weewx.sdb'
Nov 13 11:19:03 raspberrypi-zero weewx[18345]: manager: Added record 2019-11-12 
21:43:46 NZDT (1573548226) to database 'weewx.sdb'
Nov 13 

Re: [weewx-user] weewx.sdb backups revisited

[Greg Troxel]

WindnFog  writes:

> Reading the list archive, the documentation, and searching the Internet 
> about the "best" way to backup SQLite databases, I conclude cold backups 
> are safer than a "hot" cp or rsync. That said, I am doing a hot rsync 
> (takes 2-3 seconds) to another LAN system and a cloud server at 01:18 AM 
> daily. Since I only write archive records to the database at XX:00, XX:05, 
> XX:10, etc., I *think* this is safe. The documentation says:

Not to contradict the advice you've gotten which all seems great, but
you can also do

sqlite3 weewx.sdb .dump > weewxdb.txt

which gets you a text representation that was extracted with database
commands and thus should be ok (fully in a before or after state with
respect to a database transaction) even with concurrent access.  You
would then back up that file.  This scheme is common with the postgresql
world, as I understand it.

-- 
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/rmi1ruddoh3.fsf%40s1.lexort.com.

[weewx-user] Re: weewx.sdb backups revisited

[vince]

On Tuesday, November 12, 2019 at 7:48:21 AM UTC-8, WindnFog wrote:
>
> What are you guys doing vis-à-vis weewx.sdb backups?
>
>
>
>  
The long discussions in the list from a couple years ago were far too 
detailed (and good) to repeat from memory.

FWIW, I've been doing the same thing for many many years.  My repo is at 
https://github.com/vinceskahan/vds-weewx-backup-data if you want to see my 
script.

In short my process is:

   - copy weewx.sdb to a scratch directory, then gzip the 'copy'.
   - scp the file weekly (manually) to my Macbook, which syncs to the cloud 
   into Dropbox
   - I 'have' verified hundreds of daily stashed backups and they're all 
   good, for my case (spinning disk, not a pi with SD card)

The sqlite3 incantation to check your backup is ok is at 
https://serverfault.com/questions/8048/how-can-i-verify-that-a-sqlite-db3-file-is-valid-consistent

-- 
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/9b38a70d-4c9c-4736-915a-1168f64e384a%40googlegroups.com.

Re: [weewx-user] weewx.sdb backups revisited

[Paul Dunphy]

Thanks,Tom!  I'm not doing anything out of the ordinary, so I shall keep 
doing what I've been doing.


Take care, Paul VE1DX

On 2019-11-12 12:12 p.m., Thomas Keffer wrote:
Unless you are running some unusual service, there should be no 
situations where weewx is modifying the database between archive events.


-tk

On Tue, Nov 12, 2019 at 7:48 AM WindnFog > wrote:


Reading the list archive, the documentation, and searching the
Internet about the "best" way to backup SQLite databases, I
conclude cold backups are safer than a "hot" cp or rsync. That
said, I am doing a hot rsync (takes 2-3 seconds) to another LAN
system and a cloud server at 01:18 AM daily. Since I only write
archive records to the database at XX:00, XX:05, XX:10, etc., I
*think* this is safe. The documentation says:


"Do not make a copy of the SQLite database while in the middle of
a transaction! Schedule the backup for immediately after an
archive record is written, and then make sure the backup completes
before the next archive record arrives. Alternatively, stop WeeWX,
perform the backup, then restart WeeWX."


I prefer not to stop/start weewx every day, but I will if
necessary. Are their situations where some part of weewx could be
modifying the database between the archive writes every 5 minutes?
I have done a couple of restores over the past 4-5 years with no
issues, but am I playing with fire?


What are you guys doing vis-à-vis weewx.sdb backups?


- Paul VE1DX

-- 
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/dc168739-054a-4b6d-950c-6e9aa7f83e74%40googlegroups.com

.

--
You received this message because you are subscribed to a topic in the 
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/UWHHpwkoVJ8/unsubscribe.
To unsubscribe from this group and all its topics, 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/CAPq0zECs61uvq5%3DGKJUbTtcPjyPAKWB0L9LpNgzGZooornCW_A%40mail.gmail.com 
.


--
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/fea87b44-d49a-728f-df71-fedefd4c1cbf%40gmail.com.

Re: [weewx-user] weewx.sdb backups revisited

[Thomas Keffer]

Unless you are running some unusual service, there should be no situations
where weewx is modifying the database between archive events.

-tk

On Tue, Nov 12, 2019 at 7:48 AM WindnFog  wrote:

> Reading the list archive, the documentation, and searching the Internet
> about the "best" way to backup SQLite databases, I conclude cold backups
> are safer than a "hot" cp or rsync. That said, I am doing a hot rsync
> (takes 2-3 seconds) to another LAN system and a cloud server at 01:18 AM
> daily. Since I only write archive records to the database at XX:00, XX:05,
> XX:10, etc., I *think* this is safe. The documentation says:
>
>
> "Do not make a copy of the SQLite database while in the middle of a
> transaction! Schedule the backup for immediately after an archive record is
> written, and then make sure the backup completes before the next archive
> record arrives. Alternatively, stop WeeWX, perform the backup, then restart
> WeeWX."
>
>
> I prefer not to stop/start weewx every day, but I will if necessary. Are
> their situations where some part of weewx could be modifying the database
> between the archive writes every 5 minutes? I have done a couple of
> restores over the past 4-5 years with no issues, but am I playing with
> fire?
>
>
> What are you guys doing vis-à-vis weewx.sdb backups?
>
>
> - Paul VE1DX
>
> --
> 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/dc168739-054a-4b6d-950c-6e9aa7f83e74%40googlegroups.com
> 
> .
>

-- 
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/CAPq0zECs61uvq5%3DGKJUbTtcPjyPAKWB0L9LpNgzGZooornCW_A%40mail.gmail.com.

[weewx-user] weewx.sdb backups revisited

[WindnFog]

Reading the list archive, the documentation, and searching the Internet 
about the "best" way to backup SQLite databases, I conclude cold backups 
are safer than a "hot" cp or rsync. That said, I am doing a hot rsync 
(takes 2-3 seconds) to another LAN system and a cloud server at 01:18 AM 
daily. Since I only write archive records to the database at XX:00, XX:05, 
XX:10, etc., I *think* this is safe. The documentation says:


"Do not make a copy of the SQLite database while in the middle of a 
transaction! Schedule the backup for immediately after an archive record is 
written, and then make sure the backup completes before the next archive 
record arrives. Alternatively, stop WeeWX, perform the backup, then restart 
WeeWX."


I prefer not to stop/start weewx every day, but I will if necessary. Are 
their situations where some part of weewx could be modifying the database 
between the archive writes every 5 minutes? I have done a couple of 
restores over the past 4-5 years with no issues, but am I playing with 
fire? 


What are you guys doing vis-à-vis weewx.sdb backups?


- Paul VE1DX

-- 
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/dc168739-054a-4b6d-950c-6e9aa7f83e74%40googlegroups.com.

[weewx-user] Can't get rid of 'demo data' from weewx.sdb

[gjr80]

Hi,

Have you cleared the cache on your browser? If not try that, if you have and 
the problem persists and WeeWX restarts with the same simulated data then 
almost certainly the database file was not deleted. Which file are you 
deleting? It should be /home/weewx/archive/weewx.sdb. I suggest you stop WeeWX, 
delete the file, verify it was deleted by displaying the contents of 
/home/weewx/archive and then restart WeeWX. If the problem persists post a copy 
of the WeeWX startup log from when you restarted WeeWX through until at least 
one archive record is saved to database.

Gary

-- 
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/a7d0eae3-c8b8-4722-a5fc-8130bd349210%40googlegroups.com.

[weewx-user] Re: wee_import PWS station not found.

[George Anestopoulos]

Hi Gary, 

No worries. 

I will wait until the release of 4.0 . 

My task is to import all historical Data from WU to my new weewx 
installation. 


Regards

On Tuesday, November 12, 2019 at 9:56:53 AM UTC, gjr80 wrote:
>
> George,
>
> Perhaps I have misunderstood you, but if you intend using 4.0 wee_import 
> now I  would advise against it as wee_import needs to be verified against 
> some recent changes elsewhere in the 4.0 code base. I will post here the 
> instructions for use of the 4.0 wee_import once I have completed the 
> verification.
>
> Gary
>
>

-- 
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/e0f652b9-6bfa-4f7c-9d6a-f2a9a8362e59%40googlegroups.com.

[weewx-user] Re: wee_import PWS station not found.

[gjr80]

George,

Perhaps I have misunderstood you, but if you intend using 4.0 wee_import now I  
would advise against it as wee_import needs to be verified against some recent 
changes elsewhere in the 4.0 code base. I will post here the instructions for 
use of the 4.0 wee_import once I have completed the verification.

Gary

-- 
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/87ad8ae7-6158-4204-b5ab-51f01838c3e6%40googlegroups.com.

[weewx-user] Can't get rid of 'demo data' from weewx.sdb

[Alex Edwards]

Hi all,

I've previously setup my FineOffset station on a raspberry Pi, using the 
pre-made package which worked fine.

I'm trying to set it up on another Pi, using the 'developer's setup.py' 
weewx 3.9.2 I believe.

However, whenever I delete the weewx.sdb , restarting weewxd (or 
weewx_database) recreates the ~2 months of demo data - with all the sine 
waves etc.

I presumed this data was being generated by the Simulator (?)  but my 
weewx.conf has no mention of that.  I've tried investigating code, config 
and docs and can't find anything obvious.

How can I stop this data being created and have a clean start to my data?  
I guess I could just delete the data in the database, but I'd like to do it 
'properly'.

Attached files of the example 'demo data' reports and my weewx.conf.

Thanks

Alex

-- 
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/f0cd1a38-4051-4d53-86b3-f195a28499ce%40googlegroups.com.
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /home/weewx

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.9.2

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Waitangi, New Zealand"

# Latitude and longitude in decimal degrees
latitude = -35.258423
longitude = 174.070621

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 68, meter

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be used.
station_type = FineOffsetUSB

# If you have a website, you may specify an URL
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[FineOffsetUSB]
# This section is for the Fine Offset series of weather stations.

# The station model, e.g., WH1080, WS1090, WS2080, WH3081
model = WS2080

# How often to poll the station for data, in seconds
polling_interval = 60

# The driver to use:
driver = weewx.drivers.fousb

##

#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = false

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
# To guard against parsing errors, put the password in quotes.
enable = false
username = replace_me
password = replace_me

[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = false
station = replace_me

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
#passcode = replace_me (APRS stations only)

[[PWSweather]]
# This section is for configuring posts to PWSweather.com.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
# To guard against parsing errors, put the password in quotes.
enable = false
station = replace_me
password = replace_me

[[WOW]]
# This section is for configuring posts to WOW.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
# To guard against parsing 

[weewx-user] Re: wee_import PWS station not found.

[George Anestopoulos]

Hi Gary, 

Thank you for your update. 

I will try to use the 4.0 import utility under the existing 3.0 
installation.


Thank you very much .

On Tuesday, November 12, 2019 at 9:18:54 AM UTC, gjr80 wrote:
>
> I have made the necessary changes to the 4.0 release wee_import to fix 
> this issue; however, I still have a few more checks to do before it can be 
> used. Unfortunately other things have limited the time I have had available 
> for wee_import development lately. I will let Tom speak for when 4.0 
> might be released, though I do have a means by which the 4.0 wee_import 
> utility can be used under an existing 3.x install without interfering with 
> the existing 3.x install. So the release of 4.0 is not the limiting factor 
> here, rather it is me finishing up with wee_import. Should be this week 
> but I can't promise that.
>
> I am not a Weatherlink user so I can't comment on any other means of 
> importing Weatherlink data,
>
> Gary 
>
> On Tuesday, 12 November 2019 02:18:38 UTC+10, George Anestopoulos wrote:
>>
>> Hi all, 
>>
>> I'm new to weewx, I have moved from weatherlink to weewx, but I cannot 
>> import my historical data because of the same error. 
>>
>> Is any Estimate when 4.0 version will come out? 
>>
>> Is any other way to import my data from weatherlink?
>>
>> Thanks.
>>
>> On Friday, August 30, 2019 at 4:20:13 PM UTC+1, Clint Parrish wrote:
>>>
>>> I’m having a problem importing records from WU.  I have over 11 years of 
>>> records that I want to combine into my weewx.sdb. 
>>>
>>> I have entered my nine digit PWS ID into my config file and get the 
>>> following when I run wee_import: 
>>>
>>> wee_import --config=/etc/weewx/weewx.conf 
>>> --import-config=/var/tmp/wu.conf --from=2019-08-29 --to=2019-08-30 
>>> --dry-run 
>>> Starting wee_import... 
>>> Observation history for Weather Underground station 'KILSULLI1' will be 
>>> imported. 
>>> Using database binding 'wx_binding', which is bound to database 
>>> 'weewx.sdb' 
>>> Destination table 'archive' unit system is '0x01' (US). 
>>> Missing derived observations will be calculated. 
>>> Observations timestamped after 2019-08-29 00:00:00 CDT (1567054800) and 
>>> up to and 
>>> including 2019-08-31 00:00:00 CDT (1567227600) will be imported. 
>>> This is a dry run, imported data will not be saved to archive. 
>>> Unable to open Weather Underground station KILSULLI1 
>>>  
>>>  Unable to load config file. 
>>>   
>>>  Nothing done, exiting. 
>>>
>>> Could somebody please help?  Thanks! 
>>>
>>> Clint
>>
>>

-- 
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/828c6a30-ed26-4e1b-bd48-77965dea373f%40googlegroups.com.

[weewx-user] Re: wee_import PWS station not found.

[gjr80]

I have made the necessary changes to the 4.0 release wee_import to fix this 
issue; however, I still have a few more checks to do before it can be used. 
Unfortunately other things have limited the time I have had available for 
wee_import development lately. I will let Tom speak for when 4.0 might be 
released, though I do have a means by which the 4.0 wee_import utility can 
be used under an existing 3.x install without interfering with the existing 
3.x install. So the release of 4.0 is not the limiting factor here, rather 
it is me finishing up with wee_import. Should be this week but I can't 
promise that.

I am not a Weatherlink user so I can't comment on any other means of 
importing Weatherlink data,

Gary 

On Tuesday, 12 November 2019 02:18:38 UTC+10, George Anestopoulos wrote:
>
> Hi all, 
>
> I'm new to weewx, I have moved from weatherlink to weewx, but I cannot 
> import my historical data because of the same error. 
>
> Is any Estimate when 4.0 version will come out? 
>
> Is any other way to import my data from weatherlink?
>
> Thanks.
>
> On Friday, August 30, 2019 at 4:20:13 PM UTC+1, Clint Parrish wrote:
>>
>> I’m having a problem importing records from WU.  I have over 11 years of 
>> records that I want to combine into my weewx.sdb. 
>>
>> I have entered my nine digit PWS ID into my config file and get the 
>> following when I run wee_import: 
>>
>> wee_import --config=/etc/weewx/weewx.conf 
>> --import-config=/var/tmp/wu.conf --from=2019-08-29 --to=2019-08-30 
>> --dry-run 
>> Starting wee_import... 
>> Observation history for Weather Underground station 'KILSULLI1' will be 
>> imported. 
>> Using database binding 'wx_binding', which is bound to database 
>> 'weewx.sdb' 
>> Destination table 'archive' unit system is '0x01' (US). 
>> Missing derived observations will be calculated. 
>> Observations timestamped after 2019-08-29 00:00:00 CDT (1567054800) and 
>> up to and 
>> including 2019-08-31 00:00:00 CDT (1567227600) will be imported. 
>> This is a dry run, imported data will not be saved to archive. 
>> Unable to open Weather Underground station KILSULLI1 
>>  
>>  Unable to load config file. 
>>   
>>  Nothing done, exiting. 
>>
>> Could somebody please help?  Thanks! 
>>
>> Clint
>
>

-- 
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/54b04b89-2904-4413-abbe-0d99900f669d%40googlegroups.com.

Re: [weewx-user] Sun & Moon sine plot/graph

[gjr80]

Agree that if you are using the WeeWX plot engine you have to archive the 
data you wish to plot; however, if you use something other than the WeeWX 
plot engine to render your plots then you can avoid archiving the data. I 
played around with a sun position plot routine in some php a few years ago 
to produce a graphic file showing a plot of solar altitude through the day 
with the current sun position highlighted. Whilst the details escape me 
(whilst I had it working I never actually deployed it) I believe I used 
WeeWX to produce a report with time and solar altitude data for the day. 
This report was produced one per day at midnight for the coming day. The 
php routine then read this data and generated the plot. A similar thing 
could be done with a json format data file and highcharts or some other 
plot library.

Developing the report will take a little thought, It could be done with 
some inline python code in a template or via a SLE to do the hard work and 
a basic template (SLE would probably be a little easier to deal with 
setting up pyephem). The report timing option provides the means to control 
when the report is produced.

Gary

-- 
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/007eae59-610e-4d80-b05e-21d8d8922d65%40googlegroups.com.