Re: [weewx-user] ftpuploader timeout with Davis Vantage Pro2 - Weewx on CentOS 7

2019-10-22 Thread Kevin H. Phillips

Got it.  Thanks for the input.


Kevin

On 10/22/19 8:13 PM, Thomas Keffer wrote:

Kevin,

I don't think there is much of a mystery here. The Davis site does 
/not/ support FTP. I would be surprised if they did: that would make 
them just another website provider, which they are not.


What they do support is a proprietary HTTP "RESTful" upload protocol 
for their WeatherLink customers. That generally requires a 
subscription, although they do offer a crippled version for "3rd 
parties", which would be us. However, we do not offer such an upload 
extension, and have no plans to do so.


So, you will have to either

1) Set up your own website with a hosting provider. Several were 
suggested in an earlier email.
2) Be satisfied with a website on your Local Area Network, that is, 
your house. You can supplement this with uploads to CWOP or 
WeatherUnderground, or one of the many other upload sites WeeWX 
supports. Unfortunately, WeatherLink is not one of them.
3) Give up on WeeWX and go all Davis. Buy their WeatherLink Live 
logger, or use a regular logger, but run their WeatherLink Computer 
Software on a computer. Either way, you would need a subscription. See 
their website for details.


-tk



On Tue, Oct 22, 2019 at 5:33 PM Kevin H. Phillips 
mailto:kh-phill...@9-5usa.org>> wrote:


I posed the question to Davis Support of "how" their WeatherLink
software uploads information to their site.  I haven not yet
received a direct response from them but I received this evening
what appears to be a generic message that might contain some
clues.  I don't know if someone directed this to me or whether
this was directed at anyone using their WeatherLink software. 
Here it is:


Dear Developers,

There are upcoming changes to api.weatherlink.com
 that may affect those using SSL to
make requests to https://api.weatherlink.com/. The upcoming change
will disable support for outdated versions of TLS. Developers
using our API without SSL will not be affected.

Changes:
On Monday, November 4th, 2019, TLS version 1.0 will be disabled on
https://api.weatherlink.com
On Monday, January 6th 2020, TLS version 1.1 will be disabled on
https://api.weatherlink.com.

Background: TLS 1.0/1.1 protocols have known security
vulnerabilities and most modern web browsers will remove all
support for TLS 1.0/1.1 in January of next year. TLS version 1.2
was originally released in 2006, therefore most of you should
already support these newer protocols. Concerned application
developers or those operating applications that support critical
infrastructure should ensure software is up-to-date to support TLS
1.2 and modern encryption ciphers.

Thanks,

Davis Instruments WeatherLink Team.


On 10/20/19 10:28 AM, Thomas Keffer wrote:

The standard approach is to host your own website on a hosting
service that supports FTP or rsync. There are tons of them out
there. Personally, I use Amazon Web Services, but that's not a
simple system. Others are GoDaddy.com, or hostgator.com
, dreamhost.com , and
many, many others.

I don't know anything about WeatherLink, but I suppose it makes
the same assumption: that you will be hosting your own website,
and, if you put in the proper credentials, WeatherLink will FTP
files up to it. But, as I said, I don't know anything about the
program.

Now, posting to the WeatherUnderground and/or CWOP is a
completely different thing. That is done using HTTP, not FTP.

-tk

On Sun, Oct 20, 2019 at 7:10 AM Kevin Phillips
mailto:kh-phill...@9-5usa.org>> wrote:

Thanks for the reply.  I thought it seemed to be working from
what I could tell.  I have re-set the archive interval to 5
minutes.   In terms of whether or not I'm sure their website
supports FTP, my answer has to be "no".  Their Weatherlink
software in Windows has FTP settings in the Internet Settings
window (FTP hostname, FTP logon name, FTP path, etc).  I had
also written Davis Support to ask if anyone had any ideas
about this.  One person responded by telling me to try the
davisinstruments.com  setting
(It had originally been davisnet.com 
from when I first got the station and set up the software).
When I replied that that did not work, a different person
responded and appeared to say that the site did not support
FTP but the reply talked in terms of initial set-up of
Weatherlink which I have had running for a couple of years. 
The response was that I just follow the prompts and "it just
uploads".  While I do agree that the Internet is magic, this
was not quite as helpful or technical response as I had hoped
for.  ;-) 

Re: [weewx-user] ftpuploader timeout with Davis Vantage Pro2 - Weewx on CentOS 7

2019-10-22 Thread Thomas Keffer
Kevin,

I don't think there is much of a mystery here. The Davis site does
*not* support
FTP. I would be surprised if they did: that would make them just
another website provider, which they are not.

