[weewx-user] Belchertown beta - funny characters in forecast

[vince]

Pat - I'm seeing unexpected units (?) in my forecasts on my 32 bit Seagate 
Dockstar running your latest beta, python 3.8.1, latest v4 weewx beta.

Uncertain what exactly's going on, but it's entirely possible this ancient 
system has a whacked set of locale(s) installed given it's history.

Other note - I had to hand-compile a 'lot' to get everything working, 
including python, openssl, a bunch of pip3 modules, etc.   That said, other 
than this one nit it looks like everything is working as expected in the 
os, weewx, and all the extensions+skins including Belchertown.

Not a big priority - I can just disable forecasts on this system if needed, 
but I thought I'd mention 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/9f38566f-5645-495c-870a-2cd2710f5476%40googlegroups.com.

[weewx-user] Connecting Froggit WH2600SE to Weewx - Setup always fails :(

[Lars]

Dear Wx experts,

after reading in different forums about weather stations I purchased a 
Froggit WH2600SE.
According to the http://weewx.com/hardware.html its made by Fine Offset and 
should be supported.
I purchased the version with bridge/observer unit because it should save as 
much power as possible (the station will run with solar in the field).
The weather logger software on the bridge device is Version 2.2.8 
(pre-configured for wunderground; with the option to change the server 
IP/Hostname, and Server Port).
Reporting to Wunderground works but I need the data directly and in a 
format I can export.

For the last 2 weeks I have been fighting in nightly sessions to get the 
data onto my new raspberry pi version 3 model B V1.2 (never used one 
before).
To start everything I assigned a fixed IP of 192.168.1.119 to my raspberry 
and 192.168.1.122 to the bridge in my router.
I used/ tried the weewx interceptor driver by Matthew Well in listen and 
sniff mode but did not get any data to my raspberry.
I went through several complete reinstalls of weewx and the raspberry OS 
(for example because I tried to bridge eth0 and eth1 (a USB LAN dongle) 
while using SSH to log in via WLAN).
Needless to say I did not succeed getting the bridge working.

During one of my first tries I used this tutorial 
http://landoflinux.com/linux_raspberry_pi_weather_station.html but I now 
realised that it probably did not work because it contains a HP1000 driver 
(which is a wifi Display afaik).
I tried several other things (
http://weewx.com/docs/usersguide.htm#installing and 
https://github.com/weewx/weewx/wiki/observer ….) but nothing worked.

I have now reinstalled raspberry OS (raspian  buster lite, administrated 
with SSH via Terminal), weewx and the interceptor driver again.
Then I edited the weewx config file to listen in port 800 and installed the 
cumulus plugin https://github.com/weewx/weewx/wiki/crt (
http://192.168.1.119/var/tmp/realtime.txt reported no real data for a while 
but cant be reached anymore).

See below weewx config file:

# 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 = 1

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

# 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

….



  # 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 = Interceptor

# 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 = 0

##

[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, smarthub, or access
#   observer - fine offset WH2600/HP1000/HP1003, ambient WS2902
#   lw30x - oregon scientific LW301/LW302
#   lacrosse-bridge - lacrosse GW1000U/C84612 internet bridge
#   fineoffset-bridge - fine offset GW1000/GW1000B/GW1000BU wifi gateway
#   wu-client - any hardware that uses the weather underground protocol
device_type = observer
port = 800
address = 192.168.1.122

##

[Simulator]
# This section is for the weewx weather station simulator

# The time (in seconds) between LOOP packets.
loop_interval = 2.5

# The simulator mode can be either 'simulator' or 'generator'.
# Real-time simulator. Sleep between each LOOP packet.
mode = simulator
# Generator.  Emit LOOP packets as fast as possible (useful for 
testing).
#mode = generator

# The start time. Format is -mm-ddTHH:MM. If not specified, the 
default 
# is to use the present time.
#start = 2011-01-01T00:00

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

##

[weewx-user] Re: ELV Mobile Alerts gateway MA 10000

[mwall]

On Wednesday, January 1, 2020 at 5:30:33 PM UTC-5, Stefanie Drucker wrote:
>
> Hi,
>
> I've bought a Mobile Alerts gateway and various sensors recently and want 
> to use it with weewx.
>
> This gateway is an European version of the LaCrosse GW-1000U. It looks 
> exactly the same, but obviously is different (see 
> https://github.com/sarnau/obileAlerts/blob/master/MobileAlertsELVvsLaCrosse.markdown
> ).
>
> Anyone has the same weather station and managed to set up weewx receiving 
> data from it?
>

you can try the weewx-interceptor driver:

https://github.com/matthewwall/weewx-interceptor

set the device_type=lacrosse-bridge

the lacross bridge has a rather complicated protocol.  try to configure as 
much as you can with the vendor's GAS program - at the very least you must 
tell the GW1000 to communicate with the computer that is running weewx 
(there is no passive sniffing mode for the lacross GW1000U).  and please 
read the comments about GW1000U in the interceptor.py file.  it is a bit 
technical, but you will probably have to tweak the serial number.

finally, do not confuse the lacross GW1000U with the fine offset GW1000.  
froggit, ecowitt (and soon others?) sell the fine offset GW1000B and 
GW1000BU - 915MHz, the GW1000A - 868MHz, and the GW1000 - 433MHz.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d9387800-443c-4518-b051-ef83e51525e8%40googlegroups.com.

[weewx-user] ELV Mobile Alerts gateway MA 10000

[Stefanie Drucker]

Hi,

I've bought a Mobile Alerts gateway and various sensors recently and want 
to use it with weewx.

This gateway is an European version of the LaCrosse GW-1000U. It looks 
exactly the same, but obviously is different (see 
https://github.com/sarnau/obileAlerts/blob/master/MobileAlertsELVvsLaCrosse.markdown
).

Anyone has the same weather station and managed to set up weewx receiving 
data from it?

Any help or hints appreciated. ☺️

Stef


-- 
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/ba8c3f7c-3af8-41b6-8003-b888721fa0e7%40googlegroups.com.

[weewx-user] Re: Belchertown Skin with Weewx v4

[vince]

On Wednesday, January 1, 2020 at 8:56:57 AM UTC-8, Johannes Ebner wrote:
>
> 1) Is the current release of weewx 4.x already useable (stable)?
> 2) Anyone tested already Belchertown-Skin on v4.x?
>
>
>
1) please follow the v4 threads here and on the weewx-development list. 
 Short answer is 'for many people', but it depends on which drivers and 
extensions you use.
2) yes - if you use the development branch, it works on v4 under python3
 

-- 
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/07668cc7-1ab4-4682-afd5-f3c5fbc82199%40googlegroups.com.

[weewx-user] Belchertown Skin with Weewx v4

['Johannes Ebner' via weewx-user]

Hi, 

I am currently running Belchertown-Skin on Weewx 3.9.2

As I anyhow want to change the Hardware for the Weewx System I am thinking 
of going already to weewx v4 (beta).

Therefore I have two questions:

