Re: [weewx-user] Re: sftp on 3.9.2, RPI3B -- **still** not working with several methods

[Messy Potamia]

Please be advised I have been using scp in conjunction with ssh in my
scripts to move things around every five minutes (weather station
stuff & wx photos).

On Sat, Feb 19, 2022 at 8:03 AM 'Dr. Thomas Tuch' via weewx-user
 wrote:
>
> Dear Rob
> After moving to a different server i have been trying to get sftp to work 
> with weewx and never managed to get pysftp compiled, probably because my pi 
> is running Ubuntu 16. This I cannot change because my home automation is 
> running on the same pi3b - I would not like to mess with heating etc in 
> German winter :-) I would therefore be happy to get a copy of your hack. 
> Thank you in advance. Thomas
>
>
> robcr...@gmail.com schrieb am Mittwoch, 27. Mai 2020 um 18:09:56 UTC+2:
>>
>> Dear Mr or Ms Potamia, ;-)
>>
>> I have code that I hacked into the standard Weewx base that implements 
>> proper sftp. If you would like a copy I can send it to you. (And anyone else 
>> who’d like a copy.) Just one modified file.
>>
>> /rob
>
> --
> 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/GdlSK3vTvYE/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/f0444643-d438-47ab-b11c-5a9bf624222en%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/CAB7-S77hMJi8nwrnGP2XmrTP0VRqqEtczn7EY0c8rA4C67%2B0YA%40mail.gmail.com.

Re: [weewx-user] best way for running a driver program as standalone

[Tom Keffer]

We need a little more information. For example, you said you tried to
install the requirements, but did not give the commands you tried. Did you
use pip? Or apt-get? Or, something else?

I am guessing that you probably got the
distutils.errors.DistutilsOptionError error because you tried installing
the prerequisites in the same directory as weewx. If you try this, venv
will see the setup.cfg file and try and install the prerequisites in
/home/weewx.

This works for me with venv.

tkeffer@nuc:~$ *cd ~*
tkeffer@nuc:~$ *python3 -m venv py-weewx*
tkeffer@nuc:~$ *source py-weewx/bin/activate*
(py-weewx) tkeffer@nuc:~$ *python3 -m pip install configobj*
(py-weewx) tkeffer@nuc:~$ *python3 -m pip install Cheetah3*
(py-weewx) tkeffer@nuc:~$ *python3 -m pip install Pillow*
(py-weewx) tkeffer@nuc:~$ *python3 -m pip install pyserial*
(py-weewx) tkeffer@nuc:~$ *python3 -m pip install pyusb*
(py-weewx) tkeffer@nuc:~$ *wget
http://weewx.com/downloads/weewx-4.6.2.tar.gz
*
(py-weewx) tkeffer@nuc:~$ *tar xvf weewx-4.6.2.tar.gz *
(py-weewx) tkeffer@nuc:~$ *cd weewx-4.6.2*
(py-weewx) tkeffer@nuc:~/weewx-4.6.2$ *PYTHONPATH=bin python3 -m
weewx.drivers.vantage*
{'dateTime': 1645274802, 'usUnits': 1, 'barometer': 30.141, 'inTemp': 68.9,
'inHumidity': 41.0, 'outTemp': 42.1, 'windSpeed': 1.0, 'windSpeed10': 3.0,
'windDir': 202.0, 'outHumidity': 80.0, 'rainRate': 0.0, 'UV': 0.0,
'radiation': 0.0, 'stormRain': 0.0, 'dayRain': 0.0, 'monthRain': 0.2,
'yearRain': 17.85, 'dayET': 0.004, 'monthET': 1.03, 'yearET': 1.52,
'leafWet4': 0.0, 'insideAlarm': 0, 'rainAlarm': 0, 'outsideAlarm1': 0,
'outsideAlarm2': 0, 'extraAlarm1': 0, 'extraAlarm2': 0, 'extraAlarm3': 0,
'extraAlarm4': 0, 'extraAlarm5': 0, 'extraAlarm6': 0, 'extraAlarm7': 0,
'extraAlarm8': 0, 'soilLeafAlarm1': 0, 'soilLeafAlarm2': 0,
'soilLeafAlarm3': 0, 'soilLeafAlarm4': 0, 'txBatteryStatus': 0,
'consBatteryVoltage': 3.83, 'forecastIcon': 6, 'forecastRule': 63,
'sunrise': 1645282920, 'sunset': 1645321140, 'rain': None}
{'dateTime': 1645274803, 'usUnits': 1, 'barometer': 30.141, 'inTemp': 68.9,
'inHumidity': 41.0, 'outTemp': 42.1, 'windSpeed': 1.0, 'windSpeed10': 3.0,
'windDir': 202.0, 'outHumidity': 80.0, 'rainRate': 0.0, 'UV': 0.0,
'radiation': 0.0, 'stormRain': 0.0, 'dayRain': 0.0, 'monthRain': 0.2,
'yearRain': 17.85, 'dayET': 0.004, 'monthET': 1.03, 'yearET': 1.52,
'leafWet4': 0.0, 'insideAlarm': 0, 'rainAlarm': 0, 'outsideAlarm1': 0,
'outsideAlarm2': 0, 'extraAlarm1': 0, 'extraAlarm2': 0, 'extraAlarm3': 0,
'extraAlarm4': 0, 'extraAlarm5': 0, 'extraAlarm6': 0, 'extraAlarm7': 0,
'extraAlarm8': 0, 'soilLeafAlarm1': 0, 'soilLeafAlarm2': 0,
'soilLeafAlarm3': 0, 'soilLeafAlarm4': 0, 'txBatteryStatus': 0,
'consBatteryVoltage': 3.83, 'forecastIcon': 6, 'forecastRule': 63,
'sunrise': 1645282920, 'sunset': 1645321140, 'rain': 0.0}



