[weewx-user] Re: windDir is None since upgrading to 4.6.2 from 4.5.1 on VP2

[Fische Namenlos]

I've similar failures for the WindGust, but only in the *creation *of 
"image"  for the *stacked WindRose*. I use the blue sofaskin on a renkforce 
WH2315, alias FineOffset.

It was working nicely with 4.5.1...

gjr80 schrieb am Mittwoch, 16. Februar 2022 um 02:30:05 UTC+1:

> The 4.5.1 archive record looks very much like a software generated archive 
> record, you can tell by the windDir value. The windDir value in a 
> hardware generated archive record from a VP2 appears in multiples of 12.5 
> degrees - that is fixed and a limitation of the archive record format 
> emitted from the console/logger. In a WeeWX VP2 hardware generated archive 
> record the wind direction values will be multiples of 12.5 or None. 
> Software generated archive records contain an average of the loop packet 
> windDir values. windDir in a VP2 loop packet is in whole degrees and not 
> subject to the '12.5 degree multiple' effect. So in a software generated 
> archive record windDir will be a float, usually with a number of decimal 
> places and certainly (almost always) not a multiple of 12.5. I also see 
> THSW in the archive records, THSW is only present in the LOOP2 archive 
> packet so I am guessing you are using LOOP2 instead of the normal LOOP1 
> packet. Should not be a problem but it's something out of the ordinary.
>
> Might help to see the WeeWX startup for each case and weewx.conf to 
> understand your configuration. You say record generation is set to hardware 
> in weewx.conf, that is great but not necessarily what is used by WeeWX. 
> WeeWX will try hardware and if for some reason it doesn't work/isn't 
> available WeeWX will drop back to software record generation. Always best 
> to check what is in the log.
>
> I would also look at the loop packets, what wind direction values do you 
> see in loop packets? What appears in the subsequent archive record? No need 
> to modify WeeWX, just run WeeWX directly 
>  and you will see 
> loop packets and archive records direct to console.
>
> Gary
> On Wednesday, 16 February 2022 at 03:02:54 UTC+10 James Taylor wrote:
>
>> Hello
>>
>> I've upgraded to weewx 4.6.2 and found out that my vantage Pro2 REC is 
>> giving a different output for windDir 
>>
>> record_generation is set to hardware in weewx.conf 
>>
>> I amended StdPrint to output new_archive_record to stdout and log.debug 
>> and I can see a difference
>>
>> 4.6.2 - 
>> Feb 15 16:30:15 pi weewx[21988] DEBUG weewx.engine: REC:   2022-02-15 
>> 16:30:00 GMT (1644942600) 'altimeter': '29.664795850933803', 'appTemp': 
>> '44.26912313212261', 'bar_calibration': '-0.0020013', 
>> 'bar_offset': '-0.010005', 'bar_reduction': 
>> '0.0020013', 'barometer': '29.673', 'beaufort': '2', 
>> 'cloudbase': '794.2252812978254', 'consBatteryVoltage': '4.65', 'dateTime': 
>> '1644942600', 'dayET': '0.013', 'dayRain': '0.1338582669002', 
>> 'dewpoint': '46.75340876228957', 'ET': '0.0', 'extraAlarm1': '0.0', 
>> 'extraAlarm2': '0.0', 'extraAlarm3': '0.0', 'extraAlarm4': '0.0', 
>> 'extraAlarm5': '0.0', 'extraAlarm6': '0.0', 'extraAlarm7': '0.0', 
>> 'extraAlarm8': '0.0', 'forecastIcon': '3.0', 'forecastRule': '158', 
>> 'heatindex': '47.3580004', 'highOutTemp': '48.5', 'highRadiation': 
>> '11.0', 'highUV': '0.0', 'hourRain': '0.0078740157', 'humidex': 
>> '49.280997613295085', 'inDewpoint': '50.40086122975667', 'inHumidity': 
>> '48.0', 'insideAlarm': '0.0', 'inTemp': '71.1', 'interval': '5', 
>> 'leafWet4': '0.0', 'lowOutTemp': '48.4', 'maxSolarRad': 
>> '46.94974186677293', 'monthET': '0.52', 'monthRain': '1.0787401509', 
>> 'outHumidity': '94.0', 'outsideAlarm1': '0.0', 'outsideAlarm2': '0.0', 
>> 'outTemp': '48.4', 'pressure': '29.21395918348061', 'pressure_raw': 
>> '29.2247995', 'radiation': '5.3995', 'rain': '0.0', 
>> 'rain15': '0.0', 'rain24': '0.1338582669002', 'rainAlarm': '0.0', 
>> 'rainRate': '0.0', 'rxCheckPercent': '97.375', 'soilLeafAlarm1': '0.0', 
>> 'soilLeafAlarm2': '0.0', 'soilLeafAlarm3': '0.0', 'soilLeafAlarm4': '0.0', 
>> 'stormRain': '0.1338582669002', 'stormStart': '1644883200.0', 
>> 'sunrise': '1644912960.0', 'sunset': '1644949080.0', 'sunshineDuration': 
>> '0.0', 'THSW': '45.0', 'trendIcon': '-20.0', 'txBatteryStatus': '0', 
>> 'usUnits': '1', 'UV': '0.0', 'wind_samples': '114.0', 'windchill': 
>> '45.762013144176095', 'windDir': 'None', 'windGust': '10.0', 'windGust10': 
>> '10.0', 'windGustDir': '247.5', 'windGustDir10': '247.0', 'windrun': '0.5', 
>> 'windSpeed': '6.0', 'windSpeed2': '5.7', 'windSpeed10': '5.0', 'yearET': 
>> '1.13', 'yearRain': '1.527559045801'
>>
>> Back to 4.5.1 and everything is good ( windDir: 237.52965750482582).
>>
>> Feb 15 16:50:15 pi weewx[22480] DEBUG weewx.engine: REC:  2022-02-15 
>> 16:50:00 GMT (1644943800) altimeter: 29.656827096532094, appTemp: 
>> 45.77889412649187, bar_calibration: -0.0020013, bar_offset: 
>> -0.01

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

[Fische Namenlos]

 I've similar failures for the WindGust, but only in the *creation *of 
"image"  for the *stacked WindRose*. I use the blue sofaskin on a renkforce 
WH2315, alias FineOffset.

It was working nicely with 4.5.1...


remy.l...@gmail.com schrieb am Montag, 14. Februar 2022 um 13:37:41 UTC+1:

> A *water year* (also called *hydrological year*, *discharge year* or *flow 
> year*) is a term commonly used in hydrology 
>  to describe a time period of 
> 12 months for which precipitation 
>  totals are measured. Its 
> beginning differs from the calendar year 
>  because part of the 
> precipitation that falls in late autumn and winter accumulates as snow 
>  and does not drain until the 
> following spring or summer's snowmelt 
> .
>
> Due to meteorological and geographical factors, the definition of the 
> water years varies; the United States Geological Survey 
>  defines 
> it as the period between October 1 of one year and September 30th of the 
> next. The water year is designated by the calendar year in which it ends, 
> so the 2010 water year (USGS) started on October 1, 2009 and ended on 
> September 30, 2010.
>
> One way to identify a water-year is to find that successive 12-month 
> period that most consistently, year after year, gives the highest 
> correlation between precipitation and streamflow and negligible changes in 
> storage (i.e., soil water and snow).
> Thank’s Wikipedia...
> Le lundi 14 février 2022 à 12:45:58 UTC+1, paul...@gmail.com a écrit :
>
>> Checked this morning and pleased to say Max Wind direction is now 
>> reporting and updating in the Day tab of the Statistics section. Still N/A 
>> in Week but I'm guessing it will update in due course.
>> Just out of interest I've noticed in the Statistics section the Year tab 
>> is blue and if you click on it you get the option of Year or Rain Year. 
>> What actually is the difference between these two? In my case the values 
>> reported are identical.
>> Paul
>>
>> On Sunday, 13 February 2022 at 20:01:25 UTC remy.l...@gmail.com wrote:
>>
>>> Yes, it’s the good python file, same as me  (if standard installation...)
>>> The Tom’s update/patch solves perfectly the problem and also min/max 
>>> windGustDir data base.
>>> Try stop and start weewx (logicaly same thing as restart... !?)
>>> Try to look for all wxxtype.py on your system to see if there is another 
>>> file ? Logicaly no...
>>>
>>>
>>> Le dimanche 13 février 2022 à 20:23:07 UTC+1, paul...@gmail.com a 
>>> écrit :
>>>
 Hi Remy
 Yes I did sudo /etc/init.d/weewx restart. Just in case I've done it 
 again but no change.
 Can I just check I swapped the correct wxxtypes.py file. I swapped the 
 one in /usr/share/weewx/weewx
 Paul

 On Sunday, 13 February 2022 at 18:08:44 UTC remy.l...@gmail.com wrote:

> Hi Paul.
> Have you triedto stop weewx and restart it ?
> You must do that if you modify python file.
> Cordialy 
>
>
> Le dimanche 13 février 2022 à 18:32:38 UTC+1, paul...@gmail.com a 
> écrit :
>
>> I don't report wind gust values/direction in the Current Conditions 
>> section of my Seasons skin (version 4.6.2) but in the Statistics 
>> (previously High/Low) section I've always had a Max Wind entry with both 
>> speed and direction reported. Since 4.6.2 the direction is reported as 
>> N/A 
>> so I've followed this thread and replaced the wxxtypes.py file with the 
>> new 
>> one from Tom but it doesn't seem to have made any difference to my Max 
>> Wind 
>> entry. If you look at the Statistics report below it still shows N/A for 
>> Max Wind degrees for Day and Week but for Month and Year (presumably 
>> data 
>> from 4.5.1) a degree value is reported.
>>
>> [image: Max Wind.jpg]
>> Any suggestions?
>>
>> Paul
>> On Sunday, 13 February 2022 at 15:04:26 UTC asla...@gmail.com wrote:
>>
>>> Brilliant, now it work just fine.
>>> Thanks a lot.
>>>
>>> On Sunday, February 13, 2022 at 3:28:45 PM UTC+1 remy.l...@gmail.com 
>>> wrote:
>>>
 Yes !! Thank-you Tom it works great now :

 [image: Capture d’écran de 2022-02-13 15-26-27.png]
 Le dimanche 13 février 2022 à 14:33:57 UTC+1, tke...@gmail.com a 
 écrit :

> I was able to replicate the problem. Pre V4.6, if windGustDir was 
> missing, windDir was substituted. That behavior went away with v4.6. 
> This 
> patch restores it.
>
> Index: bin/weewx/wxxtypes.py
> ===
> diff --git a/bin/weewx/wxxtypes.py b/bin/weewx/wxxtypes.

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

[Fische Namenlos]

Fische Namenlos schrieb am Mittwoch, 16. Februar 2022 um 10:52:28 UTC+1:

> I've similar failures for the WindGust, but only in the *creation *of 
> "image"  for the *stacked WindRose*. I use the blue sofaskin on a 
> renkforce WH2315, alias FineOffset.
>
> It was working nicely with 4.5.1...
>
>
> remy.l...@gmail.com schrieb am Montag, 14. Februar 2022 um 13:37:41 UTC+1:
>
>> A *water year* (also called *hydrological year*, *discharge year* or *flow 
>> year*) is a term commonly used in hydrology 
>>  to describe a time period of 
>> 12 months for which precipitation 
>>  totals are measured. Its 
>> beginning differs from the calendar year 
>>  because part of the 
>> precipitation that falls in late autumn and winter accumulates as snow 
>>  and does not drain until the 
>> following spring or summer's snowmelt 
>> .
>>
>> Due to meteorological and geographical factors, the definition of the 
>> water years varies; the United States Geological Survey 
>>  defines 
>> it as the period between October 1 of one year and September 30th of the 
>> next. The water year is designated by the calendar year in which it ends, 
>> so the 2010 water year (USGS) started on October 1, 2009 and ended on 
>> September 30, 2010.
>>
>> One way to identify a water-year is to find that successive 12-month 
>> period that most consistently, year after year, gives the highest 
>> correlation between precipitation and streamflow and negligible changes in 
>> storage (i.e., soil water and snow).
>> Thank’s Wikipedia...
>> Le lundi 14 février 2022 à 12:45:58 UTC+1, paul...@gmail.com a écrit :
>>
>>> Checked this morning and pleased to say Max Wind direction is now 
>>> reporting and updating in the Day tab of the Statistics section. Still N/A 
>>> in Week but I'm guessing it will update in due course.
>>> Just out of interest I've noticed in the Statistics section the Year tab 
>>> is blue and if you click on it you get the option of Year or Rain Year. 
>>> What actually is the difference between these two? In my case the values 
>>> reported are identical.
>>> Paul
>>>
>>> On Sunday, 13 February 2022 at 20:01:25 UTC remy.l...@gmail.com wrote:
>>>
 Yes, it’s the good python file, same as me  (if standard 
 installation...)
 The Tom’s update/patch solves perfectly the problem and also min/max 
 windGustDir data base.
 Try stop and start weewx (logicaly same thing as restart... !?)
 Try to look for all wxxtype.py on your system to see if there is 
 another file ? Logicaly no...


 Le dimanche 13 février 2022 à 20:23:07 UTC+1, paul...@gmail.com a 
 écrit :

> Hi Remy
> Yes I did sudo /etc/init.d/weewx restart. Just in case I've done it 
> again but no change.
> Can I just check I swapped the correct wxxtypes.py file. I swapped the 
> one in /usr/share/weewx/weewx
> Paul
>
> On Sunday, 13 February 2022 at 18:08:44 UTC remy.l...@gmail.com wrote:
>
>> Hi Paul.
>> Have you triedto stop weewx and restart it ?
>> You must do that if you modify python file.
>> Cordialy 
>>
>>
>> Le dimanche 13 février 2022 à 18:32:38 UTC+1, paul...@gmail.com a 
>> écrit :
>>
>>> I don't report wind gust values/direction in the Current Conditions 
>>> section of my Seasons skin (version 4.6.2) but in the Statistics 
>>> (previously High/Low) section I've always had a Max Wind entry with 
>>> both 
>>> speed and direction reported. Since 4.6.2 the direction is reported as 
>>> N/A 
>>> so I've followed this thread and replaced the wxxtypes.py file with the 
>>> new 
>>> one from Tom but it doesn't seem to have made any difference to my Max 
>>> Wind 
>>> entry. If you look at the Statistics report below it still shows N/A 
>>> for 
>>> Max Wind degrees for Day and Week but for Month and Year (presumably 
>>> data 
>>> from 4.5.1) a degree value is reported.
>>>
>>> [image: Max Wind.jpg]
>>> Any suggestions?
>>>
>>> Paul
>>> On Sunday, 13 February 2022 at 15:04:26 UTC asla...@gmail.com wrote:
>>>
 Brilliant, now it work just fine.
 Thanks a lot.

 On Sunday, February 13, 2022 at 3:28:45 PM UTC+1 
 remy.l...@gmail.com wrote:

> Yes !! Thank-you Tom it works great now :
>
> [image: Capture d’écran de 2022-02-13 15-26-27.png]
> Le dimanche 13 février 2022 à 14:33:57 UTC+1, tke...@gmail.com a 
> écrit :
>
>> I was able to replicate the problem. Pre V4.6, if windGustDir was 
>> missing, windDir was substituted. That behavior went away with v4.6. 
>> This 
>

[weewx-user] Re: Belchertown w/MQTT Temperature not updating?

[DaveStLou]

Attached is a clip from my log this morning with debug on and config files. 
I'll subscribe to the topic and post that asap.
Thanks

On Tuesday, February 15, 2022 at 5:00:03 PM UTC-6 vince wrote:

> On Tuesday, February 15, 2022 at 1:24:28 PM UTC-8 DaveStLou wrote:
>
>> On my station website OakvilleWX.com, I see MQTT updates most values 
>> real-time as it's supposed to. If I leave it up for a time though, I've 
>> noticed that the temperature doesn't update unless I refresh the page.
>>
>>
> In the absence of any logs or config files or description of your station, 
>   I can only suggest doing an external mqtt subscribe to the same topic you 
> have weewx subscribing to and verify you are sending temperature data.
>
>

-- 
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/77d7ae7d-d363-48c7-a5bd-b0fc7a49022dn%40googlegroups.com.
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2021 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

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

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

# 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.6.2

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Oakville, Missouri, USA"

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

# Altitude of the station, with the unit it is in. This is used only
# if the hardware cannot supply a value.
altitude = 515, foot# Choose 'foot' or 'meter' for unit

# Set to type of station hardware. There must be a corresponding stanza
# in this file, which includes a value for the 'driver' option.
station_type = Vantage

# If you have a website, you may specify an URL. This is required if you
# intend to register your station.
station_url = https://OakvilleWX.com

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

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

##