1) Is the current release of weewx 4.x already useable (stable)?
2) Anyone tested already Belchertown-Skin on v4.x?

Best Regards,
Johannes

-- 
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/f5b346b5-f628-4b4b-b289-f2fe5e269c74%40googlegroups.com.

[weewx-user] Re: Communication error on Terminal with Davis Vantage Pro 2

[Geni]

It's clear now. But this says weewx and means itself! 


Am Mittwoch, 1. Januar 2020 10:34:18 UTC+1 schrieb Geni:
>
> Why do I usually get this error on the console? 
> After the second or third attempt the info is listed?
>
> sudo wee_device --info
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
> Unable to wake up console... sleeping
> Unable to wake up console... retrying
> Traceback (most recent call last):
>   File "/usr/bin/wee_device", line 66, in 
> main()
>   File "/usr/bin/wee_device", line 62, in main
> device.configure(config_dict)
>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
> self.do_options(options, parser, config_dict, prompt)
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1973, in 
> do_options
> station = Vantage(**config_dict[DRIVER_NAME])
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 488, in __init__
> self._setup()
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1290, in _setup
> unit_bits  = self._getEEPROM_value(0x29)[0]
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1376, in 
> _getEEPROM_value
> raise weewx.RetriesExceeded("While getting EEPROM data value at 
> address 0x%X" % offset)
> weewx.RetriesExceeded: While getting EEPROM data value at address 0x29
>
> syslog:
> Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: SerialException on read
> .
> Jan  1 09:23:45 Wetter-Raspi weewx[3001]:  device reports 
> readiness to read but returned no data (device disconnected or multiple 
> access on port?)
> Jan  1 09:23:45 Wetter-Raspi weewx[3001]:  Is there a competing 
> process running??
> Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: LOOP try #1; error: 
> device reports readiness to read but returned no data (device disconnected 
> or multiple access on port?)
> Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP 
> packets.
> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Retry  #0 failed
> Jan  1 09:23:49 Wetter-Raspi wee_device[6419]: vantage: No  received 
> from console
> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Rude wake up of 
> console successful
> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: No  received from 
> console
> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: LOOP try #2; error: No 
>  received from Vantage console
> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP 
> packets.
> Jan  1 09:23:49 Wetter-Raspi wee_device[6419]: vantage: No  received 
> from console
> Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: Retry  #0 failed
> Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: SerialException on read
> .
> Jan  1 09:23:51 Wetter-Raspi weewx[3001]:  device reports 
> readiness to read but returned no data (device disconnected or multiple 
> access on port?)
> Jan  1 09:23:51 Wetter-Raspi weewx[3001]:  Is there a competing 
> process running??
> Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: Retry  #1 failed
> Jan  1 09:23:55 Wetter-Raspi weewx[3001]: vantage: Retry  #2 failed
> Jan  1 09:23:55 Wetter-Raspi wee_device[6419]: vantage: SerialException 
> on read.
> Jan  1 09:23:55 Wetter-Raspi wee_device[6419]:  device reports 
> readiness to read but returned no data (device disconnected or multiple 
> access on port?)
> Jan  1 09:23:55 Wetter-Raspi wee_device[6419]:  Is there a 
> competing process running??
> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Retry  #3 failed
> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Unable to wake up 
> console
> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: LOOP try #3; error: 
> Unable to wake up Vantage console
> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP 
> packets.
> Jan  1 09:23:56 Wetter-Raspi wee_device[6419]: vantage: Unable to pass 
> CRC16 check while getting data
> Jan  1 09:23:56 Wetter-Raspi wee_device[6419]: vantage: Max retries 
> exceeded while getting EEPROM data at address 0x29
>
> Regards
> Geni
>

-- 
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/ec76c5bf-40bd-48c3-ae67-03a50ac63c35%40googlegroups.com.

Re: [weewx-user] Re: Communication error on Terminal with Davis Vantage Pro 2

[Thomas Keffer]

If you look in the logs, you'll see:

Jan  1 09:23:51 Wetter-Raspi weewx[3001]:  Is there a competing
process running??

On Wed, Jan 1, 2020 at 8:01 AM Geni  wrote:

> Yes, that's how it works without mistakes, thank you.
> Is this in the documentation, or do you just know this?
> Regards,
> Geni
>
> Am Mittwoch, 1. Januar 2020 10:34:18 UTC+1 schrieb Geni:
>>
>> Why do I usually get this error on the console?
>> After the second or third attempt the info is listed?
>>
>> sudo wee_device --info
>> Using configuration file /etc/weewx/weewx.conf
>> Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
>> Unable to wake up console... sleeping
>> Unable to wake up console... retrying
>> Traceback (most recent call last):
>>   File "/usr/bin/wee_device", line 66, in 
>> main()
>>   File "/usr/bin/wee_device", line 62, in main
>> device.configure(config_dict)
>>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
>> self.do_options(options, parser, config_dict, prompt)
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1973, in
>> do_options
>> station = Vantage(**config_dict[DRIVER_NAME])
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 488, in __init__
>> self._setup()
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1290, in _setup
>> unit_bits  = self._getEEPROM_value(0x29)[0]
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1376, in
>> _getEEPROM_value
>> raise weewx.RetriesExceeded("While getting EEPROM data value at
>> address 0x%X" % offset)
>> weewx.RetriesExceeded: While getting EEPROM data value at address 0x29
>>
>> syslog:
>> Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: SerialException on
>> read.
>> Jan  1 09:23:45 Wetter-Raspi weewx[3001]:  device reports
>> readiness to read but returned no data (device disconnected or multiple
>> access on port?)
>> Jan  1 09:23:45 Wetter-Raspi weewx[3001]:  Is there a competing
>> process running??
>> Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: LOOP try #1; error:
>> device reports readiness to read but returned no data (device disconnected
>> or multiple access on port?)
>> Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP
>> packets.
>> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Retry  #0 failed
>> Jan  1 09:23:49 Wetter-Raspi wee_device[6419]: vantage: No 
>> received from console
>> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Rude wake up of
>> console successful
>> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: No  received from
>> console
>> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: LOOP try #2; error:
>> No  received from Vantage console
>> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP
>> packets.
>> Jan  1 09:23:49 Wetter-Raspi wee_device[6419]: vantage: No 
>> received from console
>> Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: Retry  #0 failed
>> Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: SerialException on
>> read.
>> Jan  1 09:23:51 Wetter-Raspi weewx[3001]:  device reports
>> readiness to read but returned no data (device disconnected or multiple
>> access on port?)
>> Jan  1 09:23:51 Wetter-Raspi weewx[3001]:  Is there a competing
>> process running??
>> Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: Retry  #1 failed
>> Jan  1 09:23:55 Wetter-Raspi weewx[3001]: vantage: Retry  #2 failed
>> Jan  1 09:23:55 Wetter-Raspi wee_device[6419]: vantage: SerialException
>> on read.
>> Jan  1 09:23:55 Wetter-Raspi wee_device[6419]:  device reports
>> readiness to read but returned no data (device disconnected or multiple
>> access on port?)
>> Jan  1 09:23:55 Wetter-Raspi wee_device[6419]:  Is there a
>> competing process running??
>> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Retry  #3 failed
>> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Unable to wake up
>> console
>> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: LOOP try #3; error:
>> Unable to wake up Vantage console
>> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP
>> packets.
>> Jan  1 09:23:56 Wetter-Raspi wee_device[6419]: vantage: Unable to pass
>> CRC16 check while getting data
>> Jan  1 09:23:56 Wetter-Raspi wee_device[6419]: vantage: Max retries
>> exceeded while getting EEPROM data at address 0x29
>>
>> Regards
>> Geni
>>
> --
> 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/a5e8167e-0d2a-4098-a629-b38cc1931b44%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subs

[weewx-user] Re: forecast 3.3.2 config question

[René Schulze]

Hello,

Now i found the problem cause DS also won't store the received data. In 
debugmode 1 i saw a error like "data to long for field qsf". After i set 
manually in the database the fields qsf and qpf to varchar(30) both 
forecast providers working fine. In the database i can find values like 
"0.0149606299212598" 
in these datafields. 
I used the api call in a browser and in the responding json i couln't found 
the values. It seems to be a foult data or wrong calculation. 

greetings René

-- 
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/ed3c108c-5b13-4cfd-91b5-77df45acd328%40googlegroups.com.

[weewx-user] Re: Communication error on Terminal with Davis Vantage Pro 2

[Geni]

Yes, that's how it works without mistakes, thank you.
Is this in the documentation, or do you just know this?
Regards,
Geni

Am Mittwoch, 1. Januar 2020 10:34:18 UTC+1 schrieb Geni:
>
> Why do I usually get this error on the console? 
> After the second or third attempt the info is listed?
>
> sudo wee_device --info
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
> Unable to wake up console... sleeping
> Unable to wake up console... retrying
> Traceback (most recent call last):
>   File "/usr/bin/wee_device", line 66, in 
> main()
>   File "/usr/bin/wee_device", line 62, in main
> device.configure(config_dict)
>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
> self.do_options(options, parser, config_dict, prompt)
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1973, in 
> do_options
> station = Vantage(**config_dict[DRIVER_NAME])
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 488, in __init__
> self._setup()
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1290, in _setup
> unit_bits  = self._getEEPROM_value(0x29)[0]
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1376, in 
> _getEEPROM_value
> raise weewx.RetriesExceeded("While getting EEPROM data value at 
> address 0x%X" % offset)
> weewx.RetriesExceeded: While getting EEPROM data value at address 0x29
>
> syslog:
> Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: SerialException on read
> .
> Jan  1 09:23:45 Wetter-Raspi weewx[3001]:  device reports 
> readiness to read but returned no data (device disconnected or multiple 
> access on port?)
> Jan  1 09:23:45 Wetter-Raspi weewx[3001]:  Is there a competing 
> process running??
> Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: LOOP try #1; error: 
> device reports readiness to read but returned no data (device disconnected 
> or multiple access on port?)
> Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP 
> packets.
> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Retry  #0 failed
> Jan  1 09:23:49 Wetter-Raspi wee_device[6419]: vantage: No  received 
> from console
> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Rude wake up of 
> console successful
> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: No  received from 
> console
> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: LOOP try #2; error: No 
>  received from Vantage console
> Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP 
> packets.
> Jan  1 09:23:49 Wetter-Raspi wee_device[6419]: vantage: No  received 
> from console
> Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: Retry  #0 failed
> Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: SerialException on read
> .
> Jan  1 09:23:51 Wetter-Raspi weewx[3001]:  device reports 
> readiness to read but returned no data (device disconnected or multiple 
> access on port?)
> Jan  1 09:23:51 Wetter-Raspi weewx[3001]:  Is there a competing 
> process running??
> Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: Retry  #1 failed
> Jan  1 09:23:55 Wetter-Raspi weewx[3001]: vantage: Retry  #2 failed
> Jan  1 09:23:55 Wetter-Raspi wee_device[6419]: vantage: SerialException 
> on read.
> Jan  1 09:23:55 Wetter-Raspi wee_device[6419]:  device reports 
> readiness to read but returned no data (device disconnected or multiple 
> access on port?)
> Jan  1 09:23:55 Wetter-Raspi wee_device[6419]:  Is there a 
> competing process running??
> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Retry  #3 failed
> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Unable to wake up 
> console
> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: LOOP try #3; error: 
> Unable to wake up Vantage console
> Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP 
> packets.
> Jan  1 09:23:56 Wetter-Raspi wee_device[6419]: vantage: Unable to pass 
> CRC16 check while getting data
> Jan  1 09:23:56 Wetter-Raspi wee_device[6419]: vantage: Max retries 
> exceeded while getting EEPROM data at address 0x29
>
> Regards
> Geni
>

-- 
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/a5e8167e-0d2a-4098-a629-b38cc1931b44%40googlegroups.com.

Re: [weewx-user] DB error(s) or something else?

[Thomas Keffer]

Most likely, your disk is failing, leading to database corruption. You can
check by using the tool sqlite3, although it is not 100% able to find all
errors.

You may have to install it first

*sudo apt install sqlite3*

Then run it on the database

*sqlite3 /var/lib/weewx/weewx.sdb*
sqlite>* PRAGMA integrity_check;*

If you find some errors, the tool DB Browser for SQLite
 purports to be able to fix some errors,
although I have never tried it. It may be worth giving it a try.

If you can fix the database, copy it over to a safe place.

Personally, unless you've got good reason to think it's OK, I would throw
the disk away and start all over with a fresh disk. Install the OS;
reinstall weewx. If you were able to recover the database, copy it over.
Otherwise, start afresh.

-tk



On Wed, Jan 1, 2020 at 7:26 AM Ian Bell  wrote:

> I am consistently getting the following error
>
> cheetahgenerator: Generated 8 files for report SeasonsReport in 1.22
> seconds
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: reportengine: Caught unrecoverable
> exception in generator 'weewx.imagegenerator.ImageGenerator'
>
> Jan  1 09:20:21 rasp-weewx weewx[515]:   database disk image
> is malformed
>
> Jan  1 09:20:21 rasp-weewx weewx[515]:   Traceback (most
> recent call last):
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/reportengine.py", line 204, in run
>
> Jan  1 09:20:21 rasp-weewx weewx[515]:   obj.start()
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/reportengine.py", line 300, in start
>
> Jan  1 09:20:21 rasp-weewx weewx[515]:   self.run()
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/imagegenerator.py", line 33, in run
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: 
> self.genImages(self.gen_ts)
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/imagegenerator.py", line 170, in genImages
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: 
> aggregate_interval=aggregate_interval)
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/manager.py", line 513, in getSqlVectors
>
> Jan  1 09:20:21 rasp-weewx weewx[515]:   aggregate_type,
> aggregate_interval)
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/manager.py", line 761, in _getSqlVectors
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: 
> _cursor.execute(sql_str, stamp)
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weedb/sqlite.py", line 29, in guarded_fn
>
> Jan  1 09:20:21 rasp-weewx weewx[515]:   return fn(*args,
> **kwargs)
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weedb/sqlite.py", line 211, in execute
>
> Jan  1 09:20:21 rasp-weewx weewx[515]:   return
> sqlite3.Cursor.execute(self, *args, **kwargs)
>
> Jan  1 09:20:21 rasp-weewx weewx[515]:   DatabaseError:
> database disk image is malformed
>
> Jan  1 09:20:21 rasp-weewx weewx[515]:   Generator terminated
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: copygenerator: copied 0 files to
> /var/www/html/weewx
>
> Jan  1 09:20:21 rasp-weewx weewx[515]: cheetahgenerator: Generated 1 files
> for report cmon in 0.03 seconds
>
> Jan  1 09:20:22 rasp-weewx weewx[515]: reportengine: Caught unrecoverable
> exception in generator 'weewx.imagegenerator.ImageGenerator'
>
> Jan  1 09:20:22 rasp-weewx weewx[515]:   database disk image
> is malformed
>
> Jan  1 09:20:22 rasp-weewx weewx[515]:   Traceback (most
> recent call last):
>
> Jan  1 09:20:22 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/reportengine.py", line 204, in run
>
> Jan  1 09:20:22 rasp-weewx weewx[515]:   obj.start()
>
> Jan  1 09:20:22 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/reportengine.py", line 300, in start
>
> Jan  1 09:20:22 rasp-weewx weewx[515]:   self.run()
>
> Jan  1 09:20:22 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/imagegenerator.py", line 33, in run
>
> Jan  1 09:20:22 rasp-weewx weewx[515]: 
> self.genImages(self.gen_ts)
>
> Jan  1 09:20:22 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/imagegenerator.py", line 170, in genImages
>
> Jan  1 09:20:22 rasp-weewx weewx[515]: 
> aggregate_interval=aggregate_interval)
>
> Jan  1 09:20:22 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/manager.py", line 513, in getSqlVectors
>
> Jan  1 09:20:22 rasp-weewx weewx[515]:   aggregate_type,
> aggregate_interval)
>
> Jan  1 09:20:22 rasp-weewx weewx[515]: File
> "/usr/share/weewx/weewx/manager.py", line 790, in _getSqlVectors
>
> Jan  1

