Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[dunbrokin]

Thank you so much!

On Mon, Jan 7, 2019 at 8:29 PM gjr80  wrote:

> Yes. That is a setting for the console rather than a weeWX config setting.
> You have two choices; you can set it manually via buttons on the console or
> you can set it using the wee_device
>  utility. To do
> the former you need to read the console manual :) For the latter have a
> look through the wee_device Vantage notes
> , you need to use the 
> --set-offset
> action .
> Something like:
>
> $ wee_device --set-offset=windDir,180
>
> should do the trick, in fact that is one of the examples. Note you may or
> may not need to prefix that with sudo. Just make sure you read through the
> Vantage wee_device notes first, make sure you stop weeWX before using
> wee_device (only one thing can talk to the console at once) and check the
> setting afterwards with wee_device --info
>
> Gary
>
> On Monday, 7 January 2019 16:22:40 UTC+10, monmul wrote:
>
>> Ooops! one more thing.how do I do a wind offset? I cannot see it in
>> the config file?!
>>
>> On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>>>
>>> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis
>>> Vantage weather station. I have a serial Envoy data logger attaced to my
>>> Rpi with a serial/usb converter. In following the set up instructions, I
>>> get these errors!
>>>
>>> sudo weewxd weewx.conf
>>> Traceback (most recent call last):
>>>   File "/usr/bin/weewxd", line 64, in 
>>> weewx.engine.main(options, args)
>>>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
>>> sane = os.stat(config_path).st_ctime
>>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
>>> pi@Weatherpi:~ $ tail -f /var/log/syslog
>>> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered:
>>> sender=:1.16 path=/MediaEndpoint/A2DPSink
>>> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
>>> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
>>> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
>>> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
>>> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan  6 13:41:35 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx
>>> version 3.8.2
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9
>>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform
>>> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>>> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary
>>> Directories...
>>> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan  6 13:53:04 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary
>>> Directories.
>>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan  6 13:55:58 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>>
>>> Please where have I gone wrong?
>>>
>>>
>>> .
>>>
>>> Hi,
>>>
>>> It appears that you are in the /home/pi directory and hence weewxd is
>>> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>>>
>>> $ sudo weewxd /etc/weewx/weewx.conf
>>>
>>> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Copy R-pi /var/www/html/weewx directory to my weather FTP Server every hour

[Andrew Milner]

just set up a cron task.  No need to use weewx.

On Monday, 7 January 2019 07:31:02 UTC+2, David Curtis wrote:
>
> To All,
>
>  1. Is there a way to use weewx FTP or Rsync to send all the 
> var/www/html/weewx files to my weather ftp server every hour?
>
>  2. If not, what is my alternative? I'll need detailed steps due to my 
> extremely limited programming skills.
>
>   Thank you..
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Copy R-pi /var/www/html/weewx directory to my weather FTP Server every hour

[gjr80]

Alternatively, use the report_timing option 

 
and then there is no need to setup a cron :)

David, do you have FTP or rsync running and just want to change the 
frequency of uploads or do you not have any FTP/rsync functioning at all?

Gary

On Monday, 7 January 2019 16:55:13 UTC+10, Andrew Milner wrote:
>
> just set up a cron task.  No need to use weewx.
>
> On Monday, 7 January 2019 07:31:02 UTC+2, David Curtis wrote:
>>
>> To All,
>>
>>  1. Is there a way to use weewx FTP or Rsync to send all the 
>> var/www/html/weewx files to my weather ftp server every hour?
>>
>>  2. If not, what is my alternative? I'll need detailed steps due to my 
>> extremely limited programming skills.
>>
>>   Thank you..
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[gjr80]

Yes. That is a setting for the console rather than a weeWX config setting. 
You have two choices; you can set it manually via buttons on the console or 
you can set it using the wee_device 
 utility. To do the 
former you need to read the console manual :) For the latter have a look 
through the wee_device Vantage notes 
, you need to use the 
--set-offset 
action . 
Something like:

$ wee_device --set-offset=windDir,180

should do the trick, in fact that is one of the examples. Note you may or 
may not need to prefix that with sudo. Just make sure you read through the 
Vantage wee_device notes first, make sure you stop weeWX before using 
wee_device (only one thing can talk to the console at once) and check the 
setting afterwards with wee_device --info

Gary

On Monday, 7 January 2019 16:22:40 UTC+10, monmul wrote:

> Ooops! one more thing.how do I do a wind offset? I cannot see it in 
> the config file?!
>
> On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>>
>> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
>> Vantage weather station. I have a serial Envoy data logger attaced to my 
>> Rpi with a serial/usb converter. In following the set up instructions, I 
>> get these errors!
>>
>> sudo weewxd weewx.conf
>> Traceback (most recent call last):
>>   File "/usr/bin/weewxd", line 64, in 
>> weewx.engine.main(options, args)
>>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
>> sane = os.stat(config_path).st_ctime
>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
>> pi@Weatherpi:~ $ tail -f /var/log/syslog
>> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
>> sender=:1.16 path=/MediaEndpoint/A2DPSink
>> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
>> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
>> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
>> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
>> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
>> 3.8.2
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
>> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
>> Directories...
>> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
>> Directories.
>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
>> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
>> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>
>> Please where have I gone wrong?
>>
>>
>> .
>>
>> Hi,
>>
>> It appears that you are in the /home/pi directory and hence weewxd is 
>> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>>
>> $ sudo weewxd /etc/weewx/weewx.conf
>>
>> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

Ooops! one more thing.how do I do a wind offset? I cannot see it in the 
config file?!

On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>
> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
> Vantage weather station. I have a serial Envoy data logger attaced to my 
> Rpi with a serial/usb converter. In following the set up instructions, I 
> get these errors!
>
> sudo weewxd weewx.conf
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
> sane = os.stat(config_path).st_ctime
> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
> pi@Weatherpi:~ $ tail -f /var/log/syslog
> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
> sender=:1.16 path=/MediaEndpoint/A2DPSink
> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
> 3.8.2
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
> Linux-4.9.35-v7+-armv7l-with-debian-8.0
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
> Directories...
> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
> Directories.
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>
> Please where have I gone wrong?
>
>
> .
>
> Hi,
>
> It appears that you are in the /home/pi directory and hence weewxd is 
> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>
> $ sudo weewxd /etc/weewx/weewx.conf
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

Yes, thank you Gary for your help..it is very much my problem and not 
yours! I have a new power supply and wifi dongle on order...that might help!

Thanks for the digging on the WD data - will have a look at that in the 
next day or so!

On Monday, 7 January 2019 19:00:56 UTC+13, gjr80 wrote:
>
> Ok, so on the face of it weeWX appears to be running fine. Not sure what 
> problem we are solving now? My post of about 2 hours ago was in an attempt 
> to work out if your headless RPi was running weeWX but it seems that is 
> down to a wifi/dongle issue. If weeWX is running OK then WU should be fine 
> as should your generated pages - checking syslog will show you what weeWX 
> is/is not doing.
>
> As an aside, I did a bit of digging on importing historical WD data. 
> Should be relatively straightforward, have started adding to wee_import. 
> Will let you know how it goes.
>
> Gary
>
> On Monday, 7 January 2019 15:54:22 UTC+10, monmul wrote:
>>
>> This is what I get headless and with the LAN as opposed to the wifi 
>> dongle!
>>
>> pi@Weatherpi:~ $ sudo systemctl status weewx 
>> ● weewx.service - LSB: weewx weather system
>>Loaded: loaded (/etc/init.d/weewx)
>>Active: active (running) since Mon 2019-01-07 18:50:45 NZDT; 50s ago
>>   Process: 510 ExecStart=/etc/init.d/weewx start (code=exited, 
>> status=0/SUCCESS)
>>CGroup: /system.slice/weewx.service
>>└─786 python /usr/bin/weewxd --daemon 
>> --pidfile=/var/run/weewx.pid...
>>
>> Jan 07 18:50:49 Weatherpi weewx[786]: restx: AWEKAS: Posting not enabled.
>> Jan 07 18:50:49 Weatherpi weewx[786]: engine: Starting up weewx version 
>> 3.8.2
>> Jan 07 18:50:49 Weatherpi weewx[786]: engine: Clock error is -8.73 
>> seconds ...t)
>> Jan 07 18:50:49 Weatherpi weewx[786]: vantage: Clock set to 2019-01-07 
>> 18:5...0)
>> Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 
>> 18:5...b'
>> Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 
>> 18:5...b'
>> Jan 07 18:50:51 Weatherpi weewx[786]: engine: Starting main packet loop.
>> Jan 07 18:50:52 Weatherpi weewx[786]: restx: Wunderground-PWS: Published 
>> re...0)
>> Jan 07 18:50:55 Weatherpi weewx[786]: vantage: LOOP try #1; error: 
>> Expected...ad
>> Jan 07 18:51:32 Weatherpi weewx[786]: vantage: LOOP try #2; error: 
>> Expected...ad
>> Hint: Some lines were ellipsized, use -l to show in full.
>> pi@Weatherpi:~ $ 
>>
>>
>> On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>>>
>>> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
>>> Vantage weather station. I have a serial Envoy data logger attaced to my 
>>> Rpi with a serial/usb converter. In following the set up instructions, I 
>>> get these errors!
>>>
>>> sudo weewxd weewx.conf
>>> Traceback (most recent call last):
>>>   File "/usr/bin/weewxd", line 64, in 
>>> weewx.engine.main(options, args)
>>>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
>>> sane = os.stat(config_path).st_ctime
>>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
>>> pi@Weatherpi:~ $ tail -f /var/log/syslog
>>> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
>>> sender=:1.16 path=/MediaEndpoint/A2DPSink
>>> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
>>> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
>>> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
>>> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
>>> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>>> next retry is Sun Jan  6 13:41:35 2019 [try 
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx 
>>> version 3.8.2
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
>>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
>>> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>>> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
>>> Directories...
>>> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>>> next retry is Sun Jan  6 13:53:04 2019 [try 
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
>>> Directories.
>>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group 
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>>> next retry is Sun Jan  6 13:55:58 2019 [try 
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group 
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>>
>>> Please where have I gone wrong?
>>>
>>>
>>> 

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

...and this is what I get when I go back to the screen and the 
Laninstead of headless and through the wifi dongle!

pi@Weatherpi:~ $ sudo systemctl status weewx 
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (running) since Mon 2019-01-07 18:31:04 NZDT; 6min ago
  Process: 538 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
   CGroup: /system.slice/weewx.service
   └─800 python /usr/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid...

Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 
14:3...b'
Jan 07 18:38:01 Weatherpi weewx[800]: restx: Wunderground-PWS: Published 
re...0)
Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 
14:4...b'
Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 
14:4...b'
Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 
14:5...b'
Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 
14:5...b'
Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 
15:0...b'
Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 
15:0...b'
Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 
15:1...b'
Jan 07 18:38:01 Weatherpi weewx[800]: manager: Added record 2019-01-07 
15:1...b'
Hint: Some lines were ellipsized, use -l to show in full.
pi@Weatherpi:~ $ 


On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>
> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
> Vantage weather station. I have a serial Envoy data logger attaced to my 
> Rpi with a serial/usb converter. In following the set up instructions, I 
> get these errors!
>
> sudo weewxd weewx.conf
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
> sane = os.stat(config_path).st_ctime
> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
> pi@Weatherpi:~ $ tail -f /var/log/syslog
> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
> sender=:1.16 path=/MediaEndpoint/A2DPSink
> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
> 3.8.2
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
> Linux-4.9.35-v7+-armv7l-with-debian-8.0
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
> Directories...
> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
> Directories.
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>
> Please where have I gone wrong?
>
>
> .
>
> Hi,
>
> It appears that you are in the /home/pi directory and hence weewxd is 
> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>
> $ sudo weewxd /etc/weewx/weewx.conf
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[gjr80]

Ok, so on the face of it weeWX appears to be running fine. Not sure what 
problem we are solving now? My post of about 2 hours ago was in an attempt 
to work out if your headless RPi was running weeWX but it seems that is 
down to a wifi/dongle issue. If weeWX is running OK then WU should be fine 
as should your generated pages - checking syslog will show you what weeWX 
is/is not doing.

As an aside, I did a bit of digging on importing historical WD data. Should 
be relatively straightforward, have started adding to wee_import. Will let 
you know how it goes.

Gary

On Monday, 7 January 2019 15:54:22 UTC+10, monmul wrote:
>
> This is what I get headless and with the LAN as opposed to the wifi dongle!
>
> pi@Weatherpi:~ $ sudo systemctl status weewx 
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx)
>Active: active (running) since Mon 2019-01-07 18:50:45 NZDT; 50s ago
>   Process: 510 ExecStart=/etc/init.d/weewx start (code=exited, 
> status=0/SUCCESS)
>CGroup: /system.slice/weewx.service
>└─786 python /usr/bin/weewxd --daemon 
> --pidfile=/var/run/weewx.pid...
>
> Jan 07 18:50:49 Weatherpi weewx[786]: restx: AWEKAS: Posting not enabled.
> Jan 07 18:50:49 Weatherpi weewx[786]: engine: Starting up weewx version 
> 3.8.2
> Jan 07 18:50:49 Weatherpi weewx[786]: engine: Clock error is -8.73 seconds 
> ...t)
> Jan 07 18:50:49 Weatherpi weewx[786]: vantage: Clock set to 2019-01-07 
> 18:5...0)
> Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 
> 18:5...b'
> Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 
> 18:5...b'
> Jan 07 18:50:51 Weatherpi weewx[786]: engine: Starting main packet loop.
> Jan 07 18:50:52 Weatherpi weewx[786]: restx: Wunderground-PWS: Published 
> re...0)
> Jan 07 18:50:55 Weatherpi weewx[786]: vantage: LOOP try #1; error: 
> Expected...ad
> Jan 07 18:51:32 Weatherpi weewx[786]: vantage: LOOP try #2; error: 
> Expected...ad
> Hint: Some lines were ellipsized, use -l to show in full.
> pi@Weatherpi:~ $ 
>
>
> On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>>
>> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
>> Vantage weather station. I have a serial Envoy data logger attaced to my 
>> Rpi with a serial/usb converter. In following the set up instructions, I 
>> get these errors!
>>
>> sudo weewxd weewx.conf
>> Traceback (most recent call last):
>>   File "/usr/bin/weewxd", line 64, in 
>> weewx.engine.main(options, args)
>>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
>> sane = os.stat(config_path).st_ctime
>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
>> pi@Weatherpi:~ $ tail -f /var/log/syslog
>> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
>> sender=:1.16 path=/MediaEndpoint/A2DPSink
>> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
>> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
>> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
>> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
>> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
>> 3.8.2
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
>> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
>> Directories...
>> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
>> Directories.
>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
>> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
>> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>
>> Please where have I gone wrong?
>>
>>
>> .
>>
>> Hi,
>>
>> It appears that you are in the /home/pi directory and hence weewxd is 
>> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>>
>> $ sudo weewxd /etc/weewx/weewx.conf
>>
>> 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 

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

