[weewx-user] Davis Vantage Pro2 - Weather Wing WS-2

[Massimiliano Buldrini]

I have a Weather Wing WS-2 connected to a Davis Vantage Pro2.
My console is connected with the serial data logger.
I want to connect my console to weewx with raspberry. Do I have to connect 
it with a USB/serial adapter to my raspberry or can I use Weather Wing WS-2 
which has an ethernet port?

Regards
MB

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1100f0ce-a3ec-4899-971d-fa9b75a80bf7n%40googlegroups.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Tom Keffer]

First time I've heard of that problem. Good to know!

Glad to hear that the problem has been fixed.

On Tue, Jul 6, 2021 at 10:25 PM Vasya Pupkin 
wrote:

> I was  stupid  idiot.
> I must  remove  power and battarey from  station when   insert weatherlink
> adapter.
> I  did  not remove   battarey when  plug it.
> Problem fixed
>
>
> среда, 7 июля 2021 г. в 07:59:35 UTC+3, Vasya Pupkin:
>
>> I  try belfryboy logger 2.3 with   it -  problem  is same
>>
>>
>> среда, 7 июля 2021 г. в 07:48:16 UTC+3, Vasya Pupkin:
>>
>>> It's  not  cable   problem. I use 4 different  cables and have  same
>>> problem on all
>>> I think   i  use  old  station (prod date  on  board is 2012 year)
>>>
>>> вторник, 6 июля 2021 г. в 23:48:27 UTC+3, tke...@gmail.com:
>>>
 Thanks.

 I would suspect the serial-to-usb cable. They are notoriously
 unreliable. Do you have another one? Alternatively, does your computer have
 a true serial port that you can use (instead of a USB port).

 I know the logger worked under Windows, but the Weatherlink software
 probably uses a different strategy. It may not even check for the 
 character.

 -tk

 On Tue, Jul 6, 2021 at 1:42 PM Vasya Pupkin 
 wrote:

> Welcome to minicom 2.7.1
>
> OPTIONS: I18n
> Compiled on May  6 2018, 08:02:47.
> Port /dev/ttyUSB1, 23:41:36
>
> Press CTRL-A Z for help on special keys
>
>  D. þk.!5¢.þPC
>
>
> вторник, 6 июля 2021 г. в 23:41:01 UTC+3, Vasya Pupkin:
>
>> Oh.. sorry
>> I use   serial-USB  adapter.  And  i use   same   cable for
>> connection to  pc with   weatherlink and weewx
>> when  i  try totype   TEST  in consolestation   replay
>>  with  that string
>> it was   replay for  minicom -b 19200 -D /dev/ttyUSB1
>>
>>
>> вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com:
>>
>>> On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin 
>>> wrote:
>>>
 In  console   it  write someting strange
>>>
>>>
>>> Sorry. I don't know what you mean by that. What is "it"? What
>>> command did you run?
>>>
>>> You said you used the same USB cable for both the linux and Windows
>>> tests. What kind of cable is it? Does it use a serial-to-usb converter?
>>>
>> --
>
 You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx-user+...@googlegroups.com.
>
 To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/13714d73-dfc6-49a7-83ed-ecb33825d258n%40googlegroups.com
> 
> .
>
 --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/65b35c0d-9a37-41e0-8fc5-30240e7faa9an%40googlegroups.com
> 
> .
>

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

Re: [weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

I was  stupid  idiot.
I must  remove  power and battarey from  station when   insert weatherlink 
adapter.
I  did  not remove   battarey when  plug it.
Problem fixed


среда, 7 июля 2021 г. в 07:59:35 UTC+3, Vasya Pupkin: 

> I  try belfryboy logger 2.3 with   it -  problem  is same
>
>
> среда, 7 июля 2021 г. в 07:48:16 UTC+3, Vasya Pupkin: 
>
>> It's  not  cable   problem. I use 4 different  cables and have  same 
>> problem on all
>> I think   i  use  old  station (prod date  on  board is 2012 year) 
>>
>> вторник, 6 июля 2021 г. в 23:48:27 UTC+3, tke...@gmail.com: 
>>
>>> Thanks.
>>>
>>> I would suspect the serial-to-usb cable. They are notoriously 
>>> unreliable. Do you have another one? Alternatively, does your computer have 
>>> a true serial port that you can use (instead of a USB port).
>>>
>>> I know the logger worked under Windows, but the Weatherlink software 
>>> probably uses a different strategy. It may not even check for the  
>>> character.
>>>
>>> -tk
>>>
>>> On Tue, Jul 6, 2021 at 1:42 PM Vasya Pupkin  wrote:
>>>
 Welcome to minicom 2.7.1

 OPTIONS: I18n 
 Compiled on May  6 2018, 08:02:47.
 Port /dev/ttyUSB1, 23:41:36

 Press CTRL-A Z for help on special keys

  D. þk.!5¢.þPC 


 вторник, 6 июля 2021 г. в 23:41:01 UTC+3, Vasya Pupkin: 

> Oh.. sorry
> I use   serial-USB  adapter.  And  i use   same   cable for connection 
> to  pc with   weatherlink and weewx
> when  i  try totype   TEST  in consolestation   replay   with  
> that string
> it was   replay for  minicom -b 19200 -D /dev/ttyUSB1
>
>
> вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com: 
>
>> On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin  
>> wrote:
>>
>>> In  console   it  write someting strange 
>>
>>  
>> Sorry. I don't know what you mean by that. What is "it"? What command 
>> did you run?
>>
>> You said you used the same USB cable for both the linux and Windows 
>> tests. What kind of cable is it? Does it use a serial-to-usb converter?
>>
> -- 

>>> You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx-user+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/13714d73-dfc6-49a7-83ed-ecb33825d258n%40googlegroups.com
  
 
 .

>>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/65b35c0d-9a37-41e0-8fc5-30240e7faa9an%40googlegroups.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

I  try belfryboy logger 2.3 with   it -  problem  is same


среда, 7 июля 2021 г. в 07:48:16 UTC+3, Vasya Pupkin: 

> It's  not  cable   problem. I use 4 different  cables and have  same 
> problem on all
> I think   i  use  old  station (prod date  on  board is 2012 year) 
>
> вторник, 6 июля 2021 г. в 23:48:27 UTC+3, tke...@gmail.com: 
>
>> Thanks.
>>
>> I would suspect the serial-to-usb cable. They are notoriously unreliable. 
>> Do you have another one? Alternatively, does your computer have a true 
>> serial port that you can use (instead of a USB port).
>>
>> I know the logger worked under Windows, but the Weatherlink software 
>> probably uses a different strategy. It may not even check for the  
>> character.
>>
>> -tk
>>
>> On Tue, Jul 6, 2021 at 1:42 PM Vasya Pupkin  wrote:
>>
>>> Welcome to minicom 2.7.1
>>>
>>> OPTIONS: I18n 
>>> Compiled on May  6 2018, 08:02:47.
>>> Port /dev/ttyUSB1, 23:41:36
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>>  D. þk.!5¢.þPC 
>>>
>>>
>>> вторник, 6 июля 2021 г. в 23:41:01 UTC+3, Vasya Pupkin: 
>>>
 Oh.. sorry
 I use   serial-USB  adapter.  And  i use   same   cable for connection 
 to  pc with   weatherlink and weewx
 when  i  try totype   TEST  in consolestation   replay   with  
 that string
 it was   replay for  minicom -b 19200 -D /dev/ttyUSB1


 вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com: 

> On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin  
> wrote:
>
>> In  console   it  write someting strange 
>
>  
> Sorry. I don't know what you mean by that. What is "it"? What command 
> did you run?
>
> You said you used the same USB cable for both the linux and Windows 
> tests. What kind of cable is it? Does it use a serial-to-usb converter?
>
 -- 
>>>
>> You received this message because you are subscribed to the Google Groups 
>>> "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/13714d73-dfc6-49a7-83ed-ecb33825d258n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b09290dd-5258-4fd5-a53d-0c00fc5e30f5n%40googlegroups.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

It's  not  cable   problem. I use 4 different  cables and have  same 
problem on all
I think   i  use  old  station (prod date  on  board is 2012 year) 

вторник, 6 июля 2021 г. в 23:48:27 UTC+3, tke...@gmail.com: 

> Thanks.
>
> I would suspect the serial-to-usb cable. They are notoriously unreliable. 
> Do you have another one? Alternatively, does your computer have a true 
> serial port that you can use (instead of a USB port).
>
> I know the logger worked under Windows, but the Weatherlink software 
> probably uses a different strategy. It may not even check for the  
> character.
>
> -tk
>
> On Tue, Jul 6, 2021 at 1:42 PM Vasya Pupkin  wrote:
>
>> Welcome to minicom 2.7.1
>>
>> OPTIONS: I18n 
>> Compiled on May  6 2018, 08:02:47.
>> Port /dev/ttyUSB1, 23:41:36
>>
>> Press CTRL-A Z for help on special keys
>>
>>  D. þk.!5¢.þPC 
>>
>>
>> вторник, 6 июля 2021 г. в 23:41:01 UTC+3, Vasya Pupkin: 
>>
>>> Oh.. sorry
>>> I use   serial-USB  adapter.  And  i use   same   cable for connection 
>>> to  pc with   weatherlink and weewx
>>> when  i  try totype   TEST  in consolestation   replay   with  
>>> that string
>>> it was   replay for  minicom -b 19200 -D /dev/ttyUSB1
>>>
>>>
>>> вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com: 
>>>
 On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin  
 wrote:

> In  console   it  write someting strange 

  
 Sorry. I don't know what you mean by that. What is "it"? What command 
 did you run?

 You said you used the same USB cable for both the linux and Windows 
 tests. What kind of cable is it? Does it use a serial-to-usb converter?

>>> -- 
>>
> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/13714d73-dfc6-49a7-83ed-ecb33825d258n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e26a2b11-ce97-4265-8d49-1b5362bbcb75n%40googlegroups.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

Yes  baudrate = 19200

вторник, 6 июля 2021 г. в 23:52:03 UTC+3, peterq...@gmail.com: 

> I'm guessing. Are you using the same baud rate for both Windows and Linux?
>
> On Tue, Jul 6, 2021 at 1:48 PM Tom Keffer  wrote:
>
>> Thanks.
>>
>> I would suspect the serial-to-usb cable. They are notoriously unreliable. 
>> Do you have another one? Alternatively, does your computer have a true 
>> serial port that you can use (instead of a USB port).
>>
>> I know the logger worked under Windows, but the Weatherlink software 
>> probably uses a different strategy. It may not even check for the  
>> character.
>>
>> -tk
>>
>> On Tue, Jul 6, 2021 at 1:42 PM Vasya Pupkin  wrote:
>>
>>> Welcome to minicom 2.7.1
>>>
>>> OPTIONS: I18n 
>>> Compiled on May  6 2018, 08:02:47.
>>> Port /dev/ttyUSB1, 23:41:36
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>>  D. þk.!5¢.þPC 
>>>
>>>
>>> вторник, 6 июля 2021 г. в 23:41:01 UTC+3, Vasya Pupkin: 
>>>
 Oh.. sorry
 I use   serial-USB  adapter.  And  i use   same   cable for connection 
 to  pc with   weatherlink and weewx
 when  i  try totype   TEST  in consolestation   replay   with  
 that string
 it was   replay for  minicom -b 19200 -D /dev/ttyUSB1


 вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com: 

> On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin  
> wrote:
>
>> In  console   it  write someting strange 
>
>  
> Sorry. I don't know what you mean by that. What is "it"? What command 
> did you run?
>
> You said you used the same USB cable for both the linux and Windows 
> tests. What kind of cable is it? Does it use a serial-to-usb converter?
>
 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/13714d73-dfc6-49a7-83ed-ecb33825d258n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEA%3DUTc9oRXT4O4Ar8YRnZzFF%2B-nXjBkjx5dXM-EKoFaLA%40mail.gmail.com
>>  
>> 
>> .
>>
>
>
> -- 
> Peter Quinn
> (415)794-2264 <(415)%20794-2264>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/26bb488c-f732-482a-bfdc-c0e1a09d099dn%40googlegroups.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

1.   I  have  external   usb-com  converters but  i  use  WeatherLink USB 
Data Logger,  so i can  not use another converter
2.  I  use  weewx  with this station  few  years  ago. Last weewx  version 
was 3.8.2 and all work  fine
Maybe   there was  changes   in driver?

For cables  -  i will  check

вторник, 6 июля 2021 г. в 23:48:27 UTC+3, tke...@gmail.com: 

> Thanks.
>
> I would suspect the serial-to-usb cable. They are notoriously unreliable. 
> Do you have another one? Alternatively, does your computer have a true 
> serial port that you can use (instead of a USB port).
>
> I know the logger worked under Windows, but the Weatherlink software 
> probably uses a different strategy. It may not even check for the  
> character.
>
> -tk
>
> On Tue, Jul 6, 2021 at 1:42 PM Vasya Pupkin  wrote:
>
>> Welcome to minicom 2.7.1
>>
>> OPTIONS: I18n 
>> Compiled on May  6 2018, 08:02:47.
>> Port /dev/ttyUSB1, 23:41:36
>>
>> Press CTRL-A Z for help on special keys
>>
>>  D. þk.!5¢.þPC 
>>
>>
>> вторник, 6 июля 2021 г. в 23:41:01 UTC+3, Vasya Pupkin: 
>>
>>> Oh.. sorry
>>> I use   serial-USB  adapter.  And  i use   same   cable for connection 
>>> to  pc with   weatherlink and weewx
>>> when  i  try totype   TEST  in consolestation   replay   with  
>>> that string
>>> it was   replay for  minicom -b 19200 -D /dev/ttyUSB1
>>>
>>>
>>> вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com: 
>>>
 On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin  
 wrote:

> In  console   it  write someting strange 

  
 Sorry. I don't know what you mean by that. What is "it"? What command 
 did you run?

 You said you used the same USB cable for both the linux and Windows 
 tests. What kind of cable is it? Does it use a serial-to-usb converter?

>>> -- 
>>
> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/13714d73-dfc6-49a7-83ed-ecb33825d258n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/06d46d64-df68-4828-9c7d-00fb916ff895n%40googlegroups.com.

Re: [weewx-user] davis vantage pro2 ACK error

[p q]

I'm guessing. Are you using the same baud rate for both Windows and Linux?

On Tue, Jul 6, 2021 at 1:48 PM Tom Keffer  wrote:

> Thanks.
>
> I would suspect the serial-to-usb cable. They are notoriously unreliable.
> Do you have another one? Alternatively, does your computer have a true
> serial port that you can use (instead of a USB port).
>
> I know the logger worked under Windows, but the Weatherlink software
> probably uses a different strategy. It may not even check for the 
> character.
>
> -tk
>
> On Tue, Jul 6, 2021 at 1:42 PM Vasya Pupkin 
> wrote:
>
>> Welcome to minicom 2.7.1
>>
>> OPTIONS: I18n
>> Compiled on May  6 2018, 08:02:47.
>> Port /dev/ttyUSB1, 23:41:36
>>
>> Press CTRL-A Z for help on special keys
>>
>>  D. þk.!5¢.þPC
>>
>>
>> вторник, 6 июля 2021 г. в 23:41:01 UTC+3, Vasya Pupkin:
>>
>>> Oh.. sorry
>>> I use   serial-USB  adapter.  And  i use   same   cable for connection
>>> to  pc with   weatherlink and weewx
>>> when  i  try totype   TEST  in consolestation   replay   with
>>> that string
>>> it was   replay for  minicom -b 19200 -D /dev/ttyUSB1
>>>
>>>
>>> вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com:
>>>
 On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin 
 wrote:

> In  console   it  write someting strange


 Sorry. I don't know what you mean by that. What is "it"? What command
 did you run?

 You said you used the same USB cable for both the linux and Windows
 tests. What kind of cable is it? Does it use a serial-to-usb converter?

>>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/13714d73-dfc6-49a7-83ed-ecb33825d258n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEA%3DUTc9oRXT4O4Ar8YRnZzFF%2B-nXjBkjx5dXM-EKoFaLA%40mail.gmail.com
> 
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAA1SM237yCNNX8PyygXU6ydX6za4pw7kBket7AX%3DUZ5EPD%3Dx5A%40mail.gmail.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Tom Keffer]