What they do support is a proprietary HTTP "RESTful" upload protocol for
their WeatherLink customers. That generally requires a subscription,
although they do offer a crippled version for "3rd parties", which would be
us. However, we do not offer such an upload extension, and have no plans to
do so.

So, you will have to either

1) Set up your own website with a hosting provider. Several were suggested
in an earlier email.
2) Be satisfied with a website on your Local Area Network, that is, your
house. You can supplement this with uploads to CWOP or WeatherUnderground,
or one of the many other upload sites WeeWX supports. Unfortunately,
WeatherLink is not one of them.
3) Give up on WeeWX and go all Davis. Buy their WeatherLink Live logger, or
use a regular logger, but run their WeatherLink Computer Software on a
computer. Either way, you would need a subscription. See their website for
details.

-tk



On Tue, Oct 22, 2019 at 5:33 PM Kevin H. Phillips 
wrote:

> I posed the question to Davis Support of "how" their WeatherLink software
> uploads information to their site.  I haven not yet received a direct
> response from them but I received this evening what appears to be a generic
> message that might contain some clues.  I don't know if someone directed
> this to me or whether this was directed at anyone using their WeatherLink
> software.  Here it is:
>
>
> Dear Developers,
>
> There are upcoming changes to api.weatherlink.com that may affect those
> using SSL to make requests to https://api.weatherlink.com/. The upcoming
> change will disable support for outdated versions of TLS. Developers using
> our API without SSL will not be affected.
>
> Changes:
> On Monday, November 4th, 2019, TLS version 1.0 will be disabled on
> https://api.weatherlink.com
> On Monday, January 6th 2020, TLS version 1.1 will be disabled on
> https://api.weatherlink.com.
>
> Background: TLS 1.0/1.1 protocols have known security vulnerabilities and
> most modern web browsers will remove all support for TLS 1.0/1.1 in January
> of next year. TLS version 1.2 was originally released in 2006, therefore
> most of you should already support these newer protocols. Concerned
> application developers or those operating applications that support
> critical infrastructure should ensure software is up-to-date to support TLS
> 1.2 and modern encryption ciphers.
>
> Thanks,
>
> Davis Instruments WeatherLink Team.
>
>
> On 10/20/19 10:28 AM, Thomas Keffer wrote:
>
> The standard approach is to host your own website on a hosting service
> that supports FTP or rsync. There are tons of them out there. Personally, I
> use Amazon Web Services, but that's not a simple system. Others are
> GoDaddy.com, or hostgator.com, dreamhost.com, and many, many others.
>
> I don't know anything about WeatherLink, but I suppose it makes the same
> assumption: that you will be hosting your own website, and, if you put in
> the proper credentials, WeatherLink will FTP files up to it. But, as I
> said, I don't know anything about the program.
>
> Now, posting to the WeatherUnderground and/or CWOP is a completely
> different thing. That is done using HTTP, not FTP.
>
> -tk
>
> On Sun, Oct 20, 2019 at 7:10 AM Kevin Phillips 
> wrote:
>
>> Thanks for the reply.  I thought it seemed to be working from what I
>> could tell.  I have re-set the archive interval to 5 minutes.   In terms of
>> whether or not I'm sure their website supports FTP, my answer has to be
>> "no".  Their Weatherlink software in Windows has FTP settings in the
>> Internet Settings window (FTP hostname, FTP logon name, FTP path, etc).  I
>> had also written Davis Support to ask if anyone had any ideas about this.
>> One person responded by telling me to try the davisinstruments.com
>> setting (It had originally been davisnet.com from when I first got the
>> station and set up the software).  When I replied that that did not work, a
>> different person responded and appeared to say that the site did not
>> support FTP but the reply talked in terms of initial set-up of Weatherlink
>> which I have had running for a couple of years.  The response was that I
>> just follow the prompts and "it just uploads".  While I do agree that the
>> Internet is magic, this was not quite as helpful or technical response as I
>> had hoped for.  ;-)  They did not respond after I pointed out the FTP
>> jargon in Weatherlink.  So, my question is:  if it does not support FTP,
>> how should I set up the Davis site in weewx?  Thanks again.  Kevin
>>
>> On Sunday, October 20, 2019 at 8:20:49 AM UTC-5, Thomas Keffer wrote:
>>>
>>> Your installation is actually running properly, but there are 3 issues:
>>>
>>> 1. This log entry gives a clue to one of your problems:
>>>
>>> Oct 15 05:43:12 RadioShack weewx[4433]:  device reports 

Re: [weewx-user] ftpuploader timeout with Davis Vantage Pro2 - Weewx on CentOS 7