This is what I get headless and with the LAN as opposed to the wifi dongle!

pi@Weatherpi:~ $ sudo systemctl status weewx 
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (running) since Mon 2019-01-07 18:50:45 NZDT; 50s ago
  Process: 510 ExecStart=/etc/init.d/weewx start (code=exited, 
status=0/SUCCESS)
   CGroup: /system.slice/weewx.service
   └─786 python /usr/bin/weewxd --daemon 
--pidfile=/var/run/weewx.pid...

Jan 07 18:50:49 Weatherpi weewx[786]: restx: AWEKAS: Posting not enabled.
Jan 07 18:50:49 Weatherpi weewx[786]: engine: Starting up weewx version 
3.8.2
Jan 07 18:50:49 Weatherpi weewx[786]: engine: Clock error is -8.73 seconds 
...t)
Jan 07 18:50:49 Weatherpi weewx[786]: vantage: Clock set to 2019-01-07 
18:5...0)
Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 
18:5...b'
Jan 07 18:50:51 Weatherpi weewx[786]: manager: Added record 2019-01-07 
18:5...b'
Jan 07 18:50:51 Weatherpi weewx[786]: engine: Starting main packet loop.
Jan 07 18:50:52 Weatherpi weewx[786]: restx: Wunderground-PWS: Published 
re...0)
Jan 07 18:50:55 Weatherpi weewx[786]: vantage: LOOP try #1; error: 
Expected...ad
Jan 07 18:51:32 Weatherpi weewx[786]: vantage: LOOP try #2; error: 
Expected...ad
Hint: Some lines were ellipsized, use -l to show in full.
pi@Weatherpi:~ $ 


On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>
> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
> Vantage weather station. I have a serial Envoy data logger attaced to my 
> Rpi with a serial/usb converter. In following the set up instructions, I 
> get these errors!
>
> sudo weewxd weewx.conf
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
> sane = os.stat(config_path).st_ctime
> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
> pi@Weatherpi:~ $ tail -f /var/log/syslog
> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
> sender=:1.16 path=/MediaEndpoint/A2DPSink
> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
> 3.8.2
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
> Linux-4.9.35-v7+-armv7l-with-debian-8.0
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
> Directories...
> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
> Directories.
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>
> Please where have I gone wrong?
>
>
> .
>
> Hi,
>
> It appears that you are in the /home/pi directory and hence weewxd is 
> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>
> $ sudo weewxd /etc/weewx/weewx.conf
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

Ah! there seems to be a power problem with my WiF

On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>
> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
> Vantage weather station. I have a serial Envoy data logger attaced to my 
> Rpi with a serial/usb converter. In following the set up instructions, I 
> get these errors!
>
> sudo weewxd weewx.conf
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
> sane = os.stat(config_path).st_ctime
> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
> pi@Weatherpi:~ $ tail -f /var/log/syslog
> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
> sender=:1.16 path=/MediaEndpoint/A2DPSink
> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
> 3.8.2
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
> Linux-4.9.35-v7+-armv7l-with-debian-8.0
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
> Directories...
> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
> Directories.
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>
> Please where have I gone wrong?
>
>
> .
>
> Hi,
>
> It appears that you are in the /home/pi directory and hence weewxd is 
> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>
> $ sudo weewxd /etc/weewx/weewx.conf
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

Ah! there seems to be a power problem with my WiFi dongle! I will try it 
headless and on the LAN.

On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>
> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
> Vantage weather station. I have a serial Envoy data logger attaced to my 
> Rpi with a serial/usb converter. In following the set up instructions, I 
> get these errors!
>
> sudo weewxd weewx.conf
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
> sane = os.stat(config_path).st_ctime
> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
> pi@Weatherpi:~ $ tail -f /var/log/syslog
> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
> sender=:1.16 path=/MediaEndpoint/A2DPSink
> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
> 3.8.2
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
> Linux-4.9.35-v7+-armv7l-with-debian-8.0
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
> Directories...
> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
> Directories.
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>
> Please where have I gone wrong?
>
>
> .
>
> Hi,
>
> It appears that you are in the /home/pi directory and hence weewxd is 
> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>
> $ sudo weewxd /etc/weewx/weewx.conf
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[dunbrokin]

Hmmm! Something weird is happening the cat syslog will not display as far
as today and stops part way through and crashes VNC so it has to reconnect!

On Mon, Jan 7, 2019 at 6:12 PM dunbrokin  wrote:

> @Weatherpi:~ $ sudo systemctl status weewx
> ● weewx.service - LSB: weewx weather system
>Loaded: loaded (/etc/init.d/weewx)
>Active: active (exited) since Mon 2019-01-07 17:17:08 NZDT; 55min ago
>   Process: 510 ExecStart=/etc/init.d/weewx start (code=exited,
> status=0/SUCCESS)
>
> Jan 07 17:17:08 Weatherpi weewx[594]: engine: Platform
> Linux-4.9.35-v7+-arm0
> Jan 07 17:17:08 Weatherpi weewx[594]: engine: Locale is 'en_GB.UTF-8'
> Jan 07 17:17:08 Weatherpi weewx[594]: engine: pid file is
> /var/run/weewx.pid
> Jan 07 17:17:08 Weatherpi weewx[806]: engine: Using configuration file
> /etc...nf
> Jan 07 17:17:08 Weatherpi weewx[806]: engine: Loading station type Vantage
> ...e)
> Jan 07 17:17:08 Weatherpi weewx[510]: Starting weewx weather system: weewx.
> Jan 07 17:17:08 Weatherpi systemd[1]: Started LSB: weewx weather system.
> Jan 07 17:17:08 Weatherpi weewx[806]: import of driver failed: could not
> op...>)
> Jan 07 17:17:08 Weatherpi weewx[806]: engine: Unable to load driver: could
> ...0'
> Jan 07 17:17:08 Weatherpi weewx[806]:   Exiting...
> Hint: Some lines were ellipsized, use -l to show in full.
> pi@Weatherpi:~ $
>
>
> On Mon, Jan 7, 2019 at 4:38 PM gjr80  wrote:
>
>> So you are able to SSH into the RPi? Assuming you can, once the RPi has
>> booted check on the status of the weeWX daemon:
>>
>> $ sudo systemctl status weewx
>>
>> What does that show?
>>
>> Also have another look at the log. There will be a lot of stuff there
>> from when the RPi booted but you should also see some lines that have weewx
>> and a number in square brackets eg:
>>
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx
>> version 3.8.2
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 (
>> default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform Linux-4.9.35-v7+-
>> armv7l-with-debian-8.0
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>>
>> What do those entries say? Post a good deal of them or right through
>> until you see some errors from weeWX (if there are any). More is better,
>> less just leave us guessing.
>>
>> Gary
>>
>> On Monday, 7 January 2019 11:22:16 UTC+10, monmul wrote:
>>>
>>> Thanks for that Gary, I might have to park the history project for a
>>> while as I seem to have bigger problems!
>>>
>>> I had everything running nicely - updating WU and was able to see my
>>> output on index.html.and then I went headless... shutdown pulled out
>>> the screen, keyboard and mouse and rebooted.now it will not update WU
>>> nor can I see it working on
>>> file:///var/www/html/weewx/index.html.Hm! I wonder what I might
>>> have done wrong now!
>>>
>>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Copy R-pi /var/www/html/weewx directory to my weather FTP Server every hour

[David Curtis]

To All,

 1. Is there a way to use weewx FTP or Rsync to send all the 
var/www/html/weewx files to my weather ftp server every hour?

 2. If not, what is my alternative? I'll need detailed steps due to my 
extremely limited programming skills.

  Thank you..

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[dunbrokin]

@Weatherpi:~ $ sudo systemctl status weewx
● weewx.service - LSB: weewx weather system
   Loaded: loaded (/etc/init.d/weewx)
   Active: active (exited) since Mon 2019-01-07 17:17:08 NZDT; 55min ago
  Process: 510 ExecStart=/etc/init.d/weewx start (code=exited,
status=0/SUCCESS)

Jan 07 17:17:08 Weatherpi weewx[594]: engine: Platform
Linux-4.9.35-v7+-arm0
Jan 07 17:17:08 Weatherpi weewx[594]: engine: Locale is 'en_GB.UTF-8'
Jan 07 17:17:08 Weatherpi weewx[594]: engine: pid file is /var/run/weewx.pid
Jan 07 17:17:08 Weatherpi weewx[806]: engine: Using configuration file
/etc...nf
Jan 07 17:17:08 Weatherpi weewx[806]: engine: Loading station type Vantage
...e)
Jan 07 17:17:08 Weatherpi weewx[510]: Starting weewx weather system: weewx.
Jan 07 17:17:08 Weatherpi systemd[1]: Started LSB: weewx weather system.
Jan 07 17:17:08 Weatherpi weewx[806]: import of driver failed: could not
op...>)
Jan 07 17:17:08 Weatherpi weewx[806]: engine: Unable to load driver: could
...0'
Jan 07 17:17:08 Weatherpi weewx[806]:   Exiting...
Hint: Some lines were ellipsized, use -l to show in full.
pi@Weatherpi:~ $


On Mon, Jan 7, 2019 at 4:38 PM gjr80  wrote:

