[weewx-user] weewx-sftp and delay in data displayed on the web

[Oscar Galvan Felez]

Hello

Let's see if someone can give me some idea of where to look for this small 
problem.

Pi OS Lite + new weewx installation (setup.py) + Belchertown skin + 
matthewwall sftp extension

I installed Apache and I can see the weewx website locally in my browser, 
the template is updated every 5 minutes and everything is correct!

The data is uploaded correctly every 5 minutes to the hosting (IONOS) but 
it takes another 5 minutes for the website to display the updated data, 
which means there is a 10-minute delay. 
Example: at 11:02 I see the data for 9:55, when the data for 11:00 has 
actually already been uploaded to the hosting. 

I spoke with my hosting and they told me everything was fine. 
In my old installation and uploading the data via FTP this did not happen 
to me. As of January 1, my hosting requires me to upload data via SFTP.

I don't have very extensive knowledge of Linux, I am a very basic user of 
following guides and learning. Any idea will be welcome. 

Thank you and Happy Holidays
Oscar Galvan

-- 
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/8db296b1-58c0-42c8-8e4e-87bcdc40bbffn%40googlegroups.com.

Re: [weewx-user] howto fix weewx sqlite database

[Oscar]

The database is corrupt.  Could be caused by a bad SD card, losing power 
during a write, a number of reasons.  I've been able to use this process to 
recover most of a corrupt data base.   With 5 years of data, the recreate 
process will take a long time (days(?)) on a pi.  I recommend coping the 
database to a faster machine to create the database, then copy it back to 
the pi.

# Dump the database as INSERT commands.  
sqlite3 weewx.sdb
.mode insert
.output dump_all.sql
.dump
.exit

# remove unwanted records from the dump file

cat dump_all.sql | grep -v TRANSACTION | grep -v ROLLBACK | grep -v COMMIT 
>dump_all_notrans.sql

# recreate the database using the insert statements.

sqlite3  new-weewx.sdb ".read dump_all_notrans.sql"

make a copy of your existing weewx.sdb file and  then copy new-weewx.sdb to 
weewx.sdb.  
 

On Monday, July 11, 2022 at 7:02:52 AM UTC-6 tke...@gmail.com wrote:

> It is very unlikely that the size of the database is a problem. Like 
> Graham, I have over 15 years of data on mine without a problem.
>
> You did not say what kind of storage you are using, but if it is an old SD 
> card, it is much more likely that the card is corrupt.
>
> You may be able to recover the database by using the utility sqlite3. 
>
> sqlite3 /home/weewx/archive/weewx.sdb
> sqlite> .recover
> sqlite> .quit
>
> However, usually this does not work, in which case you will have to 
> recover from a backup copy. Then, replace the card.
>
> -tk
>
>
> On Sun, Jul 10, 2022 at 10:27 AM Fische Namenlos  
> wrote:
>
>> here it is:
>> Sun Jul 10 19:25:39 2022 user.debug weewx[2812] DEBUG weewx.restx: Shut 
>> down StationRegistry thread.
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: Caught 
>> unrecoverable exception:
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   database disk image is malformed
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   Traceback (most recent call last):
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 214, in run
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   callback(event)
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 634, in check_loop
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   raise BreakLoop
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   weewx.engine.BreakLoop
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   During handling of the above exception, another exception occurred:
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   Traceback (most recent call last):
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewxd", line 153, in main
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   engine.run()
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 221, in run
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   callback(event)
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 644, in post_loop
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   self._software_catchup()
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 715, in 
>> _software_catchup
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD,
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 245, in dispatchEvent
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>   callback(event)
>> Sun Jul 10 19:25:39 2022 user.crit weewx[2812] CRITICAL __main__: 
>>

[weewx-user] Re: Problem Wunderground and Graph Wind Gust

[Oscar Galvan Felez]

Thanks Thomas for answer.

I try your solution and don't work, the graph show bad again. Only when I 
disable RapidaFire the graph look fine.

Others stations with 15-30 seconds refresh work fine the graph, I don't 
know if them have RapidFire enable, show other software not weewx.