2019-10-22 Thread Kevin H. Phillips
I posed the question to Davis Support of "how" their WeatherLink 
software uploads information to their site.  I haven not yet received a 
direct response from them but I received this evening what appears to be 
a generic message that might contain some clues.  I don't know if 
someone directed this to me or whether this was directed at anyone using 
their WeatherLink software. Here it is:



Dear Developers,

There are upcoming changes to api.weatherlink.com that may affect those 
using SSL to make requests to https://api.weatherlink.com/. The upcoming 
change will disable support for outdated versions of TLS. Developers 
using our API without SSL will not be affected.


Changes:
On Monday, November 4th, 2019, TLS version 1.0 will be disabled on 
https://api.weatherlink.com
On Monday, January 6th 2020, TLS version 1.1 will be disabled on 
https://api.weatherlink.com.


Background: TLS 1.0/1.1 protocols have known security vulnerabilities 
and most modern web browsers will remove all support for TLS 1.0/1.1 in 
January of next year. TLS version 1.2 was originally released in 2006, 
therefore most of you should already support these newer protocols. 
Concerned application developers or those operating applications that 
support critical infrastructure should ensure software is up-to-date to 
support TLS 1.2 and modern encryption ciphers.


Thanks,

Davis Instruments WeatherLink Team.


On 10/20/19 10:28 AM, Thomas Keffer wrote:
The standard approach is to host your own website on a hosting service 
that supports FTP or rsync. There are tons of them out there. 
Personally, I use Amazon Web Services, but that's not a simple system. 
Others are GoDaddy.com, or hostgator.com , 
dreamhost.com , and many, many others.


I don't know anything about WeatherLink, but I suppose it makes the 
same assumption: that you will be hosting your own website, and, if 
you put in the proper credentials, WeatherLink will FTP files up to 
it. But, as I said, I don't know anything about the program.


Now, posting to the WeatherUnderground and/or CWOP is a completely 
different thing. That is done using HTTP, not FTP.


-tk

On Sun, Oct 20, 2019 at 7:10 AM Kevin Phillips > wrote:


Thanks for the reply.  I thought it seemed to be working from what
I could tell.  I have re-set the archive interval to 5 minutes.  
In terms of whether or not I'm sure their website supports FTP, my
answer has to be "no".  Their Weatherlink software in Windows has
FTP settings in the Internet Settings window (FTP hostname, FTP
logon name, FTP path, etc).  I had also written Davis Support to
ask if anyone had any ideas about this.  One person responded by
telling me to try the davisinstruments.com
 setting (It had originally been
davisnet.com  from when I first got the
station and set up the software). When I replied that that did not
work, a different person responded and appeared to say that the
site did not support FTP but the reply talked in terms of initial
set-up of Weatherlink which I have had running for a couple of
years. The response was that I just follow the prompts and "it
just uploads".  While I do agree that the Internet is magic, this
was not quite as helpful or technical response as I had hoped
for.  ;-)  They did not respond after I pointed out the FTP jargon
in Weatherlink.  So, my question is:  if it does not support FTP,
how should I set up the Davis site in weewx?  Thanks again.  Kevin

On Sunday, October 20, 2019 at 8:20:49 AM UTC-5, Thomas Keffer wrote:

Your installation is actually running properly, but there are
3 issues:

1. This log entry gives a clue to one of your problems:

Oct 15 05:43:12 RadioShack weewx[4433]:  device
reports readiness to read but returned no data (device
disconnected or multiple access on port?)
Oct 15 05:43:12 RadioShack weewx[4433]:  Is there
a competing process running??
Oct 15 05:43:16 RadioShack wee_device[5135]: vantage:
Max retries exceeded while getting EEPROM data at
address 0x29


You cannot run wee_device and weewxd at the same time. They
both need to control the console. Run one or the other, never
both.

2. Are you sure that www.davisinstruments.com
 supports FTP? When I try it,
the connection just times out. I would be very surprised if
they did.

3. Your console has a very long archive interval (1800
seconds, or half an hour). That means it will generate reports
and do the FTP upload only every half an hour. Consider
changing it to 5 minutes by using the utility wee_device with
the 

Re: [weewx-user] ftpuploader timeout with Davis Vantage Pro2 - Weewx on CentOS 7

2019-10-20 Thread Kevin H. Phillips
I will see if I can get any information from Davis Support about what 
their site might use.  I created an entry in weewx.conf similar to the 
one for Wunderground.  I tried two sets of information:  one using the 
Device ID and key generated by the WeatherLink software and another 
using the user-id and password I use to log onto their website.  Neither 
one worked to upload data to their site so I guess it is not HTTP.  I 
enabled both the entries for Wunderground and CWOP and both appear to be 
working now so that's the most important thing to me.



Thanks


Kevin