> So you are able to SSH into the RPi? Assuming you can, once the RPi has
> booted check on the status of the weeWX daemon:
>
> $ sudo systemctl status weewx
>
> What does that show?
>
> Also have another look at the log. There will be a lot of stuff there from
> when the RPi booted but you should also see some lines that have weewx and
> a number in square brackets eg:
>
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version
> 3.8.2
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 (default
> , Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform Linux-4.9.35-v7+-
> armv7l-with-debian-8.0
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>
> What do those entries say? Post a good deal of them or right through until
> you see some errors from weeWX (if there are any). More is better, less
> just leave us guessing.
>
> Gary
>
> On Monday, 7 January 2019 11:22:16 UTC+10, monmul wrote:
>>
>> Thanks for that Gary, I might have to park the history project for a
>> while as I seem to have bigger problems!
>>
>> I had everything running nicely - updating WU and was able to see my
>> output on index.html.and then I went headless... shutdown pulled out
>> the screen, keyboard and mouse and rebooted.now it will not update WU
>> nor can I see it working on
>> file:///var/www/html/weewx/index.html.Hm! I wonder what I might
>> have done wrong now!
>>
>> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[gjr80]

So you are able to SSH into the RPi? Assuming you can, once the RPi has 
booted check on the status of the weeWX daemon:

$ sudo systemctl status weewx

What does that show?

Also have another look at the log. There will be a lot of stuff there from 
when the RPi booted but you should also see some lines that have weewx and 
a number in square brackets eg:

Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
3.8.2
Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 (default, 
Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform Linux-4.9.35-v7+-
armv7l-with-debian-8.0
Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'

What do those entries say? Post a good deal of them or right through until 
you see some errors from weeWX (if there are any). More is better, less 
just leave us guessing.

Gary

On Monday, 7 January 2019 11:22:16 UTC+10, monmul wrote:
>
> Thanks for that Gary, I might have to park the history project for a while 
> as I seem to have bigger problems!
>
> I had everything running nicely - updating WU and was able to see my 
> output on index.html.and then I went headless... shutdown pulled out 
> the screen, keyboard and mouse and rebooted.now it will not update WU 
> nor can I see it working on 
> file:///var/www/html/weewx/index.html.Hm! I wonder what I might 
> have done wrong now!
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

RE: [weewx-user] Re: Alarm.py Help

[nineback]

Thanks for the heads up. I hardly ever use this email account (non-SSL) so was 
not aware of the problem. I updated the MX record and then tested it using the 
alarm.py file in the example directory.  Worked fine.

 

Again thanks for the help and sorry for the confusion.

 

Tom

 

 

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Sunday, January 6, 2019 10:01 AM
To: weewx-user 
Subject: Re: [weewx-user] Re: Alarm.py Help

 

It looks like the problem is that there is no DNS entry for your hostname. This 
was causing a socket.gaierror exception to be raised, which quietly terminated 
the thread. I've changed the code to catch such an exception and log it.

 

-tk

 

On Sun, Jan 6, 2019 at 7:38 AM mailto:nineb...@gmail.com> 
> wrote:

Sent.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Sunday, January 6, 2019 9:33 AM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Possibly, but I don't think so. The library smtplib uses a default of 465 for 
attempting SSL connections. Also, even if one attempted to connect using the 
wrong port, it should still time out. Which it didn't.

 

Can you send the host name of the non-SSL server by private email? I don't need 
the user name and password. 

 

tkeffer at gmail.com 

 

 

-tk

 

On Sun, Jan 6, 2019 at 7:27 AM mailto:nineb...@gmail.com> 
> wrote:

It is the mail server provided by my ISP, inmotionhosting.com 

 .  No exception was raised.  Could it be something to do with the port?  I 
noticed in the setup that there was no way to designate a port.

 

SSL:

Outgoing Server:  secure246.inmotionhosting.com 

SMTP Port: 465

 

Non-SSL:

Outgoing Server:  mail.XXX.com 

  SMTP Port: 587

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Sunday, January 6, 2019 6:51 AM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

OK, but I wish we knew what the trouble was.

 

The last version had a 20 second 'timeout': if the server didn't respond, an 
exception should have been raised. Sounds like that didn't happen.

 

What was the non-SSL server you were using?

 

-tk

 

On Sat, Jan 5, 2019 at 6:59 PM mailto:nineb...@gmail.com> 
> wrote:

OK.  I got it working by changing my server to one requiring SSL.  I was using 
a non-SSL server and the latest version you sent still would not work.  I also 
tried Gmail SMTP and it works.  The “issue” seems to be with non-SSL servers.  
I usually find it the other way around.

 

I tried the original example alarm.py using an SSL server and it works so I 
think this confirms my ”issue” is with non-SSL servers.

 

Sorry for all the trouble.  I am happy to use the SSL server.

 

Many thanks.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 8:22 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Looks like your smtp server hangs if you try to connect to it using SSL. Try 
this version. 

 

-tk

 

On Sat, Jan 5, 2019 at 5:23 PM mailto:nineb...@gmail.com> 
> wrote:

As requested.

 

Thanks for helping.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 6:58 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Hmmm. Try this version. It has been heavily instrumented. Again, run with 
debug=1. Make sure you restart WeeWX.

 

-tk

 

On Sat, Jan 5, 2019 at 4:46 PM mailto:nineb...@gmail.com> 
> wrote:

I used the alarm.py version that you sent the link to.  I 

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

This is what the syslog is telling me

Jan  7 15:04:21 Weatherpi kernel: [ 4429.981076] usb 1-1: New USB device 
found, idVendor=0424, idProduct=9514
Jan  7 15:04:21 Weatherpi kernel: [ 4429.981091] usb 1-1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
Jan  7 15:04:21 Weatherpi kernel: [ 4429.982079] hub 1-1:1.0: USB hub found
Jan  7 15:04:21 Weatherpi kernel: [ 4429.982189] hub 1-1:1.0: 5 ports 
detected
Jan  7 15:04:21 Weatherpi kernel: [ 4430.300691] usb 1-1.1: new high-speed 
USB device number 56 using dwc_otg
Jan  7 15:04:22 Weatherpi kernel: [ 4430.431143] usb 1-1.1: New USB device 
found, idVendor=0424, idProduct=ec00
Jan  7 15:04:22 Weatherpi kernel: [ 4430.431160] usb 1-1.1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
Jan  7 15:04:22 Weatherpi kernel: [ 4430.441007] smsc95xx v1.0.5
Jan  7 15:04:22 Weatherpi systemd-udevd[3160]: failed to execute 
'/lib/udev/mtp-probe' 'mtp-probe 
/sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.1 1 56': No such file 
or directory
Jan  7 15:04:22 Weatherpi kernel: [ 4430.545142] smsc95xx 1-1.1:1.0 eth0: 
register 'smsc95xx' at usb-3f98.usb-1.1, smsc95xx USB 2.0 Ethernet, 
b8:27:eb:00:74:cf
Jan  7 15:04:22 Weatherpi kernel: [ 4430.545503] usb 1-1-port2: 
over-current change
Jan  7 15:04:22 Weatherpi kernel: [ 4430.790726] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:22 Weatherpi kernel: [ 4430.790760] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:22 Weatherpi kernel: [ 4430.790785] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:22 Weatherpi kernel: [ 4430.790845] hub 1-1:1.0: 
hub_ext_port_status failed (err = -71)
Jan  7 15:04:22 Weatherpi avahi-daemon[440]: Withdrawing workstation 
service for eth0.
Jan  7 15:04:22 Weatherpi kernel: [ 4430.810779] usb 1-1: USB disconnect, 
device number 55
Jan  7 15:04:22 Weatherpi kernel: [ 4430.810796] usb 1-1.1: USB disconnect, 
device number 56
Jan  7 15:04:22 Weatherpi kernel: [ 4430.811122] smsc95xx 1-1.1:1.0 eth0: 
unregister 'smsc95xx' usb-3f98.usb-1.1, smsc95xx USB 2.0 Ethernet
Jan  7 15:04:22 Weatherpi kernel: [ 4431.080820] Indeed it is in host mode 
hprt0 = 00021501
Jan  7 15:04:22 Weatherpi kernel: [ 4431.290672] usb 1-1: new high-speed 
USB device number 57 using dwc_otg
Jan  7 15:04:22 Weatherpi kernel: [ 4431.290824] Indeed it is in host mode 
hprt0 = 1101
Jan  7 15:04:23 Weatherpi kernel: [ 4431.530986] usb 1-1: New USB device 
found, idVendor=0424, idProduct=9514
Jan  7 15:04:23 Weatherpi kernel: [ 4431.531002] usb 1-1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
Jan  7 15:04:23 Weatherpi kernel: [ 4431.532050] hub 1-1:1.0: USB hub found
Jan  7 15:04:23 Weatherpi kernel: [ 4431.532190] hub 1-1:1.0: 5 ports 
detected
Jan  7 15:04:23 Weatherpi kernel: [ 4431.640835] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:23 Weatherpi kernel: [ 4431.640878] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:23 Weatherpi kernel: [ 4431.640903] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:23 Weatherpi kernel: [ 4431.640968] hub 1-1:1.0: 
hub_ext_port_status failed (err = -71)
Jan  7 15:04:23 Weatherpi kernel: [ 4431.641029] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:23 Weatherpi kernel: [ 4431.641048] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:23 Weatherpi kernel: [ 4431.641068] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:23 Weatherpi kernel: [ 4431.641123] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:23 Weatherpi kernel: [ 4431.641142] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:23 Weatherpi kernel: [ 4431.641165] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:23 Weatherpi kernel: [ 4431.641206] usb 1-1: Failed to suspend 
device, error -71
Jan  7 15:04:23 Weatherpi kernel: [ 4431.800893] usb 1-1: USB disconnect, 
device number 57
Jan  7 15:04:23 Weatherpi kernel: [ 4432.000866] Indeed it is in host mode 
hprt0 = 00021501
Jan  7 15:04:23 Weatherpi kernel: [ 4432.200714] usb 1-1: new high-speed 
USB device number 58 using dwc_otg
Jan  7 15:04:23 Weatherpi kernel: [ 4432.200895] Indeed it is in host mode 
hprt0 = 1101
Jan  7 15:04:24 Weatherpi kernel: [ 4432.430976] usb 1-1: New USB device 
found, idVendor=0424, idProduct=9514
Jan  7 15:04:24 Weatherpi kernel: [ 4432.430991] usb 1-1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
Jan  7 15:04:24 Weatherpi kernel: [ 4432.431949] hub 1-1:1.0: USB hub found
Jan  7 15:04:24 Weatherpi kernel: [ 4432.432059] hub 1-1:1.0: 5 ports 
detected
Jan  7 15:04:24 Weatherpi kernel: [ 4432.550724] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:24 Weatherpi kernel: [ 4432.550755] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:24 Weatherpi kernel: [ 4432.550775] NYET/NAK/ACK/other in 
non-error case, 0x0002
Jan  7 15:04:24 Weatherpi kernel: [ 4432.550855] hub 1-1:1.0: 

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[monmul]

Duh! thanks Gary!

On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>
> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
> Vantage weather station. I have a serial Envoy data logger attaced to my 
> Rpi with a serial/usb converter. In following the set up instructions, I 
> get these errors!
>
> sudo weewxd weewx.conf
> Traceback (most recent call last):
>   File "/usr/bin/weewxd", line 64, in 
> weewx.engine.main(options, args)
>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
> sane = os.stat(config_path).st_ctime
> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
> pi@Weatherpi:~ $ tail -f /var/log/syslog
> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
> sender=:1.16 path=/MediaEndpoint/A2DPSink
> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version 
> 3.8.2
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
> Linux-4.9.35-v7+-armv7l-with-debian-8.0
> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
> Directories...
> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
> Directories.
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>  ]
> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying 
> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>
> Please where have I gone wrong?
>
>
> .
>
> Hi,
>
> It appears that you are in the /home/pi directory and hence weewxd is 
> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>
> $ sudo weewxd /etc/weewx/weewx.conf
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[dunbrokin]

Thanks for that Gary, I might have to park the history project for a while
as I seem to have bigger problems!

I had everything running nicely - updating WU and was able to see my output
on index.html.and then I went headless... shutdown pulled out the
screen, keyboard and mouse and rebooted.now it will not update WU nor
can I see it working on file:///var/www/html/weewx/index.html.Hm! I
wonder what I might have done wrong now!

On Mon, Jan 7, 2019 at 12:22 PM gjr80  wrote:

> WeeWX stores its data in the archive table in your weewx database, one
> archive record per row. A summary table is created for each observation
> field that records daily highs/lows/sums, counts and times etc. These
> summary tables are used as an optimization strategy when aggregates are
> sought from the historical data. There are a couple of ways to import data.
> the first is the use of the weeWX utility wee_import
> , this is the
> preferred way to import data but it only supports importing data from a CSV
> format file, Cumulus monthly log files and Weatherunderground. The other
> approach is to manually add rows to the archive table and then rebuild the
> daily summaries. Rebuilding the daily summaries is easy using wee_database
> , adding rows
> to the archive will be a slow manual process. You may think that adding
> highs/lows to the daily summaries is a solution, it is not.
>
> In terms of importing your WD data I guess the options are limited, I have
> little WD knowledge but if you can get the data into one of the formats
> supported by wee_import that would work (if you google the weewx forums
> this has come up once or twice before, not sure if there was a third party
> utility that converted WD data into a format that wee_import supports).
> Manually adding data is going to take a long time considering you have 5
> years of data. I have had a task to add WD support to wee_import for some
> time now, there has been little call for it so it has taken a back seat. I
> am happy to look into this again, it won't happen today or tomorrow but
> then again that is the beauty of importing historical data, the data is not
> going anywhere so the time imperative is not there. If I have some details
> about the data structure and format I can look at what be done with
> wee_import.
>
> A word of warning, manipulating the weeWX database manually can be
> hazardous to the continued good and proper operation of weeWX, do so at
> your own risk and always make sure you have a backup of your database.
>
> Gary
>
> On Monday, 7 January 2019 06:40:23 UTC+10, monmul wrote:
>>
>> Next issue for me is to import historic information (about 5 years
>> worth...or just the highs and lows during that period of each measured
>> item) into weewx? Where is the historic information stored and is there an
>> easy way of importing the data from WeatherDisplay?
>>
>> On Mon, Jan 7, 2019 at 9:35 AM dunbrokin  wrote:
>>
>>> Right I have 10.1.1.1 and 8.8.4.4 as "nameserver"  (while shown as
>>> "name_servers" in the resolvconf.conf file) in the resolv.conf fileI
>>> presume that will do the job?
>>>
>>>
>>> On Mon, Jan 7, 2019 at 9:32 AM Scott Grayban  wrote:
>>>
 Ahh I didn't know that. I don't install resolvconfd.
 On Jan 6, 2019, at 12:30 PM, dunbrokin  wrote:
>
> Using nameserver instead of name_server means that none of them appear
> in the resolv.conf file!
>
> On Mon, Jan 7, 2019 at 9:27 AM dunbrokin < dunb...@gmail.com> wrote:
>
>> OK will do again. Just looked in the resolv.,conf file.I get
>> nameserver 8.8.4.4 but not the 8.8.8.8!
>>
>> On Mon, Jan 7, 2019 at 9:23 AM Scott Grayban < sgra...@gmail.com>
>> wrote:
>>
>>> Use
>>>
>>> nameserver not name_server
>>> On Jan 6, 2019, at 12:20 PM, dunbrokin < dunb...@gmail.com> wrote:

 Thank you so much for your help Scott!

 On Mon, Jan 7, 2019 at 9:14 AM Scott Grayban < sgra...@gmail.com>
 wrote:

> If it works yes.
> On Jan 6, 2019, at 12:11 PM, dunbrokin < dunb...@gmail.com>
> wrote:
>>
>> Great, thanks, will do.does this now get around the
>> installation of NTP daemon as recommended in the set up instructions?
>>
>> On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban < sgra...@gmail.com>
>> wrote:
>>
>>> Ok replace that with this then reboot the PI and look at your
>>> weewx log again for the ntp sync.
>>>
>>> After reboot your  */etc/resolv.conf* should have those name
>>> servers listed
>>>
>>> # Configuration for resolvconf(8)
>>> # See resolvconf.conf(5) for details
>>>
>>> resolv_conf=/etc/resolv.conf
>>> # If you run a local name server, you should uncomment the below

[weewx-user] Re: instantaneous rain vs averaged

[Adam Harvey]

Hopefully it rains this afternoon...

On Friday, 4 January 2019 19:29:29 UTC+10, Adam Harvey wrote:
>
> Hi, I have a raspberry pi with weewx installed.  Outside I  have a Davis 
> vantage vue, I have a connection from the davis console to the rpi.  
>
> All works well, except, the rain rates seem averaged out, I notice some 
> nearby stations seem to get higher instantaneous rates.
>
> I'm struggling to understand the loop vs archive, is that the change I 
> need to make?
>
> thanks in advance for any assistance. 
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[gjr80]

WeeWX stores its data in the archive table in your weewx database, one 
archive record per row. A summary table is created for each observation 
field that records daily highs/lows/sums, counts and times etc. These 
summary tables are used as an optimization strategy when aggregates are 
sought from the historical data. There are a couple of ways to import data. 
the first is the use of the weeWX utility wee_import 
, this is the 
preferred way to import data but it only supports importing data from a CSV 
format file, Cumulus monthly log files and Weatherunderground. The other 
approach is to manually add rows to the archive table and then rebuild the 
daily summaries. Rebuilding the daily summaries is easy using wee_database 
, adding rows to 
the archive will be a slow manual process. You may think that adding 
highs/lows to the daily summaries is a solution, it is not.

In terms of importing your WD data I guess the options are limited, I have 
little WD knowledge but if you can get the data into one of the formats 
supported by wee_import that would work (if you google the weewx forums 
this has come up once or twice before, not sure if there was a third party 
utility that converted WD data into a format that wee_import supports). 
Manually adding data is going to take a long time considering you have 5 
years of data. I have had a task to add WD support to wee_import for some 
time now, there has been little call for it so it has taken a back seat. I 
am happy to look into this again, it won't happen today or tomorrow but 
then again that is the beauty of importing historical data, the data is not 
going anywhere so the time imperative is not there. If I have some details 
about the data structure and format I can look at what be done with 
wee_import.

A word of warning, manipulating the weeWX database manually can be 
hazardous to the continued good and proper operation of weeWX, do so at 
your own risk and always make sure you have a backup of your database.

Gary

On Monday, 7 January 2019 06:40:23 UTC+10, monmul wrote:
>
> Next issue for me is to import historic information (about 5 years 
> worth...or just the highs and lows during that period of each measured 
> item) into weewx? Where is the historic information stored and is there an 
> easy way of importing the data from WeatherDisplay?
>
> On Mon, Jan 7, 2019 at 9:35 AM dunbrokin > 
> wrote:
>
>> Right I have 10.1.1.1 and 8.8.4.4 as "nameserver"  (while shown as 
>> "name_servers" in the resolvconf.conf file) in the resolv.conf fileI 
>> presume that will do the job?
>>
>>
>> On Mon, Jan 7, 2019 at 9:32 AM Scott Grayban > > wrote:
>>
>>> Ahh I didn't know that. I don't install resolvconfd.
>>> On Jan 6, 2019, at 12:30 PM, dunbrokin > 
>>> wrote:

 Using nameserver instead of name_server means that none of them appear 
 in the resolv.conf file! 

 On Mon, Jan 7, 2019 at 9:27 AM dunbrokin < dunb...@gmail.com 
 > wrote: 

> OK will do again. Just looked in the resolv.,conf file.I get 
> nameserver 8.8.4.4 but not the 8.8.8.8! 
>
> On Mon, Jan 7, 2019 at 9:23 AM Scott Grayban < sgra...@gmail.com 
> > wrote: 
>
>> Use 
>>
>> nameserver not name_server 
>> On Jan 6, 2019, at 12:20 PM, dunbrokin < dunb...@gmail.com 
>> > wrote: 
>>>
>>> Thank you so much for your help Scott! 
>>>
>>> On Mon, Jan 7, 2019 at 9:14 AM Scott Grayban < sgra...@gmail.com 
>>> > wrote: 
>>>
 If it works yes. 
 On Jan 6, 2019, at 12:11 PM, dunbrokin < dunb...@gmail.com 
 > wrote: 
>
> Great, thanks, will do.does this now get around the 
> installation of NTP daemon as recommended in the set up instructions? 
>
> On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban < sgra...@gmail.com 
> > wrote: 
>
>> Ok replace that with this then reboot the PI and look at your 
>> weewx log again for the ntp sync. 
>>
>> After reboot your  */etc/resolv.conf* should have those name 
>> servers listed 
>>
>> # Configuration for resolvconf(8) 
>> # See resolvconf.conf(5) for details 
>>
>> resolv_conf=/etc/resolv.conf 
>> # If you run a local name server, you should uncomment the below 
>> line and 
>> # configure your subscribers configuration files below. 
>> #nameserver 127.0.0.1 
>> nameserver 8.8.8.8 
>> nameserver 8.8.4.4 
>>
>> # Mirror the Debian package defaults for the below resolvers 
>> # so that resolvconf integrates seemlessly. 
>> dnsmasq_resolv=/var/run/dnsmasq/resolv.conf 
>> pdnsd_conf=/etc/pdnsd.conf 
>> unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf 
>>
>> -- 
>> You 

[weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[gjr80]

Just to be clear I was just pointing out that the two places to look for 
info on what weeWX is doing is the console output when running weeWX 
directly  (this 
shows the data coming from the station) and the log (this shows config 
(during startup) and any errors that may be logged). I was not necessarily 
expecting to see any errors in your log.

Seeing as you are using a Vantage station you should be seeing loop packets 
every 2 odd seconds.  Given the small screen capture showing just 2 loop 
packets only that were 5 seconds apart with the wakeup message between that 
would cause me to look more closely to see if you are somehow dropping loop 
packets. How often does that wakeup message appear and does it result in a 
dropped loop packet each time, if it occurs once a day it probably makes 
little difference, every second loop packet perhaps more of a difference 
(depends on your config). If you wanted to look into it further my 
suggestion was to provide a larger screen capture when running weeWX 
directly so we could gauge the extent of the issue (those wakeup log 
entries should also appear in the log - how often do they occur). Of course 
if you are not concerned about the wakeup /missing loop packets then you 
need do nothing :)

Gary

On Sunday, 6 January 2019 15:39:44 UTC+10, monmul wrote:
>
> This is all I could find on the syslogno errors given so I will ignore 
> the LOOP etc
>
> Jan  6 18:25:20 Weatherpi weewx[831]: engine: Loading station type Vantage 
> (weewx.drivers.vantage)
> Jan  6 18:25:20 Weatherpi weewx[831]: import of driver failed: [Errno 11] 
> Resource temporarily unavailable ()
> Jan  6 18:25:20 Weatherpi weewx[688]: vantage: No  received from 
> console
> Jan  6 18:25:20 Weatherpi weewx[831]: engine: Unable to load driver: 
> [Errno 11] Resource temporarily unavailable
> Jan  6 18:25:20 Weatherpi weewx[831]:   Exiting...
> Jan  6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: 
> 0.debian.pool.ntp.org
> Jan  6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: 
> 1.debian.pool.ntp.org
> Jan  6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: 
> 2.debian.pool.ntp.org
> Jan  6 18:25:20 Weatherpi ntpd_intres[684]: host name not found: 
> 3.debian.pool.ntp.org
> Jan  6 18:25:20 Weatherpi weewx[688]: vantage: No  received from 
> console
> Jan  6 18:25:20 Weatherpi weewx[688]: vantage: No  received from 
> console
> Jan  6 18:25:20 Weatherpi avahi-daemon[468]: Joining mDNS multicast group 
> on interface eth0.IPv6 with address fe80::1cc0:5dfe:d383:8c98.
> Jan  6 18:25:20 Weatherpi avahi-daemon[468]: New relevant interface 
> eth0.IPv6 for mDNS.
>
>
> On Sunday, 6 January 2019 17:52:24 UTC+13, gjr80 wrote:
>>
>> On Sunday, 6 January 2019 14:20:09 UTC+10, monmul wrote:
>>>
>>> Hmmm! I would have to pass on that oneI am not sure I even know what 
>>> it means.is it something I set up when following the instructions about 
>>> installing nginx?
>>>
>>> Ok, you posted a screen capture with a couple of loop packets (the lines 
>> starting with LOOP: ). This was part of the output you would have seen when 
>> you ran weewx directly using sudo weewxd /etc/weewx/weewx.conf. Since 
>> you only showed us a couple of loop packets things could be running fine, 
>> its hard to say with such a small snapshot. The loop packets were 5 seconds 
>> apart, if you station emits loop packets every 5 seconds then this is fine, 
>> if it emits loop packets every 2 seconds then maybe there is an issue. 
>> Having a look at a good couple of archive periods of output would give a 
>> better feel for things rather than just a couple of loop packets. We would 
>> also see some archive records (they occur once per archive period) and 
>> start with REC: on screen. Would also be handy to know the station 
>> type/model.
>>
>> You might want to have a read through Loop packets vs. archive records 
>> 
>>  
>> in the Customization Guide  - it 
>> will give you a bit of background. Also, have a look at your log (likely 
>> /var/log/syslog) from when you start weeWX, you will see a whole pile of 
>> info there as to how your station and weeWX are configured. teh log is good 
>> for seeing startup config and events as they happen (including errors). 
>> Screen output from running weeWX directly is handy for seeing the actual 
>> data weeWX gets off the station.
>>
>> nginx will have nothing to do it, nginx is purely serving web pages/data 
>> to your browser, the sleeping/retrying etc is weeWX interacting with your 
>> weather station.
>>  
>>
>>> One other thingI have not done anything about setting up the NTP 
>>> Daemon thingdo I need to do that also?
>>>
>>
>> Horses for courses. If it were me I would get NTP setup and working 
>> properly. Correct time is critical for weeWX to 

Re: [weewx-user] Uploading to WeatherCloud?

[Jeff Ross]

Thanks for the suggestion!

I got the same 429 response you did, which makes no sense to me unless they 
are counting all the failed uploads as valid requests.  I've been getting 
"Station off line" e-mails from weathercloud.net every 6 hours.

I used tcpdump to capture the actual traffic from the browser to 
weathercloud,net and it shows that although 429 is printed to the screen,  
the message that comes back is the same HTTP/1.1 400 Bad Request.

Still a mystery to debug it seems but now I know it's something on my end 
and not system wide.

Jeff

On Sunday, January 6, 2019 at 9:21:16 AM UTC-7, Thomas Keffer wrote:
>
> My uploader seems to be working fine.
>
> I also tried the URL you provided using my id and key, and it seems to 
> work. At least, it responded with a 429 error ("Too many requests"), which 
> sounds about right.
>
> Try using the URL (with the correct key) in a browser and see what comes 
> back.
>
> -tk
>
> On Sun, Jan 6, 2019 at 8:14 AM Jeff Ross > 
> wrote:
>
>> Hi all,
>>
>> I've installed the weathercloud driver according to the instructions 
>> WeatherCloud sent when I requested the docs for the API.
>>
>> https://weathercloud.net/info/weewx
>>
>> It mostly fails to upload data though--here's a section of debug logs:
>>
>> 2019-01-06 09:05:47.992719500 127.0.0.1: user.debug: Jan 6 09:05:47 
>> weewx[64490]: restx: WeatherCloud: url: 
>> http://api.weathercloud.net/v01/set?wid=444b000107d31735=71=103=41=0=20=0=3.8.2=457=16=251=208=104=60=0=32=XXX=20190106=16=19=8597=32=208=-39=1605=0
>> 2019-01-06 09:05:48.379906500 127.0.0.1: user.debug: Jan 6 09:05:48 
>> weewx[64490]: restx: WeatherCloud: Failed upload attempt 1: HTTP Error 400: 
>> Bad Request
>> 2019-01-06 09:06:53.400736500 127.0.0.1: user.debug: Jan 6 09:06:53 
>> weewx[64490]: restx: WeatherCloud: Failed upload attempt 2: > timed out>
>> 2019-01-06 09:06:57.950420500 127.0.0.1: user.debug: Jan 6 09:06:57 
>> weewx[64490]: interceptor: MainThread: empty queue
>> 2019-01-06 09:07:00.513001500 127.0.0.1: user.debug: Jan 6 09:07:00 
>> weewx[64490]: restx: WeatherCloud: Failed upload attempt 3: HTTP Error 400: 
>> Bad Request
>> 2019-01-06 09:07:05.520782500 127.0.0.1: user.err: Jan 6 09:07:05 
>> weewx[64490]: restx: WeatherCloud: Failed to publish record 2019-01-06 
>> 09:05:00 MST (1546790700): Failed upload after 3 tries
>>
>> Once in a great while I get a successful upload but I'd say 99% of the 
>> time I get the HTTP Error 400.
>>
>> Anyone else having a problem with WeatherCloud?
>>
>> Thanks,
>>
>> Jeff Ross
>> Townsend, MT
>>
>> -- 
>> 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 .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: use Weewx on raspberry

[gjr80]

Hi Patrick,

Judging by the number it looks like a pressure in hPa is being interpreted 
as a pressure in inHg. The solution depends on a number of things. Since 
there has been a bit of water under the bridge, in particular a reinstall 
of weeWX, since you last posted your code could I ask you to post your 
driver code and a sanitised (ie passwords, api keys, user names removed) 
copy of weewx.conf.

Gary

On Monday, 7 January 2019 05:51:47 UTC+10, Patrick Tranchant wrote:
>
> hello Pat and Gary
> I reinstalled weewx with Sqlite3 and I see value in database, but some 
> datas are bad, 
> I think at " driver BYOWS"
>
> example: Jan  6 20:46:43 raspberrypi weewx[2807]: engine: 2019-01-06 
> 20:46:43 CET (1546804003) LOOP value 'pressure' 1019.4978 outside 
> limits (24.0, 34.5)
> this data with my script is correct, wy outside limit, the display in the 
> website is bad also..
> An other file to modify ?
> I modified the datas inside file skin.conf
> [[Units]
> # This section is for managing the selection and formatting of units.
>
> [[Groups]]
> # For each group of measurements, this section sets what units to
> # use for it.
> # NB: The unit is always in the singular. I.e., 'mile_per_hour',
> # NOT 'miles_per_hour'
>
> group_altitude = meter # Options are 'foot' or 
> 'meter'
> group_degree_day   = degree_C_day # Options are 
> 'degree_F_day' or 'degree_C_day'
> group_direction= degree_compass
> group_moisture = centibar
> group_percent  = percent
> group_pressure = hPa # Options are 'inHg', 
> 'mmHg', 'mbar', or 'hPa'
> group_radiation= watt_per_meter_squared
> group_rain = mm # Options are 'inch', 
> 'cm', or 'mm'
> group_rainrate = mm_per_hour# Options are 
> 'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
> group_speed= km_per_hour# Options are 
> 'mile_per_hour', 'km_per_hour', 'knot', or 'meter_per_second'
> group_speed2   = km_per_hour2   # Options are 
> 'mile_per_hour2', 'km_per_hour2', 'knot2', or 'meter_per_second2'
> group_temperature  = degree_C # Options are 'degree_F' 
> or 'degree_C'
> group_uv   = uv_index
> group_volt = volt
> ]
>
> thanks
>
> Patrick
>
> On Saturday, December 8, 2018 at 3:40:43 PM UTC+1, Patrick Tranchant wrote:
>>
>> hello I am a newbie from France ( sorry for my english )
>>
>> I want to use weewx on a raspberry with a weather station built by myself 
>> (view on Magpi)
>> I don't see my station on your website to configure :
>>
>> Weather Station Hardware Comparison: I don't found my weather station.
>> Do you have a solution or how to configure Weewx
>>
>> thank you for your help
>>
>> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[dunbrokin]

Thank you for all your help Scott in getting me up and running.I
really appreciate it. Hopefully some other kind soul can come to the party
for the next step!

On Mon, Jan 7, 2019 at 9:42 AM Scott Grayban  wrote:

> That I can't help with. Sorry
> On Jan 6, 2019, at 12:40 PM, dunbrokin  wrote:
>>
>> Next issue for me is to import historic information (about 5 years
>> worth...or just the highs and lows during that period of each measured
>> item) into weewx? Where is the historic information stored and is there an
>> easy way of importing the data from WeatherDisplay?
>>
>> On Mon, Jan 7, 2019 at 9:35 AM dunbrokin < dunbro...@gmail.com> wrote:
>>
>>> Right I have 10.1.1.1 and 8.8.4.4 as "nameserver"  (while shown as
>>> "name_servers" in the resolvconf.conf file) in the resolv.conf fileI
>>> presume that will do the job?
>>>
>>>
>>> On Mon, Jan 7, 2019 at 9:32 AM Scott Grayban < sgray...@gmail.com>
>>> wrote:
>>>
 Ahh I didn't know that. I don't install resolvconfd.
 On Jan 6, 2019, at 12:30 PM, dunbrokin < dunbro...@gmail.com> wrote:
>
> Using nameserver instead of name_server means that none of them appear
> in the resolv.conf file!
>
> On Mon, Jan 7, 2019 at 9:27 AM dunbrokin < dunbro...@gmail.com>
> wrote:
>
>> OK will do again. Just looked in the resolv.,conf file.I get
>> nameserver 8.8.4.4 but not the 8.8.8.8!
>>
>> On Mon, Jan 7, 2019 at 9:23 AM Scott Grayban < sgray...@gmail.com>
>> wrote:
>>
>>> Use
>>>
>>> nameserver not name_server
>>> On Jan 6, 2019, at 12:20 PM, dunbrokin < dunbro...@gmail.com>
>>> wrote:

 Thank you so much for your help Scott!

 On Mon, Jan 7, 2019 at 9:14 AM Scott Grayban < sgray...@gmail.com>
 wrote:

> If it works yes.
> On Jan 6, 2019, at 12:11 PM, dunbrokin < dunbro...@gmail.com>
> wrote:
>>
>> Great, thanks, will do.does this now get around the
>> installation of NTP daemon as recommended in the set up instructions?
>>
>> On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban < sgray...@gmail.com>
>> wrote:
>>
>>> Ok replace that with this then reboot the PI and look at your
>>> weewx log again for the ntp sync.
>>>
>>> After reboot your  */etc/resolv.conf* should have those name
>>> servers listed
>>>
>>> # Configuration for resolvconf(8)
>>> # See resolvconf.conf(5) for details
>>>
>>> resolv_conf=/etc/resolv.conf
>>> # If you run a local name server, you should uncomment the below
>>> line and
>>> # configure your subscribers configuration files below.
>>> #nameserver 127.0.0.1
>>> nameserver 8.8.8.8
>>> nameserver 8.8.4.4
>>>
>>> # Mirror the Debian package defaults for the below resolvers
>>> # so that resolvconf integrates seemlessly.
>>> dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
>>> pdnsd_conf=/etc/pdnsd.conf
>>> unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
>>>
>>> --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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/LGS3xtzmot0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
 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.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>> You 

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[Scott Grayban]

That I can't help with. Sorry

On Jan 6, 2019, 12:40 PM, at 12:40 PM, dunbrokin  wrote:
>Next issue for me is to import historic information (about 5 years
>worth...or just the highs and lows during that period of each measured
>item) into weewx? Where is the historic information stored and is there
>an
>easy way of importing the data from WeatherDisplay?
>
>On Mon, Jan 7, 2019 at 9:35 AM dunbrokin  wrote:
>
>> Right I have 10.1.1.1 and 8.8.4.4 as "nameserver"  (while shown as
>> "name_servers" in the resolvconf.conf file) in the resolv.conf
>fileI
>> presume that will do the job?
>>
>>
>> On Mon, Jan 7, 2019 at 9:32 AM Scott Grayban 
>wrote:
>>
>>> Ahh I didn't know that. I don't install resolvconfd.
>>> On Jan 6, 2019, at 12:30 PM, dunbrokin  wrote:

 Using nameserver instead of name_server means that none of them
>appear
 in the resolv.conf file!

 On Mon, Jan 7, 2019 at 9:27 AM dunbrokin < dunbro...@gmail.com>
>wrote:

> OK will do again. Just looked in the resolv.,conf file.I get
> nameserver 8.8.4.4 but not the 8.8.8.8!
>
> On Mon, Jan 7, 2019 at 9:23 AM Scott Grayban < sgray...@gmail.com>
> wrote:
>
>> Use
>>
>> nameserver not name_server
>> On Jan 6, 2019, at 12:20 PM, dunbrokin < dunbro...@gmail.com>
>wrote:
>>>
>>> Thank you so much for your help Scott!
>>>
>>> On Mon, Jan 7, 2019 at 9:14 AM Scott Grayban <
>sgray...@gmail.com>
>>> wrote:
>>>
 If it works yes.
 On Jan 6, 2019, at 12:11 PM, dunbrokin < dunbro...@gmail.com>
 wrote:
>
> Great, thanks, will do.does this now get around the
> installation of NTP daemon as recommended in the set up
>instructions?
>
> On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban <
>sgray...@gmail.com>
> wrote:
>
>> Ok replace that with this then reboot the PI and look at your
>> weewx log again for the ntp sync.
>>
>> After reboot your  */etc/resolv.conf* should have those name
>> servers listed
>>
>> # Configuration for resolvconf(8)
>> # See resolvconf.conf(5) for details
>>
>> resolv_conf=/etc/resolv.conf
>> # If you run a local name server, you should uncomment the
>below
>> line and
>> # configure your subscribers configuration files below.
>> #nameserver 127.0.0.1
>> nameserver 8.8.8.8
>> nameserver 8.8.4.4
>>
>> # Mirror the Debian package defaults for the below resolvers
>> # so that resolvconf integrates seemlessly.
>> dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
>> pdnsd_conf=/etc/pdnsd.conf
>> unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
 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.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
 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/LGS3xtzmot0/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 weewx-user+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>
>-- 
>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/LGS3xtzmot0/unsubscribe.
>To unsubscribe from this group and all its topics, send an email to
>weewx-user+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.

-- 
You 

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[Scott Grayban]

It should

On Jan 6, 2019, 12:36 PM, at 12:36 PM, dunbrokin  wrote:
>Right I have 10.1.1.1 and 8.8.4.4 as "nameserver"  (while shown as
>"name_servers" in the resolvconf.conf file) in the resolv.conf
>fileI
>presume that will do the job?
>
>
>On Mon, Jan 7, 2019 at 9:32 AM Scott Grayban 
>wrote:
>
>> Ahh I didn't know that. I don't install resolvconfd.
>> On Jan 6, 2019, at 12:30 PM, dunbrokin  wrote:
>>>
>>> Using nameserver instead of name_server means that none of them
>appear in
>>> the resolv.conf file!
>>>
>>> On Mon, Jan 7, 2019 at 9:27 AM dunbrokin < dunbro...@gmail.com>
>wrote:
>>>
 OK will do again. Just looked in the resolv.,conf file.I get
 nameserver 8.8.4.4 but not the 8.8.8.8!

 On Mon, Jan 7, 2019 at 9:23 AM Scott Grayban < sgray...@gmail.com>
 wrote:

> Use
>
> nameserver not name_server
> On Jan 6, 2019, at 12:20 PM, dunbrokin < dunbro...@gmail.com>
>wrote:
>>
>> Thank you so much for your help Scott!
>>
>> On Mon, Jan 7, 2019 at 9:14 AM Scott Grayban <
>sgray...@gmail.com>
>> wrote:
>>
>>> If it works yes.
>>> On Jan 6, 2019, at 12:11 PM, dunbrokin < dunbro...@gmail.com>
>wrote:

 Great, thanks, will do.does this now get around the
>installation
 of NTP daemon as recommended in the set up instructions?

 On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban <
>sgray...@gmail.com>
 wrote:

> Ok replace that with this then reboot the PI and look at your
>weewx
> log again for the ntp sync.
>
> After reboot your  */etc/resolv.conf* should have those name
> servers listed
>
> # Configuration for resolvconf(8)
> # See resolvconf.conf(5) for details
>
> resolv_conf=/etc/resolv.conf
> # If you run a local name server, you should uncomment the
>below
> line and
> # configure your subscribers configuration files below.
> #nameserver 127.0.0.1
> nameserver 8.8.8.8
> nameserver 8.8.4.4
>
> # Mirror the Debian package defaults for the below resolvers
> # so that resolvconf integrates seemlessly.
> dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
> pdnsd_conf=/etc/pdnsd.conf
> unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> 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/LGS3xtzmot0/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>-- 
>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/LGS3xtzmot0/unsubscribe.
>To unsubscribe from this group and all its topics, send an email to
>weewx-user+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[dunbrokin]

Next issue for me is to import historic information (about 5 years
worth...or just the highs and lows during that period of each measured
item) into weewx? Where is the historic information stored and is there an
easy way of importing the data from WeatherDisplay?

On Mon, Jan 7, 2019 at 9:35 AM dunbrokin  wrote:

> Right I have 10.1.1.1 and 8.8.4.4 as "nameserver"  (while shown as
> "name_servers" in the resolvconf.conf file) in the resolv.conf fileI
> presume that will do the job?
>
>
> On Mon, Jan 7, 2019 at 9:32 AM Scott Grayban  wrote:
>
>> Ahh I didn't know that. I don't install resolvconfd.
>> On Jan 6, 2019, at 12:30 PM, dunbrokin  wrote:
>>>
>>> Using nameserver instead of name_server means that none of them appear
>>> in the resolv.conf file!
>>>
>>> On Mon, Jan 7, 2019 at 9:27 AM dunbrokin < dunbro...@gmail.com> wrote:
>>>
 OK will do again. Just looked in the resolv.,conf file.I get
 nameserver 8.8.4.4 but not the 8.8.8.8!

 On Mon, Jan 7, 2019 at 9:23 AM Scott Grayban < sgray...@gmail.com>
 wrote:

> Use
>
> nameserver not name_server
> On Jan 6, 2019, at 12:20 PM, dunbrokin < dunbro...@gmail.com> wrote:
>>
>> Thank you so much for your help Scott!
>>
>> On Mon, Jan 7, 2019 at 9:14 AM Scott Grayban < sgray...@gmail.com>
>> wrote:
>>
>>> If it works yes.
>>> On Jan 6, 2019, at 12:11 PM, dunbrokin < dunbro...@gmail.com>
>>> wrote:

 Great, thanks, will do.does this now get around the
 installation of NTP daemon as recommended in the set up instructions?

 On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban < sgray...@gmail.com>
 wrote:

> Ok replace that with this then reboot the PI and look at your
> weewx log again for the ntp sync.
>
> After reboot your  */etc/resolv.conf* should have those name
> servers listed
>
> # Configuration for resolvconf(8)
> # See resolvconf.conf(5) for details
>
> resolv_conf=/etc/resolv.conf
> # If you run a local name server, you should uncomment the below
> line and
> # configure your subscribers configuration files below.
> #nameserver 127.0.0.1
> nameserver 8.8.8.8
> nameserver 8.8.4.4
>
> # Mirror the Debian package defaults for the below resolvers
> # so that resolvconf integrates seemlessly.
> dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
> pdnsd_conf=/etc/pdnsd.conf
> unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> 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/LGS3xtzmot0/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[dunbrokin]

Right I have 10.1.1.1 and 8.8.4.4 as "nameserver"  (while shown as
"name_servers" in the resolvconf.conf file) in the resolv.conf fileI
presume that will do the job?


On Mon, Jan 7, 2019 at 9:32 AM Scott Grayban  wrote:

> Ahh I didn't know that. I don't install resolvconfd.
> On Jan 6, 2019, at 12:30 PM, dunbrokin  wrote:
>>
>> Using nameserver instead of name_server means that none of them appear in
>> the resolv.conf file!
>>
>> On Mon, Jan 7, 2019 at 9:27 AM dunbrokin < dunbro...@gmail.com> wrote:
>>
>>> OK will do again. Just looked in the resolv.,conf file.I get
>>> nameserver 8.8.4.4 but not the 8.8.8.8!
>>>
>>> On Mon, Jan 7, 2019 at 9:23 AM Scott Grayban < sgray...@gmail.com>
>>> wrote:
>>>
 Use

 nameserver not name_server
 On Jan 6, 2019, at 12:20 PM, dunbrokin < dunbro...@gmail.com> wrote:
>
> Thank you so much for your help Scott!
>
> On Mon, Jan 7, 2019 at 9:14 AM Scott Grayban < sgray...@gmail.com>
> wrote:
>
>> If it works yes.
>> On Jan 6, 2019, at 12:11 PM, dunbrokin < dunbro...@gmail.com> wrote:
>>>
>>> Great, thanks, will do.does this now get around the installation
>>> of NTP daemon as recommended in the set up instructions?
>>>
>>> On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban < sgray...@gmail.com>
>>> wrote:
>>>
 Ok replace that with this then reboot the PI and look at your weewx
 log again for the ntp sync.

 After reboot your  */etc/resolv.conf* should have those name
 servers listed

 # Configuration for resolvconf(8)
 # See resolvconf.conf(5) for details

 resolv_conf=/etc/resolv.conf
 # If you run a local name server, you should uncomment the below
 line and
 # configure your subscribers configuration files below.
 #nameserver 127.0.0.1
 nameserver 8.8.8.8
 nameserver 8.8.4.4

 # Mirror the Debian package defaults for the below resolvers
 # so that resolvconf integrates seemlessly.
 dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
 pdnsd_conf=/etc/pdnsd.conf
 unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf

 --
 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.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
 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.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>> 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/LGS3xtzmot0/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[Scott Grayban]

Ahh I didn't know that. I don't install resolvconfd.

On Jan 6, 2019, 12:30 PM, at 12:30 PM, dunbrokin  wrote:
>Using nameserver instead of name_server means that none of them appear
>in
>the resolv.conf file!
>
>On Mon, Jan 7, 2019 at 9:27 AM dunbrokin  wrote:
>
>> OK will do again. Just looked in the resolv.,conf file.I get
>> nameserver 8.8.4.4 but not the 8.8.8.8!
>>
>> On Mon, Jan 7, 2019 at 9:23 AM Scott Grayban 
>wrote:
>>
>>> Use
>>>
>>> nameserver not name_server
>>> On Jan 6, 2019, at 12:20 PM, dunbrokin  wrote:

 Thank you so much for your help Scott!

 On Mon, Jan 7, 2019 at 9:14 AM Scott Grayban 
>wrote:

> If it works yes.
> On Jan 6, 2019, at 12:11 PM, dunbrokin 
>wrote:
>>
>> Great, thanks, will do.does this now get around the
>installation
>> of NTP daemon as recommended in the set up instructions?
>>
>> On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban 
>> wrote:
>>
>>> Ok replace that with this then reboot the PI and look at your
>weewx
>>> log again for the ntp sync.
>>>
>>> After reboot your */etc/resolv.conf* should have those name
>servers
>>> listed
>>>
>>> # Configuration for resolvconf(8)
>>> # See resolvconf.conf(5) for details
>>>
>>> resolv_conf=/etc/resolv.conf
>>> # If you run a local name server, you should uncomment the below
>line
>>> and
>>> # configure your subscribers configuration files below.
>>> #nameserver 127.0.0.1
>>> nameserver 8.8.8.8
>>> nameserver 8.8.4.4
>>>
>>> # Mirror the Debian package defaults for the below resolvers
>>> # so that resolvconf integrates seemlessly.
>>> dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
>>> pdnsd_conf=/etc/pdnsd.conf
>>> unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
>>>
>>> --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>
>-- 
>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/LGS3xtzmot0/unsubscribe.
>To unsubscribe from this group and all its topics, send an email to
>weewx-user+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[dunbrokin]

OK will do again. Just looked in the resolv.,conf file.I get nameserver
8.8.4.4 but not the 8.8.8.8!

On Mon, Jan 7, 2019 at 9:23 AM Scott Grayban  wrote:

> Use
>
> nameserver not name_server
> On Jan 6, 2019, at 12:20 PM, dunbrokin  wrote:
>>
>> Thank you so much for your help Scott!
>>
>> On Mon, Jan 7, 2019 at 9:14 AM Scott Grayban  wrote:
>>
>>> If it works yes.
>>> On Jan 6, 2019, at 12:11 PM, dunbrokin  wrote:

 Great, thanks, will do.does this now get around the installation of
 NTP daemon as recommended in the set up instructions?

 On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban 
 wrote:

> Ok replace that with this then reboot the PI and look at your weewx
> log again for the ntp sync.
>
> After reboot your */etc/resolv.conf* should have those name servers
> listed
>
> # Configuration for resolvconf(8)
> # See resolvconf.conf(5) for details
>
> resolv_conf=/etc/resolv.conf
> # If you run a local name server, you should uncomment the below line
> and
> # configure your subscribers configuration files below.
> #nameserver 127.0.0.1
> nameserver 8.8.8.8
> nameserver 8.8.4.4
>
> # Mirror the Debian package defaults for the below resolvers
> # so that resolvconf integrates seemlessly.
> dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
> pdnsd_conf=/etc/pdnsd.conf
> unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> 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.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[Scott Grayban]

Use

nameserver not name_server


On Jan 6, 2019, 12:20 PM, at 12:20 PM, dunbrokin  wrote:
>Thank you so much for your help Scott!
>
>On Mon, Jan 7, 2019 at 9:14 AM Scott Grayban 
>wrote:
>
>> If it works yes.
>> On Jan 6, 2019, at 12:11 PM, dunbrokin  wrote:
>>>
>>> Great, thanks, will do.does this now get around the installation
>of
>>> NTP daemon as recommended in the set up instructions?
>>>
>>> On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban 
>wrote:
>>>
 Ok replace that with this then reboot the PI and look at your weewx
>log
 again for the ntp sync.

 After reboot your */etc/resolv.conf* should have those name servers
 listed

 # Configuration for resolvconf(8)
 # See resolvconf.conf(5) for details

 resolv_conf=/etc/resolv.conf
 # If you run a local name server, you should uncomment the below
>line and
 # configure your subscribers configuration files below.
 #nameserver 127.0.0.1
 nameserver 8.8.8.8
 nameserver 8.8.4.4

 # Mirror the Debian package defaults for the below resolvers
 # so that resolvconf integrates seemlessly.
 dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
 pdnsd_conf=/etc/pdnsd.conf
 unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf

 --
 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.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>-- 
>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/LGS3xtzmot0/unsubscribe.
>To unsubscribe from this group and all its topics, send an email to
>weewx-user+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[dunbrokin]

Just for the record, for anybody following this discussion, there is a
slight difference in my file to the solution shown abovenot sure it
makes much difference; but it may save some confusion.

min has "name_server" instead of "nameserver". I am assuming that
"name_server" is the one I should use.

On Mon, Jan 7, 2019 at 9:11 AM dunbrokin  wrote:

> Great, thanks, will do.does this now get around the installation of
> NTP daemon as recommended in the set up instructions?
>
> On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban  wrote:
>
>> Ok replace that with this then reboot the PI and look at your weewx log
>> again for the ntp sync.
>>
>> After reboot your */etc/resolv.conf* should have those name servers
>> listed
>>
>> # Configuration for resolvconf(8)
>> # See resolvconf.conf(5) for details
>>
>> resolv_conf=/etc/resolv.conf
>> # If you run a local name server, you should uncomment the below line and
>> # configure your subscribers configuration files below.
>> #nameserver 127.0.0.1
>> nameserver 8.8.8.8
>> nameserver 8.8.4.4
>>
>> # Mirror the Debian package defaults for the below resolvers
>> # so that resolvconf integrates seemlessly.
>> dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
>> pdnsd_conf=/etc/pdnsd.conf
>> unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[Scott Grayban]

If it works yes.

On Jan 6, 2019, 12:11 PM, at 12:11 PM, dunbrokin  wrote:
>Great, thanks, will do.does this now get around the installation of
>NTP
>daemon as recommended in the set up instructions?
>
>On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban 
>wrote:
>
>> Ok replace that with this then reboot the PI and look at your weewx
>log
>> again for the ntp sync.
>>
>> After reboot your */etc/resolv.conf* should have those name servers
>listed
>>
>> # Configuration for resolvconf(8)
>> # See resolvconf.conf(5) for details
>>
>> resolv_conf=/etc/resolv.conf
>> # If you run a local name server, you should uncomment the below line
>and
>> # configure your subscribers configuration files below.
>> #nameserver 127.0.0.1
>> nameserver 8.8.8.8
>> nameserver 8.8.4.4
>>
>> # Mirror the Debian package defaults for the below resolvers
>> # so that resolvconf integrates seemlessly.
>> dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
>> pdnsd_conf=/etc/pdnsd.conf
>> unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>-- 
>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/LGS3xtzmot0/unsubscribe.
>To unsubscribe from this group and all its topics, send an email to
>weewx-user+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[dunbrokin]

Great, thanks, will do.does this now get around the installation of NTP
daemon as recommended in the set up instructions?

On Sun, Jan 6, 2019 at 9:54 PM Scott Grayban  wrote:

> Ok replace that with this then reboot the PI and look at your weewx log
> again for the ntp sync.
>
> After reboot your */etc/resolv.conf* should have those name servers listed
>
> # Configuration for resolvconf(8)
> # See resolvconf.conf(5) for details
>
> resolv_conf=/etc/resolv.conf
> # If you run a local name server, you should uncomment the below line and
> # configure your subscribers configuration files below.
> #nameserver 127.0.0.1
> nameserver 8.8.8.8
> nameserver 8.8.4.4
>
> # Mirror the Debian package defaults for the below resolvers
> # so that resolvconf integrates seemlessly.
> dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
> pdnsd_conf=/etc/pdnsd.conf
> unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: use Weewx on raspberry

[Patrick Tranchant]

hello Pat and Gary
I reinstalled weewx with Sqlite3 and I see value in database, but some 
datas are bad, 
I think at " driver BYOWS"

example: Jan  6 20:46:43 raspberrypi weewx[2807]: engine: 2019-01-06 
20:46:43 CET (1546804003) LOOP value 'pressure' 1019.4978 outside 
limits (24.0, 34.5)
this data with my script is correct, wy outside limit, the display in the 
website is bad also..
An other file to modify ?
I modified the datas inside file skin.conf
[[Units]
# This section is for managing the selection and formatting of units.

[[Groups]]
# For each group of measurements, this section sets what units to
# use for it.
# NB: The unit is always in the singular. I.e., 'mile_per_hour',
# NOT 'miles_per_hour'

group_altitude = meter # Options are 'foot' or 
'meter'
group_degree_day   = degree_C_day # Options are 
'degree_F_day' or 'degree_C_day'
group_direction= degree_compass
group_moisture = centibar
group_percent  = percent
group_pressure = hPa # Options are 'inHg', 
'mmHg', 'mbar', or 'hPa'
group_radiation= watt_per_meter_squared
group_rain = mm # Options are 'inch', 'cm', 
or 'mm'
group_rainrate = mm_per_hour# Options are 
'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
group_speed= km_per_hour# Options are 
'mile_per_hour', 'km_per_hour', 'knot', or 'meter_per_second'
group_speed2   = km_per_hour2   # Options are 
'mile_per_hour2', 'km_per_hour2', 'knot2', or 'meter_per_second2'
group_temperature  = degree_C # Options are 'degree_F' 
or 'degree_C'
group_uv   = uv_index
group_volt = volt
]

thanks

Patrick

On Saturday, December 8, 2018 at 3:40:43 PM UTC+1, Patrick Tranchant wrote:
>
> hello I am a newbie from France ( sorry for my english )
>
> I want to use weewx on a raspberry with a weather station built by myself 
> (view on Magpi)
> I don't see my station on your website to configure :
>
> Weather Station Hardware Comparison: I don't found my weather station.
> Do you have a solution or how to configure Weewx
>
> thank you for your help
>
> 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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: USB write fail and then cannot restart service

[Andrew Milner]

and a lot more expensive


On Sunday, 6 January 2019 15:42:35 UTC+2, Rich Altmaier wrote:
>
> Sorry to hear of your troubles.
> I got tired of RPI USB troubles and hangs, and switched to Intel NUC.  So 
> much faster, so much more stable!

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Uploading to WeatherCloud?

[Thomas Keffer]

My uploader seems to be working fine.

I also tried the URL you provided using my id and key, and it seems to
work. At least, it responded with a 429 error ("Too many requests"), which
sounds about right.

Try using the URL (with the correct key) in a browser and see what comes
back.

-tk

On Sun, Jan 6, 2019 at 8:14 AM Jeff Ross  wrote:

> Hi all,
>
> I've installed the weathercloud driver according to the instructions
> WeatherCloud sent when I requested the docs for the API.
>
> https://weathercloud.net/info/weewx
>
> It mostly fails to upload data though--here's a section of debug logs:
>
> 2019-01-06 09:05:47.992719500 127.0.0.1: user.debug: Jan 6 09:05:47
> weewx[64490]: restx: WeatherCloud: url:
> http://api.weathercloud.net/v01/set?wid=444b000107d31735=71=103=41=0=20=0=3.8.2=457=16=251=208=104=60=0=32=XXX=20190106=16=19=8597=32=208=-39=1605=0
> 2019-01-06 09:05:48.379906500 127.0.0.1: user.debug: Jan 6 09:05:48
> weewx[64490]: restx: WeatherCloud: Failed upload attempt 1: HTTP Error 400:
> Bad Request
> 2019-01-06 09:06:53.400736500 127.0.0.1: user.debug: Jan 6 09:06:53
> weewx[64490]: restx: WeatherCloud: Failed upload attempt 2:  timed out>
> 2019-01-06 09:06:57.950420500 127.0.0.1: user.debug: Jan 6 09:06:57
> weewx[64490]: interceptor: MainThread: empty queue
> 2019-01-06 09:07:00.513001500 127.0.0.1: user.debug: Jan 6 09:07:00
> weewx[64490]: restx: WeatherCloud: Failed upload attempt 3: HTTP Error 400:
> Bad Request
> 2019-01-06 09:07:05.520782500 127.0.0.1: user.err: Jan 6 09:07:05
> weewx[64490]: restx: WeatherCloud: Failed to publish record 2019-01-06
> 09:05:00 MST (1546790700): Failed upload after 3 tries
>
> Once in a great while I get a successful upload but I'd say 99% of the
> time I get the HTTP Error 400.
>
> Anyone else having a problem with WeatherCloud?
>
> Thanks,
>
> Jeff Ross
> Townsend, MT
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Uploading to WeatherCloud?

[Jeff Ross]

Hi all,

I've installed the weathercloud driver according to the instructions 
WeatherCloud sent when I requested the docs for the API.

https://weathercloud.net/info/weewx

It mostly fails to upload data though--here's a section of debug logs:

2019-01-06 09:05:47.992719500 127.0.0.1: user.debug: Jan 6 09:05:47 
weewx[64490]: restx: WeatherCloud: url: 
http://api.weathercloud.net/v01/set?wid=444b000107d31735=71=103=41=0=20=0=3.8.2=457=16=251=208=104=60=0=32=XXX=20190106=16=19=8597=32=208=-39=1605=0
2019-01-06 09:05:48.379906500 127.0.0.1: user.debug: Jan 6 09:05:48 
weewx[64490]: restx: WeatherCloud: Failed upload attempt 1: HTTP Error 400: 
Bad Request
2019-01-06 09:06:53.400736500 127.0.0.1: user.debug: Jan 6 09:06:53 
weewx[64490]: restx: WeatherCloud: Failed upload attempt 2: 
2019-01-06 09:06:57.950420500 127.0.0.1: user.debug: Jan 6 09:06:57 
weewx[64490]: interceptor: MainThread: empty queue
2019-01-06 09:07:00.513001500 127.0.0.1: user.debug: Jan 6 09:07:00 
weewx[64490]: restx: WeatherCloud: Failed upload attempt 3: HTTP Error 400: 
Bad Request
2019-01-06 09:07:05.520782500 127.0.0.1: user.err: Jan 6 09:07:05 
weewx[64490]: restx: WeatherCloud: Failed to publish record 2019-01-06 
09:05:00 MST (1546790700): Failed upload after 3 tries

Once in a great while I get a successful upload but I'd say 99% of the time 
I get the HTTP Error 400.

Anyone else having a problem with WeatherCloud?

Thanks,

Jeff Ross
Townsend, MT

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Alarm.py Help

[Thomas Keffer]

It looks like the problem is that there is no DNS entry for your hostname.
This was causing a socket.gaierror exception to be raised, which quietly
terminated the thread. I've changed the code to catch such an exception and
log it.

-tk

On Sun, Jan 6, 2019 at 7:38 AM  wrote:

> Sent.
>
>
>
> Tom
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *Thomas Keffer
> *Sent:* Sunday, January 6, 2019 9:33 AM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: Alarm.py Help
>
>
>
> Possibly, but I don't think so. The library smtplib uses a default of 465
> for attempting SSL connections. Also, even if one attempted to connect
> using the wrong port, it should still time out. Which it didn't.
>
>
>
> Can you send the host name of the non-SSL server by private email? I don't
> need the user name and password.
>
>
>
> tkeffer at gmail.com
> 
>
>
>
> -tk
>
>
>
> On Sun, Jan 6, 2019 at 7:27 AM  wrote:
>
> It is the mail server provided by my ISP, inmotionhosting.com
> .
> No exception was raised.  Could it be something to do with the port?  I
> noticed in the setup that there was no way to designate a port.
>
>
>
> SSL:
>
> Outgoing Server:  secure246.inmotionhosting.com
> 
>   SMTP Port: 465
>
>
>
> Non-SSL:
>
> Outgoing Server:  mail.XXX.com
> 
> SMTP Port: 587
>
>
>
> Tom
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *Thomas Keffer
> *Sent:* Sunday, January 6, 2019 6:51 AM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: Alarm.py Help
>
>
>
> OK, but I wish we knew what the trouble was.
>
>
>
> The last version had a 20 second 'timeout': if the server didn't respond,
> an exception should have been raised. Sounds like that didn't happen.
>
>
>
> What was the non-SSL server you were using?
>
>
>
> -tk
>
>
>
> On Sat, Jan 5, 2019 at 6:59 PM  wrote:
>
> OK.  I got it working by changing my server to one requiring SSL.  I was
> using a non-SSL server and the latest version you sent still would not
> work.  I also tried Gmail SMTP and it works.  The “issue” seems to be with
> non-SSL servers.  I usually find it the other way around.
>
>
>
> I tried the original example alarm.py using an SSL server and it works so
> I think this confirms my ”issue” is with non-SSL servers.
>
>
>
> Sorry for all the trouble.  I am happy to use the SSL server.
>
>
>
> Many thanks.
>
>
>
> Tom
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *Thomas Keffer
> *Sent:* Saturday, January 5, 2019 8:22 PM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: Alarm.py Help
>
>
>
> Looks like your smtp server hangs if you try to connect to it using SSL.
> Try this version.
>
>
>
> -tk
>
>
>
> On Sat, Jan 5, 2019 at 5:23 PM  wrote:
>
> As requested.
>
>
>
> Thanks for helping.
>
>
>
> Tom
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *Thomas Keffer
> *Sent:* Saturday, January 5, 2019 6:58 PM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: Alarm.py Help
>
>
>
> Hmmm. Try this version. It has been heavily instrumented. Again, run with
> debug=1. Make sure you restart WeeWX.
>
>
>
> -tk
>
>
>
> On Sat, Jan 5, 2019 at 4:46 PM  wrote:
>
> I used the alarm.py version that you sent the link to.  I attached it
> along with the syslog.  I am not using an SSL connection.  Still nothing.
> I  did notice an error when I quit weewx this time.
>
>
> On Saturday, January 5, 2019 at 12:20:32 PM UTC-6, nine...@gmail.com
> wrote:
>
> I set up alarm.py per the instructions (I think).  I wanted to test an
> alarm so I set it for expression= "outTemp > 40".  When I run weewx I get
>
>
>
> alarm: Alarm set for expression: 'outTemp > 40.0'
>
>
>
> alarm: Alarm expression "outTemp > 40.0" evaluated True at 2019-01-05
> 11:15:00 CST (1546708500)
>
>
>
> This is what I would expect however nothing else happens.  I looked in the
> syslog file and there is no mention of the mail being sent or an smtp
> error.   Also there were no other entries stating the expression was true.
>
>
>
> I waited one hour and again got this but no other entries in 

RE: [weewx-user] Re: Alarm.py Help

[nineback]

Sent.

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Sunday, January 6, 2019 9:33 AM
To: weewx-user 
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Possibly, but I don't think so. The library smtplib uses a default of 465 for 
attempting SSL connections. Also, even if one attempted to connect using the 
wrong port, it should still time out. Which it didn't.

 

Can you send the host name of the non-SSL server by private email? I don't need 
the user name and password. 

 

tkeffer at gmail.com 

 

 

-tk

 

On Sun, Jan 6, 2019 at 7:27 AM mailto:nineb...@gmail.com> 
> wrote:

It is the mail server provided by my ISP, inmotionhosting.com 

 .  No exception was raised.  Could it be something to do with the port?  I 
noticed in the setup that there was no way to designate a port.

 

SSL:

Outgoing Server:  secure246.inmotionhosting.com 

SMTP Port: 465

 

Non-SSL:

Outgoing Server:  mail.XXX.com 

  SMTP Port: 587

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Sunday, January 6, 2019 6:51 AM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

OK, but I wish we knew what the trouble was.

 

The last version had a 20 second 'timeout': if the server didn't respond, an 
exception should have been raised. Sounds like that didn't happen.

 

What was the non-SSL server you were using?

 

-tk

 

On Sat, Jan 5, 2019 at 6:59 PM mailto:nineb...@gmail.com> 
> wrote:

OK.  I got it working by changing my server to one requiring SSL.  I was using 
a non-SSL server and the latest version you sent still would not work.  I also 
tried Gmail SMTP and it works.  The “issue” seems to be with non-SSL servers.  
I usually find it the other way around.

 

I tried the original example alarm.py using an SSL server and it works so I 
think this confirms my ”issue” is with non-SSL servers.

 

Sorry for all the trouble.  I am happy to use the SSL server.

 

Many thanks.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 8:22 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Looks like your smtp server hangs if you try to connect to it using SSL. Try 
this version. 

 

-tk

 

On Sat, Jan 5, 2019 at 5:23 PM mailto:nineb...@gmail.com> 
> wrote:

As requested.

 

Thanks for helping.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 6:58 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Hmmm. Try this version. It has been heavily instrumented. Again, run with 
debug=1. Make sure you restart WeeWX.

 

-tk

 

On Sat, Jan 5, 2019 at 4:46 PM mailto:nineb...@gmail.com> 
> wrote:

I used the alarm.py version that you sent the link to.  I attached it along 
with the syslog.  I am not using an SSL connection.  Still nothing.  I  did 
notice an error when I quit weewx this time.


On Saturday, January 5, 2019 at 12:20:32 PM UTC-6, nine...@gmail.com 
  wrote:

I set up alarm.py per the instructions (I think).  I wanted to test an alarm so 
I set it for expression= "outTemp > 40".  When I run weewx I get

 

alarm: Alarm set for expression: 'outTemp > 40.0'

 

alarm: Alarm expression "outTemp > 40.0" evaluated True at 2019-01-05 11:15:00 
CST (1546708500)

 

This is what I would expect however nothing else happens.  I looked in the 
syslog file and there is no mention of the mail being sent or an smtp error.   
Also there were no other entries stating the expression was true.

 

I waited one hour and again got this but no other entries in syslog.

 

Jan  5 12:16:16 raspberrypi 

Re: [weewx-user] Re: Alarm.py Help

[Thomas Keffer]

Possibly, but I don't think so. The library smtplib uses a default of 465
for attempting SSL connections. Also, even if one attempted to connect
using the wrong port, it should still time out. Which it didn't.

Can you send the host name of the non-SSL server by private email? I don't
need the user name and password.

tkeffer at gmail.com

-tk

On Sun, Jan 6, 2019 at 7:27 AM  wrote:

> It is the mail server provided by my ISP, inmotionhosting.com.  No
> exception was raised.  Could it be something to do with the port?  I
> noticed in the setup that there was no way to designate a port.
>
>
>
> SSL:
>
> Outgoing Server:  secure246.inmotionhosting.com   SMTP Port: 465
>
>
>
> Non-SSL:
>
> Outgoing Server:  mail.XXX.com SMTP Port: 587
>
>
>
> Tom
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *Thomas Keffer
> *Sent:* Sunday, January 6, 2019 6:51 AM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: Alarm.py Help
>
>
>
> OK, but I wish we knew what the trouble was.
>
>
>
> The last version had a 20 second 'timeout': if the server didn't respond,
> an exception should have been raised. Sounds like that didn't happen.
>
>
>
> What was the non-SSL server you were using?
>
>
>
> -tk
>
>
>
> On Sat, Jan 5, 2019 at 6:59 PM  wrote:
>
> OK.  I got it working by changing my server to one requiring SSL.  I was
> using a non-SSL server and the latest version you sent still would not
> work.  I also tried Gmail SMTP and it works.  The “issue” seems to be with
> non-SSL servers.  I usually find it the other way around.
>
>
>
> I tried the original example alarm.py using an SSL server and it works so
> I think this confirms my ”issue” is with non-SSL servers.
>
>
>
> Sorry for all the trouble.  I am happy to use the SSL server.
>
>
>
> Many thanks.
>
>
>
> Tom
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *Thomas Keffer
> *Sent:* Saturday, January 5, 2019 8:22 PM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: Alarm.py Help
>
>
>
> Looks like your smtp server hangs if you try to connect to it using SSL.
> Try this version.
>
>
>
> -tk
>
>
>
> On Sat, Jan 5, 2019 at 5:23 PM  wrote:
>
> As requested.
>
>
>
> Thanks for helping.
>
>
>
> Tom
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *Thomas Keffer
> *Sent:* Saturday, January 5, 2019 6:58 PM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: Alarm.py Help
>
>
>
> Hmmm. Try this version. It has been heavily instrumented. Again, run with
> debug=1. Make sure you restart WeeWX.
>
>
>
> -tk
>
>
>
> On Sat, Jan 5, 2019 at 4:46 PM  wrote:
>
> I used the alarm.py version that you sent the link to.  I attached it
> along with the syslog.  I am not using an SSL connection.  Still nothing.
> I  did notice an error when I quit weewx this time.
>
>
> On Saturday, January 5, 2019 at 12:20:32 PM UTC-6, nine...@gmail.com
> wrote:
>
> I set up alarm.py per the instructions (I think).  I wanted to test an
> alarm so I set it for expression= "outTemp > 40".  When I run weewx I get
>
>
>
> alarm: Alarm set for expression: 'outTemp > 40.0'
>
>
>
> alarm: Alarm expression "outTemp > 40.0" evaluated True at 2019-01-05
> 11:15:00 CST (1546708500)
>
>
>
> This is what I would expect however nothing else happens.  I looked in the
> syslog file and there is no mention of the mail being sent or an smtp
> error.   Also there were no other entries stating the expression was true.
>
>
>
> I waited one hour and again got this but no other entries in syslog.
>
>
>
> Jan  5 12:16:16 raspberrypi weewx[5473]: alarm: Alarm expression "outTemp
> > 40.0" evaluated True at 2019-01-05 12:16:00 CST (1546712160)
>
>
>
>
>
> I am using a Raspberry Pi.
>
>
>
> Thanks,
>
>
>
> Tom
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout
> 
> .
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout
> 
> .
>
> --
> 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, 

RE: [weewx-user] Re: Alarm.py Help

[nineback]

It is the mail server provided by my ISP, inmotionhosting.com.  No exception 
was raised.  Could it be something to do with the port?  I noticed in the setup 
that there was no way to designate a port.

 

SSL:

Outgoing Server:  secure246.inmotionhosting.com   SMTP Port: 465

 

Non-SSL:

Outgoing Server:  mail.XXX.com SMTP Port: 587

 

Tom

 

From: weewx-user@googlegroups.com  On Behalf Of 
Thomas Keffer
Sent: Sunday, January 6, 2019 6:51 AM
To: weewx-user 
Subject: Re: [weewx-user] Re: Alarm.py Help

 

OK, but I wish we knew what the trouble was.

 

The last version had a 20 second 'timeout': if the server didn't respond, an 
exception should have been raised. Sounds like that didn't happen.

 

What was the non-SSL server you were using?

 

-tk

 

On Sat, Jan 5, 2019 at 6:59 PM mailto:nineb...@gmail.com> 
> wrote:

OK.  I got it working by changing my server to one requiring SSL.  I was using 
a non-SSL server and the latest version you sent still would not work.  I also 
tried Gmail SMTP and it works.  The “issue” seems to be with non-SSL servers.  
I usually find it the other way around.

 

I tried the original example alarm.py using an SSL server and it works so I 
think this confirms my ”issue” is with non-SSL servers.

 

Sorry for all the trouble.  I am happy to use the SSL server.

 

Many thanks.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 8:22 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Looks like your smtp server hangs if you try to connect to it using SSL. Try 
this version. 

 

-tk

 

On Sat, Jan 5, 2019 at 5:23 PM mailto:nineb...@gmail.com> 
> wrote:

As requested.

 

Thanks for helping.

 

Tom

 

From: weewx-user@googlegroups.com   
mailto:weewx-user@googlegroups.com> > On Behalf 
Of Thomas Keffer
Sent: Saturday, January 5, 2019 6:58 PM
To: weewx-user mailto:weewx-user@googlegroups.com> >
Subject: Re: [weewx-user] Re: Alarm.py Help

 

Hmmm. Try this version. It has been heavily instrumented. Again, run with 
debug=1. Make sure you restart WeeWX.

 

-tk

 

On Sat, Jan 5, 2019 at 4:46 PM mailto:nineb...@gmail.com> 
> wrote:

I used the alarm.py version that you sent the link to.  I attached it along 
with the syslog.  I am not using an SSL connection.  Still nothing.  I  did 
notice an error when I quit weewx this time.


On Saturday, January 5, 2019 at 12:20:32 PM UTC-6, nine...@gmail.com 
  wrote:

I set up alarm.py per the instructions (I think).  I wanted to test an alarm so 
I set it for expression= "outTemp > 40".  When I run weewx I get

 

alarm: Alarm set for expression: 'outTemp > 40.0'

 

alarm: Alarm expression "outTemp > 40.0" evaluated True at 2019-01-05 11:15:00 
CST (1546708500)

 

This is what I would expect however nothing else happens.  I looked in the 
syslog file and there is no mention of the mail being sent or an smtp error.   
Also there were no other entries stating the expression was true.

 

I waited one hour and again got this but no other entries in syslog.

 

Jan  5 12:16:16 raspberrypi weewx[5473]: alarm: Alarm expression "outTemp > 
40.0" evaluated True at 2019-01-05 12:16:00 CST (1546712160)

 

 

I am using a Raspberry Pi.

 

Thanks,

 

Tom

 

 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com 
 .
For more options, visit https://groups.google.com/d/optout 

 .

-- 
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 
 .
For more options, visit https://groups.google.com/d/optout 

 .

-- 
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 
 .
For more options, visit https://groups.google.com/d/optout 

[weewx-user] MQTT and Bloomsky Belchertown skin

[Chris Plant]

Trying to understand how MQTT works as id like to have my site autoupdate.  
I am using the Bloomsky API Driver from GitHub, so it pulls info via API 
every 5 minutes.  When I set up everything, I can get mosquito to work, 
however on my website it shows "Unable to connect to weather station, try 
again later"  Is that because the Bloomsky doesn't constantly shoot info in 
the Loops?  Why can't MQTT update every five minutes when MQTT gets the 
archive info? Is it a port issue?  What port do I use in the Belchertown 
skin, 1883 or the websockets port 9001?  Thanks for any clarification!

Chris Plant

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: USB write fail and then cannot restart service

['Rich Altmaier' via weewx-user]

Sorry to hear of your troubles.
I got tired of RPI USB troubles and hangs, and switched to Intel NUC.  So much 
faster, so much more stable!

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Meteobridge realtime extension for weeWX

[steeple ian]

Ok doing well so far. I have packaged a 'mbrt.py' file and installed it
correctly. It is producing a 'MBrealtimeupload.txt' file with some data.
Hopefully all I need to do is map the Meteobridge fields into the correct
positions. Will have to leave that until this evening as 'outdoor jobs' are
beckoning.

On Sun, Jan 6, 2019 at 10:33 AM Ian Millard 
wrote:

> Ok thanks for the confidence boost.
>
> I already have a comparison of the two live data files. They are very
> similar but Meteobridge has extra fields. In general these additional
> fields do not appear to be used by the template. As a first step, I will
> amend the field listing at the end of crt.py to match the Meteobridge
> format and see what happens - or am I being too simplistic?
>
> Thanks,
> Ian
>
>
>
> Sent from my iPad
>
> On 6 Jan 2019, at 08:41, mwall  wrote:
>
> On Sunday, January 6, 2019 at 1:17:07 AM UTC-5, Ian Millard wrote:
>>
>> I may be imagining things but some time ago I came across a mention of a
>> Meteobridge realtime extension for weeWX to emit live data in a similar
>> fashion to the CRT extension. I have searched and searched but nothing has
>> turned up. I am prepared to try and have a go myself but Python is very
>> much *not* my strong point. Is there anyone willing to hold my hand
>> through the process?
>>
>
> you should be able to do this pretty easily.  post questions here, or if
> it gets too technical move the discussion to weewx-development, if you
> like.  we've been through this process before with cumulus (realtime.txt
> and variants) and weatherdisplay (customclientraw.txt and variants) for
> steelseries and numerous other 'templates'.
>
> you might want to start by forking the weewx-crt extension.  just modify
> the output so that it contains the data in whatever order and format
> meteobridge emits them.
>
> hopefully you can get the specification from boris or brian.  but if not,
> you can easily reverse engineer it by looking at a sample of whatever
> weather34 for meteobridge is trying to ingest.
>
> m
>
> --
> 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/IYev_usupEM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Alarm.py Help