Thanks.

I would suspect the serial-to-usb cable. They are notoriously unreliable.
Do you have another one? Alternatively, does your computer have a true
serial port that you can use (instead of a USB port).

I know the logger worked under Windows, but the Weatherlink software
probably uses a different strategy. It may not even check for the 
character.

-tk

On Tue, Jul 6, 2021 at 1:42 PM Vasya Pupkin  wrote:

> Welcome to minicom 2.7.1
>
> OPTIONS: I18n
> Compiled on May  6 2018, 08:02:47.
> Port /dev/ttyUSB1, 23:41:36
>
> Press CTRL-A Z for help on special keys
>
>  D. þk.!5¢.þPC
>
>
> вторник, 6 июля 2021 г. в 23:41:01 UTC+3, Vasya Pupkin:
>
>> Oh.. sorry
>> I use   serial-USB  adapter.  And  i use   same   cable for connection
>> to  pc with   weatherlink and weewx
>> when  i  try totype   TEST  in consolestation   replay   with
>> that string
>> it was   replay for  minicom -b 19200 -D /dev/ttyUSB1
>>
>>
>> вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com:
>>
>>> On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin  wrote:
>>>
 In  console   it  write someting strange
>>>
>>>
>>> Sorry. I don't know what you mean by that. What is "it"? What command
>>> did you run?
>>>
>>> You said you used the same USB cable for both the linux and Windows
>>> tests. What kind of cable is it? Does it use a serial-to-usb converter?
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/13714d73-dfc6-49a7-83ed-ecb33825d258n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEA%3DUTc9oRXT4O4Ar8YRnZzFF%2B-nXjBkjx5dXM-EKoFaLA%40mail.gmail.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on May  6 2018, 08:02:47.
Port /dev/ttyUSB1, 23:41:36

Press CTRL-A Z for help on special keys

 D. þk.!5¢.þPC 


вторник, 6 июля 2021 г. в 23:41:01 UTC+3, Vasya Pupkin: 

> Oh.. sorry
> I use   serial-USB  adapter.  And  i use   same   cable for connection to  
> pc with   weatherlink and weewx
> when  i  try totype   TEST  in consolestation   replay   with  
> that string
> it was   replay for  minicom -b 19200 -D /dev/ttyUSB1
>
>
> вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com: 
>
>> On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin  wrote:
>>
>>> In  console   it  write someting strange 
>>
>>  
>> Sorry. I don't know what you mean by that. What is "it"? What command did 
>> you run?
>>
>> You said you used the same USB cable for both the linux and Windows 
>> tests. What kind of cable is it? Does it use a serial-to-usb converter?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/13714d73-dfc6-49a7-83ed-ecb33825d258n%40googlegroups.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

Oh.. sorry
I use   serial-USB  adapter.  And  i use   same   cable for connection to  
pc with   weatherlink and weewx
when  i  try totype   TEST  in consolestation   replay   with  that 
string
it was   replay for  minicom -b 19200 -D /dev/ttyUSB1


вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com: 

> On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin  wrote:
>
>> In  console   it  write someting strange 
>
>  
> Sorry. I don't know what you mean by that. What is "it"? What command did 
> you run?
>
> You said you used the same USB cable for both the linux and Windows tests. 
> What kind of cable is it? Does it use a serial-to-usb converter?
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bf80b790-9222-47a2-96ff-2728d2adb5abn%40googlegroups.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

Oh.. sorry
I use   serial-USB  adapter.  And  i use   same   cable for connection to  
pc with   weatherlink and weewx
when  i  try totype   TEST  in consolestation   replay   with  that 
string

вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com: 

> On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin  wrote:
>
>> In  console   it  write someting strange 
>
>  
> Sorry. I don't know what you mean by that. What is "it"? What command did 
> you run?
>
> You said you used the same USB cable for both the linux and Windows tests. 
> What kind of cable is it? Does it use a serial-to-usb converter?
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3165f4c8-a3ad-4417-9dc4-213674072b31n%40googlegroups.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

Oh.. sorry
I use   serial-USB  adapter.  And  i use   same   cable for connection to  
pc with   weatherlink and win
when  i  try totype   TEST  in consolestation   replay   with  that 
string

вторник, 6 июля 2021 г. в 23:25:30 UTC+3, tke...@gmail.com: 

> On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin  wrote:
>
>> In  console   it  write someting strange 
>
>  
> Sorry. I don't know what you mean by that. What is "it"? What command did 
> you run?
>
> You said you used the same USB cable for both the linux and Windows tests. 
> What kind of cable is it? Does it use a serial-to-usb converter?
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/89eb53db-72eb-4f5e-82b8-964eb06f70cbn%40googlegroups.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Tom Keffer]

On Tue, Jul 6, 2021 at 1:22 PM Vasya Pupkin  wrote:

> In  console   it  write someting strange


Sorry. I don't know what you mean by that. What is "it"? What command did
you run?

You said you used the same USB cable for both the linux and Windows tests.
What kind of cable is it? Does it use a serial-to-usb converter?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEBYzjWx-tPuhx7MDs25NwqJsshurqjE6E_RVaa0b0R%3DpQ%40mail.gmail.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

In  console   it  write someting strange 

D%­%ݡ%­%D)­%oa»+v%ÿ


вторник, 6 июля 2021 г. в 22:38:49 UTC+3, Vasya Pupkin: 

> Connection is ok
>
> In  log  there is
>  Jul  6 22:38:06 hass weewx[8079] DEBUG weewx.drivers.vantage: Opened up 
> serial port /dev/ttyUSB1; baud 19200; timeout 120.00
> Jul  6 22:38:06 hass weewx[8079] DEBUG weewx.drivers.vantage: Gentle wake 
> up of console successful
>
>
> вторник, 6 июля 2021 г. в 22:18:43 UTC+3, tke...@gmail.com: 
>
>> The first step is to make sure you have connectivity to your station. 
>> Take a look at the wiki article *Establishing connectivity 
>> *.
>>  
>>
>>
>> If it passes those tests, then we'll take a closer look.
>>
>> On Tue, Jul 6, 2021 at 11:59 AM Vasya Pupkin  wrote:
>>
>>> Hi all  Now  i try  to recover   my weather  station
>>> On  windows  it connect .  And all is ok:  station work  with  
>>> weatherlink 
>>> On  both  computers  i  use  same   usb cable
>>>
>>> But when  i  plug it  to  linux pc with weewx I have problem:  it can't  
>>>  start
>>>
>>> I add   to  /etc/init.d/weewx 
>>> to DAEMON_ARGS flag  --loop-on-init
>>> and  set   timeout 120 sec in config
>>>
>>>
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/b54643d4--40e5-af42-0c4db10f4566n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ec1338e8-b082-4ed7-97c4-6679333b8de7n%40googlegroups.com.