El martes, 16 de abril de 2019, 20:53:29 (UTC+2), Oscar Galvan Felez 
escribió:
>
> Hello 
>
> I´m newbie, sorry for inconveniences!
>
> I have a problem with Wunderground graph "wind speed" and "wind gust", 
> generally the same values ​​appear and it is not true (into my Web 
> <http://oscargalvan.es/meteo/> the graph its ok)
> I don't know if problem is mine or the wunderground web (here my Station 
> <https://www.wunderground.com/dashboard/pws/IZARAGOZ138> into 
> wunderground)
>
> I have included an image of how the graph looks. Usually other stations 
> near from me show "orange dots" differentiated.
>
> Always I had "TRUE" the RapidFire function in weewx.conf , *now I 
> disabled this option for test*; but for me its very interesting know real 
> time wind and graph
>
> I read about "rtfreq" command for change update time from RapidFire but I 
> cannot change this update time (I try add into weewx.conf after line 
> "Rapid-fire = Enable", ... the update time its the same 2.5 seconds)
>
>
> My station:
> Davis Vantage Pro2 wireless
> Weewx 3.9.1
> Raspberry Pi 3 B+
>
> All log don't show any problem
>
> Other stations near from me, I see the update time its about 15-30 seconds 
> and wind graph show ok. (not David stations, not weewx software)
>
> Maybe this my problem but I don´t know how change this value refresh time 
> with RapidFire enable.
>
>
> Thanks
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Problem Wunderground and Graph Wind Gust

[Oscar Galvan Felez]

Hello 

I´m newbie, sorry for inconveniences!

I have a problem with Wunderground graph "wind speed" and "wind gust", 
generally the same values ​​appear and it is not true (into my Web 
 the graph its ok)
I don't know if problem is mine or the wunderground web (here my Station 
 into wunderground)

I have included an image of how the graph looks. Usually other stations 
near from me show "orange dots" differentiated.

Always I had "TRUE" the RapidFire function in weewx.conf , *now I disabled 
this option for test*; but for me its very interesting know real time wind 
and graph

I read about "rtfreq" command for change update time from RapidFire but I 
cannot change this update time (I try add into weewx.conf after line 
"Rapid-fire = Enable", ... the update time its the same 2.5 seconds)


My station:
Davis Vantage Pro2 wireless
Weewx 3.9.1
Raspberry Pi 3 B+

All log don't show any problem

Other stations near from me, I see the update time its about 15-30 seconds 
and wind graph show ok. (not David stations, not weewx software)

Maybe this my problem but I don´t know how change this value refresh time 
with RapidFire enable.


Thanks

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: launch of report thread aborted: existing report thread still running.

[Oscar]

Thanks Glen!

Sorry for the delay.  I thought I posted this yesterday.  

I found the issue with multiple copies of weewx running.  On another note, 
I removed systemd (Thanks!).  Time is set in rc.local.  The pi has an old 
time until rc.local runs.  Here is the current log.

Dec 31 17:00:20 zk30 weewx[1749]: engine: Initializing weewx version 3.7.1
Dec 31 17:00:20 zk30 weewx[1749]: engine: Using Python 2.7.13 (default, Jan 
19 2017, 14:48:08) #012[GCC 6.3.0 20170124]
Dec 31 17:00:20 zk30 weewx[1749]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-9.1
Dec 31 17:00:20 zk30 weewx[1749]: engine: Locale is 'C'
Dec 31 17:00:20 zk30 weewx[1749]: engine: pid file is 
/home/weewx/weewx/run/weewx.pid
Dec 31 17:00:20 zk30 weewx[2075]: engine: waiting for sane time.  current 
time is 1969-12-31 17:00:18 MST (18)
Oct 13 11:22:42 zk30 weewx[2075]: engine: Using configuration file 
/home/weewx/weewx/conf/weewx.conf
Oct 13 11:22:42 zk30 weewx[2075]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Oct 13 11:22:42 zk30 weewx[2075]: engine: StdConvert target unit is 0x1
Oct 13 11:22:42 zk30 weewx[2075]: 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
Oct 13 11:22:42 zk30 weewx[2075]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Oct 13 11:22:42 zk30 weewx[2075]: engine: Archive will use data binding 
wx_binding
Oct 13 11:22:42 zk30 weewx[2075]: engine: Record generation will be 
attempted in 'hardware'
Oct 13 11:22:42 zk30 weewx[2075]: engine: Using archive interval of 300 
seconds (specified by hardware)
Oct 13 11:22:42 zk30 weewx[2075]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
Oct 13 11:22:42 zk30 weewx[2075]: manager: Starting backfill of daily 
summaries