On 10/20/19 10:28 AM, Thomas Keffer wrote:
The standard approach is to host your own website on a hosting service 
that supports FTP or rsync. There are tons of them out there. 
Personally, I use Amazon Web Services, but that's not a simple system. 
Others are GoDaddy.com, or hostgator.com , 
dreamhost.com , and many, many others.


I don't know anything about WeatherLink, but I suppose it makes the 
same assumption: that you will be hosting your own website, and, if 
you put in the proper credentials, WeatherLink will FTP files up to 
it. But, as I said, I don't know anything about the program.


Now, posting to the WeatherUnderground and/or CWOP is a completely 
different thing. That is done using HTTP, not FTP.


-tk

On Sun, Oct 20, 2019 at 7:10 AM Kevin Phillips > wrote:


Thanks for the reply.  I thought it seemed to be working from what
I could tell.  I have re-set the archive interval to 5 minutes.  
In terms of whether or not I'm sure their website supports FTP, my
answer has to be "no".  Their Weatherlink software in Windows has
FTP settings in the Internet Settings window (FTP hostname, FTP
logon name, FTP path, etc).  I had also written Davis Support to
ask if anyone had any ideas about this.  One person responded by
telling me to try the davisinstruments.com
 setting (It had originally been
davisnet.com  from when I first got the
station and set up the software). When I replied that that did not
work, a different person responded and appeared to say that the
site did not support FTP but the reply talked in terms of initial
set-up of Weatherlink which I have had running for a couple of
years. The response was that I just follow the prompts and "it
just uploads".  While I do agree that the Internet is magic, this
was not quite as helpful or technical response as I had hoped
for.  ;-)  They did not respond after I pointed out the FTP jargon
in Weatherlink.  So, my question is:  if it does not support FTP,
how should I set up the Davis site in weewx?  Thanks again.  Kevin

On Sunday, October 20, 2019 at 8:20:49 AM UTC-5, Thomas Keffer wrote:

Your installation is actually running properly, but there are
3 issues:

1. This log entry gives a clue to one of your problems:

Oct 15 05:43:12 RadioShack weewx[4433]:  device
reports readiness to read but returned no data (device
disconnected or multiple access on port?)
Oct 15 05:43:12 RadioShack weewx[4433]:  Is there
a competing process running??
Oct 15 05:43:16 RadioShack wee_device[5135]: vantage:
Max retries exceeded while getting EEPROM data at
address 0x29


You cannot run wee_device and weewxd at the same time. They
both need to control the console. Run one or the other, never
both.

2. Are you sure that www.davisinstruments.com
 supports FTP? When I try it,
the connection just times out. I would be very surprised if
they did.

3. Your console has a very long archive interval (1800
seconds, or half an hour). That means it will generate reports
and do the FTP upload only every half an hour. Consider
changing it to 5 minutes by using the utility wee_device with
the --set-interval option
.

-tk



On Sat, Oct 19, 2019 at 9:13 PM Kevin Phillips
 wrote:

I am trying to get back into Linux after several years
away.  I recently installed CentOS 7 on a Dell OptiPlex
790.  It has an Intel i5-2400 3.10 ghz process and 4GB of
RAM.  I installed weewx 3.9.2 from the rpm package.  I
have a Davis Vantage Pro2 model 6162 weather station.  It
has a wireless console with the data logger.  I recently
upgraded the console firmware to v3.80.  The computer is
dual-boot with Win7 Professional 64-bit on the other
side.  I have been using the Davis Weatherlink software to
uploaded data to their website 

Re: [weewx-user] ftpuploader timeout with Davis Vantage Pro2 - Weewx on CentOS 7

2019-10-20 Thread Thomas Keffer
The standard approach is to host your own website on a hosting service that
supports FTP or rsync. There are tons of them out there. Personally, I use
Amazon Web Services, but that's not a simple system. Others are
GoDaddy.com, or hostgator.com, dreamhost.com, and many, many others.

I don't know anything about WeatherLink, but I suppose it makes the same
assumption: that you will be hosting your own website, and, if you put in
the proper credentials, WeatherLink will FTP files up to it. But, as I
said, I don't know anything about the program.

Now, posting to the WeatherUnderground and/or CWOP is a completely
different thing. That is done using HTTP, not FTP.

-tk

On Sun, Oct 20, 2019 at 7:10 AM Kevin Phillips 
wrote:

> Thanks for the reply.  I thought it seemed to be working from what I could
> tell.  I have re-set the archive interval to 5 minutes.   In terms of
> whether or not I'm sure their website supports FTP, my answer has to be
> "no".  Their Weatherlink software in Windows has FTP settings in the
> Internet Settings window (FTP hostname, FTP logon name, FTP path, etc).  I
> had also written Davis Support to ask if anyone had any ideas about this.
> One person responded by telling me to try the davisinstruments.com
> setting (It had originally been davisnet.com from when I first got the
> station and set up the software).  When I replied that that did not work, a
> different person responded and appeared to say that the site did not
> support FTP but the reply talked in terms of initial set-up of Weatherlink
> which I have had running for a couple of years.  The response was that I
> just follow the prompts and "it just uploads".  While I do agree that the
> Internet is magic, this was not quite as helpful or technical response as I
> had hoped for.  ;-)  They did not respond after I pointed out the FTP
> jargon in Weatherlink.  So, my question is:  if it does not support FTP,
> how should I set up the Davis site in weewx?  Thanks again.  Kevin
>
> On Sunday, October 20, 2019 at 8:20:49 AM UTC-5, Thomas Keffer wrote:
>>
>> Your installation is actually running properly, but there are 3 issues:
>>
>> 1. This log entry gives a clue to one of your problems:
>>
>> Oct 15 05:43:12 RadioShack weewx[4433]:  device reports readiness to
>>> read but returned no data (device disconnected or multiple access on port?)
>>> Oct 15 05:43:12 RadioShack weewx[4433]:  Is there a competing
>>> process running??
>>> Oct 15 05:43:16 RadioShack wee_device[5135]: vantage: Max retries
>>> exceeded while getting EEPROM data at address 0x29
>>
>>
>> You cannot run wee_device and weewxd at the same time. They both need to
>> control the console. Run one or the other, never both.
>>
>> 2. Are you sure that www.davisinstruments.com supports FTP? When I try
>> it, the connection just times out. I would be very surprised if they did.
>>
>> 3. Your console has a very long archive interval (1800 seconds, or half
>> an hour). That means it will generate reports and do the FTP upload only
>> every half an hour. Consider changing it to 5 minutes by using the utility
>> wee_device with the --set-interval option
>> .
>>
>> -tk
>>
>>
>>
>> On Sat, Oct 19, 2019 at 9:13 PM Kevin Phillips 
>> wrote:
>>
>>> I am trying to get back into Linux after several years away.  I recently
>>> installed CentOS 7 on a Dell OptiPlex 790.  It has an Intel i5-2400 3.10
>>> ghz process and 4GB of RAM.  I installed weewx 3.9.2 from the rpm package.
>>> I have a Davis Vantage Pro2 model 6162 weather station.  It has a wireless
>>> console with the data logger.  I recently upgraded the console firmware to
>>> v3.80.  The computer is dual-boot with Win7 Professional 64-bit on the
>>> other side.  I have been using the Davis Weatherlink software to uploaded
>>> data to their website which then disseminates it to CWOP and Wunderground.
>>> I have not been able to get weewx to upload similarly.  I am using FTP with
>>> the same parameters entered in weewx.conf as I have in Weatherlink.  I
>>> recently upgraded the kernel to 5.3 after reading some information
>>> indicating it might have better hardware support but that did not help.
>>> The Davis console is connected to the computer with a USB cable.  In CentOS
>>> it is connected at /dev/ttyUSB0.  I can enter wee_device --info and get
>>> various error messages regarding the console sleeping/waking up.  I will
>>> copy two of these messages below along with a sample of the log.  The
>>> console will usually wake up after 2-3 attempts like this.  I have been
>>> reading blog posts and have seen several instances of similar behavior but
>>> I have not found an exact match for what I am experiencing nor have I have
>>> a clear solution.  I appear to be able to FTP to the Davis site manually.
>>> Any help is very much appreciated.  Thanks,  Kevin
>>>
>>> Using configuration file /etc/weewx/weewx.conf
>>>
>>> Using Vantage driver version 

Re: [weewx-user] ftpuploader timeout with Davis Vantage Pro2 - Weewx on CentOS 7

2019-10-20 Thread Kevin Phillips
Thanks for the reply.  I thought it seemed to be working from what I could 
tell.  I have re-set the archive interval to 5 minutes.   In terms of 
whether or not I'm sure their website supports FTP, my answer has to be 
"no".  Their Weatherlink software in Windows has FTP settings in the 
Internet Settings window (FTP hostname, FTP logon name, FTP path, etc).  I 
had also written Davis Support to ask if anyone had any ideas about this.  
One person responded by telling me to try the davisinstruments.com setting 
(It had originally been davisnet.com from when I first got the station and 
set up the software).  When I replied that that did not work, a different 
person responded and appeared to say that the site did not support FTP but 
the reply talked in terms of initial set-up of Weatherlink which I have had 
running for a couple of years.  The response was that I just follow the 
prompts and "it just uploads".  While I do agree that the Internet is 
magic, this was not quite as helpful or technical response as I had hoped 
for.  ;-)  They did not respond after I pointed out the FTP jargon in 
Weatherlink.  So, my question is:  if it does not support FTP, how should I 
set up the Davis site in weewx?  Thanks again.  Kevin

