Re: [weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-17 Thread S R
i figured out the utf-8 issue. weewx.conf has to be in utf, but i made the 
mistake of editing in the shell with edit. once i used geany and change the 
encoding back to utf-8 it came good. 

current status is; 
- console updates both ecowitt and wunderground online every minute. 
- config using ecowitt protocol with custom config pointing to local 
freenas jail / weewx server - path = index.php?
- using seasons default report 
- weewx is not upating and pfsense is showing me below with a packet 
capture, but no rules are blocking.
- i have tcp options enabled on both rules (WEEWX and WH2900C are on 
different VLANs)

222.968670WH2900CWEEWXTCP5820150 → 8080 [SYN] Seq=0 
Win=5840 Len=0 MSS=1460
232.969709WEEWXWH2900CTCP548080 → 20150 [RST, ACK] 
Seq=1 Ack=1 Win=0 Len=0


On Sunday, January 17, 2021 at 8:54:36 PM UTC+1 lang@googlemail.com 
wrote:

> As a workaround I would remove / replace your suspects - change "Umlaute", 
> if any, from Ä -> AE, Ö -->OE, Ü --> UE, accents just omit them and leave 
> the vowels without them.
> They will anyway only appear in temporary graphs. Then figure out your 
> UTF-8 issue and fix it, while your weewx could already run and archive data.
> On 17.01.2021 19:59, S R wrote:
>
> thanks for the clarification. i will switch the protocol to ecowitt, but 
> the more immediate problem is the UTF-8 error which is now preventing weewx 
> from starting.
>
> On Sunday, January 17, 2021 at 4:30:38 PM UTC+1 galfert wrote:
>
>> This thread started with the discussion being around the Ambient WS-2902 
>> and that is totally different despite looking like the same unit. This is 
>> because Ambient is the only Fine Offset clone reseller that changes the 
>> firmware and they limit options. The Ambient version does not let you 
>> upload to custom server address. The confusion here is that my response was 
>> because I thought you had and Ambient branded unit. Since you don't have an 
>> Ambient branded unit you do have the option to send to a custom server 
>> using both WU and Ecowitt protocols. The WU protocol is limited and only 
>> sends the basic set of sensors. The Ecowitt protocol allows you to send a 
>> lot more optional sensors like PM2.5, soil moisture, extra temp/hum 
>> sensorsetc. But still you'll have to configure the Interceptor driver 
>> to match the protocol type that you set in you WH2900C for uploading to 
>> your custom server.  
>>
>> The GW1000 though is still a more elegant and newer solution. 
>>
>> * The newest Ambient WS-2902 firmware finally after many years does gain 
>> the ability to send to a custom serverBUT it is not WU protocol and it 
>> is not Ecowitt protocolit is Ambientweather.net protocol and enough 
>> significant differences that the Interceptor driver will not work. This 
>> newest firmware is not yet officially supported by Ambient. They haven't 
>> yet release the updated awnet mobile app to enable turning and configuring 
>> this option. All of these complexities and changing nature of the situation 
>> makes it difficult to explain the situation to cover all possible 
>> scenarios...what model you have and whom it is from and what firmware 
>> version you are running and all the different supporting protocols that are 
>> possible. 
>>
>> Using pfsense to capture and forward packets is really unnecessary for 
>> anyone with a non-Ambient WH2900Cas it has a built in simple to 
>> configure "Customized" server upload feature.
>>
>>
>>
>> On Sunday, January 17, 2021 at 7:32:03 AM UTC-5 sjr4...@gmail.com wrote:
>>
>>> For the record, mine is a Chinese Mi-Sol WH2900C. It is a copy of the 
>>> Fine Offset WH2900 or the Ecowitt WS2950. Indeed, the unit requires a 
>>> connection to Ecowitt to set the Time/Date and automatically downloaded the 
>>> EasyWeather 1.56 firmware update from Ecowitt. 
>>>
>>> I haven't got the outdoor setup done yet, while i play with getting the 
>>> unit up and running. but Ecowitt, shows my indoor temperature and pressure 
>>> on the home page. I use pfsense so can run a packet capture if it helps. 
>>> Since editing the weewx.conf file, i am getting the utf-8 problem. I guess 
>>> this is related to me using European accented characters in my editors 
>>> which are UTF-8. So that leaves me with two questions;
>>> 1) how to have it accept the UTF-8 characters
>>> 2) you mentioned not getting all the sensor data, unless using Ecowitt. 
>>> In view, that i am. Can you tell me what additional parameters i need in 
>>> the config file please.
>>>
>>>
>>>
>>> On Sunday, January 17, 2021 at 9:21:33 AM UTC+1 S R wrote:
>>>
 almost there, but now 

 /usr/local/share/weewx # ./bin/wee_reports

 Traceback (most recent call last):
   File "./bin/wee_reports", line 103, in 
 main()
   File "./bin/wee_reports", line 51, in main
 config_path, config_dict = weecfg.read_config(options.config_path, 
 args)
   File 

Re: [weewx-user] Re: Weewx 4.3.0 and weewx multi on a fresh install

2021-01-17 Thread Stéphane et Corinne LE PROVOST
Hello
the file weewx.txt :is the file in /etc/init.d/
the file etc-default-weewx.txt  is the file in /etc/default/weewx