On Wednesday, October 11, 2017 at 3:05:33 PM UTC-6, Oscar wrote:
>
> Lost power the other day.  When power came back on, the error "launch of 
> report thread aborted:  existing report thread still running." was being 
> written to the log file every couple of seconds.  I restarted weewx and the 
> issue was resolved.  As a test, I disconnected power and the same issue 
> occurred.  I did a 'ps -ef | grep weewx' and one entry of weewxd was 
> displayed.  Is there an issue with an old PID file being read?  
>
> weewx version 3.7.1
> raspberry pi2
> 1,236,526 records in archive table
>
> Thanks,
> Oscar
>
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: launch of report thread aborted: existing report thread still running.

[Oscar]

Here are portions of the startup file.

Here is portions of the startup file.

# set the hardware clock
wait_for_time_set() {
   if [ ! -f /sys/class/i2c-adapter/i2c-1/new_device ]
   then
  echo "Setting Clock"
  echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-1/new_device
  hwclock -s
   fi
}


do_start() {
   # call proc to set the hardware clock
wait_for_time_set
NPROC=$(count_procs)
if [ $NPROC != 0 ]; then
return 1
fi
start-stop-daemon --start --chuid $WEEWX_USER --pidfile $PIDFILE --exec 
$DAEMON -- $DAEMON_ARGS || return 2
return 0
}


On Wednesday, October 11, 2017 at 3:05:33 PM UTC-6, Oscar wrote:
>
> Lost power the other day.  When power came back on, the error "launch of 
> report thread aborted:  existing report thread still running." was being 
> written to the log file every couple of seconds.  I restarted weewx and the 
> issue was resolved.  As a test, I disconnected power and the same issue 
> occurred.  I did a 'ps -ef | grep weewx' and one entry of weewxd was 
> displayed.  Is there an issue with an old PID file being read?  
>
> weewx version 3.7.1
> raspberry pi2
> 1,236,526 records in archive table
>
> Thanks,
> Oscar
>
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: launch of report thread aborted: existing report thread still running.

[Oscar]

e: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:33 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:33 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:33 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:33 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:34 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:34 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:34 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:34 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:34 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:34 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:34 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:34 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:34 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:34 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:34 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running
Oct 11 18:43:35 zk30 weewx[672]: engine: Launch of report thread aborted: 
existing report thread still running


On Wednesday, October 11, 2017 at 3:05:33 PM UTC-6, Oscar wrote:
>
> Lost power the other day.  When power came back on, the error "launch of 
> report thread aborted:  existing report thread still running." was being 
> written to the log file every couple of seconds.  I restarted weewx and the 
> issue was resolved.  As a test, I disconnected power and the same issue 
> occurred.  I did a 'ps -ef | grep weewx' and one entry of weewxd was 
> displayed.  Is there an issue with an old PID file being read?  
>
> weewx version 3.7.1
> raspberry pi2
> 1,236,526 records in archive table
>
> Thanks,
> Oscar
>
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] launch of report thread aborted: existing report thread still running.

[Oscar]

Lost power the other day.  When power came back on, the error "launch of 
report thread aborted:  existing report thread still running." was being 
written to the log file every couple of seconds.  I restarted weewx and the 
issue was resolved.  As a test, I disconnected power and the same issue 
occurred.  I did a 'ps -ef | grep weewx' and one entry of weewxd was 
displayed.  Is there an issue with an old PID file being read?  

weewx version 3.7.1
raspberry pi2
1,236,526 records in archive table

Thanks,
Oscar



-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx interceptor with acurite and raspberry not working.

[Oscar]