On Sunday, October 20, 2019 at 8:20:49 AM UTC-5, Thomas Keffer wrote:
>
> Your installation is actually running properly, but there are 3 issues:
>
> 1. This log entry gives a clue to one of your problems:
>
> Oct 15 05:43:12 RadioShack weewx[4433]:  device reports readiness to 
>> read but returned no data (device disconnected or multiple access on port?)
>> Oct 15 05:43:12 RadioShack weewx[4433]:  Is there a competing process 
>> running??
>> Oct 15 05:43:16 RadioShack wee_device[5135]: vantage: Max retries 
>> exceeded while getting EEPROM data at address 0x29
>
>
> You cannot run wee_device and weewxd at the same time. They both need to 
> control the console. Run one or the other, never both.
>
> 2. Are you sure that www.davisinstruments.com supports FTP? When I try 
> it, the connection just times out. I would be very surprised if they did.
>
> 3. Your console has a very long archive interval (1800 seconds, or half an 
> hour). That means it will generate reports and do the FTP upload only every 
> half an hour. Consider changing it to 5 minutes by using the utility 
> wee_device with the --set-interval option 
> .
>
> -tk
>
>
>
> On Sat, Oct 19, 2019 at 9:13 PM Kevin Phillips  > wrote:
>
>> I am trying to get back into Linux after several years away.  I recently 
>> installed CentOS 7 on a Dell OptiPlex 790.  It has an Intel i5-2400 3.10 
>> ghz process and 4GB of RAM.  I installed weewx 3.9.2 from the rpm package.  
>> I have a Davis Vantage Pro2 model 6162 weather station.  It has a wireless 
>> console with the data logger.  I recently upgraded the console firmware to 
>> v3.80.  The computer is dual-boot with Win7 Professional 64-bit on the 
>> other side.  I have been using the Davis Weatherlink software to uploaded 
>> data to their website which then disseminates it to CWOP and Wunderground.  
>> I have not been able to get weewx to upload similarly.  I am using FTP with 
>> the same parameters entered in weewx.conf as I have in Weatherlink.  I 
>> recently upgraded the kernel to 5.3 after reading some information 
>> indicating it might have better hardware support but that did not help.  
>> The Davis console is connected to the computer with a USB cable.  In CentOS 
>> it is connected at /dev/ttyUSB0.  I can enter wee_device --info and get 
>> various error messages regarding the console sleeping/waking up.  I will 
>> copy two of these messages below along with a sample of the log.  The 
>> console will usually wake up after 2-3 attempts like this.  I have been 
>> reading blog posts and have seen several instances of similar behavior but 
>> I have not found an exact match for what I am experiencing nor have I have 
>> a clear solution.  I appear to be able to FTP to the Davis site manually.  
>> Any help is very much appreciated.  Thanks,  Kevin
>>
>> Using configuration file /etc/weewx/weewx.conf
>>
>> Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
>>
>> Traceback (most recent call last):
>>
>> File "/bin/wee_device", line 66, in 
>>
>> main()
>>
>> File "/bin/wee_device", line 62, in main
>>
>> device.configure(config_dict)
>>
>> File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
>>
>> self.do_options(options, parser, config_dict, prompt)
>>
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1973, in do_options
>>
>> station = Vantage(**config_dict[DRIVER_NAME])
>>
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 488, in __init__
>>
>> self._setup()
>>
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1290, in _setup
>>
>> unit_bits = self._getEEPROM_value(0x29)[0]
>>
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1376, in 

Re: [weewx-user] ftpuploader timeout with Davis Vantage Pro2 - Weewx on CentOS 7

2019-10-20 Thread Thomas Keffer
Your installation is actually running properly, but there are 3 issues:

1. This log entry gives a clue to one of your problems:

Oct 15 05:43:12 RadioShack weewx[4433]:  device reports readiness to
> read but returned no data (device disconnected or multiple access on port?)
> Oct 15 05:43:12 RadioShack weewx[4433]:  Is there a competing process
> running??
> Oct 15 05:43:16 RadioShack wee_device[5135]: vantage: Max retries exceeded
> while getting EEPROM data at address 0x29


You cannot run wee_device and weewxd at the same time. They both need to
control the console. Run one or the other, never both.

2. Are you sure that www.davisinstruments.com supports FTP? When I try it,
the connection just times out. I would be very surprised if they did.