[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

##

#   This section is for uploading data to In

[weewx-user] Re: windDir is None since upgrading to 4.6.2 from 4.5.1 on VP2

[James Taylor]

Thanks Gary

Yes - I forgot about the 12.5 multiples thing so yes gives me a possible 
idea on what is going to work out what has changed in behavior as the 
weewx.conf hasn't changed (apart from the version details)

James

On Wednesday, February 16, 2022 at 1:30:05 AM UTC gjr80 wrote:

> The 4.5.1 archive record looks very much like a software generated archive 
> record, you can tell by the windDir value. The windDir value in a 
> hardware generated archive record from a VP2 appears in multiples of 12.5 
> degrees - that is fixed and a limitation of the archive record format 
> emitted from the console/logger. In a WeeWX VP2 hardware generated archive 
> record the wind direction values will be multiples of 12.5 or None. 
> Software generated archive records contain an average of the loop packet 
> windDir values. windDir in a VP2 loop packet is in whole degrees and not 
> subject to the '12.5 degree multiple' effect. So in a software generated 
> archive record windDir will be a float, usually with a number of decimal 
> places and certainly (almost always) not a multiple of 12.5. I also see 
> THSW in the archive records, THSW is only present in the LOOP2 archive 
> packet so I am guessing you are using LOOP2 instead of the normal LOOP1 
> packet. Should not be a problem but it's something out of the ordinary.
>
> Might help to see the WeeWX startup for each case and weewx.conf to 
> understand your configuration. You say record generation is set to hardware 
> in weewx.conf, that is great but not necessarily what is used by WeeWX. 
> WeeWX will try hardware and if for some reason it doesn't work/isn't 
> available WeeWX will drop back to software record generation. Always best 
> to check what is in the log.
>
> I would also look at the loop packets, what wind direction values do you 
> see in loop packets? What appears in the subsequent archive record? No need 
> to modify WeeWX, just run WeeWX directly 
>  and you will see 
> loop packets and archive records direct to console.
>
> Gary
> On Wednesday, 16 February 2022 at 03:02:54 UTC+10 James Taylor wrote:
>
>> Hello
>>
>> I've upgraded to weewx 4.6.2 and found out that my vantage Pro2 REC is 
>> giving a different output for windDir 
>>
>> record_generation is set to hardware in weewx.conf 
>>
>> I amended StdPrint to output new_archive_record to stdout and log.debug 
>> and I can see a difference
>>
>> 4.6.2 - 
>> Feb 15 16:30:15 pi weewx[21988] DEBUG weewx.engine: REC:   2022-02-15 
>> 16:30:00 GMT (1644942600) 'altimeter': '29.664795850933803', 'appTemp': 
>> '44.26912313212261', 'bar_calibration': '-0.0020013', 
>> 'bar_offset': '-0.010005', 'bar_reduction': 
>> '0.0020013', 'barometer': '29.673', 'beaufort': '2', 
>> 'cloudbase': '794.2252812978254', 'consBatteryVoltage': '4.65', 'dateTime': 
>> '1644942600', 'dayET': '0.013', 'dayRain': '0.1338582669002', 
>> 'dewpoint': '46.75340876228957', 'ET': '0.0', 'extraAlarm1': '0.0', 
>> 'extraAlarm2': '0.0', 'extraAlarm3': '0.0', 'extraAlarm4': '0.0', 
>> 'extraAlarm5': '0.0', 'extraAlarm6': '0.0', 'extraAlarm7': '0.0', 
>> 'extraAlarm8': '0.0', 'forecastIcon': '3.0', 'forecastRule': '158', 
>> 'heatindex': '47.3580004', 'highOutTemp': '48.5', 'highRadiation': 
>> '11.0', 'highUV': '0.0', 'hourRain': '0.0078740157', 'humidex': 
>> '49.280997613295085', 'inDewpoint': '50.40086122975667', 'inHumidity': 
>> '48.0', 'insideAlarm': '0.0', 'inTemp': '71.1', 'interval': '5', 
>> 'leafWet4': '0.0', 'lowOutTemp': '48.4', 'maxSolarRad': 
>> '46.94974186677293', 'monthET': '0.52', 'monthRain': '1.0787401509', 
>> 'outHumidity': '94.0', 'outsideAlarm1': '0.0', 'outsideAlarm2': '0.0', 
>> 'outTemp': '48.4', 'pressure': '29.21395918348061', 'pressure_raw': 
>> '29.2247995', 'radiation': '5.3995', 'rain': '0.0', 
>> 'rain15': '0.0', 'rain24': '0.1338582669002', 'rainAlarm': '0.0', 
>> 'rainRate': '0.0', 'rxCheckPercent': '97.375', 'soilLeafAlarm1': '0.0', 
>> 'soilLeafAlarm2': '0.0', 'soilLeafAlarm3': '0.0', 'soilLeafAlarm4': '0.0', 
>> 'stormRain': '0.1338582669002', 'stormStart': '1644883200.0', 
>> 'sunrise': '1644912960.0', 'sunset': '1644949080.0', 'sunshineDuration': 
>> '0.0', 'THSW': '45.0', 'trendIcon': '-20.0', 'txBatteryStatus': '0', 
>> 'usUnits': '1', 'UV': '0.0', 'wind_samples': '114.0', 'windchill': 
>> '45.762013144176095', 'windDir': 'None', 'windGust': '10.0', 'windGust10': 
>> '10.0', 'windGustDir': '247.5', 'windGustDir10': '247.0', 'windrun': '0.5', 
>> 'windSpeed': '6.0', 'windSpeed2': '5.7', 'windSpeed10': '5.0', 'yearET': 
>> '1.13', 'yearRain': '1.527559045801'
>>
>> Back to 4.5.1 and everything is good ( windDir: 237.52965750482582).
>>
>> Feb 15 16:50:15 pi weewx[22480] DEBUG weewx.engine: REC:  2022-02-15 
>> 16:50:00 GMT (1644943800) altimeter: 29.656827096532094, appTemp: 
>> 45.77889412649187, bar_calibration: -0.0020013, bar_offset: 
>> 

[weewx-user] Re: Belchertown w/MQTT Temperature not updating?

[DaveStLou]

Here's a sample from subscribing to weather/loop. Shows outside temp at 
51.4. Meanwhile my weather page at https://OakvilleWX.com on my browser was 
still showing 51.1 but wind was changing every three seconds as expected.

When I refreshed page in browser it then showed 51.4 as well.

On Wednesday, February 16, 2022 at 6:24:36 AM UTC-6 DaveStLou wrote:

> Attached is a clip from my log this morning with debug on and config 
> files. I'll subscribe to the topic and post that asap.
> Thanks
>
> On Tuesday, February 15, 2022 at 5:00:03 PM UTC-6 vince wrote:
>
>> On Tuesday, February 15, 2022 at 1:24:28 PM UTC-8 DaveStLou wrote:
>>
>>> On my station website OakvilleWX.com, I see MQTT updates most values 
>>> real-time as it's supposed to. If I leave it up for a time though, I've 
>>> noticed that the temperature doesn't update unless I refresh the page.
>>>
>>>
>> In the absence of any logs or config files or description of your 
>> station,   I can only suggest doing an external mqtt subscribe to the same 
>> topic you have weewx subscribing to and verify you are sending temperature 
>> data.
>>
>>

-- 
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/b0ef9d5f-f994-4f74-8dfe-91a7e31a9677n%40googlegroups.com.
{"dateTime": "1645015618.0", "usUnits": "1.0", "barometer": "30.008", "inTemp": 
"61.8", "inHumidity": "44.0", "outTemp": "51.4", "windSpeed": "2.0", 
"windSpeed10": "4.0", "windDir": "152.0", "outHumidity": "66.0", "rainRate": 
"0.0", "stormRain": "0.0", "dayRain": "0.0", "monthRain": "1.21", "yearRain": 
"2.7", "dayET": "0.0", "monthET": "0.0", "yearET": "0.0", "leafWet4": "0.0", 
"insideAlarm": "0.0", "rainAlarm": "0.0", "outsideAlarm1": "0.0", 
"outsideAlarm2": "0.0", "extraAlarm1": "0.0", "extraAlarm2": "0.0", 
"extraAlarm3": "0.0", "extraAlarm4": "0.0", "extraAlarm5": "0.0", 
"extraAlarm6": "0.0", "extraAlarm7": "0.0", "extraAlarm8": "0.0", 
"soilLeafAlarm1": "0.0", "soilLeafAlarm2": "0.0", "soilLeafAlarm3": "0.0", 
"soilLeafAlarm4": "0.0", "txBatteryStatus": "0.0", "consBatteryVoltage": 
"3.77", "forecastIcon": "6.0", "forecastRule": "44.0", "sunrise": 
"1645023420.0", "sunset": "1645062540.0", "rain": "0.0", "windGust": "9.0", 
"windGustDir": "130.0", "pressure": "29.41518502846202", "altimeter": 
"30.009175316592362", "appTemp": "48.135690081723865", "cloudbase": 
"3043.8641896577337", "dewpoint": "40.42699756550597", "heatindex": "49.342", 
"humidex": "51.4", "inDewpoint": "39.65455192110421", "maxSolarRad": "0.0", 
"windchill": "51.4", "beaufort": "1.0", "hourRain": "0.0", "rain24": "0.0"}
{"dateTime": "1645015616.0", "usUnits": "1.0", "barometer": "30.008", "inTemp": 
"61.8", "inHumidity": "44.0", "outTemp": "51.4", "windSpeed": "1.0", 
"windSpeed10": "4.0", "windDir": "155.0", "outHumidity": "66.0", "rainRate": 
"0.0", "stormRain": "0.0", "dayRain": "0.0", "monthRain": "1.21", "yearRain": 
"2.7", "dayET": "0.0", "monthET": "0.0", "yearET": "0.0", "leafWet4": "0.0", 
"insideAlarm": "0.0", "rainAlarm": "0.0", "outsideAlarm1": "0.0", 
"outsideAlarm2": "0.0", "extraAlarm1": "0.0", "extraAlarm2": "0.0", 
"extraAlarm3": "0.0", "extraAlarm4": "0.0", "extraAlarm5": "0.0", 
"extraAlarm6": "0.0", "extraAlarm7": "0.0", "extraAlarm8": "0.0", 
"soilLeafAlarm1": "0.0", "soilLeafAlarm2": "0.0", "soilLeafAlarm3": "0.0", 
"soilLeafAlarm4": "0.0", "txBatteryStatus": "0.0", "consBatteryVoltage": 
"3.77", "forecastIcon": "6.0", "forecastRule": "44.0", "sunrise": 
"1645023420.0", "sunset": "1645062540.0", "rain": "0.0", "windGust": "9.0", 
"windGustDir": "130.0", "pressure": "29.41518502846202", "altimeter": 
"30.009175316592362", "appTemp": "48.698959081723864", "cloudbase": 
"3043.8641896577337", "dewpoint": "40.42699756550597", "heatindex": "49.342", 
"humidex": "51.4", "inDewpoint": "39.65455192110421", "maxSolarRad": "0.0", 
"windchill": "51.4", "beaufort": "0.0", "hourRain": "0.0", "rain24": "0.0"}
qos : 0, retain : false, cmd : publish, dup : false, topic : weather/loop, 
messageId : , length : 1318, Raw payload : 
1233410097116101841051091013458323449545253484953544954464834443234117115851101051161153458323449464834443234989711409101116101114345832345148464848563444323410511084101109112345832345449465634443234105110721171091051001051161213458323452524648344432341711684101109112345832345349465234443234119105110100831121011011003458323449464834443234119105110100831121011011004948345832345246483444323411910511010068105114345832344953534648344432341711672117109105100105116121345832345454464834443234114971051108297116101345832344846483444323411511614109829710511034583234484648344432341009712182971051103458323448464834443234109101161048297105110345832344946504934443234121101971148297105110345832345046553444323410097121698434583234484648

Re: [weewx-user] Re: WeeWX V4.6.1 released

[salinois]

hello,

I just upgraded to 4.6.2-1.deb, so far so good.

to be continued.

Patrick

Le 15/02/2022 à 20:35, Tom Keffer a écrit :
For some reason, every channel in your console is active. You can try 
shutting them all off except the ISS. Either do it through the console 
( see your owners manual), or wee_device can do this.


Generally the ISS is on channel 1.

On Mon, Feb 14, 2022 at 5:37 PM Rob Cranfill  
wrote:


Well that 'splains it! :-) I'll set about removing those (and
cleaning up the DB, right? As detailed elsewhere in this thread?)

As requested,

pi@pi3b:/etc/weewx $ wee_device --info
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.2.3 (weewx.drivers.vantage)
Unable to wake up console... sleeping
Unable to wake up console... retrying
Querying...
Davis Vantage EEPROM settings:

    CONSOLE TYPE:                   Vantage Vue

    CONSOLE FIRMWARE:
      Date:                         Feb  3 2015
      Version:                      4.18

    CONSOLE SETTINGS:
      Archive interval:             60 (seconds)
      Altitude:                     150 (foot)
      Wind cup type:                large
      Rain bucket type:             0.01 inches
      Rain year start:              1
      Onboard time:                 2022-02-14 17:34:27

    CONSOLE DISPLAY UNITS:
      Barometer:                    mbar
      Temperature:                  degree_F
      Rain:                         inch
      Wind:                         mile_per_hour

    CONSOLE STATION INFO:
      Latitude (onboard):           +47.6
      Longitude (onboard):          -122.3
      Use manual or auto DST?       AUTO
      DST setting:                  N/A
      Use GMT offset or zone code?  ZONE_CODE
      Time zone code:               4
      GMT offset:                   N/A
      Temperature logging:          LAST
      Retransmit channel:           OFF (0)

    TRANSMITTERS:
      Channel   Receive   Repeater  Type
         1      active      none    iss
         2      active      none    (N/A)
         3      active      none    (N/A)
         4      active      none    (N/A)
         5      active      none    (N/A)
         6      active      none    (N/A)
         7      active      none    (N/A)
         8      active      none    (N/A)

    RECEPTION STATS:
      Total packets received:       24546
      Total packets missed:         143
      Number of resynchronizations: 0
      Longest good stretch:         677
      Number of CRC errors:         16

    BAROMETER CALIBRATION DATA:
      Current barometer reading:    29.980 inHg
      Altitude:                     150 feet
      Dew point:                    42 F
      Virtual temperature:          48 F
      Humidity correction factor:   1.8
      Correction ratio:             1.006
      Correction constant:          +0.000 inHg
      Gain:                         0.000
      Offset:                       -33.000

    OFFSETS:
      Wind direction:               +0 deg
      Inside Temperature:           +0.0 F
      Inside Humidity:              +0 %
      Outside Temperature:          +0.0 F
      Outside Humidity:             +0 %

On Monday, February 14, 2022 at 3:28:09 PM UTC-8 tke...@gmail.com
wrote:

Rob,

Before this version, weewx only reported on explicit tags. For
example, if you didn't put $current.soilTemp1 in the template,
you were not going to see it in the report.

Now it basically reports on everything that's in the database.

To stop it, look in the skin.conf file for the Seasons skin.
Near the top, you will see a stanza labelled [DisplayOptions].
In this stanza are lists of the various types. Just remove any
type for which you do not want to be included in the report.

As for where these values are coming from, I have no idea.
Either they are being emitted by your Vantage Vue, or they are
being introduced by one of your extensions. It's also possible
you are picking up sensors from a neighbor.

In fact, now that I think about it, it would be worth seeing
which sensors your Vantage is aware of. Try running

*wee_device --info*


-tk

On Mon, Feb 14, 2022 at 3:15 PM Rob Cranfill
 wrote:

First, I guess I'm just confused as to why I'm getting all
this good stuff when my previous (<4.6) installation was
happy for so long.

I just did a quick 'grep' looking around, and I do see
that the standard Seasons skin *defines* a bunch of these
unwanted values. Is that enough to cause them to be reported?

On Monday,

Re: [weewx-user] Trying to install docker and need yml assistance

[Adam Morgan]

Do you see anything wrong in the config that I posted yesterday?

Here is the view from putty:



On Tuesday, February 15, 2022 at 9:24:51 PM UTC-5 vince wrote:

> Wild guess is that you either tried to map to directories that don't 
> exist, or your volume mounts aren't working.
>
>
>

-- 
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/5aaa609b-7bc7-4f0a-9594-7bbe4f9aaed9n%40googlegroups.com.

[weewx-user] Accessing weewx data from other programs

[Seth Ratner]

Hello everyone,

Part of this is my weakness in python, but:

I'm writing an independent program in python that will calculate irrigation 
times and durations. To do this it needs information from the WeeWX 
database such as:

- Total ET for a particular day or time range
- Total rain for a day or time range
- Current rain rate

The current rain rate I can just use MQTT for, but the others require 
database queries.

I know WeeWX can pull all sorts of queries using tags, but can I use that 
system from a separate python program? Is it just a simple import? A 
complex import? Something else entirely?

For instance, in WeeWX $day($days_ago=2).rain.sum gets me what I want. If I 
can somehow use that in my own program, I would be able to completely 
remove any need to query the database directly.

But if it's not how python works, oh well.

Thanks!
Seth

-- 
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/b1bdae38-699e-494c-af65-79e282789f9dn%40googlegroups.com.

Re: [weewx-user] Re: Upgrade Raspberry Pi 2 to Raspberry Pi 4

[Seth Ratner]

If you are not using any other devices connected to the RPi2, I would set 
up the RPi4 with a fresh install on a new SD card (use the newly released 
64-bit OS). Get WeeWX installed, copy over all your customized files 
(weewx.conf, skin.conf, any custom drivers or services, etc), install any 
extensions you're using. Get the new RPi4 running correctly before you ever 
stop WeeWX on the old RPi2. When you're happy the new Pi is running the 
same as the old one, stop WeeWX on both Pis and copy the database from the 
old one to the new one. Then start WeeWX back up on both, and make sure the 
new one has the archive and is running well. 

But if your old RPi2 is working and is just running WeeWX, I don't know if 
there's much reason to upgrade to a RPi4.

On Monday, February 14, 2022 at 4:12:19 PM UTC-6 peterq...@gmail.com wrote:

> Unless you're dealing with a hardware failure of your old Raspi, I'd set 
> up the new one from scratch as suggested, but I'd do it before taking down 
> the old one.
>
> On Mon, Feb 14, 2022 at 2:01 PM vince  wrote:
>
>> Experimentation will tell you.
>> The worst that happens is it doesn't work.
>>
>> But personally I'd upgrade to the current os and take this as an 
>> opportunity to start cleanly and document how you (re)installed everything.
>>
>> On Monday, February 14, 2022 at 1:34:31 PM UTC-8 bchap...@gmail.com 
>> wrote:
>>
>>> Can I just swap out the card?
>>
>> -- 
>> 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/2d9eaf54-81e8-4758-96c1-9a7987382740n%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/15ca227d-7117-49ff-b987-d5bae765f41dn%40googlegroups.com.

Re: [weewx-user] Re: WeeWX V4.6.1 released

[Rob Cranfill]

Aha, I see that now in the 'info' output. 

After repeated applications of the proper wee_device command,

  wee_device --set-transmitter-type=*N*,10

I now have:
TRANSMITTERS:
  Channel   Receive   Repeater  Type
 1  active  noneiss
 2  inactivenone(N/A)
 3  inactivenone(N/A)
 4  inactivenone(N/A)
 5  inactivenone(N/A)
 6  inactivenone(N/A)
 7  inactivenone(N/A)
 8  inactivenone(N/A)


Thanks!

On Tuesday, February 15, 2022 at 11:35:22 AM UTC-8 tke...@gmail.com wrote:

> For some reason, every channel in your console is active. You can try 
> shutting them all off except the ISS. Either do it through the console ( 
> see your owners manual), or wee_device can do this. 
>
> Generally the ISS is on channel 1. 
>
> On Mon, Feb 14, 2022 at 5:37 PM Rob Cranfill  wrote:
>
>> Well that 'splains it! :-) I'll set about removing those (and cleaning up 
>> the DB, right? As detailed elsewhere in this thread?)
>>
>> As requested, 
>>
>> pi@pi3b:/etc/weewx $ wee_device --info
>> Using configuration file /etc/weewx/weewx.conf
>> Using Vantage driver version 3.2.3 (weewx.drivers.vantage)
>> Unable to wake up console... sleeping
>> Unable to wake up console... retrying
>> Querying...
>> Davis Vantage EEPROM settings:
>>
>> CONSOLE TYPE:   Vantage Vue
>>
>> CONSOLE FIRMWARE:
>>   Date: Feb  3 2015
>>   Version:  4.18
>>
>> CONSOLE SETTINGS:
>>   Archive interval: 60 (seconds)
>>   Altitude: 150 (foot)
>>   Wind cup type:large
>>   Rain bucket type: 0.01 inches
>>   Rain year start:  1
>>   Onboard time: 2022-02-14 17:34:27
>>
>> CONSOLE DISPLAY UNITS:
>>   Barometer:mbar
>>   Temperature:  degree_F
>>   Rain: inch
>>   Wind: mile_per_hour
>>
>> CONSOLE STATION INFO:
>>   Latitude (onboard):   +47.6
>>   Longitude (onboard):  -122.3
>>   Use manual or auto DST?   AUTO
>>   DST setting:  N/A
>>   Use GMT offset or zone code?  ZONE_CODE
>>   Time zone code:   4
>>   GMT offset:   N/A
>>   Temperature logging:  LAST
>>   Retransmit channel:   OFF (0)
>>
>> TRANSMITTERS:
>>   Channel   Receive   Repeater  Type
>>  1  active  noneiss
>>  2  active  none(N/A)
>>  3  active  none(N/A)
>>  4  active  none(N/A)
>>  5  active  none(N/A)
>>  6  active  none(N/A)
>>  7  active  none(N/A)
>>  8  active  none(N/A)
>>
>> RECEPTION STATS:
>>   Total packets received:   24546
>>   Total packets missed: 143
>>   Number of resynchronizations: 0
>>   Longest good stretch: 677
>>   Number of CRC errors: 16
>>
>> BAROMETER CALIBRATION DATA:
>>   Current barometer reading:29.980 inHg
>>   Altitude: 150 feet
>>   Dew point:42 F
>>   Virtual temperature:  48 F
>>   Humidity correction factor:   1.8
>>   Correction ratio: 1.006
>>   Correction constant:  +0.000 inHg
>>   Gain: 0.000
>>   Offset:   -33.000
>>
>> OFFSETS:
>>   Wind direction:   +0 deg
>>   Inside Temperature:   +0.0 F
>>   Inside Humidity:  +0 %
>>   Outside Temperature:  +0.0 F
>>   Outside Humidity: +0 %
>>
>> On Monday, February 14, 2022 at 3:28:09 PM UTC-8 tke...@gmail.com wrote:
>>
>>> Rob,
>>>
>>> Before this version, weewx only reported on explicit tags. For example, 
>>> if you didn't put $current.soilTemp1 in the template, you were not going to 
>>> see it in the report.
>>>
>>> Now it basically reports on everything that's in the database. 
>>>
>>> To stop it, look in the skin.conf file for the Seasons skin. Near the 
>>> top, you will see a stanza labelled [DisplayOptions]. In this stanza are 
>>> lists of the various types. Just remove any type for which you do not want 
>>> to be included in the report.
>>>
>>> As for where these values are coming from, I have no idea. Either they 
>>> are being emitted by your Vantage Vue, or they are being introduced by one 
>>> of your extensions. It's also possible you are picking up sensors from a 
>>> neighbor. 
>>>
>>> In fact, now that I think about it, it would be worth seeing which 
>>> sensors your Vantage is aware of. Try running
>>>
>>> *wee_device --info*
>>>
>>>
>>> -tk
>>>
>>> On Mon, Feb 14, 2022 at 3:15 

Re: [weewx-user] Updated to 4.6.0 Wunderground service upload fails

[Rob Cranfill]

Weird. I was just today (2/16, 8 days after this thread started) dinking 
around with my recently-upgraded-to-4.6 installation, and now WU is not 
taking my uploads, either. But the weird thing is, I've only been dealing 
with some "skin" issues, today, and did the 4.6 upgrade some time ago - 
nothing you'd think would affect WU  but the uploads only stopped 
working a couple hours ago! So, is it me, or is it WU?

On Tuesday, February 8, 2022 at 4:22:12 PM UTC-8 n0...@n0nb.us wrote:

> * On 2022 08 Feb 13:16 -0600, Phil Green wrote:
> > Have re-enabled uploading to Wunderground.
> > Seems like it is working again. 
>
> It appears to be. According to my logs it recovered around 1900z and
> then a glitch at 2000z and two at 2015z and clean since.
>
> > Thanks for your comments. 
>
> I'm following the journal in a terminal so it is easy to see how it is
> going.
>
> - Nate
>
> -- 
> "The optimist proclaims that we live in the best of all
> possible worlds. The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>
>

-- 
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/d40e0d23-79a5-46d5-a224-43f5fa3d8493n%40googlegroups.com.

Re: [weewx-user] Updated to 4.6.0 Wunderground service upload fails

[Rob Cranfill]

Thusly:

Feb 16 14:05:21 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 1 
files for report CrandardReport in 0.03 seconds
Feb 16 14:05:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/weewx/Crandard
Feb 16 14:05:24 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 11 
files for report Belchertown in 2.71 seconds
Feb 16 14:05:24 pi3b weewx[15366] INFO weewx.reportengine: Copied 2 files 
to /var/www/html/weewx/belchertown
Feb 16 14:05:26 pi3b weewx[15366] ERROR weewx.restx: Wunderground-PWS: 
Failed to publish record 2022-02-16 14:05:00 PST (1645049100): Failed 
upload after 3 tries
Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.manager: Added record 
2022-02-16 14:06:00 PST (1645049160) to database 'weewx.sdb'
Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.manager: Added record 
2022-02-16 14:06:00 PST (1645049160) to daily summary in 'weewx.sdb'
Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.restx: PWSWeather: Published 
record 2022-02-16 14:06:00 PST (1645049160)
Feb 16 14:06:18 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 8 
files for report SeasonsReport in 2.56 seconds
Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.imagegenerator: Generated 17 
images for report SeasonsReport in 2.85 seconds
Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/weewx
Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 1 
files for report CrandardReport in 0.03 seconds
Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0 files 
to /var/www/html/weewx/Crandard
Feb 16 14:06:23 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 11 
files for report Belchertown in 2.58 seconds
Feb 16 14:06:23 pi3b weewx[15366] INFO weewx.reportengine: Copied 2 files 
to /var/www/html/weewx/belchertown
Feb 16 14:06:26 pi3b weewx[15366] ERROR weewx.restx: Wunderground-PWS: 
Failed to publish record 2022-02-16 14:06:00 PST (1645049160): Failed 
upload after 3 tries

On Wednesday, February 16, 2022 at 2:05:56 PM UTC-8 Rob Cranfill wrote:

> Weird. I was just today (2/16, 8 days after this thread started) dinking 
> around with my recently-upgraded-to-4.6 installation, and now WU is not 
> taking my uploads, either. But the weird thing is, I've only been dealing 
> with some "skin" issues, today, and did the 4.6 upgrade some time ago - 
> nothing you'd think would affect WU  but the uploads only stopped 
> working a couple hours ago! So, is it me, or is it WU?
>
> On Tuesday, February 8, 2022 at 4:22:12 PM UTC-8 n0...@n0nb.us wrote:
>
>> * On 2022 08 Feb 13:16 -0600, Phil Green wrote:
>> > Have re-enabled uploading to Wunderground.
>> > Seems like it is working again. 
>>
>> It appears to be. According to my logs it recovered around 1900z and
>> then a glitch at 2000z and two at 2015z and clean since.
>>
>> > Thanks for your comments. 
>>
>> I'm following the journal in a terminal so it is easy to see how it is
>> going.
>>
>> - Nate
>>
>> -- 
>> "The optimist proclaims that we live in the best of all
>> possible worlds. The pessimist fears this is true."
>> Web: https://www.n0nb.us
>> Projects: https://github.com/N0NB
>> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>>
>>

-- 
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/286ddec7-ffab-442b-942b-b1a1f4aac192n%40googlegroups.com.

[weewx-user] No module named 'user.xstats'

[Liz Dodd]

This is a new install, because I'm replacing my server. I am using Debian 11
and install with the deb method. Weewx version is 4.6.0-1.
Having successfully setup weewx and some extensions, I have no reports. 
I'm sure someone can tell me immediately which python module I'm missing. I 
can install that and all will work, but for others installing a new system 
through deb packages will also be missing this dependency. 
$ wee_reports
Using configuration file /etc/weewx/weewx.conf
Generating for all time
Traceback (most recent call last):
  File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
obj.start()
  File "/usr/share/weewx/weewx/reportengine.py", line 378, in start
self.run()
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run
self.init_extensions(gen_dict[section_name])
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 197, in 
init_extensions
klass = weeutil.weeutil.get_object(x)
  File "/usr/share/weewx/weeutil/weeutil.py", line 1149, in get_object
mod = __import__(module)
ModuleNotFoundError: No module named 'user.xstats'

I've looked at reportengine.py and tried to work out what I am missing
# System imports:
import datetime
import ftplib
import glob
import logging
import os.path
import threading
import time
import traceback

I didn't find any python package on my system providing libftp, glob, 
logging, os.path, threading or traceback.
I have ensured that every package listed on the wiki for the install.py 
method is installed on my system. I installed packages I thought covered 
the needs of reportengine.py but the error persists.

Liz


-- 
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/a5fbfef7-3737-41ac-8250-db71df589ae1n%40googlegroups.com.

Re: [weewx-user] No module named 'user.xstats'

[Tom]

Look under /usr/share/doc/weewx/examples.  You will find xstats there and can 
install it.

Tom

From: weewx-user@googlegroups.com  on behalf of 
Liz Dodd 
Date: Wednesday, February 16, 2022 at 4:07 PM
To: weewx-user 
Subject: [weewx-user] No module named 'user.xstats'
This is a new install, because I'm replacing my server. I am using Debian 11
and install with the deb method. Weewx version is 4.6.0-1.
Having successfully setup weewx and some extensions, I have no reports.
I'm sure someone can tell me immediately which python module I'm missing. I can 
install that and all will work, but for others installing a new system through 
deb packages will also be missing this dependency.
$ wee_reports
Using configuration file /etc/weewx/weewx.conf
Generating for all time
Traceback (most recent call last):
  File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
obj.start()
  File "/usr/share/weewx/weewx/reportengine.py", line 378, in start
self.run()
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run
self.init_extensions(gen_dict[section_name])
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 197, in 
init_extensions
klass = weeutil.weeutil.get_object(x)
  File "/usr/share/weewx/weeutil/weeutil.py", line 1149, in get_object
mod = __import__(module)
ModuleNotFoundError: No module named 'user.xstats'

I've looked at reportengine.py and tried to work out what I am missing
# System imports:
import datetime
import ftplib
import glob
import logging
import os.path
import threading
import time
import traceback

I didn't find any python package on my system providing libftp, glob, logging, 
os.path, threading or traceback.
I have ensured that every package listed on the wiki for the install.py method 
is installed on my system. I installed packages I thought covered the needs of 
reportengine.py but the error persists.

Liz


--
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/a5fbfef7-3737-41ac-8250-db71df589ae1n%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/BN7PR17MB232181E4025A89506327058FFF359%40BN7PR17MB2321.namprd17.prod.outlook.com.

[weewx-user] Re: windDir is None since upgrading to 4.6.2 from 4.5.1 on VP2

[James Taylor]

Tonight's debug

So I've detected that I'm not getting windDir on the archive record from 
the Vantage Pro 2 on the records coming every 5 mins, compared to any 
archive records received after a restart, so possibly a hardware issue.

PRESENT -
Feb 16 21:41:02 pi weewx[5179] DEBUG weewx.drivers.vantage: Getting archive 
packets since 2022-02-16 21:25:00 GMT (1645046700)
Feb 16 21:41:02 pi weewx[5179] DEBUG weewx.drivers.vantage: Gentle wake up 
of console successful
Feb 16 21:41:02 pi weewx[5179] DEBUG weewx.drivers.vantage: Retrieving 1 
page(s); starting index= 0
Feb 16 21:41:02 pi weewx[5179] DEBUG weewx.engine: REC:  2022-02-16 
21:40:00 GMT (1645047600) 'barometer': '29.472', 'consBatteryVoltage': 
'None', 'dateTime': '1645047600', 'ET': '0.0', 'forecastRule': '192', 
'highOutTemp': '53.5', 'highRadiation': '0.0', 'highUV': '0.0', 
'inHumidity': '53.0', 'inTemp': '72.5', 'interval': '5', 'lowOutTemp': 
'53.4', 'outHumidity': '86.0', 'outTemp': '53.5', 'radiation': '0.0', 
'rain': '0.0', 'rainRate': '0.0', 'rxCheckPercent': '19.6458332', 
'txBatteryStatus': 'None', 'usUnits': '1', 'UV': '0.0', 'wind_samples': 
'23.0', 'windDir': '270.0', 'windGust': '13.0', 'windGustDir': '247.5', 
'windSpeed': '7.0'
Feb 16 21:41:02 pi weewx[5179] INFO weewx.wxxtypes: Type beaufort has been 
deprecated. Use unit beaufort instead.

MISSING -
Feb 16 22:30:15 pi weewx[5796] DEBUG weewx.engine: REC:  2022-02-16 
22:30:00 GMT (1645050600) 'barometer': '29.511', 'consBatteryVoltage': 
'4.66', 'dateTime': '1645050600', 'ET': '0.0', 'forecastRule': '122', 
'highOutTemp': '52.1', 'highRadiation': '0.0', 'highUV': '0.0', 
'inHumidity': '50.0', 'inTemp': '75.6', 'interval': '5', 'lowOutTemp': 
'51.9', 'outHumidity': '78.0', 'outTemp': '51.9', 'radiation': '0.0', 
'rain': '0.0', 'rainRate': '0.0', 'rxCheckPercent': '99.9375', 
'txBatteryStatus': '0', 'usUnits': '1', 'UV': '0.0', 'wind_samples': 
'117.0', 'windGust': '14.0', 'windGustDir': '247.5', 'windSpeed': '8.0'

I've also worked out that, I appear to be getting caught up with getting a 
weewx.CannotCalculate (hence a None) from calc_windDir in wxxtypes.py, 
because the default calculation is software for windDir under wxservices.py

If I set it to windDir = hardware, then it uses the loop entries and 
creates the averages!

James
On Wednesday, February 16, 2022 at 12:26:51 PM UTC James Taylor wrote:

> Thanks Gary
>
> Yes - I forgot about the 12.5 multiples thing so yes gives me a possible 
> idea on what is going to work out what has changed in behavior as the 
> weewx.conf hasn't changed (apart from the version details)
>
> James
>
> On Wednesday, February 16, 2022 at 1:30:05 AM UTC gjr80 wrote:
>
>> The 4.5.1 archive record looks very much like a software generated 
>> archive record, you can tell by the windDir value. The windDir value in 
>> a hardware generated archive record from a VP2 appears in multiples of 12.5 
>> degrees - that is fixed and a limitation of the archive record format 
>> emitted from the console/logger. In a WeeWX VP2 hardware generated archive 
>> record the wind direction values will be multiples of 12.5 or None. 
>> Software generated archive records contain an average of the loop packet 
>> windDir values. windDir in a VP2 loop packet is in whole degrees and not 
>> subject to the '12.5 degree multiple' effect. So in a software generated 
>> archive record windDir will be a float, usually with a number of decimal 
>> places and certainly (almost always) not a multiple of 12.5. I also see 
>> THSW in the archive records, THSW is only present in the LOOP2 archive 
>> packet so I am guessing you are using LOOP2 instead of the normal LOOP1 
>> packet. Should not be a problem but it's something out of the ordinary.
>>
>> Might help to see the WeeWX startup for each case and weewx.conf to 
>> understand your configuration. You say record generation is set to hardware 
>> in weewx.conf, that is great but not necessarily what is used by WeeWX. 
>> WeeWX will try hardware and if for some reason it doesn't work/isn't 
>> available WeeWX will drop back to software record generation. Always best 
>> to check what is in the log.
>>
>> I would also look at the loop packets, what wind direction values do you 
>> see in loop packets? What appears in the subsequent archive record? No need 
>> to modify WeeWX, just run WeeWX directly 
>>  and you will see 
>> loop packets and archive records direct to console.
>>
>> Gary
>> On Wednesday, 16 February 2022 at 03:02:54 UTC+10 James Taylor wrote:
>>
>>> Hello
>>>
>>> I've upgraded to weewx 4.6.2 and found out that my vantage Pro2 REC is 
>>> giving a different output for windDir 
>>>
>>> record_generation is set to hardware in weewx.conf 
>>>
>>> I amended StdPrint to output new_archive_record to stdout and log.debug 
>>> and I can see a difference
>>>
>>> 4.6.2 - 
>>> Feb 15 16:30:15 pi weewx[21988] DEBUG weewx.engine: REC:   2022-02-15 
>>> 16:30:00

Re: [weewx-user] Updated to 4.6.0 Wunderground service upload fails

[gjr80]

My money is on WU. 

You could set debug = 3 in weewx.conf then restart WeeWX to increase the 
debug log output for the WU uploads. This will show you the data being sent 
by WeeWX along with any response from WU, though I would not expect to see 
too much useful info being provided back from WU. Setting debug = 3 will 
likely result in a lot of debug info in your log so it might take a bit to 
pick out the WU entries but they should be fairly self evident.

Gary

On Thursday, 17 February 2022 at 08:07:30 UTC+10 robcr...@gmail.com wrote:

> Thusly:
>
> Feb 16 14:05:21 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 1 
> files for report CrandardReport in 0.03 seconds
> Feb 16 14:05:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0 files 
> to /var/www/html/weewx/Crandard
> Feb 16 14:05:24 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 
> 11 files for report Belchertown in 2.71 seconds
> Feb 16 14:05:24 pi3b weewx[15366] INFO weewx.reportengine: Copied 2 files 
> to /var/www/html/weewx/belchertown
> Feb 16 14:05:26 pi3b weewx[15366] ERROR weewx.restx: Wunderground-PWS: 
> Failed to publish record 2022-02-16 14:05:00 PST (1645049100): Failed 
> upload after 3 tries
> Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.manager: Added record 
> 2022-02-16 14:06:00 PST (1645049160) to database 'weewx.sdb'
> Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.manager: Added record 
> 2022-02-16 14:06:00 PST (1645049160) to daily summary in 'weewx.sdb'
> Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.restx: PWSWeather: Published 
> record 2022-02-16 14:06:00 PST (1645049160)
> Feb 16 14:06:18 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 8 
> files for report SeasonsReport in 2.56 seconds
> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.imagegenerator: Generated 17 
> images for report SeasonsReport in 2.85 seconds
> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0 files 
> to /var/www/html/weewx
> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 1 
> files for report CrandardReport in 0.03 seconds
> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0 files 
> to /var/www/html/weewx/Crandard
> Feb 16 14:06:23 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 
> 11 files for report Belchertown in 2.58 seconds
> Feb 16 14:06:23 pi3b weewx[15366] INFO weewx.reportengine: Copied 2 files 
> to /var/www/html/weewx/belchertown
> Feb 16 14:06:26 pi3b weewx[15366] ERROR weewx.restx: Wunderground-PWS: 
> Failed to publish record 2022-02-16 14:06:00 PST (1645049160): Failed 
> upload after 3 tries
>
> On Wednesday, February 16, 2022 at 2:05:56 PM UTC-8 Rob Cranfill wrote:
>
>> Weird. I was just today (2/16, 8 days after this thread started) dinking 
>> around with my recently-upgraded-to-4.6 installation, and now WU is not 
>> taking my uploads, either. But the weird thing is, I've only been dealing 
>> with some "skin" issues, today, and did the 4.6 upgrade some time ago - 
>> nothing you'd think would affect WU  but the uploads only stopped 
>> working a couple hours ago! So, is it me, or is it WU?
>>
>> On Tuesday, February 8, 2022 at 4:22:12 PM UTC-8 n0...@n0nb.us wrote:
>>
>>> * On 2022 08 Feb 13:16 -0600, Phil Green wrote: 
>>> > Have re-enabled uploading to Wunderground. 
>>> > Seems like it is working again. 
>>>
>>> It appears to be. According to my logs it recovered around 1900z and 
>>> then a glitch at 2000z and two at 2015z and clean since. 
>>>
>>> > Thanks for your comments. 
>>>
>>> I'm following the journal in a terminal so it is easy to see how it is 
>>> going. 
>>>
>>> - Nate 
>>>
>>> -- 
>>> "The optimist proclaims that we live in the best of all 
>>> possible worlds. The pessimist fears this is true." 
>>> Web: https://www.n0nb.us 
>>> Projects: https://github.com/N0NB 
>>> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 
>>>
>>>

-- 
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/b381653d-c2d3-420c-9ec3-c964f2f1e324n%40googlegroups.com.

Re: [weewx-user] Updated to 4.6.0 Wunderground service upload fails

[Rob Cranfill]

I should have held my tongue (fingers?) - it's back up.

On Wednesday, February 16, 2022 at 3:07:52 PM UTC-8 gjr80 wrote:

> My money is on WU. 
>
> You could set debug = 3 in weewx.conf then restart WeeWX to increase the 
> debug log output for the WU uploads. This will show you the data being sent 
> by WeeWX along with any response from WU, though I would not expect to see 
> too much useful info being provided back from WU. Setting debug = 3 will 
> likely result in a lot of debug info in your log so it might take a bit to 
> pick out the WU entries but they should be fairly self evident.
>
> Gary
>
> On Thursday, 17 February 2022 at 08:07:30 UTC+10 robcr...@gmail.com wrote:
>
>> Thusly:
>>
>> Feb 16 14:05:21 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 
>> 1 files for report CrandardReport in 0.03 seconds
>> Feb 16 14:05:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0 files 
>> to /var/www/html/weewx/Crandard
>> Feb 16 14:05:24 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 
>> 11 files for report Belchertown in 2.71 seconds
>> Feb 16 14:05:24 pi3b weewx[15366] INFO weewx.reportengine: Copied 2 files 
>> to /var/www/html/weewx/belchertown
>> Feb 16 14:05:26 pi3b weewx[15366] ERROR weewx.restx: Wunderground-PWS: 
>> Failed to publish record 2022-02-16 14:05:00 PST (1645049100): Failed 
>> upload after 3 tries
>> Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.manager: Added record 
>> 2022-02-16 14:06:00 PST (1645049160) to database 'weewx.sdb'
>> Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.manager: Added record 
>> 2022-02-16 14:06:00 PST (1645049160) to daily summary in 'weewx.sdb'
>> Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.restx: PWSWeather: Published 
>> record 2022-02-16 14:06:00 PST (1645049160)
>> Feb 16 14:06:18 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 
>> 8 files for report SeasonsReport in 2.56 seconds
>> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.imagegenerator: Generated 17 
>> images for report SeasonsReport in 2.85 seconds
>> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0 files 
>> to /var/www/html/weewx
>> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 
>> 1 files for report CrandardReport in 0.03 seconds
>> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0 files 
>> to /var/www/html/weewx/Crandard
>> Feb 16 14:06:23 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated 
>> 11 files for report Belchertown in 2.58 seconds
>> Feb 16 14:06:23 pi3b weewx[15366] INFO weewx.reportengine: Copied 2 files 
>> to /var/www/html/weewx/belchertown
>> Feb 16 14:06:26 pi3b weewx[15366] ERROR weewx.restx: Wunderground-PWS: 
>> Failed to publish record 2022-02-16 14:06:00 PST (1645049160): Failed 
>> upload after 3 tries
>>
>> On Wednesday, February 16, 2022 at 2:05:56 PM UTC-8 Rob Cranfill wrote:
>>
>>> Weird. I was just today (2/16, 8 days after this thread started) dinking 
>>> around with my recently-upgraded-to-4.6 installation, and now WU is not 
>>> taking my uploads, either. But the weird thing is, I've only been dealing 
>>> with some "skin" issues, today, and did the 4.6 upgrade some time ago - 
>>> nothing you'd think would affect WU  but the uploads only stopped 
>>> working a couple hours ago! So, is it me, or is it WU?
>>>
>>> On Tuesday, February 8, 2022 at 4:22:12 PM UTC-8 n0...@n0nb.us wrote:
>>>
 * On 2022 08 Feb 13:16 -0600, Phil Green wrote: 
 > Have re-enabled uploading to Wunderground. 
 > Seems like it is working again. 

 It appears to be. According to my logs it recovered around 1900z and 
 then a glitch at 2000z and two at 2015z and clean since. 

 > Thanks for your comments. 

 I'm following the journal in a terminal so it is easy to see how it is 
 going. 

 - Nate 

 -- 
 "The optimist proclaims that we live in the best of all 
 possible worlds. The pessimist fears this is true." 
 Web: https://www.n0nb.us 
 Projects: https://github.com/N0NB 
 GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819 



-- 
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/f3b6cc22-d02e-4639-9816-ee2df79a24a9n%40googlegroups.com.

Re: [weewx-user] Updated to 4.6.0 Wunderground service upload fails

[Tom Keffer]

Through the years we've learned that when it comes to the WU, it's best not
to expend any excess energy. It's almost always their fault. Flakiest API
on the internet.

On Wed, Feb 16, 2022 at 3:39 PM Rob Cranfill  wrote:

> I should have held my tongue (fingers?) - it's back up.
>
> On Wednesday, February 16, 2022 at 3:07:52 PM UTC-8 gjr80 wrote:
>
>> My money is on WU.
>>
>> You could set debug = 3 in weewx.conf then restart WeeWX to increase the
>> debug log output for the WU uploads. This will show you the data being sent
>> by WeeWX along with any response from WU, though I would not expect to see
>> too much useful info being provided back from WU. Setting debug = 3 will
>> likely result in a lot of debug info in your log so it might take a bit to
>> pick out the WU entries but they should be fairly self evident.
>>
>> Gary
>>
>> On Thursday, 17 February 2022 at 08:07:30 UTC+10 robcr...@gmail.com
>> wrote:
>>
>>> Thusly:
>>>
>>> Feb 16 14:05:21 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated
>>> 1 files for report CrandardReport in 0.03 seconds
>>> Feb 16 14:05:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0
>>> files to /var/www/html/weewx/Crandard
>>> Feb 16 14:05:24 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated
>>> 11 files for report Belchertown in 2.71 seconds
>>> Feb 16 14:05:24 pi3b weewx[15366] INFO weewx.reportengine: Copied 2
>>> files to /var/www/html/weewx/belchertown
>>> Feb 16 14:05:26 pi3b weewx[15366] ERROR weewx.restx: Wunderground-PWS:
>>> Failed to publish record 2022-02-16 14:05:00 PST (1645049100): Failed
>>> upload after 3 tries
>>> Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.manager: Added record
>>> 2022-02-16 14:06:00 PST (1645049160) to database 'weewx.sdb'
>>> Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.manager: Added record
>>> 2022-02-16 14:06:00 PST (1645049160) to daily summary in 'weewx.sdb'
>>> Feb 16 14:06:15 pi3b weewx[15366] INFO weewx.restx: PWSWeather:
>>> Published record 2022-02-16 14:06:00 PST (1645049160)
>>> Feb 16 14:06:18 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated
>>> 8 files for report SeasonsReport in 2.56 seconds
>>> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.imagegenerator: Generated
>>> 17 images for report SeasonsReport in 2.85 seconds
>>> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0
>>> files to /var/www/html/weewx
>>> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated
>>> 1 files for report CrandardReport in 0.03 seconds
>>> Feb 16 14:06:21 pi3b weewx[15366] INFO weewx.reportengine: Copied 0
>>> files to /var/www/html/weewx/Crandard
>>> Feb 16 14:06:23 pi3b weewx[15366] INFO weewx.cheetahgenerator: Generated
>>> 11 files for report Belchertown in 2.58 seconds
>>> Feb 16 14:06:23 pi3b weewx[15366] INFO weewx.reportengine: Copied 2
>>> files to /var/www/html/weewx/belchertown
>>> Feb 16 14:06:26 pi3b weewx[15366] ERROR weewx.restx: Wunderground-PWS:
>>> Failed to publish record 2022-02-16 14:06:00 PST (1645049160): Failed
>>> upload after 3 tries
>>>
>>> On Wednesday, February 16, 2022 at 2:05:56 PM UTC-8 Rob Cranfill wrote:
>>>
 Weird. I was just today (2/16, 8 days after this thread started)
 dinking around with my recently-upgraded-to-4.6 installation, and now WU is
 not taking my uploads, either. But the weird thing is, I've only been
 dealing with some "skin" issues, today, and did the 4.6 upgrade some time
 ago - nothing you'd think would affect WU  but the uploads only stopped
 working a couple hours ago! So, is it me, or is it WU?

 On Tuesday, February 8, 2022 at 4:22:12 PM UTC-8 n0...@n0nb.us wrote:

> * On 2022 08 Feb 13:16 -0600, Phil Green wrote:
> > Have re-enabled uploading to Wunderground.
> > Seems like it is working again.
>
> It appears to be. According to my logs it recovered around 1900z and
> then a glitch at 2000z and two at 2015z and clean since.
>
> > Thanks for your comments.
>
> I'm following the journal in a terminal so it is easy to see how it is
> going.
>
> - Nate
>
> --
> "The optimist proclaims that we live in the best of all
> possible worlds. The pessimist fears this is true."
> Web: https://www.n0nb.us
> Projects: https://github.com/N0NB
> GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819
>
> --
> 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/f3b6cc22-d02e-4639-9816-ee2df79a24a9n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"

Re: [weewx-user] Re: WeeWX V4.6.1 released

[Tom Keffer]

Rob, I'll be curious to hear whether you continue to get bogus database
entries after doing this.

On Wed, Feb 16, 2022 at 11:50 AM Rob Cranfill  wrote:

> Aha, I see that now in the 'info' output.
>
> After repeated applications of the proper wee_device command,
>
>   wee_device --set-transmitter-type=*N*,10
>
> I now have:
> TRANSMITTERS:
>   Channel   Receive   Repeater  Type
>  1  active  noneiss
>  2  inactivenone(N/A)
>  3  inactivenone(N/A)
>  4  inactivenone(N/A)
>  5  inactivenone(N/A)
>  6  inactivenone(N/A)
>  7  inactivenone(N/A)
>  8  inactivenone(N/A)
>
>
> Thanks!
>
> On Tuesday, February 15, 2022 at 11:35:22 AM UTC-8 tke...@gmail.com wrote:
>
>> For some reason, every channel in your console is active. You can try
>> shutting them all off except the ISS. Either do it through the console (
>> see your owners manual), or wee_device can do this.
>>
>> Generally the ISS is on channel 1.
>>
>> On Mon, Feb 14, 2022 at 5:37 PM Rob Cranfill  wrote:
>>
>>> Well that 'splains it! :-) I'll set about removing those (and cleaning
>>> up the DB, right? As detailed elsewhere in this thread?)
>>>
>>> As requested,
>>>
>>> pi@pi3b:/etc/weewx $ wee_device --info
>>> Using configuration file /etc/weewx/weewx.conf
>>> Using Vantage driver version 3.2.3 (weewx.drivers.vantage)
>>> Unable to wake up console... sleeping
>>> Unable to wake up console... retrying
>>> Querying...
>>> Davis Vantage EEPROM settings:
>>>
>>> CONSOLE TYPE:   Vantage Vue
>>>
>>> CONSOLE FIRMWARE:
>>>   Date: Feb  3 2015
>>>   Version:  4.18
>>>
>>> CONSOLE SETTINGS:
>>>   Archive interval: 60 (seconds)
>>>   Altitude: 150 (foot)
>>>   Wind cup type:large
>>>   Rain bucket type: 0.01 inches
>>>   Rain year start:  1
>>>   Onboard time: 2022-02-14 17:34:27
>>>
>>> CONSOLE DISPLAY UNITS:
>>>   Barometer:mbar
>>>   Temperature:  degree_F
>>>   Rain: inch
>>>   Wind: mile_per_hour
>>>
>>> CONSOLE STATION INFO:
>>>   Latitude (onboard):   +47.6
>>>   Longitude (onboard):  -122.3
>>>   Use manual or auto DST?   AUTO
>>>   DST setting:  N/A
>>>   Use GMT offset or zone code?  ZONE_CODE
>>>   Time zone code:   4
>>>   GMT offset:   N/A
>>>   Temperature logging:  LAST
>>>   Retransmit channel:   OFF (0)
>>>
>>> TRANSMITTERS:
>>>   Channel   Receive   Repeater  Type
>>>  1  active  noneiss
>>>  2  active  none(N/A)
>>>  3  active  none(N/A)
>>>  4  active  none(N/A)
>>>  5  active  none(N/A)
>>>  6  active  none(N/A)
>>>  7  active  none(N/A)
>>>  8  active  none(N/A)
>>>
>>> RECEPTION STATS:
>>>   Total packets received:   24546
>>>   Total packets missed: 143
>>>   Number of resynchronizations: 0
>>>   Longest good stretch: 677
>>>   Number of CRC errors: 16
>>>
>>> BAROMETER CALIBRATION DATA:
>>>   Current barometer reading:29.980 inHg
>>>   Altitude: 150 feet
>>>   Dew point:42 F
>>>   Virtual temperature:  48 F
>>>   Humidity correction factor:   1.8
>>>   Correction ratio: 1.006
>>>   Correction constant:  +0.000 inHg
>>>   Gain: 0.000
>>>   Offset:   -33.000
>>>
>>> OFFSETS:
>>>   Wind direction:   +0 deg
>>>   Inside Temperature:   +0.0 F
>>>   Inside Humidity:  +0 %
>>>   Outside Temperature:  +0.0 F
>>>   Outside Humidity: +0 %
>>>
>>> On Monday, February 14, 2022 at 3:28:09 PM UTC-8 tke...@gmail.com wrote:
>>>
 Rob,

 Before this version, weewx only reported on explicit tags. For example,
 if you didn't put $current.soilTemp1 in the template, you were not going to
 see it in the report.

 Now it basically reports on everything that's in the database.

 To stop it, look in the skin.conf file for the Seasons skin. Near the
 top, you will see a stanza labelled [DisplayOptions]. In this stanza are
 lists of the various types. Just remove any type for which you do not want
 to be included in the report.

 As for where these values are coming from, I have no idea. Either they
 are being emitted by your Vantage Vue, or they are being introduced by one
 of your exte

Re: [weewx-user] Accessing weewx data from other programs

[Tom Keffer]

You could access the WeeWX database API directly. For example, the
equivalent query for $day($days_ago=2).rain.sum would be

weewx.xtypes.get_aggregate('rain', ts, 'sum', db_manager)

where 'ts' is the timespan that covers two days ago. This one is easy
because the "xtypes" interface is reasonably well documented. See the Wiki
article, "WeeWX V4 user defined types
".

But some queries might require extensions, both from users and within WeeWX
itself.

Provided you're not doing anything too fancy, I'd just do the queries
directly to the database.

On Wed, Feb 16, 2022 at 6:50 AM Seth Ratner  wrote:

> Hello everyone,
>
> Part of this is my weakness in python, but:
>
> I'm writing an independent program in python that will calculate
> irrigation times and durations. To do this it needs information from the
> WeeWX database such as:
>
> - Total ET for a particular day or time range
> - Total rain for a day or time range
> - Current rain rate
>
> The current rain rate I can just use MQTT for, but the others require
> database queries.
>
> I know WeeWX can pull all sorts of queries using tags, but can I use that
> system from a separate python program? Is it just a simple import? A
> complex import? Something else entirely?
>
> For instance, in WeeWX $day($days_ago=2).rain.sum gets me what I want. If
> I can somehow use that in my own program, I would be able to completely
> remove any need to query the database directly.
>
> But if it's not how python works, oh well.
>
> Thanks!
> Seth
>
> --
> 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/b1bdae38-699e-494c-af65-79e282789f9dn%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/CAPq0zEA9yDLP1Lxq7hbkro1QF2CVQyNsm953wGNZUtaSw0XrRQ%40mail.gmail.com.

Re: [weewx-user] No module named 'user.xstats'

[Liz]

On Wed, 16 Feb 2022 22:40:29 +
Tom  wrote:

> Look under /usr/share/doc/weewx/examples.  You will find xstats there
> and can install it.
> 
> Tom
> 
Thanks Tom

-- 
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/20220217114220.75b12c73.edodd55%40gmail.com.

[weewx-user] All You Ever Wanted to Know About Phenology But Were Afraid to Ask

[Chuck Rhode]

I've updated my Phenology Extension to v1.3 for WeeWX 4.6.2.  There
are no new features.

My WeeWX extension may be downloaded from its own Web site, which
assumes the reader has already installed WeeWX and is familiar with
its architecture and configuration.

o http://lacusveris.com/Phenology

The discussion on the Web site about phenology in general and the need
for models of insect and plant development is aimed at enthusiasts.
Casual readers may, of course, skip the boring bits.

Suffice it to say that phenology is the study of seasonal biological
development. Growth of plants and animals is dependent on food,
nutrients, water, and light. Assuming that these are abundant, the
factor that determines the speed of development is temperature. Models
of crop and insect development are thus based on daily temperatures.
Developmental stages are observed to follow the product of temperature
and time: Growing Degree-Days.

The Web site delves into chemical treatments for apple codling moth,
using this insect as an example of applying a Growing Degree-Day
developmental model to a real-world problem.  The data from a weather
station tracks daily minimum and maximum temperatures, and my WeeWX
extension charts when egg laying is likely to be occurring based on
cumulative Growing Degree-Days.  Then orchard spraying can begin with
less risk of waste due to starting too early or too late.

-- 
.. Be Seeing You,
.. Chuck Rhode, Sheboygan, WI, USA
.. Weather:  http://LacusVeris.com/WX
.. 40° — Wind NW 5 mph — Sky overcast.

-- 
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/20220216192459.7fcded3e%40wealthy.