Re: [weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

Connection is ok

In  log  there is
 Jul  6 22:38:06 hass weewx[8079] DEBUG weewx.drivers.vantage: Opened up 
serial port /dev/ttyUSB1; baud 19200; timeout 120.00
Jul  6 22:38:06 hass weewx[8079] DEBUG weewx.drivers.vantage: Gentle wake 
up of console successful


вторник, 6 июля 2021 г. в 22:18:43 UTC+3, tke...@gmail.com: 

> The first step is to make sure you have connectivity to your station. Take 
> a look at the wiki article *Establishing connectivity 
> *.
>  
>
>
> If it passes those tests, then we'll take a closer look.
>
> On Tue, Jul 6, 2021 at 11:59 AM Vasya Pupkin  wrote:
>
>> Hi all  Now  i try  to recover   my weather  station
>> On  windows  it connect .  And all is ok:  station work  with  
>> weatherlink 
>> On  both  computers  i  use  same   usb cable
>>
>> But when  i  plug it  to  linux pc with weewx I have problem:  it can't  
>>  start
>>
>> I add   to  /etc/init.d/weewx 
>> to DAEMON_ARGS flag  --loop-on-init
>> and  set   timeout 120 sec in config
>>
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/b54643d4--40e5-af42-0c4db10f4566n%40googlegroups.com
>>  
>> 
>> .
>>
>

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

Re: [weewx-user] davis vantage pro2 ACK error

[Tom Keffer]

The first step is to make sure you have connectivity to your station. Take
a look at the wiki article *Establishing connectivity
*.


If it passes those tests, then we'll take a closer look.

On Tue, Jul 6, 2021 at 11:59 AM Vasya Pupkin 
wrote:

> Hi all  Now  i try  to recover   my weather  station
> On  windows  it connect .  And all is ok:  station work  with  weatherlink
> On  both  computers  i  use  same   usb cable
>
> But when  i  plug it  to  linux pc with weewx I have problem:  it can't
>  start
>
> I add   to  /etc/init.d/weewx
> to DAEMON_ARGS flag  --loop-on-init
> and  set   timeout 120 sec in config
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/b54643d4--40e5-af42-0c4db10f4566n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zECkzjgDjmn487-VT6-E99wACk3becpW%2BOvBd%2Bg-0KDn3w%40mail.gmail.com.

[weewx-user] davis vantage pro2 ACK error

[Vasya Pupkin]

Hi all  Now  i try  to recover   my weather  station
On  windows  it connect .  And all is ok:  station work  with  weatherlink 
On  both  computers  i  use  same   usb cable

But when  i  plug it  to  linux pc with weewx I have problem:  it can't  
 start

I add   to  /etc/init.d/weewx 
to DAEMON_ARGS flag  --loop-on-init
and  set   timeout 120 sec in config



-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b54643d4--40e5-af42-0c4db10f4566n%40googlegroups.com.
Jul  6 21:47:57 hass weewx[21665] INFO __main__: retrying...
Jul  6 21:47:57 hass weewx[21665] INFO __main__: Using configuration file 
/etc/weewx/weewx.conf
Jul  6 21:47:57 hass weewx[21665] INFO __main__: Debug is 1
Jul  6 21:47:57 hass weewx[21665] DEBUG __main__: Initializing engine
Jul  6 21:47:57 hass weewx[21665] INFO weewx.engine: Loading station type 
Vantage (weewx.drivers.vantage)
Jul  6 21:47:57 hass weewx[21665] DEBUG weewx.drivers.vantage: Driver version 
is 3.2.2
Jul  6 21:47:57 hass weewx[21665] DEBUG weewx.drivers.vantage: Option 
loop_request=1
Jul  6 21:47:57 hass weewx[21665] DEBUG weewx.drivers.vantage: Opened up serial 
port /dev/ttyUSB1; baud 19200; timeout 120.00
Jul  6 21:47:57 hass weewx[21665] DEBUG weewx.drivers.vantage: Gentle wake up 
of console successful
Jul  6 21:47:57 hass weewx[21665] ERROR weewx.drivers.vantage: No  
received from console
Jul  6 21:47:57 hass weewx[21665] ERROR weewx.drivers.vantage: 
_determine_hardware; retry #0: 'No  received from Vantage console'
Jul  6 21:47:57 hass weewx[21665] ERROR weewx.drivers.vantage: No  
received from console
Jul  6 21:47:57 hass weewx[21665] ERROR weewx.drivers.vantage: 
_determine_hardware; retry #1: 'No  received from Vantage console'
Jul  6 21:47:57 hass weewx[21665] ERROR weewx.drivers.vantage: No  
received from console
Jul  6 21:47:57 hass weewx[21665] ERROR weewx.drivers.vantage: 
_determine_hardware; retry #2: 'No  received from Vantage console'
Jul  6 21:47:57 hass weewx[21665] ERROR weewx.drivers.vantage: No  
received from console
Jul  6 21:47:57 hass weewx[21665] ERROR weewx.drivers.vantage: 
_determine_hardware; retry #3: 'No  received from Vantage console'
Jul  6 21:47:57 hass weewx[21665] ERROR weewx.drivers.vantage: Unable to read 
hardware type; raise WeeWxIOError
Jul  6 21:47:57 hass weewx[21665] ERROR weewx.engine: Import of driver failed: 
Unable to read hardware type ()
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine:   Traceback 
(most recent call last):
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/engine.py", line 119, in setupStation
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine:   
self.console = loader_function(config_dict, self)
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine:   return 
VantageService(engine, config_dict)
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/vantage.py", line 1899, in __init__
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine:   
Vantage.__init__(self, **config_dict[DRIVER_NAME])
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/vantage.py", line 516, in __init__
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine:   
self._setup()
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/vantage.py", line 1322, in _setup
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine:   
self.hardware_type = self._determine_hardware()
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/vantage.py", line 1313, in _determine_hardware
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine:   raise 
weewx.WeeWxIOError("Unable to read hardware type")
Jul  6 21:47:57 hass weewx[21665] CRITICAL weewx.engine:   
weewx.WeeWxIOError: Unable to read hardware type
Jul  6 21:47:57 hass weewx[21665] CRITICAL __main__: Unable to load driver: 
Unable to read hardware type
Jul  6 21:47:57 hass weewx[21665] CRITICAL __main__:   Waiting 60 
seconds then retrying...

Re: [weewx-user] Davis vantage pro2

['Peter Fletcher' via weewx-user]

I have used a variety of loggers with my Davis VP 2+ - for many years 
directly connected to Windows systems; subsequently (but also for 2-3 years 
now) to a Raspberry Pi. I can say without doubt that the Meteo-Pi, once set 
up, has given me fewer problems than the Davis alternatives. It also allows 
the Davis console to be powered directly from the Pi through the same cable 
as carries the serial data, slightly reducing cable clutter. The console 
draws so little power that the extra load is no problem for a Pi power 
supply. I should, perhaps, add the disclaimer that I was a beta-tester for 
a number of the devices created and sold by the Meteo-Pi''s producer, so I 
got mine free, but I get no other income or other benefit from ongoing 
sales of the devices.

On Saturday, April 10, 2021 at 3:29:36 PM UTC-4 vince wrote:

> On Saturday, April 10, 2021 at 11:18:07 AM UTC-7 chris.th...@gmail.com 
> wrote:
>
>> so I found this:
>> https://shop.weatherstations.co.uk/meteo-pi-1832-p.asp
>> seems like you can connect the davis console directly to raspberry pi 
>> header and use via serial.
>> anyone tried this with weewx?
>> Seems a bit cheaper than the weatherlink option and maybe more suitable 
>> for my needs.
>>
>
> A real Davis logger is $30 US more expensive than a Meteo-pi.   You have 
> to ask yourself how important that 30 bucks is, as compared to your time 
> and stress level of using a third-party logger.  Personally I'd recommend 
> just going Davis all the way.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/640040fd-0277-496c-baa3-9bc64c7a7404n%40googlegroups.com.

Re: [weewx-user] Davis vantage pro2

[Greg Troxel]

Chris Thompstone  writes:

> So basically if I want to use weewx with davis station and Pi.  I'd need:
> https://www.weathershop.co.uk/shop/brands/davis-instruments/vantage-pro/davis-vantage-pro2-cabled-weather-station
> plus
> https://www.weathershop.co.uk/shop/accessories/spares-by-brands/davis-spare-parts-accessories/davis-accessories-upgrades/vantage-pro/davis-6510-weatherlink-serial
>
> This should be a reliable problem free setup?

Well, more reliable than anything else in the sub-$1000 price class.
Basically the history on the list is that Davis users complain about how
expensive things are, and other users talk about failures of their
hardware.  That's not 100% fair, but it is my rough percepion.

I have never used a Davis cabled station.   But I haven't heard
complaints.

> Think unfortunately there is very little choice of weather station if you 
> want something that's going to last and you can get spares for.
> Thanks for the advice.

Yes, that is unfortunate but that is how I see it.   especially if you
add the "no cloud" requirement.

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


signature.asc
Description: PGP signature

Re: [weewx-user] Davis vantage pro2

[vince]

US prices on scaledinstruments.com are 30 US different.  I can't speak to 
UK prices/taxes/import etc.


On Saturday, April 10, 2021 at 12:59:40 PM UTC-7 chris.th...@gmail.com 
wrote:

>
> £89 vs £165 in the UK
> not sure where the 30$ fits in?
>
> am I looking at the wrong thing?
> On Saturday, 10 April 2021 at 20:29:36 UTC+1 vince wrote:
>
>> On Saturday, April 10, 2021 at 11:18:07 AM UTC-7 chris.th...@gmail.com 
>> wrote:
>>
>>> so I found this:
>>> https://shop.weatherstations.co.uk/meteo-pi-1832-p.asp
>>> seems like you can connect the davis console directly to raspberry pi 
>>> header and use via serial.
>>> anyone tried this with weewx?
>>> Seems a bit cheaper than the weatherlink option and maybe more suitable 
>>> for my needs.
>>>
>>
>> A real Davis logger is $30 US more expensive than a Meteo-pi.   You have 
>> to ask yourself how important that 30 bucks is, as compared to your time 
>> and stress level of using a third-party logger.  Personally I'd recommend 
>> just going Davis all the way.
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1153caa8-16e8-4f7b-a19f-2f518f736718n%40googlegroups.com.

Re: [weewx-user] Davis vantage pro2

[Chris Thompstone]

£89 vs £165 in the UK
not sure where the 30$ fits in?

am I looking at the wrong thing?
On Saturday, 10 April 2021 at 20:29:36 UTC+1 vince wrote:

> On Saturday, April 10, 2021 at 11:18:07 AM UTC-7 chris.th...@gmail.com 
> wrote:
>
>> so I found this:
>> https://shop.weatherstations.co.uk/meteo-pi-1832-p.asp
>> seems like you can connect the davis console directly to raspberry pi 
>> header and use via serial.
>> anyone tried this with weewx?
>> Seems a bit cheaper than the weatherlink option and maybe more suitable 
>> for my needs.
>>
>
> A real Davis logger is $30 US more expensive than a Meteo-pi.   You have 
> to ask yourself how important that 30 bucks is, as compared to your time 
> and stress level of using a third-party logger.  Personally I'd recommend 
> just going Davis all the way.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6f79f14a-e8b6-49f2-b378-ab31819c798bn%40googlegroups.com.

Re: [weewx-user] Davis vantage pro2

[vince]

On Saturday, April 10, 2021 at 11:18:07 AM UTC-7 chris.th...@gmail.com 
wrote:

> so I found this:
> https://shop.weatherstations.co.uk/meteo-pi-1832-p.asp
> seems like you can connect the davis console directly to raspberry pi 
> header and use via serial.
> anyone tried this with weewx?
> Seems a bit cheaper than the weatherlink option and maybe more suitable 
> for my needs.
>

A real Davis logger is $30 US more expensive than a Meteo-pi.   You have to 
ask yourself how important that 30 bucks is, as compared to your time and 
stress level of using a third-party logger.  Personally I'd recommend just 
going Davis all the way.


-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9fd412e0-a38a-43e1-93dd-349911329ec4n%40googlegroups.com.

Re: [weewx-user] Davis vantage pro2

[Chris Thompstone]

so I found this:
https://shop.weatherstations.co.uk/meteo-pi-1832-p.asp
seems like you can connect the davis console directly to raspberry pi 
header and use via serial.
anyone tried this with weewx?
Seems a bit cheaper than the weatherlink option and maybe more suitable for 
my needs.
T

On Saturday, 10 April 2021 at 17:02:53 UTC+1 Chris Thompstone wrote:

> So basically if I want to use weewx with davis station and Pi.  I'd need:
>
> https://www.weathershop.co.uk/shop/brands/davis-instruments/vantage-pro/davis-vantage-pro2-cabled-weather-station
> plus
>
> https://www.weathershop.co.uk/shop/accessories/spares-by-brands/davis-spare-parts-accessories/davis-accessories-upgrades/vantage-pro/davis-6510-weatherlink-serial
>
> This should be a reliable problem free setup?
> Think unfortunately there is very little choice of weather station if you 
> want something that's going to last and you can get spares for.
> Thanks for the advice.
> On Saturday, 10 April 2021 at 16:23:34 UTC+1 Greg Troxel wrote:
>
>>
>> Chris Thompstone  writes: 
>>
>> > [davis query] 
>>
>> > I like a wired station setup, due to reliability/simplicity and it must 
>> > work with weewx reliably. (no periodic fiddling or messing) 
>> > So was thinking a vantage pro2 wired with a serial interface to connect 
>> to 
>> > my Pi. 
>> > 
>> > To be honest not interested in the console as I generally never look at 
>> > them. Can't see the point when I can use the weewx on my phone or PC. 
>> If 
>> > I had my way there would be a blank box with serial socket to connect 
>> the 
>> > Pi to, plus power, nothing more. 
>> > 
>> > But I guess I have to have that anyway, but does the console have the 
>> > serial connection on it to get to the Pi? How do I go from my serial 
>> USB 
>> > cable on my Pi to the Davis? Do I have to buy something else? 
>> > 
>> > Not interested in any of the Davis logging stuff, just want the raw 
>> data 
>> > flowing into weewx on a Pi, nothing more. 
>>
>> Here's one solution: 
>>
>> Davis Vantage Pro wired 
>> ISS outside 
>> console inside 
>>
>> Davis serial datalogger #6510SER 
>> plugged into console 
>>
>> the datalogger has a DB9 and plugs into a usb/serial adaptor (or an 
>> actual serial port). I'm using an prolific adaptor 
>>
>> weewx configured to talk to the USB serial port 
>>
>> system that is running weewx has a battery-backed RTC so it knows the 
>> data when it boots. A workaround is scripts to not start weewx until 
>> the computer is affirmatively synchronized with NTP. 
>>
>> For me, this setup has been reliable. 
>>
>> You said you weren't interested in some things but I wanted to point 
>> out: 
>>
>> My VP2 is wireless. I have had zero trouble with the wireless part. 
>> I have had to replace the CR123 in the ISS maybe a few times in 10 
>> years. I had a VP(non-2) and that wireless worked, but I think the 
>> supercap failed and it's on my list to fix. However, I am not sure if 
>> the wired option provides power to the ISS, or if it's just the data 
>> link. I don't mean to suggest you are wrong to do wired, just that I 
>> went wireless because wires were awkward and it has been ok. 
>>
>> The pressure sensor is in the console, as is indoor temp/humidity. 
>> The ISS only has wind/rain and outside temp/humidity. So even if you 
>> don't look at the console, without it you will not have pressure/temp. 
>>
>> There is a "weather envoy" which I think still needs a datalogger to 
>> plug in which is more or less a console without a display but I'm not 
>> sure about pressure. I have neer seen one or used it. 
>>
>> You can get a VP2+ with solar radiation and UV sensors on the ISS, or 
>> you can add them later. 
>>
>> There are third-party loggers and interfaces. I decided to just pay 
>> for the davis one even though it costs double the third-party ones, 
>> because I was confident I would have no trouble. I have nothing bad 
>> to say about the third-party stuff -- I just haven't tried it. There 
>> are some that have datalogging and some that don't. 
>>
>> You said you were not interested in logging, just raw data to Pi, but 
>> I think that's a mistake. The davis logger records data every 5 
>> minutes (hardware archive interval, configurable) and will do so on 
>> the 3 D cell batteries in the console for multiple days during a power 
>> failure. When the weewx computer starts up it will get the old 
>> archive records and put them in the weewx database. This has happened 
>> to me mulitple times and worked very well. So I have continuous data 
>> over several storms where I would have had a gap. If your RPI is on a 
>> UPS/generator that can go 2 weeks AND if it is *never* down for more 
>> than 5 minutes even when you have sd card trouble or upgrade trouble 
>> then you don't need the logger. As you can guess I don't believe 
>> this. If you really don't mind losing data, then yes you don't need 
>> the logger. 
>>
>> If you mean you aren't interested in having the equipment send data t

Re: [weewx-user] Davis vantage pro2

[Chris Thompstone]

So basically if I want to use weewx with davis station and Pi.  I'd need:
https://www.weathershop.co.uk/shop/brands/davis-instruments/vantage-pro/davis-vantage-pro2-cabled-weather-station
plus
https://www.weathershop.co.uk/shop/accessories/spares-by-brands/davis-spare-parts-accessories/davis-accessories-upgrades/vantage-pro/davis-6510-weatherlink-serial

This should be a reliable problem free setup?
Think unfortunately there is very little choice of weather station if you 
want something that's going to last and you can get spares for.
Thanks for the advice.
On Saturday, 10 April 2021 at 16:23:34 UTC+1 Greg Troxel wrote:

>
> Chris Thompstone  writes:
>
> > [davis query]
>
> > I like a wired station setup, due to reliability/simplicity and it must 
> > work with weewx reliably. (no periodic fiddling or messing)
> > So was thinking a vantage pro2 wired with a serial interface to connect 
> to 
> > my Pi.
> >
> > To be honest not interested in the console as I generally never look at 
> > them. Can't see the point when I can use the weewx on my phone or PC. If 
> > I had my way there would be a blank box with serial socket to connect 
> the 
> > Pi to, plus power, nothing more.
> >
> > But I guess I have to have that anyway, but does the console have the 
> > serial connection on it to get to the Pi? How do I go from my serial USB 
> > cable on my Pi to the Davis? Do I have to buy something else?
> >
> > Not interested in any of the Davis logging stuff, just want the raw data 
> > flowing into weewx on a Pi, nothing more.
>
> Here's one solution:
>
> Davis Vantage Pro wired
> ISS outside
> console inside
>
> Davis serial datalogger #6510SER
> plugged into console
>
> the datalogger has a DB9 and plugs into a usb/serial adaptor (or an
> actual serial port). I'm using an prolific adaptor
>
> weewx configured to talk to the USB serial port
>
> system that is running weewx has a battery-backed RTC so it knows the
> data when it boots. A workaround is scripts to not start weewx until
> the computer is affirmatively synchronized with NTP.
>
> For me, this setup has been reliable.
>
> You said you weren't interested in some things but I wanted to point
> out:
>
> My VP2 is wireless. I have had zero trouble with the wireless part.
> I have had to replace the CR123 in the ISS maybe a few times in 10
> years. I had a VP(non-2) and that wireless worked, but I think the
> supercap failed and it's on my list to fix. However, I am not sure if
> the wired option provides power to the ISS, or if it's just the data
> link. I don't mean to suggest you are wrong to do wired, just that I
> went wireless because wires were awkward and it has been ok.
>
> The pressure sensor is in the console, as is indoor temp/humidity.
> The ISS only has wind/rain and outside temp/humidity. So even if you
> don't look at the console, without it you will not have pressure/temp.
>
> There is a "weather envoy" which I think still needs a datalogger to
> plug in which is more or less a console without a display but I'm not
> sure about pressure. I have neer seen one or used it.
>
> You can get a VP2+ with solar radiation and UV sensors on the ISS, or
> you can add them later.
>
> There are third-party loggers and interfaces. I decided to just pay
> for the davis one even though it costs double the third-party ones,
> because I was confident I would have no trouble. I have nothing bad
> to say about the third-party stuff -- I just haven't tried it. There
> are some that have datalogging and some that don't.
>
> You said you were not interested in logging, just raw data to Pi, but
> I think that's a mistake. The davis logger records data every 5
> minutes (hardware archive interval, configurable) and will do so on
> the 3 D cell batteries in the console for multiple days during a power
> failure. When the weewx computer starts up it will get the old
> archive records and put them in the weewx database. This has happened
> to me mulitple times and worked very well. So I have continuous data
> over several storms where I would have had a gap. If your RPI is on a
> UPS/generator that can go 2 weeks AND if it is *never* down for more
> than 5 minutes even when you have sd card trouble or upgrade trouble
> then you don't need the logger. As you can guess I don't believe
> this. If you really don't mind losing data, then yes you don't need
> the logger.
>
> If you mean you aren't interested in having the equipment send data to
> the davis cloud where you have trouble geting it back from, then
> agreed :-)
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/790cde1f-b15a-4d61-b261-00e672851414n%40googlegroups.com.

Re: [weewx-user] Davis vantage pro2

[Greg Troxel]

Chris Thompstone  writes:

> [davis query]

> I like a wired station setup, due to reliability/simplicity and it must 
> work with weewx reliably. (no periodic fiddling or messing)
> So was thinking a vantage pro2 wired with a serial interface to connect to 
> my Pi.
>
> To be honest not interested in the console as I generally never look at 
> them.  Can't see the point when I can use the weewx on my phone or PC.  If 
> I had my way there would be a blank box with serial socket to connect the 
> Pi to, plus power, nothing more.
>
> But I guess I have to have that anyway, but does the console have the 
> serial connection on it to get to the Pi?  How do I go from my serial USB 
> cable on my Pi to the Davis?  Do I have to buy something else?
>
> Not interested in any of the Davis logging stuff, just want the raw data 
> flowing into weewx on a Pi, nothing more.

Here's one solution:

  Davis Vantage Pro wired
ISS outside
console inside

  Davis serial datalogger #6510SER
plugged into console

  the datalogger has a DB9 and plugs into a usb/serial adaptor (or an
  actual serial port).  I'm using an prolific adaptor

  weewx configured to talk to the USB serial port

  system that is running weewx has a battery-backed RTC so it knows the
  data when it boots.   A workaround is scripts to not start weewx until
  the computer is affirmatively synchronized with NTP.

For me, this setup has been reliable.

