Re: [weewx-user] Re: index.html not updating

[Kevin Davis]

Thanks for the help Gary.  I was literally 2 hours away at the beach, away
from my Pi at the time that it's stuck at, so I know I didn't make any
changes intentionally.  The only correlation I can come up close to the
11:55pm time that it's stuck at is, each night @ 11:59pm via a cron job, I
stop weewx, back it up and then restart it.  Based on /var/log/messages, it
was back up and running 18 seconds later.


pi@corbett:~ $ wee_debug --info
Using verbosity=1, displaying most info

wee_debug output will be sent to stdout(console)

Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database
'archive_sqlite'

System info
  Platform:   Linux-4.19.66-v7+-armv7l-with-debian-9.13
  Python Version: 2.7.13

Load Information
  1 minute load average:  0.00
  5 minute load average:  0.00
  15 minute load average: 0.00

General Weewx info
  Weewx version 4.2.0 detected.

Station info
  Station type: Vantage
  Driver:   weewx.drivers.vantage

Driver info
[Vantage]
# This section is for the Davis Vantage series of weather stations.

# Connection type: serial or ethernet
#  serial (the classic VantagePro)
#  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
type = serial

# If the connection type is serial, a port must be specified:
#   Debian, Ubuntu, Redhat, Fedora, and SuSE:
# /dev/ttyUSB0 is a common USB port name
# /dev/ttyS0   is a common serial port name
#   BSD:
# /dev/cuaU0   is a common serial port name
port = /dev/ttyUSB0

# If the connection type is ethernet, an IP Address/hostname is
required:
host = 1.2.3.4

##
# The rest of this section rarely needs any attention.
# You can safely leave it "as is."
##

# Serial baud rate (usually 19200)
baudrate = 19200

# TCP port (when using the WeatherLinkIP)
tcp_port = 2

# TCP send delay (when using the WeatherLinkIP):
tcp_send_delay = 0.5

# The type of LOOP packet to request: 1 = LOOP1; 2 = LOOP2; 3 = both
loop_request = 1

# The id of your ISS station (usually 1). If you use a wind meter
connected
# to a anemometer transmitter kit, use its id
iss_id = 1

# How long to wait for a response from the station before giving up (in
# seconds; must be greater than 2)
timeout = 4

# How long to wait before trying again (in seconds)
wait_before_retry = 1.2

# How many times to try before giving up:
max_tries = 4

# Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2
model_type = 2

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

Currently installed extensions
Extension NameVersion   Description
mqtt  0.23  Upload weather data to MQTT server.
forecast  3.3.2 Generate and display weather and tide forecasts.

Archive info
  Database name:weewx.sdb
  Table name:   archive
  Version   2
  Unit system:  1 (US)
  First good timestamp: 2019-07-03 21:35:00 PDT (1562214900)
  Last good timestamp:  2021-01-03 20:10:00 PST (1609733400)
  Number of records:156772
  weewx (weewx.conf) is set to use an archive interval of 300 seconds.
  The station hardware was not interrogated in determining archive interval.

Databases configured in weewx.conf
  Database name:weewx.sdb
  Database driver:  weedb.sqlite

  Database name:weewx
  Database driver:  weedb.mysql
  Database host:localhost

  Database name:forecast.sdb
  Database driver:  weedb.sqlite


Parsed and obfuscated weewx.conf
# 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 = 4.2.0

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Corbett Ln. : Portland, OR"

# Latitude and longitude in decimal degrees
latitude = 45.4557641
longitude = -122.6769627

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

# Set to type of station hardware. There must be a corresponding stanz

[weewx-user] Re: Weird Barometric Pressure Analysis from Gladstone (CWOP)

[galfert]

It is the fault of all your neighbors with poorly calibrated stations. All 
you can do is reach out to all of your neighbors that you feel have done a 
poor job in calibrating their station. You all affect each other. 

Your neighbors:
http://www.findu.com/cgi-bin/wxnear.cgi?call=KQ6UP

Email contact search:
http://wxqa.com/search.htm


On Sunday, January 3, 2021 at 11:58:00 PM UTC-5 ch...@chrismaness.com wrote:

> This is a little off topic, but if you look at the attached screenshot, 
> you will see that the predicted barometric pressure by which I am 
> supposed to check my barometric pressure readings oscillate wildly.  
> Anyone seen this before?  What forum or person should I contact to 
> figure out how to get this fixed?  I do believe it is on their end -- 
> not mine.
>
> Thanks,
>
> Chirs KQ6UP
>
>

-- 
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/b3d31520-1ea9-4db3-a687-f7d95d418d6cn%40googlegroups.com.

[weewx-user] Re: ignore_zero_wind not working in 4.2.0?

[G Smith]

Hi, Gary.
I have also been affected by this change and, fortunately, your solution 
fixed my problem.  Do you know if this is a temporary regression that will 
require me to change my .conf again (back to the pre-4.2.0 way) in the near 
future?  Or is this expected to be a permanent change?

Thanks!
-- Greg

On Tuesday, November 17, 2020 at 12:52:40 AM UTC-5 gjr80 wrote:

> Bill,
>
> There was a change to the StdWXCalculate service in 4.2.0 that has 
> inadvertently changed the operation of ignore_zero_wind. Normal (expected) 
> operation should resume if you change the ignore_zero_wind setting to be 
> the opposite of its current value (ie if under 4.1.1 or earlier you 
> had ignore_zero_wind = False change it to ignore_zero_wind = True or if you 
> had ignore_zero_wind = True change it to ignore_zero_wind = False).
>
> If you don’t use ignore_zero_wind you are not affected by the change and 
> need do nothing.
>
> Gary
>
> On Tuesday, 17 November 2020 at 14:20:55 UTC+10 wa4...@gmail.com wrote:
>
>> I have three pi's running weewx, two have been moved up to 4.2.0, one is 
>> still on 4.1.1. All have ignore_zero_wind set to False. The two that are on 
>> 4.2.0 no longer work as expected (zero wind shows wind direction) but the 
>> 4.1.1 still works as expected.
>>
>> Did something happen in 4.2.0 that changed the behavior of 
>> ignore_zero_wind = False?
>
>

-- 
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/4ceddcb1-fea7-4061-8f36-91abeb0fc152n%40googlegroups.com.

Re: [weewx-user] Re: New to weewx, AW WS-2000

[galfert]

I meant to say water leak not water lead sensor.


On Sunday, January 3, 2021 at 10:51:34 PM UTC-5 galfert wrote:

> The WS-2000 does not support more sensors than the GW1000. Its the other 
> way around. The GW1000 supports every single sensor that the WS-2000 
> support, plus it supports sensors from Ecowitt that Ambient doesn't sell, 
> WH32-EP, WH31-EP, WH45 to name a few, and Ecowitt is working on some 
> sensors that they will have before Ambient gets them (new soil moisture 
> with temperature). The GW1000 also had support for water lead and lightning 
> many months before the WS-2000.
>
>
>
> On Sunday, January 3, 2021 at 8:42:57 PM UTC-5 gm@gmail.com wrote:
>
>> Thanks for the link to the chart...I need to look at it closer but I 
>> think my WS-2000 supports more sensors than the GW1000 so I may be looking 
>> at integrating FOSHK plug-in into weewx directly...unless I'm missing 
>> something...
>>
>> I also need to look at the license for FOSHK plug-in as that may make 
>> this impossible (legally, that is)
>>
>> On Sat, Jan 2, 2021, 12:40 PM Rainer Lang  wrote:
>>
>>> It works with all Ambient Weather sensors which are clones of Fine 
>>> Offset sensors.
>>>
>>> (Ambient also sells non-Fine Offset clone sensors and weather stations)
>>>
>>> What sensors these are, you can see at 
>>>
>>> https://www.wxforum.net/index.php?topic=40730.0
>>>
>>>
>>> On 02.01.2021 21:34, George Morgan wrote:
>>>
>>> Does the GW1000 work with all the AW sensors?
>>>
>>> On Sat, Jan 2, 2021, 11:41 AM galfert  wrote:
>>>
 Well there is a way to get from WS-2000 AW protocol to WeeWX...but you 
 need a translator. You can use FOSHKplugin and that will convert AW 
 protocol to Ecowitt protocol and then you can use the WeeWX Interceptor 
 driver. 


 On Saturday, January 2, 2021 at 2:17:39 PM UTC-5 gm@gmail.com 
 wrote:

> Is there an effort to support the AW protocol for the WS-2000 server?  
> As a developer I would be interested in working on this if it is 
> documented 
> (and maybe even if it is not).  My WS-2000 has the latest wifi and base 
> firmware installed. 
>
> I will also look into the GW-1000 and RTL SDR options.
>
> On Sat, Jan 2, 2021, 9:58 AM galfert  wrote:
>
>> The best way is to buy the GW1000 and then it will pick up al your 
>> WS-2000 sensors. Then you install WeeWX with the GW1000 API driver. 
>> https://github.com/gjr80/weewx-gw1000
>>
>> There is not telnet with the WS-2000. The Interceptor driver will not 
>> pick up all your sensorsif you have added optional sensors. Besides 
>> with the WS-2000 it is too convoluted to get the Interceptor working 
>> because there is no "Customized" server option with the supported 
>> protocol 
>> for the Interceptor driver. The WS-2000 newly gained "Customized" server 
>> upload option but it is Ambient protocol which is different than what 
>> the 
>> Interceptor expects.
>>
>>
>> On Saturday, January 2, 2021 at 10:29:32 AM UTC-5 gm@gmail.com 
>> wrote:
>>
>>> Hi All, 
>>>
>>> I received a weather station for Christmas and realized really 
>>> quickly that I want / need something like weewx to make it much more 
>>> capable.
>>>
>>> I saw in the list archives that others are using weewx with the 
>>> WS-2000, intercepting WU data.   Is there another method where weewx 
>>> polls 
>>> the WS-2000 or receives data directly from the WS-2000?  I noticed the 
>>> telnet protocol info on the AW website but haven't figured out which 
>>> port 
>>> the WS-2000 is using for this communication?  If I am barking up the 
>>> wrong 
>>> tree, please let me know.
>>>
>>> BTW, I have a background in computer networking, software 
>>> development (day job), system administration (day job), and have been 
>>> doing 
>>> automation for many years.
>>>
>>> Please let me know if this is a more appropriate question for the 
>>> dev list.
>>>
>>> Happy New Year!
>>>
>>>
>>> -- 
>> 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/a4f2febd-177e-4160-aef2-23d0f3a064d3n%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