On Thu, Feb 17, 2022 at 9:36 AM Saverio Guzzo  wrote:

> Hello community, this is my first post here! :)
>
> I am interested in running the vantage's driver program as standalone, in
> order to integrate it in my application. Could you please give me some
> suggestions on how to achieve that?
>
> I am struggling already at installing the requirements I tried to
> install them using both venv and conda env, but I get the error
> "distutils.errors.DistutilsOptionError: can't combine user with prefix,
> exec_prefix/home, or install_(plat)base".
>
> Should I also export the env variable PYTHONPATH=bin python -m
> weewx.drivers.vantage? When trying to do this, I get the errors "-bash:
> export: not valid in this context: -m" and "-bash: export:
> `weewx.drivers.vantage': not a valid identifier".
>
> Could you kindly give me some directions? I would really aprpeciate it :)
>
> Thanks,
> Saverio
>
> --
> 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/0bb1abeb-0ff2-4a65-b345-042e51d57482n%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/CAPq0zEDErJ6dOmPrTNrZysfEUaY97XKK5f9NCeNFtRkiM58x-A%40mail.gmail.com.

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

[Tom Keffer]

Rob, it occurs to me that the origins of the REC archive record wasn't
clear in the weewxd output that you posted. Could you run the instrumented
version of vantage.py again, but this time capture the output through the
generation of an archive record? I believe your archive interval is 60
seconds, so a couple minutes of output is more than enough.

On Thu, Feb 17, 2022 at 9:15 PM Rob Cranfill  wrote:

> Thanks, I thought I'd fixed that!
>
> On Thursday, February 17, 2022 at 8:34:24 PM UTC-8 gjr80 wrote:
>
>> Rob,
>>
>> Not that I think it has anything to do with the issue at hand but I
>> suspect you have the incorrect sign on your station longitude, unless of
>> course your station is actually in Zalantun, Mongolia. :)
>>
>> Gary
>>
>> On Friday, 18 February 2022 at 13:28:55 UTC+10 robcr...@gmail.com wrote:
>>
>>> No, thank *you*! :-)
>>>
>>>
>>> On Thursday, February 17, 2022 at 6:44:34 PM UTC-8 tke...@gmail.com
>>> wrote:
>>>
 Hmm, the RAW and LOOP packets are as to be expected, yet the archive
 records contain the unwanted data. Something is injecting the bogus data
 into the data stream. Another request: run

 *wee_debug --info --output=/var/tmp/sanitized.txt*


 Look through /var/tmp/sanitized.txt to make sure that it doesn't
 include any unwanted passwords (they should have been obfuscated), then
 post it.

 Thanks again.

 -tk


 On Thu, Feb 17, 2022 at 6:33 PM Rob Cranfill 
 wrote:

> Your wish is my command! :-)
>
> On Thursday, February 17, 2022 at 5:52:21 PM UTC-8 tke...@gmail.com
> wrote:
>
>> That's great, but now you have my curiosity piqued! All of the
>> channels have been shut off, yet the driver is still emitting values? How
>> can this possibly be?
>>
>> Would you mind running weewxd directly from the command line with the
>> attached instrumented version of vantage.py? It will print out exactly 
>> what
>> is in the raw LOOP packets.
>>
>> Oh, and if you could run
>>
>> *wee_device --info*
>>
>>
>> just one more time to make sure all the channels are truly off.
>>
>> Thanks, Rob!
>>
>> -tk
>>
>>
>> On Thu, Feb 17, 2022 at 11:39 AM Rob Cranfill 
>> wrote:
>>
>>> I do still see various "soil" and "leaf" values in the REC & LOOP
>>> data, but I'm happy now that I've simply removed the unwanted graphs 
>>> from
>>> the "plot_groups" entry in Seasons'  skin.conf file. (as seen at
>>> http://robcranfill.net/weather/ :-) )
>>>
>>> REC:2022-02-17 11:32:00 PST (1645126320) 'altimeter':
>>> '30.465171734312715', 'appTemp': '43.52206836601618', 'barometer':
>>> '30.467', 'cloudbase': '1476.5271458098498', 'consBatteryVoltage': 
>>> 'None',
>>> 'dateTime': '1645126320', 'dewpoint': '40.863280558436664', 'ET': '0.0',
>>> 'forecastRule': '9', 'heatindex': '44.835', 'highOutTemp':
>>> '46.7', 'humidex': '46.7', 'inDewpoint': '42.72068451224605', 
>>> 'inHumidity':
>>> '59.0', 'inTemp': '56.9', 'interval': '1', 'leafTemp1': '-89.0',
>>> 'leafTemp2': '-90.0', 'leafWet1': '1.0', 'leafWet2': '8.0', 
>>> 'lowOutTemp':
>>> '46.7', 'maxSolarRad': 'None', 'outHumidity': '80.0', 'outTemp': '46.7',
>>> 'pressure': '30.29821430422651', 'rain': '0.0', 'rainRate': '0.0',
>>> 'rxCheckPercent': '98.229167', 'soilMoist1': '4.0', 
>>> 'soilMoist2':
>>> '8.0', 'soilMoist3': '4.0', 'soilMoist4': '32.0', 'soilTemp1': '-89.0',
>>> 'soilTemp2': '-90.0', 'soilTemp3': '-89.0', 'soilTemp4': '-90.0',
>>> 'txBatteryStatus': 'None', 'usUnits': '1', 'wind_samples': '23.0',
>>> 'windchill': '46.7', 'windDir': '157.5', 'windGust': '4.0', 
>>> 'windGustDir':
>>> '135.0', 'windrun': '0.0', 'windSpeed': '2.0'
>>> LOOP:   2022-02-17 11:32:30 PST (1645126350) 'altimeter':
>>> '30.465171734312715', 'appTemp': '43.52206836601618', 'barometer':
>>> '30.467', 'cloudbase': '1476.5271458098498', 'consBatteryVoltage': 
>>> '0.8',
>>> 'dateTime': '1645126350', 'dayET': '0.0', 'dayRain': '0.0', 'dewpoint':
>>> '40.863280558436664', 'ET': 'None', 'extraAlarm1': '0', 'extraAlarm2': 
>>> '0',
>>> 'extraAlarm3': '0', 'extraAlarm4': '0', 'extraAlarm5': '0', 
>>> 'extraAlarm6':
>>> '0', 'extraAlarm7': '0', 'extraAlarm8': '0', 'forecastIcon': '6',
>>> 'forecastRule': '9', 'heatindex': '44.835', 'humidex': 
>>> '46.7',
>>> 'inDewpoint': '42.72068451224605', 'inHumidity': '59.0', 'insideAlarm':
>>> '0', 'inTemp': '56.9', 'leafWet4': '0.0', 'maxSolarRad': 'None', 
>>> 'monthET':
>>> '0.0', 'monthRain': '0.34', 'outHumidity': '80.0', 'outsideAlarm1': '0',
>>> 'outsideAlarm2': '0', 'outTemp': '46.7', 'pressure': 
>>> '30.29821430422651',
>>> 'rain': 'None', 'rainAlarm': '0', 'rainRate': '0.0', 'soilLeafAlarm1': 
>>> '0',
>>> 's

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

[Chuck Rhode]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

You mentioned Chill Hours.  This keeps coming up, and I've wondered
whether I ought to try to tackle it, but it's not a hot-button issue
for me.  I'm aware that most apple varieties require differing amounts
of "chill hours" to bloom.  However, the consideration of chill hours
available in any given location is usually moot once an orchard is
planted.  I suppose it's possible that chill hours must be calculated
annually for other kinds of crops.  Also, people are sensitive to
supposed climate shifts nowadays.  They want to verify government
figures for chill hours, so desire to do these calculations has some
currency.

There are other types of calculations similar to chill hours and
growing degree-days.  Have you looked into Pollen Tube Growth Models?

o http://weather.wsu.edu/PollenModel/PollenTubeModel.pdf

The *.pdf file has an internal date of 18 Mar 2014.  It's impossible to
tell from the presentation foils whether this remains an active locus
of research, but I thought it was an intriguing idea.  You count open
apple blossoms, and, when you have enough for a good crop, you wait
until the pollen tubes from the first blooms have had enough growing
degree-days to reach the ovules.  Then you repeatedly nuke all the
blooms chemically to be sure there isn't any excessive fruit set.

- -- 
.. Be Seeing You,
.. Chuck Rhode, Sheboygan, WI, USA
.. Weather:  http://LacusVeris.com/WX
.. 2° — Wind WNW 20 mph

-BEGIN PGP SIGNATURE-

iFwEARECAB0WIQT+MY/5I/LMPSswTbVg2/xipKOWUgUCYhD3aAAKCRBg2/xipKOW
UmX2AJiyfDT4F8fqfuqoG5NecImhwn7ZAJ9LyPZ1EOr3wBnXyaIr9UuJWr/3xw==
=e8a5
-END PGP SIGNATURE-

-- 
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/20220219075800.608dc1d1%40wealthy.

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

[GBJ]

Hi, guys. First, sorry about any mistakes. My english isn't the best...

I have 2 Raspberrys and I did a fresh 4.6.2 installation on both, via 
apt-get install weewx.

RPi #1 has a Vantage Pro 2. Everything worked well out of the box.
RPi #2 has a Vantage Vue. Evetything seems to work, except in this case I 
started to see Leaf and Soil graphs, but my Vantage doesn't have these 
sensors.

So I stopped weewx, did a database backup and: 

update archive set leafTemp1=NULL where leafTemp1 is not NULL;

update archive set leafTemp2=NULL where leafTemp2 is not NULL;

update archive set leafWet1=NULL where leafWet1 is not NULL;

update archive set leafWet2=NULL where leafWet2 is not NULL;

update archive set soilMoist1=NULL where soilMoist1 is not NULL;

update archive set soilMoist2=NULL where soilMoist2 is not NULL;

update archive set soilMoist3=NULL where soilMoist3 is not NULL;

update archive set soilMoist4=NULL where soilMoist4 is not NULL;

update archive set soilTemp1=NULL where soilTemp1 is not NULL;

update archive set soilTemp2=NULL where soilTemp2 is not NULL;

update archive set soilTemp3=NULL where soilTemp3 is not NULL;

update archive set soilTemp4=NULL where soilTemp4 is not NULL;
After that, I ran wee_database --rebuild-daily, and also disabled all other 
channels by running wee_device --set-transmitter-type=X,10 command.

Finally, just in case, I executed a wee_device --clear

Restarted weewx service and... the bogus data showed again in database.

Is the console generating the bad data? Or is it some kind of bug in the 
logger? 

I'll be happy to help.
On Saturday, February 19, 2022 at 10:16:14 AM UTC-3 tke...@gmail.com wrote:

> Rob, it occurs to me that the origins of the REC archive record wasn't 
> clear in the weewxd output that you posted. Could you run the instrumented 
> version of vantage.py again, but this time capture the output through the 
> generation of an archive record? I believe your archive interval is 60 
> seconds, so a couple minutes of output is more than enough.
>
> On Thu, Feb 17, 2022 at 9:15 PM Rob Cranfill  wrote:
>
>> Thanks, I thought I'd fixed that!
>>
>> On Thursday, February 17, 2022 at 8:34:24 PM UTC-8 gjr80 wrote:
>>
>>> Rob,
>>>
>>> Not that I think it has anything to do with the issue at hand but I 
>>> suspect you have the incorrect sign on your station longitude, unless of 
>>> course your station is actually in Zalantun, Mongolia. :)
>>>
>>> Gary
>>>
>>> On Friday, 18 February 2022 at 13:28:55 UTC+10 robcr...@gmail.com wrote:
>>>
 No, thank *you*! :-)


 On Thursday, February 17, 2022 at 6:44:34 PM UTC-8 tke...@gmail.com 
 wrote:

> Hmm, the RAW and LOOP packets are as to be expected, yet the archive 
> records contain the unwanted data. Something is injecting the bogus data 
> into the data stream. Another request: run 
>
> *wee_debug --info --output=/var/tmp/sanitized.txt*
>
>
> Look through /var/tmp/sanitized.txt to make sure that it doesn't 
> include any unwanted passwords (they should have been obfuscated), then 
> post it. 
>
> Thanks again.
>
> -tk
>
>
> On Thu, Feb 17, 2022 at 6:33 PM Rob Cranfill  
> wrote:
>
>> Your wish is my command! :-) 
>>
>> On Thursday, February 17, 2022 at 5:52:21 PM UTC-8 tke...@gmail.com 
>> wrote:
>>
>>> That's great, but now you have my curiosity piqued! All of the 
>>> channels have been shut off, yet the driver is still emitting values? 
>>> How 
>>> can this possibly be?
>>>
>>> Would you mind running weewxd directly from the command line with 
>>> the attached instrumented version of vantage.py? It will print out 
>>> exactly 
>>> what is in the raw LOOP packets. 
>>>
>>> Oh, and if you could run
>>>
>>> *wee_device --info*
>>>
>>>
>>> just one more time to make sure all the channels are truly off.
>>>
>>> Thanks, Rob!
>>>
>>> -tk
>>>
>>>
>>> On Thu, Feb 17, 2022 at 11:39 AM Rob Cranfill  
>>> wrote:
>>>
 I do still see various "soil" and "leaf" values in the REC & LOOP 
 data, but I'm happy now that I've simply removed the unwanted graphs 
 from 
 the "plot_groups" entry in Seasons'  skin.conf file. (as seen at 
 http://robcranfill.net/weather/ :-) )

 REC:2022-02-17 11:32:00 PST (1645126320) 'altimeter': 
 '30.465171734312715', 'appTemp': '43.52206836601618', 'barometer': 
 '30.467', 'cloudbase': '1476.5271458098498', 'consBatteryVoltage': 
 'None', 
 'dateTime': '1645126320', 'dewpoint': '40.863280558436664', 'ET': 
 '0.0', 
 'forecastRule': '9', 'heatindex': '44.835', 'highOutTemp': 
 '46.7', 'humidex': '46.7', 'inDewpoint': '42.72068451224605', 
 'inHumidity': 
 '59.0', 'inTemp': '56.9', 'interval': '1', 'leafTemp1': '-89.0', 
 'leafTemp2':

[weewx-user] Sudden error running reports? Any help appreciated

['andyhud...@googlemail.com' via weewx-user]

 

Afternoon - weewx has been happily running, i noticed when i run reports i 
get an error (yet the website seems to be working ok? -  
http://www.finchamweather.co.uk/) 

Any help would be really appreciated:

Using configuration file /etc/weewx/weewx.conf

Generating for all time

Traceback (most recent call last):

  File "/usr/share/weewx/weewx/reportengine.py", line 196, in run

obj.start()

  File "/usr/share/weewx/weewx/reportengine.py", line 281, in start

self.run()

  File "/usr/share/weewx/user/belchertown.py", line 2520, in run

time_length = int(time_length)

ValueError: invalid literal for int() with base 10: 'yesterday'


Andy

-- 
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/97369c08-c4af-4812-94be-9790c27c0a0an%40googlegroups.com.

[weewx-user] Re: Sudden error running reports? Any help appreciated

['andyhud...@googlemail.com' via weewx-user]

Edit - noting it's not a sudden error, my Yesterday Graph has not updated 
for 10 days, so i must be something in my graphs.conf ... :)

Andy

On Saturday, 19 February 2022 at 15:35:10 UTC andyhud...@googlemail.com 
wrote:

> Afternoon - weewx has been happily running, i noticed when i run reports i 
> get an error (yet the website seems to be working ok? -  
> http://www.finchamweather.co.uk/) 
>
> Any help would be really appreciated:
>
> Using configuration file /etc/weewx/weewx.conf
>
> Generating for all time
>
> Traceback (most recent call last):
>
>   File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
>
> obj.start()
>
>   File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
>
> self.run()
>
>   File "/usr/share/weewx/user/belchertown.py", line 2520, in run
>
> time_length = int(time_length)
>
> ValueError: invalid literal for int() with base 10: 'yesterday'
>
>
> Andy
>

-- 
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/fb81a4c6-39b6-4542-9d23-aff2ec4cefd5n%40googlegroups.com.

Re: [weewx-user] Re: Sudden error running reports? Any help appreciated

[Tom Keffer]

Option "time_length
" is set to
the string 'yesterday', instead of a number.

On Sat, Feb 19, 2022 at 8:04 AM 'andyhud...@googlemail.com' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Edit - noting it's not a sudden error, my Yesterday Graph has not updated
> for 10 days, so i must be something in my graphs.conf ... :)
>
> Andy
>
> On Saturday, 19 February 2022 at 15:35:10 UTC andyhud...@googlemail.com
> wrote:
>
>> Afternoon - weewx has been happily running, i noticed when i run reports
>> i get an error (yet the website seems to be working ok? -
>> http://www.finchamweather.co.uk/)
>>
>> Any help would be really appreciated:
>>
>> Using configuration file /etc/weewx/weewx.conf
>>
>> Generating for all time
>>
>> Traceback (most recent call last):
>>
>>   File "/usr/share/weewx/weewx/reportengine.py", line 196, in run
>>
>> obj.start()
>>
>>   File "/usr/share/weewx/weewx/reportengine.py", line 281, in start
>>
>> self.run()
>>
>>   File "/usr/share/weewx/user/belchertown.py", line 2520, in run
>>
>> time_length = int(time_length)
>>
>> ValueError: invalid literal for int() with base 10: 'yesterday'
>>
>>
>> Andy
>>
> --
> 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/fb81a4c6-39b6-4542-9d23-aff2ec4cefd5n%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/CAPq0zEBNL0w85E_wUUbjCVLS%3D5Osme-S_buRw2v1VL1vDoOPhw%40mail.gmail.com.

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

[Rob Cranfill]

Tom, thanks for your continuing investigations! I’m afraid I am out of town
for the next few days so I won’t be able to get back to you till early/mid
next week with any new info.--


-- 
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/CAOVFAvqC6FgmZ1wztE83GLpPM%2BjRz8_sjdRFPHvDEznurtNrpQ%40mail.gmail.com.

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

[Gentil de Bortoli Jr]

Thanks, Tom!

Here is the output using your vantage.py. This first is from my Vantage Vue.

Keep scrolling because at the and there is the output from the Vantage Pro,
from the other Raspberry, using the same modified vantage.py.

Also, looking at Vantage Pro weewx's database, as expected, there is no
information registered for these sensors (Leaf and Soil).

RAW PACKET:2022-02-19 15:30:14 -03 (1645295414) 'barometer': '29744',
'bucket_type': '1', 'consBatteryVoltage': '801', 'dayET': '0', 'dayRain':
'1', 'extraAlarm1': '0', 'extraAlarm2': '0', 'extraAlarm3': '0',
'extraAlarm4': '0', 'extraAlarm5': '0', 'extraAlarm6': '0', 'extraAlarm7':
'0', 'extraAlarm8': '0', 'extraHumid1': '255', 'extraHumid2': '255',
'extraHumid3': '255', 'extraHumid4': '255', 'extraHumid5': '255',
'extraHumid6': '255', 'extraHumid7': '255', 'extraTemp1': '255',
'extraTemp2': '255', 'extraTemp3': '255', 'extraTemp4': '255',
'extraTemp5': '255', 'extraTemp6': '255', 'extraTemp7': '255',
'forecastIcon': '7', 'forecastRule': '173', 'inHumidity': '59',
'insideAlarm': '0', 'inTemp': '747', 'leafTemp1': '255', 'leafTemp2':
'255', 'leafTemp3': '255', 'leafTemp4': '255', 'leafWet1': '255',
'leafWet2': '255', 'leafWet3': '255', 'leafWet4': '0', 'loop': 'LOO',
'monthET': '0', 'monthRain': '920', 'next_record': '51', 'outHumidity':
'55', 'outsideAlarm1': '0', 'outsideAlarm2': '0', 'outTemp': '834',
'packet_type': '0', 'radiation': '32767', 'rainAlarm': '0', 'rainRate':
'0', 'rev_type': '-60', 'soilLeafAlarm1': '0', 'soilLeafAlarm2': '0',
'soilLeafAlarm3': '0', 'soilLeafAlarm4': '0', 'soilMoist1': '255',
'soilMoist2': '255', 'soilMoist3': '255', 'soilMoist4': '255', 'soilTemp1':
'255', 'soilTemp2': '255', 'soilTemp3': '255', 'soilTemp4': '255',
'stormRain': '24', 'stormStart': '10390', 'sunrise': '609', 'sunset':
'1857', 'txBatteryStatus': '0', 'UV': '255', 'windDir': '94', 'windSpeed':
'0', 'windSpeed10': '2', 'yearET': '0', 'yearRain': '1983'

LOOP:   2022-02-19 15:30:14 -03 (1645295414) 'altimeter': '29.8903338519',
'appTemp': '88.9124237731', 'barometer': '29.744', 'cloudbase':
'6788.899723', 'consBatteryVoltage': '4.69', 'dateTime': '1645295414',
'dayET': '0.0', 'dayRain': '0.0078740157', 'dewpoint': '65.5100412188',
'ET': 'None', 'extraAlarm1': '0', 'extraAlarm2': '0', 'extraAlarm3': '0',
'extraAlarm4': '0', 'extraAlarm5': '0', 'extraAlarm6': '0', 'extraAlarm7':
'0', 'extraAlarm8': '0', 'forecastIcon': '7', 'forecastRule': '173',
'heatindex': '85.4007233592', 'humidex': '95.0436629998', 'inDewpoint':
'59.4026997841', 'inHumidity': '59.0', 'insideAlarm': '0', 'inTemp':
'74.7', 'leafWet4': '0.0', 'maxSolarRad': '758.79256832', 'monthET': '0.0',
'monthRain': '7.24409', 'outHumidity': '55.0', 'outsideAlarm1': '0',
'outsideAlarm2': '0', 'outTemp': '83.4', 'pressure': '27.0609251606',
'rain': '0.0', 'rainAlarm': '0', 'rainRate': '0.0', 'soilLeafAlarm1': '0',
'soilLeafAlarm2': '0', 'soilLeafAlarm3': '0', 'soilLeafAlarm4': '0',
'stormRain': '0.1889763768', 'stormStart': '1645066800', 'sunrise':
'1645261740', 'sunset': '1645307820', 'txBatteryStatus': '0', 'usUnits':
'1', 'windchill': '83.4', 'windDir': 'None', 'windGust': '0.0',
'windGustDir': 'None', 'windrun': 'None', 'windSpeed': '0.0',
'windSpeed10': '2.0', 'yearET': '0.0', 'yearRain': '15.6141731331'

RAW PACKET:2022-02-19 15:30:16 -03 (1645295416) 'barometer': '29744',
'bucket_type': '1', 'consBatteryVoltage': '801', 'dayET': '0', 'dayRain':
'1', 'extraAlarm1': '0', 'extraAlarm2': '0', 'extraAlarm3': '0',
'extraAlarm4': '0', 'extraAlarm5': '0', 'extraAlarm6': '0', 'extraAlarm7':
'0', 'extraAlarm8': '0', 'extraHumid1': '255', 'extraHumid2': '255',
'extraHumid3': '255', 'extraHumid4': '255', 'extraHumid5': '255',
'extraHumid6': '255', 'extraHumid7': '255', 'extraTemp1': '255',
'extraTemp2': '255', 'extraTemp3': '255', 'extraTemp4': '255',
'extraTemp5': '255', 'extraTemp6': '255', 'extraTemp7': '255',
'forecastIcon': '7', 'forecastRule': '173', 'inHumidity': '59',
'insideAlarm': '0', 'inTemp': '747', 'leafTemp1': '255', 'leafTemp2':
'255', 'leafTemp3': '255', 'leafTemp4': '255', 'leafWet1': '255',
'leafWet2': '255', 'leafWet3': '255', 'leafWet4': '0', 'loop': 'LOO',
'monthET': '0', 'monthRain': '920', 'next_record': '51', 'outHumidity':
'55', 'outsideAlarm1': '0', 'outsideAlarm2': '0', 'outTemp': '834',
'packet_type': '0', 'radiation': '32767', 'rainAlarm': '0', 'rainRate':
'0', 'rev_type': '-60', 'soilLeafAlarm1': '0', 'soilLeafAlarm2': '0',
'soilLeafAlarm3': '0', 'soilLeafAlarm4': '0', 'soilMoist1': '255',
'soilMoist2': '255', 'soilMoist3': '255', 'soilMoist4': '255', 'soilTemp1':
'255', 'soilTemp2': '255', 'soilTemp3': '255', 'soilTemp4': '255',
'stormRain': '24', 'stormStart': '10390', 'sunrise': '609', 'sunset':
'1857', 'txBatteryStatus': '0', 'UV': '255', 'windDir': '94', 'windSpeed':
'0', 'windSpeed10': '2', 'yearET': '0', 'yearRain': '1983'

LOOP:   2022-02-19 15:30:16 -03 (1645295416) 'altimeter': '29.8903338519',
'appTemp': '88.9124237731', 'barometer': '29.744', 'cloudbase

[weewx-user] visualize past and zoomed weather data out of db

[kede...@gmail.com]

Hello,

perhaps there is already a solution here for my problem but searching with 
keywords doesn't give me any results.

Using WeeWX since several years I am able to have diagrams of the last 
day(s), last week, last month and the last year. 

But if I want to look at a special date in past for specified period of 
time I have no tool to zooming those data out of my local database and 
visualize them.

For example in January the vulcano Hunga-Tonga-Hunga-Ha'apai had an 
eruption that sends a pressure wave around the world witch was detected by 
all weatherstations. But I have no chance to focuse on that event.

Storing weatherdata for several years in a database on a SD-Card may not be 
necessary if I am not flexibel in data requests.

Any idea?

Kind regards
Klaus

-- 
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/916fb4ea-c001-4e5b-9b5e-2d6bab352b05n%40googlegroups.com.

Re: [weewx-user] visualize past and zoomed weather data out of db

[Tom Keffer]

The only thing WeeWX offers is the ability to generate a report for any
timestamp. So, for example,

*wee_reports /etc/weewx/weewx.conf 1642327200*


gives a pretty good rendition for my location. You may have to experiment
with different timestamps.

[image: image.png]

On Sat, Feb 19, 2022 at 2:03 PM kede...@gmail.com 
wrote:

> Hello,
>
> perhaps there is already a solution here for my problem but searching with
> keywords doesn't give me any results.
>
> Using WeeWX since several years I am able to have diagrams of the last
> day(s), last week, last month and the last year.
>
> But if I want to look at a special date in past for specified period of
> time I have no tool to zooming those data out of my local database and
> visualize them.
>
> For example in January the vulcano Hunga-Tonga-Hunga-Ha'apai had an
> eruption that sends a pressure wave around the world witch was detected by
> all weatherstations. But I have no chance to focuse on that event.
>
> Storing weatherdata for several years in a database on a SD-Card may not
> be necessary if I am not flexibel in data requests.
>
> Any idea?
>
> Kind regards
> Klaus
>
> --
> 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/916fb4ea-c001-4e5b-9b5e-2d6bab352b05n%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/CAPq0zEBB%3D9AoONq%3D1TqAHptSBTHobaHsCeC9W%2B%2BUGGcmzd6poA%40mail.gmail.com.

[weewx-user] A howto for rsync in weewx.

[Liz Dodd]

I recently setup rsync with weewx. This took a couple of hours, and help 
from my friends, so I wrote out all the steps I used to make it work.
This is not the only way to make rsync work, but a single set of 
instructions.
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/f110b3eb-56e2-4909-8d11-3940a4d3f7ben%40googlegroups.com.
1. Work out
which computer is the source (the one collecting the weather data)
which computer is the destination (the one where the public to check 
your weather site)
on the destination computer, what is the user name for the webserver
the IP address of the destination computer eg 192.168.1.1 OR its domain 
name eg myweather.com
the correct paths for the data on each computer
and, on your source computer which is your weewx.conf file 
2. Install any packages required - ssh, rsync 
Check that ssh on the destination will accept key pair login
Make sure you have ssh access to both computers
3. On the source computer make a new private / public key pair.
Don't overwrite an existing pair.
From your user directory check for previous existing pairs
$ ls -al ~/.ssh/id_*.pub
If you get "No such file or directory" you are set to go. If you have 
existing key pairs you need
to either move them out of the way temporarily or risk reusing them.
To make the new key pair 
$ ssh-keygen -t rsa -b 4096 -C "your_em...@domain.com"
The email address is not critical, but it helps you identify the key. 
You might have
'weewx_rs...@myweather.com'
Accept the default file location for your key pair, and just press 
enter for the passphrase, twice.
Check that you now have two files 
$ ls ~/.ssh/id_* 
output /home/yourusername/.ssh/id_rsa /home/yourusername/.ssh/id_rsa.pub
id_rsa is your private key, to stay on your source computer
id_rsa.pub is your public key to put on the destination computer.
4. Copy the Public key to its new home
Firstly copy the public key to your directory on the destination.
$ ssh-copy-id your_destination_username@destination_server_ip_address 
(eg fr...@myweather.com)
You should find in /home/user/.ssh/authorized_keys the identical file 
to id_rsa.pub
Before you move it again, check you can do a passwordless login via ssh 
from your source computer
$ ssh u...@myweather.com or ssh user@192.168.1.1 (use the correct 
address)
If this doesn't work you need to check your ssh configurations
Once you can do the passwordless login, move the file.
Here you need the user name for the webserver. On Debian its www-data. 
Move with sudo, then change the ownership of the file to www-data
$ sudo mv .ssh/authorized_keys ~www-data/.ssh/authorized keys
$ sudo chown www-data:www-data ~www-data/.ssh/authorized_keys
British English users need to resist the temptation to change the 
spelling.
Test again from your source computer 
$ ssh www-d...@myweather.com or ssh www-data@192.168.1.1 (use the 
correct address)
As www-data hasn't got a shell (like bash) you won't be able to do much 
without providing one
On the destination computer 
$ sudo chsh www-data will allow you to provide a shell eg '/bin/bash' 
for www-data
I don't know if this is required.
5. Copy the private key to its new home
Weewx runs as root, so root has to be able to find the private key. 
On source computer 
$ sudo mv /home/user/.ssh/id_rsa /root/.ssh/id_rsa
6. Test rsync on the command line
$ sudo rsync -arP /var/www/html/weewx/ 
www-data@192.168.1.1:/var/www/html/weewx/ (use the correct address and paths)
If you get errors check that your webserver user does own the files and 
directories on the destination
$ sudo chown -R www-data: /var/www/html/weewx
7. Rsync from weewx every reporting cycle
Edit /etc/weewx/weewx.conf (it may have another path)
Under [[RSYNC]]
remove the hash from the server, path and user lines and put in your 
destination server, the path on 
the destination server and the username, as in the example here
server = 192.168.1.1
path = /var/www/html/weewx/
user = www-data
Check your work, save the file and restart weewx
8. If its all working, tidy up. Remove the copy of the public key from our home 
directory.
$ rm .ssh/id_rsa* 
If you moved a key pair from your own user space you need to be put it 
back.
 

Re: [weewx-user] wind run always zero after update to 4.6.0

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

updating.

after 2 days suddenly windmeter again always zero on steelseries page.
i suspicius that happens only on steelseries ,because in test page with 
$windrun.day.sum  , windrun updating well every 5 minutes , and the  
steelseries odometer remains steel in zero. 
with windrun = software and   record[obs_type] = self[obs_type].sum if self[
obs_type].count else None , in accum.py

Στις Παρασκευή 11 Φεβρουαρίου 2022 στις 3:06:35 μ.μ. UTC+2, ο χρήστης 
Δημήτρης Βήχος έγραψε:

> widmeter works well now  with windrun = prefer_hardware and , record[
> obs_type] = self[obs_type].sum if self[obs_type].count else None , in 
> accum.py.  thank you!
>
> Στις Πέμπτη 10 Φεβρουαρίου 2022 στις 11:19:12 μ.μ. UTC+2, ο χρήστης 
> tke...@gmail.com έγραψε:
>
>> See issue #737 .
>>
>> Solution is to change 'prefer_hardware' to 'software' for windrun. While 
>> you're in there, you might as well change ET too. When you're done, it will 
>> look something like:
>>
>> [StdWXCalculate]
>> 
>> [[Calculations]]
>> # How to calculate derived quantities.  Possible values are:
>> #  hardware- use the value provided by hardware
>> #  software- use the value calculated by weewx
>> #  prefer_hardware - use value provide by hardware if available,
>> #  otherwise use value calculated by weewx
>> 
>> pressure = prefer_hardware
>> altimeter = prefer_hardware
>> appTemp = prefer_hardware
>> barometer = prefer_hardware
>> cloudbase = prefer_hardware
>> dewpoint = prefer_hardware
>> ET = software
>> heatindex = prefer_hardware
>> humidex = prefer_hardware
>> inDewpoint = prefer_hardware
>> maxSolarRad = prefer_hardware
>> rainRate = prefer_hardware
>> windchill = prefer_hardware
>> windrun = software
>>
>>
>>
>>
>> On Thu, Feb 10, 2022 at 1:07 PM Δημήτρης Βήχος  
>> wrote:
>>
>>> 2 days before i was update weewx from 4.5.1 to 4.6.0
>>> after update to new version and restarting in steelseries wind run is 
>>> always zero. wind speed and gust calculating as before.
>>> [image: Στιγμιότυπο οθόνης_2022-02-10_23-03-55.png] 
>>>
>>> -- 
>>> 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/bf41204e-5675-42ff-aa4a-8647697e7c6bn%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/8992658c-1df5-4f17-8380-d0ac256e42e5n%40googlegroups.com.

[weewx-user] Changing Vantage Pro2 Archive Interval

[Bruce Rees]

Hi there,

Total noob here, I want to change the archive interval for my Vantage Pro2 
to 5 minutes, I see the warning "Proceeding will erase all archive 
records."  what does this actually mean?  Will I lose any history for the 
station?  This is new install on an RPI4 so I'm not concerned about losing 
weewx data but wondering if it clears the console history?

Thanks!
Bruce

-- 
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/13d91d0a-754f-482d-9e00-e91b1e277ef1n%40googlegroups.com.

Re: [weewx-user] Changing Vantage Pro2 Archive Interval

[Tom Keffer]

Yes, it does clear the console history. If you care about the values in
there, you can use the wee_device utility with the --dump option
 to
put them into the database.

First stop weewxd, then run the command

*wee_device --dump*


You may get multiple "primary key errors" if archive records are already in
your database. You can ignore these.

On Sat, Feb 19, 2022 at 3:14 PM Bruce Rees  wrote:

> Hi there,
>
> Total noob here, I want to change the archive interval for my Vantage Pro2
> to 5 minutes, I see the warning "Proceeding will erase all archive
> records."  what does this actually mean?  Will I lose any history for the
> station?  This is new install on an RPI4 so I'm not concerned about losing
> weewx data but wondering if it clears the console history?
>
> Thanks!
> Bruce
>
> --
> 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/13d91d0a-754f-482d-9e00-e91b1e277ef1n%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/CAPq0zEBbzTXRqzozDb%2Bh5ji%3DiRfYBY8M5OUJk9G1gHThXg4Mpg%40mail.gmail.com.