I ve used it on a old install well but since I install on a fresh install
, I ve problem with the path   (weewx-multi doesnt find the "good path" of
weewxd
Thanks a lot
Stéphane


Le dim. 17 janv. 2021 à 23:31, gjr80  a écrit :

> Hi,
>
> It would be helpful to see the WeeWX service file you are using and the
> corresponding defaults. Assuming you followed the weewx-multi
>  instructions in the
> wiki the service file should be /etc/init.d/weewx and the defaults
> /etc/default/weewx-multi. Please post the contents of both here.
>
>>
>> FYI : ( I ve posted the same post in weewx developpement group)
>>
>
> Also, perhaps you did not read the weewx-user banner:
>
> There is a separate group, weewx-development, for developers who are
> actively working on extensions and the weewx codebase.
>
> *Please do not cross-post to both weewx-user and weewx-development!*
>
> Cross posting doesn't get you any more help any faster, in fact it just
> slows things down as we have twice as much to read.
>
> Gary
>
> --
> 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/nlg3qFnlWB8/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/f06ec671-467f-48ad-9ee8-f945d23a07acn%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/CAFkzkfV5oH-CkrB3jQAh-CiJ4rJ1jijN9o-pG%2Bg0C6Qxd%2BS9Ng%40mail.gmail.com.
WEEWX_INSTANCES="WMR200"
WEEWX_PYTHON=python2
WEEWX_BINDIR=/usr/share/weewx
WEEWX_BIN=/usr/bin/weewxd
WEEWX_CFG=/etc/weewx/weewx.conf
#! /bin/sh
# Copyright 2016 Matthew Wall, all rights reserved
# init script to run multiple instances of weewx
#
# each weewx instance is identified by name.  that name is used to identify the
# configuration and pid files.
#
# this init script expects the following configuration:
#   /etc/weewx/a.conf
#   /etc/weewx/b.conf
#   /var/run/weewx-a.pid
#   /var/run/weewx-b.pid
#
# with the appropriate rsyslog and logrotate configurations:
#   /var/log/weewx/a.log
#   /var/log/weewx/b.log
#
# to configure the script, override variables in /etc/default/weewx-multi
# for example:
#
#   WEEWX_INSTANCES="vantage acurite"
#   WEEWX_BINDIR=/opt/weewx/bin
#   WEEWX_CFGDIR=/etc/weewx

### BEGIN INIT INFO
# Provides:  weewx-multi
# Required-Start:$local_fs $remote_fs $syslog $time
# Required-Stop: $local_fs $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop:  0 1 6
# Short-Description: weewx-multi
# Description:   Manages multiple instances of weewx
### END INIT INFO

PATH=/sbin:/usr/sbin:/bin:/usr/bin

WEEWX_INSTANCES="no_instances_specified"
WEEWX_USER=root:root
WEEWX_BINDIR=/usr/bin/
WEEWX_CFGDIR=/etc/weewx

# Try to keep systemd from screwing everything up
export SYSTEMCTL_SKIP_REDIRECT=1

# Read configuration variable file if it is present
[ -r /etc/default/weewx-multi ] && . /etc/default/weewx-multi

DESC=weewx
DAEMON=$WEEWX_BINDIR/weewxd

# Exit if the package is not installed
if [ ! -x "$DAEMON" ]; then
echo "The $DESC daemon is not installed at $DAEMON"
exit 0
fi

# Load the VERBOSE setting and other rcS variables
. /lib/init/vars.sh

# Define LSB log_* functions.
# Depend on lsb-base (>= 3.0-6) to ensure that this file is present.
. /lib/lsb/init-functions

# start the daemon
#   0 if daemon has been started
#   1 if daemon was already running
#   2 if daemon could not be started
do_start() {
INSTANCE=$1
NAME=weewx-$INSTANCE
PIDFILE=/var/run/$NAME.pid
CFGFILE=$WEEWX_CFGDIR/$INSTANCE.conf
DAEMON_ARGS="--daemon --log-label $NAME --pidfile=$PIDFILE $CFGFILE"

if [ ! -f "$CFGFILE" ]; then
echo "The instance $INSTANCE does not have a config at $CFGFILE"
return 2
fi

NPROC=$(count_procs $INSTANCE)
if [ $NPROC != 0 ]; then
return 1
fi
start-stop-daemon --start --chuid $WEEWX_USER --pidfile $PIDFILE --exec 
$DAEMON -- $DAEMON_ARGS || return 2
return 0
}

# stop the daemon
#   0 if daemon has been stopped
#   1 if daemon was already stopped
#   2 if daemon could not be stopped
#   other if a failure occurred
do_stop() {
INSTANCE=$1
NAME=weewx-$INSTANCE
PIDFILE=/var/run/$NAME.pid

# bail out if the app is 

[weewx-user] Re: 4.1.1 - No module named 'Image'

2021-01-17 Thread gjr80
Appreciate you have installed PIL under python3 but are you sure that WeeWX 
is being run under python3 and not python2? I see nothing in what you have 
posted that confirms this one way or another. The python version is logged 
when starting WeeWX. What does the log say when you start WeeWX?

Gary

On Monday, 18 January 2021 at 14:14:24 UTC+10 cql...@gmail.com wrote:

> Hey all,
> I've recently begun the process of migrating my existing weewx install to 
> my
> kubernetes cluster, using this base docker image 
> 
> I'm still getting used to the setup, but it seems to be pulling data from 
> my
> weather station and populating my sqlite db. However, I'm running into 
> problems
> generating images due to a ModuleNotFoundError. Below, take a look at some 
> of
> the results of my troubleshooting.
>
>
>- Here's my setup:
>
> root@weewx-84bfc8b796-gwrr7:/home/weewx# python --version
> Python 3.9.0
> root@weewx-84bfc8b796-gwrr7:/home/weewx# pip --version
> pip 20.2.3 from /opt/venv/lib/python3.9/site-packages/pip (python 3.9)
> root@weewx-84bfc8b796-gwrr7:/home/weewx# cat version.txt
> __version__ = "4.1.1"
>
>- Here's my weewx logs showing the ModuleNotFoundError 
>
>- I found a previous thread 
>discussing this 
>issue, but it didn't seem to describe successful workarounds. 
>- Here's the output from working through that thread 
>   
>- Looking at this issue outside the context of weewx, it seemed 
>reasonable to try to install pillow via pip, but doing so resulted in this 
>long, ugly error 
>
> Wondering if anybody has navigated this issue before. Thanks!
>
>
>

-- 
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/27dd6ff7-5ce9-4a72-a692-07199377b1a6n%40googlegroups.com.


[weewx-user] 4.1.1 - No module named 'Image'

2021-01-17 Thread cql...@gmail.com
Hey all,
I've recently begun the process of migrating my existing weewx install to my
kubernetes cluster, using this base docker image 

I'm still getting used to the setup, but it seems to be pulling data from my
weather station and populating my sqlite db. However, I'm running into 
problems
generating images due to a ModuleNotFoundError. Below, take a look at some 
of
the results of my troubleshooting.


   - Here's my setup:

root@weewx-84bfc8b796-gwrr7:/home/weewx# python --version
Python 3.9.0
root@weewx-84bfc8b796-gwrr7:/home/weewx# pip --version
pip 20.2.3 from /opt/venv/lib/python3.9/site-packages/pip (python 3.9)
root@weewx-84bfc8b796-gwrr7:/home/weewx# cat version.txt
__version__ = "4.1.1"

   - Here's my weewx logs showing the ModuleNotFoundError 
   
   - I found a previous thread 
   discussing this 
   issue, but it didn't seem to describe successful workarounds. 
   - Here's the output from working through that thread 
  
   - Looking at this issue outside the context of weewx, it seemed 
   reasonable to try to install pillow via pip, but doing so resulted in this 
   long, ugly error 
   
Wondering if anybody has navigated this issue before. Thanks!


-- 
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/cb092b9a-6b6f-4ad8-8165-74d46aac44afn%40googlegroups.com.


Re: [weewx-user] Re: New internet provider - now ftp doesn't work

2021-01-17 Thread Rich Strle
Jan 17 21:30:44 pi-weather weewx[429] ERROR weeutil.ftpupload: Failed 
uploading /var/www/html/weewx/yearradiation.png to server 
www.cliffandbuster.com. Reason: '229 Extended Passive Mode Entered 
(|||50458|)'
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine: 
ftpgenerator: (2): caught exception '': 229 
Extended Passive Mode Entered (|||50458|)
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
   Traceback (most recent call last):
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
   n = ftp_data.run()
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
 File "/usr/share/weewx/weeutil/ftpupload.py", line 163, in run
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
   ftp_server.storbinary(stor_cmd, fd)
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
 File "/usr/lib/python3.7/ftplib.py", line 504, in storbinary
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
   with self.transfercmd(cmd, rest) as conn:
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
 File "/usr/lib/python3.7/ftplib.py", line 399, in transfercmd
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
   return self.ntransfercmd(cmd, rest)[0]
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
 File "/usr/lib/python3.7/ftplib.py", line 359, in ntransfercmd
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
   host, port = self.makepasv()
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
 File "/usr/lib/python3.7/ftplib.py", line 337, in makepasv
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
   host, port = parse227(self.sendcmd('PASV'))
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
 File "/usr/lib/python3.7/ftplib.py", line 845, in parse227
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
   raise error_reply(resp)
Jan 17 21:30:45 pi-weather weewx[429] ERROR weewx.reportengine:
   ftplib.error_reply: 229 Extended Passive Mode Entered (|||50458|)
Jan 17 21:30:45 pi-weather weewx[429] DEBUG weewx.reportengine: Report 
'RSYNC' not enabled. Skipping.


On Sunday, January 17, 2021 at 9:28:38 PM UTC-6 Rich Strle wrote:

> I installed FileZilla and was able to use the same user name and password 
> to upload files from /var/www/html/weewx/ to the same spot on my webserver. 
> I did get an error message Hostname does not match certificate but I've 
> gotten that before...
>
> On Sunday, January 17, 2021 at 7:24:45 PM UTC-6 tke...@gmail.com wrote:
>
>> Can you FTP using Filezilla? The goal here is to see if it's some 
>> firewall / network/ provider issue, or a problem peculiar to the Python FTP 
>> library.
>>
>> On Sun, Jan 17, 2021 at 10:04 AM Rich Strle  wrote:
>>
>>> My bad, the ftp in whew still doesn't work. The Access Point only has an 
>>> IPv6 number listed, it doesn't have an IPv4 number listed. My website 
>>> provider only allows 1 sftp account at the root level and I was trying to 
>>> avoid using that.
>>>
>>> On Sunday, January 17, 2021 at 11:41:18 AM UTC-6 Rich Strle wrote:
>>>
 I spoke with t-mobile again. They didn't say they did anything but all 
 of a sudden ftp started working. I will continue to monitor.

 On Sunday, January 17, 2021 at 10:50:19 AM UTC-6 galfert wrote:

> Anyone care to google "T-Mobile FTP"  You'll see that this is an 
> issue for everyone! My recommendation is to try to instead use SFTP.
>
>
> On Sunday, January 17, 2021 at 11:41:25 AM UTC-5 Rich Strle wrote:
>
>> I did as instructed. Attached is the log file after I made the 
>> change. I have a call into my provider to see if they are IPV6.
>>
>>
>>
>> On Sunday, January 17, 2021 at 10:17:33 AM UTC-6 tke...@gmail.com 
>> wrote:
>>
>>> You definitely want passive mode (passive=1).
>>>
>>> Two things:
>>>
>>> 1. By any chance, is your new provider using IPV6 (instead of 
>>> the traditional IPV4)?
>>>
>>> 2. Set debug=2 in weewx.conf, then retry. This will put lots of 
>>> information in the log about what FTP is doing.
>>>
>>> -tk
>>>
>>> On Sun, Jan 17, 2021 at 7:46 AM Rich Strle  wrote:
>>>
 Thanks for your response David but that didn't fix my issue. 

 It was set at 1. I stopped the weewx process, set the ftp to 0, 
 restarted weewx and it did not help. I changed it back to 1.

 On Sunday, January 17, 2021 at 6:21:02 AM UTC-6 dav...@gmail.com 
 wrote:

> Check out 

Re: [weewx-user] Re: New internet provider - now ftp doesn't work

2021-01-17 Thread Rich Strle
I installed FileZilla and was able to use the same user name and password 
to upload files from /var/www/html/weewx/ to the same spot on my webserver. 
I did get an error message Hostname does not match certificate but I've 
gotten that before...

On Sunday, January 17, 2021 at 7:24:45 PM UTC-6 tke...@gmail.com wrote:

> Can you FTP using Filezilla? The goal here is to see if it's some firewall 
> / network/ provider issue, or a problem peculiar to the Python FTP library.
>
> On Sun, Jan 17, 2021 at 10:04 AM Rich Strle  wrote:
>
>> My bad, the ftp in whew still doesn't work. The Access Point only has an 
>> IPv6 number listed, it doesn't have an IPv4 number listed. My website 
>> provider only allows 1 sftp account at the root level and I was trying to 
>> avoid using that.
>>
>> On Sunday, January 17, 2021 at 11:41:18 AM UTC-6 Rich Strle wrote:
>>
>>> I spoke with t-mobile again. They didn't say they did anything but all 
>>> of a sudden ftp started working. I will continue to monitor.
>>>
>>> On Sunday, January 17, 2021 at 10:50:19 AM UTC-6 galfert wrote:
>>>
 Anyone care to google "T-Mobile FTP"  You'll see that this is an 
 issue for everyone! My recommendation is to try to instead use SFTP.


 On Sunday, January 17, 2021 at 11:41:25 AM UTC-5 Rich Strle wrote:

> I did as instructed. Attached is the log file after I made the change. 
> I have a call into my provider to see if they are IPV6.
>
>
>
> On Sunday, January 17, 2021 at 10:17:33 AM UTC-6 tke...@gmail.com 
> wrote:
>
>> You definitely want passive mode (passive=1).
>>
>> Two things:
>>
>> 1. By any chance, is your new provider using IPV6 (instead of 
>> the traditional IPV4)?
>>
>> 2. Set debug=2 in weewx.conf, then retry. This will put lots of 
>> information in the log about what FTP is doing.
>>
>> -tk
>>
>> On Sun, Jan 17, 2021 at 7:46 AM Rich Strle  wrote:
>>
>>> Thanks for your response David but that didn't fix my issue. 
>>>
>>> It was set at 1. I stopped the weewx process, set the ftp to 0, 
>>> restarted weewx and it did not help. I changed it back to 1.
>>>
>>> On Sunday, January 17, 2021 at 6:21:02 AM UTC-6 dav...@gmail.com 
>>> wrote:
>>>
 Check out http://weewx.com/docs/usersguide.htm#config_FTP and look 
 to add/adjust the passive setting in your weewx.conf config. 

 David 

 On Saturday, January 16, 2021 at 10:11:56 PM UTC-5 Rich Strle wrote:

> I changed out my internet provider to t-mobile home internet 
> service and now I'm getting ftp errors. I tried connecting to the ftp 
> from 
> another computer and that worked. When my raspberry pi tries to 
> connect I 
> get errors. This was working fine before I switched providers. Any 
> ideas?
>
> Jan 16 21:01:25 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
> Attempting connection to www.cliffandbuster.com
> Jan 16 21:01:26 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
> Connected to www.cliffandbuster.com
> Jan 16 21:01:26 pi-weather weewx[30706] ERROR weeutil.ftpupload: 
> Failed uploading /var/www/html/weewx/seasons.css to server 
> www.cliffandbuster.com. Reason: '229 Extended Passive Mode 
> Entered (|||50207|)'
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine: 
> ftpgenerator: (1): caught exception '': 
> 229 
> Extended Passive Mode Entered (|||50207|)
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:  
>  Traceback (most recent call last):
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:  
>File "/usr/share/weewx/weewx/reportengine.py", line 
> 331, in 
> run
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:  
>  n = ftp_data.run()
>
> -- 
>>> 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/ba3b1d83-b48b-4578-b7a5-85b3fe2e4fden%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> 

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-17 Thread vince
Restarted with your add-on plus belchertown both enabled - the RSS is 
nominally growing at 4 MB per 5-minute archive period.

1610928917 139.53125 63.97265625 15.453125
1610929217 143.02734375 70.41796875 15.4921875
1610929517 144.46484375 74.43359375 15.4921875
1610929817 145.96484375 78.48046875 15.55078125
1610930117 147.46484375 82.65625 15.58203125
1610930417 149.09375 86.69921875 15.58203125
1610930717 150.34375 90.55078125 15.58203125
1610931017 151.84375 94.203125 15.24609375

-- 
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/3c245310-ec4c-446a-8ebc-b3787176c6c0n%40googlegroups.com.


Re: [weewx-user] Re: New internet provider - now ftp doesn't work

2021-01-17 Thread Tom Keffer
Can you FTP using Filezilla? The goal here is to see if it's some firewall
/ network/ provider issue, or a problem peculiar to the Python FTP library.

On Sun, Jan 17, 2021 at 10:04 AM Rich Strle  wrote:

> My bad, the ftp in whew still doesn't work. The Access Point only has an
> IPv6 number listed, it doesn't have an IPv4 number listed. My website
> provider only allows 1 sftp account at the root level and I was trying to
> avoid using that.
>
> On Sunday, January 17, 2021 at 11:41:18 AM UTC-6 Rich Strle wrote:
>
>> I spoke with t-mobile again. They didn't say they did anything but all of
>> a sudden ftp started working. I will continue to monitor.
>>
>> On Sunday, January 17, 2021 at 10:50:19 AM UTC-6 galfert wrote:
>>
>>> Anyone care to google "T-Mobile FTP"  You'll see that this is an
>>> issue for everyone! My recommendation is to try to instead use SFTP.
>>>
>>>
>>> On Sunday, January 17, 2021 at 11:41:25 AM UTC-5 Rich Strle wrote:
>>>
 I did as instructed. Attached is the log file after I made the change.
 I have a call into my provider to see if they are IPV6.



 On Sunday, January 17, 2021 at 10:17:33 AM UTC-6 tke...@gmail.com
 wrote:

> You definitely want passive mode (passive=1).
>
> Two things:
>
> 1. By any chance, is your new provider using IPV6 (instead of
> the traditional IPV4)?
>
> 2. Set debug=2 in weewx.conf, then retry. This will put lots of
> information in the log about what FTP is doing.
>
> -tk
>
> On Sun, Jan 17, 2021 at 7:46 AM Rich Strle  wrote:
>
>> Thanks for your response David but that didn't fix my issue.
>>
>> It was set at 1. I stopped the weewx process, set the ftp to 0,
>> restarted weewx and it did not help. I changed it back to 1.
>>
>> On Sunday, January 17, 2021 at 6:21:02 AM UTC-6 dav...@gmail.com
>> wrote:
>>
>>> Check out http://weewx.com/docs/usersguide.htm#config_FTP and look
>>> to add/adjust the passive setting in your weewx.conf config.
>>>
>>> David
>>>
>>> On Saturday, January 16, 2021 at 10:11:56 PM UTC-5 Rich Strle wrote:
>>>
 I changed out my internet provider to t-mobile home internet
 service and now I'm getting ftp errors. I tried connecting to the ftp 
 from
 another computer and that worked. When my raspberry pi tries to 
 connect I
 get errors. This was working fine before I switched providers. Any 
 ideas?

 Jan 16 21:01:25 pi-weather weewx[30706] DEBUG weeutil.ftpupload:
 Attempting connection to www.cliffandbuster.com
 Jan 16 21:01:26 pi-weather weewx[30706] DEBUG weeutil.ftpupload:
 Connected to www.cliffandbuster.com
 Jan 16 21:01:26 pi-weather weewx[30706] ERROR weeutil.ftpupload:
 Failed uploading /var/www/html/weewx/seasons.css to server
 www.cliffandbuster.com. Reason: '229 Extended Passive Mode Entered
 (|||50207|)'
 Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
 ftpgenerator: (1): caught exception '': 229
 Extended Passive Mode Entered (|||50207|)
 Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
  Traceback (most recent call last):
 Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
File "/usr/share/weewx/weewx/reportengine.py", line 
 331, in
 run
 Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
  n = ftp_data.run()

 --
>> 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/ba3b1d83-b48b-4578-b7a5-85b3fe2e4fden%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/08999a97-41a4-4436-b59d-2f8793532fb6n%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 

Re: [weewx-user] How does battery and signal observation works/proccess?

2021-01-17 Thread Greg Troxel

"jmc...@gmail.com"  writes:

> For signal (signal1, signal2, etc..), I have link-quality (0-255) and dBm 
> (negative values).

I don't mean to contradict anything already said, but it's good to
understand that dBm means dB relative to 1 mW (milliwatt, 10^-3 W),
which is the standard way to measure RF power.  While calibration is
hard, it is entirely sensible for a receiver to measure signal strength
in dBm.  As an example -30 dBm means 30 dB, which is 3 B, which is 10^3
= 1000 less than 1 mW, which means 1 uW.  As a received signal strength
this is huge.

The smallest signal strength that works depends on the modulation and
data rate.  A very rough notion of a minimally workable signal strength
might be -100 dBm.  Take that with a huge grain of salt.

Also realize that much equipment isn't calibrated or close, so this is
all relative more than it should be.  But typically, relative values
from the same receiver can be compared.

Some stations (Davis) report something that is more or less % of recent
transmission that were received.  This is correlated with strength but
is fundamentally different. In RF data networking, what really matters
is if packets are received.

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


signature.asc
Description: PGP signature


Re: [weewx-user] Re: How does battery and signal observation works/proccess?

2021-01-17 Thread Jonis Maurin Ceará
Tks Gary, helped a lot!


Em dom., 17 de jan. de 2021 às 20:02, gjr80  escreveu:

> Hi,
>
> Provided the battery status field concerned is in your database schema
> WeeWX just stores whatever values the driver emits in any
> BatteryStatus fields, so if your driver emits 0 or 1 or a number from
> 0 to 255 that is what WeeWX stores. How that data is presented then comes
> down to the skins/reports that you are using. If you are using the Seasons
> skin Seasons assumes that if BatteryStatus is 0 then the battery
> status is 'OK' otherwise it is considered 'low'. If your station/driver
> works differently eg 1 is 'OK' and 0 is 'low' or >= 75 is 'OK' and < 75 is
> 'low' then you will need to alter some of the logic in the relevant report
> template. In the case of the Seasons skin this is
> skins/Seasons/sensors.inc, in particular the internal get_battery_status()
> function which is defined starting at line 11.
>
> Signal levels/states are similar but in this case you may need to make
> sure your driver emits signal status in fields that are included in your
> database schema, if the field names are different you will need to change
> the field/sensor mapping in the driver (if possible) or do some field name
> gymnastics in the StdCalibrate service
> . The Seasons skin
> does not include any code to display any of the signal fields, you will
> need to add this yourself to sensors.inc (the BatteryStatus HTML
> template code should give you some clues as to what to do/include). The
> other complicating factor here is that if your signal fields are dB then
> you will need to tell WeeWX this in order to make use of the
> formatting/conversion capabilities of the WeeWX report tags, otherwise
> WeeWX will treat the signal fields as just plain numbers (you could not
> bother but you will then be responsible for all formatting yourself). You
> might want to have a look at this thread
> 
> where I helped someone with similar requirements. In particular, look at
> the final sensors.inc (posted as sensors.txt) and the additions to
> skins/Seasons/skin.conf and user/extensions.py.
>
> Gary
>
> On Sunday, 17 January 2021 at 11:21:09 UTC+10 jmc...@gmail.com wrote:
>
>> Hi!
>> How does these two observations works?
>> I mean: for battery, I have "0-100" (%) for "inTempBatteryStatus"
>> field.but in reports page, I'm getting "LOW".
>>
>> For signal (signal1, signal2, etc..), I have link-quality (0-255) and dBm
>> (negative values). I'm not using any right now, but I would like to
>> useI just don't know how it is proccesed/displayed.
>>
>>
>>
>> --
> 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/DvHT0iuXcqc/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/37c346ae-73d1-482f-8246-35cce214c714n%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/CACK8wihQPFPw_NWM8d046Hb%2Byi7yr0svdSayZEogRQbkqi4Q%2BQ%40mail.gmail.com.


Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-17 Thread Garry A Lockyer
So you are seeing what I am - the leak is evident when belchertown is enabled 
*and* the .inc file is regenerated, yes?

Regards,

Garry Lockyer
C: +1.250.689.0686
E: ga...@lockyer.ca


> On Jan 17, 2021, at 16:06, vince  wrote:
> 
> garry - I installed your thing and did not see a memory increase 'without' 
> belchertown running, and but it 'is' leaking' it seems 'with' belchertown 1.2 
> installed.  I'm running the simulator and ubuntu-2004 in a Vagrant VM running 
> python3 weewx 4.3.0 via setup.py -  Here's some raw numbers with a little 
> commentary for when I did what.
> 
> echo "select dateTime,mem_size,mem_rss,mem_share from archive;"|sqlite3 
> /home/weewx/archive/mem.sdb | sed -e s/\|/\\t/g
> 
>  ran without belchertown here 
> 
> 1610919015132.8085937551.07421875 15.6171875
> 1610919315132.937551.375  15.6171875
> 1610919615132.9648437551.40234375 15.6171875
> 1610919915132.9648437551.40234375 15.6171875
> 1610920215132.9570312551.39453125 15.6171875
> 1610920515132.9570312551.39453125 15.6171875
> 1610920815133.1523437551.58984375 15.6171875
> 1610921115133.1523437551.875  15.62109375
> 1610921415133.1523437551.875  15.62109375
> 1610921715133.3242187552.046875   15.62109375
> 
>  restarted with belchertown here 
> 1610922315140.2890625 65.08203125 15.7421875
> 1610922615143.5234375 71.39453125 15.7421875
> 1610922915145.21875   75.625  15.7421875
> 1610923215146.71875   79.61328125 15.7421875
> 1610923515147.96875   83.43359375 15.7421875
> 1610923815149.6054687587.3671875  15.6875
> 
> --- restarted with belchertown 'on' and .inc generator 'off' 
> 1610925015128.3007812549.48046875 13.20703125
> 1610925315128.6796875 50.39453125 13.20703125
> 1610925615128.6796875 50.39453125 13.20703125
> 1610925916129.1796875 50.6796875  13.20703125
> 1610926215129.1796875 50.31640625 12.84375
> 1610926515129.4296875 50.9062512.96875
> 1610926815129.4296875 50.9062512.96875
> 1610927115129.4296875 50.9062512.96875
> 1610927415129.4296875 50.9062512.96875
> 1610927715129.4296875 50.9062512.96875
> 1610928015129.4296875 50.9062512.96875
> 
> 
> -- 
> 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/14a90da6-c84c-40ab-9a37-a85ae5aeddcan%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/A337768A-A7AB-46AD-8009-70CA6C5A8D8E%40gmail.com.


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

2021-01-17 Thread Mike Revitt
That is the next thing I plan to document, but at the moment I just do a 
file copy and am converting that to a SQLite backup and I am also planning 
to take advantage of S3 versioning so I have more than 1 copy

On Sunday, January 17, 2021 at 11:16:10 PM UTC LeaF wrote:

> Mike,
> You mentioned up above that you do a nightly backup to AWS S3 for the 
> database.  Can you show us how that was accomplished?   (I followed your 
> instructions on how to upload my weather data to S3, and it has worked 
> perfectly. Thanks)
> Lee
>
> On Sunday, January 3, 2021 at 2:29:38 AM UTC-8 mi...@cougar.eu.com wrote:
>
>> This was on of my main concerns when I first moved my WeeWX station to a 
>> Raspberry Pi, so I have added a nightly backup to AWS S3 for the database 
>> and as S3 now has versioning that will be my next addition so I have more 
>> than one backup .
>>
>> I haven't gotten around to writing this up yet, but it has been working 
>> uninterrupted for 213 days.
>>
>> If you want to know how I did it just reach out, the process is very 
>> similar to my solution for publishing to S3 which I have just finished 
>> writing up this week
>>
>> On Friday, January 1, 2021 at 8:35:37 PM UTC lang@googlemail.com 
>> wrote:
>>
>>> @ (not only) weatherlist
>>>
>>> If you had copied the list completely,  
>>>
>>> See below - bold by me.
>>>
>>> (but possibly a SSD comes cheaper than the higher capacity SLC micro SD 
>>> cards - still may need an enclosure with USB (best 3) interface; not too 
>>> expensive either)
>>>
>>> .
>>>
>>> Meteobridge enforces the use of one of the following industrial SLC 
>>> cards:
>>>
>>> ..
>>>
>>>- Western Digital/SanDisk SDSDQED-00*8G*-XI, SDSDQED-0*16G*-XI, 
>>>SDSDQED-0*32G*-XI, SDSDQED-064G-XI (microSD Card, 8-*64* GB, SLC 
>>>Flash) 
>>>- Greenliant GLS93MP008G1-I-BZ801 (microSD Card, *8 GB*, SLC Flash) 
>>>
>>> On 01.01.2021 20:44, Michael Form wrote:
>>>
>>> As someone has previously suggested, you can boot and run a Raspberry Pi 
>>> off of a SSD. These are a lot more reliable than most SD cards and are 
>>> available with huge capacities. Unless you are buying a 1 TB or 2 TB SSD, 
>>> they are also relatively inexpensive. I am running several Pis, both models 
>>> 3 and 4, on some 500 GB and 250 GB SSDs with no problems. You can also use 
>>> a MSATA or M2 drive as well. 
>>>
>>> Although there are off the shelf solutions to do this (check out 
>>> Geekworm), the easiest way is to buy an inexpensive SATA, MSATA or M2 to 
>>> USB external interface and plug it into the Pi's USB port. If you use a 
>>> Pi4, then you can run it as a USB3 device, which is faster.
>>>
>>> Mike
>>>
>>> On 1/1/2021 2:21 PM, steep...@gmail.com wrote:
>>>
>>> There are more SLC cards available from Mouser and other distributors 
>>> with much lager capacities. Those quoted below would struggle to contain an 
>>> operating system, WeeWX and data.
>>>
>>>  
>>>
>>> Sent from Mail  for 
>>> Windows 10
>>>
>>>  
>>>
>>> *From: *weather list
>>> *Sent: *01 January 2021 17:32
>>> *To: *weewx...@googlegroups.com
>>> *Subject: *Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 
>>> months of data?
>>>
>>>  
>>>
>>> The Meteobridge builder requires a high endurance microSD card for their 
>>> NANO SD unit; I haven’t investigated to see if they come in higher 
>>> capacities though it seems likely they would.
>>>
>>>  
>>>
>>> *Choice of microSD Card *
>>>
>>> To avoid lots of system fails caused by worn out consumer microSD cards 
>>> we restrict microSD cards that can be used in the NANO to 1GB and 2GB 
>>> industrial SLC cards. These are world-wide available from Mouser and other 
>>> electronic distributors. We decided to enforce use of these high endurance 
>>> cards to avoid having tons of unnecessary support requests and not to harm 
>>> the reputation of the NANO SD by failed cards. Please trust in our 
>>> experience with flash storage issues that there is simply no reasonable way 
>>> to avoid buying of high-price, high-endurance SLC storage. These are the 
>>> currently supported microSD cards: 
>>>
>>> swissbit SFSD1024N1BM1TO-I-DF-221-STD (microSD Card, 1 GB, SLC Flash, 
>>> -40°C - 85°C)
>>> swissbit SFSD2048N1BM1MT-I-ME-221-STD (microSD Card, 2 GB, SLC Flash, 
>>> -40°C - 85°C) 
>>>
>>> swissbit SFSD2048N1BM1MT-E-ME-221-STD (microSD Card, 2 GB, SLC Flash, 
>>> -25°C - 85°C)
>>> ATP AF2GUDI (microSD Card, 2 GB, SLC Flash, -40°C – 80°C)
>>> Cactus KS2GRIT-803M (microSD Card, 2 GB, SLC Flash, -45°C – 90°C)
>>>
>>> Panasonic SMSC02DA1 (microSD Card, 2 GB, SLC Flash, -40°C - 85°C)
>>>
>>> Apacer MSD02GIDI-T (microSD Card, 2 GB, SLC Flash) 
>>>
>>>
>>>
>>>
>>>
>>> On 1 Jan, 2021, at 08:52, Joe  wrote:
>>>
>>>  
>>>
>>> Sandisk extreme with the red and brown two tone color.  Unfortuantely, I 
>>> did not have one of these in the PI at the time.  Though I do now.  I've 
>>> never had one fail .
>>>
>>> On Monday, 

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-17 Thread vince
garry - I installed your thing and did not see a memory increase 'without' 
belchertown running, and but it 'is' leaking' it seems 'with' belchertown 
1.2 installed.  I'm running the simulator and ubuntu-2004 in a Vagrant VM 
running python3 weewx 4.3.0 via setup.py -  Here's some raw numbers with a 
little commentary for when I did what.

echo "select dateTime,mem_size,mem_rss,mem_share from archive;"|sqlite3 
/home/weewx/archive/mem.sdb | sed -e s/\|/\\t/g

 ran without belchertown here 

1610919015 132.80859375 51.07421875 15.6171875
1610919315 132.9375 51.375 15.6171875
1610919615 132.96484375 51.40234375 15.6171875
1610919915 132.96484375 51.40234375 15.6171875
1610920215 132.95703125 51.39453125 15.6171875
1610920515 132.95703125 51.39453125 15.6171875
1610920815 133.15234375 51.58984375 15.6171875
1610921115 133.15234375 51.875 15.62109375
1610921415 133.15234375 51.875 15.62109375
1610921715 133.32421875 52.046875 15.62109375

 restarted with belchertown here 
1610922315 140.2890625 65.08203125 15.7421875
1610922615 143.5234375 71.39453125 15.7421875
1610922915 145.21875 75.625 15.7421875
1610923215 146.71875 79.61328125 15.7421875
1610923515 147.96875 83.43359375 15.7421875
1610923815 149.60546875 87.3671875 15.6875

--- restarted with belchertown 'on' and .inc generator 'off' 
1610925015 128.30078125 49.48046875 13.20703125
1610925315 128.6796875 50.39453125 13.20703125
1610925615 128.6796875 50.39453125 13.20703125
1610925916 129.1796875 50.6796875 13.20703125
1610926215 129.1796875 50.31640625 12.84375
1610926515 129.4296875 50.90625 12.96875
1610926815 129.4296875 50.90625 12.96875
1610927115 129.4296875 50.90625 12.96875
1610927415 129.4296875 50.90625 12.96875
1610927715 129.4296875 50.90625 12.96875
1610928015 129.4296875 50.90625 12.96875


-- 
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/14a90da6-c84c-40ab-9a37-a85ae5aeddcan%40googlegroups.com.


[weewx-user] Re: error 401 with import WU

2021-01-17 Thread gjr80
I should also add can you double check your API key in /var/tmp/wu.conf is 
correct by confirming it against the API key listed under the 'API Keys' 
tab of 'Member Settings' when you login to your WU account.

Gary

On Monday, 18 January 2021 at 09:20:23 UTC+10 gjr80 wrote:

> Thank you. It would appear the credentials you are using to access WU are 
> not being accepted by WU. Currently there are three distinct pieces of 
> information you will use in WeeWX to access WU. To post WeeWX data to WU 
> you will use station ID or name and a password. These are defined in 
> weewx.conf under [StdRESTful] [[Wunderground]]. If WeeWX is successfully 
> uploading data to WU then these two parameters are correctly set.
>
> When using wee_import to download data from WU you need to use station ID 
> or name again but his time you need an API key rather than a password. The 
> API key must be obtained from WU separately is a hexadecimal string 32 
> characters in length. You must define your station ID or name and API key 
> in your import config file, in your case /var/tmp/wu.conf.
>
> Can you confirm that you have the correct API key against the api_key 
> setting in /var/tmp/wu.conf and is it 32 hexadecimal characters in length?
>
> Also, could you please post future console output as text rather than as 
> an image/screenshot, screenshots make life difficult for us, particularly 
> when using mobile devices. There are a number of ways to do this, if you 
> are unsure how you will find some guidance in the Help! posting to 
> weewx-user 
>  wiki 
> article.
>
> Gary
> On Sunday, 17 January 2021 at 06:24:49 UTC+10 f4...@f4gqk.fr wrote:
>
>> Hello,
>>
>> [image: error401.jpg]
>>
>>
>> My version Weewx is : 4.3.0
>>
>> Thanks
>>
>> Sebastien - F4GQK 
>>
>> Le mardi 12 janvier 2021 à 20:30:37 UTC+1, gjr80 a écrit :
>>
>>> Hi,
>>>
>>> Can you please post the exact output you are seeing when wee_import 
>>> fails. Also what version of WeeWX are you running?
>>>
>>> Gary
>>> On Wednesday, 13 January 2021 at 03:52:44 UTC+10 f4...@f4gqk.fr wrote:
>>>
 Hello,

 I am going to the following command:



 * wee_import --config=/etc/weewx/weewx.conf 
 --import-config=/var/tmp/wu.conf  *

 and I have a 401 error.

 *HTTP Error 401, Unauthorized*

 My station ID is OK on wunderground and my password is OK too.

 Does anyone have the same problem?

 Thank you and happy new year

 Sebastien 




-- 
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/c8f7c5ae-f46d-48cb-91d6-41c47fecd0e4n%40googlegroups.com.


[weewx-user] Re: error 401 with import WU

2021-01-17 Thread gjr80
Thank you. It would appear the credentials you are using to access WU are 
not being accepted by WU. Currently there are three distinct pieces of 
information you will use in WeeWX to access WU. To post WeeWX data to WU 
you will use station ID or name and a password. These are defined in 
weewx.conf under [StdRESTful] [[Wunderground]]. If WeeWX is successfully 
uploading data to WU then these two parameters are correctly set.

When using wee_import to download data from WU you need to use station ID 
or name again but his time you need an API key rather than a password. The 
API key must be obtained from WU separately is a hexadecimal string 32 
characters in length. You must define your station ID or name and API key 
in your import config file, in your case /var/tmp/wu.conf.

Can you confirm that you have the correct API key against the api_key 
setting in /var/tmp/wu.conf and is it 32 hexadecimal characters in length?

Also, could you please post future console output as text rather than as an 
image/screenshot, screenshots make life difficult for us, particularly when 
using mobile devices. There are a number of ways to do this, if you are 
unsure how you will find some guidance in the Help! posting to weewx-user 
 wiki 
article.

Gary
On Sunday, 17 January 2021 at 06:24:49 UTC+10 f4...@f4gqk.fr wrote:

> Hello,
>
> [image: error401.jpg]
>
>
> My version Weewx is : 4.3.0
>
> Thanks
>
> Sebastien - F4GQK 
>
> Le mardi 12 janvier 2021 à 20:30:37 UTC+1, gjr80 a écrit :
>
>> Hi,
>>
>> Can you please post the exact output you are seeing when wee_import 
>> fails. Also what version of WeeWX are you running?
>>
>> Gary
>> On Wednesday, 13 January 2021 at 03:52:44 UTC+10 f4...@f4gqk.fr wrote:
>>
>>> Hello,
>>>
>>> I am going to the following command:
>>>
>>>
>>>
>>> * wee_import --config=/etc/weewx/weewx.conf 
>>> --import-config=/var/tmp/wu.conf  *
>>>
>>> and I have a 401 error.
>>>
>>> *HTTP Error 401, Unauthorized*
>>>
>>> My station ID is OK on wunderground and my password is OK too.
>>>
>>> Does anyone have the same problem?
>>>
>>> Thank you and happy new year
>>>
>>> Sebastien 
>>>
>>>
>>>

-- 
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/0e0c29b3-1607-42b1-9b75-44b332f54340n%40googlegroups.com.


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

2021-01-17 Thread LeaF
Mike,
You mentioned up above that you do a nightly backup to AWS S3 for the 
database.  Can you show us how that was accomplished?   (I followed your 
instructions on how to upload my weather data to S3, and it has worked 
perfectly. Thanks)
Lee

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

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

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-17 Thread Garry A Lockyer
Thanks for your assistance.

I used setup.py to install WeeWX.

Yes, the HTML file is huge but it really is just a test case.  I suspect a 
smaller feed that generates a smaller include file would cause a smaller leak 
that wouldn’t be so obvious.  My actual extension has filters to select items 
of particular interest which would result in a smaller include file.

Re: cron, I’m thinking of using it to restart WeeWX every day.

I hadn’t thought about a separate job to do the RSS feed pulls because (in 
retrospect because of your good suggestion!) I’ve pretty much had “tunnel 
vision” working within WeeWX and Belchertown.  At this time, I’d bet that the 
memory problem will still exist because about 2 hours ago I disabled 
Belchertown.

The only change I made was setting ‘enable’ to false.  Memory usage is flat!

Regards,

Garry Lockyer
C: +1.250.689.0686
E: ga...@lockyer.ca


> On Jan 17, 2021, at 13:11, vince  wrote:
> 
> On Sunday, January 17, 2021 at 12:04:21 PM UTC-8 garrya...@gmail.com wrote:
>> RPi 4 - 8 GB
>> Ubuntu Raspberry Pi OS 20.10
>> Python3 - 3.8.6
>> WeeWX 4.3
>> Belchertown 1.2
>> - Problem was first noticed on RPi Zero W with Raspberry Pi OS Lite.
>> - Problem was reproduced on RPi 4 - 4 & 8 GB with Raspberry Pi OS 
>> Desktop.
>> - My extension was reduced to minimum code needed to reproduce the 
>> problem - that code is attached.
>> 
> 
> 
> Are you setup.py or dpkg for your installation ? Reason I'm asking is that 
> Tom previously wondered about a memory leak in other things like PIL/pillow.  
>  That's also why I was wondering about python2 vs. python3, as that would 
> change the versions of underlying things.
> 
> Let us know how it goes after you leave things alone for a few hours...
>  
> That URL returns a 800K file which is kinda big.  Do road conditions change 
> 'that' often ?   Why not have a standalone cron job that does all the heavy 
> lifting and writes out the output HTML and see if that helps any ?  That 
> would almost eliminate weewx from the equation wouldn't it ?
> 
>  
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/44242da6-de69-4f68-a0b2-963689c6f46an%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/265A1482-5171-4E6F-B8B2-2725C830B709%40gmail.com.


[weewx-user] Re: How does battery and signal observation works/proccess?

2021-01-17 Thread gjr80
Hi,

Provided the battery status field concerned is in your database schema 
WeeWX just stores whatever values the driver emits in any BatteryStatus 
fields, so if your driver emits 0 or 1 or a number from 0 to 255 that is 
what WeeWX stores. How that data is presented then comes down to the 
skins/reports that you are using. If you are using the Seasons skin Seasons 
assumes that if BatteryStatus is 0 then the battery status is 'OK' 
otherwise it is considered 'low'. If your station/driver works differently 
eg 1 is 'OK' and 0 is 'low' or >= 75 is 'OK' and < 75 is 'low' then you 
will need to alter some of the logic in the relevant report template. In 
the case of the Seasons skin this is skins/Seasons/sensors.inc, in 
particular the internal get_battery_status() function which is defined 
starting at line 11.

Signal levels/states are similar but in this case you may need to make sure 
your driver emits signal status in fields that are included in your 
database schema, if the field names are different you will need to change 
the field/sensor mapping in the driver (if possible) or do some field name 
gymnastics in the StdCalibrate service 
. The Seasons skin does 
not include any code to display any of the signal fields, you will need to 
add this yourself to sensors.inc (the BatteryStatus HTML template code 
should give you some clues as to what to do/include). The other 
complicating factor here is that if your signal fields are dB then you will 
need to tell WeeWX this in order to make use of the formatting/conversion 
capabilities of the WeeWX report tags, otherwise WeeWX will treat the 
signal fields as just plain numbers (you could not bother but you will then 
be responsible for all formatting yourself). You might want to have a look 
at this thread 
 where 
I helped someone with similar requirements. In particular, look at the 
final sensors.inc (posted as sensors.txt) and the additions to 
skins/Seasons/skin.conf and user/extensions.py.

Gary

On Sunday, 17 January 2021 at 11:21:09 UTC+10 jmc...@gmail.com wrote:

> Hi!
> How does these two observations works?
> I mean: for battery, I have "0-100" (%) for "inTempBatteryStatus" 
> field.but in reports page, I'm getting "LOW".
>
> For signal (signal1, signal2, etc..), I have link-quality (0-255) and dBm 
> (negative values). I'm not using any right now, but I would like to 
> useI just don't know how it is proccesed/displayed.
>
>
>
>

-- 
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/37c346ae-73d1-482f-8246-35cce214c714n%40googlegroups.com.


[weewx-user] Re: Weewx 4.3.0 and weewx multi on a fresh install

2021-01-17 Thread gjr80
Hi,

It would be helpful to see the WeeWX service file you are using and the 
corresponding defaults. Assuming you followed the weewx-multi 
 instructions in the wiki 
the service file should be /etc/init.d/weewx and the defaults 
/etc/default/weewx-multi. Please post the contents of both here.
 
>
> FYI : ( I ve posted the same post in weewx developpement group) 
>

Also, perhaps you did not read the weewx-user banner:

There is a separate group, weewx-development, for developers who are 
actively working on extensions and the weewx codebase. 

*Please do not cross-post to both weewx-user and weewx-development!*

Cross posting doesn't get you any more help any faster, in fact it just 
slows things down as we have twice as much to read.

Gary

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


Re: [weewx-user] Re: Rain Rate Calc Problem?

2021-01-17 Thread Banana Bob
It may be of interest to you that I had problems with the rain rate being 
reported as 0.00 all the time.
I eventually tracked this down to the weewx.conf file having cm/hr rather 
than mm/hr as the measurement required. This was in the Units Group section 
of Standard Report and Defaults lower down.

On Saturday, 26 December 2020 at 02:02:22 UTC+13 jbel...@gmail.com wrote:

> I do appreciate the guess, but I know they’re all using the stone conf 
> file since there’s only one! :-)
>
> Sent from my iPhone
>
> On Dec 24, 2020, at 6:56 PM, Tom Keffer  wrote:
>
> 
>
> Hard to say without seeing the log, but if I had to hazard a guess, I'd 
> say you're not consistently using the same copy of weewx.conf for all runs. 
> One of the copies does not have rainRate in [StdWXCalculate].
>
> But, that's just a guess. 
>
> On Thu, Dec 24, 2020 at 1:58 PM James Bellanca  wrote:
>
>> Appreciate the help so far. I had to wait for it to start raining again 
>> to do anything haha. And ok, so this is very strange behavior. 
>>
>> I stopped the weewx service, and ran it directly (log of the terminal 
>> window is attached). rainRate calculates fine, AND updates the database 
>> fine, just like it should. I stop the direct run, and run it as a service 
>> again, and it's working fine now! HOWEVER – Those results are weird, so I 
>> did it all again from scratch - rebooted, ran at startup as a service (no 
>> rain rate in the database again, just like before!), stopped it, ran it 
>> directly (rain rate works fine), stopped it, started the service (and now 
>> it works again?!). So it calculates rain rate, but won't update the 
>> database with it, UNTIL I run it directly first, then after that, it works 
>> even not directly... until I reboot, and it's broken again.
>>
>> Any idea what would cause that bizarre behavior???
>>
>> Attaching three files - 
>> (1) weewx.log from startup (directly) through some archive cycles where 
>> it was actually raining (which you'll see near the end).
>> https://www.dropbox.com/s/iqmi3e61y1zn0yt/weewx-1224-1500.log?dl=1
>> (2) terminal.log from running weewx directly. I can see in this that it's 
>> definitely calculating rainRate. It's just not updating the field in the 
>> database with the value it's calculating.
>> https://www.dropbox.com/s/xtbilj0s1ar9fw7/terminal-1224-1500.log?dl=1
>> (3) full weewx.log from Dec 9th (when I confided this new Pi 4) with 
>> weewx startup (as a service) through some archive cycles where it was 
>> raining, including the direct starts today where it worked.
>> https://www.dropbox.com/s/6veouk8rets8lsg/weewx-420-full.log?dl=1
>>
>>
>> On Thursday, December 24, 2020 at 1:00:04 PM UTC-5 tke...@gmail.com 
>> wrote:
>>
>>> The log does not include when weewx started up, so we can't tell which 
>>> weewx.conf it is using, what the sensor map was, nor what services are 
>>> being loaded. Otherwise, it looks normal. Do a restart, then post the log 
>>> through the first archive cycle.
>>>
>>> If rainRate is being calculated (and your instrumented version of 
>>> wxxtypes.py seems to indicate that it is), then, if it's in the schema, it 
>>> should be incorporated into the database.
>>>
>>> If you run weewxd directly from the command line, it will print out all 
>>> LOOP packets and archive records. What do they show for rainRate?
>>>
>>>
>>>
>>> On Thu, Dec 24, 2020 at 7:56 AM James Bellanca  
>>> wrote:
>>>
 Here's a little more info. I added from log.debug lines in the 
 wxxtypes.py rainRater class.

 In get_scalar that calculated rainRate, right before "return rr", I 
 added: log.debug("rr=%s", rr)
 In _setup in the if not... section right before the except error trap, 
 I added: log.debug("Log row %s %s %s.", time_ts, unit_system, rain)

 Now in the logs, I'm seeing a lot of rows like:

 Dec 24 10:36:56 raspberrypi weewx[18054] DEBUG weewx.wxxtypes: 
 rr=(0.0010683464566929135, 'inch_per_hour', 'group_rainrate')

 Dec 24 10:37:01 raspberrypi weewx[18054] DEBUG weewx.wxxtypes: 
 rr=(0.0015807874015748033, 'inch_per_hour', 'group_rainrate')
 ...

 Dec 24 10:42:04 raspberrypi weewx[18054] DEBUG weewx.wxxtypes: 
 rr=(0.0017618897637795277, 'inch_per_hour', 'group_rainrate')
 I've been watching the log for 10 mins now and I'm not seeing any "Log 
 row..." debug messages. 
 But, this means is calculating rainRate, but it's not updating the 
 database with what it's calculating for some reason.





 On Thursday, December 24, 2020 at 9:39:13 AM UTC-5 James Bellanca wrote:

> Both running on Python 3. 
>
> $ ps ax | grep python
>   831 ?Sl   468:45 *python3* /usr/share/weewx/weewxd --daemon 
> --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf
>
> Attaching 3 files - the weewx.conf files from both 4.1.1 and 4.2.2, 
> and the logs from 4.2.0 from 12/21 through today. It's been raining all 
> morning 

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-17 Thread vince
On Sunday, January 17, 2021 at 12:04:21 PM UTC-8 garrya...@gmail.com wrote:

> RPi 4 - 8 GB
> Ubuntu Raspberry Pi OS 20.10
> Python3 - 3.8.6
> WeeWX 4.3
> Belchertown 1.2
> - Problem was first noticed on RPi Zero W with Raspberry Pi OS Lite.
> - Problem was reproduced on RPi 4 - 4 & 8 GB with Raspberry Pi OS 
> Desktop.
> - My extension was reduced to minimum code needed to reproduce the 
> problem - that code is attached.
>
>

Are you setup.py or dpkg for your installation ? Reason I'm asking is that 
Tom previously wondered about a memory leak in other things like 
PIL/pillow.   That's also why I was wondering about python2 vs. python3, as 
that would change the versions of underlying things.

Let us know how it goes after you leave things alone for a few hours...
 
That URL returns a 800K file which is kinda big.  Do road conditions change 
'that' often ?   Why not have a standalone cron job that does all the heavy 
lifting and writes out the output HTML and see if that helps any ?  That 
would almost eliminate weewx from the equation wouldn't it ?

 

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


[weewx-user] Weewx 4.3.0 and weewx multi on a fresh install

2021-01-17 Thread sc.lep...@gmail.com
Hello 
FYI : ( I ve posted the same post in weewx developpement group) 


I reinstall from scratch my raspberry Pi 
I decided to install python3 by default  ( *now I use  python2*)  
I decided to install weewx 4.3.0 latest release

But  I decided to install weewx-multi ( i have 2 stations  an old WMR200 
with the good driver) 
and a new Froggit)
I install weewx-multi 
But  It seems there is a little bug when I want to stop service ...
When I start  : 

root@rpi-weewx:/etc/init.d# systemctl status weewx.service
● weewx.service - LSB: weewx-multi
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: failed (Result: exit-code) since Wed 2021-01-13 22:12:26 CET; 7s 
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 6148 ExecStart=/etc/init.d/weewx start (code=exited, 
status=1/FAILURE)
Tasks: 6 (limit: 2063)
   CGroup: /system.slice/weewx.service
   └─6163 python /usr/share/weewx/weewxd --daemon --log-label 
weewx-WMR200 --pidfile=/var/run/weewx-WMR200.pid /etc/weewx/WMR200.conf

janv. 13 22:12:27 rpi-weewx python[6163]: weewx-WMR200[6163] INFO 
weewx.restx: WOW: Posting not enabled.
janv. 13 22:12:27 rpi-weewx python[6163]: weewx-WMR200[6163] INFO 
weewx.restx: AWEKAS: Posting not enabled.
janv. 13 22:12:27 rpi-weewx python[6163]: weewx-WMR200[6163] INFO __main__: 
Starting up weewx version 4.3.0
janv. 13 22:12:27 rpi-weewx python[6163]: weewx-WMR200[6163] INFO 
weewx.engine: Using binding 'wx_binding' to database 'weewx-WMR200.sdb'
janv. 13 22:12:27 rpi-weewx python[6163]: weewx-WMR200[6163] INFO 
weewx.manager: Starting backfill of daily summaries
janv. 13 22:12:28 rpi-weewx python[6163]: weewx-WMR200[6163] INFO 
user.wmr200: Time drift between host and console in seconds:29
janv. 13 22:12:32 rpi-weewx python[6163]: weewx-WMR200[6163] INFO 
user.wmr200: genStartup() Still receiving archive packets cnt:0 len:1
janv. 13 22:12:32 rpi-weewx python[6163]: weewx-WMR200[6163] INFO 
user.wmr200: Using pc time adjusting archive record time by 29 sec 
2021-01-13 06:21:00 CET (1610515260) => 2021-01-13 06:21:29 CET (1610515289)
janv. 13 22:12:32 rpi-weewx python[6163]: weewx-WMR200[6163] INFO 
weewx.manager: Added record 2021-01-13 06:21:29 CET (1610515289) to 
database 'weewx-WMR200.sdb'
janv. 13 22:12:32 rpi-weewx python[6163]: weewx-WMR200[6163] INFO 
weewx.manager: Added record 2021-01-13 06:21:29 CET (1610515289) to daily 
summary in 'weewx-WMR200.sdb'


 this is important i thing  :  
6163 python /usr/share/weewx/weewxd --daemon --log-label weewx-WMR200 
--pidfile=/var/run/weewx-WMR200.pid /etc/weewx/WMR200.conf  

But When I want to stop the weewx service 
never this PID is killed ;-( ...

Perhaps I ve make some mistakes

Someone help me ? 
Best regards
Stéphane

-- 
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/1f6a5195-4a97-496e-b606-5faccd0ddb09n%40googlegroups.com.


Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-17 Thread garrya...@gmail.com
- If you disable Belchertown and 'enable' your custom code that generates 
the include file, does memory grow ?
  - Yes.  I just started at test run with WXFeedsMemoryTest.py (attached 
here) and Belchertown enabled.  
The station website is at: 
https://lockyer.ca/weather/OsoyoosLakeNorthEast and the mem graphs are 
   at: https://lockyer.ca/weather/OsoyoosLakeNorthEast/mem.

- You also haven't told us what hardware you're on.  Is it a pi ?  What os 
?   What version ?
  - From an earlier post:
RPi 4 - 8 GB
Ubuntu Raspberry Pi OS 20.10
Python3 - 3.8.6
WeeWX 4.3
Belchertown 1.2

- Problem was first noticed on RPi Zero W with Raspberry Pi OS Lite.
- Problem was reproduced on RPi 4 - 4 & 8 GB with Raspberry Pi OS 
Desktop.
- My extension was reduced to minimum code needed to reproduce the 
problem - that code is attached.

- Your log says you're running python3.  Have you tried the same thing on a 
python2 system ?
  - No.  I have no interest in python2. :^))