Re: [weewx-user] Re: New to weewx, AW WS-2000

[galfert]

The WS-2000 does not support more sensors than the GW1000. Its the other 
way around. The GW1000 supports every single sensor that the WS-2000 
support, plus it supports sensors from Ecowitt that Ambient doesn't sell, 
WH32-EP, WH31-EP, WH45 to name a few, and Ecowitt is working on some 
sensors that they will have before Ambient gets them (new soil moisture 
with temperature). The GW1000 also had support for water lead and lightning 
many months before the WS-2000.



On Sunday, January 3, 2021 at 8:42:57 PM UTC-5 gm@gmail.com wrote:

> Thanks for the link to the chart...I need to look at it closer but I think 
> my WS-2000 supports more sensors than the GW1000 so I may be looking at 
> integrating FOSHK plug-in into weewx directly...unless I'm missing 
> something...
>
> I also need to look at the license for FOSHK plug-in as that may make this 
> impossible (legally, that is)
>
> On Sat, Jan 2, 2021, 12:40 PM Rainer Lang  wrote:
>
>> It works with all Ambient Weather sensors which are clones of Fine 
>> Offset sensors.
>>
>> (Ambient also sells non-Fine Offset clone sensors and weather stations)
>>
>> What sensors these are, you can see at 
>>
>> https://www.wxforum.net/index.php?topic=40730.0
>>
>>
>> On 02.01.2021 21:34, George Morgan wrote:
>>
>> Does the GW1000 work with all the AW sensors?
>>
>> On Sat, Jan 2, 2021, 11:41 AM galfert  wrote:
>>
>>> Well there is a way to get from WS-2000 AW protocol to WeeWX...but you 
>>> need a translator. You can use FOSHKplugin and that will convert AW 
>>> protocol to Ecowitt protocol and then you can use the WeeWX Interceptor 
>>> driver. 
>>>
>>>
>>> On Saturday, January 2, 2021 at 2:17:39 PM UTC-5 gm@gmail.com wrote:
>>>
 Is there an effort to support the AW protocol for the WS-2000 server?  
 As a developer I would be interested in working on this if it is 
 documented 
 (and maybe even if it is not).  My WS-2000 has the latest wifi and base 
 firmware installed. 

 I will also look into the GW-1000 and RTL SDR options.

 On Sat, Jan 2, 2021, 9:58 AM galfert  wrote:

> The best way is to buy the GW1000 and then it will pick up al your 
> WS-2000 sensors. Then you install WeeWX with the GW1000 API driver. 
> https://github.com/gjr80/weewx-gw1000
>
> There is not telnet with the WS-2000. The Interceptor driver will not 
> pick up all your sensorsif you have added optional sensors. Besides 
> with the WS-2000 it is too convoluted to get the Interceptor working 
> because there is no "Customized" server option with the supported 
> protocol 
> for the Interceptor driver. The WS-2000 newly gained "Customized" server 
> upload option but it is Ambient protocol which is different than what the 
> Interceptor expects.
>
>
> On Saturday, January 2, 2021 at 10:29:32 AM UTC-5 gm@gmail.com 
> wrote:
>
>> Hi All, 
>>
>> I received a weather station for Christmas and realized really 
>> quickly that I want / need something like weewx to make it much more 
>> capable.
>>
>> I saw in the list archives that others are using weewx with the 
>> WS-2000, intercepting WU data.   Is there another method where weewx 
>> polls 
>> the WS-2000 or receives data directly from the WS-2000?  I noticed the 
>> telnet protocol info on the AW website but haven't figured out which 
>> port 
>> the WS-2000 is using for this communication?  If I am barking up the 
>> wrong 
>> tree, please let me know.
>>
>> BTW, I have a background in computer networking, software development 
>> (day job), system administration (day job), and have been doing 
>> automation 
>> for many years.
>>
>> Please let me know if this is a more appropriate question for the dev 
>> list.
>>
>> Happy New Year!
>>
>>
>> -- 
> 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/a4f2febd-177e-4160-aef2-23d0f3a064d3n%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/26ac7b65-73ef-4991-856e-7e3b979d3e9bn%40googlegroups.com
>>>  
>>> 

[weewx-user] Re: index.html not updating

[gjr80]

Hi,

That is interesting, you have debug = 1 but the detail that is showing in 
the log is less than there should be. Could you please post the output from 
wee_debug 
--info . Before 
posting the wee_debug output check to make sure there is no sensitive info 
in the output such as user names, passwords, api keys etc, wee_debug will 
obfuscate such info but it is not perfect.

Gary

On Monday, 4 January 2021 at 12:58:27 UTC+10 blu...@gmail.com wrote:

> On my Seasons skins, for some reason the index.html file isn't getting 
> updated.   I don't remember changing anything since the 1/1/21 @ 11:55pm 
> timestamp of the last update. 
>
> The Standard and Mobile versions are both updating correctly. 
>
> http://wx.ke7k.com/
>
> I changed debug = 1 and restarted
>
> Jan  3 18:24:29 corbett weewx[18565] INFO __main__: Initializing weewx 
> version 4.2.0
> Jan  3 18:24:29 corbett weewx[18565] INFO __main__: Using Python 2.7.13 
> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Jan  3 18:24:29 corbett weewx[18565] INFO __main__: Platform 
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Jan  3 18:24:29 corbett weewx[18565] INFO __main__: Locale is 'en_US.UTF-8'
> Jan  3 18:24:29 corbett weewx[18565] INFO __main__: PID file is 
> /var/run/weewx.pid
> Jan  3 18:24:29 corbett weewx[18569] INFO __main__: Using configuration 
> file /etc/weewx/weewx.conf
> Jan  3 18:24:29 corbett weewx[18569] INFO __main__: Debug is 1
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: StdConvert target 
> unit is 0x1
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Archive will use 
> data binding wx_binding
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Record generation 
> will be attempted in 'software'
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Using archive 
> interval of 300 seconds (software record generation)
> Jan  3 18:24:29 corbett weewxd: forecast: MainThread: Zambretti: forecast 
> version 3.3.2
> Jan  3 18:24:29 corbett weewxd: forecast: MainThread: Zambretti: 
> interval=600 max_age=604800 winddir_period=1800 pressure_period=10800 
> hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
> Jan  3 18:24:29 corbett weewxd: forecast: MainThread: NWS: forecast 
> version 3.3.2
> Jan  3 18:24:29 corbett weewxd: forecast: MainThread: NWS: interval=10800 
> max_age=604800 lid=ORZ006 foid=PQR
> Jan  3 18:24:29 corbett weewxd: forecast: MainThread: WU: forecast version 
> 3.3.2
> Jan  3 18:24:29 corbett weewxd: forecast: MainThread: OWM: forecast 
> version 3.3.2
> Jan  3 18:24:29 corbett weewxd: forecast: MainThread: UKMO: forecast 
> version 3.3.2
> Jan  3 18:24:29 corbett weewxd: forecast: MainThread: Aeris: forecast 
> version 3.3.2
> Jan  3 18:24:29 corbett weewxd: forecast: MainThread: WWO: forecast 
> version 3.3.2
> Jan  3 18:24:29 corbett weewxd: forecast: MainThread: DS: forecast version 
> 3.3.2
> Jan  3 18:24:29 corbett weewxd: forecast: MainThread: XTide: forecast 
> version 3.3.2
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: StationRegistry: 
> Station will be registered.
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: Wunderground: 
> Posting not enabled.
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: PWSweather: Posting 
> not enabled.
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: CWOP: Posting not 
> enabled.
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: WOW: Posting not 
> enabled.
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: AWEKAS: Posting not 
> enabled.
> Jan  3 18:24:29 corbett weewx[18569] INFO user.mqtt: service version is 
> 0.23
> Jan  3 18:24:29 corbett weewx[18569] INFO user.mqtt: binding to archive
> Jan  3 18:24:29 corbett weewx[18569] INFO user.mqtt: topic is 
> corbett/weather
> Jan  3 18:24:29 corbett weewx[18569] INFO user.mqtt: data will be uploaded 
> to mqtt://127.0.0.1:1883
> Jan  3 18:24:29 corbett weewx[18569] INFO __main__: Starting up weewx 
> version 4.2.0
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Clock error is 
> 0.07 seconds (positive is fast)
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Using binding 
> 'wx_binding' to database 'weewx.sdb'
> Jan  3 18:24:29 corbett weewx[18569] INFO weewx.manager: Starting backfill 
> of daily summaries
> Jan  3 18:24:32 corbett weewx[18569] INFO weewx.engine: Starting main 
> packet loop.
> Jan  3 18:25:14 corbett weewx[18569] INFO weewx.manager: Added record 
> 2021-01-03 18:25:00 PST (1609727100) to database 'weewx.sdb'
> Jan  3 18:25:14 corbett weewx[18569] INFO weewx.manager: Added record 
> 2021-01-03 18:25:00 PST (1609727100) to daily summary in 'weewx.sdb'
> Jan  3 18:25:14 corbett weewxd: forecast: NWSThread: NWS: downloading 
> forecast from '
> http://forecast.weather.gov/product.php?site=NWS&product=PFM&format=txt&issuedb

[weewx-user] index.html not updating

[Kevin Davis]

On my Seasons skins, for some reason the index.html file isn't getting
updated.   I don't remember changing anything since the 1/1/21 @ 11:55pm
timestamp of the last update.

The Standard and Mobile versions are both updating correctly.

http://wx.ke7k.com/

I changed debug = 1 and restarted