[Thomas Keffer]

OK, but I wish we knew what the trouble was.

The last version had a 20 second 'timeout': if the server didn't respond,
an exception should have been raised. Sounds like that didn't happen.

What was the non-SSL server you were using?

-tk

On Sat, Jan 5, 2019 at 6:59 PM  wrote:

> OK.  I got it working by changing my server to one requiring SSL.  I was
> using a non-SSL server and the latest version you sent still would not
> work.  I also tried Gmail SMTP and it works.  The “issue” seems to be with
> non-SSL servers.  I usually find it the other way around.
>
>
>
> I tried the original example alarm.py using an SSL server and it works so
> I think this confirms my ”issue” is with non-SSL servers.
>
>
>
> Sorry for all the trouble.  I am happy to use the SSL server.
>
>
>
> Many thanks.
>
>
>
> Tom
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *Thomas Keffer
> *Sent:* Saturday, January 5, 2019 8:22 PM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: Alarm.py Help
>
>
>
> Looks like your smtp server hangs if you try to connect to it using SSL.
> Try this version.
>
>
>
> -tk
>
>
>
> On Sat, Jan 5, 2019 at 5:23 PM  wrote:
>
> As requested.
>
>
>
> Thanks for helping.
>
>
>
> Tom
>
>
>
> *From:* weewx-user@googlegroups.com  *On
> Behalf Of *Thomas Keffer
> *Sent:* Saturday, January 5, 2019 6:58 PM
> *To:* weewx-user 
> *Subject:* Re: [weewx-user] Re: Alarm.py Help
>
>
>
> Hmmm. Try this version. It has been heavily instrumented. Again, run with
> debug=1. Make sure you restart WeeWX.
>
>
>
> -tk
>
>
>
> On Sat, Jan 5, 2019 at 4:46 PM  wrote:
>
> I used the alarm.py version that you sent the link to.  I attached it
> along with the syslog.  I am not using an SSL connection.  Still nothing.
> I  did notice an error when I quit weewx this time.
>
>
> On Saturday, January 5, 2019 at 12:20:32 PM UTC-6, nine...@gmail.com
> wrote:
>
> I set up alarm.py per the instructions (I think).  I wanted to test an
> alarm so I set it for expression= "outTemp > 40".  When I run weewx I get
>
>
>
> alarm: Alarm set for expression: 'outTemp > 40.0'
>
>
>
> alarm: Alarm expression "outTemp > 40.0" evaluated True at 2019-01-05
> 11:15:00 CST (1546708500)
>
>
>
> This is what I would expect however nothing else happens.  I looked in the
> syslog file and there is no mention of the mail being sent or an smtp
> error.   Also there were no other entries stating the expression was true.
>
>
>
> I waited one hour and again got this but no other entries in syslog.
>
>
>
> Jan  5 12:16:16 raspberrypi weewx[5473]: alarm: Alarm expression "outTemp
> > 40.0" evaluated True at 2019-01-05 12:16:00 CST (1546712160)
>
>
>
>
>
> I am using a Raspberry Pi.
>
>
>
> Thanks,
>
>
>
> Tom
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout
> 
> .
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout
> 
> .
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout
> 
> .
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout
> 
> .
>
> --
> You received this message 