- Can you duplicate the problem using just the Simulator driver and your 
addition so we can try to replicate it ?
  - The run I just started (about 11:30 AM PST) is using the Simulator 
(rather than WeatherFlow), and memory usage 
is growing.  I'll let it fun for 1-2 hours and then disable Belchertown.

Regards,

Garry

Sorry but I was not able to attach a file to this message!  I was able to 
previously under Raspberry Pi OS so maybe it's related to Ubuntu?

Here's the code for WXFeedsMemoryTest.py:

##
#   WXFeedsMemoryTest.py
#
#Copyright (c) 2021 Garry Lockyer - ga...@lockyer.ca
#See the file LICENSE.txt for your rights.
#
#   Based on alarm.py by:
#Copyright (c) 2009-2019 Tom Keffer 
#See the file LICENSE.txt for your rights.

"""
To use this service, add the following to the weewx configuration file:

[WXFeedsMemoryTest]
# No options are required or processed at this time.

This service requests data from an RSS feed:

feedURL = 
"https://511.alberta.ca/api/v2/get/winterroads?format=json=en;

and creates an include file that the Belchertown Skin can include.

***
To enable this service:
1) Copy this file to the WeWX bin/user directory - /home/weewx/bin/user if 
WeeWX was 
   installed with setup.py. See https://bit.ly/33YHsqX for where your user
   directory is located.

2) Modify the weewx configuration file by adding this service to the option
"report_services", located in section [Engine][[Services]].
[Engine]
  [[Services]]
...
report_services = weewx.engine.StdPrint, weewx.engine.StdReport, 
user.WXFeedsMemoryTest.WXFeedsMemoryTest

# I want WXFeedsMemoryTest to run before StdReport so I actually use:

report_services = weewx.engine.StdPrint, 
user.WXFeedsMemoryTest.WXFeedsMemoryTest, weewx.engine.StdReport

"""

import weewx
from weewx.engine import StdService
import logging
import os
import sys
import gc
import requests
import shutil

# Inherit from the base class StdService:

class WXFeedsMemoryTest(StdService):
"""
A WeeWX service extension to demonstrate that WeeWX with the 
Belchertown skin 
memory usage grows after each archive period.

All it does is get one RSS feed and produce one Belchertown include 
file.

Other than creating an include in skins/Belchertown there are no 
dependencies 
on any skin.
"""

def __init__(self, engine, config_dict):
# Pass the initialization information on to my superclass:
super(WXFeedsMemoryTest, self).__init__(engine, config_dict)

self.log = logging.getLogger( __name__ )
assert self.log != None

self.log.info( "WXFeedsMemoryTest::__init__(). . ." )

self.bind( weewx.NEW_ARCHIVE_RECORD, self.new_archive_record )

return

def new_archive_record(self, event):
"""Gets called on a new archive record event."""

self.log.info( "WXFeedsMemoryTest::new_archive_record(). . ." )

self.log.info( "Process ID: %d" % os.getpid() )

#   This URL is for Alberta 511's Road Conditions RSS feed.

feedURL = 
"https://511.alberta.ca/api/v2/get/winterroads?format=json=en;

# The include file is used by the Belchertown Skin.
#
# The problem:
#
# If the include file is static, as in it is not re-created while 
# Belchertown is enabled, weewx memory usage does not grow.
#
# If the include file is dynamic, as in it is re-created while 
# Belchertown is enabled, weewx memory usage increases 
# after each file re-creation.
#
# If this service is enabled AND Belchertown is disabled, memory 
# usage does not grow,

includeFileName = 
"/home/weewx/skins/Belchertown/index_hook_after_charts.inc"
tempFileName= 

Re: [weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-17 Thread Rainer Lang
As a workaround I would remove / replace your suspects - change 
"Umlaute", if any, from Ä -> AE, Ö -->OE, Ü --> UE, accents just omit 
them and leave the vowels without them.
They will anyway only appear in temporary graphs. Then figure out your 
UTF-8 issue and fix it, while your weewx could already run and archive data.


On 17.01.2021 19:59, S R wrote:
thanks for the clarification. i will switch the protocol to ecowitt, 
but the more immediate problem is the UTF-8 error which is now 
preventing weewx from starting.


On Sunday, January 17, 2021 at 4:30:38 PM UTC+1 galfert wrote:

This thread started with the discussion being around the Ambient
WS-2902 and that is totally different despite looking like the
same unit. This is because Ambient is the only Fine Offset clone
reseller that changes the firmware and they limit options. The
Ambient version does not let you upload to custom server address.
The confusion here is that my response was because I thought you
had and Ambient branded unit. Since you don't have an Ambient
branded unit you do have the option to send to a custom server
using both WU and Ecowitt protocols. The WU protocol is limited
and only sends the basic set of sensors. The Ecowitt protocol
allows you to send a lot more optional sensors like PM2.5, soil
moisture, extra temp/hum sensorsetc. But still you'll have to
configure the Interceptor driver to match the protocol type that
you set in you WH2900C for uploading to your custom server.

The GW1000 though is still a more elegant and newer solution.

* The newest Ambient WS-2902 firmware finally after many years
does gain the ability to send to a custom serverBUT it is not
WU protocol and it is not Ecowitt protocolit is
Ambientweather.net protocol and enough significant differences
that the Interceptor driver will not work. This newest firmware is
not yet officially supported by Ambient. They haven't yet release
the updated awnet mobile app to enable turning and configuring
this option. All of these complexities and changing nature of the
situation makes it difficult to explain the situation to cover all
possible scenarios...what model you have and whom it is from and
what firmware version you are running and all the different
supporting protocols that are possible.

Using pfsense to capture and forward packets is really unnecessary
for anyone with a non-Ambient WH2900Cas it has a built in
simple to configure "Customized" server upload feature.



On Sunday, January 17, 2021 at 7:32:03 AM UTC-5 sjr4...@gmail.com
wrote:

For the record, mine is a Chinese Mi-Sol WH2900C. It is a copy
of the Fine Offset WH2900 or the Ecowitt WS2950. Indeed, the
unit requires a connection to Ecowitt to set the Time/Date and
automatically downloaded the EasyWeather 1.56 firmware update
from Ecowitt.

I haven't got the outdoor setup done yet, while i play with
getting the unit up and running. but Ecowitt, shows my indoor
temperature and pressure on the home page. I use pfsense so
can run a packet capture if it helps. Since editing the
weewx.conf file, i am getting the utf-8 problem. I guess this
is related to me using European accented characters in my
editors which are UTF-8. So that leaves me with two questions;
1) how to have it accept the UTF-8 characters
2) you mentioned not getting all the sensor data, unless using
Ecowitt. In view, that i am. Can you tell me what additional
parameters i need in the config file please.



On Sunday, January 17, 2021 at 9:21:33 AM UTC+1 S R wrote:

almost there, but now

/usr/local/share/weewx # ./bin/wee_reports

Traceback (most recent call last):
  File "./bin/wee_reports", line 103, in 
    main()
  File "./bin/wee_reports", line 51, in main
    config_path, config_dict =
weecfg.read_config(options.config_path, args)
  File "/usr/local/share/weewx/bin/weecfg/__init__.py",
line 180, in read_config
    default_encoding='utf-8')
  File
"/usr/local/lib/python3.7/site-packages/configobj.py",
line 1229, in __init__
    self._load(infile, configspec)
  File
"/usr/local/lib/python3.7/site-packages/configobj.py",
line 1287, in _load
    content = self._handle_bom(content)

On Saturday, January 16, 2021 at 11:30:28 PM UTC+1 galfert
wrote:

Yes the best method when using the Interceptor is to
use the Customized server settings. The path doesn't
matter. But in some firmware versions it just couldn't
be left blank or it wouldn't send. So just put 

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-17 Thread garrya...@gmail.com

   
   - If you disable Belchertown and 'enable' your custom code that 
   generates the include file, does memory grow ?
  - Yes.  I just started at test run with WXFeedsMemoryTest.py 
  (attached here) and Belchertown enabled.  The station website is at: 
  https://lockyer.ca/weather/OsoyoosLakeNorthEast and the mem graphs 
  are  at: https://lockyer.ca/weather/OsoyoosLakeNorthEast/mem.
   - You also haven't told us what hardware you're on.  Is it a pi ?  What 
   os ?   What version ?
  - From an earlier post:
 - RPi 4 - 8 GB
 - Ubuntu Raspberry Pi OS 20.10
 - Python3 - 3.8.6
 - WeeWX 4.3
 - Belchertown 1.2
 - Problem was first noticed on RPi Zero W with Raspberry Pi OS 
  Lite.
  - Problem was reproduced on RPi 4 - 4 & 8 GB with Raspberry Pi OS 
  Desktop.
  - My extension was reduced to minimum code needed to reproduce the 
  problem - that code is attached.
   - Your log says you're running python3.  Have you tried the same thing 
   on a python2 system ?
  - No.  I have no interest in python2. :^))
   - Can you duplicate the problem using just the Simulator driver and your 
   addition so we can try to replicate it ?
  - The run I just started (about 11:30 AM PST) is using the Simulator 
  (rather than WeatherFlow).
   
On Sunday, January 17, 2021 at 9:28:24 AM UTC-8 vince wrote:

> On Saturday, January 9, 2021 at 8:02:51 PM UTC-8 garrya...@gmail.com 
> wrote:
>
>> My experience is that when I recreate an include file for Belchertown on 
>> each archive cycle, as an extension to Belchertown or as a service, memory 
>> usage increases with each cycle and eventually errors start.  
>>
>
> I continue to think you need to concentrate on what your code is doing and 
> your os configuration.
>
>- If you disable Belchertown and 'enable' your custom code that 
>generates the include file, does memory grow ?
>- You also haven't told us what hardware you're on.  Is it a pi ? 
> What os ?   What version ?
>- Your log says you're running python3.  Have you tried the same thing 
>on a python2 system ?
>- Can you duplicate the problem using just the Simulator driver and 
>your addition so we can try to replicate it ?
>
>
>  
>

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


Re: [weewx-user] Data errors preventing report generation

2021-01-17 Thread Tom Keffer
I think we've seen this issue before with the hp1000 driver. See this
thread: https://groups.google.com/g/weewx-user/c/XytZUhZVfuY/m/yKub_9UMCAAJ

Just let it run and see if the errors eventually clear up.

On Sun, Jan 17, 2021 at 11:13 AM icoj...@gmail.com 
wrote:

> Ignore the issue with the gap - I tried to wipe the weather station, it
> wiped 2021 data but there seems to be an issue preventing it from wiping
> 2020 data.  Is there any way I can prevent weewx retrieving historical
> records?
>
> On Sunday, 17 January 2021 at 19:01:28 UTC icoj...@gmail.com wrote:
>
>> Thank you for your response, unfortunately that is because I tried to
>> remove the daemon to see if that was the issue so I must have started two
>> somehow.  I have since done a completely fresh install on a brand new sd
>> card and I watched the log from the beginning.  It populated historic data
>> from the last 4 or so months, then it started throwing the same unique
>> constraint errors.  The excerpts from the log are below.  I thought it
>> could be a time issue but now I'm thinking it must be a weather station
>> issue.  Can anyone see anything obvious below?
>>
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Initializing weewx
>> version 4.3.0
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Using Python 3.7.3
>> (default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Platform
>> Linux-5.4.83-v7+-armv7l-with-debian-10.7
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Locale is
>> 'en_GB.UTF-8'
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Using configuration
>> file /home/weewx/weewx.conf
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Debug is 1
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG __main__: Initializing engine
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO weewx.engine: Loading station
>> type HP1000 (user.HP1000)
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: HP1000 Starting
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Using
>> user-defined broadcast mask - 192.168.86.35
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Address Mask =
>> 192.168.86.35
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Retry count =
>> 5.00
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Socket timeout =
>> 5.00
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Loop delay =
>> 15.00
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Retry Wait =
>> 5.00
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Max Retry =
>> 3.00
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service
>> weewx.engine.StdTimeSynch
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished
>> loading service weewx.engine.StdTimeSynch
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service
>> weewx.engine.StdConvert
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO weewx.engine: StdConvert
>> target unit is 0x1
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished
>> loading service weewx.engine.StdConvert
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service
>> weewx.engine.StdCalibrate
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished
>> loading service weewx.engine.StdCalibrate
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service
>> weewx.engine.StdQC
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished
>> loading service weewx.engine.StdQC
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service
>> weewx.wxservices.StdWXCalculate
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO weewx.manager: Created and
>> initialized table 'archive' in database 'weewx.sdb'
>> Jan 17 16:14:35 weatherpi weewx[3716] INFO weewx.manager: Created daily
>> summary tables
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.manager: Daily summary
>> version is 3.0
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished
>> loading service weewx.wxservices.StdWXCalculate
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service
>> weewx.wxxtypes.StdWXXTypes
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished
>> loading service weewx.wxxtypes.StdWXXTypes
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service
>> weewx.wxxtypes.StdPressureCooker
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished
>> loading service weewx.wxxtypes.StdPressureCooker
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service
>> weewx.wxxtypes.StdRainRater
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished
>> loading service weewx.wxxtypes.StdRainRater
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service
>> weewx.wxxtypes.StdDelta
>> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished
>> loading 

Re: [weewx-user] Data errors preventing report generation

2021-01-17 Thread icoj...@gmail.com
Ignore the issue with the gap - I tried to wipe the weather station, it 
wiped 2021 data but there seems to be an issue preventing it from wiping 
2020 data.  Is there any way I can prevent weewx retrieving historical 
records?

On Sunday, 17 January 2021 at 19:01:28 UTC icoj...@gmail.com wrote:

> Thank you for your response, unfortunately that is because I tried to 
> remove the daemon to see if that was the issue so I must have started two 
> somehow.  I have since done a completely fresh install on a brand new sd 
> card and I watched the log from the beginning.  It populated historic data 
> from the last 4 or so months, then it started throwing the same unique 
> constraint errors.  The excerpts from the log are below.  I thought it 
> could be a time issue but now I'm thinking it must be a weather station 
> issue.  Can anyone see anything obvious below?
>
> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Initializing weewx 
> version 4.3.0
> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Using Python 3.7.3 
> (default, Jul 25 2020, 13:03:44) #012[GCC 8.3.0]
> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Platform 
> Linux-5.4.83-v7+-armv7l-with-debian-10.7
> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Locale is 
> 'en_GB.UTF-8'
> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Using configuration 
> file /home/weewx/weewx.conf
> Jan 17 16:14:35 weatherpi weewx[3716] INFO __main__: Debug is 1
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG __main__: Initializing engine
> Jan 17 16:14:35 weatherpi weewx[3716] INFO weewx.engine: Loading station 
> type HP1000 (user.HP1000)
> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: HP1000 Starting
> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Using user-defined 
> broadcast mask - 192.168.86.35
> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Address Mask = 
> 192.168.86.35
> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Retry count = 
> 5.00
> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Socket timeout = 
> 5.00
> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Loop delay = 
> 15.00
> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Retry Wait = 
> 5.00
> Jan 17 16:14:35 weatherpi weewx[3716] INFO root: HP100: Max Retry = 
> 3.00
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service 
> weewx.engine.StdTimeSynch
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdTimeSynch
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service 
> weewx.engine.StdConvert
> Jan 17 16:14:35 weatherpi weewx[3716] INFO weewx.engine: StdConvert target 
> unit is 0x1
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdConvert
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service 
> weewx.engine.StdCalibrate
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdCalibrate
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service 
> weewx.engine.StdQC
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdQC
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service 
> weewx.wxservices.StdWXCalculate
> Jan 17 16:14:35 weatherpi weewx[3716] INFO weewx.manager: Created and 
> initialized table 'archive' in database 'weewx.sdb'
> Jan 17 16:14:35 weatherpi weewx[3716] INFO weewx.manager: Created daily 
> summary tables
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.manager: Daily summary 
> version is 3.0
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished loading 
> service weewx.wxservices.StdWXCalculate
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service 
> weewx.wxxtypes.StdWXXTypes
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished loading 
> service weewx.wxxtypes.StdWXXTypes
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service 
> weewx.wxxtypes.StdPressureCooker
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished loading 
> service weewx.wxxtypes.StdPressureCooker
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service 
> weewx.wxxtypes.StdRainRater
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished loading 
> service weewx.wxxtypes.StdRainRater
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service 
> weewx.wxxtypes.StdDelta
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Finished loading 
> service weewx.wxxtypes.StdDelta
> Jan 17 16:14:35 weatherpi weewx[3716] DEBUG weewx.engine: Loading service 
> weewx.engine.StdArchive
> Jan 17 16:14:35 weatherpi weewx[3716] INFO weewx.engine: Archive will use 
> data binding wx_binding
> Jan 17 16:14:35 weatherpi weewx[3716] INFO weewx.engine: Record generation 

Re: \Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Δημήτρης Βήχος
done with uncomment thank you!! sometimes cant see the obvious!   and with 
greek characters on station name. theres no issue with greek characters.

Στις Κυριακή, 17 Ιανουαρίου 2021 στις 8:33:44 μ.μ. UTC+2, ο χρήστης Ξ 
έγραψε:

> please uncomment (#) the URL:
> # If you have a website, you may specify an URL
> station_url = https://kairos.moudania.com/kolxiko/
>
>
>
> On Sunday, January 17, 2021 at 8:14:31 PM UTC+2 hobbyl...@gmail.com wrote:
>
>> #   This section is for information about the station.
>>
>> [Station]
>> 
>> # Description of the station location
>> location = Kolxiko weather station
>> 
>> # Latitude in decimal degrees. Negative for southern hemisphere
>> latitude = 40.757
>> # Longitude in decimal degrees. Negative for western hemisphere.
>> longitude = 23.128
>> 
>> # Altitude of the station, with unit it is in. This is downloaded from
>> # from the station if the hardware supports it.
>> altitude = 147, meter
>> 
>> # Set to type of station hardware. There must be a corresponding 
>> stanza
>> # in this file with a 'driver' parameter indicating the driver to be 
>> used.
>> station_type = FineOffsetUSB
>> 
>> # If you have a website, you may specify an URL
>> #station_url = https://kairos.moudania.com/kolxiko/
>> 
>> # 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
>>
>>
>> ##
>> [StdRESTful]
>> 
>> [[StationRegistry]]
>> # To register this weather station with weewx, set this to true
>> register_this_station = true
>> Στις Κυριακή, 17 Ιανουαρίου 2021 στις 8:08:21 μ.μ. UTC+2, ο χρήστης Ξ 
>> έγραψε:
>>
>>> Maybe ask in the Belchertown theme thread in the group?  For me it's 
>>> enough to change in weewx.conf: 
>>> [Station]
>>>
>>> # Description of the station location
>>> location = [Name of station in Greek/Bulgarian/Latin]
>>>
>>> # If you have a website, you may specify an URL
>>> station_url = [url of station]
>>>
>>> and 
>>> [[StationRegistry]]
>>> # To register this weather station with weewx, set this to true
>>> register_this_station = True
>>>
>>> I have no idea how the config of Belchertown is supposed to be done but 
>>> I think changing these three fields should be enough.
>>>
>>

-- 
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/69d5a42f-5310-4fb0-9b7c-f05f49975e02n%40googlegroups.com.


[weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-17 Thread S R
thanks for the clarification. i will switch the protocol to ecowitt, but 
the more immediate problem is the UTF-8 error which is now preventing weewx 
from starting.

On Sunday, January 17, 2021 at 4:30:38 PM UTC+1 galfert wrote:

> This thread started with the discussion being around the Ambient WS-2902 
> and that is totally different despite looking like the same unit. This is 
> because Ambient is the only Fine Offset clone reseller that changes the 
> firmware and they limit options. The Ambient version does not let you 
> upload to custom server address. The confusion here is that my response was 
> because I thought you had and Ambient branded unit. Since you don't have an 
> Ambient branded unit you do have the option to send to a custom server 
> using both WU and Ecowitt protocols. The WU protocol is limited and only 
> sends the basic set of sensors. The Ecowitt protocol allows you to send a 
> lot more optional sensors like PM2.5, soil moisture, extra temp/hum 
> sensorsetc. But still you'll have to configure the Interceptor driver 
> to match the protocol type that you set in you WH2900C for uploading to 
> your custom server. 
>
> The GW1000 though is still a more elegant and newer solution. 
>
> * The newest Ambient WS-2902 firmware finally after many years does gain 
> the ability to send to a custom serverBUT it is not WU protocol and it 
> is not Ecowitt protocolit is Ambientweather.net protocol and enough 
> significant differences that the Interceptor driver will not work. This 
> newest firmware is not yet officially supported by Ambient. They haven't 
> yet release the updated awnet mobile app to enable turning and configuring 
> this option. All of these complexities and changing nature of the situation 
> makes it difficult to explain the situation to cover all possible 
> scenarios...what model you have and whom it is from and what firmware 
> version you are running and all the different supporting protocols that are 
> possible. 
>
> Using pfsense to capture and forward packets is really unnecessary for 
> anyone with a non-Ambient WH2900Cas it has a built in simple to 
> configure "Customized" server upload feature.
>
>
>
> On Sunday, January 17, 2021 at 7:32:03 AM UTC-5 sjr4...@gmail.com wrote:
>
>> For the record, mine is a Chinese Mi-Sol WH2900C. It is a copy of the 
>> Fine Offset WH2900 or the Ecowitt WS2950. Indeed, the unit requires a 
>> connection to Ecowitt to set the Time/Date and automatically downloaded the 
>> EasyWeather 1.56 firmware update from Ecowitt. 
>>
>> I haven't got the outdoor setup done yet, while i play with getting the 
>> unit up and running. but Ecowitt, shows my indoor temperature and pressure 
>> on the home page. I use pfsense so can run a packet capture if it helps. 
>> Since editing the weewx.conf file, i am getting the utf-8 problem. I guess 
>> this is related to me using European accented characters in my editors 
>> which are UTF-8. So that leaves me with two questions;
>> 1) how to have it accept the UTF-8 characters
>> 2) you mentioned not getting all the sensor data, unless using Ecowitt. 
>> In view, that i am. Can you tell me what additional parameters i need in 
>> the config file please.
>>
>>
>>
>> On Sunday, January 17, 2021 at 9:21:33 AM UTC+1 S R wrote:
>>
>>> almost there, but now 
>>>
>>> /usr/local/share/weewx # ./bin/wee_reports
>>>
>>> Traceback (most recent call last):
>>>   File "./bin/wee_reports", line 103, in 
>>> main()
>>>   File "./bin/wee_reports", line 51, in main
>>> config_path, config_dict = weecfg.read_config(options.config_path, 
>>> args)
>>>   File "/usr/local/share/weewx/bin/weecfg/__init__.py", line 180, in 
>>> read_config
>>> default_encoding='utf-8')
>>>   File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1229, 
>>> in __init__
>>> self._load(infile, configspec)
>>>   File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1287, 
>>> in _load
>>> content = self._handle_bom(content)
>>>
>>> On Saturday, January 16, 2021 at 11:30:28 PM UTC+1 galfert wrote:
>>>
 Yes the best method when using the Interceptor is to use the Customized 
 server settings. The path doesn't matter. But in some firmware versions it 
 just couldn't be left blank or it wouldn't send. So just put in index.php? 
 for the path.


 On Saturday, January 16, 2021 at 3:49:17 PM UTC-5 sjr4...@gmail.com 
 wrote:

> OK. So i am homing in a little closer here. 
> I have configured the console to wunderground and it is working. 
>
> Now i need to adjust weewx.conf with the following, but as the weewx 
> server is on a different subnet, i will need to use listen mode. 
>
> [Interceptor]
> driver = user.interceptor
> device_type = wu-client 
>
> If i understand, i can point the console with a custom config to my 
> server, and then publish from my server to wunderground right?
>
> if i do that, 

[weewx-user] Re: sensor for the snow depth

2021-01-17 Thread Clay Jackson
I'm working on one now using an Ultrasonic Distance sensor - hopefully will 
have it up and running on my bench sometime this week.   My goal is to get 
it mounted outside before our next forecast snow (Friday).

On Sunday, January 17, 2021 at 5:48:12 AM UTC-8 sali...@gmail.com wrote:

>
> Has anyone already made a sensor for the snow depth to connect it to the 
> RPi and display the data on Weewx?
>
> bye
>
> Patrick
>

-- 
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/32f384e5-4e81-483a-9d11-54ab525a1386n%40googlegroups.com.


Re: \Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Ξ
please uncomment (#) the URL:
# If you have a website, you may specify an URL
station_url = https://kairos.moudania.com/kolxiko/



On Sunday, January 17, 2021 at 8:14:31 PM UTC+2 hobbyl...@gmail.com wrote:

> #   This section is for information about the station.
>
> [Station]
> 
> # Description of the station location
> location = Kolxiko weather station
> 
> # Latitude in decimal degrees. Negative for southern hemisphere
> latitude = 40.757
> # Longitude in decimal degrees. Negative for western hemisphere.
> longitude = 23.128
> 
> # Altitude of the station, with unit it is in. This is downloaded from
> # from the station if the hardware supports it.
> altitude = 147, meter
> 
> # Set to type of station hardware. There must be a corresponding stanza
> # in this file with a 'driver' parameter indicating the driver to be 
> used.
> station_type = FineOffsetUSB
> 
> # If you have a website, you may specify an URL
> #station_url = https://kairos.moudania.com/kolxiko/
> 
> # 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
>
>
> ##
> [StdRESTful]
> 
> [[StationRegistry]]
> # To register this weather station with weewx, set this to true
> register_this_station = true
> Στις Κυριακή, 17 Ιανουαρίου 2021 στις 8:08:21 μ.μ. UTC+2, ο χρήστης Ξ 
> έγραψε:
>
>> Maybe ask in the Belchertown theme thread in the group?  For me it's 
>> enough to change in weewx.conf: 
>> [Station]
>>
>> # Description of the station location
>> location = [Name of station in Greek/Bulgarian/Latin]
>>
>> # If you have a website, you may specify an URL
>> station_url = [url of station]
>>
>> and 
>> [[StationRegistry]]
>> # To register this weather station with weewx, set this to true
>> register_this_station = True
>>
>> I have no idea how the config of Belchertown is supposed to be done but I 
>> think changing these three fields should be enough.
>>
>

-- 
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/fccb4787-098d-4a77-b6d4-12a89c5147f9n%40googlegroups.com.


Re: \Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread salinois

hi,

http://jurassikpat.ddns.net/weewx/belchertown

patrick

Le 17/01/2021 à 18:36, Ξ a écrit :

what's your weather station's URL?

On Sunday, January 17, 2021 at 7:20:31 PM UTC+2 hobbyl...@gmail.com wrote:

all the greek stations are have english characters. i was cheking
this. also changing the name of the station in weewx.conf and
restarting weewx, my weather station dont yet appears on map.

Στις Κυριακή, 17 Ιανουαρίου 2021 στις 6:32:44 μ.μ. UTC+2, ο
χρήστης sali...@gmail.com έγραψε:

tom

because I saw the post of didier with the image which does not
appear in "Running stations weewx" and like me it does not
work also; I said to myself. sorry to put me in the post.

Patrick

Le 17/01/2021 à 17:18, Tom Keffer a écrit :

Patrick, not sure what you are referring to. The discussion
above about providing a .png file is just a proposal. 


--
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/f343474c-00da-49e1-ab07-d9a17cc4ed9bn%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/c9be69fa-8cc5-e2e4-53d6-cadbf9a9c9bc%40gmail.com.


Re: \Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Δημήτρης Βήχος
#   This section is for information about the station.

[Station]

# Description of the station location
location = Kolxiko weather station

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

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

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be 
used.
station_type = FineOffsetUSB

# If you have a website, you may specify an URL
#station_url = https://kairos.moudania.com/kolxiko/

# 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

##
[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = true
Στις Κυριακή, 17 Ιανουαρίου 2021 στις 8:08:21 μ.μ. UTC+2, ο χρήστης Ξ 
έγραψε:

> Maybe ask in the Belchertown theme thread in the group?  For me it's 
> enough to change in weewx.conf: 
> [Station]
>
> # Description of the station location
> location = [Name of station in Greek/Bulgarian/Latin]
>
> # If you have a website, you may specify an URL
> station_url = [url of station]
>
> and 
> [[StationRegistry]]
> # To register this weather station with weewx, set this to true
> register_this_station = True
>
> I have no idea how the config of Belchertown is supposed to be done but I 
> think changing these three fields should be enough.
>

-- 
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/55d09e9c-e2cd-4f3c-af9d-2513fa326a1an%40googlegroups.com.


Re: \Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Ξ
Maybe ask in the Belchertown theme thread in the group?  For me it's enough 
to change in weewx.conf: 
[Station]

# Description of the station location
location = [Name of station in Greek/Bulgarian/Latin]

# If you have a website, you may specify an URL
station_url = [url of station]

and 
[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = True

I have no idea how the config of Belchertown is supposed to be done but I 
think changing these three fields should be enough.

-- 
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/9b0ad5cf-3a26-4977-a4c4-b07dd8e7n%40googlegroups.com.


Re: [weewx-user] Re: New internet provider - now ftp doesn't work

2021-01-17 Thread Rich Strle
My bad, the ftp in whew still doesn't work. The Access Point only has an 
IPv6 number listed, it doesn't have an IPv4 number listed. My website 
provider only allows 1 sftp account at the root level and I was trying to 
avoid using that.

On Sunday, January 17, 2021 at 11:41:18 AM UTC-6 Rich Strle wrote:

> I spoke with t-mobile again. They didn't say they did anything but all of 
> a sudden ftp started working. I will continue to monitor.
>
> On Sunday, January 17, 2021 at 10:50:19 AM UTC-6 galfert wrote:
>
>> Anyone care to google "T-Mobile FTP"  You'll see that this is an 
>> issue for everyone! My recommendation is to try to instead use SFTP.
>>
>>
>> On Sunday, January 17, 2021 at 11:41:25 AM UTC-5 Rich Strle wrote:
>>
>>> I did as instructed. Attached is the log file after I made the change. I 
>>> have a call into my provider to see if they are IPV6.
>>>
>>>
>>>
>>> On Sunday, January 17, 2021 at 10:17:33 AM UTC-6 tke...@gmail.com wrote:
>>>
 You definitely want passive mode (passive=1).

 Two things:

 1. By any chance, is your new provider using IPV6 (instead of 
 the traditional IPV4)?

 2. Set debug=2 in weewx.conf, then retry. This will put lots of 
 information in the log about what FTP is doing.

 -tk

 On Sun, Jan 17, 2021 at 7:46 AM Rich Strle  wrote:

> Thanks for your response David but that didn't fix my issue. 
>
> It was set at 1. I stopped the weewx process, set the ftp to 0, 
> restarted weewx and it did not help. I changed it back to 1.
>
> On Sunday, January 17, 2021 at 6:21:02 AM UTC-6 dav...@gmail.com 
> wrote:
>
>> Check out http://weewx.com/docs/usersguide.htm#config_FTP and look 
>> to add/adjust the passive setting in your weewx.conf config. 
>>
>> David 
>>
>> On Saturday, January 16, 2021 at 10:11:56 PM UTC-5 Rich Strle wrote:
>>
>>> I changed out my internet provider to t-mobile home internet service 
>>> and now I'm getting ftp errors. I tried connecting to the ftp from 
>>> another 
>>> computer and that worked. When my raspberry pi tries to connect I get 
>>> errors. This was working fine before I switched providers. Any ideas?
>>>
>>> Jan 16 21:01:25 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
>>> Attempting connection to www.cliffandbuster.com
>>> Jan 16 21:01:26 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
>>> Connected to www.cliffandbuster.com
>>> Jan 16 21:01:26 pi-weather weewx[30706] ERROR weeutil.ftpupload: 
>>> Failed uploading /var/www/html/weewx/seasons.css to server 
>>> www.cliffandbuster.com. Reason: '229 Extended Passive Mode Entered 
>>> (|||50207|)'
>>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine: 
>>> ftpgenerator: (1): caught exception '': 229 
>>> Extended Passive Mode Entered (|||50207|)
>>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>>    Traceback (most recent call last):
>>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>>  File "/usr/share/weewx/weewx/reportengine.py", line 331, 
>>> in run
>>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>>    n = ftp_data.run()
>>>
>>> -- 
> 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/ba3b1d83-b48b-4578-b7a5-85b3fe2e4fden%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/08999a97-41a4-4436-b59d-2f8793532fb6n%40googlegroups.com.


Re: [weewx-user] Re: Ubuntu 20.04 install, no HTML Files at all

2021-01-17 Thread Rob Cook
I wanted to reply back and let you all know that my WeeWx install is
working now, publishing to Wunderground. Thanks for the help!

On Fri, Jan 15, 2021 at 7:16 PM Tom Keffer  wrote:

> Report generation happens with every archive interval. With the Vantage
> stations, the interval is set by the hardware, not by WeeWX. Your station
> hardware has it set to 30 minutes.
>
> To change, either consult the directions that came with your console, or
> use the WeeWX utility wee_device with the --set-interval option
> . For
> example,
>
> *wee_device --set-interval=5*
>
> would change the interval to 5 minutes.
>
> -tk
>
> On Fri, Jan 15, 2021 at 4:09 PM Greg Reive  wrote:
>
>> You have to wait at least 5 minutes as that is the report generation time
>> default.
>>
>> On Sat, 16 Jan 2021 at 11:07, Rob Cook  wrote:
>>
>>> Aand now it's working? Was I simply being impatient? I now have
>>> files in /var/www/html/weewx and graphs. WTH?
>>>
>>> I guess I'm good, just need to enter in my Wunderground Info.
>>>
>>> On Fri, Jan 15, 2021 at 6:04 PM Rob Cook  wrote:
>>>
 First, thanks for all the help. I'll post logs below but I need to go
 feed my dogs and make dinner so if I don't get back to this tonight I'll
 pick it up in the morning.

 I've attached the entire syslog as well. Hopefully there's something in
 there.

 Jan 15 23:58:39 t630weewx systemd[1]: weewx.service: Succeeded.
 Jan 15 23:58:39 t630weewx systemd[1]: Stopped LSB: weewx weather system.
 Jan 15 23:58:39 t630weewx systemd[1]: Starting LSB: weewx weather
 system...
 Jan 15 23:58:39 t630weewx weewx[3329]:  * Starting weewx weather system
 weewx
 Jan 15 23:58:39 t630weewx weewx[3354] INFO __main__: Initializing weewx
 version 4.3.0
 Jan 15 23:58:39 t630weewx weewx[3354] INFO __main__: Using Python 3.8.5
 (default, Jul 28 2020, 12:59:40) #012[GCC 9.3.0]
 Jan 15 23:58:39 t630weewx weewx[3354] INFO __main__: Platform
 Linux-5.4.0-62-generic-x86_64-with-glibc2.29
 Jan 15 23:58:39 t630weewx weewx[3354] INFO __main__: Locale is 'C.UTF-8'
 Jan 15 23:58:39 t630weewx weewx[3354] INFO __main__: PID file is
 /var/run/weewx.pid
 Jan 15 23:58:39 t630weewx weewx[3357] INFO __main__: Using
 configuration file /etc/weewx/weewx.conf
 Jan 15 23:58:39 t630weewx weewx[3357] INFO __main__: Debug is 1
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG __main__: Initializing
 engine
 Jan 15 23:58:39 t630weewx weewx[3329]:...done.
 Jan 15 23:58:39 t630weewx systemd[1]: Started LSB: weewx weather system.
 Jan 15 23:58:39 t630weewx weewx[3357] INFO weewx.engine: Loading
 station type Vantage (weewx.drivers.vantage)
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.drivers.vantage:
 Driver version is 3.2.1
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.drivers.vantage:
 Option loop_request=1
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.drivers.vantage:
 Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.drivers.vantage:
 Gentle wake up of console successful
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.drivers.vantage:
 Hardware type is 16
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.drivers.vantage: ISS
 ID is 1
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.drivers.vantage:
 Hardware name: Vantage Pro2
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.engine: Loading
 service weewx.engine.StdTimeSynch
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.engine: Finished
 loading service weewx.engine.StdTimeSynch
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.engine: Loading
 service weewx.engine.StdConvert
 Jan 15 23:58:39 t630weewx weewx[3357] INFO weewx.engine: StdConvert
 target unit is 0x1
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.engine: Finished
 loading service weewx.engine.StdConvert
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.engine: Loading
 service weewx.engine.StdCalibrate
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.engine: Finished
 loading service weewx.engine.StdCalibrate
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.engine: Loading
 service weewx.engine.StdQC
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.engine: Finished
 loading service weewx.engine.StdQC
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.engine: Loading
 service weewx.wxservices.StdWXCalculate
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.manager: Daily
 summary version is 3.0
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.engine: Finished
 loading service weewx.wxservices.StdWXCalculate
 Jan 15 23:58:39 t630weewx weewx[3357] DEBUG weewx.engine: Loading
 service weewx.wxxtypes.StdWXXTypes
 Jan 15 23:58:39 t630weewx 

Re: [weewx-user] Re: New internet provider - now ftp doesn't work

2021-01-17 Thread Rich Strle
I spoke with t-mobile again. They didn't say they did anything but all of a 
sudden ftp started working. I will continue to monitor.

On Sunday, January 17, 2021 at 10:50:19 AM UTC-6 galfert wrote:

> Anyone care to google "T-Mobile FTP"  You'll see that this is an issue 
> for everyone! My recommendation is to try to instead use SFTP.
>
>
> On Sunday, January 17, 2021 at 11:41:25 AM UTC-5 Rich Strle wrote:
>
>> I did as instructed. Attached is the log file after I made the change. I 
>> have a call into my provider to see if they are IPV6.
>>
>>
>>
>> On Sunday, January 17, 2021 at 10:17:33 AM UTC-6 tke...@gmail.com wrote:
>>
>>> You definitely want passive mode (passive=1).
>>>
>>> Two things:
>>>
>>> 1. By any chance, is your new provider using IPV6 (instead of 
>>> the traditional IPV4)?
>>>
>>> 2. Set debug=2 in weewx.conf, then retry. This will put lots of 
>>> information in the log about what FTP is doing.
>>>
>>> -tk
>>>
>>> On Sun, Jan 17, 2021 at 7:46 AM Rich Strle  wrote:
>>>
 Thanks for your response David but that didn't fix my issue. 

 It was set at 1. I stopped the weewx process, set the ftp to 0, 
 restarted weewx and it did not help. I changed it back to 1.

 On Sunday, January 17, 2021 at 6:21:02 AM UTC-6 dav...@gmail.com wrote:

> Check out http://weewx.com/docs/usersguide.htm#config_FTP and look to 
> add/adjust the passive setting in your weewx.conf config. 
>
> David 
>
> On Saturday, January 16, 2021 at 10:11:56 PM UTC-5 Rich Strle wrote:
>
>> I changed out my internet provider to t-mobile home internet service 
>> and now I'm getting ftp errors. I tried connecting to the ftp from 
>> another 
>> computer and that worked. When my raspberry pi tries to connect I get 
>> errors. This was working fine before I switched providers. Any ideas?
>>
>> Jan 16 21:01:25 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
>> Attempting connection to www.cliffandbuster.com
>> Jan 16 21:01:26 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
>> Connected to www.cliffandbuster.com
>> Jan 16 21:01:26 pi-weather weewx[30706] ERROR weeutil.ftpupload: 
>> Failed uploading /var/www/html/weewx/seasons.css to server 
>> www.cliffandbuster.com. Reason: '229 Extended Passive Mode Entered 
>> (|||50207|)'
>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine: 
>> ftpgenerator: (1): caught exception '': 229 
>> Extended Passive Mode Entered (|||50207|)
>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>    Traceback (most recent call last):
>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/weewx/reportengine.py", line 331, in 
>> run
>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>    n = ftp_data.run()
>>
>> -- 
 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/ba3b1d83-b48b-4578-b7a5-85b3fe2e4fden%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/1bf4f912-9199-4d46-b140-f2708402f8d0n%40googlegroups.com.


Re: \Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Δημήτρης Βήχος
the url  https://kairos.moudania.com/kolxiko/

Στις Κυριακή, 17 Ιανουαρίου 2021 στις 7:36:51 μ.μ. UTC+2, ο χρήστης Ξ 
έγραψε:

> what's your weather station's URL?
>
> On Sunday, January 17, 2021 at 7:20:31 PM UTC+2 hobbyl...@gmail.com wrote:
>
>> all the greek stations are have english characters. i was cheking this. 
>> also changing the name of the station in weewx.conf and restarting weewx, 
>> my weather station dont yet appears on map.
>>
>> Στις Κυριακή, 17 Ιανουαρίου 2021 στις 6:32:44 μ.μ. UTC+2, ο χρήστης 
>> sali...@gmail.com έγραψε:
>>
>>> tom
>>>
>>> because I saw the post of didier with the image which does not appear in 
>>> "Running stations weewx" and like me it does not work also; I said to 
>>> myself. sorry to put me in the post.
>>>
>>> Patrick
>>> Le 17/01/2021 à 17:18, Tom Keffer a écrit :
>>>
>>> Patrick, not sure what you are referring to. The discussion above about 
>>> providing a .png file is just a proposal. 
>>>
>>>

-- 
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/ee4981c2-7bd7-4a72-af1e-a9bf41424bb3n%40googlegroups.com.


Re: \Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Ξ
what's your weather station's URL?

On Sunday, January 17, 2021 at 7:20:31 PM UTC+2 hobbyl...@gmail.com wrote:

> all the greek stations are have english characters. i was cheking this. 
> also changing the name of the station in weewx.conf and restarting weewx, 
> my weather station dont yet appears on map.
>
> Στις Κυριακή, 17 Ιανουαρίου 2021 στις 6:32:44 μ.μ. UTC+2, ο χρήστης 
> sali...@gmail.com έγραψε:
>
>> tom
>>
>> because I saw the post of didier with the image which does not appear in 
>> "Running stations weewx" and like me it does not work also; I said to 
>> myself. sorry to put me in the post.
>>
>> Patrick
>> Le 17/01/2021 à 17:18, Tom Keffer a écrit :
>>
>> Patrick, not sure what you are referring to. The discussion above about 
>> providing a .png file is just a proposal. 
>>
>>

-- 
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/f343474c-00da-49e1-ab07-d9a17cc4ed9bn%40googlegroups.com.


Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-17 Thread vince
On Saturday, January 9, 2021 at 8:02:51 PM UTC-8 garrya...@gmail.com wrote:

> My experience is that when I recreate an include file for Belchertown on 
> each archive cycle, as an extension to Belchertown or as a service, memory 
> usage increases with each cycle and eventually errors start.  
>

I continue to think you need to concentrate on what your code is doing and 
your os configuration.

   - If you disable Belchertown and 'enable' your custom code that 
   generates the include file, does memory grow ?
   - You also haven't told us what hardware you're on.  Is it a pi ?  What 
   os ?   What version ?
   - Your log says you're running python3.  Have you tried the same thing 
   on a python2 system ?
   - Can you duplicate the problem using just the Simulator driver and your 
   addition so we can try to replicate it ?


 

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


\Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Δημήτρης Βήχος
all the greek stations are have english characters. i was cheking this. 
also changing the name of the station in weewx.conf and restarting weewx, 
my weather station dont yet appears on map.

Στις Κυριακή, 17 Ιανουαρίου 2021 στις 6:32:44 μ.μ. UTC+2, ο χρήστης 
sali...@gmail.com έγραψε:

> tom
>
> because I saw the post of didier with the image which does not appear in 
> "Running stations weewx" and like me it does not work also; I said to 
> myself. sorry to put me in the post.
>
> Patrick
> Le 17/01/2021 à 17:18, Tom Keffer a écrit :
>
> Patrick, not sure what you are referring to. The discussion above about 
> providing a .png file is just a proposal. 
>
>

-- 
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/c718d74b-1db4-448e-beb7-d5a2632an%40googlegroups.com.


Re: [weewx-user] Re: New internet provider - now ftp doesn't work

2021-01-17 Thread galfert
Anyone care to google "T-Mobile FTP"  You'll see that this is an issue 
for everyone! My recommendation is to try to instead use SFTP.


On Sunday, January 17, 2021 at 11:41:25 AM UTC-5 Rich Strle wrote:

> I did as instructed. Attached is the log file after I made the change. I 
> have a call into my provider to see if they are IPV6.
>
>
>
> On Sunday, January 17, 2021 at 10:17:33 AM UTC-6 tke...@gmail.com wrote:
>
>> You definitely want passive mode (passive=1).
>>
>> Two things:
>>
>> 1. By any chance, is your new provider using IPV6 (instead of 
>> the traditional IPV4)?
>>
>> 2. Set debug=2 in weewx.conf, then retry. This will put lots of 
>> information in the log about what FTP is doing.
>>
>> -tk
>>
>> On Sun, Jan 17, 2021 at 7:46 AM Rich Strle  wrote:
>>
>>> Thanks for your response David but that didn't fix my issue. 
>>>
>>> It was set at 1. I stopped the weewx process, set the ftp to 0, 
>>> restarted weewx and it did not help. I changed it back to 1.
>>>
>>> On Sunday, January 17, 2021 at 6:21:02 AM UTC-6 dav...@gmail.com wrote:
>>>
 Check out http://weewx.com/docs/usersguide.htm#config_FTP and look to 
 add/adjust the passive setting in your weewx.conf config. 

 David 

 On Saturday, January 16, 2021 at 10:11:56 PM UTC-5 Rich Strle wrote:

> I changed out my internet provider to t-mobile home internet service 
> and now I'm getting ftp errors. I tried connecting to the ftp from 
> another 
> computer and that worked. When my raspberry pi tries to connect I get 
> errors. This was working fine before I switched providers. Any ideas?
>
> Jan 16 21:01:25 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
> Attempting connection to www.cliffandbuster.com
> Jan 16 21:01:26 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
> Connected to www.cliffandbuster.com
> Jan 16 21:01:26 pi-weather weewx[30706] ERROR weeutil.ftpupload: 
> Failed uploading /var/www/html/weewx/seasons.css to server 
> www.cliffandbuster.com. Reason: '229 Extended Passive Mode Entered 
> (|||50207|)'
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine: 
> ftpgenerator: (1): caught exception '': 229 
> Extended Passive Mode Entered (|||50207|)
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:  
>  Traceback (most recent call last):
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:  
>File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:  
>  n = ftp_data.run()
>
> -- 
>>> 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/ba3b1d83-b48b-4578-b7a5-85b3fe2e4fden%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/09a65e40-4345-476d-be29-84d6490d8199n%40googlegroups.com.


Re: [weewx-user] Re: New internet provider - now ftp doesn't work

2021-01-17 Thread Rich Strle
I did as instructed. Attached is the log file after I made the change. I 
have a call into my provider to see if they are IPV6.



On Sunday, January 17, 2021 at 10:17:33 AM UTC-6 tke...@gmail.com wrote:

> You definitely want passive mode (passive=1).
>
> Two things:
>
> 1. By any chance, is your new provider using IPV6 (instead of 
> the traditional IPV4)?
>
> 2. Set debug=2 in weewx.conf, then retry. This will put lots of 
> information in the log about what FTP is doing.
>
> -tk
>
> On Sun, Jan 17, 2021 at 7:46 AM Rich Strle  wrote:
>
>> Thanks for your response David but that didn't fix my issue. 
>>
>> It was set at 1. I stopped the weewx process, set the ftp to 0, restarted 
>> weewx and it did not help. I changed it back to 1.
>>
>> On Sunday, January 17, 2021 at 6:21:02 AM UTC-6 dav...@gmail.com wrote:
>>
>>> Check out http://weewx.com/docs/usersguide.htm#config_FTP and look to 
>>> add/adjust the passive setting in your weewx.conf config. 
>>>
>>> David 
>>>
>>> On Saturday, January 16, 2021 at 10:11:56 PM UTC-5 Rich Strle wrote:
>>>
 I changed out my internet provider to t-mobile home internet service 
 and now I'm getting ftp errors. I tried connecting to the ftp from another 
 computer and that worked. When my raspberry pi tries to connect I get 
 errors. This was working fine before I switched providers. Any ideas?

 Jan 16 21:01:25 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
 Attempting connection to www.cliffandbuster.com
 Jan 16 21:01:26 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
 Connected to www.cliffandbuster.com
 Jan 16 21:01:26 pi-weather weewx[30706] ERROR weeutil.ftpupload: Failed 
 uploading /var/www/html/weewx/seasons.css to server 
 www.cliffandbuster.com. Reason: '229 Extended Passive Mode Entered 
 (|||50207|)'
 Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine: 
 ftpgenerator: (1): caught exception '': 229 
 Extended Passive Mode Entered (|||50207|)
 Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:  
  Traceback (most recent call last):
 Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:  
File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
 Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:  
  n = ftp_data.run()

 -- 
>> 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/ba3b1d83-b48b-4578-b7a5-85b3fe2e4fden%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/215595b0-70e1-4e1d-b3cd-bc723304b81cn%40googlegroups.com.
Jan 17 10:21:56 pi-weather weewx[20816] INFO weewx.manager: Starting backfill 
of daily summaries
Jan 17 10:21:56 pi-weather weewx[20816] DEBUG weewx.manager: Daily summary 
version is 2
Jan 17 10:21:56 pi-weather weewx[20816] DEBUG weewx.drivers.vantage: Getting 
archive packets since 2021-01-17 10:20:00 CST (1610900400)
Jan 17 10:21:56 pi-weather weewx[20816] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Jan 17 10:21:56 pi-weather weewx[20816] DEBUG weewx.drivers.vantage: Retrieving 
0 page(s); starting index= 0
Jan 17 10:21:56 pi-weather weewx[20816] INFO weewx.engine: Starting main packet 
loop.
Jan 17 10:22:00 pi-weather weewx[20816] DEBUG weewx.drivers.vantage: Retry #0 
failed
Jan 17 10:22:00 pi-weather weewx[20816] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Jan 17 10:22:00 pi-weather weewx[20816] DEBUG weewx.drivers.vantage: Requesting 
200 LOOP packets.
Jan 17 10:22:00 pi-weather weewx[20816] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Jan 17 10:28:34 pi-weather weewx[20816] DEBUG weewx.drivers.vantage: Requesting 
200 LOOP packets.
Jan 17 10:28:34 pi-weather weewx[20816] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Jan 17 10:30:01 pi-weather CRON[20868]: (pi) CMD 
(/etc/cron.d/image-processing.sh)
Jan 17 10:30:03 pi-weather CRON[20867]: (CRON) info (No MTA installed, 
discarding output)
Jan 17 10:30:14 pi-weather weewx[20816] DEBUG weewx.drivers.vantage: Getting 
archive packets since 2021-01-17 10:20:00 CST (1610900400)
Jan 17 10:30:18 pi-weather weewx[20816] DEBUG weewx.drivers.vantage: Retry #0 
failed
Jan 17 10:30:18 pi-weather weewx[20816] DEBUG 

Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread salinois

tom

because I saw the post of didier with the image which does not appear in 
"Running stations weewx" and like me it does not work also; I said to 
myself. sorry to put me in the post.


Patrick

Le 17/01/2021 à 17:18, Tom Keffer a écrit :
Patrick, not sure what you are referring to. The discussion above 
about providing a .png file is just a proposal. 


--
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/7bcfdf4d-d3fe-2657-c347-8a800a09c800%40gmail.com.


Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Tom Keffer
Patrick, not sure what you are referring to. The discussion above about
providing a .png file is just a proposal.

On Sun, Jan 17, 2021 at 8:07 AM salinois  wrote:

> hi
>
> it is obligatory a file with extension .png ?
>
> patrick
> Le 17/01/2021 à 15:46, Tom Keffer a écrit :
>
> Entirely possible. I've created issue #3
>  to track.
>
> On Sun, Jan 17, 2021 at 4:38 AM Δημήτρης Βήχος 
> wrote:
>
>> i have my weather station since december 2020 , i had set registration to
>> true , after restarting weewx.but until now dont show in map. i wonder if
>> the problem is the greek characters  of station name. the rest greek
>> stations on map have english names. i had same issue in noaa reports and
>> solved that setting from ascii to utf 8 in skin conf. i dont know how to
>> solve this and i want to see my station in map.
>>
>> Στις Κυριακή, 11 Οκτωβρίου 2020 στις 9:18:04 μ.μ. UTC+3, ο χρήστης
>> tke...@gmail.com έγραψε:
>>
>>> It's something we've talked about.
>>>
>>> On Sun, Oct 11, 2020 at 10:50 AM Brent Fraser  wrote:
>>>
 How about allowing the station to optionally specify the image url?

 [station]
station_image=url = http://mydomain/station_image.png

 That should off-load the image creation.

 On Thursday, October 8, 2020 at 5:51:33 AM UTC-6 tke...@gmail.com
 wrote:

> Unfortunately, we have suspended preview snapshots. It was just taking
> too much memory, which would cause weewx.com to hang. Maybe later!
>
> On Thu, Oct 8, 2020 at 4:38 AM Didier Decoodt 
> wrote:
>
>> Hi Tom
>>
>> I have registered my station, it's OK but I have not a preview image
>> when I select the station
>> An idea?
>> [image: image.png]
>> Didier
>>
>> Le jeu. 8 oct. 2020 à 13:20, Tom Keffer  a écrit :
>>
>>> Why not just middle-button click?
>>>
>>> On Thu, Oct 8, 2020 at 12:29 AM Greg from Oz 
>>> wrote:
>>>
 Hi Tom,

 Is there a way to put right click on the url of the web cam links
 in the http://weewx.com/stations.html?

 The reason I ask is because when I click on a link to have a look
 at that web site and then press the back button it goes back to the 
 zoomed
 out view and then I have to move the map and zoom in all over again.

 If I could right click I could select open in a new tab and then I
 don't have to zoom and pan every time.

 I think this option was available ages ago.

 Thanks

 On Thursday, 8 October 2020 00:46:44 UTC+11, Tom Keffer wrote:
>
> Unfortunately, we have suspended preview snapshots. It was just
> taking too much memory, which would cause weewx.com to hang.
> Maybe later!
>
> On Tue, Oct 6, 2020 at 12:40 PM Vetti52  wrote:
>
>> being registered, but...
>> when opening the station on the map, there is no preview picture.
>> I am afraid, that for URLs containing windy.com a preview is not
>> available, right? I could establish another URL, which, however is 
>> only
>> available per IPv6 (IPv4 access is locked by a firewall). Would this
>> satisfy as source for a preview picture?
>>
>> Vetti52 schrieb am Dienstag, 6. Oktober 2020 um 10:49:19 UTC+2:
>>
>>> That's it!
>>> thanks
>>>
>>> tke...@gmail.com schrieb am Montag, 5. Oktober 2020 um 23:26:19
>>> UTC+2:
>>>
 I'm seeing an error on the server end: "station_url cannot
 contain single quotes".

 Not exactly sure what that means. Try using the URL
 https://www.windy.com/station/pws-f069b42a, without any quotes.

 -tk

 On Mon, Oct 5, 2020 at 12:21 PM Vetti52 
 wrote:

> just registered today, due to the advise in this thread.
> However there is no map entry. I get this log:
>
> Oct  5 21:00:30 raspbee weewx[10983] ERROR weewx.restx:
> StationRegistry: Failed to publish record 2020-10-05 21:00:00 CEST
> (1601924400): Failed upload after 3 tries
>
> I am using Weewx 4.1.1. My URL at windy.com actually works
> fine:
> https://www.windy.com/station/pws-f069b42a?54.088,10.258,8
> What is wrong?
>
> gjr80 schrieb am Sonntag, 4. Oktober 2020 um 22:57:52 UTC+2:
>
>> The only requirement of the URL is that it is unique in the
>> station registry. So I guess if you are making up an arbitrary 
>> URL be
>> creative. WU URLs are fine, they are used by numerous users in 
>> the station
>> registry.

Re: [weewx-user] Re: New internet provider - now ftp doesn't work

2021-01-17 Thread Tom Keffer
You definitely want passive mode (passive=1).

Two things:

1. By any chance, is your new provider using IPV6 (instead of
the traditional IPV4)?

2. Set debug=2 in weewx.conf, then retry. This will put lots of information
in the log about what FTP is doing.

-tk

On Sun, Jan 17, 2021 at 7:46 AM Rich Strle  wrote:

> Thanks for your response David but that didn't fix my issue.
>
> It was set at 1. I stopped the weewx process, set the ftp to 0, restarted
> weewx and it did not help. I changed it back to 1.
>
> On Sunday, January 17, 2021 at 6:21:02 AM UTC-6 dav...@gmail.com wrote:
>
>> Check out http://weewx.com/docs/usersguide.htm#config_FTP and look to
>> add/adjust the passive setting in your weewx.conf config.
>>
>> David
>>
>> On Saturday, January 16, 2021 at 10:11:56 PM UTC-5 Rich Strle wrote:
>>
>>> I changed out my internet provider to t-mobile home internet service and
>>> now I'm getting ftp errors. I tried connecting to the ftp from another
>>> computer and that worked. When my raspberry pi tries to connect I get
>>> errors. This was working fine before I switched providers. Any ideas?
>>>
>>> Jan 16 21:01:25 pi-weather weewx[30706] DEBUG weeutil.ftpupload:
>>> Attempting connection to www.cliffandbuster.com
>>> Jan 16 21:01:26 pi-weather weewx[30706] DEBUG weeutil.ftpupload:
>>> Connected to www.cliffandbuster.com
>>> Jan 16 21:01:26 pi-weather weewx[30706] ERROR weeutil.ftpupload: Failed
>>> uploading /var/www/html/weewx/seasons.css to server
>>> www.cliffandbuster.com. Reason: '229 Extended Passive Mode Entered
>>> (|||50207|)'
>>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>> ftpgenerator: (1): caught exception '': 229
>>> Extended Passive Mode Entered (|||50207|)
>>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>>    Traceback (most recent call last):
>>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>>  File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
>>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>>    n = ftp_data.run()
>>>
>>> --
> 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/ba3b1d83-b48b-4578-b7a5-85b3fe2e4fden%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/CAPq0zEBgem4NKDqfYg%3DU8nb%2BpCH_yXN9V6TGaz-wKOH_u-uDzw%40mail.gmail.com.


[weewx-user] Re: Need help: Bresser Weather 6in1 Pro WiFi and weewx Interceptor

2021-01-17 Thread galfert
It is not true that WU doesn't let you download your own data. The 
confusion is that you can't download data the old way with a .csv download 
file. The new way to download your own data is to use an API key that you 
can generate under your account setting. Then you must use this new API 
method to download your data. There is even a WeeWX extension to use this 
new method that has been created.

The reason for this change is that before anyone could download any amount 
of data and there were no controls to limit bandwidth usage. With the new 
API key method you are limited in the amount of bandwidth you can use on a 
monthly basis. This limits bandwidth abuse and it allows WU to better run 
their servers and reduce costs. If you are a business and you were 
previously downloading tons of data from WU, then those efforts have been 
blocked. You'll now have to purchase a commercial license in order to 
continue to download the amounts of data that you were before. You could 
say that a few bad apples with their abuse ruined the simplicity of the 
previous .csv download method. There were a few years where WU servers were 
hardly ever up. Sure things are not still perfect with WU but they 
certainly are a lot better than they were before these controls were 
implemented.




On Sunday, January 17, 2021 at 10:41:11 AM UTC-5 Steinwolf wrote:

> Hello,
> I need help with the Bresser 6in1 Pro Wifi. (sends data to 
> WeatherUnderground). Unfortunatelly it is the "stupid" not FINEOffset 
> version, so I have to use the interceptor, but I'm unable to get the 
> interceptor working. 
> I'm really unhappy with WU (now they even dont let you download your own 
> data!) and thats why I will use weewx. 
> By the way - this whole raspbian, linux,... thing is also new to me, so I 
> struggle with this all and can only do things I found on the internet. So 
> please, in case you write back, dont think I know anything - tell me like 
> I'm a litte kid or so ;)
>
> My setup: 
> Bresser Weather 6in1 Pro WiFi (the one with the display) (IP 
> 192.168.188.60- I guess, because the Bresser configuration site is here)
> Raspberry Pi3 (with weewx, interceptor and apache)
> Fritz.Box as router
>
> IPs: 
> Bresser Weather IP 192.168.188.60 (I guess, because the Bresser 
> configuration site is here) 
> Raspbi IP LAN 192.168.188.34, IP WLan  192.168.188.35 
> (raspbiweather.fritz.box also works) 
> FritzBox IP (as gateway?) 192.168.188.1
>
> The problem:
> I permanently get this error:
>
> pi@raspbiWeather:~ $ sudo /etc/init.d/weewx status
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx; generated)
>Active: active (exited) since Sun 2021-01-17 13:50:40 GMT; 3s ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 2410 ExecStart=/etc/init.d/weewx start (code=exited, 
> status=0/SUCCESS)
>
> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
> weewx.engine:   self._server = Consumer.TCPServer(address, 
> port, handler)
> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
> weewx.engine: File "/usr/share/weewx/user/interceptor.py", line 
> 584, in __init__
> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
> weewx.engine:   TCPServer.__init__(self, (address, int(port)), 
> handler)
> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
> weewx.engine: File "/usr/lib/python3.7/socketserver.py", line 
> 452, in __init__
> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
> weewx.engine:   self.server_bind()
> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
> weewx.engine: File "/usr/lib/python3.7/socketserver.py", line 
> 466, in server_bind
> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
> weewx.engine:   self.socket.bind(self.server_address)
> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
> weewx.engine:   OSError: [Errno 99] Die angeforderte Adresse kann 
> nicht zugewiesen werden
> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
> __main__: Unable to load driver: [Errno 99] Die angeforderte Adresse kann 
> nicht zugewiesen werden
> Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
> __main__:   Exiting...
>
> So that " Die angeforderte Adresse kann nicht zugewiesen werden" means in 
> english "The requested address cannot be assigned".
>
> I think that the IP address of the PWS is wrong or so?
> If I do (didn't know what the commands exactly do, but found this on 
> another help thread of some user) "sudo tcpdump -Anpl -s0 -w - -i eth0 src 
> 192.168.188.60 | stdbuf -oL strings -n8", I get (after a few seconds 
> waiting and Cntr+C) this:
>
> tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 
> 262144 bytes
> _services
> 3881D711F7A3-mysimplelink
> 3881D711F7A3-mysimplelink
> 

Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread salinois