Jan  3 18:24:29 corbett weewx[18565] INFO __main__: Initializing weewx
version 4.2.0
Jan  3 18:24:29 corbett weewx[18565] INFO __main__: Using Python 2.7.13
(default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
Jan  3 18:24:29 corbett weewx[18565] INFO __main__: Platform
Linux-4.19.66-v7+-armv7l-with-debian-9.13
Jan  3 18:24:29 corbett weewx[18565] INFO __main__: Locale is 'en_US.UTF-8'
Jan  3 18:24:29 corbett weewx[18565] INFO __main__: PID file is
/var/run/weewx.pid
Jan  3 18:24:29 corbett weewx[18569] INFO __main__: Using configuration
file /etc/weewx/weewx.conf
Jan  3 18:24:29 corbett weewx[18569] INFO __main__: Debug is 1
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Loading station
type Vantage (weewx.drivers.vantage)
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: StdConvert target
unit is 0x1
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Archive will use
data binding wx_binding
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Record generation
will be attempted in 'software'
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Using archive
interval of 300 seconds (software record generation)
Jan  3 18:24:29 corbett weewxd: forecast: MainThread: Zambretti: forecast
version 3.3.2
Jan  3 18:24:29 corbett weewxd: forecast: MainThread: Zambretti:
interval=600 max_age=604800 winddir_period=1800 pressure_period=10800
hemisphere=NORTH lower_pressure=950.0 upper_pressure=1050.0
Jan  3 18:24:29 corbett weewxd: forecast: MainThread: NWS: forecast version
3.3.2
Jan  3 18:24:29 corbett weewxd: forecast: MainThread: NWS: interval=10800
max_age=604800 lid=ORZ006 foid=PQR
Jan  3 18:24:29 corbett weewxd: forecast: MainThread: WU: forecast version
3.3.2
Jan  3 18:24:29 corbett weewxd: forecast: MainThread: OWM: forecast version
3.3.2
Jan  3 18:24:29 corbett weewxd: forecast: MainThread: UKMO: forecast
version 3.3.2
Jan  3 18:24:29 corbett weewxd: forecast: MainThread: Aeris: forecast
version 3.3.2
Jan  3 18:24:29 corbett weewxd: forecast: MainThread: WWO: forecast version
3.3.2
Jan  3 18:24:29 corbett weewxd: forecast: MainThread: DS: forecast version
3.3.2
Jan  3 18:24:29 corbett weewxd: forecast: MainThread: XTide: forecast
version 3.3.2
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: StationRegistry:
Station will be registered.
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: Wunderground:
Posting not enabled.
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: PWSweather: Posting
not enabled.
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: CWOP: Posting not
enabled.
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: WOW: Posting not
enabled.
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.restx: AWEKAS: Posting not
enabled.
Jan  3 18:24:29 corbett weewx[18569] INFO user.mqtt: service version is 0.23
Jan  3 18:24:29 corbett weewx[18569] INFO user.mqtt: binding to archive
Jan  3 18:24:29 corbett weewx[18569] INFO user.mqtt: topic is
corbett/weather
Jan  3 18:24:29 corbett weewx[18569] INFO user.mqtt: data will be uploaded
to mqtt://127.0.0.1:1883
Jan  3 18:24:29 corbett weewx[18569] INFO __main__: Starting up weewx
version 4.2.0
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Clock error is 0.07
seconds (positive is fast)
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.engine: Using binding
'wx_binding' to database 'weewx.sdb'
Jan  3 18:24:29 corbett weewx[18569] INFO weewx.manager: Starting backfill
of daily summaries
Jan  3 18:24:32 corbett weewx[18569] INFO weewx.engine: Starting main
packet loop.
Jan  3 18:25:14 corbett weewx[18569] INFO weewx.manager: Added record
2021-01-03 18:25:00 PST (1609727100) to database 'weewx.sdb'
Jan  3 18:25:14 corbett weewx[18569] INFO weewx.manager: Added record
2021-01-03 18:25:00 PST (1609727100) to daily summary in 'weewx.sdb'
Jan  3 18:25:14 corbett weewxd: forecast: NWSThread: NWS: downloading
forecast from '
http://forecast.weather.gov/product.php?site=NWS&product=PFM&format=txt&issuedby=PQR
'
Jan  3 18:25:15 corbett weewx[18569] INFO weewx.restx: MQTT: Published
record 2021-01-03 18:25:00 PST (1609727100)
Jan  3 18:25:15 corbett weewx[18569] INFO weewx.restx: StationRegistry:
Published record 2021-01-03 18:25:00 PST (1609727100)
Jan  3 18:25:15 corbett weewxd: forecast: ZambrettiThread: Zambretti:
generated 1 forecast record
Jan  3 18:25:20 corbett weewx[18569] INFO weewx.cheetahgenerator: Generated
7 files for report SeasonsReport in 5.29 seconds
Jan  3 18:25:20 corbett weewxd: forecast: NWSThread: NWS: got 40 forecast
records for Scappoose-Columbia OR 45.77N 122.86W Elev. 49 ft
Jan  3 18:25:21 corbett weewx[18569] INFO weewx.imagegenerator: Generated
14 images for report SeasonsReport in 1.05 seconds

Re: [weewx-user] Re: FUN with Windows

[Tom Keffer]

Thanks for your comments.

I have no problem with posting "related" material. Posts do not have to be
about weewx directly. My original goal with WeeWX was to allow
experimentation by weather enthusiasts. I think we've accomplished that.
Because it's designed as a flexible, almost chameleon-like, system, it's
inevitable that WeeWX will evolve in novel, perhaps surprising directions.
Part of that evolution is learning about new systems and hardware.

So, post away.

Let's end this thread here. PLEASE, no back and forth, no clarifications,
no "not what I meant." Let's just end it and leave me with the final word.

Cheers,

-tk


On Sun, Jan 3, 2021 at 5:57 PM Xant  wrote:

>
> To Vince et all
>
> 1st and foremost, wishing you a "possible 2021" (all considered).
>
> You may have realized (or not), that I'm no longer posting to Weewx Forum
> group for months (as my postings seems to get different perspective than
> intended...).
>
> I'm NOT in a "Medium blog person" (not even sure what "Medium" is), whom
> doesn't even have a Facebook or Instagram account (whatever this "social
> media" means...).
>
> Per our Weewx Tom's founder posting, "Last, but definitely not least, A
> fun, supportive Users' Group ",
> which I tried to support (as a token of recognition to our Weewx Founders
> and supporting Group).
>
> I APOLOGIZE to all Weewx group (as not wish to escalate..). But Vince, all
> my contributions were in good will... and STOP been the "police" in this
> forum (as it happens to me, it also happens to others; btw: you still owns
> me, as I saved you in MQTT settings before).
>
> There are indeed TWO Forums:
>
> 1) Users Group
>
> 2) Developers Group
>
> Where each one must be address accordingly.
>
> I had GREAT pleasure in participating in this Forum (as I may still
> contribute at times), but Vince... please just be polite (or ignore posting
> feedback... ).
>
> 2021, Xant
>
>
> PS1: pls, no replies
> PS2: u... after sooo many Months, 2021 indeed feels better...
>
> On Tuesday, June 9, 2020 at 10:45:29 AM UTC-4 vince wrote:
>
>> On Monday, June 8, 2020 at 10:35:16 PM UTC-7, Xant wrote:
>>
>>> Wondering feedback from any path above.
>>>
>>>
>>>
>> Actually I'm wondering what your post(s) have to do with weewx.   Seems
>> like you want to write a Medium blog or something, which is fine - good
>> stuff, just perhaps the wrong place to post about it.   There are a
>> thousand reddit forums if you're looking for other places to post instead.
>>
> --
> 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/ef45e6d1-a52c-4f85-888f-b48f9b97b569n%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/CAPq0zECnh7bwK%3DRBm--cotA7iB0CuVMAGH0wFQMeP5ggNKWX_g%40mail.gmail.com.

[weewx-user] Re: FUN with Windows

[Xant]

To Vince et all

1st and foremost, wishing you a "possible 2021" (all considered).

You may have realized (or not), that I'm no longer posting to Weewx Forum 
group for months (as my postings seems to get different perspective than 
intended...).

I'm NOT in a "Medium blog person" (not even sure what "Medium" is), whom 
doesn't even have a Facebook or Instagram account (whatever this "social 
media" means...).

Per our Weewx Tom's founder posting, "Last, but definitely not least, A 
fun, supportive Users' Group ", 
which I tried to support (as a token of recognition to our Weewx Founders 
and supporting Group).

I APOLOGIZE to all Weewx group (as not wish to escalate..). But Vince, all 
my contributions were in good will... and STOP been the "police" in this 
forum (as it happens to me, it also happens to others; btw: you still owns 
me, as I saved you in MQTT settings before). 

There are indeed TWO Forums:

1) Users Group

2) Developers Group

Where each one must be address accordingly.

I had GREAT pleasure in participating in this Forum (as I may still 
contribute at times), but Vince... please just be polite (or ignore posting 
feedback... ).

2021, Xant


PS1: pls, no replies
PS2: u... after sooo many Months, 2021 indeed feels better...

On Tuesday, June 9, 2020 at 10:45:29 AM UTC-4 vince wrote:

> On Monday, June 8, 2020 at 10:35:16 PM UTC-7, Xant wrote:
>
>> Wondering feedback from any path above.
>>
>>
>>
> Actually I'm wondering what your post(s) have to do with weewx.   Seems 
> like you want to write a Medium blog or something, which is fine - good 
> stuff, just perhaps the wrong place to post about it.   There are a 
> thousand reddit forums if you're looking for other places to post instead.
>

-- 
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/ef45e6d1-a52c-4f85-888f-b48f9b97b569n%40googlegroups.com.

Re: [weewx-user] Re: New to weewx, AW WS-2000

[George Morgan]

Thanks for the link to the chart...I need to look at it closer but I think
my WS-2000 supports more sensors than the GW1000 so I may be looking at
integrating FOSHK plug-in into weewx directly...unless I'm missing
something...