Re: [weewx-user] instantaneous rain vs averaged

[Andrew Milner]

I would expect the davis (hardware) to be more accurate than weewx 
generated (software) - but how it compares to other stations depends on 
what type of station they are!!!

There is also a setting for store loop hi/lo or use record value for hi/lo 
values - loop would be more accurate but can result in unwanted spikes.



On Sunday, 6 January 2019 12:17:43 UTC+2, Adam Harvey wrote:
>
> I'll jump into the config and change it to prefer software and see what 
> happens.
>
> Thanks.
>
> On Saturday, 5 January 2019 16:46:47 UTC+10, Andrew Milner wrote:
>>
>> may not have been that clear from Tom's response - but there are two main 
>> areas involoved here:
>> 1. [StdWXCalculate] where all options should normally specify prefer 
>> hardware for vantage stations. if rainRate is set to prefer_software then 
>> weewx calculates the average rate over the archive period
>> 2. [StdArchive] where record_generation is usually set to hardware.  
>> However if record_generation = software is set weewx calculates all values 
>> as averages over the archive period.
>>
>> I do not know what happens if rainRate is set as prefer_software but 
>> record_generation is set al hardware.  ie I do not know if weewx overrides 
>> the hardware record values with its calculated rate or not.
>>
>>
>>
>> On Saturday, 5 January 2019 07:31:37 UTC+2, Adam Harvey wrote:
>>>
>>> Thanks, I will have another read.
>>>
>>> On Saturday, 5 January 2019 03:13:37 UTC+10, Thomas Keffer wrote:

 Reports are entirely generated from the database, which contains 
 archive records. Where do the archive records come from? If you have 
 selected hardware record generation (the default) then, in the case of the 
 Vantage, they are downloaded from the console. The value of rain rate you 
 are seeing is what was downloaded from the console.

 For more information, see the section *LOOP packets vs archive records 
 *
  in 
 the Customizing Guide, and the section on Vantage stations 
  in the Hardware 
 Guide.

 As for the other stations, who knows where they are getting their 
 values...

 -tk

 On Fri, Jan 4, 2019 at 1:49 AM Adam Harvey  wrote:

> Hi, I have a raspberry pi with weewx installed.  Outside I  have a 
> Davis vantage vue, I have a connection from the davis console to the rpi. 
>  
>
> All works well, except, the rain rates seem averaged out, I notice 
> some nearby stations seem to get higher instantaneous rates.
>
> I'm struggling to understand the loop vs archive, is that the change I 
> need to make?
>
> thanks in advance for any assistance. 
>
> -- 
> 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.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Meteobridge realtime extension for weeWX

[Ian Millard]

Ok thanks for the confidence boost.

I already have a comparison of the two live data files. They are very similar 
but Meteobridge has extra fields. In general these additional fields do not 
appear to be used by the template. As a first step, I will amend the field 
listing at the end of crt.py to match the Meteobridge format and see what 
happens - or am I being too simplistic?

Thanks,
Ian



Sent from my iPad

> On 6 Jan 2019, at 08:41, mwall  wrote:
> 
>> On Sunday, January 6, 2019 at 1:17:07 AM UTC-5, Ian Millard wrote:
>> I may be imagining things but some time ago I came across a mention of a 
>> Meteobridge realtime extension for weeWX to emit live data in a similar 
>> fashion to the CRT extension. I have searched and searched but nothing has 
>> turned up. I am prepared to try and have a go myself but Python is very much 
>> not my strong point. Is there anyone willing to hold my hand through the 
>> process? 
> 
> you should be able to do this pretty easily.  post questions here, or if it 
> gets too technical move the discussion to weewx-development, if you like.  
> we've been through this process before with cumulus (realtime.txt and 
> variants) and weatherdisplay (customclientraw.txt and variants) for 
> steelseries and numerous other 'templates'.
> 
> you might want to start by forking the weewx-crt extension.  just modify the 
> output so that it contains the data in whatever order and format meteobridge 
> emits them.
> 
> hopefully you can get the specification from boris or brian.  but if not, you 
> can easily reverse engineer it by looking at a sample of whatever weather34 
> for meteobridge is trying to ingest.
> 
> m 
> -- 
> 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/IYev_usupEM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] instantaneous rain vs averaged