hi

it is obligatory a file with extension .png ?

patrick

Le 17/01/2021 à 15:46, Tom Keffer a écrit :
Entirely possible. I've created issue #3 
 to track.


On Sun, Jan 17, 2021 at 4:38 AM Δημήτρης Βήχος > wrote:


i have my weather station since december 2020 , i had set
registration to true , after restarting weewx.but until now dont
show in map. i wonder if the problem is the greek characters  of
station name. the rest greek stations on map have english names. i
had same issue in noaa reports and solved that setting from ascii
to utf 8 in skin conf. i dont know how to solve this and i want to
see my station in map.

Στις Κυριακή, 11 Οκτωβρίου 2020 στις 9:18:04 μ.μ. UTC+3, ο χρήστης
tke...@gmail.com  έγραψε:

It's something we've talked about.

On Sun, Oct 11, 2020 at 10:50 AM Brent Fraser
 wrote:

How about allowing the station to optionally specify the
image url?

[station]
station_image=url = http://mydomain/station_image.png


That should off-load the image creation.

On Thursday, October 8, 2020 at 5:51:33 AM UTC-6
tke...@gmail.com wrote:

Unfortunately, we have suspended preview snapshots. It
was just taking too much memory, which would cause
weewx.com  to hang. Maybe later!

On Thu, Oct 8, 2020 at 4:38 AM Didier Decoodt
 wrote:

Hi Tom

I have registered my station, it's OK but I have
not a preview image when I select the station
An idea?
image.png
Didier

Le jeu. 8 oct. 2020 à 13:20, Tom Keffer
 a écrit :

Why not just middle-button click?

On Thu, Oct 8, 2020 at 12:29 AM Greg from Oz
 wrote:

Hi Tom,

Is there a way to put right click on the
url of the web cam links in the
http://weewx.com/stations.html
?

The reason I ask is because when I click
on a link to have a look at that web site
and then press the back button it goes
back to the zoomed out view and then I
have to move the map and zoom in all over
again.

If I could right click I could select open
in a new tab and then I don't have to zoom
and pan every time.

I think this option was available ages ago.

Thanks

On Thursday, 8 October 2020 00:46:44
UTC+11, Tom Keffer wrote:

Unfortunately, we have suspended
preview snapshots. It was just taking
too much memory, which would cause
weewx.com  to hang.
Maybe later!

On Tue, Oct 6, 2020 at 12:40 PM
Vetti52  wrote:

being registered, but...
when opening the station on the
map, there is no preview picture.
I am afraid, that for URLs
containing windy.com
 a preview is
not available, right? I could
establish another URL, which,
however is only available per IPv6
(IPv4 access is locked by a
firewall). Would this satisfy as
source for a preview picture?

Vetti52 schrieb am Dienstag, 6.
Oktober 2020 um 10:49:19 UTC+2:

That's it!
thanks

tke...@gmail.com schrieb am
Montag, 5. Oktober 2020 um
23:26:19 UTC+2:

I'm seeing an error on the
   

[weewx-user] Re: New internet provider - now ftp doesn't work

2021-01-17 Thread Rich Strle
Thanks for your response David but that didn't fix my issue. 

It was set at 1. I stopped the weewx process, set the ftp to 0, restarted 
weewx and it did not help. I changed it back to 1.

On Sunday, January 17, 2021 at 6:21:02 AM UTC-6 dav...@gmail.com wrote:

> Check out http://weewx.com/docs/usersguide.htm#config_FTP and look to 
> add/adjust the passive setting in your weewx.conf config. 
>
> David 
>
> On Saturday, January 16, 2021 at 10:11:56 PM UTC-5 Rich Strle wrote:
>
>> I changed out my internet provider to t-mobile home internet service and 
>> now I'm getting ftp errors. I tried connecting to the ftp from another 
>> computer and that worked. When my raspberry pi tries to connect I get 
>> errors. This was working fine before I switched providers. Any ideas?
>>
>> Jan 16 21:01:25 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
>> Attempting connection to www.cliffandbuster.com
>> Jan 16 21:01:26 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
>> Connected to www.cliffandbuster.com
>> Jan 16 21:01:26 pi-weather weewx[30706] ERROR weeutil.ftpupload: Failed 
>> uploading /var/www/html/weewx/seasons.css to server 
>> www.cliffandbuster.com. Reason: '229 Extended Passive Mode Entered 
>> (|||50207|)'
>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine: 
>> ftpgenerator: (1): caught exception '': 229 
>> Extended Passive Mode Entered (|||50207|)
>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>    Traceback (most recent call last):
>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
>> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>>    n = ftp_data.run()
>>
>>

-- 
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/ba3b1d83-b48b-4578-b7a5-85b3fe2e4fden%40googlegroups.com.


[weewx-user] Need help: Bresser Weather 6in1 Pro WiFi and weewx Interceptor

2021-01-17 Thread Steinwolf
Hello,
I need help with the Bresser 6in1 Pro Wifi. (sends data to 
WeatherUnderground). Unfortunatelly it is the "stupid" not FINEOffset 
version, so I have to use the interceptor, but I'm unable to get the 
interceptor working. 
I'm really unhappy with WU (now they even dont let you download your own 
data!) and thats why I will use weewx. 
By the way - this whole raspbian, linux,... thing is also new to me, so I 
struggle with this all and can only do things I found on the internet. So 
please, in case you write back, dont think I know anything - tell me like 
I'm a litte kid or so ;)

My setup: 
Bresser Weather 6in1 Pro WiFi (the one with the display) (IP 
192.168.188.60- I guess, because the Bresser configuration site is here)
Raspberry Pi3 (with weewx, interceptor and apache)
Fritz.Box as router

IPs: 
Bresser Weather IP 192.168.188.60 (I guess, because the Bresser 
configuration site is here) 
Raspbi IP LAN 192.168.188.34, IP WLan  192.168.188.35 
(raspbiweather.fritz.box also works) 
FritzBox IP (as gateway?) 192.168.188.1

The problem:
I permanently get this error:

pi@raspbiWeather:~ $ sudo /etc/init.d/weewx status
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx; generated)
   Active: active (exited) since Sun 2021-01-17 13:50:40 GMT; 3s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 2410 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)

Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
weewx.engine:   self._server = Consumer.TCPServer(address, 
port, handler)
Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
weewx.engine: File "/usr/share/weewx/user/interceptor.py", line 
584, in __init__
Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
weewx.engine:   TCPServer.__init__(self, (address, int(port)), 
handler)
Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
weewx.engine: File "/usr/lib/python3.7/socketserver.py", line 
452, in __init__
Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
weewx.engine:   self.server_bind()
Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
weewx.engine: File "/usr/lib/python3.7/socketserver.py", line 
466, in server_bind
Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
weewx.engine:   self.socket.bind(self.server_address)
Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
weewx.engine:   OSError: [Errno 99] Die angeforderte Adresse kann 
nicht zugewiesen werden
Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL __main__: 
Unable to load driver: [Errno 99] Die angeforderte Adresse kann nicht 
zugewiesen werden
Jän 17 13:50:40 raspbiWeather python3[2426]: weewx[2426] CRITICAL 
__main__:   Exiting...

So that " Die angeforderte Adresse kann nicht zugewiesen werden" means in 
english "The requested address cannot be assigned".

I think that the IP address of the PWS is wrong or so?
If I do (didn't know what the commands exactly do, but found this on 
another help thread of some user) "sudo tcpdump -Anpl -s0 -w - -i eth0 src 
192.168.188.60 | stdbuf -oL strings -n8", I get (after a few seconds 
waiting and Cntr+C) this:

tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 
262144 bytes
_services
3881D711F7A3-mysimplelink
3881D711F7A3-mysimplelink
3881D711F7A3-mysimplelink
^C2 packets captured
2 packets received by filter
0 packets dropped by kernel

" 3881D711F7A3-mysimplelink" is the Bresser PWS on the Fritzbox. Pakets 
received are sometimes more, sometimes less. I guess that the PWS sends 
every 10 secs or so, and thats why. 

So is this correct? Than why it doesn't work? 

In the weewx config I have:
station_type = Interceptor
##

[Interceptor]
# This section is for the network traffic interceptor driver.

# The driver to use:
driver = user.interceptor
#device_type = lw30x
device_type = wu-client
#mode = sniff
address = 192.168.188.60
#port = 80

##

Port is with "#" because I dont know the port and the the query above only 
works without " and port 80".

Please be so kind and help.
BR,
Steinwolf

-- 
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/839f388e-4b53-4233-87b4-63019e79395cn%40googlegroups.com.


Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Tom Keffer
Got it.

Yes, it looks like the map handles UTF-8 characters just fine. Thanks.