I also need to look at the license for FOSHK plug-in as that may make this
impossible (legally, that is)

On Sat, Jan 2, 2021, 12:40 PM Rainer Lang  wrote:

> It works with all Ambient Weather sensors which are clones of Fine Offset
> sensors.
>
> (Ambient also sells non-Fine Offset clone sensors and weather stations)
>
> What sensors these are, you can see at
>
> https://www.wxforum.net/index.php?topic=40730.0
>
>
> On 02.01.2021 21:34, George Morgan wrote:
>
> Does the GW1000 work with all the AW sensors?
>
> On Sat, Jan 2, 2021, 11:41 AM galfert  wrote:
>
>> Well there is a way to get from WS-2000 AW protocol to WeeWX...but you
>> need a translator. You can use FOSHKplugin and that will convert AW
>> protocol to Ecowitt protocol and then you can use the WeeWX Interceptor
>> driver.
>>
>>
>> On Saturday, January 2, 2021 at 2:17:39 PM UTC-5 gm@gmail.com wrote:
>>
>>> Is there an effort to support the AW protocol for the WS-2000 server?
>>> As a developer I would be interested in working on this if it is documented
>>> (and maybe even if it is not).  My WS-2000 has the latest wifi and base
>>> firmware installed.
>>>
>>> I will also look into the GW-1000 and RTL SDR options.
>>>
>>> On Sat, Jan 2, 2021, 9:58 AM galfert  wrote:
>>>
 The best way is to buy the GW1000 and then it will pick up al your
 WS-2000 sensors. Then you install WeeWX with the GW1000 API driver.
 https://github.com/gjr80/weewx-gw1000

 There is not telnet with the WS-2000. The Interceptor driver will not
 pick up all your sensorsif you have added optional sensors. Besides
 with the WS-2000 it is too convoluted to get the Interceptor working
 because there is no "Customized" server option with the supported protocol
 for the Interceptor driver. The WS-2000 newly gained "Customized" server
 upload option but it is Ambient protocol which is different than what the
 Interceptor expects.


 On Saturday, January 2, 2021 at 10:29:32 AM UTC-5 gm@gmail.com
 wrote:

> Hi All,
>
> I received a weather station for Christmas and realized really quickly
> that I want / need something like weewx to make it much more capable.
>
> I saw in the list archives that others are using weewx with the
> WS-2000, intercepting WU data.   Is there another method where weewx polls
> the WS-2000 or receives data directly from the WS-2000?  I noticed the
> telnet protocol info on the AW website but haven't figured out which port
> the WS-2000 is using for this communication?  If I am barking up the wrong
> tree, please let me know.
>
> BTW, I have a background in computer networking, software development
> (day job), system administration (day job), and have been doing automation
> for many years.
>
> Please let me know if this is a more appropriate question for the dev
> list.
>
> Happy New Year!
>
>
> --
 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/a4f2febd-177e-4160-aef2-23d0f3a064d3n%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/26ac7b65-73ef-4991-856e-7e3b979d3e9bn%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/CAJ%2B0VHzg5APMmRJnbV6ubLfG%3DvpJFWsk9vwLwR%3DrfAz0-V0Lrg%40mail.gmail.com
> 
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, sen

Re: [weewx-user] Re: CentOS is on shakey ground

[HRM Resident]

I suspect a lot of web hosting companies use CentOS.  The outfit I was with in 
Florida sure did. No doubt there’s going to be a scramble to get Rocky Linux or 
equivalent going quickly. 

I am now hosting my weewx website on a VPS now using Ubuntu and Apache.  That 
way I have full control and don’t have to pay a fortune for someone else to do 
it.  It cost me $50 USD for the TLS certificate alone! Now I get my own and 
install it for free.  I used to use Fedora, but it’s really a beta version for 
RedHat and I got tired of the incessant bug fixes and updates.  CentOS was a 
great solution as it was familiar and mature. 

Anyway, I guess this is not really weewx related. 

- Paul VE1DX 

> On Jan 3, 2021, at 6:20 PM, Mark Jenks  wrote:
> 
> I use CentOS for everything, except my home server.At home I use Fedora, 
> since it's RedHat based..
> 
>> On Sunday, January 3, 2021 at 12:48:56 PM UTC-6 WindnFog wrote:
>> I may have been the only one using CentOS for weewx (before switching to a 
>> Raspberry Pi about a year ago.)  I note it's still mentioned as a distro in 
>> the weewx documentation, with RedHat and Fedora.  CentOS was to be supported 
>> until 31 May 2029. 
>> 
>> Since the takeover of RedHat by IBM, this has been shortened to 31 December 
>> 2021.  If anyone is still using CentOS for weewx, it's probably a good idea 
>> to migrate to another distro soon.  There's a movement to replace CentOS 
>> with "Rocky Linux", but there's no timeframe for its deployment:
>> 
>> https://wiki.rockylinux.org/
>> 
>> The "strength" of CentOS was stability because it is a clone of RedHat.  I 
>> still use CentOS for other things than weewx, and rather than wait to see if 
>> Rocky Linux is successful, I'm moving to Ubuntu LTS 2020, which has at least 
>> 5 years of support/stability.
>> 
>> - Paul VE1DX
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/0xzffO8ddEE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/d86315f0-d75f-4ff6-924f-aa023c28a8fcn%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/9DAA1374-A7E6-4C43-995E-8AD898FDF597%40gmail.com.

[weewx-user] Re: CentOS is on shakey ground

[Mark Jenks]

I use CentOS for everything, except my home server.At home I use 
Fedora, since it's RedHat based..

On Sunday, January 3, 2021 at 12:48:56 PM UTC-6 WindnFog wrote:

> I may have been the only one using CentOS for weewx (before switching to a 
> Raspberry Pi about a year ago.)  I note it's still mentioned as a distro in 
> the weewx documentation, with RedHat and Fedora.  CentOS was to be 
> supported until 31 May 2029. 
>
> Since the takeover of RedHat by IBM, this has been shortened to 31 
> December 2021.  If anyone is still using CentOS for weewx, it's probably a 
> good idea to migrate to another distro soon.  There's a movement to replace 
> CentOS with "Rocky Linux", but there's no timeframe for its deployment:
>
> https://wiki.rockylinux.org/
>
> The "strength" of CentOS was stability because it is a clone of RedHat.  I 
> still use CentOS for other things than weewx, and rather than wait to see 
> if Rocky Linux is successful, I'm moving to Ubuntu LTS 2020, which has at 
> least 5 years of support/stability.
>
> - Paul VE1DX
>

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

[weewx-user] Re: MQTT & Belchertown - mixed F & C units

[David Levine]

I wanted to close this out in case someone else runs into the same 
situation. 

The reason for the unexpected behavior results coming back from the broker 
was using a public broker (HiveMQ) and what must be another user already 
using the weather topic. I modified the MQTT topic name in the config to be 
unique and all seems to be working as expected. The subscription must have 
been returning someone else's data, though their value were very close to 
mine.I thought I tried a unique topic previously but maybe I missed 
updating the Belchertowm topic name. 

David

On Saturday, January 2, 2021 at 1:11:34 PM UTC-5 David Levine wrote:

> I did some more troubleshooting this morning. I looked at the weewx-mqtt 
> code and saw if debug = 2, it would log the messages to the broker queue. 
> What I see are only F values being sent to the MQTT broker such as:
>
> Jan  2 17:30:36 raspberrypi weewx[14221] DEBUG user.mqtt: data: 
> {'dateTime': '1609608633.0', 'usUnits': '1.0', 'rainRate_inch_per_hour': 
> '0.0041459842519685035', 'hourRain_in': '0.0010364960629921259', 
> 'rain24_in': '0.7630002755905513', 'dayRain_in': '0.015043897637795279', 
> 'outTemp_F': '48.704', 'outHumidity': '65.82', 'pressure_inHg': 
> '29.569262383375', 'outTempBatteryStatus': '2.58', 'UV': '1.13', 'rain_in': 
> '0.0', 'windBatteryStatus': '2.58', 'radiation_Wpm2': '195.0', 
> 'altimeter_inHg': '29.8730484820492', 'barometer_inHg': 
> '29.87618364623033', 'cloudbase_foot': '2760.0530237211146', 'dewpoint_F': 
> '37.791766695627096', 'heatindex_F': '46.3679404', 'humidex_F': 
> '48.704001'}
>
> I am still seeing C units coming back while debugging the dev tools 
> console when the Belchertown skin is receiving/logging the message like in 
> my original post. Scanning the belcherown.js, with debug it is logging the 
> incoming message so it is a head scratcher to me how one component is 
> logging the outgoing message in F (US) while a different component is 
> logging the incoming message in C (Metric)
>
> David
>
>
>
> On Friday, January 1, 2021 at 3:28:51 PM UTC-5 David Levine wrote:
>
>> I have a new setup and working on adding MQTT to the mix. I went with 
>> hivemq to start. What is occurring is the MQTT realtime refreshes appear to 
>> be a celcius value and not my expected/configured fahrenheit value. Am I 
>> missing a config setting/section?
>>
>> Below is a snippet of debug console output and what I notice is the first 
>> message in the snippet shows temp in F which is what is expected. The 3rd 
>> message shows everything in C which is unexpected. When I first load my web 
>> page, it shows the temp, etc in F but after the first MQTT adjustment, a 
>> couple of the values switch to C, though the label stays F. 
>>
>> belchertown.js?1609531535:37 MQTT: {"dateTime": "1609532099.0", 
>> "usUnits": "1.0", "rainRate_inch_per_hour": "0.0", "hourRain_in": "0.0", 
>> "rain24_in": "0.0", "dayRain_in": "0.0", "outTemp_F": "36.248", 
>> "outHumidity": "63.68", "pressure_inHg": "30.143325340375", 
>> "outTempBatteryStatus": "2.559", "UV": "0.15", "rain_in": "0.0", 
>> "windBatteryStatus": "2.559", "radiation_Wpm2": "27.0", "altimeter_inHg": 
>> "30.451898910400498", "barometer_inHg": "30.46410551847069", 
>> "cloudbase_foot": "2805.165679377027", "dewpoint_F": "25.137271010741078", 
>> "heatindex_F": "36.248", "humidex_F": "36.248"}
>>
>> belchertown.js?1609531535:37 MQTT: {"dateTime": "1609532102.0", 
>> "windSpeed_mph": "0.0", "usUnits": "1.0", "rainRate_inch_per_hour": "0.0", 
>> "hourRain_in": "0.0", "rain24_in": "0.0", "dayRain_in": "0.0"}
>>
>> belchertown.js?1609531535:37 MQTT: {"dateTime": "1609532103.0", 
>> "pressure_mbar": "1013.7152953417267", "outHumidity": "85.0", "inHumidity": 
>> "97.0", "outTemp_C": "2.", "inTemp_C": "5.221", 
>> "windSpeed_kph": "1.802465280003", "windGust_kph": 
>> "1.802465280003", "windDir": "227.0", "radiation_Wpm2": "0.0", 
>> "rain_cm": "0.0", "rainRate_mm_per_hour": "0.0", "UV": "0.0", 
>> "extraTemp1_C": "7.8995", "extraTemp2_C": "6.901", 
>> "extraHumid1": "85.0", "extraHumid2": "85.0", "rainBatteryStatus": "1.6", 
>> "windBatteryStatus": "1.66", "barometer_mbar": "1013.7152953417267", 
>> "altimeter_mbar": "1021.4013952324038", "windchill_C": 
>> "2.", "heatindex_C": "2.", "dewpoint_C": 
>> "0.5099126991358697", "inDewpoint_C": "4.785153750721902", 
>> "maxSolarRad_Wpm2": "0.0", "cloudbase_meter": "345.781455500638", 
>> "beaufort_count": "0.0", "appTemp_C": "0.5178210591074577", "humidex_C": 
>> "2.", "hourRain_cm": "0.0", "rain24_cm": "0.02032", 
>> "dayRain_mm": "0.20322", "usUnits": "16.0"}
>>
>> The first message looks correct and the 3rd message not so much. 
>>
>> Here's my MQTT config and what I added to the Belchertown/Extras section 
>> of weewx.conf:
>>
>> [[MQTT]]
>> server_url = mqtt://broker.hivemq.com:1883/
>> topic = we