[weewx-user] corrupt DB or something else?

[Die Fledermaus]

I am consistently getting the following error

cheetahgenerator: Generated 8 files for report SeasonsReport in 1.22 seconds

Jan  1 09:20:21 rasp-weewx weewx[515]: reportengine: Caught unrecoverable 
exception in generator 'weewx.imagegenerator.ImageGenerator'

Jan  1 09:20:21 rasp-weewx weewx[515]:   database disk image is 
malformed

Jan  1 09:20:21 rasp-weewx weewx[515]:   Traceback (most recent 
call last):

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/reportengine.py", line 204, in run

Jan  1 09:20:21 rasp-weewx weewx[515]:   obj.start()

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/reportengine.py", line 300, in start

Jan  1 09:20:21 rasp-weewx weewx[515]:   self.run()

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/imagegenerator.py", line 33, in run

Jan  1 09:20:21 rasp-weewx weewx[515]:   
self.genImages(self.gen_ts)

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/imagegenerator.py", line 170, in genImages

Jan  1 09:20:21 rasp-weewx weewx[515]:   
aggregate_interval=aggregate_interval)

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/manager.py", line 513, in getSqlVectors

Jan  1 09:20:21 rasp-weewx weewx[515]:   aggregate_type, 
aggregate_interval)

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/manager.py", line 761, in _getSqlVectors