On Sun, Jan 17, 2021 at 7:03 AM Ξ  wrote:

> You can also see in Troyan, Bulgaria (northeast of Sofia) a station with a
> Bulgarian name: *СУ „Св. Кл. Охридски“ Троян*
>
> On Sunday, January 17, 2021 at 4:56:39 PM UTC+2 tke...@gmail.com wrote:
>
>> I don't know where Sofia is, but all the Greek station names I'm seeing
>> on the map are using ASCII characters. Clicking around the globe, I've
>> found a few that use Latin-1 characters, but none that use more than one
>> byte.
>>
>> On Sun, Jan 17, 2021 at 6:50 AM Ξ  wrote:
>>
>>> I've just changed my station name to Greek (Ντόλνι Οκόλ) and it's on the
>>> map, look just south of Sofia. What's your station's URL?
>>>
>>> On Sunday, January 17, 2021 at 2:38:05 PM UTC+2 hobbyl...@gmail.com
>>> wrote:
>>>
 i have my weather station since december 2020 , i had set registration
 to true , after restarting weewx.but until now dont show in map. i wonder
 if the problem is the greek characters  of station name. the rest greek
 stations on map have english names. i had same issue in noaa reports and
 solved that setting from ascii to utf 8 in skin conf. i dont know how to
 solve this and i want to see my station in map.

 Στις Κυριακή, 11 Οκτωβρίου 2020 στις 9:18:04 μ.μ. UTC+3, ο χρήστης
 tke...@gmail.com έγραψε:

> It's something we've talked about.
>
> On Sun, Oct 11, 2020 at 10:50 AM Brent Fraser 
> wrote:
>
>> How about allowing the station to optionally specify the image url?
>>
>> [station]
>>station_image=url = http://mydomain/station_image.png
>>
>> That should off-load the image creation.
>>
>> On Thursday, October 8, 2020 at 5:51:33 AM UTC-6 tke...@gmail.com
>> wrote:
>>
>>> Unfortunately, we have suspended preview snapshots. It was just
>>> taking too much memory, which would cause weewx.com to hang. Maybe
>>> later!
>>>
>>> On Thu, Oct 8, 2020 at 4:38 AM Didier Decoodt 
>>> wrote:
>>>
 Hi Tom

 I have registered my station, it's OK but I have not a preview
 image when I select the station
 An idea?
 [image: image.png]
 Didier

 Le jeu. 8 oct. 2020 à 13:20, Tom Keffer  a
 écrit :

> Why not just middle-button click?
>
> On Thu, Oct 8, 2020 at 12:29 AM Greg from Oz 
> wrote:
>
>> Hi Tom,
>>
>> Is there a way to put right click on the url of the web cam links
>> in the http://weewx.com/stations.html?
>>
>> The reason I ask is because when I click on a link to have a look
>> at that web site and then press the back button it goes back to the 
>> zoomed
>> out view and then I have to move the map and zoom in all over again.
>>
>> If I could right click I could select open in a new tab and then
>> I don't have to zoom and pan every time.
>>
>> I think this option was available ages ago.
>>
>> Thanks
>>
>> On Thursday, 8 October 2020 00:46:44 UTC+11, Tom Keffer wrote:
>>>
>>> Unfortunately, we have suspended preview snapshots. It was just
>>> taking too much memory, which would cause weewx.com to hang.
>>> Maybe later!
>>>
>>> On Tue, Oct 6, 2020 at 12:40 PM Vetti52 
>>> wrote:
>>>
 being registered, but...
 when opening the station on the map, there is no preview
 picture. I am afraid, that for URLs containing windy.com a
 preview is not available, right? I could establish another URL, 
 which,
 however is only available per IPv6 (IPv4 access is locked by a 
 firewall).
 Would this satisfy as source for a preview picture?

 Vetti52 schrieb am Dienstag, 6. Oktober 2020 um 10:49:19 UTC+2:

> That's it!
> thanks
>
> tke...@gmail.com schrieb am Montag, 5. Oktober 2020 um
> 23:26:19 UTC+2:
>
>> I'm seeing an error on the server end: "station_url cannot
>> contain single quotes".
>>
>> Not exactly sure what that means. Try using the URL
>> https://www.windy.com/station/pws-f069b42a, without any
>> quotes.
>>
>> -tk
>>
>> On Mon, Oct 5, 2020 at 12:21 PM Vetti52 
>> wrote:
>>
>>> just registered today, due to the advise in this thread.
>>> However there is no map entry. I get this log:
>>>
>>> Oct  5 21:00:30 raspbee weewx[10983] ERROR weewx.restx:
>>> StationRegistry: Failed to publish record 2020-10-05 21:00:00 
>>> 

[weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-17 Thread galfert
This thread started with the discussion being around the Ambient WS-2902 
and that is totally different despite looking like the same unit. This is 
because Ambient is the only Fine Offset clone reseller that changes the 
firmware and they limit options. The Ambient version does not let you 
upload to custom server address. The confusion here is that my response was 
because I thought you had and Ambient branded unit. Since you don't have an 
Ambient branded unit you do have the option to send to a custom server 
using both WU and Ecowitt protocols. The WU protocol is limited and only 
sends the basic set of sensors. The Ecowitt protocol allows you to send a 
lot more optional sensors like PM2.5, soil moisture, extra temp/hum 
sensorsetc. But still you'll have to configure the Interceptor driver 
to match the protocol type that you set in you WH2900C for uploading to 
your custom server. 

The GW1000 though is still a more elegant and newer solution. 

* The newest Ambient WS-2902 firmware finally after many years does gain 
the ability to send to a custom serverBUT it is not WU protocol and it 
is not Ecowitt protocolit is Ambientweather.net protocol and enough 
significant differences that the Interceptor driver will not work. This 
newest firmware is not yet officially supported by Ambient. They haven't 
yet release the updated awnet mobile app to enable turning and configuring 
this option. All of these complexities and changing nature of the situation 
makes it difficult to explain the situation to cover all possible 
scenarios...what model you have and whom it is from and what firmware 
version you are running and all the different supporting protocols that are 
possible. 

Using pfsense to capture and forward packets is really unnecessary for 
anyone with a non-Ambient WH2900Cas it has a built in simple to 
configure "Customized" server upload feature.



On Sunday, January 17, 2021 at 7:32:03 AM UTC-5 sjr4...@gmail.com wrote:

> For the record, mine is a Chinese Mi-Sol WH2900C. It is a copy of the Fine 
> Offset WH2900 or the Ecowitt WS2950. Indeed, the unit requires a connection 
> to Ecowitt to set the Time/Date and automatically downloaded the 
> EasyWeather 1.56 firmware update from Ecowitt. 
>
> I haven't got the outdoor setup done yet, while i play with getting the 
> unit up and running. but Ecowitt, shows my indoor temperature and pressure 
> on the home page. I use pfsense so can run a packet capture if it helps. 
> Since editing the weewx.conf file, i am getting the utf-8 problem. I guess 
> this is related to me using European accented characters in my editors 
> which are UTF-8. So that leaves me with two questions;
> 1) how to have it accept the UTF-8 characters
> 2) you mentioned not getting all the sensor data, unless using Ecowitt. In 
> view, that i am. Can you tell me what additional parameters i need in the 
> config file please.
>
>
>
> On Sunday, January 17, 2021 at 9:21:33 AM UTC+1 S R wrote:
>
>> almost there, but now 
>>
>> /usr/local/share/weewx # ./bin/wee_reports
>>
>> Traceback (most recent call last):
>>   File "./bin/wee_reports", line 103, in 
>> main()
>>   File "./bin/wee_reports", line 51, in main
>> config_path, config_dict = weecfg.read_config(options.config_path, 
>> args)
>>   File "/usr/local/share/weewx/bin/weecfg/__init__.py", line 180, in 
>> read_config
>> default_encoding='utf-8')
>>   File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1229, 
>> in __init__
>> self._load(infile, configspec)
>>   File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1287, 
>> in _load
>> content = self._handle_bom(content)
>>
>> On Saturday, January 16, 2021 at 11:30:28 PM UTC+1 galfert wrote:
>>
>>> Yes the best method when using the Interceptor is to use the Customized 
>>> server settings. The path doesn't matter. But in some firmware versions it 
>>> just couldn't be left blank or it wouldn't send. So just put in index.php? 
>>> for the path.
>>>
>>>
>>> On Saturday, January 16, 2021 at 3:49:17 PM UTC-5 sjr4...@gmail.com 
>>> wrote:
>>>
 OK. So i am homing in a little closer here. 
 I have configured the console to wunderground and it is working. 

 Now i need to adjust weewx.conf with the following, but as the weewx 
 server is on a different subnet, i will need to use listen mode. 

 [Interceptor]
 driver = user.interceptor
 device_type = wu-client 

 If i understand, i can point the console with a custom config to my 
 server, and then publish from my server to wunderground right?

 if i do that, what will the path on weewx for the console? 

 host:  weewx.local.lan
 Path: ?
 ID:   xx
 Key:xx

 also, on a side note. I can't find the log in freebsd. 

 On Saturday, January 16, 2021 at 9:17:02 PM UTC+1 galfert wrote:

> What I understand you are saying is that you have a WH2910 

Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Ξ
You can also see in Troyan, Bulgaria (northeast of Sofia) a station with a 
Bulgarian name: *СУ „Св. Кл. Охридски“ Троян*

On Sunday, January 17, 2021 at 4:56:39 PM UTC+2 tke...@gmail.com wrote:

> I don't know where Sofia is, but all the Greek station names I'm seeing on 
> the map are using ASCII characters. Clicking around the globe, I've found a 
> few that use Latin-1 characters, but none that use more than one byte.
>
> On Sun, Jan 17, 2021 at 6:50 AM Ξ  wrote:
>
>> I've just changed my station name to Greek (Ντόλνι Οκόλ) and it's on the 
>> map, look just south of Sofia. What's your station's URL?
>>
>> On Sunday, January 17, 2021 at 2:38:05 PM UTC+2 hobbyl...@gmail.com 
>> wrote:
>>
>>> i have my weather station since december 2020 , i had set registration 
>>> to true , after restarting weewx.but until now dont show in map. i wonder 
>>> if the problem is the greek characters  of station name. the rest greek 
>>> stations on map have english names. i had same issue in noaa reports and 
>>> solved that setting from ascii to utf 8 in skin conf. i dont know how to 
>>> solve this and i want to see my station in map. 
>>>
>>> Στις Κυριακή, 11 Οκτωβρίου 2020 στις 9:18:04 μ.μ. UTC+3, ο χρήστης 
>>> tke...@gmail.com έγραψε:
>>>
 It's something we've talked about.

 On Sun, Oct 11, 2020 at 10:50 AM Brent Fraser  wrote:

> How about allowing the station to optionally specify the image url?
>
> [station]
>station_image=url = http://mydomain/station_image.png
>
> That should off-load the image creation.
>
> On Thursday, October 8, 2020 at 5:51:33 AM UTC-6 tke...@gmail.com 
> wrote:
>
>> Unfortunately, we have suspended preview snapshots. It was just 
>> taking too much memory, which would cause weewx.com to hang. Maybe 
>> later!
>>
>> On Thu, Oct 8, 2020 at 4:38 AM Didier Decoodt  
>> wrote:
>>
>>> Hi Tom
>>>
>>> I have registered my station, it's OK but I have not a preview image 
>>> when I select the station
>>> An idea?
>>> [image: image.png]
>>> Didier
>>>
>>> Le jeu. 8 oct. 2020 à 13:20, Tom Keffer  a écrit :
>>>
 Why not just middle-button click?

 On Thu, Oct 8, 2020 at 12:29 AM Greg from Oz  
 wrote:

> Hi Tom,
>
> Is there a way to put right click on the url of the web cam links 
> in the http://weewx.com/stations.html?
>
> The reason I ask is because when I click on a link to have a look 
> at that web site and then press the back button it goes back to the 
> zoomed 
> out view and then I have to move the map and zoom in all over again.
>
> If I could right click I could select open in a new tab and then I 
> don't have to zoom and pan every time.
>
> I think this option was available ages ago.
>
> Thanks
>
> On Thursday, 8 October 2020 00:46:44 UTC+11, Tom Keffer wrote:
>>
>> Unfortunately, we have suspended preview snapshots. It was just 
>> taking too much memory, which would cause weewx.com to hang. 
>> Maybe later!
>>
>> On Tue, Oct 6, 2020 at 12:40 PM Vetti52  wrote:
>>
>>> being registered, but...
>>> when opening the station on the map, there is no preview 
>>> picture. I am afraid, that for URLs containing windy.com a 
>>> preview is not available, right? I could establish another URL, 
>>> which, 
>>> however is only available per IPv6 (IPv4 access is locked by a 
>>> firewall). 
>>> Would this satisfy as source for a preview picture?
>>>
>>> Vetti52 schrieb am Dienstag, 6. Oktober 2020 um 10:49:19 UTC+2:
>>>
 That's it!
 thanks

 tke...@gmail.com schrieb am Montag, 5. Oktober 2020 um 
 23:26:19 UTC+2:

> I'm seeing an error on the server end: "station_url cannot 
> contain single quotes".
>
> Not exactly sure what that means. Try using the URL 
> https://www.windy.com/station/pws-f069b42a, without any 
> quotes.
>
> -tk
>
> On Mon, Oct 5, 2020 at 12:21 PM Vetti52  
> wrote:
>
>> just registered today, due to the advise in this thread. 
>> However there is no map entry. I get this log:
>>
>> Oct  5 21:00:30 raspbee weewx[10983] ERROR weewx.restx: 
>> StationRegistry: Failed to publish record 2020-10-05 21:00:00 
>> CEST 
>> (1601924400): Failed upload after 3 tries
>>
>> I am using Weewx 4.1.1. My URL at windy.com actually works 
>> fine: 
>> 

Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Ξ
Sofia Bulgaria, just north of Greece, Tom. The station appears between 
Sofia and Samokov on the map.

On Sunday, January 17, 2021 at 4:56:39 PM UTC+2 tke...@gmail.com wrote:

> I don't know where Sofia is, but all the Greek station names I'm seeing on 
> the map are using ASCII characters. Clicking around the globe, I've found a 
> few that use Latin-1 characters, but none that use more than one byte.
>
> On Sun, Jan 17, 2021 at 6:50 AM Ξ  wrote:
>
>> I've just changed my station name to Greek (Ντόλνι Οκόλ) and it's on the 
>> map, look just south of Sofia. What's your station's URL?
>>
>> On Sunday, January 17, 2021 at 2:38:05 PM UTC+2 hobbyl...@gmail.com 
>> wrote:
>>
>>> i have my weather station since december 2020 , i had set registration 
>>> to true , after restarting weewx.but until now dont show in map. i wonder 
>>> if the problem is the greek characters  of station name. the rest greek 
>>> stations on map have english names. i had same issue in noaa reports and 
>>> solved that setting from ascii to utf 8 in skin conf. i dont know how to 
>>> solve this and i want to see my station in map. 
>>>
>>> Στις Κυριακή, 11 Οκτωβρίου 2020 στις 9:18:04 μ.μ. UTC+3, ο χρήστης 
>>> tke...@gmail.com έγραψε:
>>>
 It's something we've talked about.

 On Sun, Oct 11, 2020 at 10:50 AM Brent Fraser  wrote:

> How about allowing the station to optionally specify the image url?
>
> [station]
>station_image=url = http://mydomain/station_image.png
>
> That should off-load the image creation.
>
> On Thursday, October 8, 2020 at 5:51:33 AM UTC-6 tke...@gmail.com 
> wrote:
>
>> Unfortunately, we have suspended preview snapshots. It was just 
>> taking too much memory, which would cause weewx.com to hang. Maybe 
>> later!
>>
>> On Thu, Oct 8, 2020 at 4:38 AM Didier Decoodt  
>> wrote:
>>
>>> Hi Tom
>>>
>>> I have registered my station, it's OK but I have not a preview image 
>>> when I select the station
>>> An idea?
>>> [image: image.png]
>>> Didier
>>>
>>> Le jeu. 8 oct. 2020 à 13:20, Tom Keffer  a écrit :
>>>
 Why not just middle-button click?

 On Thu, Oct 8, 2020 at 12:29 AM Greg from Oz  
 wrote:

> Hi Tom,
>
> Is there a way to put right click on the url of the web cam links 
> in the http://weewx.com/stations.html?
>
> The reason I ask is because when I click on a link to have a look 
> at that web site and then press the back button it goes back to the 
> zoomed 
> out view and then I have to move the map and zoom in all over again.
>
> If I could right click I could select open in a new tab and then I 
> don't have to zoom and pan every time.
>
> I think this option was available ages ago.
>
> Thanks
>
> On Thursday, 8 October 2020 00:46:44 UTC+11, Tom Keffer wrote:
>>
>> Unfortunately, we have suspended preview snapshots. It was just 
>> taking too much memory, which would cause weewx.com to hang. 
>> Maybe later!
>>
>> On Tue, Oct 6, 2020 at 12:40 PM Vetti52  wrote:
>>
>>> being registered, but...
>>> when opening the station on the map, there is no preview 
>>> picture. I am afraid, that for URLs containing windy.com a 
>>> preview is not available, right? I could establish another URL, 
>>> which, 
>>> however is only available per IPv6 (IPv4 access is locked by a 
>>> firewall). 
>>> Would this satisfy as source for a preview picture?
>>>
>>> Vetti52 schrieb am Dienstag, 6. Oktober 2020 um 10:49:19 UTC+2:
>>>
 That's it!
 thanks

 tke...@gmail.com schrieb am Montag, 5. Oktober 2020 um 
 23:26:19 UTC+2:

> I'm seeing an error on the server end: "station_url cannot 
> contain single quotes".
>
> Not exactly sure what that means. Try using the URL 
> https://www.windy.com/station/pws-f069b42a, without any 
> quotes.
>
> -tk
>
> On Mon, Oct 5, 2020 at 12:21 PM Vetti52  
> wrote:
>
>> just registered today, due to the advise in this thread. 
>> However there is no map entry. I get this log:
>>
>> Oct  5 21:00:30 raspbee weewx[10983] ERROR weewx.restx: 
>> StationRegistry: Failed to publish record 2020-10-05 21:00:00 
>> CEST 
>> (1601924400): Failed upload after 3 tries
>>
>> I am using Weewx 4.1.1. My URL at windy.com actually works 
>> fine: 
>> https://www.windy.com/station/pws-f069b42a?54.088,10.258,8
>> 

Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Ξ
Alternatively you can try temporarily change the station name to Latin 
characters and see if it appears, my station's name has always been in 
Latin and only now I changed it to Greek, this way we can see if charset 
matters for initial registration.

On Sunday, January 17, 2021 at 2:38:05 PM UTC+2 hobbyl...@gmail.com wrote:

> i have my weather station since december 2020 , i had set registration to 
> true , after restarting weewx.but until now dont show in map. i wonder if 
> the problem is the greek characters  of station name. the rest greek 
> stations on map have english names. i had same issue in noaa reports and 
> solved that setting from ascii to utf 8 in skin conf. i dont know how to 
> solve this and i want to see my station in map. 
>
> Στις Κυριακή, 11 Οκτωβρίου 2020 στις 9:18:04 μ.μ. UTC+3, ο χρήστης 
> tke...@gmail.com έγραψε:
>
>> It's something we've talked about.
>>
>> On Sun, Oct 11, 2020 at 10:50 AM Brent Fraser  wrote:
>>
>>> How about allowing the station to optionally specify the image url?
>>>
>>> [station]
>>>station_image=url = http://mydomain/station_image.png
>>>
>>> That should off-load the image creation.
>>>
>>> On Thursday, October 8, 2020 at 5:51:33 AM UTC-6 tke...@gmail.com wrote:
>>>
 Unfortunately, we have suspended preview snapshots. It was just taking 
 too much memory, which would cause weewx.com to hang. Maybe later!

 On Thu, Oct 8, 2020 at 4:38 AM Didier Decoodt  
 wrote:

> Hi Tom
>
> I have registered my station, it's OK but I have not a preview image 
> when I select the station
> An idea?
> [image: image.png]
> Didier
>
> Le jeu. 8 oct. 2020 à 13:20, Tom Keffer  a écrit :
>
>> Why not just middle-button click?
>>
>> On Thu, Oct 8, 2020 at 12:29 AM Greg from Oz  
>> wrote:
>>
>>> Hi Tom,
>>>
>>> Is there a way to put right click on the url of the web cam links in 
>>> the http://weewx.com/stations.html?
>>>
>>> The reason I ask is because when I click on a link to have a look at 
>>> that web site and then press the back button it goes back to the zoomed 
>>> out 
>>> view and then I have to move the map and zoom in all over again.
>>>
>>> If I could right click I could select open in a new tab and then I 
>>> don't have to zoom and pan every time.
>>>
>>> I think this option was available ages ago.
>>>
>>> Thanks
>>>
>>> On Thursday, 8 October 2020 00:46:44 UTC+11, Tom Keffer wrote:

 Unfortunately, we have suspended preview snapshots. It was just 
 taking too much memory, which would cause weewx.com to hang. Maybe 
 later!

 On Tue, Oct 6, 2020 at 12:40 PM Vetti52  wrote:

> being registered, but...
> when opening the station on the map, there is no preview picture. 
> I am afraid, that for URLs containing windy.com a preview is not 
> available, right? I could establish another URL, which, however is 
> only 
> available per IPv6 (IPv4 access is locked by a firewall). Would this 
> satisfy as source for a preview picture?
>
> Vetti52 schrieb am Dienstag, 6. Oktober 2020 um 10:49:19 UTC+2:
>
>> That's it!
>> thanks
>>
>> tke...@gmail.com schrieb am Montag, 5. Oktober 2020 um 23:26:19 
>> UTC+2:
>>
>>> I'm seeing an error on the server end: "station_url cannot 
>>> contain single quotes".
>>>
>>> Not exactly sure what that means. Try using the URL 
>>> https://www.windy.com/station/pws-f069b42a, without any quotes.
>>>
>>> -tk
>>>
>>> On Mon, Oct 5, 2020 at 12:21 PM Vetti52  
>>> wrote:
>>>
 just registered today, due to the advise in this thread. 
 However there is no map entry. I get this log:

 Oct  5 21:00:30 raspbee weewx[10983] ERROR weewx.restx: 
 StationRegistry: Failed to publish record 2020-10-05 21:00:00 CEST 
 (1601924400): Failed upload after 3 tries

 I am using Weewx 4.1.1. My URL at windy.com actually works 
 fine: 
 https://www.windy.com/station/pws-f069b42a?54.088,10.258,8
 What is wrong?  

 gjr80 schrieb am Sonntag, 4. Oktober 2020 um 22:57:52 UTC+2:

> The only requirement of the URL is that it is unique in the 
> station registry. So I guess if you are making up an arbitrary 
> URL be 
> creative. WU URLs are fine, they are used by numerous users in 
> the station 
> registry.
>
> Gary
>
> On Monday, 5 October 2020 at 06:11:06 UTC+10 maf@gmail.com 
> wrote:
>
>> Tom:
>>

Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Tom Keffer
I don't know where Sofia is, but all the Greek station names I'm seeing on
the map are using ASCII characters. Clicking around the globe, I've found a
few that use Latin-1 characters, but none that use more than one byte.

On Sun, Jan 17, 2021 at 6:50 AM Ξ  wrote:

> I've just changed my station name to Greek (Ντόλνι Οκόλ) and it's on the
> map, look just south of Sofia. What's your station's URL?
>
> On Sunday, January 17, 2021 at 2:38:05 PM UTC+2 hobbyl...@gmail.com wrote:
>
>> i have my weather station since december 2020 , i had set registration to
>> true , after restarting weewx.but until now dont show in map. i wonder if
>> the problem is the greek characters  of station name. the rest greek
>> stations on map have english names. i had same issue in noaa reports and
>> solved that setting from ascii to utf 8 in skin conf. i dont know how to
>> solve this and i want to see my station in map.
>>
>> Στις Κυριακή, 11 Οκτωβρίου 2020 στις 9:18:04 μ.μ. UTC+3, ο χρήστης
>> tke...@gmail.com έγραψε:
>>
>>> It's something we've talked about.
>>>
>>> On Sun, Oct 11, 2020 at 10:50 AM Brent Fraser  wrote:
>>>
 How about allowing the station to optionally specify the image url?

 [station]
station_image=url = http://mydomain/station_image.png

 That should off-load the image creation.

 On Thursday, October 8, 2020 at 5:51:33 AM UTC-6 tke...@gmail.com
 wrote:

> Unfortunately, we have suspended preview snapshots. It was just taking
> too much memory, which would cause weewx.com to hang. Maybe later!
>
> On Thu, Oct 8, 2020 at 4:38 AM Didier Decoodt 
> wrote:
>
>> Hi Tom
>>
>> I have registered my station, it's OK but I have not a preview image
>> when I select the station
>> An idea?
>> [image: image.png]
>> Didier
>>
>> Le jeu. 8 oct. 2020 à 13:20, Tom Keffer  a écrit :
>>
>>> Why not just middle-button click?
>>>
>>> On Thu, Oct 8, 2020 at 12:29 AM Greg from Oz 
>>> wrote:
>>>
 Hi Tom,

 Is there a way to put right click on the url of the web cam links
 in the http://weewx.com/stations.html?

 The reason I ask is because when I click on a link to have a look
 at that web site and then press the back button it goes back to the 
 zoomed
 out view and then I have to move the map and zoom in all over again.

 If I could right click I could select open in a new tab and then I
 don't have to zoom and pan every time.

 I think this option was available ages ago.

 Thanks

 On Thursday, 8 October 2020 00:46:44 UTC+11, Tom Keffer wrote:
>
> Unfortunately, we have suspended preview snapshots. It was just
> taking too much memory, which would cause weewx.com to hang.
> Maybe later!
>
> On Tue, Oct 6, 2020 at 12:40 PM Vetti52  wrote:
>
>> being registered, but...
>> when opening the station on the map, there is no preview picture.
>> I am afraid, that for URLs containing windy.com a preview is not
>> available, right? I could establish another URL, which, however is 
>> only
>> available per IPv6 (IPv4 access is locked by a firewall). Would this
>> satisfy as source for a preview picture?
>>
>> Vetti52 schrieb am Dienstag, 6. Oktober 2020 um 10:49:19 UTC+2:
>>
>>> That's it!
>>> thanks
>>>
>>> tke...@gmail.com schrieb am Montag, 5. Oktober 2020 um 23:26:19
>>> UTC+2:
>>>
 I'm seeing an error on the server end: "station_url cannot
 contain single quotes".

 Not exactly sure what that means. Try using the URL
 https://www.windy.com/station/pws-f069b42a, without any quotes.

 -tk

 On Mon, Oct 5, 2020 at 12:21 PM Vetti52 
 wrote:

> just registered today, due to the advise in this thread.
> However there is no map entry. I get this log:
>
> Oct  5 21:00:30 raspbee weewx[10983] ERROR weewx.restx:
> StationRegistry: Failed to publish record 2020-10-05 21:00:00 CEST
> (1601924400): Failed upload after 3 tries
>
> I am using Weewx 4.1.1. My URL at windy.com actually works
> fine:
> https://www.windy.com/station/pws-f069b42a?54.088,10.258,8
> What is wrong?
>
> gjr80 schrieb am Sonntag, 4. Oktober 2020 um 22:57:52 UTC+2:
>
>> The only requirement of the URL is that it is unique in the
>> station registry. So I guess if you are making up an arbitrary 
>> URL be
>> creative. WU URLs are fine, they are used by numerous users in 
>> 

Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Ξ
I've just changed my station name to Greek (Ντόλνι Οκόλ) and it's on the 
map, look just south of Sofia. What's your station's URL?

On Sunday, January 17, 2021 at 2:38:05 PM UTC+2 hobbyl...@gmail.com wrote:

> i have my weather station since december 2020 , i had set registration to 
> true , after restarting weewx.but until now dont show in map. i wonder if 
> the problem is the greek characters  of station name. the rest greek 
> stations on map have english names. i had same issue in noaa reports and 
> solved that setting from ascii to utf 8 in skin conf. i dont know how to 
> solve this and i want to see my station in map. 
>
> Στις Κυριακή, 11 Οκτωβρίου 2020 στις 9:18:04 μ.μ. UTC+3, ο χρήστης 
> tke...@gmail.com έγραψε:
>
>> It's something we've talked about.
>>
>> On Sun, Oct 11, 2020 at 10:50 AM Brent Fraser  wrote:
>>
>>> How about allowing the station to optionally specify the image url?
>>>
>>> [station]
>>>station_image=url = http://mydomain/station_image.png
>>>
>>> That should off-load the image creation.
>>>
>>> On Thursday, October 8, 2020 at 5:51:33 AM UTC-6 tke...@gmail.com wrote:
>>>
 Unfortunately, we have suspended preview snapshots. It was just taking 
 too much memory, which would cause weewx.com to hang. Maybe later!

 On Thu, Oct 8, 2020 at 4:38 AM Didier Decoodt  
 wrote:

> Hi Tom
>
> I have registered my station, it's OK but I have not a preview image 
> when I select the station
> An idea?
> [image: image.png]
> Didier
>
> Le jeu. 8 oct. 2020 à 13:20, Tom Keffer  a écrit :
>
>> Why not just middle-button click?
>>
>> On Thu, Oct 8, 2020 at 12:29 AM Greg from Oz  
>> wrote:
>>
>>> Hi Tom,
>>>
>>> Is there a way to put right click on the url of the web cam links in 
>>> the http://weewx.com/stations.html?
>>>
>>> The reason I ask is because when I click on a link to have a look at 
>>> that web site and then press the back button it goes back to the zoomed 
>>> out 
>>> view and then I have to move the map and zoom in all over again.
>>>
>>> If I could right click I could select open in a new tab and then I 
>>> don't have to zoom and pan every time.
>>>
>>> I think this option was available ages ago.
>>>
>>> Thanks
>>>
>>> On Thursday, 8 October 2020 00:46:44 UTC+11, Tom Keffer wrote:

 Unfortunately, we have suspended preview snapshots. It was just 
 taking too much memory, which would cause weewx.com to hang. Maybe 
 later!

 On Tue, Oct 6, 2020 at 12:40 PM Vetti52  wrote:

> being registered, but...
> when opening the station on the map, there is no preview picture. 
> I am afraid, that for URLs containing windy.com a preview is not 
> available, right? I could establish another URL, which, however is 
> only 
> available per IPv6 (IPv4 access is locked by a firewall). Would this 
> satisfy as source for a preview picture?
>
> Vetti52 schrieb am Dienstag, 6. Oktober 2020 um 10:49:19 UTC+2:
>
>> That's it!
>> thanks
>>
>> tke...@gmail.com schrieb am Montag, 5. Oktober 2020 um 23:26:19 
>> UTC+2:
>>
>>> I'm seeing an error on the server end: "station_url cannot 
>>> contain single quotes".
>>>
>>> Not exactly sure what that means. Try using the URL 
>>> https://www.windy.com/station/pws-f069b42a, without any quotes.
>>>
>>> -tk
>>>
>>> On Mon, Oct 5, 2020 at 12:21 PM Vetti52  
>>> wrote:
>>>
 just registered today, due to the advise in this thread. 
 However there is no map entry. I get this log:

 Oct  5 21:00:30 raspbee weewx[10983] ERROR weewx.restx: 
 StationRegistry: Failed to publish record 2020-10-05 21:00:00 CEST 
 (1601924400): Failed upload after 3 tries

 I am using Weewx 4.1.1. My URL at windy.com actually works 
 fine: 
 https://www.windy.com/station/pws-f069b42a?54.088,10.258,8
 What is wrong?  

 gjr80 schrieb am Sonntag, 4. Oktober 2020 um 22:57:52 UTC+2:

> The only requirement of the URL is that it is unique in the 
> station registry. So I guess if you are making up an arbitrary 
> URL be 
> creative. WU URLs are fine, they are used by numerous users in 
> the station 
> registry.
>
> Gary
>
> On Monday, 5 October 2020 at 06:11:06 UTC+10 maf@gmail.com 
> wrote:
>
>> Tom:
>>
>> A question on 1. below. What if you do not have a web page or 
>> use any other (e.g. Weather 

Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Tom Keffer
Entirely possible. I've created issue #3
 to track.

On Sun, Jan 17, 2021 at 4:38 AM Δημήτρης Βήχος 
wrote:

> i have my weather station since december 2020 , i had set registration to
> true , after restarting weewx.but until now dont show in map. i wonder if
> the problem is the greek characters  of station name. the rest greek
> stations on map have english names. i had same issue in noaa reports and
> solved that setting from ascii to utf 8 in skin conf. i dont know how to
> solve this and i want to see my station in map.
>
> Στις Κυριακή, 11 Οκτωβρίου 2020 στις 9:18:04 μ.μ. UTC+3, ο χρήστης
> tke...@gmail.com έγραψε:
>
>> It's something we've talked about.
>>
>> On Sun, Oct 11, 2020 at 10:50 AM Brent Fraser  wrote:
>>
>>> How about allowing the station to optionally specify the image url?
>>>
>>> [station]
>>>station_image=url = http://mydomain/station_image.png
>>>
>>> That should off-load the image creation.
>>>
>>> On Thursday, October 8, 2020 at 5:51:33 AM UTC-6 tke...@gmail.com wrote:
>>>
 Unfortunately, we have suspended preview snapshots. It was just taking
 too much memory, which would cause weewx.com to hang. Maybe later!

 On Thu, Oct 8, 2020 at 4:38 AM Didier Decoodt 
 wrote:

> Hi Tom
>
> I have registered my station, it's OK but I have not a preview image
> when I select the station
> An idea?
> [image: image.png]
> Didier
>
> Le jeu. 8 oct. 2020 à 13:20, Tom Keffer  a écrit :
>
>> Why not just middle-button click?
>>
>> On Thu, Oct 8, 2020 at 12:29 AM Greg from Oz 
>> wrote:
>>
>>> Hi Tom,
>>>
>>> Is there a way to put right click on the url of the web cam links in
>>> the http://weewx.com/stations.html?
>>>
>>> The reason I ask is because when I click on a link to have a look at
>>> that web site and then press the back button it goes back to the zoomed 
>>> out
>>> view and then I have to move the map and zoom in all over again.
>>>
>>> If I could right click I could select open in a new tab and then I
>>> don't have to zoom and pan every time.
>>>
>>> I think this option was available ages ago.
>>>
>>> Thanks
>>>
>>> On Thursday, 8 October 2020 00:46:44 UTC+11, Tom Keffer wrote:

 Unfortunately, we have suspended preview snapshots. It was just
 taking too much memory, which would cause weewx.com to hang. Maybe
 later!

 On Tue, Oct 6, 2020 at 12:40 PM Vetti52  wrote:

> being registered, but...
> when opening the station on the map, there is no preview picture.
> I am afraid, that for URLs containing windy.com a preview is not
> available, right? I could establish another URL, which, however is 
> only
> available per IPv6 (IPv4 access is locked by a firewall). Would this
> satisfy as source for a preview picture?
>
> Vetti52 schrieb am Dienstag, 6. Oktober 2020 um 10:49:19 UTC+2:
>
>> That's it!
>> thanks
>>
>> tke...@gmail.com schrieb am Montag, 5. Oktober 2020 um 23:26:19
>> UTC+2:
>>
>>> I'm seeing an error on the server end: "station_url cannot
>>> contain single quotes".
>>>
>>> Not exactly sure what that means. Try using the URL
>>> https://www.windy.com/station/pws-f069b42a, without any quotes.
>>>
>>> -tk
>>>
>>> On Mon, Oct 5, 2020 at 12:21 PM Vetti52 
>>> wrote:
>>>
 just registered today, due to the advise in this thread.
 However there is no map entry. I get this log:

 Oct  5 21:00:30 raspbee weewx[10983] ERROR weewx.restx:
 StationRegistry: Failed to publish record 2020-10-05 21:00:00 CEST
 (1601924400): Failed upload after 3 tries

 I am using Weewx 4.1.1. My URL at windy.com actually works
 fine:
 https://www.windy.com/station/pws-f069b42a?54.088,10.258,8
 What is wrong?

 gjr80 schrieb am Sonntag, 4. Oktober 2020 um 22:57:52 UTC+2:

> The only requirement of the URL is that it is unique in the
> station registry. So I guess if you are making up an arbitrary 
> URL be
> creative. WU URLs are fine, they are used by numerous users in 
> the station
> registry.
>
> Gary
>
> On Monday, 5 October 2020 at 06:11:06 UTC+10 maf@gmail.com
> wrote:
>
>> Tom:
>>
>> A question on 1. below. What if you do not have a web page or
>> use any other (e.g. Weather Underground) site? Are you saying 
>> that we can
>> make up any arbitrary 

Re: [weewx-user] Rain data handling on custom driver

2021-01-17 Thread Tom Keffer
You've commented out the relevant code (in _augment_packet()), but it looks
to me like you're doing it the right way.

The only type that needs to be emitted is 'rain', but it's always a good
idea to augment the packet with anything else that can be relied on. So,
you might consider emitting 'totalRain' as well. It can always be
calculated from the database, but some people like to store it in the
database along with 'rain'.

I couldn't quite parse your sentence about whether the number of bucket
tips needs to be reset once in a while, or need *not* be reset. Assuming
the former, and assuming it's an unsigned integer, you could just let it
roll over, which calculate_rain() will detect.

Hope that helps. Not sure I answered your question.



On Sun, Jan 17, 2021 at 3:16 AM thago...@gmail.com 
wrote:

> Hello all!
>
> So, I've beed doing some searching & reading about how WeeWX handles rain
> data from various weather station devices. However, it's not clear to me
> what would the right strategy be in my case.
>
> I'm using a Microbit climate kit  and
> wrote a custom microbit program to serialise and send weather data through
> USB to a Raspberry pi which feeds it to WeeWX. Similarly, I used
> weesx-arduino-weather-station
>  driver as a
> base driver and modified it for my case. I also read how HP1000 driver
> handles rain (I read it in a previous post in this forum if I remember
> correctly) but I can't say I found it enlightening (it probably has to with
> my level of comprehension for WeeWX code).
>
> I attach my version of the driver. It's as simple as I my mind could
> program it. Please do not pay attention to my current way of reading rain
> data. I know it doesn't work. If I only correct the data binding, WeeWX
> stores rain data incrementally for every LOOP packet, as expected.
>
> Subsequently, my question is *not* how to retrieve rain data from the
> weather station, rather than how to feed it to WeeWX in order to get
> meaningful observations. The limitations on my microbit weather station are
> these:
> * No real time clock available on Microbit. I could use uptime, but it's
> not so useful as the microbit refuses to work properly every few days, so
> it needs to be reset. I could reset it manually with a cronjob if needed.
> * Rain data from the weather station only includes one number = bucket
> tips (which I convert to mm on microbit) which can only go up until
> microbit is reset - and it *needs* not be reset once in a while.
>
> How does one handle the last_rain, total_rain and rain data in WeeWX? The
> official documentation did not answer my question so if you could point me
> on the right direction or ideally describe the strategy I should follow, it
> would be great!
>
> Thank you all for your time! Cheers!
>
> --
> 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/00e5c25d-87c8-4f1d-91ce-2effcb98761an%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/CAPq0zEDG8Dz8PAHPbDqHQ81aBdAonywBw28WUDaAWP8KJ%3DQgMw%40mail.gmail.com.


Re: [weewx-user] Errors in 4.3

2021-01-17 Thread Tom Keffer
The type 'totalRain' has been in the code for a long time. What I'm
wondering about is where did the line

rain = prefer_hardware

come from.

If you are still on squeeze, you're best off staying with Python 2. Not all
of the Python 3 pre-requisites are available through the repositories.

-tk

On Sat, Jan 16, 2021 at 8:31 PM Clay Jackson  wrote:

> OK - thanks.  Had a bit of a scare when I corrupted my config file and
> NOTHING would start.   I commented rain and rainRate out of StdWXCaiculate
> and looks good now.  I AM getting an N/A in RanRate om the disp;lay, but
> that's OK for the time being.   Will check when we  next get rain to see
> what happens.
>
>  It would be nice to know where totalRain came from - I tried grep'ing for
> it in all the .py files and only found it in accum and units.  Before I
> posted, I actually commented those lines out and that did NOT work. Any
> thoughts on that?
>
> Also, I notice from the log I'm still using Python 2, which is what
> /usr/bin/python points to by default on squeeze, which is what I'm running
> right now.  Are there notes on how to force weewx to use python3?
>
> Thanks!
>
>
>
>
> On Sat, Jan 16, 2021 at 5:36 PM Tom Keffer  wrote:
>
>> Try removing the line
>>
>> rain = prefer_hardware
>>
>> It's what's causing the StdWXCalculate service to try and calculate a
>> value.
>>
>> I wonder where that line came from. I don't recall it ever being part of
>> weewx.conf
>>
>> -tk
>>
>> On Sat, Jan 16, 2021 at 4:58 PM Clay Jackson 
>> wrote:
>>
>>> I'm using an Accurite 5n1 - this has been working since early 3.x; just
>>> stopped in 4.3,  I AM using my 4.2 config files and skins.
>>>
>>> [StdWXCalculate]
>>>
>>> [[Calculations]]
>>> # Derived quantities are calculated by this service. 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
>>> barometer = prefer_hardware
>>> altimeter = software
>>> windchill = software
>>> heatindex = software
>>> dewpoint = software
>>> inDewpoint = prefer_hardware
>>> rainRate = prefer_hardware
>>> rain = prefer_hardware
>>> ET = software
>>> maxSolarRad = prefer_hardware
>>> cloudbase = prefer_hardware
>>> humidex = prefer_hardware
>>> appTemp = prefer_hardware
>>> windrun = prefer_hardware
>>>
>>>
>>> On Sat, Jan 16, 2021 at 4:45 PM Tom Keffer  wrote:
>>>
 Normally, the driver does it, but if asked, WeeWX can calculate 'rain'
 from cumulative quantities such as totalRain, by taking a difference.

 Your configuration file seems to be asking to do so, but totalRain is
 not available. As for why it's asking, that's not clear.

 What does the section [StdWXCalculate] in your file weewx.conf look
 like?


 On Sat, Jan 16, 2021 at 4:17 PM Clay Jackson 
 wrote:

> I just upgraded (through apt update, using raspbian) to 4.3.0 and am
> seeing the following error.
> Jan 16 15:59:12 Weather weewx[17287] INFO __main__: PID file is
> /var/run/weewx.pid
> Jan 16 15:59:12 Weather weewx[17275]: Starting weewx weather system:
> weewx.
> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Using
> configuration file /etc/weewx/weewx.conf
> Jan 16 15:59:12 Weather weewx[17291] INFO __main__: Debug is 0
> Jan 16 15:59:12 Weather weewx[17291] INFO weewx.engine: Loading
> station type SDR (user.sdr)
> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: driver version is
> 0.78
> Jan 16 15:59:12 Weather weewx[17291] INFO user.sdr: sensor map is
> {u'windDir': u'wind_dir.04C9.Acurite5n1PacketV2', u'windSpeed':
> u'wind_speed.04C9.Acurite5n1PacketV2', u'outTemp':
> u'temperature.04C9.Acurite5n1PacketV2', u'outHumidity':
> u'humidity.04C9.Acurite5n1PacketV2', u'rain_total':
> u'rain_total.04C9.Acurite5n1PacketV2', u'txBatteryStatus':
> u'battery.04C9.Acurite5n1PacketV2', u'inTemp':
> u'temperature.4:0.AmbientF007THPacket', u'inHumidity':
> u'humidity.4:0.AmbientF007THPacket', u'lightning_distance':
> u'distance.002B.AcuriteLightningPacket', u'soilTemp1':
> u'temperature_probe.0F66.Acurite00275MPacket', u'extraTemp5':
> u'temperature.0F66.Acurite00275MPacket', u'extraHumid3':
> u'humidity.0F66.Acurite00275MPacket', u'extraTemp1':
> u'temperature.002B.AcuriteLightningPacket', u'extraHumid1':
> u'humidity.002B.AcuriteLightningPacket', u'strikes_total':
> u'strikes_total.002B.AcuriteLightningPacket', u'extraTemp2':
> u'temperature.1:0.AmbientF007THPacket', u'extraTemp3':
> u'temperature.2:0.AmbientF007THPacket', u'extraTemp4':
> 

[weewx-user] sensor for the snow depth

2021-01-17 Thread sali...@gmail.com

Has anyone already made a sensor for the snow depth to connect it to the 
RPi and display the data on Weewx?

bye

Patrick

-- 
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/ef6ebe61-7163-4891-8166-e75b3c682c35n%40googlegroups.com.


Re: [weewx-user] Re: skin Belchertown " earth Quake"

2021-01-17 Thread salinois

hi,

so, now is good, I tried an other time with the master.zip

an error in the file weewx.conf maybe !!!

thanks for your help, Arend

bye

Patrick

Le 16/01/2021 à 21:11, Arend a écrit :

If this is your website:

http://jurassikpat.ddns.net/weewx/belchertown/ 



Then you don't have installed the skin version that a gave the link to.

Op zaterdag 16 januari 2021 om 20:39:58 UTC+1 schreef sali...@gmail.com:

Hi

I used already the master, "weewx-belchertown-master.zip", but
there is more errors before !!!

bye

patrick

Le 16/01/2021 à 19:31, Arend a écrit :

Thank you Vince for pointing this out.

He needs the unreleased master:
https://github.com/poblabs/weewx-belchertown/archive/master.zip


Arend

Op zaterdag 16 januari 2021 om 19:20:56 UTC+1 schreef vince:

On Saturday, January 16, 2021 at 9:59:45 AM UTC-8 Arend wrote:

That belchertown.py file is an old 1.2 version. The
problem right now is that there are multiple Belchertown
versions out there which all bear the version number 1.2.
This is because at the moment changes are all merged into
the Belchertown 1.2 master without changes to the version
numbers.


Um - not quite.   There is no such thing as 'Belchertown
1.2 master'.   There is the released v1.2 and there is a
rolling  'unreleased' master of whatever might come next.

A quick look says that there have been 137 commits to master
after 1.2 was released in September, so if you simply run off
a git clone of master there is some risk until Pat releases a
new tested version.  You can get the 'released' versions from
https://github.com/poblabs/weewx-belchertown/releases



-- 
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/95d5d647-c8d2-427f-9484-f7908843d877n%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/9a02a429-8a71-4f95-af7a-6be4e08dbbb5n%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/cca01e7d-d79c-ddcd-6a92-5bf42541d741%40gmail.com.


[weewx-user] Re: Inserting missing data using wee_import

2021-01-17 Thread Mike Revitt
For those that are interested in this, I have now completed the update of 
the missing data and documented how I did that here, turned out to be a lot 
simpler than I thought it would be

https://www.cougar.eu.com/useful-guides/weewx-guides/add-missing-data.html


On Friday, January 15, 2021 at 1:44:48 PM UTC Mike Revitt wrote:

> All appear to have worked perfectly thanks Gary,
>
> I can see all the history now and just need to wait for the week, month 
> and year images to refresh
>
> On Friday, January 15, 2021 at 1:15:49 PM UTC gjr80 wrote:
>
>> Yes, wee_import inserts and does not update. If you have a look back at 
>> the WeeWX log from when you did the import you will probably find a lot of 
>> error messages about ‘unique constraint failures’ on dateTime, this is 
>> because wee_import tried to add a record with a timestamp that already 
>> existed in the database. wee_import uses code used by StdArchive for adding 
>> records to the database and unfortunately wee_import is unable to tell if 
>> the insert was successful or not, that is why you if you look closely there 
>> is some oddly worded summary text after a wee_import run. It advises you of 
>> how many records were processed and not how many were saved, and you are 
>> directed to the log to check success or otherwise.
>>
>> Gary 
>> On Friday, 15 January 2021 at 23:04:07 UTC+10 mi...@cougar.eu.com wrote:
>>
>>> Thanks Gary, will give that a go.
>>>
>>> And am I correct in my suspicion that wee_import didn't work because it 
>>> only does inserts not updates
>>>
>>>
>>> On Friday, January 15, 2021 at 1:01:20 PM UTC gjr80 wrote:
>>>
 That’s one of the reasons we discourage writing to the database 
 directly, far better to let the WeeWX machinery take care of everything. 
 In 
 answer to your question, if you have inserted the missing data in the 
 archive then just use the wee_database 
  utility 
 to rebuild the daily summaries for the period concerned, that will take 
 care of everything in the daily summary tables.

 Gary

 On Friday, 15 January 2021 at 20:50:53 UTC+10 mi...@cougar.eu.com 
 wrote:

> I have also discovered some columns  sum REAL, count INTEGER, wsum 
> REAL, sumtime INTEGER
> and have no idea what to put in them
>
> On Friday, January 15, 2021 at 9:51:59 AM UTC Mike Revitt wrote:
>
>> I am having some interesting challenges around updating my database 
>> with some missing data.
>>
>> Now that I have integrated my Caravan temperatures into WeeWX I am 
>> have extracted the data from the period that I was recording it but not 
>> updating WeeWX.
>>
>> I have created a css file with the data and wee_import runs perfectly 
>> with no errors, but no new data appears in the database.
>>
>> I suspect that this is because I am trying to do an update rather 
>> than an insert. So I have created an update script for. the archive 
>> table 
>> and this runs perfectly, I used python to generate the epoc dates, and I 
>> ran this on a copy of the database so I did not screw anything up.
>>
>> The challenge is updating the archive tables archive_day_extraHumid1 
>> etc. I can relatively easily construct the min and max values for a time 
>> period but constructing the min time is a little more challenging. So 
>> before I do that is there some tool I can invoke that will populate 
>> these 
>> archive tables from the new data in the main archive table
>>
>>

-- 
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/f6c44641-bb54-420d-af46-9ac9f0094e85n%40googlegroups.com.


Re: [weewx-user] Re: skin Belchertown " earth Quake"

2021-01-17 Thread salinois

hi again,

so, now I try your link on an other RPi and I have errors:

Jan 17 13:54:17 raspberrypi weewx[2134] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   'aqi'
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   Traceback (most recent call last):
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:     File 
"/usr/share/weewx/user/belchertown.py", line 1074, in get_extension_list
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   aqi = 
data['aqi'][0]['response'][0]['periods'][0]['aqi']
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   KeyError: 'aqi'
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine: 
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   During handling of the above 
exception, another exception occurred:
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine: 
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   Traceback (most recent call last):
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:     File 
"/usr/share/weewx/weewx/reportengine.py", line 196, in run
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   obj.start()
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:     File 
"/usr/share/weewx/weewx/reportengine.py", line 281, in start
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   self.run()
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:     File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 149, in run
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   ngen = 
self.generate(gen_dict[section_name], self.gen_ts)
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:     File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 219, in generate
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   ngen += 
self.generate(section[subsection], gen_ts)
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:     File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 219, in generate
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   ngen += 
self.generate(section[subsection], gen_ts)
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:     File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 308, in generate
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   default_binding)
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:     File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 379, in _getSearchList
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   searchList += 
obj.get_extension_list(timespan, db_lookup)
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:     File 
"/usr/share/weewx/user/belchertown.py", line 1079, in get_extension_list
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   logerr( "Error getting AQI from 
Aeris weather. The error was:\n%s\nThe response from the Aeris AQI 
server was:\n%s\nThe URL being used is:\n%s" % (error, data['aqi'], 
aqi_url))
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   KeyError: 'aqi'
Jan 17 13:54:17 raspberrypi weewx[2134] ERROR 
weewx.reportengine:   Generator terminated



Patrick

Le 16/01/2021 à 21:11, Arend a écrit :

If this is your website:

http://jurassikpat.ddns.net/weewx/belchertown/ 



Then you don't have installed the skin version that a gave the link to.

Op zaterdag 16 januari 2021 om 20:39:58 UTC+1 schreef sali...@gmail.com:

Hi

I used already the master, "weewx-belchertown-master.zip", but
there is more errors before !!!

bye

patrick

Le 16/01/2021 à 19:31, Arend a écrit :

Thank you Vince for pointing this out.

He needs the unreleased master:
https://github.com/poblabs/weewx-belchertown/archive/master.zip


Arend

Op zaterdag 16 januari 2021 om 19:20:56 UTC+1 schreef vince:

On Saturday, January 16, 2021 at 9:59:45 AM UTC-8 Arend wrote:

That belchertown.py file is an old 1.2 version. The
problem right now is that there are multiple Belchertown
versions out there which all bear the version number 1.2.
This is because at the moment changes are all merged into
the Belchertown 1.2 

Re: [weewx-user] Register your WeeWX station!

2021-01-17 Thread Δημήτρης Βήχος
i have my weather station since december 2020 , i had set registration to 
true , after restarting weewx.but until now dont show in map. i wonder if 
the problem is the greek characters  of station name. the rest greek 
stations on map have english names. i had same issue in noaa reports and 
solved that setting from ascii to utf 8 in skin conf. i dont know how to 
solve this and i want to see my station in map. 