3. Your console has a very long archive interval (1800 seconds, or half an
hour). That means it will generate reports and do the FTP upload only every
half an hour. Consider changing it to 5 minutes by using the utility
wee_device with the --set-interval option
.

-tk



On Sat, Oct 19, 2019 at 9:13 PM Kevin Phillips 
wrote:

> I am trying to get back into Linux after several years away.  I recently
> installed CentOS 7 on a Dell OptiPlex 790.  It has an Intel i5-2400 3.10
> ghz process and 4GB of RAM.  I installed weewx 3.9.2 from the rpm package.
> I have a Davis Vantage Pro2 model 6162 weather station.  It has a wireless
> console with the data logger.  I recently upgraded the console firmware to
> v3.80.  The computer is dual-boot with Win7 Professional 64-bit on the
> other side.  I have been using the Davis Weatherlink software to uploaded
> data to their website which then disseminates it to CWOP and Wunderground.
> I have not been able to get weewx to upload similarly.  I am using FTP with
> the same parameters entered in weewx.conf as I have in Weatherlink.  I
> recently upgraded the kernel to 5.3 after reading some information
> indicating it might have better hardware support but that did not help.
> The Davis console is connected to the computer with a USB cable.  In CentOS
> it is connected at /dev/ttyUSB0.  I can enter wee_device --info and get
> various error messages regarding the console sleeping/waking up.  I will
> copy two of these messages below along with a sample of the log.  The
> console will usually wake up after 2-3 attempts like this.  I have been
> reading blog posts and have seen several instances of similar behavior but
> I have not found an exact match for what I am experiencing nor have I have
> a clear solution.  I appear to be able to FTP to the Davis site manually.
> Any help is very much appreciated.  Thanks,  Kevin
>
> Using configuration file /etc/weewx/weewx.conf
>
> Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
>
> Traceback (most recent call last):
>
> File "/bin/wee_device", line 66, in 
>
> main()
>
> File "/bin/wee_device", line 62, in main
>
> device.configure(config_dict)
>
> File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
>
> self.do_options(options, parser, config_dict, prompt)
>
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1973, in do_options
>
> station = Vantage(**config_dict[DRIVER_NAME])
>
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 488, in __init__
>
> self._setup()
>
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1290, in _setup
>
> unit_bits = self._getEEPROM_value(0x29)[0]
>
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1376, in
> _getEEPROM_value
>
> raise weewx.RetriesExceeded("While getting EEPROM data value at address
> 0x%X" % offset)
>
> weewx.RetriesExceeded: While getting EEPROM data value at address 0x29
>
>
>
> sing configuration file /etc/weewx/weewx.conf
>
> Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
>
> Traceback (most recent call last):
>
> File "/bin/wee_device", line 66, in 
>
> main()
>
> File "/bin/wee_device", line 62, in main
>
> device.configure(config_dict)
>
> File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
>
> self.do_options(options, parser, config_dict, prompt)
>
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1973, in do_options
>
> station = Vantage(**config_dict[DRIVER_NAME])
>
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 489, in __init__
>
> syslog.syslog(syslog.LOG_DEBUG, "vantage: Hardware name: %s" %
> self.hardware_name)
>
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1256, in
> hardware_name
>
> raise weewx.UnsupportedFeature("Unknown hardware type %d" %
> self.hardware_type)
>
> weewx.UnsupportedFeature: Unknown hardware type 79
>
>
>
> [kphillips@RadioShack ~]$ service weewx restart
>
> Restarting weewx (via systemctl): [ OK ]
>
> [kphillips@RadioShack ~]$ sudo tail -f /var/log/messages
>
> [sudo] password for kphillips:
>
> Oct 15 05:38:12 RadioShack weewx[4433]: restx: CWOP: Posting not enabled.
>
> Oct 15 05:38:12 RadioShack weewx[4433]: 

[weewx-user] ftpuploader timeout with Davis Vantage Pro2 - Weewx on CentOS 7

2019-10-19 Thread Kevin Phillips
I am trying to get back into Linux after several years away.  I recently 
installed CentOS 7 on a Dell OptiPlex 790.  It has an Intel i5-2400 3.10 
ghz process and 4GB of RAM.  I installed weewx 3.9.2 from the rpm package.  
I have a Davis Vantage Pro2 model 6162 weather station.  It has a wireless 
console with the data logger.  I recently upgraded the console firmware to 
v3.80.  The computer is dual-boot with Win7 Professional 64-bit on the 
other side.  I have been using the Davis Weatherlink software to uploaded 
data to their website which then disseminates it to CWOP and Wunderground.  
I have not been able to get weewx to upload similarly.  I am using FTP with 
the same parameters entered in weewx.conf as I have in Weatherlink.  I 
recently upgraded the kernel to 5.3 after reading some information 
indicating it might have better hardware support but that did not help.  
The Davis console is connected to the computer with a USB cable.  In CentOS 
it is connected at /dev/ttyUSB0.  I can enter wee_device --info and get 
various error messages regarding the console sleeping/waking up.  I will 
copy two of these messages below along with a sample of the log.  The 
console will usually wake up after 2-3 attempts like this.  I have been 
reading blog posts and have seen several instances of similar behavior but 
I have not found an exact match for what I am experiencing nor have I have 
a clear solution.  I appear to be able to FTP to the Davis site manually.  
Any help is very much appreciated.  Thanks,  Kevin

Using configuration file /etc/weewx/weewx.conf

Using Vantage driver version 3.1.1 (weewx.drivers.vantage)

Traceback (most recent call last):

File "/bin/wee_device", line 66, in 

main()

File "/bin/wee_device", line 62, in main

device.configure(config_dict)

File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure

self.do_options(options, parser, config_dict, prompt)

File "/usr/share/weewx/weewx/drivers/vantage.py", line 1973, in do_options

station = Vantage(**config_dict[DRIVER_NAME])

File "/usr/share/weewx/weewx/drivers/vantage.py", line 488, in __init__

self._setup()

File "/usr/share/weewx/weewx/drivers/vantage.py", line 1290, in _setup

unit_bits = self._getEEPROM_value(0x29)[0]

File "/usr/share/weewx/weewx/drivers/vantage.py", line 1376, in 
_getEEPROM_value

raise weewx.RetriesExceeded("While getting EEPROM data value at address 
0x%X" % offset)

weewx.RetriesExceeded: While getting EEPROM data value at address 0x29



sing configuration file /etc/weewx/weewx.conf

Using Vantage driver version 3.1.1 (weewx.drivers.vantage)

Traceback (most recent call last):

File "/bin/wee_device", line 66, in 

main()

File "/bin/wee_device", line 62, in main

device.configure(config_dict)

File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure

self.do_options(options, parser, config_dict, prompt)

File "/usr/share/weewx/weewx/drivers/vantage.py", line 1973, in do_options

station = Vantage(**config_dict[DRIVER_NAME])

File "/usr/share/weewx/weewx/drivers/vantage.py", line 489, in __init__

syslog.syslog(syslog.LOG_DEBUG, "vantage: Hardware name: %s" % 
self.hardware_name)

File "/usr/share/weewx/weewx/drivers/vantage.py", line 1256, in 
hardware_name

raise weewx.UnsupportedFeature("Unknown hardware type %d" % 
self.hardware_type)

weewx.UnsupportedFeature: Unknown hardware type 79



[kphillips@RadioShack ~]$ service weewx restart

Restarting weewx (via systemctl): [ OK ]

[kphillips@RadioShack ~]$ sudo tail -f /var/log/messages

[sudo] password for kphillips: 

Oct 15 05:38:12 RadioShack weewx[4433]: restx: CWOP: Posting not enabled.

Oct 15 05:38:12 RadioShack weewx[4433]: restx: WOW: Posting not enabled.

Oct 15 05:38:12 RadioShack weewx[4433]: restx: AWEKAS: Posting not enabled.

Oct 15 05:38:12 RadioShack weewx[4433]: engine: Starting up weewx version 
3.9.2

Oct 15 05:38:12 RadioShack weewx[4433]: engine: Clock error is 2.16 seconds 
(positive is fast)

Oct 15 05:38:12 RadioShack weewx[4433]: engine: Starting main packet loop.

Oct 15 05:38:41 RadioShack dbus[971]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service'

Oct 15 05:38:41 RadioShack systemd: Starting Fingerprint Authentication 
Daemon...

Oct 15 05:38:41 RadioShack dbus[971]: [system] Successfully activated 
service 'net.reactivated.Fprint'

Oct 15 05:38:41 RadioShack systemd: Started Fingerprint Authentication 
Daemon.

Oct 15 05:40:01 RadioShack systemd: Created slice User Slice of root.

Oct 15 05:40:01 RadioShack systemd: Started Session 3 of user root.

Oct 15 05:40:01 RadioShack systemd: Removed slice User Slice of root.

Oct 15 05:41:03 RadioShack systemd: Starting Cleanup of Temporary 
Directories...

Oct 15 05:41:03 RadioShack systemd: Started Cleanup of Temporary 
Directories.

Oct 15 05:42:52 RadioShack dbus[971]: [system] Activating via systemd: 
service name='net.reactivated.Fprint' unit='fprintd.service'

Oct 15 05:42:52 RadioShack