Re: [weewx-user] MQTT lagging

[T Reid]

Thank you for your very thorough response, Greg.  In response to your 
questions and suggestions:

   - I am publishing aggregate data. Here is the MQTT section of my 
   weeewx.conf:

[[MQTT]]
server_url = mqtts://user:passw...@mqtt.example.com:8883/
topic = weather/belmont
binding = archive, loop
aggregation = aggregate
[[[tls]]]
ca_certs = /etc/ssl/certs/ca-certificates.crt

   - I looked at the traffic with mosquitto_sub, and the incoming weather 
   data right now is from 45 minutes ago.
   - I'm afraid that I don't know what running "netstat ... to look for 
   full output queues" means.
   - What am I looking for in the logs? I see new "INFO weewx.restx: MQTT" 
   entries every two seconds or so. Each entry says that it has published a 
   record with a time stamp from about 45 minutes ago.
   - What I am seeing on my weather page using the Belchertown skin are 
   charts built using current archive records (updated every five minutes), 
   but  "station observations" at the top of the page using MQTT delivered 
   loop records that reflect weather data from 45 minutes ago.  Earlier today, 
   the lag was only 30 minutes.  The lag grows over time.
   - I restarted the broker, and the MQTT weather data on the web page, on 
   mosquitto_sub, and in the weewx logs is still running 45 minutes behind.  
   No change. 
   - I run my own broker using mosquitto running on a droplet on Digital 
   Ocean.  My copy of weewx is running on a raspberry pi that is hooked up to 
   the datalogger on my Davis Vantage Pro2 console with a USB cable.

To my eyes, it looks like weewx is running further and further behind in 
publishing loop records over MQTT, which makes no sense to me.

On Sunday, October 25, 2020 at 7:43:08 AM UTC-7 Greg Troxel wrote:

>
> T Reid  writes:
>
> > I am using the MQTT add-in to pipe real time loop entries from my Davis 
> > Vantage Pro into the Belchertown skin, using the standard instructions 
> for 
> > that skin. It generally works great. But every couple of days the MQTT 
> > feed will fall behind, sometimes by as much as an hour or more. To fix 
> it, 
> > I have to restart weewx. Any idea what might be happening? I am running 
> > weewx 4.1.1 with Belchertown 1.1.
>
> My suggestions:
>
> explain if you are publishing aggregate or individual data
>
> Use mosquitto_sub (from mosquitto) on the broker to watch the traffic.
>
> Run netstat on the weewx host to look for full output queues
>
> read the weewx logs
>
> explain what you are seeing more precisely than saying "fall behind".
>
> next time it fails, restart your broker instead of weewx and see what
> happens. That will cause the weewx->broker connection to get shut
> down and weewx/mqtt will open a new one.
>
> if you are using some cloud broker, run your own
>
>

-- 
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/75afa842-2d50-4e1f-96ff-21799bc73b5cn%40googlegroups.com.

[weewx-user] RPI + rtl_sdr on weewx 4.2.0

[Mario St-Gelais]

I am setting up weewx on RPI3 using rtl_433.
I have output as per sample:
Oct 27 20:22:09 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:12 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:15 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:18 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:21 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:25 raspberrypi weewx[6774] DEBUG user.sdr: lines=['{"time" : 
"2020-10-28 00:22:21", "model" : "Acurite-5n1", "message_type" : 56, "id" : 
1601, "channel" : "A", "sequence_num" : 0, "battery_ok" : 1, 
"wind_avg_km_h" : 0.000, "temperature_F" : 26.200, "humidity" : 84, "mic" : 
"CHECKSUM"}\n', '{"time" : "2020-10-28 00:22:21", "model" : "Acurite-5n1", 
"message_type" : 56, "id" : 1601, "channel" : "A", "sequence_num" : 1, 
"battery_ok" : 1, "wind_avg_km_h" : 0.000, "temperature_F" : 26.200, 
"humidity" : 84, "mic" : "CHECKSUM"}\n', '{"time" : "2020-10-28 00:22:21", 
"model" : "Acurite-5n1", "message_type" : 56, "id" : 1601, "channel" : "A", 
"sequence_num" : 2, "battery_ok" : 1, "wind_avg_km_h" : 0.000, 
"temperature_F" : 26.200, "humidity" : 84, "mic" : "CHECKSUM"}\n']
Oct 27 20:22:29 raspberrypi weewx[6774] DEBUG user.sdr: lines=['{"time" : 
"2020-10-28 00:22:25", "model" : "LaCrosse-TX141THBv2", "id" : 50, 
"channel" : 0, "battery_ok" : 1, "temperature_C" : -0.600, "humidity" : 60, 
"test" : "No"}\n']
Oct 27 20:22:29 raspberrypi weewx[6774] DEBUG user.sdr: parse_json: unknown 
model LaCrosse-TX141THBv2
Oct 27 20:22:29 raspberrypi weewx[6774] DEBUG user.sdr: punt unrecognized 
line '{"time" : "2020-10-28 00:22:25", "model" : "LaCrosse-TX141THBv2", 
"id" : 50, "channel" : 0, "battery_ok" : 1, "temperature_C" : -0.600, 
"humidity" : 60, "test" : "No"}#012'
Oct 27 20:22:32 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:35 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:38 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:44 raspberrypi weewx[6774] DEBUG user.sdr: lines=['{"time" : 
"2020-10-28 00:22:40", "model" : "Acurite-5n1", "message_type" : 49, "id" : 
1601, "channel" : "A", "sequence_num" : 0, "battery_ok" : 1, 
"wind_avg_km_h" : 0.000, "wind_dir_deg" : 270.000, "rain_in" : 1.400, "mic" 
: "CHECKSUM"}\n', '{"time" : "2020-10-28 00:22:40", "model" : 
"Acurite-5n1", "message_type" : 49, "id" : 1601, "channel" : "A", 
"sequence_num" : 1, "battery_ok" : 1, "wind_avg_km_h" : 0.000, 
"wind_dir_deg" : 270.000, "rain_in" : 1.400, "mic" : "CHECKSUM"}\n', 
'{"time" : "2020-10-28 00:22:40", "model" : "Acurite-5n1", "message_type" : 
49, "id" : 1601, "channel" : "A", "sequence_num" : 2, "battery_ok" : 1, 
"wind_avg_km_h" : 0.000, "wind_dir_deg" : 270.000, "rain_in" : 1.400, "mic" 
: "CHECKSUM"}\n']
Oct 27 20:22:47 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:50 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:53 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:56 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]
Oct 27 20:22:59 raspberrypi weewx[6774] DEBUG user.sdr: lines=[]

Nothing is going in the sqlite db.  wee_reports only creates graphics, no 
index.html

weewx.conf:
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2020 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 = /home/weewx

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

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

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

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = Maison

# Latitude in decimal degrees. Negative for southern hemisphere
latitude = ##
# Longitude in decimal degrees. Negative for western hemisphere.
longitude = ###

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 100, meter# Choose 'foot' or 'meter' for unit

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

# 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

# 

Re: [weewx-user] Error Message when generating Archive

[Tom Keffer]

Can you take a look inside your database? What is the result of:

*sqlite3 /var/lib/weewx/weewx.sdb*
sqlite> *SELECT tbl_name FROM sqlite_master WHERE type='table';*
sqlite> *.quit*

This will tell us whether the table archive_day_wind exists in your
database.

-tk



On Tue, Oct 27, 2020 at 2:20 PM Alessandro Del Prete <
alessandro.delpr...@gmail.com> wrote:

> Hi,
>
> I have the same issue, it's a brand new installation of weewx 4.1.1,
> working since a month with a belchertown skin and a weatherflow tempest.
>
> Today I was checking weewx.log and I noticed this:
>
> Oct 27 21:39:24 ubuntu weewx[59297] DEBUG weewx.manager: Daily summary
> version is 2.0
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: Generate
> failed with exception ''
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> Ignoring template /etc/weewx/skins/Seasons/NOAA/NOAA-%Y-%m.txt.tmpl
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> Reason: cannot find 'count' while searching for 'day.wind.count.raw'
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> Traceback (most recent call last):
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> unicode_string = compiled_template.respond()
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> File "_etc_weewx_skins_Seasons_NOAA_NOAA__Y__m_txt_tmpl.py", line 431, in
> respond
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> NameMapper.NotFound: cannot find 'count' while searching for
> 'day.wind.count.raw'
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: Generate
> failed with exception ''
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> Ignoring template /etc/weewx/skins/Seasons/NOAA/NOAA-%Y-%m.txt.tmpl
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> Reason: cannot find 'count' while searching for 'day.wind.count.raw'
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> Traceback (most recent call last):
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> unicode_string = compiled_template.respond()
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> File "_etc_weewx_skins_Seasons_NOAA_NOAA__Y__m_txt_tmpl.py", line 431, in
> respond
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
> NameMapper.NotFound: cannot find 'count' while searching for
> 'day.wind.count.raw'
>
> Then I found your reply to solve the problem. I checked the DataBindings
> section, and everything's like you suggested, no mixing (it was a new
> installation), so I don't know why the issue came up only after some time.
>
> Is it possible to solve the problem without deleting the database?
>
> Thanks for any advice on this.
>
> Alessandro
>
> On Thursday, September 17, 2020 at 8:20:48 PM UTC+2 tke...@gmail.com
> wrote:
>
>> The reason why this can occur is a rather technical one, but has to do
>> with mixing the older, V3.x, way of specifying a schema, and the newer,
>> V4.x way.
>>
>> 1. Stop weewx
>>
>> 2. Assuming there is nothing valuable in it, delete the archive
>> /var/lib/weewx/weewx.sdb
>>
>> 3. Make sure your [DataBindings] section looks like this. Pay attention
>> to the highlighted areas.
>>
>> [DataBindings]
>>
>> [[wx_binding]]
>> # The database must match one of the sections in [Databases].
>> # This is likely to be the only option you would want to change.
>> database = archive_sqlite
>> # The name of the table within the database
>> table_name = archive
>> # The manager handles aggregation of data for historical summaries
>> manager = weewx.manager.DaySummaryManager
>> # The schema defines the structure of the database.
>> # It is *only* used when the database is created.
>> schema = schemas.wview_extended.schema
>>
>> 4. Restart weewx.
>>
>> -tk
>>
>>
>>
>> On Thu, Sep 17, 2020 at 11:00 AM 'joh@googlemail.com' via weewx-user
>>  wrote:
>>
>>> Hi,
>>>
>>> After two tries with cheaper Weather Stations which failed due to
>>> Quality I bought now a Davis Vantage Pro2 Wireless with a Weatherlink Live
>>> Adapter
>>>
>>> I have setup now a new Weewx Installation and had it running for some
>>> days with "simulator" without any issues.
>>>
>>> Now I got my davis and I have configured it immediatly.
>>>
>>> But unfortunatley I am getting now the following error:
>>>
>>> *Sep 17 19:55:17 weewx-test weewx[23751] ERROR weewx.cheetahgenerator:
>>> Generate failed with exception ''*
>>> *Sep 17 19:55:17 weewx-test weewx[23751

[weewx-user] Re: Version 4.2.0 ready

[Greg from Oz]

Hi Tom,

I restored from snapshot.
I edited /etc/weewx.conf and changed version = 4.2.0a1 to version = 4.2.1 
and then ran  dpkg -i python3-weewx_4.2.0-1_all.deb 

 
I also selected N when prompted to change the conf file.
Now it seems to have installed correctly and it is up and running.

https://weather.ubeaut.work/

Don't know what happened but I did try the upgrade twice with the same 
results both times until I changed the version number in the weewx.conf 
file.



On Tuesday, 27 October 2020 at 23:14:04 UTC+11 tke...@gmail.com wrote:

> Some new features, fixes some bugs.
>
> See the *Upgrade Guide * for 
> instructions on how to upgrade.
>
> CHANGE LOG
>
> CHANGES COMING! This is the last release that will support the LaCrosse 
> WS23xx,
> Oregon WMR200 and WMR300 stations. In the future, they will be published as
> unsupported extensions.
>
> Made it easier to add new, derived types via StdWXCalculate. Fixes issue #491.
>
> Changed the tag system slightly in order to make it possible for the XTypes
> system to add new aggregations that take an argument.
>
> Added the new data types in the extended_wview schema to the WeeWX types
> system. Fixes issue #613.
>
> Added ability to label left, right or both y-axes of graphs.  PR#610.
> Fixes issue #609. Thanks to user Brent Fraser!
>
> Added units and labels for the lightning data types.
>
> Fixed problem where threads attempt to access non-existent database. Fixes
> issue #579.
>
> Fixed problem that caused reporting units to revert to US if they were in a
> mixed unit system. Fixes issue #576.
>
> Fixed problem that could cause the station registry to fail if given a 
> location
> with a non-ASCII location name.
>
> Changed TE923 bucket size from 0.02589 inches to 1/36 of an inch
> (0.0278 in). PR #575. Fixes issue #574. Thanks to user Timothy!
>
> Undocumented option retry_certificate has been renamed to retry_ssl, and now
> covers all SSL errors (not just certificate errors). Fixes issue #569. Thanks
> to user Eric!
>
> Fixed problem caused by specifying a [Logging]/[[formatters]] section in
> weewx.conf that uses interpolated variables.
>
> Fixed problem in the Vantage driver that resulted in incorrect sunrise/sunset
> being included in loop packets when run under Python 3. Thanks to users 
> Constantine and Jacques!
>
> Improved auto-scaling of plot axes.
>
> Fixed problem where aggregates of windvec and windgustvec returned the 
> aggregate
> since start of day, not the start of the aggregation period. Fixes issue #590.
>
> New unit "beaufort", included in "group_speed". Treating beaufort as a 
> separate
> type has been deprecated. Fixes issue #591.
>
> New unit "kPa", included in "group_pressure". Fixes issue #596.
>
> Fixed bug in the simulator. Made it easier to subclass class Simulator.
>
> Expressions in StdCalibration are now ordered. Later corrections can depend on
> earlier corrections.
>
> Fixed problem under Python 2, where option 'none' could cause exception.
> PR #597. Thanks to user Clément!
>
> Fixed problem with ws23xx driver under Python 3 that caused it to crash.
>
> Use a more modern formula for heat index. Fixes issue #601. Thanks to
> user Peter Q!
>
> Allow overriding the data binding when using iterators. Fixes issue #580.
>
> Fixed problem where old daily summaries may not have a version number.
>
> Fixed problem in WMR200 driver where missing UV reports as index 255.
>
> Added option 'force_direction' for working around a WU bug. Fixes issue #614.
>
>

-- 
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/1c5bc974-39ed-4c24-b6a3-61fb337ce4fdn%40googlegroups.com.

Re: [weewx-user] Version 4.2.0 ready

[Tom Keffer]

Unfortunately, when the configuration file manager we use, ConfigObj,
writes a file out, it drops the quotes.

It shouldn't matter unless you use the hash symbol ('#') in your password.

On Tue, Oct 27, 2020 at 3:09 PM PJO  wrote:

> Update from v3.9.2 on Pi2 w FineOffset WH1080 completed OK using apt.
>
> However, I noticed quotes were removed from passwords. Is this how they
> should be now? (Perhaps it wasn't with WeeWX, but I do remember having to
> add quotes to passwords in a .conf file at some point.)
>
> On Tuesday, October 27, 2020 at 2:32:04 PM UTC phil@gmail.com wrote:
>
>> Installed on my Pi3 updated using setup.py method on existing install
>> running python3.
>> Weather station Vantage Vue.
>> All working fine.
>> Many thanks.
>> Phil
>>
>> On Tuesday, October 27, 2020 at 1:47:53 PM UTC tke...@gmail.com wrote:
>>
>>> The drivers are being dropped because of their complexity and lack of
>>> use. With an all-volunteer effort, we have to husband our resources.
>>> Something has to go.
>>>
>>> Python 3 is definitely very mature and 100% "baked." No reason not to
>>> use it, if you can.
>>>
>>> No plans to drop Python 2.
>>>
>>> -tk
>>>
>>>
>>>
>>> On Tue, Oct 27, 2020 at 6:21 AM Greg Troxel  wrote:
>>>

   CHANGES COMING! This is the last release that will support the
 LaCrosse WS23xx,
   Oregon WMR200 and WMR300 stations. In the future, they will be
 published as
   unsupported extensions.

 This is definitely not a complaint, and sorry if I have failed to notice
 list traffic about this.

 I don't have any of those stations, so this won't affect me.  But given
 the overall "weewx way", I find this surprising.  I wonder if they are
 troubled and nobody has volunteered to fix,if there is some reason they
 are too hard to keep working, or if there are too many unreasonable
 demands for support, or something else?


 I'm also curious if there is a plan/timeline for dropping python 2.7
 support.  (I haven't personally moved to 3, partly because it has seemed
 not 100% baked, and partly I just haven't.  With this release, it seems
 python 3 is perhaps the standard approach, and certainly not
 experimental.

 Greg

>>> --
> 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/1970da9b-2c88-4b75-bfbe-d1cfc103d348n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAdWEdqkJVPpus4s8pX9DMRJMFueCW15fXtg_-fPMxykA%40mail.gmail.com.

Re: [weewx-user] Error Message when generating Archive

[Alessandro Del Prete]

Because I used it as the "default" skin for now, I'm still testing things, 
and it was useful to double check things.

I can disable it, but this does not solve the problem, it bypasses it. I 
still don't know what caused the problem, maybe there's a bad configuration 
and that was only a symptom, that's why I asked.

Thanks for the suggestion, if there's no solution I'll disable that skin.

On Tuesday, October 27, 2020 at 11:12:04 PM UTC+1 vince wrote:

> On Tuesday, October 27, 2020 at 2:20:33 PM UTC-7, Alessandro Del Prete 
> wrote:
>
>> I have the same issue, it's a brand new installation of weewx 4.1.1, 
>> working since a month with a belchertown skin and a weatherflow tempest.
>>
>> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: 
>> Generate failed with exception ''
>> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
>> Ignoring template /etc/weewx/skins/Seasons/NOAA/NOAA-%Y-%m.txt.tmpl
>
>
> If you're running the Belchertown skin, why are you 'also' still running 
> the default Seasons skin ?
>
> I'd just disable Seasons in weewx.conf and restart weewx if you don't need 
> 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/4184a416-b70e-4416-a509-68bdce3bc238n%40googlegroups.com.

Re: [weewx-user] Error Message when generating Archive

[vince]

On Tuesday, October 27, 2020 at 2:20:33 PM UTC-7, Alessandro Del Prete 
wrote:
>
> I have the same issue, it's a brand new installation of weewx 4.1.1, 
> working since a month with a belchertown skin and a weatherflow tempest.
>
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: Generate 
> failed with exception ''
> Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
> Ignoring template /etc/weewx/skins/Seasons/NOAA/NOAA-%Y-%m.txt.tmpl


If you're running the Belchertown skin, why are you 'also' still running 
the default Seasons skin ?

I'd just disable Seasons in weewx.conf and restart weewx if you don't need 
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/c06d9729-dabe-40c1-aaca-6e065d468762o%40googlegroups.com.

Re: [weewx-user] Version 4.2.0 ready

[PJO]

Update from v3.9.2 on Pi2 w FineOffset WH1080 completed OK using apt. 

However, I noticed quotes were removed from passwords. Is this how they 
should be now? (Perhaps it wasn't with WeeWX, but I do remember having to 
add quotes to passwords in a .conf file at some point.)

On Tuesday, October 27, 2020 at 2:32:04 PM UTC phil@gmail.com wrote:

> Installed on my Pi3 updated using setup.py method on existing install 
> running python3.
> Weather station Vantage Vue.
> All working fine.
> Many thanks.
> Phil
>
> On Tuesday, October 27, 2020 at 1:47:53 PM UTC tke...@gmail.com wrote:
>
>> The drivers are being dropped because of their complexity and lack of 
>> use. With an all-volunteer effort, we have to husband our resources. 
>> Something has to go.
>>
>> Python 3 is definitely very mature and 100% "baked." No reason not to use 
>> it, if you can.
>>
>> No plans to drop Python 2. 
>>
>> -tk
>>
>>
>>
>> On Tue, Oct 27, 2020 at 6:21 AM Greg Troxel  wrote:
>>
>>>
>>>   CHANGES COMING! This is the last release that will support the 
>>> LaCrosse WS23xx,
>>>   Oregon WMR200 and WMR300 stations. In the future, they will be 
>>> published as
>>>   unsupported extensions.
>>>
>>> This is definitely not a complaint, and sorry if I have failed to notice
>>> list traffic about this.
>>>
>>> I don't have any of those stations, so this won't affect me.  But given
>>> the overall "weewx way", I find this surprising.  I wonder if they are
>>> troubled and nobody has volunteered to fix,if there is some reason they
>>> are too hard to keep working, or if there are too many unreasonable
>>> demands for support, or something else?
>>>
>>>
>>> I'm also curious if there is a plan/timeline for dropping python 2.7
>>> support.  (I haven't personally moved to 3, partly because it has seemed
>>> not 100% baked, and partly I just haven't.  With this release, it seems
>>> python 3 is perhaps the standard approach, and certainly not
>>> experimental.
>>>
>>> Greg
>>>
>>

-- 
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/1970da9b-2c88-4b75-bfbe-d1cfc103d348n%40googlegroups.com.

[weewx-user] Re: Version 4.2.0 ready

[Greg from Oz]

Hi Tom,
I upgraded from 4.2.0.0a1 using dpkg -i python3-weewx_4.2.0-1_all.deb 

 
There was a warning saying I was downgrading.
The install worked but when I looked at the logs it didn't look right. The 
mqtt was sending every second.
I selected N when prompted to change the weewx.conf file.
The install seems to have changed parts of the weewx.con file as my 
location is back to santas workshop but other parts like my rsync is still 
there.
I have reverted back as I can snapshot so I will look at it further later 
today.

Thanks

On Tuesday, 27 October 2020 at 23:14:04 UTC+11 tke...@gmail.com wrote:

> Some new features, fixes some bugs.
>
> See the *Upgrade Guide * for 
> instructions on how to upgrade.
>
> CHANGE LOG
>
> CHANGES COMING! This is the last release that will support the LaCrosse 
> WS23xx,
> Oregon WMR200 and WMR300 stations. In the future, they will be published as
> unsupported extensions.
>
> Made it easier to add new, derived types via StdWXCalculate. Fixes issue #491.
>
> Changed the tag system slightly in order to make it possible for the XTypes
> system to add new aggregations that take an argument.
>
> Added the new data types in the extended_wview schema to the WeeWX types
> system. Fixes issue #613.
>
> Added ability to label left, right or both y-axes of graphs.  PR#610.
> Fixes issue #609. Thanks to user Brent Fraser!
>
> Added units and labels for the lightning data types.
>
> Fixed problem where threads attempt to access non-existent database. Fixes
> issue #579.
>
> Fixed problem that caused reporting units to revert to US if they were in a
> mixed unit system. Fixes issue #576.
>
> Fixed problem that could cause the station registry to fail if given a 
> location
> with a non-ASCII location name.
>
> Changed TE923 bucket size from 0.02589 inches to 1/36 of an inch
> (0.0278 in). PR #575. Fixes issue #574. Thanks to user Timothy!
>
> Undocumented option retry_certificate has been renamed to retry_ssl, and now
> covers all SSL errors (not just certificate errors). Fixes issue #569. Thanks
> to user Eric!
>
> Fixed problem caused by specifying a [Logging]/[[formatters]] section in
> weewx.conf that uses interpolated variables.
>
> Fixed problem in the Vantage driver that resulted in incorrect sunrise/sunset
> being included in loop packets when run under Python 3. Thanks to users 
> Constantine and Jacques!
>
> Improved auto-scaling of plot axes.
>
> Fixed problem where aggregates of windvec and windgustvec returned the 
> aggregate
> since start of day, not the start of the aggregation period. Fixes issue #590.
>
> New unit "beaufort", included in "group_speed". Treating beaufort as a 
> separate
> type has been deprecated. Fixes issue #591.
>
> New unit "kPa", included in "group_pressure". Fixes issue #596.
>
> Fixed bug in the simulator. Made it easier to subclass class Simulator.
>
> Expressions in StdCalibration are now ordered. Later corrections can depend on
> earlier corrections.
>
> Fixed problem under Python 2, where option 'none' could cause exception.
> PR #597. Thanks to user Clément!
>
> Fixed problem with ws23xx driver under Python 3 that caused it to crash.
>
> Use a more modern formula for heat index. Fixes issue #601. Thanks to
> user Peter Q!
>
> Allow overriding the data binding when using iterators. Fixes issue #580.
>
> Fixed problem where old daily summaries may not have a version number.
>
> Fixed problem in WMR200 driver where missing UV reports as index 255.
>
> Added option 'force_direction' for working around a WU bug. Fixes issue #614.
>
>

-- 
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/17af8b18-b30c-42ff-bdac-c807c5af37f8n%40googlegroups.com.

[weewx-user] Re: Belchertown: earthquake miles vs km's

[Arend]

I am going to make a pull request out of this issue, hopefully Pat will 
incorporate this fix into the master. That way you will be able to download 
it from the repository.
In the mean time you could try to replace the modified file with the 
original from the repo and see what happens. Did you check your logs for 
errors?

Mvg, Arend

Op dinsdag 27 oktober 2020 om 21:36:04 UTC+1 schreef blee...@xs4all.nl:

> Hi Arend,
>
> Thanks for the suggestions.
>
> - The JSON tels me about an eartquake  6 km E of Belle-Plagne in France, 
> and lat=53.254&lon=5.895&maxradiuskm=2000 as set in my config, seems OK to 
> me.
> - The config is same as yours
> - I checked the changes in belchertown.py, the only difference with your 
> fixes is the order of the 4 lines, they do not come across these 
> consecutively from top to bottom as you suggested, but first 1 (line 1060), 
> then 3 (line 1139), then 4 (line 1152) and finally 2 (line 1161). I 
> copy/pasted the lines (again) from GitHub in the editor.
>
> And still no data...
>
> Regards, Keimpe   
>
> Op dinsdag 27 oktober 2020 om 20:51:31 UTC+1 schreef Arend:
>
>> Goedenavond Keimpe,
>>
>> You can check your earthquake file typing this into your browser:
>>
>> http://oentsjerk.eu/json/earthquake.json
>>
>> It shows the same data as mine which means it is loaded/updated 
>> correctly, check the epoch timestamp to verify when it was 
>> downloaded/updated.
>> Are you sure you copied the changes the right way (without additional 
>> tabs or spaces)?
>> Are there no errors in your logs?
>> My configuration shows this:
>>
>> # Earthquake defaults
>> earthquake_enabled = 1
>> earthquake_maxradiuskm = 2000
>> earthquake_stale = 10740
>> earthquake_server = USGS
>>
>> Does it match yours?
>>
>> Mvg, Arend
>>
>> Op dinsdag 27 oktober 2020 om 19:30:46 UTC+1 schreef blee...@xs4all.nl:
>>
>>> Hi Arend,
>>>
>>> Stil no recent earthquake data avilable (http://oentsjerk.eu). Can I 
>>> have your URL to check the actuality?
>>>
>>> Regards, Keimpe
>>>  
>>>
>>> Op zondag 25 oktober 2020 om 11:46:06 UTC+1 schreef blee...@xs4all.nl:
>>>
 Goedemiddag Arend,

 Thnx, changes made!
 At this time it says 'no recent data avilabale' so I have to wait for 
 een eartqauke data-update.
 Keep you informed.

 Regards, Keimpe

 Op zaterdag 24 oktober 2020 om 21:46:02 UTC+2 schreef Arend:

> Hi Keimpe,
>
> I had the same problem and created an issue about this in the repo. 
> You can use the fix, let me know if it works for you.
>
> https://github.com/poblabs/weewx-belchertown/issues/422
>
> Mvg, Arend
>
> Op zaterdag 24 oktober 2020 om 21:04:04 UTC+2 schreef 
> blee...@xs4all.nl:
>
>> Thnx Vince, Strange, also on mobile, WLAN and 4G network, the same 
>> problem so it can't be a localization issue related to the network.
>>
>>
>> Op zaterdag 24 oktober 2020 om 20:49:37 UTC+2 schreef vince:
>>
>>> On Saturday, October 24, 2020 at 10:47:03 AM UTC-7, 
>>> blee...@xs4all.nl wrote:

 I'm facing just a minor issue: in the skin.conf is defined 
 'earthquake_maxradiuskm = 2000'. Therefore I'm expecting a distance in 
 km's, but the actual distance as well as the units are still in miles 
 (mijl 
 in Dutch). How to resolve this? (http://oentsjerk.eu/)


>>> I see km when I look at your page. 
>>>
>>

-- 
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/ca529c37-7f05-486b-a7af-3ecfdff09fdan%40googlegroups.com.

Re: [weewx-user] Re: Sunshine Hours

[gjr80]

Thanks Kalli, I will put something together and email you.

Gary

On Wednesday, 28 October 2020 at 01:52:30 UTC+10 Kalli wrote:

> Gir80 I have the weewx 3.8 weewx wd v1.3 
>
> tke...@gmail.com schrieb am Dienstag, 27. Oktober 2020 um 13:40:39 UTC+1:
>
>> Never mind!
>>
>> On Tue, Oct 27, 2020 at 5:39 AM gjr80  wrote:
>>
>>> Tom,
>>>
>>> I suspect that in this case FreshWDL is displaying sunshine hours as 
>>> measured by a sunshine recorder 
>>> . Some PWS software 
>>> approximates sunshine hours by calculating the cumulative time for a day 
>>> where the solar irradiance is above a given level. From memory the 
>>> measurement of sunshine hours has come up a couple of times here or in 
>>> weewx-development.
>>>
>>> Gary
>>> On Tuesday, 27 October 2020 at 22:25:34 UTC+10 tke...@gmail.com wrote:
>>>
 The Seasons skin has something you can use. Look in the file 
 celestial.inc. 

 If you just want amount of daylight, try something like (NOT TESTED):

 #set $sunrise_ts = $almanac.sun.rise.raw
 #set $sunset_ts = $almanac.sun.set.raw
 #if $sunrise_ts and $sunset_ts

 #set $today_daylight = $sunset_ts -  $sunrise_ts
 #set $seconds = $today_daylight
 #set $hours = $seconds //3600
 #set $seconds %= 3600
 #set $minutes = $seconds//60
 #set $seconds %= 60
 #set $daylight_str = "%d hours, %d minutes, %d seconds" % ($hours, 
 $minutes, $seconds)

 Total daylight: $daylight_str

 #end if

 -tk

 On Mon, Oct 26, 2020 at 7:55 PM gjr80  wrote:

> Hallo Kalli,
>
> The short answer is at the moment sunshine hours is not provided by 
> WeeWX or WeeWX-WD. Looking at the WeeWX-WD code it appears to be 
> something 
> I started working on but never fully implemented. Can you let me know hat 
> version of WeeWX and WeeWX-WD you are running. It should be a simple 
> function to implement.
>
> Gary
>
> On Tuesday, 27 October 2020 at 03:16:23 UTC+10 Kalli wrote:
>
>>
>> Hello i have weewx-wd. in FreshWDL the sun is displayed. 
>> unfortunately i can't find any settings for it at weewx. Can anybody 
>> help 
>> me further. 
>
> -- 
> 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+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/884f712b-74c8-4bd4-8655-74610e4f94dcn%40googlegroups.com
>  
> 
> .
>
 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/3ad7fb34-745e-40bd-8e65-454da4c0c701n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b257405a-93d9-4946-8b04-6e721bd56708n%40googlegroups.com.

Re: [weewx-user] Error Message when generating Archive

[Alessandro Del Prete]

Hi,

I have the same issue, it's a brand new installation of weewx 4.1.1, 
working since a month with a belchertown skin and a weatherflow tempest.

Today I was checking weewx.log and I noticed this:

Oct 27 21:39:24 ubuntu weewx[59297] DEBUG weewx.manager: Daily summary 
version is 2.0
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: Generate 
failed with exception ''
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Seasons/NOAA/NOAA-%Y-%m.txt.tmpl
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
Reason: cannot find 'count' while searching for 'day.wind.count.raw'
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
Traceback (most recent call last):
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
unicode_string = compiled_template.respond()
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  File 
"_etc_weewx_skins_Seasons_NOAA_NOAA__Y__m_txt_tmpl.py", line 431, in respond
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
NameMapper.NotFound: cannot find 'count' while searching for 
'day.wind.count.raw'
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator: Generate 
failed with exception ''
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Seasons/NOAA/NOAA-%Y-%m.txt.tmpl
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
Reason: cannot find 'count' while searching for 'day.wind.count.raw'
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
Traceback (most recent call last):
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
unicode_string = compiled_template.respond()
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  File 
"_etc_weewx_skins_Seasons_NOAA_NOAA__Y__m_txt_tmpl.py", line 431, in respond
Oct 27 21:39:24 ubuntu weewx[59297] ERROR weewx.cheetahgenerator:  
NameMapper.NotFound: cannot find 'count' while searching for 
'day.wind.count.raw'

Then I found your reply to solve the problem. I checked the DataBindings 
section, and everything's like you suggested, no mixing (it was a new 
installation), so I don't know why the issue came up only after some time.

Is it possible to solve the problem without deleting the database? 

Thanks for any advice on this.

Alessandro

On Thursday, September 17, 2020 at 8:20:48 PM UTC+2 tke...@gmail.com wrote:

> The reason why this can occur is a rather technical one, but has to do 
> with mixing the older, V3.x, way of specifying a schema, and the newer, 
> V4.x way.
>
> 1. Stop weewx
>
> 2. Assuming there is nothing valuable in it, delete the archive 
> /var/lib/weewx/weewx.sdb
>
> 3. Make sure your [DataBindings] section looks like this. Pay attention to 
> the highlighted areas.
>
> [DataBindings]
>
> [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> database = archive_sqlite
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.manager.DaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> schema = schemas.wview_extended.schema
>
> 4. Restart weewx.
>
> -tk
>
>
>
> On Thu, Sep 17, 2020 at 11:00 AM 'joh@googlemail.com' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> Hi,
>>
>> After two tries with cheaper Weather Stations which failed due to Quality 
>> I bought now a Davis Vantage Pro2 Wireless with a Weatherlink Live Adapter
>>
>> I have setup now a new Weewx Installation and had it running for some 
>> days with "simulator" without any issues.
>>
>> Now I got my davis and I have configured it immediatly. 
>>
>> But unfortunatley I am getting now the following error:
>>
>> *Sep 17 19:55:17 weewx-test weewx[23751] ERROR weewx.cheetahgenerator: 
>> Generate failed with exception ''*
>> *Sep 17 19:55:17 weewx-test weewx[23751] ERROR weewx.cheetahgenerator: 
>>  Ignoring template /etc/weewx/skins/Seasons/NOAA/NOAA-%Y-%m.txt.tmpl*
>> *Sep 17 19:55:17 weewx-test weewx[23751] ERROR weewx.cheetahgenerator: 
>>  Reason: cannot find 'count' while searching for 'day.wind.count.raw'*
>> *Sep 17 19:55:17 weewx-test weewx[23751] ERROR weewx.cheetahgenerator: 
>>   Traceback (most recent call last):*
>> *Sep 17 19:55:17 weewx-test weewx[23751] ERROR weewx.cheetahgenerator: 
>>   

[weewx-user] Re: Belchertown: earthquake miles vs km's

[blee...@xs4all.nl]

Hi Arend,

Thanks for the suggestions.

- The JSON tels me about an eartquake  6 km E of Belle-Plagne in France, 
and lat=53.254&lon=5.895&maxradiuskm=2000 as set in my config, seems OK to 
me.
- The config is same as yours
- I checked the changes in belchertown.py, the only difference with your 
fixes is the order of the 4 lines, they do not come across these 
consecutively from top to bottom as you suggested, but first 1 (line 1060), 
then 3 (line 1139), then 4 (line 1152) and finally 2 (line 1161). I 
copy/pasted the lines (again) from GitHub in the editor.

And still no data...

Regards, Keimpe   

Op dinsdag 27 oktober 2020 om 20:51:31 UTC+1 schreef Arend:

> Goedenavond Keimpe,
>
> You can check your earthquake file typing this into your browser:
>
> http://oentsjerk.eu/json/earthquake.json
>
> It shows the same data as mine which means it is loaded/updated correctly, 
> check the epoch timestamp to verify when it was downloaded/updated.
> Are you sure you copied the changes the right way (without additional tabs 
> or spaces)?
> Are there no errors in your logs?
> My configuration shows this:
>
> # Earthquake defaults
> earthquake_enabled = 1
> earthquake_maxradiuskm = 2000
> earthquake_stale = 10740
> earthquake_server = USGS
>
> Does it match yours?
>
> Mvg, Arend
>
> Op dinsdag 27 oktober 2020 om 19:30:46 UTC+1 schreef blee...@xs4all.nl:
>
>> Hi Arend,
>>
>> Stil no recent earthquake data avilable (http://oentsjerk.eu). Can I 
>> have your URL to check the actuality?
>>
>> Regards, Keimpe
>>  
>>
>> Op zondag 25 oktober 2020 om 11:46:06 UTC+1 schreef blee...@xs4all.nl:
>>
>>> Goedemiddag Arend,
>>>
>>> Thnx, changes made!
>>> At this time it says 'no recent data avilabale' so I have to wait for 
>>> een eartqauke data-update.
>>> Keep you informed.
>>>
>>> Regards, Keimpe
>>>
>>> Op zaterdag 24 oktober 2020 om 21:46:02 UTC+2 schreef Arend:
>>>
 Hi Keimpe,

 I had the same problem and created an issue about this in the repo. You 
 can use the fix, let me know if it works for you.

 https://github.com/poblabs/weewx-belchertown/issues/422

 Mvg, Arend

 Op zaterdag 24 oktober 2020 om 21:04:04 UTC+2 schreef blee...@xs4all.nl
 :

> Thnx Vince, Strange, also on mobile, WLAN and 4G network, the same 
> problem so it can't be a localization issue related to the network.
>
>
> Op zaterdag 24 oktober 2020 om 20:49:37 UTC+2 schreef vince:
>
>> On Saturday, October 24, 2020 at 10:47:03 AM UTC-7, blee...@xs4all.nl 
>> wrote:
>>>
>>> I'm facing just a minor issue: in the skin.conf is defined 
>>> 'earthquake_maxradiuskm = 2000'. Therefore I'm expecting a distance in 
>>> km's, but the actual distance as well as the units are still in miles 
>>> (mijl 
>>> in Dutch). How to resolve this? (http://oentsjerk.eu/)
>>>
>>>
>> I see km when I look at your page. 
>>
>

-- 
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/ffb84ae0-870a-4d46-a43f-fa8df7f04805n%40googlegroups.com.

[weewx-user] Re: Belchertown: earthquake miles vs km's

[Arend]

Goedenavond Keimpe,

You can check your earthquake file typing this into your browser:

http://oentsjerk.eu/json/earthquake.json

It shows the same data as mine which means it is loaded/updated correctly, 
check the epoch timestamp to verify when it was downloaded/updated.
Are you sure you copied the changes the right way (without additional tabs 
or spaces)?
Are there no errors in your logs?
My configuration shows this:

# Earthquake defaults
earthquake_enabled = 1
earthquake_maxradiuskm = 2000
earthquake_stale = 10740
earthquake_server = USGS

Does it match yours?

Mvg, Arend

Op dinsdag 27 oktober 2020 om 19:30:46 UTC+1 schreef blee...@xs4all.nl:

> Hi Arend,
>
> Stil no recent earthquake data avilable (http://oentsjerk.eu). Can I have 
> your URL to check the actuality?
>
> Regards, Keimpe
>  
>
> Op zondag 25 oktober 2020 om 11:46:06 UTC+1 schreef blee...@xs4all.nl:
>
>> Goedemiddag Arend,
>>
>> Thnx, changes made!
>> At this time it says 'no recent data avilabale' so I have to wait for een 
>> eartqauke data-update.
>> Keep you informed.
>>
>> Regards, Keimpe
>>
>> Op zaterdag 24 oktober 2020 om 21:46:02 UTC+2 schreef Arend:
>>
>>> Hi Keimpe,
>>>
>>> I had the same problem and created an issue about this in the repo. You 
>>> can use the fix, let me know if it works for you.
>>>
>>> https://github.com/poblabs/weewx-belchertown/issues/422
>>>
>>> Mvg, Arend
>>>
>>> Op zaterdag 24 oktober 2020 om 21:04:04 UTC+2 schreef blee...@xs4all.nl:
>>>
 Thnx Vince, Strange, also on mobile, WLAN and 4G network, the same 
 problem so it can't be a localization issue related to the network.


 Op zaterdag 24 oktober 2020 om 20:49:37 UTC+2 schreef vince:

> On Saturday, October 24, 2020 at 10:47:03 AM UTC-7, blee...@xs4all.nl 
> wrote:
>>
>> I'm facing just a minor issue: in the skin.conf is defined 
>> 'earthquake_maxradiuskm = 2000'. Therefore I'm expecting a distance in 
>> km's, but the actual distance as well as the units are still in miles 
>> (mijl 
>> in Dutch). How to resolve this? (http://oentsjerk.eu/)
>>
>>
> I see km when I look at your page. 
>


-- 
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/981fbc8e-ee34-4810-968e-7e55be06b510n%40googlegroups.com.

[weewx-user] Re: Belchertown: earthquake miles vs km's

[blee...@xs4all.nl]

Hi Arend,

Stil no recent earthquake data avilable (http://oentsjerk.eu). Can I have 
your URL to check the actuality?

Regards, Keimpe
 

Op zondag 25 oktober 2020 om 11:46:06 UTC+1 schreef blee...@xs4all.nl:

> Goedemiddag Arend,
>
> Thnx, changes made!
> At this time it says 'no recent data avilabale' so I have to wait for een 
> eartqauke data-update.
> Keep you informed.
>
> Regards, Keimpe
>
> Op zaterdag 24 oktober 2020 om 21:46:02 UTC+2 schreef Arend:
>
>> Hi Keimpe,
>>
>> I had the same problem and created an issue about this in the repo. You 
>> can use the fix, let me know if it works for you.
>>
>> https://github.com/poblabs/weewx-belchertown/issues/422
>>
>> Mvg, Arend
>>
>> Op zaterdag 24 oktober 2020 om 21:04:04 UTC+2 schreef blee...@xs4all.nl:
>>
>>> Thnx Vince, Strange, also on mobile, WLAN and 4G network, the same 
>>> problem so it can't be a localization issue related to the network.
>>>
>>>
>>> Op zaterdag 24 oktober 2020 om 20:49:37 UTC+2 schreef vince:
>>>
 On Saturday, October 24, 2020 at 10:47:03 AM UTC-7, blee...@xs4all.nl 
 wrote:
>
> I'm facing just a minor issue: in the skin.conf is defined 
> 'earthquake_maxradiuskm = 2000'. Therefore I'm expecting a distance in 
> km's, but the actual distance as well as the units are still in miles 
> (mijl 
> in Dutch). How to resolve this? (http://oentsjerk.eu/)
>
>
 I see km when I look at your page. 

>>>

-- 
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/b8a22a5d-8a0a-478d-bcab-a71e593e1fb1n%40googlegroups.com.

Re: [weewx-user] Re: Sunshine Hours

[Kalli]

 Gir80 I have the weewx 3.8 weewx wd v1.3 

tke...@gmail.com schrieb am Dienstag, 27. Oktober 2020 um 13:40:39 UTC+1:

> Never mind!
>
> On Tue, Oct 27, 2020 at 5:39 AM gjr80  wrote:
>
>> Tom,
>>
>> I suspect that in this case FreshWDL is displaying sunshine hours as 
>> measured by a sunshine recorder 
>> . Some PWS software 
>> approximates sunshine hours by calculating the cumulative time for a day 
>> where the solar irradiance is above a given level. From memory the 
>> measurement of sunshine hours has come up a couple of times here or in 
>> weewx-development.
>>
>> Gary
>> On Tuesday, 27 October 2020 at 22:25:34 UTC+10 tke...@gmail.com wrote:
>>
>>> The Seasons skin has something you can use. Look in the file 
>>> celestial.inc. 
>>>
>>> If you just want amount of daylight, try something like (NOT TESTED):
>>>
>>> #set $sunrise_ts = $almanac.sun.rise.raw
>>> #set $sunset_ts = $almanac.sun.set.raw
>>> #if $sunrise_ts and $sunset_ts
>>>
>>> #set $today_daylight = $sunset_ts -  $sunrise_ts
>>> #set $seconds = $today_daylight
>>> #set $hours = $seconds //3600
>>> #set $seconds %= 3600
>>> #set $minutes = $seconds//60
>>> #set $seconds %= 60
>>> #set $daylight_str = "%d hours, %d minutes, %d seconds" % ($hours, 
>>> $minutes, $seconds)
>>>
>>> Total daylight: $daylight_str
>>>
>>> #end if
>>>
>>> -tk
>>>
>>> On Mon, Oct 26, 2020 at 7:55 PM gjr80  wrote:
>>>
 Hallo Kalli,

 The short answer is at the moment sunshine hours is not provided by 
 WeeWX or WeeWX-WD. Looking at the WeeWX-WD code it appears to be something 
 I started working on but never fully implemented. Can you let me know hat 
 version of WeeWX and WeeWX-WD you are running. It should be a simple 
 function to implement.

 Gary

 On Tuesday, 27 October 2020 at 03:16:23 UTC+10 Kalli wrote:

>
> Hello i have weewx-wd. in FreshWDL the sun is displayed. unfortunately 
> i can't find any settings for it at weewx. Can anybody help me further. 

 -- 
 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+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/884f712b-74c8-4bd4-8655-74610e4f94dcn%40googlegroups.com
  
 
 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/3ad7fb34-745e-40bd-8e65-454da4c0c701n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7decd3d2-0b13-4ef7-9a84-58e19f519117n%40googlegroups.com.

Re: [weewx-user] Version 4.2.0 ready

[Phil Green]

Installed on my Pi3 updated using setup.py method on existing install 
running python3.
Weather station Vantage Vue.
All working fine.
Many thanks.
Phil

On Tuesday, October 27, 2020 at 1:47:53 PM UTC tke...@gmail.com wrote:

> The drivers are being dropped because of their complexity and lack of use. 
> With an all-volunteer effort, we have to husband our resources. Something 
> has to go.
>
> Python 3 is definitely very mature and 100% "baked." No reason not to use 
> it, if you can.
>
> No plans to drop Python 2. 
>
> -tk
>
>
>
> On Tue, Oct 27, 2020 at 6:21 AM Greg Troxel  wrote:
>
>>
>>   CHANGES COMING! This is the last release that will support the LaCrosse 
>> WS23xx,
>>   Oregon WMR200 and WMR300 stations. In the future, they will be 
>> published as
>>   unsupported extensions.
>>
>> This is definitely not a complaint, and sorry if I have failed to notice
>> list traffic about this.
>>
>> I don't have any of those stations, so this won't affect me.  But given
>> the overall "weewx way", I find this surprising.  I wonder if they are
>> troubled and nobody has volunteered to fix,if there is some reason they
>> are too hard to keep working, or if there are too many unreasonable
>> demands for support, or something else?
>>
>>
>> I'm also curious if there is a plan/timeline for dropping python 2.7
>> support.  (I haven't personally moved to 3, partly because it has seemed
>> not 100% baked, and partly I just haven't.  With this release, it seems
>> python 3 is perhaps the standard approach, and certainly not
>> experimental.
>>
>> Greg
>>
>

-- 
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/4bb65722-c2be-4e71-90da-4ecaf0e3cae5n%40googlegroups.com.

Re: [weewx-user] Version 4.2.0 ready

[Tom Keffer]

The drivers are being dropped because of their complexity and lack of use.
With an all-volunteer effort, we have to husband our resources. Something
has to go.

Python 3 is definitely very mature and 100% "baked." No reason not to use
it, if you can.

No plans to drop Python 2.

-tk



On Tue, Oct 27, 2020 at 6:21 AM Greg Troxel  wrote:

>
>   CHANGES COMING! This is the last release that will support the LaCrosse
> WS23xx,
>   Oregon WMR200 and WMR300 stations. In the future, they will be published
> as
>   unsupported extensions.
>
> This is definitely not a complaint, and sorry if I have failed to notice
> list traffic about this.
>
> I don't have any of those stations, so this won't affect me.  But given
> the overall "weewx way", I find this surprising.  I wonder if they are
> troubled and nobody has volunteered to fix,if there is some reason they
> are too hard to keep working, or if there are too many unreasonable
> demands for support, or something else?
>
>
> I'm also curious if there is a plan/timeline for dropping python 2.7
> support.  (I haven't personally moved to 3, partly because it has seemed
> not 100% baked, and partly I just haven't.  With this release, it seems
> python 3 is perhaps the standard approach, and certainly not
> experimental.
>
> Greg
>

-- 
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/CAPq0zEB3wm%3DmbxP80yf6HCfN-2GBFFZPN9%3Dj80jRLyrARRL6tg%40mail.gmail.com.

Re: [weewx-user] Version 4.2.0 ready

[Greg Troxel]

  CHANGES COMING! This is the last release that will support the LaCrosse 
WS23xx,
  Oregon WMR200 and WMR300 stations. In the future, they will be published as
  unsupported extensions.

This is definitely not a complaint, and sorry if I have failed to notice
list traffic about this.

I don't have any of those stations, so this won't affect me.  But given
the overall "weewx way", I find this surprising.  I wonder if they are
troubled and nobody has volunteered to fix,if there is some reason they
are too hard to keep working, or if there are too many unreasonable
demands for support, or something else?


I'm also curious if there is a plan/timeline for dropping python 2.7
support.  (I haven't personally moved to 3, partly because it has seemed
not 100% baked, and partly I just haven't.  With this release, it seems
python 3 is perhaps the standard approach, and certainly not
experimental.

Greg

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


signature.asc
Description: PGP signature

[weewx-user] Re: 0 files copied to /home/weewx/public_html

[Steve Sykes]

Thank you Gary, I just wondered if it was a problem, I don't usually look 
at the log file but I had a problem where WeeWx wasn't starting reliably. I 
will just ignore the line.

Steve

On Tuesday, October 27, 2020 at 11:56:46 AM UTC gjr80 wrote:

> Hi,
>
> I presume the message you refer to is:
>
> Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.reportengine: Copied 0 
> files to /home/weewx/public_html
>
> This is normal and is not necessarily a sign that anything is amiss. The 
> line concerned is the from the CopyGenerator and is quite correct, it did 
> not copy any files. The CheetahGenerator is creating files from your 
> cheetah templates and the ImageGenerator is creating image files for your 
> plots. These generators place the generated files in the correct 
> destination directory not the CopyGenerator.
>
> The CopyGenerator  
> is used to copy static files from a skin directory to somewhere else on the 
> system. It is typically used to copy static css or javascript files for use 
> by a web server. The CopyGenerator has two modes of operation; copy once 
> where it copies files on the first report cycle after WeeWX has started or 
> copy always where it copies the specified files on every report cycle. The 
> WeeWX Seasons and Standard skins (by default) run the CopyGenerator (along 
> with the CheetahGenerator and ImageGenerator) on each report cycle but 
> the CopyGenerator is not used to copy any files.
>
> If the line is annoying you can do one of two things. You can prevent the 
> Seasons skin from invoking the CopyGenerator by removing it from the 
> generator_list config setting at the bottom of the Seasons skin config file 
> (skins/Seasons/skin.conf). You could also set log_success = false under 
> [StdReport] in weewx.conf, but this will also have the effect of silencing 
> all log entries for all generators not just the CopyGenerator.
>
> Gary
>
>
> On Tuesday, 27 October 2020 20:34:59 UTC+10, Steve Sykes wrote:
>>
>> I am getting this message in my log file, but the weewx wepbage is 
>> updating as it should. I have also looked in the  public_html directory and 
>> see files of the latest update interval so files are being copied in spite 
>> of the log file data.
>> Can anyone explain this?
>>
>> Steve KD2OM
>>
>>
>>
>> TOS=0x00 PREC=0x00 TTL=64 ID=54300 DF PROTO=UDP SPT=1900 DPT=36154 
>> LEN=329 
>> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
>> 2020-10-27 06:25:00 EDT (1603794300) to database 'weewx.sdb'
>> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
>> 2020-10-27 06:25:00 EDT (1603794300) to daily summary in 'weewx.sdb'
>> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 0.32 seconds
>> Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.imagegenerator: 
>> Generated 15 images for report SeasonsReport in 0.18 seconds
>> Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.reportengine: Copied 0 
>> files to /home/weewx/public_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/5a4428f5-b90f-44ab-bdb0-cbb5b6e57f9en%40googlegroups.com.

Re: [weewx-user] Re: Sunshine Hours

[Tom Keffer]

Never mind!

On Tue, Oct 27, 2020 at 5:39 AM gjr80  wrote:

> Tom,
>
> I suspect that in this case FreshWDL is displaying sunshine hours as
> measured by a sunshine recorder
> . Some PWS software
> approximates sunshine hours by calculating the cumulative time for a day
> where the solar irradiance is above a given level. From memory the
> measurement of sunshine hours has come up a couple of times here or in
> weewx-development.
>
> Gary
> On Tuesday, 27 October 2020 at 22:25:34 UTC+10 tke...@gmail.com wrote:
>
>> The Seasons skin has something you can use. Look in the file
>> celestial.inc.
>>
>> If you just want amount of daylight, try something like (NOT TESTED):
>>
>> #set $sunrise_ts = $almanac.sun.rise.raw
>> #set $sunset_ts = $almanac.sun.set.raw
>> #if $sunrise_ts and $sunset_ts
>>
>> #set $today_daylight = $sunset_ts -  $sunrise_ts
>> #set $seconds = $today_daylight
>> #set $hours = $seconds //3600
>> #set $seconds %= 3600
>> #set $minutes = $seconds//60
>> #set $seconds %= 60
>> #set $daylight_str = "%d hours, %d minutes, %d seconds" % ($hours,
>> $minutes, $seconds)
>>
>> Total daylight: $daylight_str
>>
>> #end if
>>
>> -tk
>>
>> On Mon, Oct 26, 2020 at 7:55 PM gjr80  wrote:
>>
>>> Hallo Kalli,
>>>
>>> The short answer is at the moment sunshine hours is not provided by
>>> WeeWX or WeeWX-WD. Looking at the WeeWX-WD code it appears to be something
>>> I started working on but never fully implemented. Can you let me know hat
>>> version of WeeWX and WeeWX-WD you are running. It should be a simple
>>> function to implement.
>>>
>>> Gary
>>>
>>> On Tuesday, 27 October 2020 at 03:16:23 UTC+10 Kalli wrote:
>>>

 Hello i have weewx-wd. in FreshWDL the sun is displayed. unfortunately
 i can't find any settings for it at weewx. Can anybody help me further.
>>>
>>> --
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/884f712b-74c8-4bd4-8655-74610e4f94dcn%40googlegroups.com
>>> 
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/3ad7fb34-745e-40bd-8e65-454da4c0c701n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAUz86KzpZCvVDPpfwFNDG_n_%2BnbM0CuXVLsy4hD4R_4g%40mail.gmail.com.

Re: [weewx-user] Re: Sunshine Hours

[gjr80]

Tom,

I suspect that in this case FreshWDL is displaying sunshine hours as 
measured by a sunshine recorder 
. Some PWS software 
approximates sunshine hours by calculating the cumulative time for a day 
where the solar irradiance is above a given level. From memory the 
measurement of sunshine hours has come up a couple of times here or in 
weewx-development.

Gary
On Tuesday, 27 October 2020 at 22:25:34 UTC+10 tke...@gmail.com wrote:

> The Seasons skin has something you can use. Look in the file 
> celestial.inc. 
>
> If you just want amount of daylight, try something like (NOT TESTED):
>
> #set $sunrise_ts = $almanac.sun.rise.raw
> #set $sunset_ts = $almanac.sun.set.raw
> #if $sunrise_ts and $sunset_ts
>
> #set $today_daylight = $sunset_ts -  $sunrise_ts
> #set $seconds = $today_daylight
> #set $hours = $seconds //3600
> #set $seconds %= 3600
> #set $minutes = $seconds//60
> #set $seconds %= 60
> #set $daylight_str = "%d hours, %d minutes, %d seconds" % ($hours, 
> $minutes, $seconds)
>
> Total daylight: $daylight_str
>
> #end if
>
> -tk
>
> On Mon, Oct 26, 2020 at 7:55 PM gjr80  wrote:
>
>> Hallo Kalli,
>>
>> The short answer is at the moment sunshine hours is not provided by WeeWX 
>> or WeeWX-WD. Looking at the WeeWX-WD code it appears to be something I 
>> started working on but never fully implemented. Can you let me know hat 
>> version of WeeWX and WeeWX-WD you are running. It should be a simple 
>> function to implement.
>>
>> Gary
>>
>> On Tuesday, 27 October 2020 at 03:16:23 UTC+10 Kalli wrote:
>>
>>>
>>> Hello i have weewx-wd. in FreshWDL the sun is displayed. unfortunately i 
>>> can't find any settings for it at weewx. Can anybody help me further. 
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/884f712b-74c8-4bd4-8655-74610e4f94dcn%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3ad7fb34-745e-40bd-8e65-454da4c0c701n%40googlegroups.com.

Re: [weewx-user] Re: Sunshine Hours

[Tom Keffer]

The Seasons skin has something you can use. Look in the file celestial.inc.

If you just want amount of daylight, try something like (NOT TESTED):

#set $sunrise_ts = $almanac.sun.rise.raw
#set $sunset_ts = $almanac.sun.set.raw
#if $sunrise_ts and $sunset_ts

#set $today_daylight = $sunset_ts -  $sunrise_ts
#set $seconds = $today_daylight
#set $hours = $seconds //3600
#set $seconds %= 3600
#set $minutes = $seconds//60
#set $seconds %= 60
#set $daylight_str = "%d hours, %d minutes, %d seconds" % ($hours,
$minutes, $seconds)

Total daylight: $daylight_str

#end if

-tk

On Mon, Oct 26, 2020 at 7:55 PM gjr80  wrote:

> Hallo Kalli,
>
> The short answer is at the moment sunshine hours is not provided by WeeWX
> or WeeWX-WD. Looking at the WeeWX-WD code it appears to be something I
> started working on but never fully implemented. Can you let me know hat
> version of WeeWX and WeeWX-WD you are running. It should be a simple
> function to implement.
>
> Gary
>
> On Tuesday, 27 October 2020 at 03:16:23 UTC+10 Kalli wrote:
>
>>
>> Hello i have weewx-wd. in FreshWDL the sun is displayed. unfortunately i
>> can't find any settings for it at weewx. Can anybody help me further.
>
> --
> 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/884f712b-74c8-4bd4-8655-74610e4f94dcn%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEDan5FKZ3rdj3LXbWFdXK%2BNLNKn3jVUznzi%2B5DTPmrwFA%40mail.gmail.com.

[weewx-user] Version 4.2.0 ready

[Tom Keffer]

Some new features, fixes some bugs.

See the *Upgrade Guide * for
instructions on how to upgrade.

CHANGE LOG

CHANGES COMING! This is the last release that will support the LaCrosse WS23xx,
Oregon WMR200 and WMR300 stations. In the future, they will be published as
unsupported extensions.

Made it easier to add new, derived types via StdWXCalculate. Fixes issue #491.

Changed the tag system slightly in order to make it possible for the XTypes
system to add new aggregations that take an argument.

Added the new data types in the extended_wview schema to the WeeWX types
system. Fixes issue #613.

Added ability to label left, right or both y-axes of graphs.  PR#610.
Fixes issue #609. Thanks to user Brent Fraser!

Added units and labels for the lightning data types.

Fixed problem where threads attempt to access non-existent database. Fixes
issue #579.

Fixed problem that caused reporting units to revert to US if they were in a
mixed unit system. Fixes issue #576.

Fixed problem that could cause the station registry to fail if given a location
with a non-ASCII location name.

Changed TE923 bucket size from 0.02589 inches to 1/36 of an inch
(0.0278 in). PR #575. Fixes issue #574. Thanks to user Timothy!

Undocumented option retry_certificate has been renamed to retry_ssl, and now
covers all SSL errors (not just certificate errors). Fixes issue #569. Thanks
to user Eric!

Fixed problem caused by specifying a [Logging]/[[formatters]] section in
weewx.conf that uses interpolated variables.

Fixed problem in the Vantage driver that resulted in incorrect sunrise/sunset
being included in loop packets when run under Python 3. Thanks to users
Constantine and Jacques!

Improved auto-scaling of plot axes.

Fixed problem where aggregates of windvec and windgustvec returned the aggregate
since start of day, not the start of the aggregation period. Fixes issue #590.

New unit "beaufort", included in "group_speed". Treating beaufort as a separate
type has been deprecated. Fixes issue #591.

New unit "kPa", included in "group_pressure". Fixes issue #596.

Fixed bug in the simulator. Made it easier to subclass class Simulator.

Expressions in StdCalibration are now ordered. Later corrections can depend on
earlier corrections.

Fixed problem under Python 2, where option 'none' could cause exception.
PR #597. Thanks to user Clément!

Fixed problem with ws23xx driver under Python 3 that caused it to crash.

Use a more modern formula for heat index. Fixes issue #601. Thanks to
user Peter Q!

Allow overriding the data binding when using iterators. Fixes issue #580.

Fixed problem where old daily summaries may not have a version number.

Fixed problem in WMR200 driver where missing UV reports as index 255.

Added option 'force_direction' for working around a WU bug. Fixes issue #614.

-- 
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/CAPq0zEBsRoG5Od3MHvDe-Mg0DRL0C6J8h0A2EGofrJb_kmnGYg%40mail.gmail.com.

[weewx-user] Re: 0 files copied to /home/weewx/public_html

[gjr80]

Hi,

I presume the message you refer to is:

Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.reportengine: Copied 0 
files to /home/weewx/public_html

This is normal and is not necessarily a sign that anything is amiss. The 
line concerned is the from the CopyGenerator and is quite correct, it did 
not copy any files. The CheetahGenerator is creating files from your 
cheetah templates and the ImageGenerator is creating image files for your 
plots. These generators place the generated files in the correct 
destination directory not the CopyGenerator.

The CopyGenerator  
is used to copy static files from a skin directory to somewhere else on the 
system. It is typically used to copy static css or javascript files for use 
by a web server. The CopyGenerator has two modes of operation; copy once 
where it copies files on the first report cycle after WeeWX has started or 
copy always where it copies the specified files on every report cycle. The 
WeeWX Seasons and Standard skins (by default) run the CopyGenerator (along 
with the CheetahGenerator and ImageGenerator) on each report cycle but 
the CopyGenerator is not used to copy any files.

If the line is annoying you can do one of two things. You can prevent the 
Seasons skin from invoking the CopyGenerator by removing it from the 
generator_list config setting at the bottom of the Seasons skin config file 
(skins/Seasons/skin.conf). You could also set log_success = false under 
[StdReport] in weewx.conf, but this will also have the effect of silencing 
all log entries for all generators not just the CopyGenerator.

Gary

On Tuesday, 27 October 2020 20:34:59 UTC+10, Steve Sykes wrote:
>
> I am getting this message in my log file, but the weewx wepbage is 
> updating as it should. I have also looked in the  public_html directory and 
> see files of the latest update interval so files are being copied in spite 
> of the log file data.
> Can anyone explain this?
>
> Steve KD2OM
>
>
>
> TOS=0x00 PREC=0x00 TTL=64 ID=54300 DF PROTO=UDP SPT=1900 DPT=36154 LEN=329 
> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
> 2020-10-27 06:25:00 EDT (1603794300) to database 'weewx.sdb'
> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
> 2020-10-27 06:25:00 EDT (1603794300) to daily summary in 'weewx.sdb'
> Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.cheetahgenerator: 
> Generated 8 files for report SeasonsReport in 0.32 seconds
> Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.imagegenerator: 
> Generated 15 images for report SeasonsReport in 0.18 seconds
> Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.reportengine: Copied 0 
> files to /home/weewx/public_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/79086aa3-eb2b-4f13-8181-aa8367ccf67co%40googlegroups.com.

[weewx-user] 0 files copied to /home/weewx/public_html

[Steve Sykes]

I am getting this message in my log file, but the weewx wepbage is updating 
as it should. I have also looked in the  public_html directory and see 
files of the latest update interval so files are being copied in spite of 
the log file data.
Can anyone explain this?

Steve KD2OM



TOS=0x00 PREC=0x00 TTL=64 ID=54300 DF PROTO=UDP SPT=1900 DPT=36154 LEN=329 
Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
2020-10-27 06:25:00 EDT (1603794300) to database 'weewx.sdb'
Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.manager: Added record 
2020-10-27 06:25:00 EDT (1603794300) to daily summary in 'weewx.sdb'
Oct 27 06:25:17 Plexserver weewx[14446] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 0.32 seconds
Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.imagegenerator: 
Generated 15 images for report SeasonsReport in 0.18 seconds
Oct 27 06:25:18 Plexserver weewx[14446] INFO weewx.reportengine: Copied 0 
files to /home/weewx/public_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/cdde9f00-3350-427a-927e-8785d0b9a297n%40googlegroups.com.