Jan  1 09:20:21 rasp-weewx weewx[515]:   
_cursor.execute(sql_str, stamp)

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weedb/sqlite.py", line 29, in guarded_fn

Jan  1 09:20:21 rasp-weewx weewx[515]:   return fn(*args, 
**kwargs)

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weedb/sqlite.py", line 211, in execute

Jan  1 09:20:21 rasp-weewx weewx[515]:   return 
sqlite3.Cursor.execute(self, *args, **kwargs)

Jan  1 09:20:21 rasp-weewx weewx[515]:   DatabaseError: 
database disk image is malformed

Jan  1 09:20:21 rasp-weewx weewx[515]:   Generator terminated

Jan  1 09:20:21 rasp-weewx weewx[515]: copygenerator: copied 0 files to 
/var/www/html/weewx

Jan  1 09:20:21 rasp-weewx weewx[515]: cheetahgenerator: Generated 1 files 
for report cmon in 0.03 seconds

Jan  1 09:20:22 rasp-weewx weewx[515]: reportengine: Caught unrecoverable 
exception in generator 'weewx.imagegenerator.ImageGenerator'

Jan  1 09:20:22 rasp-weewx weewx[515]:   database disk image is 
malformed

Jan  1 09:20:22 rasp-weewx weewx[515]:   Traceback (most recent 
call last):

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/reportengine.py", line 204, in run

Jan  1 09:20:22 rasp-weewx weewx[515]:   obj.start()

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/reportengine.py", line 300, in start

Jan  1 09:20:22 rasp-weewx weewx[515]:   self.run()

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/imagegenerator.py", line 33, in run

Jan  1 09:20:22 rasp-weewx weewx[515]:   
self.genImages(self.gen_ts)

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/imagegenerator.py", line 170, in genImages

Jan  1 09:20:22 rasp-weewx weewx[515]:   
aggregate_interval=aggregate_interval)

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/manager.py", line 513, in getSqlVectors

Jan  1 09:20:22 rasp-weewx weewx[515]:   aggregate_type, 
aggregate_interval)

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/manager.py", line 790, in _getSqlVectors

Jan  1 09:20:22 rasp-weewx weewx[515]:   for _rec in 
_cursor.execute(sql_str, (startstamp, stopstamp)):

Jan  1 09:20:22 rasp-weewx weewx[515]:   DatabaseError: 
database disk image is malformed

Jan  1 09:20:22 rasp-weewx weewx[515]:   Generator terminated
 I had my usb stick on my raspberry Pi fail during an update so I had to 
restore my weewx from my backed up files. I am concerned the DB copy I have 
is corrupt. and I will loose all my previous data. If I have to start with 
a new DB what is the best way to do this short of reinstalling weewx, and 
putting back the backed up files minus the DB.

-- 
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/6f86e690-4844-41e8-8c5c-ed6bc1b13fba%40g

[weewx-user] DB error(s) or something else?

[Ian Bell]

I am consistently getting the following error

cheetahgenerator: Generated 8 files for report SeasonsReport in 1.22 seconds

Jan  1 09:20:21 rasp-weewx weewx[515]: reportengine: Caught unrecoverable 
exception in generator 'weewx.imagegenerator.ImageGenerator'

Jan  1 09:20:21 rasp-weewx weewx[515]:   database disk image is 
malformed