[Adam Harvey]

I'll jump into the config and change it to prefer software and see what 
happens.

Thanks.

On Saturday, 5 January 2019 16:46:47 UTC+10, Andrew Milner wrote:
>
> may not have been that clear from Tom's response - but there are two main 
> areas involoved here:
> 1. [StdWXCalculate] where all options should normally specify prefer 
> hardware for vantage stations. if rainRate is set to prefer_software then 
> weewx calculates the average rate over the archive period
> 2. [StdArchive] where record_generation is usually set to hardware.  
> However if record_generation = software is set weewx calculates all values 
> as averages over the archive period.
>
> I do not know what happens if rainRate is set as prefer_software but 
> record_generation is set al hardware.  ie I do not know if weewx overrides 
> the hardware record values with its calculated rate or not.
>
>
>
> On Saturday, 5 January 2019 07:31:37 UTC+2, Adam Harvey wrote:
>>
>> Thanks, I will have another read.
>>
>> On Saturday, 5 January 2019 03:13:37 UTC+10, Thomas Keffer wrote:
>>>
>>> Reports are entirely generated from the database, which contains archive 
>>> records. Where do the archive records come from? If you have selected 
>>> hardware record generation (the default) then, in the case of the Vantage, 
>>> they are downloaded from the console. The value of rain rate you are seeing 
>>> is what was downloaded from the console.
>>>
>>> For more information, see the section *LOOP packets vs archive records 
>>> *
>>>  in 
>>> the Customizing Guide, and the section on Vantage stations 
>>>  in the Hardware 
>>> Guide.
>>>
>>> As for the other stations, who knows where they are getting their 
>>> values...
>>>
>>> -tk
>>>
>>> On Fri, Jan 4, 2019 at 1:49 AM Adam Harvey  wrote:
>>>
 Hi, I have a raspberry pi with weewx installed.  Outside I  have a 
 Davis vantage vue, I have a connection from the davis console to the rpi.  

 All works well, except, the rain rates seem averaged out, I notice some 
 nearby stations seem to get higher instantaneous rates.

 I'm struggling to understand the loop vs archive, is that the change I 
 need to make?

 thanks in advance for any assistance. 

 -- 
 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.
 For more options, visit https://groups.google.com/d/optout.