[weewx-user] Re: CentOS is on shakey ground

[vince]

It's a little unclear if IBM will keep to the centos-7 EOL date of 2024 or 
not, if that helps any.  While we know centos-8 will essentially become 
rhel-next-rolling-release-candidate, they haven't said what they'll do with 
centos-7 moving forward as far as I've heard.  Maybe that helps a little.

But fortunately weewx doesn't care what os you're on as long as you meet 
the python prerequisites.

I 'did' verify at $work that Oracle Linux seeems to be equally 
indistinguishable from RHEL like CentOS is, so that is definitely an option 
short term, if you want to deal with 'that' evil empire.   They also 
quickly published a script to convert your CentOS setup to a OL setup, but 
I didn't test that.   Personally I'd flatten+reload it if you wanted to go 
that way.  I found some upgrade scenarios didn't get quite an identical 
result under the hood as a clean flatten+load did.

On Sunday, January 3, 2021 at 10:48:56 AM UTC-8 WindnFog wrote:

> I may have been the only one using CentOS for weewx (before switching to a 
> Raspberry Pi about a year ago.)  I note it's still mentioned as a distro in 
> the weewx documentation, with RedHat and Fedora.  CentOS was to be 
> supported until 31 May 2029. 
>
> Since the takeover of RedHat by IBM, this has been shortened to 31 
> December 2021.  If anyone is still using CentOS for weewx, it's probably a 
> good idea to migrate to another distro soon.  There's a movement to replace 
> CentOS with "Rocky Linux", but there's no timeframe for its deployment:
>
> https://wiki.rockylinux.org/
>
> The "strength" of CentOS was stability because it is a clone of RedHat.  I 
> still use CentOS for other things than weewx, and rather than wait to see 
> if Rocky Linux is successful, I'm moving to Ubuntu LTS 2020, which has at 
> least 5 years of support/stability.
>
> - Paul VE1DX
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/61b0dd8a-9f52-45d8-bb6f-71a63054fce7n%40googlegroups.com.

[weewx-user] Re: Publishing WeeWX to AWS S3

[vince]

Very cool.  Thanks for posting the howto.   Pretty amazing you can do this 
for under a dollar a month.

I did DevOps tooling for a AWS-hosted $job for a few years using 
ansible/terraform/boto3 and a little CloudFormation (ugh) so I had some 
questions about what's under the hood a bit more than just the (nice) howto 
stuff you have in your link.

My current setup is an AWS Lightsail instance ($4/month) with DNS provided 
by Google DNS ($1/month).

   - how do you get your stable .eu.com FQDN onto your website's ip address 
   ?
   - is the website ip address stable ?
   - are you using Route53 for your DNS ?  What's that cost ?
  - (background - I went Google DNS years ago because Route53 was too 
  expensive.  Google DNS also had some nice email and site aliasing 
features 
  that Route53 didn't have back then.   I particularly like the ability to 
  add email aliases for the family very easily, pointing to email wherever 
  they want it to be hosted)
   

My Lightsail instance sees zillions of attack attempts from the usual 
bots+script kiddies, trying to probe for the usual things (WordPress, PHP, 
etc.), from the usual suspect countries with distributions about what you'd 
expect from reading the press. I know geoip lookups are an inexact science, 
but the data indicate the bots probably aren't trying too hard to falsify 
their source ip.  They just scan the public address space periodically and 
run the same probes the next time.


   - I use geoip fencing in nginx to only permit in ip addresses from a 
   handful of countries with folks I collaborate with.  That lessens the 
   number of attack attempts by a huge amount.   Does CloudFront have that 
   kind of ability too ?
   - I also run fail2ban to block ip from addresses (from permitted 
   countries) who seem to be trying to attack the system.   Can CloudFront 
   also do something like that ?
   - do you have anything enabled to alert you if your costs spike up due 
   to somebody successfully getting into your setup ?   I know that a S3 
   bucket with web data is not any risk from a security standpoint, but I 
   always worry about AWS costs if a 'feature' happens and somebody/something 
   causes your usage to spike up.  AWS sure likes billing on usage numbers 
   (sigh).


Lastly - automation.Everything AWS is scriptable basically, which is 
pretty powerful.  When I rebuilt my Lightsail instance that is a simple 
ubuntu running just nginx so I can rsync up to it from my home LAN weewx 
box, I automated most of it with Terraform.  Previously I'd done similar 
things with Ansible.  But regardless it was pretty great getting the AWS 
unique stuff done fully scripted.  All I had to do afterward was set up 
LetsEncrypt and do a couple odds+ends.

Have you given any thought on scripting your whole setup with something 
like Ansible / Terraform / CloudFormation ?It would be pretty cool to 
have an accompanying script or equivalent that did that, once you have the 
manual step of getting an account and saving the AWS credentials of course.

Very cool howto.  Thanks !

On Sunday, January 3, 2021 at 2:32:40 AM UTC-8 mi...@cougar.eu.com wrote:

> It is nearly 2 years since I migrated my Web Site to AWS S3 but that was 
> done in a rather clumsy way. So when I moved my WeeWX deployment to my 
> Rasberry Pi I decided to do it properly.
>
> With time on my hands over Christmas I have finally gotten around to 
> writing up how I did it and for those that are interested  the cost is free 
> for the first 12 months then $1.00 US per month after that.
>
> Instructions are here 
> 
>
>
>

-- 
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/34cad7c8-5f3d-4a07-be05-e400194434dcn%40googlegroups.com.

Re: [weewx-user] Modify StdPrint to not print loop packets?

[Tom Keffer]

True. It would only work under Python 2.

Fixed in commit e12237c


-tk

On Sun, Jan 3, 2021 at 9:59 AM Brad Furman  wrote:

> Thanks Tom. BTW, the example shown on the help docs for modifying an
> existing service is incorrect.
> http://weewx.com/docs/customizing.htm#Customizing_a_service
>
> The print statement in this example needs to be encapsulated in
> parentheses.
>
> On Sun, Jan 3, 2021 at 8:47 AM Tom Keffer  wrote:
>
>> Unfortunately, there are no options to do that. You'd have to
>> replace StdPrint with your own service .
>>
>> On Sat, Jan 2, 2021 at 9:12 PM bdf0506  wrote:
>>
>>> My log file is far too noisy in my docker implementation of wee
>>> experience, so I’m looking for a quick and easy way to only print the
>>> archive packets with StdPrint and then only print loop packets if debug is
>>> enabled. Is this easily possible? Or will I have to create my own service
>>> to run, as described in the customization guide?
>>>
>>> Thanks in advance!
>>>
>>> --
>>> 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/75d759a9-9e93-4c8e-b6b9-e4a2ec8fe8f8n%40googlegroups.com
>>> 
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/i1gVISpngc4/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEByrhqfkQT6tKi7bznYPGRuCtNH2y_aOgZL6R7E1AkmJg%40mail.gmail.com
>> 
>> .
>>
>
>
> --
> Brad Furman
> bdfur...@gmail.com
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAEwo8bL05C-ce3ZMfLH_smsF_PKKfacPdwsBZ1pbB0oJDa2huQ%40mail.gmail.com
> 
> .
>

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

[weewx-user] Re: Battery Status for TE923

[stelli...@gmail.com]

Solved it on my own. If others are interested, here is what I did:

   1. Copying the sensors.inc file from the Seasons skin to the root folder 
   of the Belchertown skin
   2. Modified the file to change from table to list style
   3. Removed sevction headings of the file
   4. included the sensors.inc via *#include "sensors.inc"*
   5. Adding the information to the Belchertown style.css file to show OK 
   in green and LOW in red

The modified sensors.inc file is attached. The result can be seen on my 
about site .

Hope that this can be helpful if others want to to adjust this...