You said you weren't interested in some things but I wanted to point
out:

  My VP2 is wireless.  I have had zero trouble with the wireless part.
  I have had to replace the CR123 in the ISS maybe a few times in 10
  years.  I had a VP(non-2) and that wireless worked, but I think the
  supercap failed and it's on my list to fix.  However, I am not sure if
  the wired option provides power to the ISS, or if it's just the data
  link.  I don't mean to suggest you are wrong to do wired, just that I
  went wireless because wires were awkward and it has been ok.

  The pressure sensor is in the console, as is indoor temp/humidity.
  The ISS only has wind/rain and outside temp/humidity.   So even if you
  don't look at the console, without it you will not have pressure/temp.

  There is a "weather envoy" which I think still needs a datalogger to
  plug in which is more or less a console without a display but I'm not
  sure about pressure.   I have neer seen one or used it.

  You can get a VP2+ with solar radiation and UV sensors on the ISS, or
  you can add them later.

  There are third-party loggers and interfaces.  I decided to just pay
  for the davis one even though it costs double the third-party ones,
  because I was confident I would have no trouble.  I have nothing bad
  to say about the third-party stuff -- I just haven't tried it.  There
  are some that have datalogging and some that don't.

  You said you were not interested in logging, just raw data to Pi, but
  I think that's a mistake.  The davis logger records data every 5
  minutes (hardware archive interval, configurable) and will do so on
  the 3 D cell batteries in the console for multiple days during a power
  failure.  When the weewx computer starts up it will get the old
  archive records and put them in the weewx database.  This has happened
  to me mulitple times and worked very well.  So I have continuous data
  over several storms where I would have had a gap.  If your RPI is on a
  UPS/generator that can go 2 weeks AND if it is *never* down for more
  than 5 minutes even when you have sd card trouble or upgrade trouble
  then you don't need the logger.  As you can guess I don't believe
  this.  If you really don't mind losing data, then yes you don't need
  the logger.

  If you mean you aren't interested in having the equipment send data to
  the davis cloud where you have trouble geting it back from, then
  agreed :-)
  

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


signature.asc
Description: PGP signature

[weewx-user] Davis vantage pro2

[Chris Thompstone]

Hi Guys can you help me understand the Davis products?
My Peet Bros wind vane has blown off the roof again.  Didn't last long.
Although the first one lasted about 5 years, this one's done maybe 2 at 
best.

I can't seem to get a new wind vane for it unless I import from the US, 
which is not a great idea (done before etc very expensive with the taxes, 
then it breaks, repeat repeat)

So think I'll have to replace the whole station, which I didn't really want 
to do.  But at least I'll get spares from UK shops.

I like a wired station setup, due to reliability/simplicity and it must 
work with weewx reliably. (no periodic fiddling or messing)
So was thinking a vantage pro2 wired with a serial interface to connect to 
my Pi.

To be honest not interested in the console as I generally never look at 
them.  Can't see the point when I can use the weewx on my phone or PC.  If 
I had my way there would be a blank box with serial socket to connect the 
Pi to, plus power, nothing more.

But I guess I have to have that anyway, but does the console have the 
serial connection on it to get to the Pi?  How do I go from my serial USB 
cable on my Pi to the Davis?  Do I have to buy something else?

Not interested in any of the Davis logging stuff, just want the raw data 
flowing into weewx on a Pi, nothing more.
Thanks
Chris
Have tried to understand this from the Davis website, but can't work it 
out, think they just trying to sell a logging package which I don't want.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/027853dc-0951-40e2-8670-07faaa172c56n%40googlegroups.com.

Re: [weewx-user] Davis Vantage Pro2 Wind Direction Issue

[Peter_F]

Thanks for the tip Thomas.  Yes, it is a wireless VP2.  I had tried moving 
the console before but I gave it another go and it made no difference.  I 
do get good signal strength with rxCheckPercent close to 100%.

- Peter


On Friday, August 16, 2019 at 8:54:27 PM UTC+9:30, Thomas Keffer wrote:
>
> Sounds like you're having a bad week!
>
> I assume this is a wireless VP2? I once had a similar experience that was 
> cured by moving the console. The RF reception between ISS and console was 
> so poor it resulted in a wind direction that was wrong, or didn't change.
>
> As an experiment, can you try moving the console closer?
>
> -tk
>
> On Thu, Aug 15, 2019 at 7:01 PM Peter_F > 
> wrote:
>
>> This may be the wrong forum for this but I have Googled this to death and 
>> no apparent answer.
>>
>> I have had my Davis Vantage Pro2 for over four years and have had no 
>> issues (Console on my desk and an Envoy with data logger plugged into RPi 
>> running WeeWX).  A few weeks ago I noticed on the console that the Wind 
>> Direction was locked onto due south (180 degrees).  Wind Speed is working 
>> OK.  The Envoy was showing the same on WeeWX.  The Console and Envoy have 
>> an offset configured for 180 degrees because the anemometer is pointing 
>> South instead of North because I want the solar panels pointing North as I 
>> am in the Southern Hemisphere.
>>
>> After checking connections, etc and finding no issues, I bit the bullet 
>> and bought a new anemometer.  To my disappointment, the problem persisted 
>> with the new anemometer.  I spoke to Davis and they said it must be the 
>> Transmitter Board so I reluctantly purchased a new one from them.  I have 
>> installed it and the problem STILL persists.  After ringing Davis again, 
>> they tried to blame the Raspberry Pi which makes no sense as the Console is 
>> not connected to the RPi.
>>
>> Since then I have tried various things - changing Transmitter channel, 
>> Firmware updates, unplugging all other sensors from the ISS - but to no 
>> avail.  Very occasionally the Wind Direction does work, but not for very 
>> long.  Other knowledgeable people I have spoken to (no knowledge about 
>> Davis Weather Stations though) said it's probably electrical interference.  
>> All the answers I can find is either a busted anemometer or a broken wire.  
>> I have replaced both the anemometer (comes with new cable) and also the 
>> Transmitter.  There's not much else to replace.
>>
>> When I ordered the new anemometer, I gave the old one to a friend who is 
>> interested in building his own Weather Station from discrete sensors and 
>> micro-controllers.  He was interested in pulling it apart and possibly 
>> fixing it.  He said the anemometer works no problems.
>>
>> I'm at my wit's end.  I have thrown a few hundred AU$ at this and have 
>> got nowhere.  To really rub it in, my Envoy decided to die the other day.  
>> I don't have the cash to replace that so I have moved the data logger to 
>> the console and now running WeeWX off that.
>>
>> Anyone have any ideas?
>>
>> - Peter
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/79acf77e-3076-4bac-b882-cdbee3cb16ca%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8e586f03-f57b-4057-ae47-fdb148c39ce7%40googlegroups.com.

Re: [weewx-user] Davis Vantage Pro2 Wind Direction Issue

[Thomas Keffer]

Sounds like you're having a bad week!

I assume this is a wireless VP2? I once had a similar experience that was
cured by moving the console. The RF reception between ISS and console was
so poor it resulted in a wind direction that was wrong, or didn't change.

As an experiment, can you try moving the console closer?

-tk

On Thu, Aug 15, 2019 at 7:01 PM Peter_F  wrote:

> This may be the wrong forum for this but I have Googled this to death and
> no apparent answer.
>
> I have had my Davis Vantage Pro2 for over four years and have had no
> issues (Console on my desk and an Envoy with data logger plugged into RPi
> running WeeWX).  A few weeks ago I noticed on the console that the Wind
> Direction was locked onto due south (180 degrees).  Wind Speed is working
> OK.  The Envoy was showing the same on WeeWX.  The Console and Envoy have
> an offset configured for 180 degrees because the anemometer is pointing
> South instead of North because I want the solar panels pointing North as I
> am in the Southern Hemisphere.
>
> After checking connections, etc and finding no issues, I bit the bullet
> and bought a new anemometer.  To my disappointment, the problem persisted
> with the new anemometer.  I spoke to Davis and they said it must be the
> Transmitter Board so I reluctantly purchased a new one from them.  I have
> installed it and the problem STILL persists.  After ringing Davis again,
> they tried to blame the Raspberry Pi which makes no sense as the Console is
> not connected to the RPi.
>
> Since then I have tried various things - changing Transmitter channel,
> Firmware updates, unplugging all other sensors from the ISS - but to no
> avail.  Very occasionally the Wind Direction does work, but not for very
> long.  Other knowledgeable people I have spoken to (no knowledge about
> Davis Weather Stations though) said it's probably electrical interference.
> All the answers I can find is either a busted anemometer or a broken wire.
> I have replaced both the anemometer (comes with new cable) and also the
> Transmitter.  There's not much else to replace.
>
> When I ordered the new anemometer, I gave the old one to a friend who is
> interested in building his own Weather Station from discrete sensors and
> micro-controllers.  He was interested in pulling it apart and possibly
> fixing it.  He said the anemometer works no problems.
>
> I'm at my wit's end.  I have thrown a few hundred AU$ at this and have got
> nowhere.  To really rub it in, my Envoy decided to die the other day.  I
> don't have the cash to replace that so I have moved the data logger to the
> console and now running WeeWX off that.
>
> Anyone have any ideas?
>
> - Peter
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/79acf77e-3076-4bac-b882-cdbee3cb16ca%40googlegroups.com
> 
> .
>

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

[weewx-user] Davis Vantage Pro2 Wind Direction Issue

[Peter_F]

This may be the wrong forum for this but I have Googled this to death and 
no apparent answer.

I have had my Davis Vantage Pro2 for over four years and have had no issues 
(Console on my desk and an Envoy with data logger plugged into RPi running 
WeeWX).  A few weeks ago I noticed on the console that the Wind Direction 
was locked onto due south (180 degrees).  Wind Speed is working OK.  The 
Envoy was showing the same on WeeWX.  The Console and Envoy have an offset 
configured for 180 degrees because the anemometer is pointing South instead 
of North because I want the solar panels pointing North as I am in the 
Southern Hemisphere.

After checking connections, etc and finding no issues, I bit the bullet and 
bought a new anemometer.  To my disappointment, the problem persisted with 
the new anemometer.  I spoke to Davis and they said it must be the 
Transmitter Board so I reluctantly purchased a new one from them.  I have 
installed it and the problem STILL persists.  After ringing Davis again, 
they tried to blame the Raspberry Pi which makes no sense as the Console is 
not connected to the RPi.

Since then I have tried various things - changing Transmitter channel, 
Firmware updates, unplugging all other sensors from the ISS - but to no 
avail.  Very occasionally the Wind Direction does work, but not for very 
long.  Other knowledgeable people I have spoken to (no knowledge about 
Davis Weather Stations though) said it's probably electrical interference.  
All the answers I can find is either a busted anemometer or a broken wire.  
I have replaced both the anemometer (comes with new cable) and also the 
Transmitter.  There's not much else to replace.

When I ordered the new anemometer, I gave the old one to a friend who is 
interested in building his own Weather Station from discrete sensors and 
micro-controllers.  He was interested in pulling it apart and possibly 
fixing it.  He said the anemometer works no problems.

I'm at my wit's end.  I have thrown a few hundred AU$ at this and have got 
nowhere.  To really rub it in, my Envoy decided to die the other day.  I 
don't have the cash to replace that so I have moved the data logger to the 
console and now running WeeWX off that.

Anyone have any ideas?

- Peter

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/79acf77e-3076-4bac-b882-cdbee3cb16ca%40googlegroups.com.

Re: [weewx-user] Davis Vantage Pro2 no data

[gjr80]

My recollection is that the 'incorrect system time at startup' issue has 
been one that seems to rear its head every now and then. Whilst the 
preferred solution is to have a battery backed RTC there have been various 
approaches taken in the WeeWX code base to ameliorate the situation where a 
battery backed RTC does not exist. These approaches have primarily been 
because of issues with the RPi but apply equally to any device. I believe 
the current approach is for WeeWX to block on startup until it sees a 
system date-time that is the same or more recent that than the weewx.conf 
file timestamp. The reasoning being that a system with no battery backed 
RTC or is yet to sync via NTP will revert to a system date-time of 
somewhere in the 1970s (epoch start ?) and weewx.conf will always be 
timestamped later than the startup date-time. The obvious issue here is the 
RPi fake hardware clock that will cause the RPi to reboot with a more 
recent system date-time, one that could be more recent than the weewx.conf 
timestamp, and hence could still cause issues with a near but not close 
enough system date-time. The solution thus relies on the RPi fake hardware 
clock being disabled.

Perhaps the issue is compounded by changes from jessie to stretch (systemd 
handling of time sync ?), but I don't see the point in going off down 
another rabbit hole until we know the current approach does not work. I 
agree the problem is likely system time related but I have not yet seen 
anything in any of the recent threads that shows that when properly 
implemented the current approach is failing.

Gary

On Friday, 31 May 2019 19:55:46 UTC+10, Liz wrote:
>
> On Thu, 30 May 2019 04:58:37 -0700 (PDT) 
> mwall > wrote: 
>
> > i am sure there are other scenarios... 
> > 
> > m 
>
> Thankyou mwall for a better discussion of the options. 
>
> Liz 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/4b39d5b7-0bed-41ba-985e-8d2e4c884221%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[Liz]

On Thu, 30 May 2019 04:58:37 -0700 (PDT)
mwall  wrote:

> i am sure there are other scenarios...
> 
> m

Thankyou mwall for a better discussion of the options.

Liz

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

Re: [weewx-user] Davis Vantage Pro2 no data

[John]

Andrew,

I am not having a problem with records in the weewx database with incorrect 
timestamps. I am having a problem with weewx not downloading data from the 
console after an extended power outage.  The underlying problem seems to be 
that if weewx updates the console clock to something earlier than the last 
record in the console's data logger, then weewx will break.  The quick 
solution is to disable weewx from updating the console clock. 



On Wednesday, May 29, 2019 at 9:32:55 PM UTC-5, Andrew Milner wrote:
>
> John
> the issue is not with syncing the clock as such.  The issues are caused by 
> records in the database with weewx generated timestamps which will be 
> incorrect if weewx is started with an incorrect time set on the rpi.  The 
> solution is to install an rtc on the rpi and to be honest I just do not 
> understand your reluctance since they only cost 10-12 dollars.  a computer 
> needs a clock - a teaching aid (as the rpi was designed for originally) 
> doesn't.  Give your RPi a clock!
>
>
>
> On Thursday, 30 May 2019 00:26:54 UTC+3, John wrote:
>>
>> I've disabled weewx from syncing the vantage console's clock. I had an 
>> another power outage yesterday for a bit over an hour and everything seemed 
>> to eventually recover without intervention. The battery backed clock in the 
>> vantage console seems to be adequate. Most routines for syncing battery 
>> backed clocks seem to protect against gross changes, requiring a 
>> manual/forced update if the time deltas are larger than a routine drift. 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ac110c9f-efe4-4af8-8e73-e63b0e2396dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[mwall]

On Tuesday, May 28, 2019 at 11:00:09 AM UTC-4, John wrote:
>
> I propose changing the vantage driver to avert setting the console time, 
> during a routine sync, earlier than the last record in the console. This 
> should prevent weewx from adjusting the console time until the weewx host 
> has had an opportunity to successfully acquire the time from an external 
> source (ntp server).   I suppose setting the console to a future time could 
> cause a problem, preventing weewx from correcting the console time without 
> first clearing the last (errant) record.
>

merge requests are welcome!

it might help to clarify the scenarios before pushing for a specific 
solution.

scenario 1: standalone rpi.  options are to install a clock, depend on ntp, 
or both.  if network is flaky, then the clock might be preferred.  in 
either case, get rid of fakehwclock.  if you depend on setting time over 
the network, then absolutely get rid of the systemd timesync and install a 
real service such as ntp.

scenario 2: rpi on your own network where you can control time.  run an ntp 
server on your network, sync it to a other ntp servers or your own gps or 
other device with known reliable time.  get rid of any systemd rubbish and 
install ntp on the rpi, then configure it to use your time server.

scenario 3: use the weather station's clock to set the rpi clock.  this 
could be done independently of weewx, and probably in a pretty generic way 
that could work for many types of stations.  or it could be done in the 
weewx driver (less desirable).  or it could be done as a generic weewx 
service.  you'll probably never get it to be as accurate as ntp, but it 
might be good enough.

i am sure there are other scenarios...

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/510ed650-de25-4d57-b188-95a4ef752d94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[Oliver Giessler]

Just my 2 Cent as the thread opener:

I solved my problem by removing the batteries from my Vantage Pro2 and 
having just the powercord. Do not ask my why this solved it …




On 28 May 2019, at 17:15, Andrew Milner wrote:

I would recommend you doing the CORRECT solution and installing an RTC 
on

your Pi zero.  Weewx relies HEAVILY on accurate time synchronisation
between weather station and controlling PC - so ensuring your pi 
EITHER has
an RTC onboard OR prevents weewx starting until time has been 
synchronised

is ESSENTIAL for correct operation.

There are many many users of weewx with Davis stations, and many many 
of us

with various models of RPi.  There are also many instances of logger
corruptions and other anomolies.. so fudging the driver for one 
situation
may open a can of worms in another situation - you have been 
warned!




On Tuesday, 28 May 2019 18:00:09 UTC+3, John wrote:


so looking at the vantage driver it seems that if the weewx host
(raspberry pi zero without a RTC) has an incorrect time like after a
restart and syncs it's bad (early) time with the vantage console, 
then
records being added to the vantage console will have an earlier 
timestamp
than existing records. when weewx goes to read the records and finds 
a
"decreasing timestamp" it stops reading more records. manually 
clearing all

the records AND setting the correct time is a solution.

I propose changing the vantage driver to avert setting the console 
time,
during a routine sync, earlier than the last record in the console. 
This
should prevent weewx from adjusting the console time until the weewx 
host
has had an opportunity to successfully acquire the time from an 
external
source (ntp server).   I suppose setting the console to a future time 
could
cause a problem, preventing weewx from correcting the console time 
without

first clearing the last (errant) record.




--
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/UM-q_RNK_Ps/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/32f79d61-7d81-4bc0-adab-6d1ad66de99c%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2D60CD0D-A875-4959-8D80-D83DEA6A2C0C%40giessler.de.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[Andrew Milner]

John
the issue is not with syncing the clock as such.  The issues are caused by 
records in the database with weewx generated timestamps which will be 
incorrect if weewx is started with an incorrect time set on the rpi.  The 
solution is to install an rtc on the rpi and to be honest I just do not 
understand your reluctance since they only cost 10-12 dollars.  a computer 
needs a clock - a teaching aid (as the rpi was designed for originally) 
doesn't.  Give your RPi a clock!



On Thursday, 30 May 2019 00:26:54 UTC+3, John wrote:
>
> I've disabled weewx from syncing the vantage console's clock. I had an 
> another power outage yesterday for a bit over an hour and everything seemed 
> to eventually recover without intervention. The battery backed clock in the 
> vantage console seems to be adequate. Most routines for syncing battery 
> backed clocks seem to protect against gross changes, requiring a 
> manual/forced update if the time deltas are larger than a routine drift. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/f43b61e2-153e-40f8-aef6-e77ab070a5af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[John]

I've disabled weewx from syncing the vantage console's clock. I had an 
another power outage yesterday for a bit over an hour and everything seemed 
to eventually recover without intervention. The battery backed clock in the 
vantage console seems to be adequate. Most routines for syncing battery 
backed clocks seem to protect against gross changes, requiring a 
manual/forced update if the time deltas are larger than a routine drift. 

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/83e54e6d-fefe-48a9-b039-dd914a8f2a56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[Andrew Milner]

fitting a RTC is the best solution to make the RPi more like a 'normal' 
computer - especially when used for real world production use.  

On Tuesday, 28 May 2019 22:44:38 UTC+3, John wrote:
>
> The instructions for delaying weewx from starting on the Raspberry Pi 
> until time is synced don't seem to be working with stretch and timesyncd as 
> the network time client.  If I "systemctl disable systemd-timesyncd"  it 
> never updates from the ntp server and weewx spins away with "engine: 
> Waiting for sane time. Current time is  ... "
>
> I have a local ntp server with a battery backed rtc. A raspberry pi with a 
> rtc that is running as my dns/dhcp server, and pi-hole.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7855a9aa-feb4-4b8a-816c-6891bbc27751%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[John]

The instructions for delaying weewx from starting on the Raspberry Pi until 
time is synced don't seem to be working with stretch and timesyncd as the 
network time client.  If I "systemctl disable systemd-timesyncd"  it never 
updates from the ntp server and weewx spins away with "engine: Waiting for 
sane time. Current time is  ... "

I have a local ntp server with a battery backed rtc. A raspberry pi with a 
rtc that is running as my dns/dhcp server, and pi-hole.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/de3eec47-88ad-4981-88ec-e22a910f4681%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[Andrew Milner]

I would recommend you doing the CORRECT solution and installing an RTC on 
your Pi zero.  Weewx relies HEAVILY on accurate time synchronisation 
between weather station and controlling PC - so ensuring your pi EITHER has 
an RTC onboard OR prevents weewx starting until time has been synchronised 
is ESSENTIAL for correct operation.

There are many many users of weewx with Davis stations, and many many of us 
with various models of RPi.  There are also many instances of logger 
corruptions and other anomolies.. so fudging the driver for one situation 
may open a can of worms in another situation - you have been warned!



On Tuesday, 28 May 2019 18:00:09 UTC+3, John wrote:
>
> so looking at the vantage driver it seems that if the weewx host 
> (raspberry pi zero without a RTC) has an incorrect time like after a 
> restart and syncs it's bad (early) time with the vantage console, then 
> records being added to the vantage console will have an earlier timestamp 
> than existing records. when weewx goes to read the records and finds a 
> "decreasing timestamp" it stops reading more records. manually clearing all 
> the records AND setting the correct time is a solution.
>
> I propose changing the vantage driver to avert setting the console time, 
> during a routine sync, earlier than the last record in the console. This 
> should prevent weewx from adjusting the console time until the weewx host 
> has had an opportunity to successfully acquire the time from an external 
> source (ntp server).   I suppose setting the console to a future time could 
> cause a problem, preventing weewx from correcting the console time without 
> first clearing the last (errant) record.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/32f79d61-7d81-4bc0-adab-6d1ad66de99c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[John]

so looking at the vantage driver it seems that if the weewx host (raspberry 
pi zero without a RTC) has an incorrect time like after a restart and syncs 
it's bad (early) time with the vantage console, then records being added to 
the vantage console will have an earlier timestamp than existing records. 
when weewx goes to read the records and finds a "decreasing timestamp" it 
stops reading more records. manually clearing all the records AND setting 
the correct time is a solution.

I propose changing the vantage driver to avert setting the console time, 
during a routine sync, earlier than the last record in the console. This 
should prevent weewx from adjusting the console time until the weewx host 
has had an opportunity to successfully acquire the time from an external 
source (ntp server).   I suppose setting the console to a future time could 
cause a problem, preventing weewx from correcting the console time without 
first clearing the last (errant) record.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/066a6494-cd10-465b-86a7-5452386adddb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[David Beach]

I spent a fair bit of time on what I believe is the same issue. I even 
installed an Adafruit RTC and that didn't seem to solve the issue. At the 
moment, I have the system on a UPS (which is huge and probably uses more 
power than my Console, Adapter/Logger module and the RPi Zero W). My UPS 
battery is dying so I will have to replace it soon if I plan to continue to 
use it.

I am not so much worried about losing data - though I can understand 
preserving the data is important for many people - but I just want the darn 
thing to start working again when the power comes back on. If I'm not 
around, it may go for many hours after the power has been restored, not 
working properly, until I clear the logger memory.

I'll be interested in seeing the comments!

David

On Saturday, 25 May 2019 13:13:16 UTC-4, John wrote:
>
> I have been experiencing similar problems recently with my Vantage Pro 2 
> console and RPI (Zero W) setup, typically after a prolonged (1+ hours) 
> power outage.  My only recovery method so far has been to clear the logger 
> which unfortunately leaves me without the storm data that initiated the 
> power outage.
>
> I have a theory, uninvestigated, that upon restart the logger is getting 
> corrupted with date-time changes as the RPI starts up with the incorrect 
> time and communicates with the logger, trying to sync time,  before 
> obtaining the correct time from a time server.  When I have extended power 
> outages, my internet provider is often offline as well so getting my lan 
> back to the correct time has been problematic. I think I have remedied this 
> by adding a battery backed RTC into my lan setup. One of my recovery 
> problems was rooted in DNS queries for time servers failing because of 
> gross time differences.   I briefly explored using the vantage console as a 
> battery backed time source.
>
> John
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e261da94-039a-4549-852f-6f7982eec27d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[John]

I have been experiencing similar problems recently with my Vantage Pro 2 
console and RPI (Zero W) setup, typically after a prolonged (1+ hours) 
power outage.  My only recovery method so far has been to clear the logger 
which unfortunately leaves me without the storm data that initiated the 
power outage.

I have a theory, uninvestigated, that upon restart the logger is getting 
corrupted with date-time changes as the RPI starts up with the incorrect 
time and communicates with the logger, trying to sync time,  before 
obtaining the correct time from a time server.  When I have extended power 
outages, my internet provider is often offline as well so getting my lan 
back to the correct time has been problematic. I think I have remedied this 
by adding a battery backed RTC into my lan setup. One of my recovery 
problems was rooted in DNS queries for time servers failing because of 
gross time differences.   I briefly explored using the vantage console as a 
battery backed time source.

John

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/cc605cd9-4141-43eb-9d18-0f61d04e6a47%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Davis Vantage Pro2 no data

[Thomas Keffer]

When you changed the logging interval to one minute, you also cleared the
memory in the logger. It's possible that your problem all along was corrupt
logger memory, but I would be surprised if that showed itself as an unknown
hardware type.

If it fails again, you probably have a bad logger. It's rare, but we've
seen a couple through the years.

-tk

On Mon, Mar 4, 2019 at 2:42 AM Asherah  wrote:

> I just had success with
>
> wee_device --set-interval=1
>
> as it cleans all the old data. Now weewx does get the new data. Might it
> be that my USB Logger has a defect? I will keep you posted.
>
> --
> 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] Davis Vantage Pro2 no data

[Asherah]

I just had success with

wee_device --set-interval=1

as it cleans all the old data. Now weewx does get the new data. Might it be 
that my USB Logger has a defect? I will keep you posted.

-- 
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] Davis Vantage Pro2 no data

[Asherah]

Unfortunately this did not help. I removed batteries, power and and the usb 
data logger overnight, restarted my Pi and still get

wee_device --info

Using configuration file /etc/weewx/weewx.conf

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

Unable to wake up console... sleeping

Unable to wake up console... retrying

Traceback (most recent call last):

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

main()

  File "/usr/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 1972, 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 1255, in 
hardware_name

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

weewx.UnsupportedFeature: Unknown hardware type 79


If I try it repeatedly I do get data

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

Querying...

Unable to wake up console... sleeping

Unable to wake up console... retrying

Davis Vantage EEPROM settings:



CONSOLE TYPE:   Vantage Pro2



CONSOLE FIRMWARE:

  Date: Jun  3 2013

  Version:  3.15



CONSOLE SETTINGS:

  Archive interval: 300 (seconds)

  Altitude: 27 (meter)

  Wind cup type:large

  Rain bucket type: 0.01 inches

  Rain year start:  1

  Onboard time: 2019-03-04 11:20:46

  

CONSOLE DISPLAY UNITS:

  Barometer:hPa

  Temperature:  degree_C

  Rain: mm

  Wind: km_per_hour

  

CONSOLE STATION INFO:

  Latitude (onboard):   +53.3°

  Longitude (onboard):  +10.3°

  Use manual or auto DST?   AUTO

  DST setting:  N/A

  Use GMT offset or zone code?  ZONE_CODE

  Time zone code:   20

  GMT offset:   N/A

  Temperature logging:  LAST

  Retransmit channel:   OFF (0)



TRANSMITTERS: 

  Channel   Receive   Repeater  Type

 1  active  none(N/A) 

 2  active  none(N/A) 

 3  inactivenone(N/A) 

 4  inactivenone(N/A) 

 5  inactivenone(N/A) 

 6  inactivenone(N/A) 

 7  inactivenoneiss 

 8  inactivenone(N/A) 


RECEPTION STATS:

  Total packets received:   802

  Total packets missed: 4

  Number of resynchronizations: 0

  Longest good stretch: 316

  Number of CRC errors: 1

  

BAROMETER CALIBRATION DATA:

  Current barometer reading:28.939 inHg

  Altitude: 89 feet

  Dew point:42 F

  Virtual temperature:  50 F

  Humidity correction factor:   1.8

  Correction ratio: 1.003

  Correction constant:  +0.000 inHg

  Gain: -1.000

  Offset:   -1.000

  

OFFSETS:

  Wind direction:   +0 deg

  Inside Temperature:   +0.0 F

  Inside Humidity:  +0 %

  Outside Temperature:  +0.0 F
  Outside Humidity: +0 %


But weewx still does not get any data. It stopped working shortly after 
updating to the latest version. 

-- 
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] Davis Vantage Pro2 no data

[Thomas Keffer]

Your logger is responding with an unknown hardware type. I doubt this has
anything to do with the upgrade.

Try power cycling:  unplug the power supply from your Vantage and take out
its batteries. While you are at it, reseat the logger. Then put everything
back together and try again.

-tk

On Sun, Mar 3, 2019 at 7:13 AM Asherah  wrote:

> Hi,
>
> after an update to the lastet version of weewx it does not get any data
> from my station anymore. With —info I get
>
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
> Unable to wake up console... sleeping
> Unable to wake up console... retrying
> Traceback (most recent call last):
>   File "/usr/bin/wee_device", line 66, in 
> main()
>   File "/usr/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 1972, 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 1255, in
> hardware_name
> raise weewx.UnsupportedFeature("Unknown hardware type %d" %
> self.hardware_type)
> weewx.UnsupportedFeature: Unknown hardware type 10
>
> As I am lost I am looking for help. 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.
>

-- 
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] Davis Vantage Pro2 no data

[Asherah]

Hi,

after an update to the lastet version of weewx it does not get any data from my 
station anymore. With —info I get

Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
Unable to wake up console... sleeping
Unable to wake up console... retrying
Traceback (most recent call last):
  File "/usr/bin/wee_device", line 66, in 
main()
  File "/usr/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 1972, 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 1255, in hardware_name
raise weewx.UnsupportedFeature("Unknown hardware type %d" % 
self.hardware_type)
weewx.UnsupportedFeature: Unknown hardware type 10

As I am lost I am looking for help. 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] Davis Vantage Pro2 on RPI, problem with console time adjustment

[Zeky91]

Hi.
lately i started to use RPI with Raspbian Stretch(last version) to send 
data from Davis console with data logger online.
Equipment is at my place at the moment, im testing it and it will go in 
remote location soon.
Everything is working nice, I have adjusted to send archives from Davis 
every 5 minutes, and ftp, wunderground, cwop...Everything working great, no 
errors.
I have just one problem. I simulated power outages(which will happen, 
location is solar powered) and when powering rpi wewx starts BEFORE ntp has 
finished checking and updating time! So soon after boot, weewx adjusts time 
on Davis to his time(which is wrong, its last time RPI was online). I have 
removed fake clock, and it seems that its still working? Because after 
boot, i always get this time when RPI was shut off. So, that leads to wrong 
archive time, and that could be a big problem because many power outages.
I was searching, and seems that weewx should wait for ntp to adjust time, 
and start after that, but that is not working correctly. 
I made a workaround by adjusting max_drift to big value, like 864000 so 
time will never update by itself(i can do it mannualy over team viewer with 
wee_device commands.
Is there any way to delay console time update, so rpi has few minutes of 
time to update ntp?
Or even, not to start weewx until ntp has finished updating(I checked weewx 
filein ini.d folder, ntp is listed as start requirment.
Is this some type of bug, and is there any way to prolong davis time 
synchronization, or to start weewx after time has been upgraded?

Regards

Željko from Croatia

-- 
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] Davis Vantage Pro2 USB

[Ryan McCammon]

Tom,

Thanks for the Belfyboy tip.  I went ahead and ordered one from him.

Regards,
Ryan

On Sat, May 6, 2017 at 7:34 PM, Ryan McCammon  wrote:
> Are there any 20-pin serial to USB connectors that are compatible with the
> Vantage Pro2 console?
>
> On May 6, 2017 7:25 PM, "Thomas Keffer"  wrote:
>>
>> Unfortunately, Davis bundles the software and logger together.
>>
>> There are some less-expensive, but unsupported, third party loggers out
>> there. In particular, the Belfryboy clone USB logger. You can either make
>> one yourself, or he will sell you a ready-to-go version
>>
>> -tk
>>
>> On Sat, May 6, 2017 at 6:00 PM, Ryan M.  wrote:
>>>
>>> Folks,
>>>
>>> I'd rather not pay for the entire product (not the Weather Link
>>> Software), just the USB connector.
>>> Does anybody know if there are companies that sell just the USB
>>> connector, and not the software.
>>> I am disappointed there's not a USB port on the ProVantage Console.  Btw,
>>> love, love, love WeeWx!!
>>>
>>> --
>>> 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/KpmKyqwoyAc/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] Davis Vantage Pro2 USB

[Ryan McCammon]

Are there any 20-pin serial to USB connectors that are compatible with the
Vantage Pro2 console?

On May 6, 2017 7:25 PM, "Thomas Keffer"  wrote:

> Unfortunately, Davis bundles the software and logger together.
>
> There are some less-expensive, but unsupported, third party loggers out
> there. In particular, the Belfryboy clone USB logger
> . You can either make one
> yourself, or he will sell you a ready-to-go version
>
> -tk
>
> On Sat, May 6, 2017 at 6:00 PM, Ryan M.  wrote:
>
>> Folks,
>>
>> I'd rather not pay for the entire product (not the Weather Link
>> Software), just the USB connector.
>> Does anybody know if there are companies that sell just the USB
>> connector, and not the software.
>> I am disappointed there's not a USB port on the ProVantage Console.  Btw,
>> love, love, love WeeWx!!
>>
>> --
>> 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/KpmKyqwoyAc/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] Davis Vantage Pro2 USB

[Thomas Keffer]

Unfortunately, Davis bundles the software and logger together.

There are some less-expensive, but unsupported, third party loggers out
there. In particular, the Belfryboy clone USB logger
. You can either make one
yourself, or he will sell you a ready-to-go version

-tk

On Sat, May 6, 2017 at 6:00 PM, Ryan M.  wrote:

> Folks,
>
> I'd rather not pay for the entire product (not the Weather Link Software),
> just the USB connector.
> Does anybody know if there are companies that sell just the USB connector,
> and not the software.
> I am disappointed there's not a USB port on the ProVantage Console.  Btw,
> love, love, love WeeWx!!
>
> --
> 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] Davis Vantage Pro2 USB

[Ryan M.]

Folks,

I'd rather not pay for the entire product (not the Weather Link Software), 
just the USB connector.
Does anybody know if there are companies that sell just the USB connector, 
and not the software.
I am disappointed there's not a USB port on the ProVantage Console.  Btw, 
love, love, love WeeWx!!

-- 
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] Davis vantage pro2 - Upgrading wind sensor - upgrading weewx?

[Thomas Keffer]

I wouldn't think so.

If you run weewx directly from the command line, it will print LOOP packets
(every 2 seconds), and REC records (every archive period). What do you see
for windSpeed and windGust in the REC printouts?

If the console is unable to support windGust when the wind sensor is
detached from the ISS, you could try switching to software record
generation (record_generation=software).

-tk

On Sat, Dec 3, 2016 at 7:04 AM, Jacek Skowroński  wrote:

> Hi guys,
> Today I had upgrade my ecosystem. I had added external sensor for wind. To
> be exact I dissatached wind sensor from ISS and attached it for external
> module. Set it up with ID=3.
> When I put wee_device I see
>  TRANSMITTERS:
>   Channel 1:iss
>   Channel 2:soil
>   Channel 3:wind
>   Channel 4:(N/A)
>   Channel 5:(N/A)
>   Channel 6:(N/A)
>   Channel 7:(N/A)
>   Channel 8:(N/A)
>
>
> Console shows wind ok, weewx site shows wind, but it seems like there is
> no gusts. I mean average wind is same as gusts.
> Do I have to configure something in weewx to tell the sw that I have
> external module for wind?
>
> Regards
> Jacek
>
> --
> 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] Davis vantage pro2 - Upgrading wind sensor - upgrading weewx?

[Jacek Skowroński]

Hi guys,
Today I had upgrade my ecosystem. I had added external sensor for wind. To 
be exact I dissatached wind sensor from ISS and attached it for external 
module. Set it up with ID=3.
When I put wee_device I see
 TRANSMITTERS:
  Channel 1:iss
  Channel 2:soil
  Channel 3:wind
  Channel 4:(N/A)
  Channel 5:(N/A)
  Channel 6:(N/A)
  Channel 7:(N/A)
  Channel 8:(N/A)


Console shows wind ok, weewx site shows wind, but it seems like there is no 
gusts. I mean average wind is same as gusts.
Do I have to configure something in weewx to tell the sw that I have 
external module for wind?

Regards
Jacek

-- 
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] Davis Vantage Pro2 and WU - best settings

[gjr80]

Hi,

I would say there are a lot of people with experience in using a Vantage with 
weewx, this link http://weewx.com/stations.html would tend to indicate at least 
271 :>)  I think you will find though that there are not many with your 
particular configuration. Time zones differences do not help either.

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] Davis Vantage Pro2 and WU - best settings

[Jacek Skowroński]

Eh
Davis console shows temp correctly
The manual was read few times
I see here is nobody with practice with davis and weewx

W dniu poniedziałek, 31 października 2016 Andrew Milner <
andrew.s.r.mil...@gmail.com> napisał(a):

> I do not know - I do not possess a Davis station - I just read the Davis
> manual and see there are three modes for the soil-leaf console.  You should
> read the whole Davis manual and make sure you are using it correctly and
> have it connected to the probe correctly!!
>
>
>
> On Monday, 31 October 2016 09:50:16 UTC+2, Jacek Skowroński wrote:
>
>> not yet.
>> Could I do this remotly via ssh to the raspberry pi? Or do I have to
>> manually click on the console?
>> The problem is I'm away from the place the Davis is located, I would be
>> there next Saturday.
>>
>> On Monday, October 31, 2016 at 8:06:03 AM UTC+1, Andrew Milner wrote:
>>>
>>> Have you tried configuring it as soil only and not leaf-soil since you
>>> say you do not have any leaf sensors?
>>>
>>> http://www.davisnet.com/product_documents/weather/manuals/
>>> VP2_Manual_Leaf_Soil_Temp_RevA.pdf
>>>
>>>
>>>
>>> On Monday, 31 October 2016 08:50:03 UTC+2, Jacek Skowroński wrote:
>>>
 I have soil_leaf module (ID=2), temp proble is the only one attached to
 the module and it is in slot 1.

 The console is configured to get data from ID=2 and module is set to
 the leaf_soil.


 That is all on the physical side.

 When I press temp button on the console I see temp with no1.

 Goig back to the issue, I'd like to have this value in the net so would
 be best to have it in the WU.
 Thanks for help

 regards
 Jacek

 W dniu 2016-10-31 o 07:43, Andrew Milner pisze:

 have you checked the soil temperature probe is in the correct slot?  It
 appears to be being read as a leaf temperature probe and not a soil
 temperature probe.

 On Monday, 31 October 2016 08:31:06 UTC+2, Jacek Skowroński wrote:
>
> Yes i have only sensor for temperature
> I have No humidity sensor now
> Can we somohow force wu to see this data?
>
> Nowhere i told i have other sensors
>
> W dniu poniedziałek, 31 października 2016 Thomas Keffer <
> tke...@gmail.com> napisał(a):
>
>> Hello, Jacek,
>>
>> You said you have soil temperature and humidity sensors, but it
>> appears that you actually have soil and *leaf temperature* sensors.
>> That is, you have values for soilTemp1 and leafTemp1, but nothing
>> for soilMoist1.
>>
>> Or, perhaps the sensors are plugged into the wrong probe slot? You
>> should check.
>>
>> The WeatherUnderground PWS protocol
>>  does
>> not recognize leaf temperature, so that would explainwhy you are not 
>> seeing
>> anything.
>>
>> -tk
>>
>> On Sun, Oct 30, 2016 at 9:36 AM, Jacek Skowroński 
>> wrote:
>>
>>> some logs
>>> REC:2016-10-30 17:30:00 CET (1477845000) altimeter:
>>> 30.2914897657, appTemp: 42.5550178172, barometer: 30.332, cloudbase:
>>> 2354.14897393, consBatteryVoltage: 1.68, dateTime: 1477845000, dewpoint:
>>> 38.9625445147, ET: 0.0, extraHumid1: None, extraHumid2: None, 
>>> extraTemp1:
>>> None, extraTemp2: None, extraTemp3: None, forecastRule: 1, heatindex: 
>>> 46.1,
>>> highOutTemp: 46.1, highRadiation: None, highUV: None, humidex: 46.1,
>>> inDewpoint: 54.6182787763, inHumidity: 49.0, inTemp: 75.1, interval: 5,
>>> leafTemp1: 45.0, leafTemp2: None, leafWet1: None, leafWet2: None,
>>> lowOutTemp: 46.0, maxSolarRad: None, outHumidity: 76.0, outTemp: 46.1,
>>> pressure: 29.5091101841, radiation: None, rain: 0.0, rainRate: 0.0,
>>> rxCheckPercent: 97.375, soilMoist1: None, soilMoist2: None, soilMoist3:
>>> None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, soilTemp3: 
>>> None,
>>> soilTemp4: None, txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 
>>> 46.1,
>>> windDir: 22.5, windGust: 4.0, windGustDir: 22.5, windrun: 54.58,
>>> windSpeed: 2.0
>>> LOOP:   2016-10-30 17:30:16 CET (1477845016) altimeter:
>>> 30.2924734796, appTemp: 42.4369596271, barometer: 30.333, cloudbase:
>>> 2353.42091128, consBatteryVoltage: 1.68, dateTime: 1477845016, dayET: 
>>> 0.0,
>>> dayRain: 0.0, dewpoint: 38.8657479904, extraAlarm1: 0, extraAlarm2: 0,
>>> extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0,
>>> extraAlarm7: 0, extraAlarm8: 0, extraHumid1: None, extraHumid2: None,
>>> extraHumid3: None, extraHumid4: None, extraHumid5: None, extraHumid6: 
>>> None,
>>> extraHumid7: None, extraTemp1: None, extraTemp2: None, extraTemp3: None,
>>> extraTemp4: None, extraTemp5: None, extraTemp6: None, extraTemp7: None,
>>> forecastIcon: 8, forecastRule: 1, heatindex: 46.0, humidex: 46.0,
>>> inDewpoint: 54.6182787

Re: [weewx-user] Davis Vantage Pro2 and WU - best settings

[Andrew Milner]

I do not know - I do not possess a Davis station - I just read the Davis 
manual and see there are three modes for the soil-leaf console.  You should 
read the whole Davis manual and make sure you are using it correctly and 
have it connected to the probe correctly!!



On Monday, 31 October 2016 09:50:16 UTC+2, Jacek Skowroński wrote:

> not yet.
> Could I do this remotly via ssh to the raspberry pi? Or do I have to 
> manually click on the console?
> The problem is I'm away from the place the Davis is located, I would be 
> there next Saturday.
>
> On Monday, October 31, 2016 at 8:06:03 AM UTC+1, Andrew Milner wrote:
>>
>> Have you tried configuring it as soil only and not leaf-soil since you 
>> say you do not have any leaf sensors?
>>
>>
>> http://www.davisnet.com/product_documents/weather/manuals/VP2_Manual_Leaf_Soil_Temp_RevA.pdf
>>
>>
>>
>> On Monday, 31 October 2016 08:50:03 UTC+2, Jacek Skowroński wrote:
>>
>>> I have soil_leaf module (ID=2), temp proble is the only one attached to 
>>> the module and it is in slot 1.
>>>
>>> The console is configured to get data from ID=2 and module is set to the 
>>> leaf_soil.
>>>
>>>
>>> That is all on the physical side.
>>>
>>> When I press temp button on the console I see temp with no1.
>>>
>>> Goig back to the issue, I'd like to have this value in the net so would 
>>> be best to have it in the WU.
>>> Thanks for help
>>>
>>> regards
>>> Jacek
>>>
>>> W dniu 2016-10-31 o 07:43, Andrew Milner pisze:
>>>
>>> have you checked the soil temperature probe is in the correct slot?  It 
>>> appears to be being read as a leaf temperature probe and not a soil 
>>> temperature probe.
>>>
>>> On Monday, 31 October 2016 08:31:06 UTC+2, Jacek Skowroński wrote: 

 Yes i have only sensor for temperature 
 I have No humidity sensor now
 Can we somohow force wu to see this data?

 Nowhere i told i have other sensors

 W dniu poniedziałek, 31 października 2016 Thomas Keffer <
 tke...@gmail.com> napisał(a):

> Hello, Jacek,
>
> You said you have soil temperature and humidity sensors, but it 
> appears that you actually have soil and *leaf temperature* sensors. 
> That is, you have values for soilTemp1 and leafTemp1, but nothing for 
> soilMoist1.
>
> Or, perhaps the sensors are plugged into the wrong probe slot? You 
> should check.
>
> The WeatherUnderground PWS protocol 
>  does 
> not recognize leaf temperature, so that would explainwhy you are not 
> seeing 
> anything.
>
> -tk
>
> On Sun, Oct 30, 2016 at 9:36 AM, Jacek Skowroński  
> wrote:
>
>> some logs 
>> REC:2016-10-30 17:30:00 CET (1477845000) altimeter: 
>> 30.2914897657, appTemp: 42.5550178172, barometer: 30.332, cloudbase: 
>> 2354.14897393, consBatteryVoltage: 1.68, dateTime: 1477845000, dewpoint: 
>> 38.9625445147, ET: 0.0, extraHumid1: None, extraHumid2: None, 
>> extraTemp1: 
>> None, extraTemp2: None, extraTemp3: None, forecastRule: 1, heatindex: 
>> 46.1, 
>> highOutTemp: 46.1, highRadiation: None, highUV: None, humidex: 46.1, 
>> inDewpoint: 54.6182787763, inHumidity: 49.0, inTemp: 75.1, interval: 5, 
>> leafTemp1: 45.0, leafTemp2: None, leafWet1: None, leafWet2: None, 
>> lowOutTemp: 46.0, maxSolarRad: None, outHumidity: 76.0, outTemp: 46.1, 
>> pressure: 29.5091101841, radiation: None, rain: 0.0, rainRate: 0.0, 
>> rxCheckPercent: 97.375, soilMoist1: None, soilMoist2: None, soilMoist3: 
>> None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, soilTemp3: 
>> None, 
>> soilTemp4: None, txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 
>> 46.1, 
>> windDir: 22.5, windGust: 4.0, windGustDir: 22.5, windrun: 54.58, 
>> windSpeed: 2.0
>> LOOP:   2016-10-30 17:30:16 CET (1477845016) altimeter: 
>> 30.2924734796, appTemp: 42.4369596271, barometer: 30.333, cloudbase: 
>> 2353.42091128, consBatteryVoltage: 1.68, dateTime: 1477845016, dayET: 
>> 0.0, 
>> dayRain: 0.0, dewpoint: 38.8657479904, extraAlarm1: 0, extraAlarm2: 0, 
>> extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, 
>> extraAlarm7: 0, extraAlarm8: 0, extraHumid1: None, extraHumid2: None, 
>> extraHumid3: None, extraHumid4: None, extraHumid5: None, extraHumid6: 
>> None, 
>> extraHumid7: None, extraTemp1: None, extraTemp2: None, extraTemp3: None, 
>> extraTemp4: None, extraTemp5: None, extraTemp6: None, extraTemp7: None, 
>> forecastIcon: 8, forecastRule: 1, heatindex: 46.0, humidex: 46.0, 
>> inDewpoint: 54.6182787763, inHumidity: 49.0, insideAlarm: 0, inTemp: 
>> 75.1, 
>> leafTemp1: 45.0, leafTemp2: None, leafTemp3: None, leafTemp4: None, 
>> leafWet1: None, leafWet2: None, leafWet3: None, leafWet4: 0.0, 
>> maxSolarRad: 
>> None, monthET: 0.0, monthRain: 2.960629922, outHumidity: 76.0, 

Re: [weewx-user] Davis Vantage Pro2 and WU - best settings

[Jacek Skowroński]

not yet.
Could I do this remotly via ssh to the raspberry pi? Or do I have to 
manually click on the console?
The problem is I'm away from the place the Davis is located, I would be 
there next Saturday.

On Monday, October 31, 2016 at 8:06:03 AM UTC+1, Andrew Milner wrote:
>
> Have you tried configuring it as soil only and not leaf-soil since you say 
> you do not have any leaf sensors?
>
>
> http://www.davisnet.com/product_documents/weather/manuals/VP2_Manual_Leaf_Soil_Temp_RevA.pdf
>
>
>
> On Monday, 31 October 2016 08:50:03 UTC+2, Jacek Skowroński wrote:
>
>> I have soil_leaf module (ID=2), temp proble is the only one attached to 
>> the module and it is in slot 1.
>>
>> The console is configured to get data from ID=2 and module is set to the 
>> leaf_soil.
>>
>>
>> That is all on the physical side.
>>
>> When I press temp button on the console I see temp with no1.
>>
>> Goig back to the issue, I'd like to have this value in the net so would 
>> be best to have it in the WU.
>> Thanks for help
>>
>> regards
>> Jacek
>>
>> W dniu 2016-10-31 o 07:43, Andrew Milner pisze:
>>
>> have you checked the soil temperature probe is in the correct slot?  It 
>> appears to be being read as a leaf temperature probe and not a soil 
>> temperature probe.
>>
>> On Monday, 31 October 2016 08:31:06 UTC+2, Jacek Skowroński wrote: 
>>>
>>> Yes i have only sensor for temperature 
>>> I have No humidity sensor now
>>> Can we somohow force wu to see this data?
>>>
>>> Nowhere i told i have other sensors
>>>
>>> W dniu poniedziałek, 31 października 2016 Thomas Keffer <
>>> tke...@gmail.com> napisał(a):
>>>
 Hello, Jacek,

 You said you have soil temperature and humidity sensors, but it appears 
 that you actually have soil and *leaf temperature* sensors. That is, 
 you have values for soilTemp1 and leafTemp1, but nothing for soilMoist1
 .

 Or, perhaps the sensors are plugged into the wrong probe slot? You 
 should check.

 The WeatherUnderground PWS protocol 
  does 
 not recognize leaf temperature, so that would explainwhy you are not 
 seeing 
 anything.

 -tk

 On Sun, Oct 30, 2016 at 9:36 AM, Jacek Skowroński  
 wrote:

> some logs 
> REC:2016-10-30 17:30:00 CET (1477845000) altimeter: 30.2914897657, 
> appTemp: 42.5550178172, barometer: 30.332, cloudbase: 2354.14897393, 
> consBatteryVoltage: 1.68, dateTime: 1477845000, dewpoint: 38.9625445147, 
> ET: 0.0, extraHumid1: None, extraHumid2: None, extraTemp1: None, 
> extraTemp2: None, extraTemp3: None, forecastRule: 1, heatindex: 46.1, 
> highOutTemp: 46.1, highRadiation: None, highUV: None, humidex: 46.1, 
> inDewpoint: 54.6182787763, inHumidity: 49.0, inTemp: 75.1, interval: 5, 
> leafTemp1: 45.0, leafTemp2: None, leafWet1: None, leafWet2: None, 
> lowOutTemp: 46.0, maxSolarRad: None, outHumidity: 76.0, outTemp: 46.1, 
> pressure: 29.5091101841, radiation: None, rain: 0.0, rainRate: 0.0, 
> rxCheckPercent: 97.375, soilMoist1: None, soilMoist2: None, soilMoist3: 
> None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, soilTemp3: 
> None, 
> soilTemp4: None, txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 
> 46.1, 
> windDir: 22.5, windGust: 4.0, windGustDir: 22.5, windrun: 54.58, 
> windSpeed: 2.0
> LOOP:   2016-10-30 17:30:16 CET (1477845016) altimeter: 30.2924734796, 
> appTemp: 42.4369596271, barometer: 30.333, cloudbase: 2353.42091128, 
> consBatteryVoltage: 1.68, dateTime: 1477845016, dayET: 0.0, dayRain: 0.0, 
> dewpoint: 38.8657479904, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
> extraAlarm8: 0, extraHumid1: None, extraHumid2: None, extraHumid3: None, 
> extraHumid4: None, extraHumid5: None, extraHumid6: None, extraHumid7: 
> None, 
> extraTemp1: None, extraTemp2: None, extraTemp3: None, extraTemp4: None, 
> extraTemp5: None, extraTemp6: None, extraTemp7: None, forecastIcon: 8, 
> forecastRule: 1, heatindex: 46.0, humidex: 46.0, inDewpoint: 
> 54.6182787763, 
> inHumidity: 49.0, insideAlarm: 0, inTemp: 75.1, leafTemp1: 45.0, 
> leafTemp2: 
> None, leafTemp3: None, leafTemp4: None, leafWet1: None, leafWet2: None, 
> leafWet3: None, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, 
> monthRain: 
> 2.960629922, outHumidity: 76.0, outsideAlarm1: 0, outsideAlarm2: 0, 
> outTemp: 46.0, pressure: 29.5100730398, radiation: None, rain: 0.0, 
> rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 
> soilLeafAlarm3: 0, soilLeafAlarm4: 0, soilMoist1: None, soilMoist2: None, 
> soilMoist3: None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, 
> soilTemp3: None, soilTemp4: None, stormRain: 0.0, stormStart: None, 
> sunrise: 1477802580, sunset: 1477837860, txBatt

Re: [weewx-user] Davis Vantage Pro2 and WU - best settings

[Andrew Milner]

Have you tried configuring it as soil only and not leaf-soil since you say 
you do not have any leaf sensors?

http://www.davisnet.com/product_documents/weather/manuals/VP2_Manual_Leaf_Soil_Temp_RevA.pdf



On Monday, 31 October 2016 08:50:03 UTC+2, Jacek Skowroński wrote:

> I have soil_leaf module (ID=2), temp proble is the only one attached to 
> the module and it is in slot 1.
>
> The console is configured to get data from ID=2 and module is set to the 
> leaf_soil.
>
>
> That is all on the physical side.
>
> When I press temp button on the console I see temp with no1.
>
> Goig back to the issue, I'd like to have this value in the net so would be 
> best to have it in the WU.
> Thanks for help
>
> regards
> Jacek
>
> W dniu 2016-10-31 o 07:43, Andrew Milner pisze:
>
> have you checked the soil temperature probe is in the correct slot?  It 
> appears to be being read as a leaf temperature probe and not a soil 
> temperature probe.
>
> On Monday, 31 October 2016 08:31:06 UTC+2, Jacek Skowroński wrote: 
>>
>> Yes i have only sensor for temperature 
>> I have No humidity sensor now
>> Can we somohow force wu to see this data?
>>
>> Nowhere i told i have other sensors
>>
>> W dniu poniedziałek, 31 października 2016 Thomas Keffer  
>> napisał(a):
>>
>>> Hello, Jacek,
>>>
>>> You said you have soil temperature and humidity sensors, but it appears 
>>> that you actually have soil and *leaf temperature* sensors. That is, 
>>> you have values for soilTemp1 and leafTemp1, but nothing for soilMoist1.
>>>
>>> Or, perhaps the sensors are plugged into the wrong probe slot? You 
>>> should check.
>>>
>>> The WeatherUnderground PWS protocol 
>>>  does not 
>>> recognize leaf temperature, so that would explainwhy you are not seeing 
>>> anything.
>>>
>>> -tk
>>>
>>> On Sun, Oct 30, 2016 at 9:36 AM, Jacek Skowroński  
>>> wrote:
>>>
 some logs 
 REC:2016-10-30 17:30:00 CET (1477845000) altimeter: 30.2914897657, 
 appTemp: 42.5550178172, barometer: 30.332, cloudbase: 2354.14897393, 
 consBatteryVoltage: 1.68, dateTime: 1477845000, dewpoint: 38.9625445147, 
 ET: 0.0, extraHumid1: None, extraHumid2: None, extraTemp1: None, 
 extraTemp2: None, extraTemp3: None, forecastRule: 1, heatindex: 46.1, 
 highOutTemp: 46.1, highRadiation: None, highUV: None, humidex: 46.1, 
 inDewpoint: 54.6182787763, inHumidity: 49.0, inTemp: 75.1, interval: 5, 
 leafTemp1: 45.0, leafTemp2: None, leafWet1: None, leafWet2: None, 
 lowOutTemp: 46.0, maxSolarRad: None, outHumidity: 76.0, outTemp: 46.1, 
 pressure: 29.5091101841, radiation: None, rain: 0.0, rainRate: 0.0, 
 rxCheckPercent: 97.375, soilMoist1: None, soilMoist2: None, soilMoist3: 
 None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, soilTemp3: None, 
 soilTemp4: None, txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 
 46.1, 
 windDir: 22.5, windGust: 4.0, windGustDir: 22.5, windrun: 54.58, 
 windSpeed: 2.0
 LOOP:   2016-10-30 17:30:16 CET (1477845016) altimeter: 30.2924734796, 
 appTemp: 42.4369596271, barometer: 30.333, cloudbase: 2353.42091128, 
 consBatteryVoltage: 1.68, dateTime: 1477845016, dayET: 0.0, dayRain: 0.0, 
 dewpoint: 38.8657479904, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
 extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
 extraAlarm8: 0, extraHumid1: None, extraHumid2: None, extraHumid3: None, 
 extraHumid4: None, extraHumid5: None, extraHumid6: None, extraHumid7: 
 None, 
 extraTemp1: None, extraTemp2: None, extraTemp3: None, extraTemp4: None, 
 extraTemp5: None, extraTemp6: None, extraTemp7: None, forecastIcon: 8, 
 forecastRule: 1, heatindex: 46.0, humidex: 46.0, inDewpoint: 
 54.6182787763, 
 inHumidity: 49.0, insideAlarm: 0, inTemp: 75.1, leafTemp1: 45.0, 
 leafTemp2: 
 None, leafTemp3: None, leafTemp4: None, leafWet1: None, leafWet2: None, 
 leafWet3: None, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 
 2.960629922, outHumidity: 76.0, outsideAlarm1: 0, outsideAlarm2: 0, 
 outTemp: 46.0, pressure: 29.5100730398, radiation: None, rain: 0.0, 
 rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 
 soilLeafAlarm3: 0, soilLeafAlarm4: 0, soilMoist1: None, soilMoist2: None, 
 soilMoist3: None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, 
 soilTemp3: None, soilTemp4: None, stormRain: 0.0, stormStart: None, 
 sunrise: 1477802580, sunset: 1477837860, txBatteryStatus: 0, usUnits: 1, 
 UV: None, windchill: 46.0, windDir: 32.0, windGust: 2.0, windGustDir: 
 32.0, 
 windSpeed: 2.0, windSpeed10: 2.0, yearET: 0.0, yearRain: 12.3

 so both loop and rec have soilTemp1 value of 45.0.

 and here other log
 pi@raspberrypi:~ $ tail -f /var/log/syslog
 Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Starting up weewx 
 version 3.5.0
 Oct 

Re: [weewx-user] Davis Vantage Pro2 and WU - best settings

[Jacek Skowroński]

I have soil_leaf module (ID=2), temp proble is the only one attached to 
the module and it is in slot 1.


The console is configured to get data from ID=2 and module is set to the 
leaf_soil.



That is all on the physical side.

When I press temp button on the console I see temp with no1.

Goig back to the issue, I'd like to have this value in the net so would 
be best to have it in the WU.

Thanks for help

regards
Jacek


W dniu 2016-10-31 o 07:43, Andrew Milner pisze:
have you checked the soil temperature probe is in the correct slot?  
It appears to be being read as a leaf temperature probe and not a soil 
temperature probe.


On Monday, 31 October 2016 08:31:06 UTC+2, Jacek Skowroński wrote:

Yes i have only sensor for temperature
I have No humidity sensor now
Can we somohow force wu to see this data?

Nowhere i told i have other sensors

W dniu poniedziałek, 31 października 2016 Thomas Keffer
> napisał(a):

Hello, Jacek,

You said you have soil temperature and humidity sensors, but
it appears that you actually have soil and /leaf temperature/
sensors. That is, you have values for soilTemp1and leafTemp1,
but nothing for soilMoist1.

Or, perhaps the sensors are plugged into the wrong probe slot?
You should check.

The WeatherUnderground PWS protocol

does not recognize leaf temperature, so that would explainwhy
you are not seeing anything.

-tk

On Sun, Oct 30, 2016 at 9:36 AM, Jacek Skowroński
 wrote:

some logs
REC:2016-10-30 17:30:00 CET (1477845000) altimeter:
30.2914897657, appTemp: 42.5550178172, barometer: 30.332,
cloudbase: 2354.14897393, consBatteryVoltage: 1.68,
dateTime: 1477845000, dewpoint: 38.9625445147, ET: 0.0,
extraHumid1: None, extraHumid2: None, extraTemp1: None,
extraTemp2: None, extraTemp3: None, forecastRule: 1,
heatindex: 46.1, highOutTemp: 46.1, highRadiation: None,
highUV: None, humidex: 46.1, inDewpoint: 54.6182787763,
inHumidity: 49.0, inTemp: 75.1, interval: 5, leafTemp1:
45.0, leafTemp2: None, leafWet1: None, leafWet2: None,
lowOutTemp: 46.0, maxSolarRad: None, outHumidity: 76.0,
outTemp: 46.1, pressure: 29.5091101841, radiation: None,
rain: 0.0, rainRate: 0.0, rxCheckPercent: 97.375,
soilMoist1: None, soilMoist2: None, soilMoist3: None,
soilMoist4: None, soilTemp1: 45.0, soilTemp2: None,
soilTemp3: None, soilTemp4: None, txBatteryStatus: 0,
usUnits: 1, UV: None, windchill: 46.1, windDir: 22.5,
windGust: 4.0, windGustDir: 22.5, windrun: 54.58,
windSpeed: 2.0
LOOP:   2016-10-30 17:30:16 CET (1477845016) altimeter:
30.2924734796, appTemp: 42.4369596271, barometer: 30.333,
cloudbase: 2353.42091128, consBatteryVoltage: 1.68,
dateTime: 1477845016, dayET: 0.0, dayRain: 0.0, dewpoint:
38.8657479904, extraAlarm1: 0, extraAlarm2: 0,
extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0,
extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0,
extraHumid1: None, extraHumid2: None, extraHumid3: None,
extraHumid4: None, extraHumid5: None, extraHumid6: None,
extraHumid7: None, extraTemp1: None, extraTemp2: None,
extraTemp3: None, extraTemp4: None, extraTemp5: None,
extraTemp6: None, extraTemp7: None, forecastIcon: 8,
forecastRule: 1, heatindex: 46.0, humidex: 46.0,
inDewpoint: 54.6182787763, inHumidity: 49.0, insideAlarm:
0, inTemp: 75.1, leafTemp1: 45.0, leafTemp2: None,
leafTemp3: None, leafTemp4: None, leafWet1: None,
leafWet2: None, leafWet3: None, leafWet4: 0.0,
maxSolarRad: None, monthET: 0.0, monthRain: 2.960629922,
outHumidity: 76.0, outsideAlarm1: 0, outsideAlarm2: 0,
outTemp: 46.0, pressure: 29.5100730398, radiation: None,
rain: 0.0, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0,
soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0,
soilMoist1: None, soilMoist2: None, soilMoist3: None,
soilMoist4: None, soilTemp1: 45.0, soilTemp2: None,
soilTemp3: None, soilTemp4: None, stormRain: 0.0,
stormStart: None, sunrise: 1477802580, sunset: 1477837860,
txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 46.0,
windDir: 32.0, windGust: 2.0, windGustDir: 32.0,
windSpeed: 2.0, windSpeed10: 2.0, yearET: 0.0, yearRain:
12.3

so both loop and rec have soilTemp1 value of 45.0.

and here other log
pi@raspberrypi:~ $ tail -f /var/log/syslog
Oct 30 17:31:33

Re: [weewx-user] Davis Vantage Pro2 and WU - best settings

[Andrew Milner]

have you checked the soil temperature probe is in the correct slot?  It 
appears to be being read as a leaf temperature probe and not a soil 
temperature probe.

On Monday, 31 October 2016 08:31:06 UTC+2, Jacek Skowroński wrote:
>
> Yes i have only sensor for temperature
> I have No humidity sensor now
> Can we somohow force wu to see this data?
>
> Nowhere i told i have other sensors
>
> W dniu poniedziałek, 31 października 2016 Thomas Keffer  > napisał(a):
>
>> Hello, Jacek,
>>
>> You said you have soil temperature and humidity sensors, but it appears 
>> that you actually have soil and *leaf temperature* sensors. That is, you 
>> have values for soilTemp1 and leafTemp1, but nothing for soilMoist1.
>>
>> Or, perhaps the sensors are plugged into the wrong probe slot? You should 
>> check.
>>
>> The WeatherUnderground PWS protocol 
>>  does not 
>> recognize leaf temperature, so that would explainwhy you are not seeing 
>> anything.
>>
>> -tk
>>
>> On Sun, Oct 30, 2016 at 9:36 AM, Jacek Skowroński  
>> wrote:
>>
>>> some logs
>>> REC:2016-10-30 17:30:00 CET (1477845000) altimeter: 30.2914897657, 
>>> appTemp: 42.5550178172, barometer: 30.332, cloudbase: 2354.14897393, 
>>> consBatteryVoltage: 1.68, dateTime: 1477845000, dewpoint: 38.9625445147, 
>>> ET: 0.0, extraHumid1: None, extraHumid2: None, extraTemp1: None, 
>>> extraTemp2: None, extraTemp3: None, forecastRule: 1, heatindex: 46.1, 
>>> highOutTemp: 46.1, highRadiation: None, highUV: None, humidex: 46.1, 
>>> inDewpoint: 54.6182787763, inHumidity: 49.0, inTemp: 75.1, interval: 5, 
>>> leafTemp1: 45.0, leafTemp2: None, leafWet1: None, leafWet2: None, 
>>> lowOutTemp: 46.0, maxSolarRad: None, outHumidity: 76.0, outTemp: 46.1, 
>>> pressure: 29.5091101841, radiation: None, rain: 0.0, rainRate: 0.0, 
>>> rxCheckPercent: 97.375, soilMoist1: None, soilMoist2: None, soilMoist3: 
>>> None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, soilTemp3: None, 
>>> soilTemp4: None, txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 46.1, 
>>> windDir: 22.5, windGust: 4.0, windGustDir: 22.5, windrun: 54.58, 
>>> windSpeed: 2.0
>>> LOOP:   2016-10-30 17:30:16 CET (1477845016) altimeter: 30.2924734796, 
>>> appTemp: 42.4369596271, barometer: 30.333, cloudbase: 2353.42091128, 
>>> consBatteryVoltage: 1.68, dateTime: 1477845016, dayET: 0.0, dayRain: 0.0, 
>>> dewpoint: 38.8657479904, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, 
>>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, 
>>> extraAlarm8: 0, extraHumid1: None, extraHumid2: None, extraHumid3: None, 
>>> extraHumid4: None, extraHumid5: None, extraHumid6: None, extraHumid7: None, 
>>> extraTemp1: None, extraTemp2: None, extraTemp3: None, extraTemp4: None, 
>>> extraTemp5: None, extraTemp6: None, extraTemp7: None, forecastIcon: 8, 
>>> forecastRule: 1, heatindex: 46.0, humidex: 46.0, inDewpoint: 54.6182787763, 
>>> inHumidity: 49.0, insideAlarm: 0, inTemp: 75.1, leafTemp1: 45.0, leafTemp2: 
>>> None, leafTemp3: None, leafTemp4: None, leafWet1: None, leafWet2: None, 
>>> leafWet3: None, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 
>>> 2.960629922, outHumidity: 76.0, outsideAlarm1: 0, outsideAlarm2: 0, 
>>> outTemp: 46.0, pressure: 29.5100730398, radiation: None, rain: 0.0, 
>>> rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, 
>>> soilLeafAlarm3: 0, soilLeafAlarm4: 0, soilMoist1: None, soilMoist2: None, 
>>> soilMoist3: None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, 
>>> soilTemp3: None, soilTemp4: None, stormRain: 0.0, stormStart: None, 
>>> sunrise: 1477802580, sunset: 1477837860, txBatteryStatus: 0, usUnits: 1, 
>>> UV: None, windchill: 46.0, windDir: 32.0, windGust: 2.0, windGustDir: 32.0, 
>>> windSpeed: 2.0, windSpeed10: 2.0, yearET: 0.0, yearRain: 12.3
>>>
>>> so both loop and rec have soilTemp1 value of 45.0.
>>>
>>> and here other log
>>> pi@raspberrypi:~ $ tail -f /var/log/syslog
>>> Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Starting up weewx 
>>> version 3.5.0
>>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of 
>>> console successful
>>> Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Clock error is 2.61 
>>> seconds (positive is fast)
>>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Getting archive 
>>> packets since 2016-10-30 17:30:00 CET (1477845000)
>>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of 
>>> console successful
>>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Retrieving 0 page(s); 
>>> starting index= 0
>>> Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Starting main packet 
>>> loop.
>>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of 
>>> console successful
>>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Requesting 200 LOOP 
>>> packets.
>>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of 
>>> console successful
>>> Oct 30 

Re: [weewx-user] Davis Vantage Pro2 and WU - best settings

[Jacek Skowroński]

Yes i have only sensor for temperature
I have No humidity sensor now
Can we somohow force wu to see this data?

Nowhere i told i have other sensors

W dniu poniedziałek, 31 października 2016 Thomas Keffer 
napisał(a):

> Hello, Jacek,
>
> You said you have soil temperature and humidity sensors, but it appears
> that you actually have soil and *leaf temperature* sensors. That is, you
> have values for soilTemp1 and leafTemp1, but nothing for soilMoist1.
>
> Or, perhaps the sensors are plugged into the wrong probe slot? You should
> check.
>
> The WeatherUnderground PWS protocol
>  does not
> recognize leaf temperature, so that would explainwhy you are not seeing
> anything.
>
> -tk
>
> On Sun, Oct 30, 2016 at 9:36 AM, Jacek Skowroński  > wrote:
>
>> some logs
>> REC:2016-10-30 17:30:00 CET (1477845000) altimeter: 30.2914897657,
>> appTemp: 42.5550178172, barometer: 30.332, cloudbase: 2354.14897393,
>> consBatteryVoltage: 1.68, dateTime: 1477845000, dewpoint: 38.9625445147,
>> ET: 0.0, extraHumid1: None, extraHumid2: None, extraTemp1: None,
>> extraTemp2: None, extraTemp3: None, forecastRule: 1, heatindex: 46.1,
>> highOutTemp: 46.1, highRadiation: None, highUV: None, humidex: 46.1,
>> inDewpoint: 54.6182787763, inHumidity: 49.0, inTemp: 75.1, interval: 5,
>> leafTemp1: 45.0, leafTemp2: None, leafWet1: None, leafWet2: None,
>> lowOutTemp: 46.0, maxSolarRad: None, outHumidity: 76.0, outTemp: 46.1,
>> pressure: 29.5091101841, radiation: None, rain: 0.0, rainRate: 0.0,
>> rxCheckPercent: 97.375, soilMoist1: None, soilMoist2: None, soilMoist3:
>> None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None, soilTemp3: None,
>> soilTemp4: None, txBatteryStatus: 0, usUnits: 1, UV: None, windchill: 46.1,
>> windDir: 22.5, windGust: 4.0, windGustDir: 22.5, windrun: 54.58,
>> windSpeed: 2.0
>> LOOP:   2016-10-30 17:30:16 CET (1477845016) altimeter: 30.2924734796,
>> appTemp: 42.4369596271, barometer: 30.333, cloudbase: 2353.42091128,
>> consBatteryVoltage: 1.68, dateTime: 1477845016, dayET: 0.0, dayRain: 0.0,
>> dewpoint: 38.8657479904, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0,
>> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0,
>> extraAlarm8: 0, extraHumid1: None, extraHumid2: None, extraHumid3: None,
>> extraHumid4: None, extraHumid5: None, extraHumid6: None, extraHumid7: None,
>> extraTemp1: None, extraTemp2: None, extraTemp3: None, extraTemp4: None,
>> extraTemp5: None, extraTemp6: None, extraTemp7: None, forecastIcon: 8,
>> forecastRule: 1, heatindex: 46.0, humidex: 46.0, inDewpoint: 54.6182787763,
>> inHumidity: 49.0, insideAlarm: 0, inTemp: 75.1, leafTemp1: 45.0, leafTemp2:
>> None, leafTemp3: None, leafTemp4: None, leafWet1: None, leafWet2: None,
>> leafWet3: None, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain:
>> 2.960629922, outHumidity: 76.0, outsideAlarm1: 0, outsideAlarm2: 0,
>> outTemp: 46.0, pressure: 29.5100730398, radiation: None, rain: 0.0,
>> rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0,
>> soilLeafAlarm3: 0, soilLeafAlarm4: 0, soilMoist1: None, soilMoist2: None,
>> soilMoist3: None, soilMoist4: None, soilTemp1: 45.0, soilTemp2: None,
>> soilTemp3: None, soilTemp4: None, stormRain: 0.0, stormStart: None,
>> sunrise: 1477802580, sunset: 1477837860, txBatteryStatus: 0, usUnits: 1,
>> UV: None, windchill: 46.0, windDir: 32.0, windGust: 2.0, windGustDir: 32.0,
>> windSpeed: 2.0, windSpeed10: 2.0, yearET: 0.0, yearRain: 12.3
>>
>> so both loop and rec have soilTemp1 value of 45.0.
>>
>> and here other log
>> pi@raspberrypi:~ $ tail -f /var/log/syslog
>> Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Starting up weewx
>> version 3.5.0
>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of
>> console successful
>> Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Clock error is 2.61
>> seconds (positive is fast)
>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Getting archive
>> packets since 2016-10-30 17:30:00 CET (1477845000)
>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of
>> console successful
>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Retrieving 0 page(s);
>> starting index= 0
>> Oct 30 17:31:33 raspberrypi weewx[10216]: engine: Starting main packet
>> loop.
>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of
>> console successful
>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: Requesting 200 LOOP
>> packets.
>> Oct 30 17:31:33 raspberrypi weewx[10216]: vantage: gentle wake up of
>> console successful
>> Oct 30 17:35:15 raspberrypi weewx[10216]: vantage: Getting archive
>> packets since 2016-10-30 17:30:00 CET (1477845000)
>> Oct 30 17:35:15 raspberrypi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Sun Oct 30 17:36:45 2016 [try http://www.rsyslog.com/e/2007
>> ]
>> Oct 30 17:35:15 raspberrypi weewx[10216]: vantage: gentle wake up of
>> console successful
>> Oct 30 17:35

Re: [weewx-user] Davis Vantage Pro2 and WU - best settings

[Thomas Keffer]

On Sat, Oct 29, 2016 at 12:49 PM, Jacek Skowroński 
wrote:

> Hi,
> I have Davis Vatange pro2 with external leaf_soil module located on ID=2.
> So according to help I did such an command
>
> wee_device --set-transmitter-type=2,8,1,1
>
>
> So if I understood it correctly I would have temperature and humidity of
> soil on the external temp1 and external hum1.
>


The temperature would show up as soilTemp1, and the humidity as soilMoist1.
You can check this by running weewx directly
. Make sure that the
values soilTemp1 and soilMoist1 look reasonable for both the LOOP and REC
values.

​


> How to get those data to WU?
>
> Just now on my station we do not see temp and humidity of the soil.
> https://www.wunderground.com/personal-weather-station/
> dashboard?ID=IWOJEWDZ56
>


If you have values for soilTemp1 and soilMoist1, weewx should be sending
them to the WU. But, let's first make sure you have values.


> Next topic is best timings for sending data, is it possible to get data in
> RealTime?
> In general Davis has archival for 5min (300sec) so it sends data every
> 5minute.
> I had tried rapid fire, but it sends data every 2.5 sec but data changes
> every 5minute so it's a little bit crazy.
>

​Both soilTemp1 and soilMoist1 are included in Davis LOOP packets, so they
should be realtime. However, I don't know that the WU will display realtime
soil temperature and moisture.
​

​-tk​

-- 
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] Davis Vantage Pro2 and WU - best settings

[Jacek Skowroński]

Hi,
I have Davis Vatange pro2 with external leaf_soil module located on ID=2.
So according to help I did such an command

wee_device --set-transmitter-type=2,8,1,1


So if I understood it correctly I would have temperature and humidity of 
soil on the external temp1 and external hum1.
How to get those data to WU?

Just now on my station we do not see temp and humidity of the soil.
https://www.wunderground.com/personal-weather-station/dashboard?ID=IWOJEWDZ56

Next topic is best timings for sending data, is it possible to get data in 
RealTime?
In general Davis has archival for 5min (300sec) so it sends data every 
5minute.
I had tried rapid fire, but it sends data every 2.5 sec but data changes 
every 5minute so it's a little bit crazy.

Is there anybody using Davis Vantage pro2 and WU and could share your 
config?

Thanks in advance
BR
Jacek 

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