>>>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Meteobridge realtime extension for weeWX

[mwall]

On Sunday, January 6, 2019 at 1:17:07 AM UTC-5, Ian Millard wrote:
>
> I may be imagining things but some time ago I came across a mention of a 
> Meteobridge realtime extension for weeWX to emit live data in a similar 
> fashion to the CRT extension. I have searched and searched but nothing has 
> turned up. I am prepared to try and have a go myself but Python is very 
> much *not* my strong point. Is there anyone willing to hold my hand 
> through the process? 
>

you should be able to do this pretty easily.  post questions here, or if it 
gets too technical move the discussion to weewx-development, if you like.  
we've been through this process before with cumulus (realtime.txt and 
variants) and weatherdisplay (customclientraw.txt and variants) for 
steelseries and numerous other 'templates'.

you might want to start by forking the weewx-crt extension.  just modify 
the output so that it contains the data in whatever order and format 
meteobridge emits them.

hopefully you can get the specification from boris or brian.  but if not, 
you can easily reverse engineer it by looking at a sample of whatever 
weather34 for meteobridge is trying to ingest.

m 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Getting the RPi 3 with Davis Vantage up and running

[Scott Grayban]

Ok replace that with this then reboot the PI and look at your weewx log 
again for the ntp sync.

After reboot your */etc/resolv.conf* should have those name servers listed

# Configuration for resolvconf(8)
# See resolvconf.conf(5) for details

resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
#nameserver 127.0.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4

# Mirror the Debian package defaults for the below resolvers
# so that resolvconf integrates seemlessly.
dnsmasq_resolv=/var/run/dnsmasq/resolv.conf
pdnsd_conf=/etc/pdnsd.conf
unbound_conf=/var/cache/unbound/resolvconf_resolvers.conf

-- 
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.
For more options, visit https://groups.google.com/d/optout.