-- 
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/a4d34150-526d-4397-9f41-73c885547f8dn%40googlegroups.com.

[weewx-user] CentOS is on shakey ground

[WindnFog]

I may have been the only one using CentOS for weewx (before switching to a 
Raspberry Pi about a year ago.)  I note it's still mentioned as a distro in 
the weewx documentation, with RedHat and Fedora.  CentOS was to be 
supported until 31 May 2029. 

Since the takeover of RedHat by IBM, this has been shortened to 31 December 
2021.  If anyone is still using CentOS for weewx, it's probably a good idea 
to migrate to another distro soon.  There's a movement to replace CentOS 
with "Rocky Linux", but there's no timeframe for its deployment:

https://wiki.rockylinux.org/

The "strength" of CentOS was stability because it is a clone of RedHat.  I 
still use CentOS for other things than weewx, and rather than wait to see 
if Rocky Linux is successful, I'm moving to Ubuntu LTS 2020, which has at 
least 5 years of support/stability.

- Paul VE1DX

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

Re: [weewx-user] Modify StdPrint to not print loop packets?

[Brad Furman]

Thanks Tom. BTW, the example shown on the help docs for modifying an
existing service is incorrect.
http://weewx.com/docs/customizing.htm#Customizing_a_service

The print statement in this example needs to be encapsulated in parentheses.

On Sun, Jan 3, 2021 at 8:47 AM Tom Keffer  wrote:

> Unfortunately, there are no options to do that. You'd have to
> replace StdPrint with your own service .
>
> On Sat, Jan 2, 2021 at 9:12 PM bdf0506  wrote:
>
>> My log file is far too noisy in my docker implementation of wee
>> experience, so I’m looking for a quick and easy way to only print the
>> archive packets with StdPrint and then only print loop packets if debug is
>> enabled. Is this easily possible? Or will I have to create my own service
>> to run, as described in the customization guide?
>>
>> Thanks in advance!
>>
>> --
>> 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/75d759a9-9e93-4c8e-b6b9-e4a2ec8fe8f8n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/i1gVISpngc4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEByrhqfkQT6tKi7bznYPGRuCtNH2y_aOgZL6R7E1AkmJg%40mail.gmail.com
> 
> .
>


-- 
Brad Furman
bdfur...@gmail.com

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

[weewx-user] Re: How to find a line in index.html.tmpl from the error log?

[WindnFog]

Vince, Peter, Gary, and of course Tom,

It's done! I used suggestions from all of you, and it wasn't as painful as 
I had thought. There was a lot of math in index.html.tmpl, but I can't say 
exactly which line(s) were causing the errors. My Pi's Raspiban O/S was 
sort of messed up because of a year of hacks, upgrades, and other unknowns. 
I rebuilt the O/S from scratch and added the latest versions of the 
extensions I needed. Then I performed a clean install of weewx 4.2.0.  

I went through index.html.tmpl using more or less a "binary search" method 
by commenting out half, then a quarter, then an 8th, etc. Each iteration 
resolved something.

This also gave me a chance to fix up weewx.conf that had been modified with 
parts commented out over the years, etc. As of today, my system is running 
flawlessly on Python 3.7.3. It's reassuring to know everything is newly 
installed and up to date. This had been one of those things on my "to do" 
list for 6-8 months. My takeaway: As with most software you've upgraded for 
some time, there comes the point when you need to bite the bullet and do a 
fresh install.

A big thank YOU to everyone who puts up with my questions. Sometimes they 
are apparent and in the documentation, and other times they are a bit 
obscure. Either way, I can say that weewx has been running my weather 
station for over 5 years, and it's been a joy to use.

https://ve1dx.net/

- Paul VE1DX


On Tuesday, December 29, 2020 at 6:09:05 PM UTC-4 vince wrote:

> FWIW, I've had some luck with the approach in one of my skins (here) 
> 
>  
> where I check for $current.whatever.has_data to show things in my skin only 
> if there's data to show. I don't know if that's a preferred failsafe 
> construct though.  Can something.has_data be true and still have the value 
> be None ?  I dunno.
>
> On Tuesday, December 29, 2020 at 2:03:00 PM UTC-8 vince wrote:
>
>> Running the simulator and looping through "*make a change, manually run 
>> wee_reports, check the log, check the results*" works pretty well as one 
>> way of doing it.   I don't think you even need weewx running to do that.   
>> I typically just spin up a Simulator VM with vagrant+VirtualBox and battle 
>> through it.
>>
>> But cheetah can certainly make it unpleasant to say the least.
>>
>> On Tuesday, December 29, 2020 at 1:39:11 PM UTC-8 WindnFog wrote:
>>
>>> Thanks, guys.  That's what I figured.  While I'm no Python guru, I was 
>>> in the IT field for 39 years.  This isn't the first time I ran into things 
>>> like this.  I will do as you both suggest.  I can add a "feature" to the 
>>> stock file one at a time, and fix the errors as I encounter them.  The good 
>>> news is I have two parallel systems . . . one is my live site:
>>>
>>> https://www.ve1dx.net
>>>
>>> And the other is sending the simulator data to a subdirectory under it.  
>>> I even have two Davis receivers,  each with a data logger and USB 
>>> interface.  I do so because I have this obsession not to let my site go 
>>> offline (failing power outages.)  I always try to have a backup plan and 
>>> duplicate the hardware if possible.  I used to manage Unix servers for up 
>>> to 2000 clients, and downtime was a no-no!
>>>
>>> So . . . it looks like I have my work cut out for me.  It's something to 
>>> do during this long, cold, dark winter.  One bite (byte?) at a time is the 
>>> way to go when facing an elephant.
>>>
>>> - Paul VE1DX
>>>
>>> On Tuesday, December 29, 2020 at 5:16:36 PM UTC-4 gjr80 wrote:
>>>
 Hi,

 Short answer is there is no direct way of obtaining the offending line 
 number in your template file. It would be helpful if we had access to the 
 temporary .py file that Cheetah creates (for which the line number is 
 provided) but unfortunately we don’t have access to that file. The best 
 you 
 can do is to infer from the error message. In the case above you are 
 looking for a multiplication operation for which the left hand operand is 
 (could be) None and the right hand operand is a float. Usually not too 
 hard 
 to spot possible problem locations (unless you have lots and lots of 
 multiplication operators). Also, NoneType issues typically come from WeeWX 
 fields/obs that are unexpectedly None, so something like 
 $current.outTemp.raw * 1.2 would be a prime candidate (outTemp could be 
 None for some reason) but 3.23 * 1.2 (no chance of None) is not nor would 
 $current.outHumidity.raw * 2 (does not use a float).

 If you are unfortunate enough to get an error message that is not very 
 descriptive, or you have just too many possible error sites in your 
 template, your only real option is to start breaking down your template 
 into smaller chunks to find the location. I favour splitting the template 
 in half, find the offending half template and then breaking that i

Re: [weewx-user] Modify StdPrint to not print loop packets?

[Tom Keffer]

Unfortunately, there are no options to do that. You'd have to
replace StdPrint with your own service .

On Sat, Jan 2, 2021 at 9:12 PM bdf0506  wrote:

> My log file is far too noisy in my docker implementation of wee
> experience, so I’m looking for a quick and easy way to only print the
> archive packets with StdPrint and then only print loop packets if debug is
> enabled. Is this easily possible? Or will I have to create my own service
> to run, as described in the customization guide?
>
> Thanks in advance!
>
> --
> 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/75d759a9-9e93-4c8e-b6b9-e4a2ec8fe8f8n%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/CAPq0zEByrhqfkQT6tKi7bznYPGRuCtNH2y_aOgZL6R7E1AkmJg%40mail.gmail.com.

Re: [weewx-user] Rainfall data on 29 Feb

[Tom Keffer]

👍

On Sun, Jan 3, 2021 at 3:25 AM Roger Saunders  wrote:

> Tom
> After some more analysis I found the problem was on my side not yours so
> apologies for this. All is OK now from my perspective,
> Regards
> Roger
>
> On 2 Jan 2021, at 22:53, Tom Keffer  wrote:
>
> Still not following. What do you mean by "monthly mean precipitation"? Do
> you mean the monthly total precipitation?
>
> If so, what do you mean by "agree with my calculations"? How did you
> calculate February's total? Directly from the database? Or, are you saying
> that the total given for February on the page NOAA-2020.txt does not match
> the total given on NOAA-2020-02.txt? Or, something else?
>
> It would help if you included the NOAA-2020.txt and NOAA-2020-02.txt
> pages. Or, even better, if they are online, include a link.
>
> There just isn't enough information to diagnose the problem.
>
> -tk
>
> On Sat, Jan 2, 2021 at 7:46 AM Roger Saunders 
> wrote:
>
>> When I select yearly summary on the weewx page: weewx/NOAA/NOAA-2020.txt
>> the monthly mean precipitation listed there all agree with my calculations
>> except for February. I tracked down the reason was that the rainfall amount
>> on 29 Feb is not included in the Feb mean printed in NOAA-2020.txt Does
>> that make sense?
>> Roger
>>
>> On Saturday, 2 January 2021 at 14:37:13 UTC tke...@gmail.com wrote:
>>
>>> Hello, Roger
>>>
>>> Can you be more specific about what you're seeing? What stats are you
>>> referring to? The tag $year.rain.sum? Something else? How is it not
>>> matching your expectations?
>>>
>>> -tk
>>>
>>> On Sat, Jan 2, 2021 at 4:54 AM Roger Saunders 
>>> wrote:
>>>
 Hi!
 I noticed that the annual rainfall stats from weewx doesn't include the
 29th Feb in its calculations, easy to understand why.
 Roger
 PS Overall though really grateful of this useful software


 --
 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/a7187f60-4e68-4c1f-9c0a-d5edc44c21c5n%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/47f15691-95c7-4de9-9f64-93b75e2a784dn%40googlegroups.com