Στις Κυριακή, 11 Οκτωβρίου 2020 στις 9:18:04 μ.μ. UTC+3, ο χρήστης 
tke...@gmail.com έγραψε:

> It's something we've talked about.
>
> On Sun, Oct 11, 2020 at 10:50 AM Brent Fraser  wrote:
>
>> How about allowing the station to optionally specify the image url?
>>
>> [station]
>>station_image=url = http://mydomain/station_image.png
>>
>> That should off-load the image creation.
>>
>> On Thursday, October 8, 2020 at 5:51:33 AM UTC-6 tke...@gmail.com wrote:
>>
>>> Unfortunately, we have suspended preview snapshots. It was just taking 
>>> too much memory, which would cause weewx.com to hang. Maybe later!
>>>
>>> On Thu, Oct 8, 2020 at 4:38 AM Didier Decoodt  
>>> wrote:
>>>
 Hi Tom

 I have registered my station, it's OK but I have not a preview image 
 when I select the station
 An idea?
 [image: image.png]
 Didier

 Le jeu. 8 oct. 2020 à 13:20, Tom Keffer  a écrit :

> Why not just middle-button click?
>
> On Thu, Oct 8, 2020 at 12:29 AM Greg from Oz  
> wrote:
>
>> Hi Tom,
>>
>> Is there a way to put right click on the url of the web cam links in 
>> the http://weewx.com/stations.html?
>>
>> The reason I ask is because when I click on a link to have a look at 
>> that web site and then press the back button it goes back to the zoomed 
>> out 
>> view and then I have to move the map and zoom in all over again.
>>
>> If I could right click I could select open in a new tab and then I 
>> don't have to zoom and pan every time.
>>
>> I think this option was available ages ago.
>>
>> Thanks
>>
>> On Thursday, 8 October 2020 00:46:44 UTC+11, Tom Keffer wrote:
>>>
>>> Unfortunately, we have suspended preview snapshots. It was just 
>>> taking too much memory, which would cause weewx.com to hang. Maybe 
>>> later!
>>>
>>> On Tue, Oct 6, 2020 at 12:40 PM Vetti52  wrote:
>>>
 being registered, but...
 when opening the station on the map, there is no preview picture. I 
 am afraid, that for URLs containing windy.com a preview is not 
 available, right? I could establish another URL, which, however is 
 only 
 available per IPv6 (IPv4 access is locked by a firewall). Would this 
 satisfy as source for a preview picture?

 Vetti52 schrieb am Dienstag, 6. Oktober 2020 um 10:49:19 UTC+2:

> That's it!
> thanks
>
> tke...@gmail.com schrieb am Montag, 5. Oktober 2020 um 23:26:19 
> UTC+2:
>
>> I'm seeing an error on the server end: "station_url cannot 
>> contain single quotes".
>>
>> Not exactly sure what that means. Try using the URL 
>> https://www.windy.com/station/pws-f069b42a, without any quotes.
>>
>> -tk
>>
>> On Mon, Oct 5, 2020 at 12:21 PM Vetti52  wrote:
>>
>>> just registered today, due to the advise in this thread. However 
>>> there is no map entry. I get this log:
>>>
>>> Oct  5 21:00:30 raspbee weewx[10983] ERROR weewx.restx: 
>>> StationRegistry: Failed to publish record 2020-10-05 21:00:00 CEST 
>>> (1601924400): Failed upload after 3 tries
>>>
>>> I am using Weewx 4.1.1. My URL at windy.com actually works 
>>> fine: https://www.windy.com/station/pws-f069b42a?54.088,10.258,8
>>> What is wrong?  
>>>
>>> gjr80 schrieb am Sonntag, 4. Oktober 2020 um 22:57:52 UTC+2:
>>>
 The only requirement of the URL is that it is unique in the 
 station registry. So I guess if you are making up an arbitrary URL 
 be 
 creative. WU URLs are fine, they are used by numerous users in the 
 station 
 registry.

 Gary

 On Monday, 5 October 2020 at 06:11:06 UTC+10 maf@gmail.com 
 wrote:

> Tom:
>
> A question on 1. below. What if you do not have a web page or 
> use any other (e.g. Weather Underground) site? Are you saying 
> that we can 
> make up any arbitrary URL as long as it is unique?
>
> Thanks.
>
> Mike
>
>
> On 10/4/2020 1:41 PM, Tom Keffer wrote:
>
> While we don't require it, I strongly encourage you to 
> 

[weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-17 Thread S R
For the record, mine is a Chinese Mi-Sol WH2900C. It is a copy of the Fine 
Offset WH2900 or the Ecowitt WS2950. Indeed, the unit requires a connection 
to Ecowitt to set the Time/Date and automatically downloaded the 
EasyWeather 1.56 firmware update from Ecowitt. 

I haven't got the outdoor setup done yet, while i play with getting the 
unit up and running. but Ecowitt, shows my indoor temperature and pressure 
on the home page. I use pfsense so can run a packet capture if it helps. 
Since editing the weewx.conf file, i am getting the utf-8 problem. I guess 
this is related to me using European accented characters in my editors 
which are UTF-8. So that leaves me with two questions;
1) how to have it accept the UTF-8 characters
2) you mentioned not getting all the sensor data, unless using Ecowitt. In 
view, that i am. Can you tell me what additional parameters i need in the 
config file please.



On Sunday, January 17, 2021 at 9:21:33 AM UTC+1 S R wrote:

> almost there, but now 
>
> /usr/local/share/weewx # ./bin/wee_reports
>
> Traceback (most recent call last):
>   File "./bin/wee_reports", line 103, in 
> main()
>   File "./bin/wee_reports", line 51, in main
> config_path, config_dict = weecfg.read_config(options.config_path, 
> args)
>   File "/usr/local/share/weewx/bin/weecfg/__init__.py", line 180, in 
> read_config
> default_encoding='utf-8')
>   File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1229, 
> in __init__
> self._load(infile, configspec)
>   File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1287, 
> in _load
> content = self._handle_bom(content)
>
> On Saturday, January 16, 2021 at 11:30:28 PM UTC+1 galfert wrote:
>
>> Yes the best method when using the Interceptor is to use the Customized 
>> server settings. The path doesn't matter. But in some firmware versions it 
>> just couldn't be left blank or it wouldn't send. So just put in index.php? 
>> for the path.
>>
>>
>> On Saturday, January 16, 2021 at 3:49:17 PM UTC-5 sjr4...@gmail.com 
>> wrote:
>>
>>> OK. So i am homing in a little closer here. 
>>> I have configured the console to wunderground and it is working. 
>>>
>>> Now i need to adjust weewx.conf with the following, but as the weewx 
>>> server is on a different subnet, i will need to use listen mode. 
>>>
>>> [Interceptor]
>>> driver = user.interceptor
>>> device_type = wu-client 
>>>
>>> If i understand, i can point the console with a custom config to my 
>>> server, and then publish from my server to wunderground right?
>>>
>>> if i do that, what will the path on weewx for the console? 
>>>
>>> host:  weewx.local.lan
>>> Path: ?
>>> ID:   xx
>>> Key:xx
>>>
>>> also, on a side note. I can't find the log in freebsd. 
>>>
>>> On Saturday, January 16, 2021 at 9:17:02 PM UTC+1 galfert wrote:
>>>
 What I understand you are saying is that you have a WH2910 and you want 
 to interface it with WeeWX. Since you don't have an Ambient version you do 
 have the ability to easily use the Interceptor driver. Ambient WS-2902 
 can't without a lot of extra work. You, with the WH2910 can simply install 
 the WeeWX Interceptor driver and make sure your WeeWX config is set to use 
 the Interceptor driver with the correct WU client settings:
 [Interceptor]
 driver = user.interceptor
 device_type = wu-client  

 ...or you can add the Ecowitt GW1000 driver and the instead use the 
 GW1000 API driver instead of the Interceptor driver. This will allow you 
 to 
 add more sensors.


 On Saturday, January 16, 2021 at 2:54:09 PM UTC-5 sjr4...@gmail.com 
 wrote:

>
> actually, mine is equivalent to the WH2910 - it is not a case of 
> getting, i already have
> On Saturday, January 16, 2021 at 4:42:53 PM UTC+1 galfert wrote:
>
>> You have dug up quite an old thread. A lot has changed since. The 
>> recommendation now is to just acquire the Ecowitt GW1000 and use the 
>> WeeWX 
>> GW1000 API driver. The GW1000 will directly pick up your sensor data (it 
>> doesn't talk to the display console...as it is its own console). You'll 
>> get 
>> a much nicer experience with the GW1000, which will also let you add 
>> extra 
>> sensors.
>> https://github.com/gjr80/weewx-gw1000
>>
>>
>> On Saturday, January 16, 2021 at 2:43:44 AM UTC-5 sjr4...@gmail.com 
>> wrote:
>>
>>> were you able to get this to work in the end. can you share the 
>>> weewx details please
>>>
>>> On Saturday, April 1, 2017 at 4:37:01 PM UTC+2 44085w...@gmail.com 
>>> wrote:
>>>
 I see that weewx is said to support the FINE OFFSET WH2900 , I was 
 wondering if anyone could share with me the protocol and port 
 information 
 that is in the driver? I

>>>

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

[weewx-user] Re: New internet provider - now ftp doesn't work

2021-01-17 Thread David Levine
Check out http://weewx.com/docs/usersguide.htm#config_FTP and look to 
add/adjust the passive setting in your weewx.conf config. 

David 

On Saturday, January 16, 2021 at 10:11:56 PM UTC-5 Rich Strle wrote:

> I changed out my internet provider to t-mobile home internet service and 
> now I'm getting ftp errors. I tried connecting to the ftp from another 
> computer and that worked. When my raspberry pi tries to connect I get 
> errors. This was working fine before I switched providers. Any ideas?
>
> Jan 16 21:01:25 pi-weather weewx[30706] DEBUG weeutil.ftpupload: 
> Attempting connection to www.cliffandbuster.com
> Jan 16 21:01:26 pi-weather weewx[30706] DEBUG weeutil.ftpupload: Connected 
> to www.cliffandbuster.com
> Jan 16 21:01:26 pi-weather weewx[30706] ERROR weeutil.ftpupload: Failed 
> uploading /var/www/html/weewx/seasons.css to server www.cliffandbuster.com. 
> Reason: '229 Extended Passive Mode Entered (|||50207|)'
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine: 
> ftpgenerator: (1): caught exception '': 229 
> Extended Passive Mode Entered (|||50207|)
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>    Traceback (most recent call last):
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>  File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
> Jan 16 21:01:27 pi-weather weewx[30706] ERROR weewx.reportengine:
>    n = ftp_data.run()
>
>

-- 
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/7384313e-ab89-48b8-85d1-b07c14964143n%40googlegroups.com.


Re: [weewx-user] Re: skin Belchertown " earth Quake"

2021-01-17 Thread salinois

hi,

as I told you in my mail of 01/16, I have already tried this version, 
but it crashes weewx and I have lots of errors that I did not have 
before !!!


weird

Patrick


Le 16/01/2021 à 21:11, Arend a écrit :

If this is your website:

http://jurassikpat.ddns.net/weewx/belchertown/ 



Then you don't have installed the skin version that a gave the link to.

Op zaterdag 16 januari 2021 om 20:39:58 UTC+1 schreef sali...@gmail.com:

Hi

I used already the master, "weewx-belchertown-master.zip", but
there is more errors before !!!

bye

patrick

Le 16/01/2021 à 19:31, Arend a écrit :

Thank you Vince for pointing this out.

He needs the unreleased master:
https://github.com/poblabs/weewx-belchertown/archive/master.zip


Arend

Op zaterdag 16 januari 2021 om 19:20:56 UTC+1 schreef vince:

On Saturday, January 16, 2021 at 9:59:45 AM UTC-8 Arend wrote:

That belchertown.py file is an old 1.2 version. The
problem right now is that there are multiple Belchertown
versions out there which all bear the version number 1.2.
This is because at the moment changes are all merged into
the Belchertown 1.2 master without changes to the version
numbers.


Um - not quite.   There is no such thing as 'Belchertown
1.2 master'.   There is the released v1.2 and there is a
rolling  'unreleased' master of whatever might come next.

A quick look says that there have been 137 commits to master
after 1.2 was released in September, so if you simply run off
a git clone of master there is some risk until Pat releases a
new tested version.  You can get the 'released' versions from
https://github.com/poblabs/weewx-belchertown/releases



-- 
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/95d5d647-c8d2-427f-9484-f7908843d877n%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/9a02a429-8a71-4f95-af7a-6be4e08dbbb5n%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/a9fe9822-5a6b-3cca-b6a8-b3422ac6373d%40gmail.com.


[weewx-user] Rain data handling on custom driver

2021-01-17 Thread thago...@gmail.com
Hello all!

So, I've beed doing some searching & reading about how WeeWX handles rain 
data from various weather station devices. However, it's not clear to me 
what would the right strategy be in my case.

I'm using a Microbit climate kit  and 
wrote a custom microbit program to serialise and send weather data through 
USB to a Raspberry pi which feeds it to WeeWX. Similarly, I used 
weesx-arduino-weather-station 
 driver as a base 
driver and modified it for my case. I also read how HP1000 driver handles 
rain (I read it in a previous post in this forum if I remember correctly) 
but I can't say I found it enlightening (it probably has to with my level 
of comprehension for WeeWX code).

I attach my version of the driver. It's as simple as I my mind could 
program it. Please do not pay attention to my current way of reading rain 
data. I know it doesn't work. If I only correct the data binding, WeeWX 
stores rain data incrementally for every LOOP packet, as expected.

Subsequently, my question is *not* how to retrieve rain data from the 
weather station, rather than how to feed it to WeeWX in order to get 
meaningful observations. The limitations on my microbit weather station are 
these:
* No real time clock available on Microbit. I could use uptime, but it's 
not so useful as the microbit refuses to work properly every few days, so 
it needs to be reset. I could reset it manually with a cronjob if needed.
* Rain data from the weather station only includes one number = bucket tips 
(which I convert to mm on microbit) which can only go up until microbit is 
reset - and it *needs* not be reset once in a while.

How does one handle the last_rain, total_rain and rain data in WeeWX? The 
official documentation did not answer my question so if you could point me 
on the right direction or ideally describe the strategy I should follow, it 
would be great!

Thank you all for your time! Cheers!

-- 
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/00e5c25d-87c8-4f1d-91ce-2effcb98761an%40googlegroups.com.
#!/usr/bin/env python
#
# This is a weeWX driver to enable weeWX to read data from a Microbit Climate.
#
# See here for more details:
#
# https://github.com/wrybread/ArduinoWeatherStation
#
# by wrybr...@gmail.com
#
#
#

"""Driver for Micro:bit Climate weather station.

See here for more info:

https://google.gr

"""

from __future__ import with_statement
import serial
import syslog
import time
import io
from pprint import pprint
import weewx.drivers

DRIVER_NAME = 'microbit'
DRIVER_VERSION = '0.1'


def loader(config_dict, _):
return MicrobitDriver(**config_dict[DRIVER_NAME])


def confeditor_loader():
return MicrobitConfEditor()


INHG_PER_MBAR = 0.0295333727
METER_PER_FOOT = 0.3048
MILE_PER_KM = 0.621371

DEFAULT_PORT = '/dev/ttyACM0'
DEBUG_READ = 1

def logmsg(level, msg):
syslog.syslog(level, 'Microbit: %s' % msg)

def logdbg(msg):
logmsg(syslog.LOG_DEBUG, msg)

def loginf(msg):
logmsg(syslog.LOG_INFO, msg)

def logerr(msg):
logmsg(syslog.LOG_ERR, msg)







class MicrobitDriver(weewx.drivers.AbstractDevice):
"""weewx driver that communicates with an Arduino weather station

port - serial port
[Required. Default is /dev/ttyACM0]

polling_interval - how often to query the serial interface, seconds
[Optional. Default is 1]

max_tries - how often to retry serial communication before giving up
[Optional. Default is 5]

retry_wait - how long to wait, in seconds, before retrying after a failure
[Optional. Default is 10]
"""
def __init__(self, **stn_dict):
self.port = stn_dict.get('port', DEFAULT_PORT)

self.polling_interval = float(stn_dict.get('polling_interval', 2))
self.max_tries = int(stn_dict.get('max_tries', 10))
self.retry_wait = int(stn_dict.get('retry_wait', 10))
self.last_rain = None
loginf('driver version is %s' % DRIVER_VERSION)
loginf('using serial port %s' % self.port)
loginf('polling interval is %s' % self.polling_interval)
global DEBUG_READ
DEBUG_READ = int(stn_dict.get('debug_read', DEBUG_READ))

self.last_read_time = time.time()
self.read_counter = 0


logdbg("Opening the Arduino on port %s" % self.port)

self.baudrate = 115200
self.timeout = 10  # changed from 60
self.serial_port = None

try:
self.serial_port = serial.Serial(self.port, self.baudrate,
 timeout=self.timeout)
self.serial_port.flush()

logdbg("Successfully opened the Arduino.")

except Exception 

Re: [weewx-user] Re: ERROR weewx.cheetahgenerator: **** MemoryError

2021-01-17 Thread garrya...@gmail.com
I haven't managed to package the "latest & greatest" up for others but I 
did do some testing.

It occurred to me that since my extension is now a service, not dependent 
on a skin, I could turn off a skin to see if that changed the problem.  So 
I disabled the Belchertown skin and restarted WeeWX.

And it looks like the problem has gone away, so at this time, it looks like 
the cause of the leak is associated with Belchertown, but I don't know 
enough (anything really!) to say whether it's about WeedWX calling 
Belchertown or Belchertown itself.

The station website at: https://lockyer.ca/weather/OsoyoosLakeNorthEast is 
no longer being updated ('cause Belchertown is disabled) but the mem graphs 
at: https://lockyer.ca/weather/OsoyoosLakeNorthEast/mem are.  The 
discontinuity of memory growth around 2:30 PM Saturday was caused by an 
poorly handled error for one of the feeds in my code - that's now fixed.  
The data before about midnight are for testing before I disabled 
Belchertown.  I'll probably re-enable Belchertown after a few hours.

In the morning, I will update my MemoryTest to provide the smallest / 
simplest code to demonstrate the problem and make it available for others 
to test with.

Thanks again for all your help,

Garry

On Saturday, January 16, 2021 at 1:29:35 PM UTC-8 garrya...@gmail.com wrote:

> Thanks, will do but later today.
>
>
> Regards,
>
> Garry Lockyer
> C: +1.250.689.0686 <(250)%20689-0686>
> E: ga...@lockyer.ca
>
>
> On Jan 16, 2021, at 11:09, bell...@gmail.com  wrote:
>
> 
>
>
> Garry,
> If you want me to run something, just make it available and give me some 
> instructions.
> rich
> On Saturday, 16 January 2021 at 12:25:33 UTC-5 garrya...@gmail.com wrote:
>
>> I've added the mem extension.  My test station, with a large number of 
>> feeds selected, is at: https://lockyer.ca/weather/OsoyoosLakeNorthEast
>>
>> mem graphs are at: https://lockyer.ca/weather/OsoyoosLakeNorthEast/mem
>>
>> Regards,
>>
>> Garry
>>
>> On Saturday, January 16, 2021 at 8:42:09 AM UTC-8 garrya...@gmail.com 
>> wrote:
>>
>>> Brief Update: January 16, 2021:
>>>
>>> I've pretty much finished moving my extension to a service.
>>>
>>> I started WeeWX at about midnight and at about 8:20 AM, memory usage has 
>>> grown to over 941MB!  Allocated blocks was at 4,245,722.
>>>
>>> So growing memory usage problem exists.
>>>
>>> Bill indicated above he ran my test code on Ubuntu so I set up a Ubuntu 
>>> Raspberry Pi Desktop system:
>>>
>>> RPi 4 - 6 GB
>>> Ubuntu Raspberry Pi OS 20.10
>>> Python3 - 3.8.6
>>> WeeWX 4.3
>>> Belchertown 1.2
>>>
>>> Later today I intend to add the mem extension.  Will report back 
>>> soonest!  I will also run things on Raspberrry Pi OS (but I have to build a 
>>> new one!).
>>>
>>> Regards,
>>>
>>> Garry
>>> PS: I *think* I'm going to continue all development on Ubuntu as it 
>>> seems more current - it has a later linux kernel and more current Python - 
>>> but I'm not sure it's otherwise better than Raspberry Pi OS.  Both OS's 
>>> have wireless mouse lag problems, fixed somewhat by changing 'mousepoll' 
>>> setting.  Installation of Ubuntu was easy and I managed to get it to boot 
>>> from a USB SSD.  In the first 8 hours or so, Ubuntu froze a couple of 
>>> times, so now I keep an ssh session open so that I can reboot.
>>>
>>> On Saturday, January 9, 2021 at 8:02:51 PM UTC-8 garrya...@gmail.com 
>>> wrote:
>>>
 My experience is that when I recreate an include file for Belchertown 
 on each archive cycle, as an extension to Belchertown or as a service, 
 memory usage increases with each cycle and eventually errors start.  I’ve 
 seen the error I reported in this string and unresponsive systems.  So, 
 yes, I think there’s a problem.

 The memory test service I provided starts out at about 45 MB and 
 increases at about 3 MB per cycle.  I’ve seen WeeWx memory usage grow to 
 over 1 GB!

 I’m working on a new version of my extension, as a service, and will 
 report back on its memory usage, hopefully within only a couple of days.

 Thanks for all your help!


 Regards,

 Garry Lockyer
 C: +1.250.689.0686 <(250)%20689-0686>
 E: ga...@lockyer.ca


 On Jan 9, 2021, at 19:11, vince  wrote:

 If your memory usage is stable, is there a problem ?

 It's pretty typical after a weewx startup for the usage to go up a bit 
 then level off nicely.

 On Saturday, January 9, 2021 at 4:41:51 PM UTC-8 bell...@gmail.com 
 wrote:

> Garry,
> I ran your test extension for a bit in my Ubuntu VM.  Doesn't appear 
> to be leaking.
>  16:42:24 {'mem_size': 338.53515625, 'mem_rss': 32.953125, 
> 'mem_share': 11.28125}
>  16:47:38 {'mem_size': 423.80859375, 'mem_rss': 47.75, 'mem_share': 
> 11.796875}
>  16:52:53 {'mem_size': 424.4140625 <(424)%20414-0625>, 'mem_rss': 
> 48.2265625, 'mem_share': 11.796875}
>  16:57:24 {'mem_size': 

[weewx-user] Re: FINE OFFSET WH2900 / Ambient Weather WS-2902

2021-01-17 Thread S R
almost there, but now 

/usr/local/share/weewx # ./bin/wee_reports
Traceback (most recent call last):
  File "./bin/wee_reports", line 103, in 
main()
  File "./bin/wee_reports", line 51, in main
config_path, config_dict = weecfg.read_config(options.config_path, args)
  File "/usr/local/share/weewx/bin/weecfg/__init__.py", line 180, in 
read_config
default_encoding='utf-8')
  File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1229, in 
__init__
self._load(infile, configspec)
  File "/usr/local/lib/python3.7/site-packages/configobj.py", line 1287, in 
_load
content = self._handle_bom(content)

On Saturday, January 16, 2021 at 11:30:28 PM UTC+1 galfert wrote:

> Yes the best method when using the Interceptor is to use the Customized 
> server settings. The path doesn't matter. But in some firmware versions it 
> just couldn't be left blank or it wouldn't send. So just put in index.php? 
> for the path.
>
>
> On Saturday, January 16, 2021 at 3:49:17 PM UTC-5 sjr4...@gmail.com wrote:
>
>> OK. So i am homing in a little closer here. 
>> I have configured the console to wunderground and it is working. 
>>
>> Now i need to adjust weewx.conf with the following, but as the weewx 
>> server is on a different subnet, i will need to use listen mode. 
>>
>> [Interceptor]
>> driver = user.interceptor
>> device_type = wu-client 
>>
>> If i understand, i can point the console with a custom config to my 
>> server, and then publish from my server to wunderground right?
>>
>> if i do that, what will the path on weewx for the console? 
>>
>> host:  weewx.local.lan
>> Path: ?
>> ID:   xx
>> Key:xx
>>
>> also, on a side note. I can't find the log in freebsd. 
>>
>> On Saturday, January 16, 2021 at 9:17:02 PM UTC+1 galfert wrote:
>>
>>> What I understand you are saying is that you have a WH2910 and you want 
>>> to interface it with WeeWX. Since you don't have an Ambient version you do 
>>> have the ability to easily use the Interceptor driver. Ambient WS-2902 
>>> can't without a lot of extra work. You, with the WH2910 can simply install 
>>> the WeeWX Interceptor driver and make sure your WeeWX config is set to use 
>>> the Interceptor driver with the correct WU client settings:
>>> [Interceptor]
>>> driver = user.interceptor
>>> device_type = wu-client  
>>>
>>> ...or you can add the Ecowitt GW1000 driver and the instead use the 
>>> GW1000 API driver instead of the Interceptor driver. This will allow you to 
>>> add more sensors.
>>>
>>>
>>> On Saturday, January 16, 2021 at 2:54:09 PM UTC-5 sjr4...@gmail.com 
>>> wrote:
>>>

 actually, mine is equivalent to the WH2910 - it is not a case of 
 getting, i already have
 On Saturday, January 16, 2021 at 4:42:53 PM UTC+1 galfert wrote:

> You have dug up quite an old thread. A lot has changed since. The 
> recommendation now is to just acquire the Ecowitt GW1000 and use the 
> WeeWX 
> GW1000 API driver. The GW1000 will directly pick up your sensor data (it 
> doesn't talk to the display console...as it is its own console). You'll 
> get 
> a much nicer experience with the GW1000, which will also let you add 
> extra 
> sensors.
> https://github.com/gjr80/weewx-gw1000
>
>
> On Saturday, January 16, 2021 at 2:43:44 AM UTC-5 sjr4...@gmail.com 
> wrote:
>
>> were you able to get this to work in the end. can you share the weewx 
>> details please
>>
>> On Saturday, April 1, 2017 at 4:37:01 PM UTC+2 44085w...@gmail.com 
>> wrote:
>>
>>> I see that weewx is said to support the FINE OFFSET WH2900 , I was 
>>> wondering if anyone could share with me the protocol and port 
>>> information 
>>> that is in the driver? I
>>>
>>

-- 
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/7f9d11e0-887a-4fba-916c-d4f401a8e318n%40googlegroups.com.