On Thursday, August 31, 2017 at 12:28:44 PM UTC-6, Eddie Lent wrote:
>
> I my set up is an acurite smarthub, a raspberry pi 1 running weewx and 
> weewx-interceptor in sniff mode, port mirroring using netgear GS105Ev2.  
>
> I can't seem to get data into weewx.
> I can run tcpdump on my router and see the packets. I can run tcpdump on 
> the raspberry pi and see packets.
>
> but I am not getting any data into weewx:
>
> from weewx.conf:
> [Interceptor]
> # This section is for the network traffic interceptor driver.
>
> # The driver to use:
> driver = user.interceptor
>
> # Specify the hardware device to capture.  Options include:
> #   acurite-bridge - acurite internet bridge
> #   observer - fine offset WH2600/HP1000/HP1003, aka 'observer'
> #   lw30x - oregon scientific LW301/LW302
> #   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
> device_type = acurite-bridge
> mode = sniff
> iface = eth0
> pcap_filter = src 192.168.5.230 and dst port 80
>
>
> pi@raspberrypiFB:~ $ tcpdump --version
> tcpdump version 4.9.0
> libpcap version 1.6.2
> OpenSSL 1.0.1t  3 May 2016
>
> If I run this line while I watch tcpdump on my router to ensure acurite 
> packets have been sent, I get nothing.
>
> pi@raspberrypiFB:~ $ sudo PYTHONPATH=/usr/share/weewx python 
> /usr/share/weewx/user/interceptor.py --device=acurite-bridge --mode=sniff 
> --iface=eth0 --filter="dst port 80"
> ^CTraceback (most recent call last):
>   File "/usr/share/weewx/user/interceptor.py", line 2060, in 
> _data = device.get_queue().get(True, 10)
>   File "/usr/lib/python2.7/Queue.py", line 177, in get
> self.not_empty.wait(remaining)
>   File "/usr/lib/python2.7/threading.py", line 359, in wait
> _sleep(delay)
> KeyboardInterrupt
> Exception in thread ServerThread (most likely raised during interpreter 
> shutdown):
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/threading.py", line 810, in __bootstrap_inner
>   File "/usr/lib/python2.7/threading.py", line 763, in run
>   File "/usr/share/weewx/user/interceptor.py", line 285, in run_server
>   File "/usr/share/weewx/user/interceptor.py", line 320, in run
>   File "/usr/lib/python2.7/dist-packages/pcap.py", line 116, in dispatch
> : 'NoneType' object has no attribute 
> 'pcapObject_dispatch'
>
>
> Here is a tcpdump run:
>
> pi@raspberrypiFB:~ $ sudo tcpdump  -U -i eth0 src 192.168.5.230 and port 80
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
> 14:12:28.859374 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [S], seq 241058131, 
> win 400, options [mss 536], length 0
> 14:12:28.887870 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [.], ack 912225648, 
> win 400, length 0
> 14:12:28.889708 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [P.], seq 0:80, ack 
> 1, win 400, length 80: HTTP: GET 
> /weatherstation/updateweatherstation?dateutc=now&action=updateraw&realtime=1[!http]
> 14:12:28.920267 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [P.], seq 80:122, ack 
> 1, win 400, length 42: HTTP
> 14:12:28.922539 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [P.], seq 122:149, 
> ack 1, win 400, length 27: HTTP
> 14:12:28.924796 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [P.], seq 149:160, 
> ack 1, win 400, length 11: HTTP
> 14:12:28.931672 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [P.], seq 160:196, 
> ack 1, win 400, length 36: HTTP
> 14:12:28.957005 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [P.], seq 80:196, ack 
> 1, win 400, length 116: HTTP
> 14:12:28.961918 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [P.], seq 196:213, 
> ack 1, win 400, length 17: HTTP
> 14:12:28.963793 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [P.], seq 213:254, 
> ack 1, win 400, length 41: HTTP
> 14:12:28.965296 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [P.], seq 254:277, 
> ack 1, win 400, length 23: HTTP
> 14:12:29.006661 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [.], ack 401, win 
> 400, length 0
> 14:12:29.032033 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [.], ack 413, win 
> 389, length 0
> 14:12:29.033168 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [.], ack 413, win 
> 400, length 0
> 14:12:29.034156 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [F.], seq 277, ack 
> 413, win 400, length 0
> 14:12:29.034827 IP Acurite.1978 > 
> ec2-52-22-110-201.compute-1.amazonaws.com.http: Flags [R.], seq 277, ack 
> 413, win 400, length 0
> ^C
> 16 packets captured
> 17 packets received by filter
> 0 pa

[weewx-user] Re: Create backup image of the running system

[Oscar]

I wrote this script to do an incremental backup of my running system.  Use 
at your own risk.

This script reads the weewx.sdb tables and insert/updates
records in a backup database.  It gets the last datetime from each of the 
weewx archive*
tables.  For the archive table, it inserts any new records in the backup
database.  For the archive_day_* tables, it deletes the last record in the  
backup database and then inserts any new records.
The exception is the archive_day__metadata table.  It is not touched.

I copied the weewx.sdb file to weewxCopy.sdb and then run the following to 
backup the database.  

zkwx_incrementCopy.py -f PATH_TO/weewx.sdb -t PATH_TO/weewxCopy.sdb

Good Luck,
Oscar

On Sunday, December 25, 2016 at 2:55:39 AM UTC-7, Per Edström wrote:
>
> I run my Weewx on Raspberry Pi and on a  "PC" (Ebox 3350 and Ubuntu 10). 
> Both have the OS on an SD/SDHC-card.
>
> Now, I find it messy to create a backup image:
> 1. Halt system
> 2. Power down
> 3. Remove SD-card
> 4. Put in laptop and create an image to file (5-10 min)
> 5. Insert SD-card in taget again and power up.
> 6. Write image file to new SD-card (15-20 min).
>
> (NB! I have noted that not all 16GB SD-card have the exact same size, it 
> varies quite a lot. This became an issue the trying to find a new SD-card 
> for the one that failed..)
>
> This procedure takes time and requires quite a lot of physical 
> intervention.
>
> Is there any way of to create or maintain an updated image from the 
> running system. Maybe it's Ok to just backup some files (user installed)?
>
> Also, it would be nice to have this "backup SD" as an alternative boot 
> SD-card in case the primary one fails. I don't know if that is possible..
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.
#!/usr/bin/python

# Filename:  zk_wx_incrementCopy.py
# Description:  This script eads the weewx.sdb tables and insert/updates
#   records in a backup database.  It gets the last datetime from the archive*
#   tables.  For the archive table, it inserts any new records in the backup
#   database.  For the archive_day_* tables, it deletes the last record in the
#   backup database and then inserts any new records.  It does not copy the
#   archive_day__metadata table.
#
###
# DateAuthorComment 
# 2016-12-16  obarlow   Create initial script

# IMPORT libraries
import datetime
import getopt
import os.path
import sqlite3
import sys

# define Variables

debugLevel = 1

# Connect to a data base

def connect_db( sqliteDB, readOnly ):
connection = None
try:
if readOnly == True:
#connection = sqlite3.connect(sqliteDB + '?mode=ro')
connection = sqlite3.connect(sqliteDB)
else:
connection = sqlite3.connect(sqliteDB)

return connection
except sqlite3.Error, e:
print "Error opening DB %s:" % sqliteDB
print "Error %s:" % e.args[0]
sys.exit(1) 


# Execute sql

def execute_sql( connection, sqliteSQL ):
try:
cursor = connection.cursor()
cursor.execute(sqliteSQL)   

return cursor
except sqlite3.Error, e:
print "Error SQL %s:" % sqliteSQL
print "Error %s:" % e.args[0]
sys.exit(1) 

# getStartTime

def getStartTime(i_archiveCon ):


SQL = 'SELECT min(dateTime) minTime from archive'

wvArchiveCur = execute_sql( i_archiveCon, SQL )

wvArchiveRow = wvArchiveCur.fetchone()

return wvArchiveRow[0]


# get parameters

try:
   opts, args = getopt.getopt(sys.argv[1:],"f:t:")
except getopt.Ge

[weewx-user] Re: weewx-forecast 3.2.6

[Oscar]

Thanks!

On Thursday, December 29, 2016 at 4:29:08 PM UTC-7, Oscar wrote:
>
> I installed weewx-forecast 3.2.6 and am getting the following error
>
> Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: downloading 
> forecast from '
> http://forecast.weather.gov/product.php?site=NWS&product=PFM&format=txt&issuedby=BOU
> '
> Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: forecast 
> failure: local variable 'mode' referenced before assignment
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx-forecast 3.2.6

[Oscar]

Yes.  For now I'm using the default index.html.tmpl and compact.html.tmpl 
that are in the skins/forecast directory.



On Thursday, December 29, 2016 at 4:29:08 PM UTC-7, Oscar wrote:
>
> I installed weewx-forecast 3.2.6 and am getting the following error
>
> Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: downloading 
> forecast from '
> http://forecast.weather.gov/product.php?site=NWS&product=PFM&format=txt&issuedby=BOU
> '
> Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: forecast 
> failure: local variable 'mode' referenced before assignment
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx-forecast 3.2.6

[Oscar]

Hi Matthew,

The compact display isn't lining up correctly when a cloud is missing.

Thanks,
Oscar


# specify settings here or in the template that includes forecast_iconic.inc
[[forecast_iconic_settings]]
source = NWS
#num_days = 7
num_days = 3
#bar_size = 150
bar_size = 75
orientation = vertical
show_date = 1
show_pop = 0
show_precip = 1
#show_obvis = 1
show_obvis = 0


On Thursday, December 29, 2016 at 4:29:08 PM UTC-7, Oscar wrote:
>
> I installed weewx-forecast 3.2.6 and am getting the following error
>
> Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: downloading 
> forecast from '
> http://forecast.weather.gov/product.php?site=NWS&product=PFM&format=txt&issuedby=BOU
> '
> Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: forecast 
> failure: local variable 'mode' referenced before assignment
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx-forecast 3.2.6

[Oscar]

That worked.  Thanks!


On Thursday, December 29, 2016 at 4:29:08 PM UTC-7, Oscar wrote:
>
> I installed weewx-forecast 3.2.6 and am getting the following error
>
> Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: downloading 
> forecast from '
> http://forecast.weather.gov/product.php?site=NWS&product=PFM&format=txt&issuedby=BOU
> '
> Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: forecast 
> failure: local variable 'mode' referenced before assignment
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: weewx-forecast 3.2.6

[Oscar]

Black Hawk.

foid = BOU  
lid = COZ036   


On Thursday, December 29, 2016 at 5:09:55 PM UTC-7, mwall wrote:
>
> oscar,
>
> which location identifier (lid) have you designated?
>
> m
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] weewx-forecast 3.2.6

[Oscar]

I installed weewx-forecast 3.2.6 and am getting the following error

Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: downloading 
forecast from 
'http://forecast.weather.gov/product.php?site=NWS&product=PFM&format=txt&issuedby=BOU'
Dec 29 16:25:15 zk30 weewx[26376]: forecast: NWSThread: NWS: forecast 
failure: local variable 'mode' referenced before assignment

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: New User - Issues with reading WVIEW sdb during conversion to WeeWX.

[Oscar]

Here is the process I use to convert my wview to weewx.  The word None and 
possibly some special characters are in the wview archive table.  The 
following process will clean up those columns.

1.  copy wview-archive.sdb to weewx.sdb
2.  run the attached script weewx-wviewCleanup.sql.  It will change those 
values to NULL. This change the command below to the appropriate paths.

sqlite3 -init PATH_TO_FILE/weewx_wviewCleanup.sql PATH_TO_DATABSE/weewx.sdb.

3.  run wee_database again.  
   If it fails, run wee_database --string-check PATH_TO_CONFIG/weewx.conf
   if that fails, note the error.  If the error identifies a column has 
None in it, modify the weewx_wviewCleanup.sql script to null out that 
column and run it again.

That process resolved my issues.

After the database has been converted by wee_database, you may want to run 
the script zkwx_wviewHiLow.py.  It reads the view-hilow.sdb data base.  
It reads most of the tables and identifies the max(high) and min(low) for 
each day.  It updates the appropriate archive_day_XXX table in weewx.sdb.  
It doesn't touch rain and rainRate.  I wasn't sure how I should total them, 
so I'm using the weewx calculation.  The script requires python3.  See 
disclaimer 2.

to run it
zkwx_wviewHiLow.py -f PATH_TO/wview-hilow.sdb -t PATH_TO/weewx.sdb

Disclaimers:
1.  Use at your own risk
2.  I don't know python.  If you (or anyone) looks at the code and asks 
themselves why did he do that, the answer is I found an example and made it 
work.

Good Luck,
Oscar




On Tuesday, December 27, 2016 at 7:07:02 PM UTC-7, Punch Card wrote:

> So I think I have gotten the configuration file correct where it is seeing 
> the weather station.
>
> But it seems that there is some errant data in my wview sdb. Also I tried 
> the *" wee_database --string-check"* there seem to be only one row in the 
> data that had an issue, but it does not look like it corrected the row.
> Is there a way to start weewx in a debug mode so I can find the errant 
> data and either correct the data, or just delete the row.
> Or do you have another suggestion?
>
> [root@weewx]# wee_database --string-check
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database 
>> 'archive_sqlite'
>> Checking archive database for strings...
>> Timestamp = 1347032100; record['rain']= u'0\n0'; ... ignored.
>> [root@weewx]# 
>>
>
> Last /var/log/messages for weewx attempt 
>
> Dec 27 08:43:10 md-centos systemd: Stopping SYSV: start and stop the weewx 
> weather system...
> Dec 27 08:43:10 md-centos weewx: Shutting down weewx: [FAILED]
> Dec 27 08:43:10 md-centos systemd: Stopped SYSV: start and stop the weewx 
> weather system.
> Dec 27 09:32:16 md-centos systemd: Starting SYSV: start and stop the weewx 
> weather system...
> Dec 27 09:32:16 md-centos weewx[31695]: engine: Initializing weewx version 
> 3.6.2
> Dec 27 09:32:16 md-centos weewx[31695]: engine: Using Python 2.7.5 
> (default, Nov  6 2016, 00:28:07) #012[GCC 4.8.5 20150623 (Red Hat 4.8.5-11)]
> Dec 27 09:32:16 md-centos weewx[31695]: engine: Platform 
> Linux-3.10.0-514.2.2.el7.x86_64-x86_64-with-centos-7.3.1611-Core
> Dec 27 09:32:16 md-centos weewx[31695]: engine: pid file is 
> /var/run/weewx.pid
> Dec 27 09:32:16 md-centos weewx[31699]: engine: Using configuration file 
> /etc/weewx/weewx.conf
> Dec 27 09:32:16 md-centos weewx[31699]: engine: Loading station type 
> WMR200 (weewx.drivers.wmr200)
> Dec 27 09:32:16 md-centos weewx: Starting weewx: [  OK  ]
> Dec 27 09:32:16 md-centos systemd: Started SYSV: start and stop the weewx 
> weather system.
> Dec 27 09:32:16 md-centos weewx[31699]: wmr200: MainThread: I Created 
> watchdog thread to poke for live data every 30 seconds
> Dec 27 09:32:16 md-centos weewx[31699]: wmr200: MainThread: I Created USB 
> polling thread to read block on device
> Dec 27 09:32:16 md-centos weewx[31699]: wmr200: Thread-2: I USB polling 
> device thread for live data launched
> Dec 27 09:32:16 md-centos weewx[31699]: wmr200: MainThread: I Reset 
> console device
> Dec 27 09:32:17 md-centos weewx[31699]: wmr200: Thread-2: I USB polling 
> device thread signaled to start
> Dec 27 09:32:17 md-centos weewx[31699]: engine: StdConvert target unit is 
> 0x1
> Dec 27 09:32:17 md-centos weewx[31699]: 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, 
>

[weewx-user] Re: customize index.html.tmpl drop down

[Oscar]

Hi Tom,

Forget my example.  It made know sense.  I'm tryin gto create this type of 
drop down list and selection.  It is possible with cheetah? You select the 
date you want and click on Browse Day Records to display the page.




On Friday, December 16, 2016 at 2:22:05 PM UTC-7, Oscar wrote:
>
> Hi Everyone,
>
> I'm looking to create a drop down list of MMDD.  I tried coping the NOAA 
> drop downs.  I thought I could use $monthDay to get a list, but that isn't 
> defined.  
>
> 
> #for $monthYear in $SummaryByMonth
> $monthDay
> #end for
> -Select month Day-
> 
>   
> Thanks,
> Oscar
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: customize index.html.tmpl drop down

[Oscar]

Got the drop downs working.

On Friday, December 16, 2016 at 2:22:05 PM UTC-7, Oscar wrote:
>
> Hi Everyone,
>
> I'm looking to create a drop down list of MMDD.  I tried coping the NOAA 
> drop downs.  I thought I could use $monthDay to get a list, but that isn't 
> defined.  
>
> 
> #for $monthYear in $SummaryByMonth
> $monthDay
> #end for
> -Select month Day-
> 
>   
> Thanks,
> Oscar
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: customize index.html.tmpl drop down

[Oscar]

adding attachment with example

On Friday, December 16, 2016 at 2:22:05 PM UTC-7, Oscar wrote:
>
> Hi Everyone,
>
> I'm looking to create a drop down list of MMDD.  I tried coping the NOAA 
> drop downs.  I thought I could use $monthDay to get a list, but that isn't 
> defined.  
>
> 
> #for $monthYear in $SummaryByMonth
> $monthDay
> #end for
> -Select month Day-
> 
>   
> Thanks,
> Oscar
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] customize index.html.tmpl drop down

[Oscar]

Hi Everyone,

I'm looking to create a drop down list of MMDD.  I tried coping the NOAA 
drop downs.  I thought I could use $monthDay to get a list, but that isn't 
defined.  


#for $monthYear in $SummaryByMonth
$monthDay
#end for
-Select month Day-

  
Thanks,
Oscar

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Converting from wview to weewx failed

[Oscar]

Thanks Tom,

Looks like some columns have "None" .  I'll null those out. 

Thanks for your help,
Oscar

On Thursday, December 1, 2016 at 4:57:06 PM UTC-7, Oscar wrote:
>
> Hi,
>
> I'm converting from wview to weewx.  I have a pi 2 running debian jessie 
> and installed weewx version 3.6.2.
> There is 11 years of data in the wview_archive database. weewxd ran over 
> 50 minutes 
> and processed over 988,000 records before it failed with the error below.  
> I ran wee_database --string-check
> and it failed as well.  Below are the errors.  Any suggestions?
>
> Thanks,
> Oscar
>
> root@zk30:/var/lib/weewx# weewxd /etc/weewx/weewx.conf
> Traceback (most recent call last):te: 2015-06-01 01:10:00 MDT (1433142600)
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 841, in main
> engine = engine_class(config_dict)
>   File "/usr/share/weewx/weewx/engine.py", line 76, in __init__
> self.loadServices(config_dict)
>   File "/usr/share/weewx/weewx/engine.py", line 140, in loadServices
> self.service_obj.append(weeutil.weeutil._get_object(svc)(self, 
> config_dict))
>   File "/usr/share/weewx/weewx/engine.py", line 486, in __init__
> self.setup_database(config_dict)
>   File "/usr/share/weewx/weewx/engine.py", line 588, in setup_database
> _nrecs, _ndays = dbmanager.backfill_day_summary() # @UnusedVariable
>   File "/usr/share/weewx/weewx/manager.py", line 1374, in 
> backfill_day_summary
> _day_accum.addRecord(_rec)
>   File "/usr/share/weewx/weewx/accum.py", line 240, in addRecord
> func(self, record, obs_type, add_hilo)
>   File "/usr/share/weewx/weewx/accum.py", line 310, in add_value
> self[obs_type].addSum(val)
>   File "/usr/share/weewx/weewx/accum.py", line 87, in addSum
> self.sum += val
> TypeError: unsupported operand type(s) for +=: 'float' and 'unicode'
>
>
> root@zk30:/var/lib/weewx# wee_database --string-check weewx.sdb
> Traceback (most recent call last):
>   File "/usr/bin/wee_database", line 453, in 
> main()
>   File "/usr/bin/wee_database", line 148, in main
> config_path, config_dict = weecfg.read_config(options.config_path, 
> args)
>   File "/usr/share/weewx/weecfg/__init__.py", line 223, in read_config
> config_dict = configobj.ConfigObj(config_path, file_error=True)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
> raise error
> configobj.ConfigObjError: Parsing failed with several errors.
> First error at line 1.
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Converting from wview to weewx failed

[Oscar]

Hi,

I'm converting from wview to weewx.  I have a pi 2 running debian jessie 
and installed weewx version 3.6.2.
There is 11 years of data in the wview_archive database. weewxd ran over 50 
minutes 
and processed over 988,000 records before it failed with the error below.  
I ran wee_database --string-check
and it failed as well.  Below are the errors.  Any suggestions?

Thanks,
Oscar

root@zk30:/var/lib/weewx# weewxd /etc/weewx/weewx.conf
Traceback (most recent call last):te: 2015-06-01 01:10:00 MDT (1433142600)
  File "/usr/bin/weewxd", line 64, in 
weewx.engine.main(options, args)
  File "/usr/share/weewx/weewx/engine.py", line 841, in main
engine = engine_class(config_dict)
  File "/usr/share/weewx/weewx/engine.py", line 76, in __init__
self.loadServices(config_dict)
  File "/usr/share/weewx/weewx/engine.py", line 140, in loadServices
self.service_obj.append(weeutil.weeutil._get_object(svc)(self, 
config_dict))
  File "/usr/share/weewx/weewx/engine.py", line 486, in __init__
self.setup_database(config_dict)
  File "/usr/share/weewx/weewx/engine.py", line 588, in setup_database
_nrecs, _ndays = dbmanager.backfill_day_summary() # @UnusedVariable
  File "/usr/share/weewx/weewx/manager.py", line 1374, in 
backfill_day_summary
_day_accum.addRecord(_rec)
  File "/usr/share/weewx/weewx/accum.py", line 240, in addRecord
func(self, record, obs_type, add_hilo)
  File "/usr/share/weewx/weewx/accum.py", line 310, in add_value
self[obs_type].addSum(val)
  File "/usr/share/weewx/weewx/accum.py", line 87, in addSum
self.sum += val
TypeError: unsupported operand type(s) for +=: 'float' and 'unicode'


root@zk30:/var/lib/weewx# wee_database --string-check weewx.sdb
Traceback (most recent call last):
  File "/usr/bin/wee_database", line 453, in 
main()
  File "/usr/bin/wee_database", line 148, in main
config_path, config_dict = weecfg.read_config(options.config_path, args)
  File "/usr/share/weewx/weecfg/__init__.py", line 223, in read_config
config_dict = configobj.ConfigObj(config_path, file_error=True)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1229, in 
__init__
self._load(infile, configspec)
  File "/usr/lib/python2.7/dist-packages/configobj.py", line 1318, in _load
raise error
configobj.ConfigObjError: Parsing failed with several errors.
First error at line 1.

-- 
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.
For more options, visit https://groups.google.com/d/optout.