>> 
>> .
>>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/x6jitm4BMhI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEC3%3DpcFJ%3DjgAk%2BsLTqQmPyYKxNeqHpF_Y87GRWEZuh7_Q%40mail.gmail.com
> 
> .
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/1058F526-607B-47C4-B68A-D72928F7C72C%40gmail.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/CAPq0zEAHrCD0tNgUDXoC9K5KNLZqJa6D0L8QgW5N1_xTJQsztA%40mail.gmail.com.

[weewx-user] Re: Acurite 5in1 and rtl_sdr

[seano...@gmail.com]

Thanks for the replies. I'm still scratching my head about this issue. A 
few weeks ago i installed a wifi plug onto the power line of the Raspberry 
Pi and i have been experimenting... whenever i see the station losing 
signal and having a breakup in the reporting (ie. *user.sdr: lines=[]*) 
then i power off the Raspberry Pi using the wifi switch which gives it a 
hard power off. I leave it off for 1 minute then power it back on and so 
far, every single time i do that, the raspberry pi starts receiving a 
signal from the Acurite5-in-1 again.

Currently, i am led to believe the RTL-SDR dongle i think i've installed (this 
one 
)
 
is actually faulty. Because a software reset doesn't bring it back online, 
but a hard reset always does. Would be curious to know if anyone else has 
experienced anything like this? My next step is to purchase a new RTL-SDR 
dongle and see if it solves the problem.

Thanks,
Sean.

On Friday, October 30, 2020 at 6:37:00 PM UTC+4 RobbH wrote:

> My suspicion is that this happens because of unusual propagation 
> conditions such as "tropospheric ducting," which may be associated with 
> unusual weather or sunspot activity, among other factors. There are 
> occasions when distant radio or TV signals can be received briefly, 
> sometimes stronger than local stations. The same conditions might affect 
> the frequencies used by weather sensors.
>
> I have a rooftop 5in1 for wind and rain measurements and a 
> temperature/humidity sensor in the back yard, both connected through an 
> Acurite bridge. Sometimes Weewx stops receiving data from one sensor, while 
> the other continues to work for a time. Then the other sensor will go 
> silent, as well, and shortly afterward the first sensor will reappear. 
> Eventually, the second sensor also reconnects.
>
> The time difference suggests to me that the outages are caused by 
> something in motion, which could be an atmospheric condition. I can't rule 
> out the possibility that there's some sort of local source of interference, 
> though.
>
> I'm sure there are people reading this forum who know more about RF than I 
> do, so it would be great to hear their opinions about this.
>
> On Thursday, October 29, 2020 at 8:03:02 AM UTC-4 Peter Whisker wrote:
>
>> I find the same occurs on my FineOffset HP1000 clone - it happens to the 
>> device receiver.
>>
>> My (unproven) theory is that the signals from the external and internal 
>> sensors which come every 16 seconds drift with respect with each other 
>> until they end up being transmitted at exactly the same time and the 
>> receiver can not discriminate them. After half a day or so the situation 
>> recovers and is fine for a month or more.
>>
>> Peter
>>
>> On Thursday, October 29, 2020 at 4:12:29 AM UTC seano...@gmail.com wrote:
>>
>>> Hi,
>>>
>>> My station has been running weewx + rt_sdr for a year and all is working 
>>> well. Weewx receives the station data and broadcasts it to windguru. 
>>> However, there is an occasional problem that happens and i can't figure out 
>>> what the cause is. All of a sudden, rtl_433 stops receiving from the sensor 
>>> for hours at a time.
>>>
>>> During those periods, when i run: 
>>> *sudo tail -f /var/log/weewx.log*
>>>
>>> All i see is:
>>> *user.sdr: lines=[]*
>>>
>>> If you leave it, it eventually comes back online itself. I can confirm 
>>> that during that time there was no loss of power or internet - because i 
>>> can still connect to the pi and manage it. Also, weather station has new 
>>> batteries, so that is not the problem. I have a feeling that the problem is 
>>> happening with the realtek SDR dongle. Because a power reset sometimes 
>>> fixes the problem - and a physical removal of the USB dongle into a 
>>> different USB port seems to fix the problem immedaitely.
>>>
>>> I've even tried a python script to eject the USB device which also seems 
>>> to help. But in order to do this i first need to disable rtl_433 in the 
>>> weewx.conf, then reboot, then run rtl_433 on its own until it sees the 
>>> sensor, then re-enable rtl_433 in weewx.conf and reboot. That is usually 
>>> the process to fix it immediately, so it definitely feels to me like a 
>>> software issue.
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> Sean
>>>
>>

-- 
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/6aba7684-4bab-4866-b5d8-21c00f0c18c1n%40googlegroups.com.

Re: [weewx-user] weatherlink template (.htx) equivalence with weeWX? (ForecastStr with Davis Vantage station)

[P C]

Hello Tom and Company
I hadn't made the connection between Tom Keffer and "*THE*" Tom Keffer. 
Congratulations and admiration for this immense work!