Jan  1 09:20:21 rasp-weewx weewx[515]:   Traceback (most recent 
call last):

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/reportengine.py", line 204, in run

Jan  1 09:20:21 rasp-weewx weewx[515]:   obj.start()

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/reportengine.py", line 300, in start

Jan  1 09:20:21 rasp-weewx weewx[515]:   self.run()

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/imagegenerator.py", line 33, in run

Jan  1 09:20:21 rasp-weewx weewx[515]:   
self.genImages(self.gen_ts)

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/imagegenerator.py", line 170, in genImages

Jan  1 09:20:21 rasp-weewx weewx[515]:   
aggregate_interval=aggregate_interval)

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/manager.py", line 513, in getSqlVectors

Jan  1 09:20:21 rasp-weewx weewx[515]:   aggregate_type, 
aggregate_interval)

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/manager.py", line 761, in _getSqlVectors

Jan  1 09:20:21 rasp-weewx weewx[515]:   
_cursor.execute(sql_str, stamp)

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weedb/sqlite.py", line 29, in guarded_fn

Jan  1 09:20:21 rasp-weewx weewx[515]:   return fn(*args, 
**kwargs)

Jan  1 09:20:21 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weedb/sqlite.py", line 211, in execute

Jan  1 09:20:21 rasp-weewx weewx[515]:   return 
sqlite3.Cursor.execute(self, *args, **kwargs)

Jan  1 09:20:21 rasp-weewx weewx[515]:   DatabaseError: 
database disk image is malformed

Jan  1 09:20:21 rasp-weewx weewx[515]:   Generator terminated

Jan  1 09:20:21 rasp-weewx weewx[515]: copygenerator: copied 0 files to 
/var/www/html/weewx

Jan  1 09:20:21 rasp-weewx weewx[515]: cheetahgenerator: Generated 1 files 
for report cmon in 0.03 seconds

Jan  1 09:20:22 rasp-weewx weewx[515]: reportengine: Caught unrecoverable 
exception in generator 'weewx.imagegenerator.ImageGenerator'

Jan  1 09:20:22 rasp-weewx weewx[515]:   database disk image is 
malformed

Jan  1 09:20:22 rasp-weewx weewx[515]:   Traceback (most recent 
call last):

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/reportengine.py", line 204, in run

Jan  1 09:20:22 rasp-weewx weewx[515]:   obj.start()

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/reportengine.py", line 300, in start

Jan  1 09:20:22 rasp-weewx weewx[515]:   self.run()

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/imagegenerator.py", line 33, in run

Jan  1 09:20:22 rasp-weewx weewx[515]:   
self.genImages(self.gen_ts)

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/imagegenerator.py", line 170, in genImages

Jan  1 09:20:22 rasp-weewx weewx[515]:   
aggregate_interval=aggregate_interval)

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/manager.py", line 513, in getSqlVectors

Jan  1 09:20:22 rasp-weewx weewx[515]:   aggregate_type, 
aggregate_interval)

Jan  1 09:20:22 rasp-weewx weewx[515]: File 
"/usr/share/weewx/weewx/manager.py", line 790, in _getSqlVectors

Jan  1 09:20:22 rasp-weewx weewx[515]:   for _rec in 
_cursor.execute(sql_str, (startstamp, stopstamp)):

Jan  1 09:20:22 rasp-weewx weewx[515]:   DatabaseError: 
database disk image is malformed

Jan  1 09:20:22 rasp-weewx weewx[515]:   Generator terminated
 I had my usb stick on my raspberry Pi fail during an update so I had to 
restore my weewx from my backed up files. I am concerned the DB copy I have 
is corrupt. and I will loose all my previous data. If I have to start with 
a new DB what is the best way to do this short of reinstalling weewx, and 
putting back the backed up files minus the DB.

-- 
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/5f507c85-2e6d-4072-9659-bc4fef6ca52b%40g

[weewx-user] Re: Display rainrate in mm/h not mm/hr

[Stefan]

Hallo Geni.

Ich habe deine Mailadresse gesucht und leider nicht gefunden. Kannst du mir 
diese bitte mal zukommen lassen?

Danke und Gruss aus der Schweiz. Meteo Oberwallis Stefan 
(i...@meteo-oberwallis.ch)

Am Sonntag, 29. Dezember 2019 16:05:12 UTC+1 schrieb Geni:
>
> Hello, 
>
> i use weewx 3.9.2 on a raspberry 3+ with a mysql database, the template is 
> season.
> unfortunately since switching to a new raspberry the rainrate is displayed 
> with xx mm/hr but i want mm/h.
> What do I have to change so that the rain rate is displayed in mm/h?
>
> Thanks, Geni
>
> Livesite is https://affolter.familyds.net/wetter/index.html
>

-- 
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/189922cc-3963-45d9-9b00-63ffb91723a9%40googlegroups.com.

[weewx-user] Re: Sunshine Time

[Stefan]

Hello everybody
I have a question about graphic design. I would like to include the sunshine 
time in the graphics. Currently the value of 0.08 in sunshine always appears 
there. This is my current code in use.
[[chart6]]
title = Sonnenschein
# Make sure the y-axis increment is at least 0.02 for the sun plot
yscale = 0.0, 1.0, 0.1
type = column
[[[sunshine_hours]]]
aggregate_type = sum
aggregate_interval = 300
color = "#e4d354"
name = Sonnenschein in Minuten

[image: Unbenannt.PNG]



I would like to do this now, because the interval 300s is 5min as sunshine. Can 
one make it like this?

Many thanks for your help