I continue my quest for the Davis Vantage station forecast. The driver 
does 
map a forecastrule byte, moreover very little documented by the 
manufacturer in its technical PDF (it mentions its presence at offset 33 
and Weather forecast rule at the end of the archive period.) and nothing 
more.
But I found a listing there: 
https://cumulus.hosiene.co.uk/viewtopic.php?f=25&t=4561&start=705 I don't 
know if it's the official one, because there is redundancies. There are also 
phrases   which appear at 
particular times depending on the weather at the moment ("*ITS RAINING CATS 
N DOGS*") or ephemeris ( Solstices, equinoxes, eclipses ...)
I'll email Davis to try to get an answer.

So Tom & Cie, how could I have this number in a Skin and by extension, the 
corresponding text?
Although I understand it a bit, I don't know Python well enough to 
implement this.

Kind regards to you all,
Pascal
Le vendredi 1 janvier 2021 à 17:27:05 UTC+1, P C a écrit :

>
>
> * but especially that it is for Davis Vantage station whose consoles give 
> a not too bad forecast string: ForecastStrBut now, I suppose it also 
> depends on the driver? *
>
>
> Yes, and to read http://www.weewx.com/docs/hardware.htm#vantage_data it 
> is not planned :(
>
> Am I wrong ?
> Le vendredi 1 janvier 2021 à 17:05:59 UTC+1, P C a écrit :
>
>> thank you,
>>
>> I forgot to specify that
>>
>>1. I am a beginner
>>2. but especially that it is *for Davis Vantage station *whose 
>>consoles give a not too bad forecast string: *ForecastStr*
>>But now, I suppose it also depends on the driver?
>>
>>
>> Le vendredi 1 janvier 2021 à 16:03:29 UTC+1, tke...@gmail.com a écrit :
>>
>>> Yes. There's a whole guide  
>>> to writing templates. The equivalent to your example would be something 
>>> like (NOT TESTED):
>>>
>>> $current.datetime
>>> $current.outTemp
>>> $current.outHumidity
>>> $current.barometer
>>> $trend.barometer
>>> $current.windSpeed
>>> $current.windDir
>>> $current.rainRate
>>> $day.rain.sum
>>> $almanac.sun.rise
>>> $almanac.sun.set
>>>
>>>
>>> The forecast string would come from a weather forecast extension.
>>>
>>> -tk
>>>
>>>
>>>
>>>
>>> On Fri, Jan 1, 2021 at 5:57 AM P C  wrote:
>>>
 Hello all,

 First of all, let's hope we get out of this cr...y year to have a 
 wonderful 2021;)

 With weatherlink, there is a way, (via ".htx" files), to "output" some 
 values in order to build your own page. For example, I use "
 
 
 
 
 
 
 
 
 
 
 
  "which help me build my WEB page header.
 My question is: is there an equivalent with WeeWX?

 Thank you and good to you,
 Pascal 

 -- 
 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/74b9470b-7396-4823-aaec-b87cf1d82774n%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/c336cf9d-0e44-48f4-b771-586e76b127afn%40googlegroups.com.

Re: [weewx-user] Rainfall data on 29 Feb

[Roger Saunders]

Tom
After some more analysis I found the problem was on my side not yours so 
apologies for this. All is OK now from my perspective, 
Regards
Roger

> On 2 Jan 2021, at 22:53, Tom Keffer  wrote:
> 
> Still not following. What do you mean by "monthly mean precipitation"? Do you 
> mean the monthly total precipitation? 
> 
> If so, what do you mean by "agree with my calculations"? How did you 
> calculate February's total? Directly from the database? Or, are you saying 
> that the total given for February on the page NOAA-2020.txt does not match 
> the total given on NOAA-2020-02.txt? Or, something else?
> 
> It would help if you included the NOAA-2020.txt and NOAA-2020-02.txt pages. 
> Or, even better, if they are online, include a link.
> 
> There just isn't enough information to diagnose the problem. 
> 
> -tk
> 
> On Sat, Jan 2, 2021 at 7:46 AM Roger Saunders  > wrote:
> When I select yearly summary on the weewx page: weewx/NOAA/NOAA-2020.txt the 
> monthly mean precipitation listed there all agree with my calculations except 
> for February. I tracked down the reason was that the rainfall amount on 29 
> Feb is not included in the Feb mean printed in NOAA-2020.txt Does that make 
> sense?
> Roger
> 
> On Saturday, 2 January 2021 at 14:37:13 UTC tke...@gmail.com 
>  wrote:
> Hello, Roger
> 
> Can you be more specific about what you're seeing? What stats are you 
> referring to? The tag $year.rain.sum? Something else? How is it not matching 
> your expectations?
> 
> -tk
> 
> On Sat, Jan 2, 2021 at 4:54 AM Roger Saunders > wrote:
> Hi!
> I noticed that the annual rainfall stats from weewx doesn't include the 29th 
> Feb in its calculations, easy to understand why. 
> Roger
> PS Overall though really grateful of this useful software
> 
> 
> -- 
> 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/a7187f60-4e68-4c1f-9c0a-d5edc44c21c5n%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/47f15691-95c7-4de9-9f64-93b75e2a784dn%40googlegroups.com
>  
> .
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "weewx-user" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/weewx-user/x6jitm4BMhI/unsubscribe 
> .
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEC3%3DpcFJ%3DjgAk%2BsLTqQmPyYKxNeqHpF_Y87GRWEZuh7_Q%40mail.gmail.com
>  
> .

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

[weewx-user] Battery Status for TE923

[stelli...@gmail.com]

I am running the current version of weewx and the Belchertown Skin. 
Everything's smooth and perfect, but I want to display the battery status 
of my rain meter etc. on my about page. However, I have no ida how to 
achieve this and how to get it mapped/displayed for my TE923 type weather 
station.
I tried to work with the station data mentioned 
under http://weewx.com/docs/hardware.htm#te923_notes.

I think that I am missing something very easy. Any idea?

-- 
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/531b4102-c084-48bf-9b0f-df306400e988n%40googlegroups.com.

[weewx-user] Publishing WeeWX to AWS S3

[Mike Revitt]

It is nearly 2 years since I migrated my Web Site to AWS S3 but that was 
done in a rather clumsy way. So when I moved my WeeWX deployment to my 
Rasberry Pi I decided to do it properly.

With time on my hands over Christmas I have finally gotten around to 
writing up how I did it and for those that are interested  the cost is free 
for the first 12 months then $1.00 US per month after that.

Instructions are here 



-- 
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/5038d616-e389-443c-a06f-70465c4df330n%40googlegroups.com.

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[Mike Revitt]

This was on of my main concerns when I first moved my WeeWX station to a 
Raspberry Pi, so I have added a nightly backup to AWS S3 for the database 
and as S3 now has versioning that will be my next addition so I have more 
than one backup .

I haven't gotten around to writing this up yet, but it has been working 
uninterrupted for 213 days.

If you want to know how I did it just reach out, the process is very 
similar to my solution for publishing to S3 which I have just finished 
writing up this week

On Friday, January 1, 2021 at 8:35:37 PM UTC lang@googlemail.com wrote:

> @ (not only) weatherlist
>
> If you had copied the list completely,  😉
>
> See below - bold by me.
>
> (but possibly a SSD comes cheaper than the higher capacity SLC micro SD 
> cards - still may need an enclosure with USB (best 3) interface; not too 
> expensive either)
>
> .
>
> Meteobridge enforces the use of one of the following industrial SLC cards:
>
> ..
>
>- Western Digital/SanDisk SDSDQED-00*8G*-XI, SDSDQED-0*16G*-XI, 
>SDSDQED-0*32G*-XI, SDSDQED-064G-XI (microSD Card, 8-*64* GB, SLC 
>Flash) 
>- Greenliant GLS93MP008G1-I-BZ801 (microSD Card, *8 GB*, SLC Flash) 
>
> On 01.01.2021 20:44, Michael Form wrote:
>
> As someone has previously suggested, you can boot and run a Raspberry Pi 
> off of a SSD. These are a lot more reliable than most SD cards and are 
> available with huge capacities. Unless you are buying a 1 TB or 2 TB SSD, 
> they are also relatively inexpensive. I am running several Pis, both models 
> 3 and 4, on some 500 GB and 250 GB SSDs with no problems. You can also use 
> a MSATA or M2 drive as well. 
>
> Although there are off the shelf solutions to do this (check out 
> Geekworm), the easiest way is to buy an inexpensive SATA, MSATA or M2 to 
> USB external interface and plug it into the Pi's USB port. If you use a 
> Pi4, then you can run it as a USB3 device, which is faster.
>
> Mike
>
> On 1/1/2021 2:21 PM, steep...@gmail.com wrote:
>
> There are more SLC cards available from Mouser and other distributors with 
> much lager capacities. Those quoted below would struggle to contain an 
> operating system, WeeWX and data.
>
>  
>
> Sent from Mail  for 
> Windows 10
>
>  
>
> *From: *weather list
> *Sent: *01 January 2021 17:32
> *To: *weewx...@googlegroups.com
> *Subject: *Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 
> months of data?
>
>  
>
> The Meteobridge builder requires a high endurance microSD card for their 
> NANO SD unit; I haven’t investigated to see if they come in higher 
> capacities though it seems likely they would.
>
>  
>
> *Choice of microSD Card *
>
> To avoid lots of system fails caused by worn out consumer microSD cards we 
> restrict microSD cards that can be used in the NANO to 1GB and 2GB 
> industrial SLC cards. These are world-wide available from Mouser and other 
> electronic distributors. We decided to enforce use of these high endurance 
> cards to avoid having tons of unnecessary support requests and not to harm 
> the reputation of the NANO SD by failed cards. Please trust in our 
> experience with flash storage issues that there is simply no reasonable way 
> to avoid buying of high-price, high-endurance SLC storage. These are the 
> currently supported microSD cards: 
>
> swissbit SFSD1024N1BM1TO-I-DF-221-STD (microSD Card, 1 GB, SLC Flash, 
> -40°C - 85°C)
> swissbit SFSD2048N1BM1MT-I-ME-221-STD (microSD Card, 2 GB, SLC Flash, 
> -40°C - 85°C) 
>
> swissbit SFSD2048N1BM1MT-E-ME-221-STD (microSD Card, 2 GB, SLC Flash, 
> -25°C - 85°C)
> ATP AF2GUDI (microSD Card, 2 GB, SLC Flash, -40°C – 80°C)
> Cactus KS2GRIT-803M (microSD Card, 2 GB, SLC Flash, -45°C – 90°C)
>
> Panasonic SMSC02DA1 (microSD Card, 2 GB, SLC Flash, -40°C - 85°C)
>
> Apacer MSD02GIDI-T (microSD Card, 2 GB, SLC Flash) 
>
>
>
>
>
> On 1 Jan, 2021, at 08:52, Joe  wrote:
>
>  
>
> Sandisk extreme with the red and brown two tone color.  Unfortuantely, I 
> did not have one of these in the PI at the time.  Though I do now.  I've 
> never had one fail .
>
> On Monday, December 28, 2020 at 7:23:04 PM UTC-6 robcr...@gmail.com wrote:
>
> With all this talk about "good quality" SD cards, can anyone share a 
> recommendation?
>
>  
>
> I have an SSD that I run my main WeeWX/HomeAssistant server on, but I have 
> several others that I play around with, and need to get some new SD cards 
> for that purpose, so I figure I may as well get some "good" ones.
>
>  
>
> Thanks for any suggestions.
>
>  
>
> On Monday, December 28, 2020 at 4:36:23 AM UTC-8 Joe wrote:
>
> Ok I will get a look at it in about a week after a needed vacation.
>
> On Sunday, December 27, 2020 at 8:38:26 PM UTC-6 graha...@gmail.com wrote:
>
> the .html timestamps are all current (assuming Dec 27 19:50 is current).
>
> the .png timestamps are current until middle of the month images, then all 
> old → stopping part way through image generation.
>
> some of the .

Re: [weewx-user] Re: change wind direction from degress

[Δημήτρης Βήχος]

that works!! thank you!  i have a repository to github who i keep the 
changes and some translations of skins in case of reinstall.
happy new year!!

Στις Κυριακή, 3 Ιανουαρίου 2021 στις 12:59:51 π.μ. UTC+2, ο χρήστης gjr80 
έγραψε:

> Hi,
>
> There is no single setting you can change to have Seasons display 
> directions as ordinates, unfortunately you will need to go through the 
> relevant report templates(s) and change the formatting for each tag 
> concerned to use .ordinal_compass. You will need to take care as some of 
> the tags will look a little different to what you find in the Customization 
> Guide. For example, in hilo.inc you will need to change:
>
> $archive[1].wind.gustdir.format(add_label=False)
>
> to
>
> $archive[1].wind.gustdir.ordinal_compass
>
> and
>
> $archive[1].wind.vecdir.format(add_label=False)
>
> to
>
> $archive[1].wind.vecdir.ordinal_compass
>
> You will probably want to remove some of the wind direction label tags 
> (for example $unit.label.windDir) that show the degree symbol as well.
>
> Other template files (statistics.inc springs to mind) may need similar 
> changes as well, .
>
> One other thing to keep in mind, changes to skins are fairly safe across 
> upgrades but obviously not safe against a re-install. You might want to 
> make note of your changes in case you need to re-apply them later.
>
> Gary
>
> On Sunday, 3 January 2021 at 07:50:29 UTC+10 hobbyl...@gmail.com wrote:
>
>> i have allready read this section. the ask in if theres option to apears 
>> in seasons skin the ordinates not with degress  by default , with setting 
>> in skin.conf. reading the docs says the only option for group_direction is 
>> degree_compass.
>> tried to set degree_compass=ordinal_compass but weewx stoped after that 
>> setting. 
>>
>>
>>
>>
>> Στις Σάββατο, 2 Ιανουαρίου 2021 στις 7:33:20 μ.μ. UTC+2, ο χρήστης 
>> peterq...@gmail.com έγραψε:
>>
>>> Have you looked here: http://weewx.com/docs/customizing.htm#Wind ?
>>>
>>> On Sat, Jan 2, 2021 at 9:31 AM Δημήτρης Βήχος  
>>> wrote:
>>>
 in current direction ok. i like to apply in all stastics  in day, 
 weewk, month, year .

 Στις Σάββατο, 2 Ιανουαρίου 2021 στις 2:57:27 μ.μ. UTC+2, ο χρήστης 
 storm...@gmail.com έγραψε:

> try this:   $current.windDir.ordinal_compass  
>
> On Saturday, January 2, 2021 at 6:42:00 AM UTC-5 hobbyl...@gmail.com 
> wrote:
>
>> hi everybody and happy new year!
>>
>> I wonder if there is a way to chande the wind direction statistics 
>> from degrees to direction original
>> for example from 360 to N 
>> 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+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/f69d9d7c-1b48-4600-a139-30f0e14dbb3bn%40googlegroups.com
  
 
 .

>>>
>>>
>>> -- 
>>> Peter Quinn
>>> (415)794-2264 <(415)%20794-2264>
>>>
>>

-- 
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/c3c3d24d-5bed-49b7-8d37-2ea07dd515a2n%40googlegroups.com.