Am Montag, 22. Juli 2019 11:50:28 UTC+2 schrieb Stefan:
>
> Hello everybody.
>
> I have found this link (
> https://github.com/brewster76/util-archer/blob/master/user/radiationhours.py) 
> where is described how to display the sunshine time. Now I would like to 
> show this value in numbers (eg 4:15 h). Is that possible?
>
> Thank you
>
>
>

-- 
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/38847624-7a27-4899-a03d-f1b6f92652d3%40googlegroups.com.

Re: [weewx-user] Re: StdReport thread has been terminated every day at 00:20 (1927, 'Connection was killed')

[Thomas Keffer]

With the changes, WeeWX will wait 60 seconds, then restart from the top. If
your backup takes 10 minutes, then it will keep retrying 10 times until it
succeeds.

On Wed, Jan 1, 2020 at 2:28 AM Geni  wrote:

> Hyperbackup runs on my synology and weewx on a Raspberry, so Hyperbackup
> can't stop and start weewx!
> I think it's better if weewx is fault tolerant, Snology is rebooted
> occasionally during updates, then there is no database connection, the
> HTML_ROOT is offline and the FTP path is not found.
>
> Am Mittwoch, 1. Januar 2020 09:29:50 UTC+1 schrieb Andrew Milner:
>>
>> or you could stop weewx for the hyperbackup period and resume when it is
>> complete.  weewx will then do 'catchup' from loggers and all should be
>> tickety-boo .
>>
>>
>>
>> On Wednesday, 1 January 2020 10:21:16 UTC+2, Geni wrote:
>>>
>>> Hi, Thomas.
>>> The hint that the error code 1927 comes from MariaDB, I knew immediately
>>> where to look for it!
>>> Now at this time a hyperbackup job is running on my synologe which also
>>> contained the application MariaDB, I have removed it and this night no
>>> error messages.
>>>
>>> Summary:
>>> The backup stops the database service for a short moment and if that's
>>> exactly when Weewx wants to access it, it won't work.
>>> My suggestion would be if weewx doesn't get a database connection it
>>> will wait for the next interval but without killing the process.
>>> In my case this would be 1 or 2 intervals and then the missing records
>>> would be read in and nobody would notice anything.
>>>
>>> Regards
>>> Geni
>>>
>>> PS: This error occurred very rarely with the Raspberry PI2?
>>>
>>>
>>> Am Dienstag, 31. Dezember 2019 11:01:10 UTC+1 schrieb Geni:

 Hello,
 Since I replaced the Raspberry PI 2 with a Raspberry PI 3+ this problem
 occurs every night, before only sporadically.
 In use:
 Raspberry 3+ mit Raspbian Buster Lite
 Externe SqlDB (MariaDB 10)
 David Vantage Pro2 Version: 3.83
 Weewx 3.9.2-1

 Every night at exactly 00:20, it stops. The report at 00:10 is still
 made
 debug-log:
 Dec 31 00:10:55 Wetter-Raspi weewx[889]: reportengine: Report 'RSYNC'
 not enabled. Skipping.
 Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Requesting 200 LOOP
 packets.
 Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Gentle wake up of
 console successful
 Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: StdReport thread has
 been terminated
 Dec 31 07:44:10 Wetter-Raspi weewx[3001]: engine: Debug is 1
 Dec 31 07:44:10 Wetter-Raspi weewx[3001]: engine: Initializing engine
 Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Driver version is
 3.1.1
 Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Opened up serial
 port /dev/ttyUSB0; baud 19200; timeout 4.00
 Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Gentle wake up of
 console successful
 Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Hardware type is 16
 Dec 31 07:44:11 Wetter-Raspi weewx[3001]: vantage: ISS ID is 1
 Dec 31 07:44:11 Wetter-Raspi weewx[3001]: vantage: Hardware name:
 Vantage Pro2

 syslog:
 Dec 31 00:17:01 Wetter-Raspi CRON[1919]: (root) CMD (   cd / &&
 run-parts --report /etc/cron.hourly)
 Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Requesting 200 LOOP
 packets.
 Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Gentle wake up of
 console successful
 Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Main loop exiting.
 Shutting engine down.
 Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Shutting down
 StdReport thread
 Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: StdReport thread has
 been terminated
 Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Caught unrecoverable
 exception in engine:
 Dec 31 00:20:01 Wetter-Raspi weewx[889]:   (1927, 'Connection
 was killed')
 Dec 31 00:20:01 Wetter-Raspi weewx[889]:   Traceback (most
 recent call last):
 Dec 31 00:20:01 Wetter-Raspi weewx[889]: File
 "/usr/share/weewx/weewx/engine.py", line 894, in main
 Dec 31 00:20:01 Wetter-Raspi weewx[889]:   engine.run()
 Dec 31 00:20:01 Wetter-Raspi weewx[889]: File
 "/usr/share/weewx/weewx/engine.py", line 191, in run
 Dec 31 00:20:01 Wetter-Raspi weewx[889]: 
 self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
 Dec 31 00:20:01 Wetter-Raspi weewx[889]: File
 "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
 Dec 31 00:20:01 Wetter-Raspi weewx[889]:   callback(event)
 Dec 31 00:20:01 Wetter-Raspi weewx[889]: File
 "/usr/share/weewx/weewx/wxservices.py", line 45, in new_loop_packet
 Dec 31 00:20:01 Wetter-Raspi weewx[889]: 
 self.calc.do_calculations(event.packet, 'loop')
 Dec 31 00:20:01 Wetter-Raspi weewx[889]:

Re: [weewx-user] Re: Display rainrate in mm/h not mm/hr

[Dave (G1OGY)]

On Wed, 1 Jan 2020 at 00:59, Thomas Keffer  wrote:
>
> OK, you've talked me into it! The defaults now use "h", instead of "hr", "km" 
> instead of "kms". I don't think they ever used "cms", at least, I can't find 
> any such references.
>
cm plural was the 2nd snag that came to me having been reading a
design with 'cms' proliferating.
Regrettably, children in the UK are taught to measure in centimetres -
millimetres are deigned `too small`.

> I've also made "metre" an option to "meter".
>
Thank you, appreciated

> But, "foot", instead of "feet"? So my altitude would be "700 foot"? That 
> sounds just plain wrong to my American ear! A user can always override.
>
My English ear too, but ISO are based in Switzerland.  They do things
differently there ;)

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

[weewx-user] Communication error on Terminal with Davis Vantage Pro 2

[gjr80]

You need to stop WeeWX before running wee_device - according to the log extract 
you posted both WeeWX and wee_device are competing to talk to the console. 
wee_device happens to work sometimes if it tries to communicate with the 
console when WeeWX is not.

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/d3a64b2d-8273-4c1b-9b48-b87dfe2b112a%40googlegroups.com.

[weewx-user] Communication error on Terminal with Davis Vantage Pro 2

[gjr80]

Did you stop WeeWX before running wee_device?

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/f5e3f7f2-be78-4e07-bc80-eb633fc4e955%40googlegroups.com.

[weewx-user] Communication error on Terminal with Davis Vantage Pro 2

[Geni]

Why do I usually get this error on the console? 
After the second or third attempt the info is listed?

sudo wee_device --info
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
Unable to wake up console... sleeping
Unable to wake up console... retrying
Traceback (most recent call last):
  File "/usr/bin/wee_device", line 66, in 
main()
  File "/usr/bin/wee_device", line 62, in main
device.configure(config_dict)
  File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
self.do_options(options, parser, config_dict, prompt)
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1973, in do_options
station = Vantage(**config_dict[DRIVER_NAME])
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 488, in __init__
self._setup()
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1290, in _setup
unit_bits  = self._getEEPROM_value(0x29)[0]
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1376, in 
_getEEPROM_value
raise weewx.RetriesExceeded("While getting EEPROM data value at address 
0x%X" % offset)
weewx.RetriesExceeded: While getting EEPROM data value at address 0x29

syslog:
Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: SerialException on read.
Jan  1 09:23:45 Wetter-Raspi weewx[3001]:  device reports readiness 
to read but returned no data (device disconnected or multiple access on port
?)
Jan  1 09:23:45 Wetter-Raspi weewx[3001]:  Is there a competing 
process running??
Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: LOOP try #1; error: 
device reports readiness to read but returned no data (device disconnected 
or multiple access on port?)
Jan  1 09:23:45 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP 
packets.
Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Retry  #0 failed
Jan  1 09:23:49 Wetter-Raspi wee_device[6419]: vantage: No  received 
from console
Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Rude wake up of console 
successful
Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: No  received from 
console
Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: LOOP try #2; error: No 
 received from Vantage console
Jan  1 09:23:49 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP 
packets.
Jan  1 09:23:49 Wetter-Raspi wee_device[6419]: vantage: No  received 
from console
Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: Retry  #0 failed
Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: SerialException on read.
Jan  1 09:23:51 Wetter-Raspi weewx[3001]:  device reports readiness 
to read but returned no data (device disconnected or multiple access on port
?)
Jan  1 09:23:51 Wetter-Raspi weewx[3001]:  Is there a competing 
process running??
Jan  1 09:23:51 Wetter-Raspi weewx[3001]: vantage: Retry  #1 failed
Jan  1 09:23:55 Wetter-Raspi weewx[3001]: vantage: Retry  #2 failed
Jan  1 09:23:55 Wetter-Raspi wee_device[6419]: vantage: SerialException on 
read.
Jan  1 09:23:55 Wetter-Raspi wee_device[6419]:  device reports 
readiness to read but returned no data (device disconnected or multiple 
access on port?)
Jan  1 09:23:55 Wetter-Raspi wee_device[6419]:  Is there a 
competing process running??
Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Retry  #3 failed
Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Unable to wake up console
Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: LOOP try #3; error: 
Unable to wake up Vantage console
Jan  1 09:23:56 Wetter-Raspi weewx[3001]: vantage: Requesting 200 LOOP 
packets.
Jan  1 09:23:56 Wetter-Raspi wee_device[6419]: vantage: Unable to pass 
CRC16 check while getting data
Jan  1 09:23:56 Wetter-Raspi wee_device[6419]: vantage: Max retries 
exceeded while getting EEPROM data at address 0x29

Regards
Geni

-- 
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/79366e15-0131-4268-9d8e-bc7057480fe9%40googlegroups.com.

[weewx-user] Re: StdReport thread has been terminated every day at 00:20 (1927, 'Connection was killed')

[Geni]

Hyperbackup runs on my synology and weewx on a Raspberry, so Hyperbackup 
can't stop and start weewx!
I think it's better if weewx is fault tolerant, Snology is rebooted 
occasionally during updates, then there is no database connection, the 
HTML_ROOT is offline and the FTP path is not found.

Am Mittwoch, 1. Januar 2020 09:29:50 UTC+1 schrieb Andrew Milner:
>
> or you could stop weewx for the hyperbackup period and resume when it is 
> complete.  weewx will then do 'catchup' from loggers and all should be 
> tickety-boo .
>
>
>
> On Wednesday, 1 January 2020 10:21:16 UTC+2, Geni wrote:
>>
>> Hi, Thomas.
>> The hint that the error code 1927 comes from MariaDB, I knew immediately 
>> where to look for it!
>> Now at this time a hyperbackup job is running on my synologe which also 
>> contained the application MariaDB, I have removed it and this night no 
>> error messages.
>>
>> Summary:
>> The backup stops the database service for a short moment and if that's 
>> exactly when Weewx wants to access it, it won't work.
>> My suggestion would be if weewx doesn't get a database connection it will 
>> wait for the next interval but without killing the process.
>> In my case this would be 1 or 2 intervals and then the missing records 
>> would be read in and nobody would notice anything.
>>
>> Regards
>> Geni
>>
>> PS: This error occurred very rarely with the Raspberry PI2?
>>
>>
>> Am Dienstag, 31. Dezember 2019 11:01:10 UTC+1 schrieb Geni:
>>>
>>> Hello, 
>>> Since I replaced the Raspberry PI 2 with a Raspberry PI 3+ this problem 
>>> occurs every night, before only sporadically.
>>> In use:
>>> Raspberry 3+ mit Raspbian Buster Lite
>>> Externe SqlDB (MariaDB 10) 
>>> David Vantage Pro2 Version: 3.83
>>> Weewx 3.9.2-1
>>>
>>> Every night at exactly 00:20, it stops. The report at 00:10 is still made
>>> debug-log:
>>> Dec 31 00:10:55 Wetter-Raspi weewx[889]: reportengine: Report 'RSYNC' 
>>> not enabled. Skipping.
>>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Requesting 200 LOOP 
>>> packets.
>>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Gentle wake up of 
>>> console successful
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: StdReport thread has 
>>> been terminated
>>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: engine: Debug is 1
>>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: engine: Initializing engine
>>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Driver version is 
>>> 3.1.1
>>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Opened up serial port 
>>> /dev/ttyUSB0; baud 19200; timeout 4.00
>>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Gentle wake up of 
>>> console successful
>>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Hardware type is 16
>>> Dec 31 07:44:11 Wetter-Raspi weewx[3001]: vantage: ISS ID is 1
>>> Dec 31 07:44:11 Wetter-Raspi weewx[3001]: vantage: Hardware name: 
>>> Vantage Pro2
>>>  
>>> syslog:
>>> Dec 31 00:17:01 Wetter-Raspi CRON[1919]: (root) CMD (   cd / && 
>>> run-parts --report /etc/cron.hourly)
>>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Requesting 200 LOOP 
>>> packets.
>>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Gentle wake up of 
>>> console successful
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Main loop exiting. 
>>> Shutting engine down.
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Shutting down StdReport 
>>> thread
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: StdReport thread has 
>>> been terminated
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Caught unrecoverable 
>>> exception in engine:
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   (1927, 'Connection 
>>> was killed')
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   Traceback (most 
>>> recent call last):
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 894, in main
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   engine.run()
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 191, in run
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   
>>> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>>> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   callback(event)
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>>> "/usr/share/weewx/weewx/wxservices.py", line 45, in new_loop_packet
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   
>>> self.calc.do_calculations(event.packet, 'loop')
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>>> "/usr/share/weewx/weewx/wxservices.py", line 191, in do_calculations
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   getattr(self, 
>>> 'calc_' + obs)(data_us, data_type)
>>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>>> "/usr/

[weewx-user] Re: StdReport thread has been terminated every day at 00:20 (1927, 'Connection was killed')

[Andrew Milner]

or you could stop weewx for the hyperbackup period and resume when it is 
complete.  weewx will then do 'catchup' from loggers and all should be 
tickety-boo .



On Wednesday, 1 January 2020 10:21:16 UTC+2, Geni wrote:
>
> Hi, Thomas.
> The hint that the error code 1927 comes from MariaDB, I knew immediately 
> where to look for it!
> Now at this time a hyperbackup job is running on my synologe which also 
> contained the application MariaDB, I have removed it and this night no 
> error messages.
>
> Summary:
> The backup stops the database service for a short moment and if that's 
> exactly when Weewx wants to access it, it won't work.
> My suggestion would be if weewx doesn't get a database connection it will 
> wait for the next interval but without killing the process.
> In my case this would be 1 or 2 intervals and then the missing records 
> would be read in and nobody would notice anything.
>
> Regards
> Geni
>
> PS: This error occurred very rarely with the Raspberry PI2?
>
>
> Am Dienstag, 31. Dezember 2019 11:01:10 UTC+1 schrieb Geni:
>>
>> Hello, 
>> Since I replaced the Raspberry PI 2 with a Raspberry PI 3+ this problem 
>> occurs every night, before only sporadically.
>> In use:
>> Raspberry 3+ mit Raspbian Buster Lite
>> Externe SqlDB (MariaDB 10) 
>> David Vantage Pro2 Version: 3.83
>> Weewx 3.9.2-1
>>
>> Every night at exactly 00:20, it stops. The report at 00:10 is still made
>> debug-log:
>> Dec 31 00:10:55 Wetter-Raspi weewx[889]: reportengine: Report 'RSYNC' not 
>> enabled. Skipping.
>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Requesting 200 LOOP 
>> packets.
>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Gentle wake up of 
>> console successful
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: StdReport thread has 
>> been terminated
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: engine: Debug is 1
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: engine: Initializing engine
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Driver version is 3.1.1
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Opened up serial port 
>> /dev/ttyUSB0; baud 19200; timeout 4.00
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Gentle wake up of 
>> console successful
>> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Hardware type is 16
>> Dec 31 07:44:11 Wetter-Raspi weewx[3001]: vantage: ISS ID is 1
>> Dec 31 07:44:11 Wetter-Raspi weewx[3001]: vantage: Hardware name: Vantage 
>> Pro2
>>  
>> syslog:
>> Dec 31 00:17:01 Wetter-Raspi CRON[1919]: (root) CMD (   cd / && run-parts 
>> --report /etc/cron.hourly)
>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Requesting 200 LOOP 
>> packets.
>> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Gentle wake up of 
>> console successful
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Main loop exiting. 
>> Shutting engine down.
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Shutting down StdReport 
>> thread
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: StdReport thread has 
>> been terminated
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Caught unrecoverable 
>> exception in engine:
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   (1927, 'Connection was 
>> killed')
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   Traceback (most recent 
>> call last):
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/engine.py", line 894, in main
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   engine.run()
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/engine.py", line 191, in run
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   
>> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   callback(event)
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/wxservices.py", line 45, in new_loop_packet
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   
>> self.calc.do_calculations(event.packet, 'loop')
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/wxservices.py", line 191, in do_calculations
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   getattr(self, 
>> 'calc_' + obs)(data_us, data_type)
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/wxservices.py", line 228, in calc_pressure
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   data['dateTime'], 
>> interval)
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
>> "/usr/share/weewx/weewx/wxservices.py", line 404, in _get_temperature_12h
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   record = 
>> dbmanager.getRecord(ts12, max_delta=self.max_delta_12h)
>> Dec 31 00:20:01 Wetter-Raspi weewx[889]: F

[weewx-user] Re: StdReport thread has been terminated every day at 00:20 (1927, 'Connection was killed')

[Geni]

Hi, Thomas.
The hint that the error code 1927 comes from MariaDB, I knew immediately 
where to look for it!
Now at this time a hyperbackup job is running on my synologe which also 
contained the application MariaDB, I have removed it and this night no 
error messages.

Summary:
The backup stops the database service for a short moment and if that's 
exactly when Weewx wants to access it, it won't work.
My suggestion would be if weewx doesn't get a database connection it will 
wait for the next interval but without killing the process.
In my case this would be 1 or 2 intervals and then the missing records 
would be read in and nobody would notice anything.

Regards
Geni

PS: This error occurred very rarely with the Raspberry PI2?


Am Dienstag, 31. Dezember 2019 11:01:10 UTC+1 schrieb Geni:
>
> Hello, 
> Since I replaced the Raspberry PI 2 with a Raspberry PI 3+ this problem 
> occurs every night, before only sporadically.
> In use:
> Raspberry 3+ mit Raspbian Buster Lite
> Externe SqlDB (MariaDB 10) 
> David Vantage Pro2 Version: 3.83
> Weewx 3.9.2-1
>
> Every night at exactly 00:20, it stops. The report at 00:10 is still made
> debug-log:
> Dec 31 00:10:55 Wetter-Raspi weewx[889]: reportengine: Report 'RSYNC' not 
> enabled. Skipping.
> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Requesting 200 LOOP 
> packets.
> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Gentle wake up of 
> console successful
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: StdReport thread has been 
> terminated
> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: engine: Debug is 1
> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: engine: Initializing engine
> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Driver version is 3.1.1
> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Opened up serial port 
> /dev/ttyUSB0; baud 19200; timeout 4.00
> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Gentle wake up of 
> console successful
> Dec 31 07:44:10 Wetter-Raspi weewx[3001]: vantage: Hardware type is 16
> Dec 31 07:44:11 Wetter-Raspi weewx[3001]: vantage: ISS ID is 1
> Dec 31 07:44:11 Wetter-Raspi weewx[3001]: vantage: Hardware name: Vantage 
> Pro2
>  
> syslog:
> Dec 31 00:17:01 Wetter-Raspi CRON[1919]: (root) CMD (   cd / && run-parts 
> --report /etc/cron.hourly)
> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Requesting 200 LOOP 
> packets.
> Dec 31 00:17:15 Wetter-Raspi weewx[889]: vantage: Gentle wake up of 
> console successful
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Main loop exiting. 
> Shutting engine down.
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Shutting down StdReport 
> thread
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: StdReport thread has been 
> terminated
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: engine: Caught unrecoverable 
> exception in engine:
> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   (1927, 'Connection was 
> killed')
> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   Traceback (most recent 
> call last):
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
> "/usr/share/weewx/weewx/engine.py", line 894, in main
> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   engine.run()
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
> "/usr/share/weewx/weewx/engine.py", line 191, in run
> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   
> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
> "/usr/share/weewx/weewx/engine.py", line 224, in dispatchEvent
> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   callback(event)
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
> "/usr/share/weewx/weewx/wxservices.py", line 45, in new_loop_packet
> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   
> self.calc.do_calculations(event.packet, 'loop')
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
> "/usr/share/weewx/weewx/wxservices.py", line 191, in do_calculations
> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   getattr(self, 
> 'calc_' + obs)(data_us, data_type)
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
> "/usr/share/weewx/weewx/wxservices.py", line 228, in calc_pressure
> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   data['dateTime'], 
> interval)
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
> "/usr/share/weewx/weewx/wxservices.py", line 404, in _get_temperature_12h
> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   record = 
> dbmanager.getRecord(ts12, max_delta=self.max_delta_12h)
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
> "/usr/share/weewx/weewx/manager.py", line 370, in getRecord
> Dec 31 00:20:01 Wetter-Raspi weewx[889]:   (time_start_ts, 
> time_stop_ts, timestamp))
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: File 
> "/usr/share/weewx/weedb/mysql.py", line 49, in guarded_fn
> Dec 31 00:20:01 Wetter-Raspi weewx[889]: