Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Thank you  for that suggestion, I will expeditiously follow up!
On Saturday, 13 March 2021 at 14:05:03 UTC+13 gjr80 wrote:

> So you are back using the original Envoy that was 'tripping the fuse'? 
> Regards the two beeps from the Envoy I understand the first indicates 
> successful startup of the processor and the second verifies the 
> installation of the logger so it seems your single beep does point to an 
> issue with the logger.  Given you have things working again it might be 
> worthwhile contacting Davis in slower time and finding out if you do have 
> an incompatible Envoy/logger or if there is some other issue with one or 
> the other. If your original Envoy just started working again it could just 
> as easily stop as well; having a backup would be handy.
>
> Gary
> On Saturday, 13 March 2021 at 10:38:16 UTC+10 monmul wrote:
>
>> A big THANK YOU to all who helped me out on this, I really appreciate the 
>> help and guidancesorry it turned into a wild goose chase!
>>
>> On Friday, 12 March 2021 at 16:24:28 UTC+13 monmul wrote:
>>
>>> Yep fully functional againupdating on the website...WTF!.are 
>>> these things sent to us to just test our patience!!
>>>
>>> On Friday, 12 March 2021 at 13:30:30 UTC+13 monmul wrote:
>>>
 Hmmm! even more curiouserI notice from my webpage that data was 
 collected and posted yesterdayafter having nothing updated for almost 
 2 
 weeks!

 On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote:

> So, if it is the RPi then it is either a sofward corruption on the 
> card caused by the repeated rebooting after the fuse tripsor else 
> some 
> hardward failure on the board was the cause of the tripping. Its strange 
> that since reassembling the Envoy, RPi etc there has not been a fuse trip.
>
> One other thought occurs to me...I have a powered USB Hub attached to 
> the RPi(its a 3B)maybe I should disconnect the hub and try the Envoy 
> directly into the RPi..if minicom works that would point to the Hub 
> as 
> being the culpit!!??
>
> On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote:
>
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ wee_device --clear-memory
>> Using configuration file /etc/weewx/weewx.conf
>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>> Proceeding will erase all archive records.
>> Are you sure you wish to proceed (y/n)? y
>> Erasing all archive records ...
>> Archive records erased.
>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 12:49:30
>>
>> Press CTRL-A Z for help on special keys
>> .
>> .
>> .
>>
>>
>> Again no return of TEST or NVER
>>
>> On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote:
>>
>>> So, having put the old Envoy back on the Rpi (having shown it worked 
>>> on the PC) this is what I getlooks like some kind of continuous 
>>> Loop 
>>> situation.
>>>
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>>>
>>>
>>>
>>> Welcome to minicom 2.7
>>>
>>> OPTIONS: I18n 
>>> Compiled on Apr 22 2017, 09:14:19.
>>> Port /dev/ttyUSB0, 12:42:51
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ b 2
>>> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ   b 2
>>> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2
>>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> Á LOO1 =vŠ 4I ÀÿÿÿPÿÿ

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

So you are back using the original Envoy that was 'tripping the fuse'? 
Regards the two beeps from the Envoy I understand the first indicates 
successful startup of the processor and the second verifies the 
installation of the logger so it seems your single beep does point to an 
issue with the logger.  Given you have things working again it might be 
worthwhile contacting Davis in slower time and finding out if you do have 
an incompatible Envoy/logger or if there is some other issue with one or 
the other. If your original Envoy just started working again it could just 
as easily stop as well; having a backup would be handy.

Gary
On Saturday, 13 March 2021 at 10:38:16 UTC+10 monmul wrote:

> A big THANK YOU to all who helped me out on this, I really appreciate the 
> help and guidancesorry it turned into a wild goose chase!
>
> On Friday, 12 March 2021 at 16:24:28 UTC+13 monmul wrote:
>
>> Yep fully functional againupdating on the website...WTF!.are 
>> these things sent to us to just test our patience!!
>>
>> On Friday, 12 March 2021 at 13:30:30 UTC+13 monmul wrote:
>>
>>> Hmmm! even more curiouserI notice from my webpage that data was 
>>> collected and posted yesterdayafter having nothing updated for almost 2 
>>> weeks!
>>>
>>> On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote:
>>>
 So, if it is the RPi then it is either a sofward corruption on the card 
 caused by the repeated rebooting after the fuse tripsor else some 
 hardward failure on the board was the cause of the tripping. Its strange 
 that since reassembling the Envoy, RPi etc there has not been a fuse trip.

 One other thought occurs to me...I have a powered USB Hub attached to 
 the RPi(its a 3B)maybe I should disconnect the hub and try the Envoy 
 directly into the RPi..if minicom works that would point to the Hub as 
 being the culpit!!??

 On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote:

> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ wee_device --clear-memory
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
> Proceeding will erase all archive records.
> Are you sure you wish to proceed (y/n)? y
> Erasing all archive records ...
> Archive records erased.
> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n 
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 12:49:30
>
> Press CTRL-A Z for help on special keys
> .
> .
> .
>
>
> Again no return of TEST or NVER
>
> On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote:
>
>> So, having put the old Envoy back on the Rpi (having shown it worked 
>> on the PC) this is what I getlooks like some kind of continuous Loop 
>> situation.
>>
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 12:42:51
>>
>> Press CTRL-A Z for help on special keys
>>
>> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ b 2
>> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ   b 2
>> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2
>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> /‚LOO1 =vŠ 4I Àÿÿÿ

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

A big THANK YOU to all who helped me out on this, I really appreciate the 
help and guidancesorry it turned into a wild goose chase!

On Friday, 12 March 2021 at 16:24:28 UTC+13 monmul wrote:

> Yep fully functional againupdating on the website...WTF!.are these 
> things sent to us to just test our patience!!
>
> On Friday, 12 March 2021 at 13:30:30 UTC+13 monmul wrote:
>
>> Hmmm! even more curiouserI notice from my webpage that data was 
>> collected and posted yesterdayafter having nothing updated for almost 2 
>> weeks!
>>
>> On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote:
>>
>>> So, if it is the RPi then it is either a sofward corruption on the card 
>>> caused by the repeated rebooting after the fuse tripsor else some 
>>> hardward failure on the board was the cause of the tripping. Its strange 
>>> that since reassembling the Envoy, RPi etc there has not been a fuse trip.
>>>
>>> One other thought occurs to me...I have a powered USB Hub attached to 
>>> the RPi(its a 3B)maybe I should disconnect the hub and try the Envoy 
>>> directly into the RPi..if minicom works that would point to the Hub as 
>>> being the culpit!!??
>>>
>>> On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote:
>>>
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ wee_device --clear-memory
 Using configuration file /etc/weewx/weewx.conf
 Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
 Proceeding will erase all archive records.
 Are you sure you wish to proceed (y/n)? y
 Erasing all archive records ...
 Archive records erased.
 pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0


 Welcome to minicom 2.7

 OPTIONS: I18n 
 Compiled on Apr 22 2017, 09:14:19.
 Port /dev/ttyUSB0, 12:49:30

 Press CTRL-A Z for help on special keys
 .
 .
 .


 Again no return of TEST or NVER

 On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote:

> So, having put the old Envoy back on the Rpi (having shown it worked 
> on the PC) this is what I getlooks like some kind of continuous Loop 
> situation.
>
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n 
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 12:42:51
>
> Press CTRL-A Z for help on special keys
>
> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ b 2
> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ   b 2
> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
>
> ¤LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2
> âYLOO1 =vŠ 4I ÁÿÿÿPÿ 5⊑? ÿÿÿ½   b 2
> ¾LOO1 =vŠ 4I Áÿÿÿ
>
> On Friday, 12 March 2021 at 12:40:56 UTC+13 monmul wrote:
>
>> But from the tests on my PC, it seems the old Envoy is 
>> workingdoes it not.(so we do not have to worry about the new Envoy 
>> for 
>> now!)...so it would appear as if the RPi is the culpithave I 
>> deducted 
>> correctly?
>>
>> On Friday, 12 March 2021 at 02:29:03 U

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Yep fully functional againupdating on the website...WTF!.are these 
things sent to us to just test our patience!!

On Friday, 12 March 2021 at 13:30:30 UTC+13 monmul wrote:

> Hmmm! even more curiouserI notice from my webpage that data was 
> collected and posted yesterdayafter having nothing updated for almost 2 
> weeks!
>
> On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote:
>
>> So, if it is the RPi then it is either a sofward corruption on the card 
>> caused by the repeated rebooting after the fuse tripsor else some 
>> hardward failure on the board was the cause of the tripping. Its strange 
>> that since reassembling the Envoy, RPi etc there has not been a fuse trip.
>>
>> One other thought occurs to me...I have a powered USB Hub attached to the 
>> RPi(its a 3B)maybe I should disconnect the hub and try the Envoy 
>> directly into the RPi..if minicom works that would point to the Hub as 
>> being the culpit!!??
>>
>> On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote:
>>
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ wee_device --clear-memory
>>> Using configuration file /etc/weewx/weewx.conf
>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>>> Proceeding will erase all archive records.
>>> Are you sure you wish to proceed (y/n)? y
>>> Erasing all archive records ...
>>> Archive records erased.
>>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>>>
>>>
>>> Welcome to minicom 2.7
>>>
>>> OPTIONS: I18n 
>>> Compiled on Apr 22 2017, 09:14:19.
>>> Port /dev/ttyUSB0, 12:49:30
>>>
>>> Press CTRL-A Z for help on special keys
>>> .
>>> .
>>> .
>>>
>>>
>>> Again no return of TEST or NVER
>>>
>>> On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote:
>>>
 So, having put the old Envoy back on the Rpi (having shown it worked on 
 the PC) this is what I getlooks like some kind of continuous Loop 
 situation.

 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0



 Welcome to minicom 2.7

 OPTIONS: I18n 
 Compiled on Apr 22 2017, 09:14:19.
 Port /dev/ttyUSB0, 12:42:51

 Press CTRL-A Z for help on special keys

 LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ b 2
 v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ   b 2
 ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2
 /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
 /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
 ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
 ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
 «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
 «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
 ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
 ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
 /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
 ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
 ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
 /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
  
 ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
  
 Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
  
 Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
  
 Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
  
 ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
  
 /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
  
 /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
  
 /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
  

 ¤LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2
 âYLOO1 =vŠ 4I ÁÿÿÿPÿ 5⊑? ÿÿÿ½   b 2
 ¾LOO1 =vŠ 4I Áÿÿÿ

 On Friday, 12 March 2021 at 12:40:56 UTC+13 monmul wrote:

> But from the tests on my PC, it seems the old Envoy is workingdoes 
> it not.(so we do not have to worry about the new Envoy for now!)...so it 
> would appear as if the RPi is the culpithave I deducted correctly?
>
> On Friday, 12 March 2021 at 02:29:03 UTC+13 tke...@gmail.com wrote:
>
>> They did, but it was about 7 or 8 years ago. 
>>
>> You really need to call Davis. 
>>
>> On Wed, Mar 10, 2021 at 7:22 PM Graham Eddy  
>> wrote:
>>
>>> i do recall that davis introduced an incompatability between old 
>>> firmware and new datalogger but i don’t

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Hmmm! even more curiouserI notice from my webpage that data was 
collected and posted yesterdayafter having nothing updated for almost 2 
weeks!

On Friday, 12 March 2021 at 13:06:27 UTC+13 monmul wrote:

> So, if it is the RPi then it is either a sofward corruption on the card 
> caused by the repeated rebooting after the fuse tripsor else some 
> hardward failure on the board was the cause of the tripping. Its strange 
> that since reassembling the Envoy, RPi etc there has not been a fuse trip.
>
> One other thought occurs to me...I have a powered USB Hub attached to the 
> RPi(its a 3B)maybe I should disconnect the hub and try the Envoy 
> directly into the RPi..if minicom works that would point to the Hub as 
> being the culpit!!??
>
> On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote:
>
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ wee_device --clear-memory
>> Using configuration file /etc/weewx/weewx.conf
>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>> Proceeding will erase all archive records.
>> Are you sure you wish to proceed (y/n)? y
>> Erasing all archive records ...
>> Archive records erased.
>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 12:49:30
>>
>> Press CTRL-A Z for help on special keys
>> .
>> .
>> .
>>
>>
>> Again no return of TEST or NVER
>>
>> On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote:
>>
>>> So, having put the old Envoy back on the Rpi (having shown it worked on 
>>> the PC) this is what I getlooks like some kind of continuous Loop 
>>> situation.
>>>
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>>>
>>>
>>>
>>> Welcome to minicom 2.7
>>>
>>> OPTIONS: I18n 
>>> Compiled on Apr 22 2017, 09:14:19.
>>> Port /dev/ttyUSB0, 12:42:51
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ b 2
>>> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ   b 2
>>> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2
>>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>>
>>>
>>> ¤LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2
>>> âYLOO1 =vŠ 4I ÁÿÿÿPÿ 5⊑? ÿÿÿ½   b 2
>>> ¾LOO1 =vŠ 4I Áÿÿÿ
>>>
>>> On Friday, 12 March 2021 at 12:40:56 UTC+13 monmul wrote:
>>>
 But from the tests on my PC, it seems the old Envoy is workingdoes 
 it not.(so we do not have to worry about the new Envoy for now!)...so it 
 would appear as if the RPi is the culpithave I deducted correctly?

 On Friday, 12 March 2021 at 02:29:03 UTC+13 tke...@gmail.com wrote:

> They did, but it was about 7 or 8 years ago. 
>
> You really need to call Davis. 
>
> On Wed, Mar 10, 2021 at 7:22 PM Graham Eddy  
> wrote:
>
>> i do recall that davis introduced an incompatability between old 
>> firmware and new datalogger but i don’t recall the details. i’m sure a 
>> search of the forum archive would see if that was relevant
>>
>> On 11 Mar 2021, at 2:17 pm, monmul  wrote:
>>
>> Yes I am using the original data logger and cable that came with the 
>> old EnvoyI take out the data logger from he old one a

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

So, if it is the RPi then it is either a sofward corruption on the card 
caused by the repeated rebooting after the fuse tripsor else some 
hardward failure on the board was the cause of the tripping. Its strange 
that since reassembling the Envoy, RPi etc there has not been a fuse trip.

One other thought occurs to me...I have a powered USB Hub attached to the 
RPi(its a 3B)maybe I should disconnect the hub and try the Envoy 
directly into the RPi..if minicom works that would point to the Hub as 
being the culpit!!??

On Friday, 12 March 2021 at 12:51:51 UTC+13 monmul wrote:

> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ wee_device --clear-memory
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
> Proceeding will erase all archive records.
> Are you sure you wish to proceed (y/n)? y
> Erasing all archive records ...
> Archive records erased.
> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n 
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 12:49:30
>
> Press CTRL-A Z for help on special keys
> .
> .
> .
>
>
> Again no return of TEST or NVER
>
> On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote:
>
>> So, having put the old Envoy back on the Rpi (having shown it worked on 
>> the PC) this is what I getlooks like some kind of continuous Loop 
>> situation.
>>
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 12:42:51
>>
>> Press CTRL-A Z for help on special keys
>>
>> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ b 2
>> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ   b 2
>> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2
>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2  
>>
>>
>> ¤LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2
>> âYLOO1 =vŠ 4I ÁÿÿÿPÿ 5⊑? ÿÿÿ½   b 2
>> ¾LOO1 =vŠ 4I Áÿÿÿ
>>
>> On Friday, 12 March 2021 at 12:40:56 UTC+13 monmul wrote:
>>
>>> But from the tests on my PC, it seems the old Envoy is workingdoes 
>>> it not.(so we do not have to worry about the new Envoy for now!)...so it 
>>> would appear as if the RPi is the culpithave I deducted correctly?
>>>
>>> On Friday, 12 March 2021 at 02:29:03 UTC+13 tke...@gmail.com wrote:
>>>
 They did, but it was about 7 or 8 years ago. 

 You really need to call Davis. 

 On Wed, Mar 10, 2021 at 7:22 PM Graham Eddy  wrote:

> i do recall that davis introduced an incompatability between old 
> firmware and new datalogger but i don’t recall the details. i’m sure a 
> search of the forum archive would see if that was relevant
>
> On 11 Mar 2021, at 2:17 pm, monmul  wrote:
>
> Yes I am using the original data logger and cable that came with the 
> old EnvoyI take out the data logger from he old one and put it in the 
> new one...I suspect that the data logger may not be compatible with the 
> new 
> Envoy
>
>
> -- 
> 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 w

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ wee_device --clear-memory
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
Proceeding will erase all archive records.
Are you sure you wish to proceed (y/n)? y
Erasing all archive records ...
Archive records erased.
pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0


Welcome to minicom 2.7

OPTIONS: I18n 
Compiled on Apr 22 2017, 09:14:19.
Port /dev/ttyUSB0, 12:49:30

Press CTRL-A Z for help on special keys
.
.
.


Again no return of TEST or NVER

On Friday, 12 March 2021 at 12:46:43 UTC+13 monmul wrote:

> So, having put the old Envoy back on the Rpi (having shown it worked on 
> the PC) this is what I getlooks like some kind of continuous Loop 
> situation.
>
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0
>
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n 
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 12:42:51
>
> Press CTRL-A Z for help on special keys
>
> LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ b 2
> v)LOO1 =vˆ 4I ÁÿÿÿPÿ 5‘? ÿÿÿÂ   b 2
> ULOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½b 2
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ¾LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ±LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> «LOO1 =vŠ 4H ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> «LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ¾—LOO1 =vŠ 4H ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ¾—LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ³˜LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
> /‚LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> ]eLOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> Á LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> Á LOO1 =vŠ 4I ÁÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> ³˜LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
> /‚LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½   b 2
>  
>
> ¤LOO1 =vŠ 4I ÀÿÿÿPÿ 5‘? ÿÿÿ½ b 2
> âYLOO1 =vŠ 4I ÁÿÿÿPÿ 5⊑? ÿÿÿ½   b 2
> ¾LOO1 =vŠ 4I Áÿÿÿ
>
> On Friday, 12 March 2021 at 12:40:56 UTC+13 monmul wrote:
>
>> But from the tests on my PC, it seems the old Envoy is workingdoes it 
>> not.(so we do not have to worry about the new Envoy for now!)...so it would 
>> appear as if the RPi is the culpithave I deducted correctly?
>>
>> On Friday, 12 March 2021 at 02:29:03 UTC+13 tke...@gmail.com wrote:
>>
>>> They did, but it was about 7 or 8 years ago. 
>>>
>>> You really need to call Davis. 
>>>
>>> On Wed, Mar 10, 2021 at 7:22 PM Graham Eddy  wrote:
>>>
 i do recall that davis introduced an incompatability between old 
 firmware and new datalogger but i don’t recall the details. i’m sure a 
 search of the forum archive would see if that was relevant

 On 11 Mar 2021, at 2:17 pm, monmul  wrote:

 Yes I am using the original data logger and cable that came with the 
 old EnvoyI take out the data logger from he old one and put it in the 
 new one...I suspect that the data logger may not be compatible with the 
 new 
 Envoy


 -- 
 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/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.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/1f558dfd-e64d-4b9c-9345-65914fbe7743n%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

So, having put the old Envoy back on the Rpi (having shown it worked on the 
PC) this is what I getlooks like some kind of continuous Loop situation.

pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ sudo minicom -b 19200 -D /dev/ttyUSB0



Welcome to minicom 2.7

OPTIONS: I18n 
Compiled on Apr 22 2017, 09:14:19.
Port /dev/ttyUSB0, 12:42:51

Press CTRL-A Z for help on special keys

LOO1 =vˆ 4I   ÁÿÿÿPÿ   5‘? ÿÿÿÂ b 2
v)LOO1 =vˆ 4I   ÁÿÿÿPÿ   5‘? ÿÿÿÂ   b 2
ULOO1 =vŠ 4I   ÀÿÿÿPÿ   5‘? ÿÿÿ½b 2
/‚LOO1 =vŠ 4I   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
/‚LOO1 =vŠ 4I   ÁÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 ¾LOO1 =vŠ 4H   ÁÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 ±LOO1 =vŠ 4H   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 «LOO1 =vŠ 4H   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 «LOO1 =vŠ 4H   ÁÿÿÿPÿ   5‘? ÿÿÿ½   b 2
¾—LOO1 =vŠ 4H   ÁÿÿÿPÿ   5‘? ÿÿÿ½   b 2
¾—LOO1 =vŠ 4I   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
/‚LOO1 =vŠ 4I   ÁÿÿÿPÿ   5‘? ÿÿÿ½   b 2
³˜LOO1 =vŠ 4I   ÁÿÿÿPÿ   5‘? ÿÿÿ½   b 2
³˜LOO1 =vŠ 4I   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
/‚LOO1 =vŠ 4I   ÁÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 
]eLOO1 =vŠ 4I   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 
Á LOO1 =vŠ 4I   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 
Á LOO1 =vŠ 4I   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 
Á LOO1 =vŠ 4I   ÁÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 
³˜LOO1 =vŠ 4I   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 
/‚LOO1 =vŠ 4I   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 
/‚LOO1 =vŠ 4I   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 
/‚LOO1 =vŠ 4I   ÀÿÿÿPÿ   5‘? ÿÿÿ½   b 2
 

¤LOO1 =vŠ 4I  ÀÿÿÿPÿ   5‘? ÿÿÿ½ b 2
âYLOO1 =vŠ 4I   ÁÿÿÿPÿ   5⊑? ÿÿÿ½   b 2
 ¾LOO1 =vŠ 4I   Áÿÿÿ

On Friday, 12 March 2021 at 12:40:56 UTC+13 monmul wrote:

> But from the tests on my PC, it seems the old Envoy is workingdoes it 
> not.(so we do not have to worry about the new Envoy for now!)...so it would 
> appear as if the RPi is the culpithave I deducted correctly?
>
> On Friday, 12 March 2021 at 02:29:03 UTC+13 tke...@gmail.com wrote:
>
>> They did, but it was about 7 or 8 years ago. 
>>
>> You really need to call Davis. 
>>
>> On Wed, Mar 10, 2021 at 7:22 PM Graham Eddy  wrote:
>>
>>> i do recall that davis introduced an incompatability between old 
>>> firmware and new datalogger but i don’t recall the details. i’m sure a 
>>> search of the forum archive would see if that was relevant
>>>
>>> On 11 Mar 2021, at 2:17 pm, monmul  wrote:
>>>
>>> Yes I am using the original data logger and cable that came with the old 
>>> EnvoyI take out the data logger from he old one and put it in the new 
>>> one...I suspect that the data logger may not be compatible with the new 
>>> Envoy
>>>
>>>
>>> -- 
>>> 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/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.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/4bd182b2-7e47-4507-bc37-157f3682da8an%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

But from the tests on my PC, it seems the old Envoy is workingdoes it 
not.(so we do not have to worry about the new Envoy for now!)...so it would 
appear as if the RPi is the culpithave I deducted correctly?

On Friday, 12 March 2021 at 02:29:03 UTC+13 tke...@gmail.com wrote:

> They did, but it was about 7 or 8 years ago. 
>
> You really need to call Davis. 
>
> On Wed, Mar 10, 2021 at 7:22 PM Graham Eddy  wrote:
>
>> i do recall that davis introduced an incompatability between old firmware 
>> and new datalogger but i don’t recall the details. i’m sure a search of the 
>> forum archive would see if that was relevant
>>
>> On 11 Mar 2021, at 2:17 pm, monmul  wrote:
>>
>> Yes I am using the original data logger and cable that came with the old 
>> EnvoyI take out the data logger from he old one and put it in the new 
>> one...I suspect that the data logger may not be compatible with the new 
>> Envoy
>>
>>
>> -- 
>> 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/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.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/43c5919c-9ec8-4e89-b2e0-a7a1efa2d180n%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

They did, but it was about 7 or 8 years ago.

You really need to call Davis.

On Wed, Mar 10, 2021 at 7:22 PM Graham Eddy  wrote:

> i do recall that davis introduced an incompatability between old firmware
> and new datalogger but i don’t recall the details. i’m sure a search of the
> forum archive would see if that was relevant
>
> On 11 Mar 2021, at 2:17 pm, monmul  wrote:
>
> Yes I am using the original data logger and cable that came with the old
> EnvoyI take out the data logger from he old one and put it in the new
> one...I suspect that the data logger may not be compatible with the new
> Envoy
>
>
> --
> 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/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.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/CAPq0zEAQ8EzCB6UcPTNSSqHDFK69p_XWZiPyEfOLaCWEaYFmbg%40mail.gmail.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Graham Eddy]

i do recall that davis introduced an incompatability between old firmware and 
new datalogger but i don’t recall the details. i’m sure a search of the forum 
archive would see if that was relevant

> On 11 Mar 2021, at 2:17 pm, monmul  wrote:
> 
> Yes I am using the original data logger and cable that came with the old 
> EnvoyI take out the data logger from he old one and put it in the new 
> one...I suspect that the data logger may not be compatible with the new Envoy

-- 
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/A4FF1391-8844-4E16-8B1D-C2F6C6F06A3B%40gmail.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Yes I am using the original data logger and cable that came with the old 
EnvoyI take out the data logger from he old one and put it in the new 
one...I suspect that the data logger may not be compatible with the new 
Envoy.the new one was purchased about 3 years ago and was just put in 
storage and never used or tested. The product numbers are slightly 
different the old one being 6316 and the new one being 6316NZ

On Thursday, 11 March 2021 at 16:12:21 UTC+13 graha...@gmail.com wrote:

> how much is ‘new’ and much much ‘old’? i.e. with the new envoy, are you 
> using the old known-working data logger and cable?
>
> On 11 Mar 2021, at 2:09 pm, monmul  wrote:
>
> New Envoy shows no response to TEST or NVER...so that one is definately 
> dead I think!
>
>
>

-- 
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/9e31efdd-ba9e-4300-8e34-040ee7fd6d27n%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Graham Eddy]

how much is ‘new’ and much much ‘old’? i.e. with the new envoy, are you using 
the old known-working data logger and cable?

> On 11 Mar 2021, at 2:09 pm, monmul  wrote:
> 
> New Envoy shows no response to TEST or NVER...so that one is definately dead 
> I think!

-- 
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/A6B84107-4BA1-4304-9B61-244F700591E4%40gmail.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

I notice the old Envoy beeps twice when I plug it in but the new one only 
beeps once.

On Thursday, 11 March 2021 at 16:01:11 UTC+13 monmul wrote:

> New Envoy shows no response to TEST or NVER...so that one is definately 
> dead I think!
>
> On Thursday, 11 March 2021 at 15:39:36 UTC+13 monmul wrote:
>
>> "WRD"<0x12><0x4d>, ACK .not sure hot to use this commandis it 
>> just "WRD"?
>> This is the old Envoy
>>
>> No data as such comes backherefrom the first "TEST" is the result 
>> of all the commands above in turn.
>> TEST
>>
>>
>> OK
>> 2363 7 0 1316 1
>>
>> OK
>>   
>>   
>> OK
>>   
>>   
>>   
>> OK
>>   
>> Dec 30 2008  
>>
>>   
>>   
>> OK
>>   
>> 1.82  
>>   
>>
>>
>>
>>
>> On Thursday, 11 March 2021 at 15:04:01 UTC+13 gjr80 wrote:
>>
>>> Ok, that sounds promising. Was that the old or the new Envoy?
>>>
>>> FYI the other testing commands are:
>>>
>>> Testing commands
>>> "TEST"   Sends the string “TEST\n” back.
>>> "WRD"<0x12><0x4d>, ACK   Responds with a weather station type that is 
>>> backward compatible with earlier Davis weather products.
>>> "RXCHECK"   Sends the Console Diagnostics report.
>>> "RXTEST"  Moves the console from the “Receiving from” screen to the 
>>> main current conditions screen.
>>> "VER"
>>> "RECEIVERS"  Sends the bit map of station IDs that the console can 
>>> hear, This is not the byte for indicating what the console selects to 
>>> listen from.
>>> "NVER"  Sends the firmware version number as a text string. This 
>>> command is only supported by Vantage Pro2 (Firmware 1.90 or later) and 
>>> Vantage Vue.
>>>
>>>
>>> Gary
>>> On Thursday, 11 March 2021 at 11:23:43 UTC+10 monmul wrote:
>>>
 j@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0
 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
 /run/user/1000/gvfs
   Output information may be incomplete.
 lsof: WARNING: can't stat() fuse.pcloud file system 
 /tmp/.mount_pcloudpeaisz
   Output information may be incomplete.
 lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
   Output information may be incomplete.
 lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive
   Output information may be incomplete.
 pj@pj-selgbuild:~$ sudo screen /dev/ttyUSB0 19200
 sudo: screen: command not found
 pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0

 Command 'minicom' not found, but can be installed with:

 sudo apt install minicom

 pj@pj-selgbuild:~$ sudo apt install minicom
 Reading package lists... Done
 Building dependency tree   
 Reading state information... Done
 The following additional packages will be installed:
   lrzsz
 The following NEW packages will be installed:
   lrzsz minicom
 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded.
 Need to get 313 kB of archives.
 After this operation, 1,486 kB of additional disk space will be used.
 Do you want to continue? [Y/n] y
 Get:1 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 
 lrzsz amd64 0.12.21-10 [74.8 kB]
 Get:2 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 
 minicom amd64 2.7.1-1.1 [239 kB]
 Fetched 313 kB in 1s (603 kB/s)  
 Selecting previously unselected package lrzsz.
 (Reading database ... 289378 files and directories currently installed.)
 Preparing to unpack .../lrzsz_0.12.21-10_amd64.deb ...
 Unpacking lrzsz (0.12.21-10) ...
 Selecting previously unselected package minicom.
 Preparing to unpack .../minicom_2.7.1-1.1_amd64.deb ...
 Unpacking minicom (2.7.1-1.1) ...
 Setting up minicom (2.7.1-1.1) ...
 Setting up lrzsz (0.12.21-10) ...
 Processing triggers for mime-support (3.64ubuntu1) ...
 Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
 Processing triggers for man-db (2.9.1-1) ...
 Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
 pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Permission denied
 pj@pj-selgbuild:~$ sudo minicom -b 19200 -D /dev/ttyUSB0


 Welcome to minicom 2.7.1

 OPTIONS: I18n 
 Compiled on Dec 23 2019, 02:06:26.
 Port /dev/ttyUSB0, 14:14:37

 Press CTRL-A Z for help on special keys









 TEST

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

New Envoy shows no response to TEST or NVER...so that one is definately 
dead I think!

On Thursday, 11 March 2021 at 15:39:36 UTC+13 monmul wrote:

> "WRD"<0x12><0x4d>, ACK .not sure hot to use this commandis it just 
> "WRD"?
> This is the old Envoy
>
> No data as such comes backherefrom the first "TEST" is the result 
> of all the commands above in turn.
> TEST
>
>
> OK
> 2363 7 0 1316 1
>
> OK
>   
>   
> OK
>   
>   
>   
> OK
>   
> Dec 30 2008
>  
>   
>   
> OK
>   
> 1.82  
>   
>
>
>
>
> On Thursday, 11 March 2021 at 15:04:01 UTC+13 gjr80 wrote:
>
>> Ok, that sounds promising. Was that the old or the new Envoy?
>>
>> FYI the other testing commands are:
>>
>> Testing commands
>> "TEST"   Sends the string “TEST\n” back.
>> "WRD"<0x12><0x4d>, ACK   Responds with a weather station type that is 
>> backward compatible with earlier Davis weather products.
>> "RXCHECK"   Sends the Console Diagnostics report.
>> "RXTEST"  Moves the console from the “Receiving from” screen to the main 
>> current conditions screen.
>> "VER"
>> "RECEIVERS"  Sends the bit map of station IDs that the console can hear, 
>> This is not the byte for indicating what the console selects to listen from.
>> "NVER"  Sends the firmware version number as a text string. This command 
>> is only supported by Vantage Pro2 (Firmware 1.90 or later) and Vantage Vue.
>>
>>
>> Gary
>> On Thursday, 11 March 2021 at 11:23:43 UTC+10 monmul wrote:
>>
>>> j@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0
>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>>> /run/user/1000/gvfs
>>>   Output information may be incomplete.
>>> lsof: WARNING: can't stat() fuse.pcloud file system 
>>> /tmp/.mount_pcloudpeaisz
>>>   Output information may be incomplete.
>>> lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
>>>   Output information may be incomplete.
>>> lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive
>>>   Output information may be incomplete.
>>> pj@pj-selgbuild:~$ sudo screen /dev/ttyUSB0 19200
>>> sudo: screen: command not found
>>> pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0
>>>
>>> Command 'minicom' not found, but can be installed with:
>>>
>>> sudo apt install minicom
>>>
>>> pj@pj-selgbuild:~$ sudo apt install minicom
>>> Reading package lists... Done
>>> Building dependency tree   
>>> Reading state information... Done
>>> The following additional packages will be installed:
>>>   lrzsz
>>> The following NEW packages will be installed:
>>>   lrzsz minicom
>>> 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded.
>>> Need to get 313 kB of archives.
>>> After this operation, 1,486 kB of additional disk space will be used.
>>> Do you want to continue? [Y/n] y
>>> Get:1 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 
>>> lrzsz amd64 0.12.21-10 [74.8 kB]
>>> Get:2 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 
>>> minicom amd64 2.7.1-1.1 [239 kB]
>>> Fetched 313 kB in 1s (603 kB/s)  
>>> Selecting previously unselected package lrzsz.
>>> (Reading database ... 289378 files and directories currently installed.)
>>> Preparing to unpack .../lrzsz_0.12.21-10_amd64.deb ...
>>> Unpacking lrzsz (0.12.21-10) ...
>>> Selecting previously unselected package minicom.
>>> Preparing to unpack .../minicom_2.7.1-1.1_amd64.deb ...
>>> Unpacking minicom (2.7.1-1.1) ...
>>> Setting up minicom (2.7.1-1.1) ...
>>> Setting up lrzsz (0.12.21-10) ...
>>> Processing triggers for mime-support (3.64ubuntu1) ...
>>> Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
>>> Processing triggers for man-db (2.9.1-1) ...
>>> Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
>>> pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Permission denied
>>> pj@pj-selgbuild:~$ sudo minicom -b 19200 -D /dev/ttyUSB0
>>>
>>>
>>> Welcome to minicom 2.7.1
>>>
>>> OPTIONS: I18n 
>>> Compiled on Dec 23 2019, 02:06:26.
>>> Port /dev/ttyUSB0, 14:14:37
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> TEST
>>>
>>>
>>> TEST
>>>
>>> OK
>>> 1.82
>>>
>>> On Thursday, 11 March 2021 at 14:14:18 UTC+13 monmul wrote:
>>>
 Hmm! nothiing shows...I have a USB port plugged into this pc...and none 
 of the USBs show?!?!

 pj@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0
 [sudo] password for pj: 
 lsof: W

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

"WRD"<0x12><0x4d>, ACK .not sure hot to use this commandis it just 
"WRD"?
This is the old Envoy

No data as such comes backherefrom the first "TEST" is the result 
of all the commands above in turn.
TEST


OK
2363 7 0 1316 1

OK


OK  



OK  

Dec 30 2008
 


OK  

1.82





On Thursday, 11 March 2021 at 15:04:01 UTC+13 gjr80 wrote:

> Ok, that sounds promising. Was that the old or the new Envoy?
>
> FYI the other testing commands are:
>
> Testing commands
> "TEST"   Sends the string “TEST\n” back.
> "WRD"<0x12><0x4d>, ACK   Responds with a weather station type that is 
> backward compatible with earlier Davis weather products.
> "RXCHECK"   Sends the Console Diagnostics report.
> "RXTEST"  Moves the console from the “Receiving from” screen to the main 
> current conditions screen.
> "VER"
> "RECEIVERS"  Sends the bit map of station IDs that the console can hear, 
> This is not the byte for indicating what the console selects to listen from.
> "NVER"  Sends the firmware version number as a text string. This command 
> is only supported by Vantage Pro2 (Firmware 1.90 or later) and Vantage Vue.
>
>
> Gary
> On Thursday, 11 March 2021 at 11:23:43 UTC+10 monmul wrote:
>
>> j@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0
>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>> /run/user/1000/gvfs
>>   Output information may be incomplete.
>> lsof: WARNING: can't stat() fuse.pcloud file system 
>> /tmp/.mount_pcloudpeaisz
>>   Output information may be incomplete.
>> lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
>>   Output information may be incomplete.
>> lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive
>>   Output information may be incomplete.
>> pj@pj-selgbuild:~$ sudo screen /dev/ttyUSB0 19200
>> sudo: screen: command not found
>> pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0
>>
>> Command 'minicom' not found, but can be installed with:
>>
>> sudo apt install minicom
>>
>> pj@pj-selgbuild:~$ sudo apt install minicom
>> Reading package lists... Done
>> Building dependency tree   
>> Reading state information... Done
>> The following additional packages will be installed:
>>   lrzsz
>> The following NEW packages will be installed:
>>   lrzsz minicom
>> 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded.
>> Need to get 313 kB of archives.
>> After this operation, 1,486 kB of additional disk space will be used.
>> Do you want to continue? [Y/n] y
>> Get:1 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 lrzsz 
>> amd64 0.12.21-10 [74.8 kB]
>> Get:2 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 
>> minicom amd64 2.7.1-1.1 [239 kB]
>> Fetched 313 kB in 1s (603 kB/s)  
>> Selecting previously unselected package lrzsz.
>> (Reading database ... 289378 files and directories currently installed.)
>> Preparing to unpack .../lrzsz_0.12.21-10_amd64.deb ...
>> Unpacking lrzsz (0.12.21-10) ...
>> Selecting previously unselected package minicom.
>> Preparing to unpack .../minicom_2.7.1-1.1_amd64.deb ...
>> Unpacking minicom (2.7.1-1.1) ...
>> Setting up minicom (2.7.1-1.1) ...
>> Setting up lrzsz (0.12.21-10) ...
>> Processing triggers for mime-support (3.64ubuntu1) ...
>> Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
>> Processing triggers for man-db (2.9.1-1) ...
>> Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
>> pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Permission denied
>> pj@pj-selgbuild:~$ sudo minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>> Welcome to minicom 2.7.1
>>
>> OPTIONS: I18n 
>> Compiled on Dec 23 2019, 02:06:26.
>> Port /dev/ttyUSB0, 14:14:37
>>
>> Press CTRL-A Z for help on special keys
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> TEST
>>
>>
>> TEST
>>
>> OK
>> 1.82
>>
>> On Thursday, 11 March 2021 at 14:14:18 UTC+13 monmul wrote:
>>
>>> Hmm! nothiing shows...I have a USB port plugged into this pc...and none 
>>> of the USBs show?!?!
>>>
>>> pj@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0
>>> [sudo] password for pj: 
>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>>> /run/user/1000/gvfs
>>>   Output information may be incomplete.
>>> lsof: WARNING: can't stat() fuse.pcloud file system 
>>> /tmp/.mount_pcloudpeaisz
>>>   Output information may be incomplete.
>>> lsof: WARNING: can't stat() fuse file system /run/user/10

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

Ok, that sounds promising. Was that the old or the new Envoy?

FYI the other testing commands are:

Testing commands
"TEST"   Sends the string “TEST\n” back.
"WRD"<0x12><0x4d>, ACK   Responds with a weather station type that is 
backward compatible with earlier Davis weather products.
"RXCHECK"   Sends the Console Diagnostics report.
"RXTEST"  Moves the console from the “Receiving from” screen to the main 
current conditions screen.
"VER"
"RECEIVERS"  Sends the bit map of station IDs that the console can hear, 
This is not the byte for indicating what the console selects to listen from.
"NVER"  Sends the firmware version number as a text string. This command is 
only supported by Vantage Pro2 (Firmware 1.90 or later) and Vantage Vue.


Gary
On Thursday, 11 March 2021 at 11:23:43 UTC+10 monmul wrote:

> j@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
>   Output information may be incomplete.
> lsof: WARNING: can't stat() fuse.pcloud file system 
> /tmp/.mount_pcloudpeaisz
>   Output information may be incomplete.
> lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
>   Output information may be incomplete.
> lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive
>   Output information may be incomplete.
> pj@pj-selgbuild:~$ sudo screen /dev/ttyUSB0 19200
> sudo: screen: command not found
> pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0
>
> Command 'minicom' not found, but can be installed with:
>
> sudo apt install minicom
>
> pj@pj-selgbuild:~$ sudo apt install minicom
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> The following additional packages will be installed:
>   lrzsz
> The following NEW packages will be installed:
>   lrzsz minicom
> 0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded.
> Need to get 313 kB of archives.
> After this operation, 1,486 kB of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Get:1 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 lrzsz 
> amd64 0.12.21-10 [74.8 kB]
> Get:2 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 
> minicom amd64 2.7.1-1.1 [239 kB]
> Fetched 313 kB in 1s (603 kB/s)  
> Selecting previously unselected package lrzsz.
> (Reading database ... 289378 files and directories currently installed.)
> Preparing to unpack .../lrzsz_0.12.21-10_amd64.deb ...
> Unpacking lrzsz (0.12.21-10) ...
> Selecting previously unselected package minicom.
> Preparing to unpack .../minicom_2.7.1-1.1_amd64.deb ...
> Unpacking minicom (2.7.1-1.1) ...
> Setting up minicom (2.7.1-1.1) ...
> Setting up lrzsz (0.12.21-10) ...
> Processing triggers for mime-support (3.64ubuntu1) ...
> Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
> Processing triggers for man-db (2.9.1-1) ...
> Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
> pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Permission denied
> pj@pj-selgbuild:~$ sudo minicom -b 19200 -D /dev/ttyUSB0
>
>
> Welcome to minicom 2.7.1
>
> OPTIONS: I18n 
> Compiled on Dec 23 2019, 02:06:26.
> Port /dev/ttyUSB0, 14:14:37
>
> Press CTRL-A Z for help on special keys
>
>
>
>
>
>
>
>
>
> TEST
>
>
> TEST
>
> OK
> 1.82
>
> On Thursday, 11 March 2021 at 14:14:18 UTC+13 monmul wrote:
>
>> Hmm! nothiing shows...I have a USB port plugged into this pc...and none 
>> of the USBs show?!?!
>>
>> pj@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0
>> [sudo] password for pj: 
>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>> /run/user/1000/gvfs
>>   Output information may be incomplete.
>> lsof: WARNING: can't stat() fuse.pcloud file system 
>> /tmp/.mount_pcloudpeaisz
>>   Output information may be incomplete.
>> lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
>>   Output information may be incomplete.
>> lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive
>>   Output information may be incomplete.
>> pj@pj-selgbuild:~$ 
>>
>>
>> On Tuesday, 9 March 2021 at 21:58:49 UTC+13 monmul wrote:
>>
>>> Been MS free since 2008. Never used Apple. Got Lineage on my phone.
>>>
>>> On Tuesday, 9 March 2021 at 21:55:46 UTC+13 gjr80 wrote:
>>>
 Someone who has seen the light! :)

 On Tuesday, 9 March 2021 at 18:27:36 UTC+10 monmul wrote:

> Thanks, I only have Ubuntuand I use VNC client.
>
>
>
> On Tuesday, 9 March 2021 at 21:22:57 UTC+13 David wrote:
>
>> PuTTY (https://www.putty.org/), which is a free SSH/telnet client 
>> works on Windows devices and can also connect to serial devices.
>>
>> --
>> David
>>
>> On Tue, Mar 9, 2021 at 5:15 PM monmul  wrote:
>>
>>> Cool, thanks, will get on that with my laptop in the next day or 
>>> sothank you!
>>>
>>> On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote:
>>>
 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

j@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
lsof: WARNING: can't stat() fuse.pcloud file system /tmp/.mount_pcloudpeaisz
  Output information may be incomplete.
lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
  Output information may be incomplete.
lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive
  Output information may be incomplete.
pj@pj-selgbuild:~$ sudo screen /dev/ttyUSB0 19200
sudo: screen: command not found
pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0

Command 'minicom' not found, but can be installed with:

sudo apt install minicom

pj@pj-selgbuild:~$ sudo apt install minicom
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  lrzsz
The following NEW packages will be installed:
  lrzsz minicom
0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded.
Need to get 313 kB of archives.
After this operation, 1,486 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 lrzsz 
amd64 0.12.21-10 [74.8 kB]
Get:2 http://ucmirror.canterbury.ac.nz/ubuntu focal/universe amd64 minicom 
amd64 2.7.1-1.1 [239 kB]
Fetched 313 kB in 1s (603 kB/s)  
Selecting previously unselected package lrzsz.
(Reading database ... 289378 files and directories currently installed.)
Preparing to unpack .../lrzsz_0.12.21-10_amd64.deb ...
Unpacking lrzsz (0.12.21-10) ...
Selecting previously unselected package minicom.
Preparing to unpack .../minicom_2.7.1-1.1_amd64.deb ...
Unpacking minicom (2.7.1-1.1) ...
Setting up minicom (2.7.1-1.1) ...
Setting up lrzsz (0.12.21-10) ...
Processing triggers for mime-support (3.64ubuntu1) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu1) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
pj@pj-selgbuild:~$ minicom -b 19200 -D /dev/ttyUSB0
minicom: cannot open /dev/ttyUSB0: Permission denied
pj@pj-selgbuild:~$ sudo minicom -b 19200 -D /dev/ttyUSB0


Welcome to minicom 2.7.1

OPTIONS: I18n 
Compiled on Dec 23 2019, 02:06:26.
Port /dev/ttyUSB0, 14:14:37

Press CTRL-A Z for help on special keys









TEST


TEST

OK
1.82

On Thursday, 11 March 2021 at 14:14:18 UTC+13 monmul wrote:

> Hmm! nothiing shows...I have a USB port plugged into this pc...and none of 
> the USBs show?!?!
>
> pj@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0
> [sudo] password for pj: 
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
>   Output information may be incomplete.
> lsof: WARNING: can't stat() fuse.pcloud file system 
> /tmp/.mount_pcloudpeaisz
>   Output information may be incomplete.
> lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
>   Output information may be incomplete.
> lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive
>   Output information may be incomplete.
> pj@pj-selgbuild:~$ 
>
>
> On Tuesday, 9 March 2021 at 21:58:49 UTC+13 monmul wrote:
>
>> Been MS free since 2008. Never used Apple. Got Lineage on my phone.
>>
>> On Tuesday, 9 March 2021 at 21:55:46 UTC+13 gjr80 wrote:
>>
>>> Someone who has seen the light! :)
>>>
>>> On Tuesday, 9 March 2021 at 18:27:36 UTC+10 monmul wrote:
>>>
 Thanks, I only have Ubuntuand I use VNC client.



 On Tuesday, 9 March 2021 at 21:22:57 UTC+13 David wrote:

> PuTTY (https://www.putty.org/), which is a free SSH/telnet client 
> works on Windows devices and can also connect to serial devices.
>
> --
> David
>
> On Tue, Mar 9, 2021 at 5:15 PM monmul  wrote:
>
>> Cool, thanks, will get on that with my laptop in the next day or 
>> sothank you!
>>
>> On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote:
>>
>>> Anything will do, no grunt needed, all you need is a terminal 
>>> program of some sort, minicom will do the job on anything Linux. 
>>> Windows 
>>> used to come with some sort of terminal program. Not sure about a Mac. 
>>> Certainly no need to install WeeWX, you just want to run the 
>>> connectivity 
>>> test with your Envoy(s) to prove it(they) respond(s).
>>>
>>> Gary
>>>
>>> On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote:
>>>
 Hmmm! the only spare RPI I have at the moment is a 3A+ is that 
 likely to have enough grunt to do the job? Oh! do you mean I could 
 attach 
 the "new" Envoy to a PC (running Ubuntu) and do the connectivity test?


 On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:

> Possibly, but if you are using the same RPi with the same cable as 
> you have used with your new unresponsive Envoy then perhaps the issue 
> i

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Hmm! nothiing shows...I have a USB port plugged into this pc...and none of 
the USBs show?!?!

pj@pj-selgbuild:~$ sudo lsof /dev/ttyUSB0
[sudo] password for pj: 
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
lsof: WARNING: can't stat() fuse.pcloud file system /tmp/.mount_pcloudpeaisz
  Output information may be incomplete.
lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
  Output information may be incomplete.
lsof: WARNING: can't stat() fuse file system /home/pj/pCloudDrive
  Output information may be incomplete.
pj@pj-selgbuild:~$ 


On Tuesday, 9 March 2021 at 21:58:49 UTC+13 monmul wrote:

> Been MS free since 2008. Never used Apple. Got Lineage on my phone.
>
> On Tuesday, 9 March 2021 at 21:55:46 UTC+13 gjr80 wrote:
>
>> Someone who has seen the light! :)
>>
>> On Tuesday, 9 March 2021 at 18:27:36 UTC+10 monmul wrote:
>>
>>> Thanks, I only have Ubuntuand I use VNC client.
>>>
>>>
>>>
>>> On Tuesday, 9 March 2021 at 21:22:57 UTC+13 David wrote:
>>>
 PuTTY (https://www.putty.org/), which is a free SSH/telnet client 
 works on Windows devices and can also connect to serial devices.

 --
 David

 On Tue, Mar 9, 2021 at 5:15 PM monmul  wrote:

> Cool, thanks, will get on that with my laptop in the next day or 
> sothank you!
>
> On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote:
>
>> Anything will do, no grunt needed, all you need is a terminal program 
>> of some sort, minicom will do the job on anything Linux. Windows used to 
>> come with some sort of terminal program. Not sure about a Mac. Certainly 
>> no 
>> need to install WeeWX, you just want to run the connectivity test with 
>> your 
>> Envoy(s) to prove it(they) respond(s).
>>
>> Gary
>>
>> On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote:
>>
>>> Hmmm! the only spare RPI I have at the moment is a 3A+ is that 
>>> likely to have enough grunt to do the job? Oh! do you mean I could 
>>> attach 
>>> the "new" Envoy to a PC (running Ubuntu) and do the connectivity test?
>>>
>>>
>>> On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:
>>>
 Possibly, but if you are using the same RPi with the same cable as 
 you have used with your new unresponsive Envoy then perhaps the issue 
 is 
 with the RPi or the cable. I would be looking for another RPi or PC 
 (Windows (ugh), Mac or whatever) and run a terminal window/program and 
 do 
 the basic connectivity test (send ENTER and get a response from the 
 Envoy). 
 I would even try a different cable if you have another. Two different 
 RPis/PCs/cables etc not working would be unusual. If that fails to get 
 a 
 response from your new Envoy then as Tom said it's time to get in 
 touch 
 with Davis or their agent.

 Gary

 On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:

> Is this telling me that my "old" Envoy is indeed broken?
>
> pi@WeatherPi:~ $ wee_device --clear-memory
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
> Unable to wake up console... sleeping
> Unable to wake up console... retrying
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_device", line 78, in 
> main()
>   File "/usr/share/weewx/wee_device", line 74, in main
> device.configure(config_dict)
>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in 
> configure
> self.do_options(options, parser, config_dict, not 
> options.noprompt)
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in 
> do_options
> station = Vantage(**config_dict[DRIVER_NAME])
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in 
> __init__
> self._setup()
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in 
> _setup
> self.hardware_type = self._determine_hardware()
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in 
> _determine_hardware
> raise weewx.WeeWxIOError("Unable to read hardware type")
> weewx.WeeWxIOError: Unable to read hardware type
>
>
> On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:
>
>> *WeeWX generates HTML pages, but it does not update them 
>> *
>>
>>
>> On Sat, Mar 6, 2021 at 10:27 PM monmul  wrote:
>

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

Someone who has seen the light! :)

On Tuesday, 9 March 2021 at 18:27:36 UTC+10 monmul wrote:

> Thanks, I only have Ubuntuand I use VNC client.
>
>
>
> On Tuesday, 9 March 2021 at 21:22:57 UTC+13 David wrote:
>
>> PuTTY (https://www.putty.org/), which is a free SSH/telnet client works 
>> on Windows devices and can also connect to serial devices.
>>
>> --
>> David
>>
>> On Tue, Mar 9, 2021 at 5:15 PM monmul  wrote:
>>
>>> Cool, thanks, will get on that with my laptop in the next day or 
>>> sothank you!
>>>
>>> On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote:
>>>
 Anything will do, no grunt needed, all you need is a terminal program 
 of some sort, minicom will do the job on anything Linux. Windows used to 
 come with some sort of terminal program. Not sure about a Mac. Certainly 
 no 
 need to install WeeWX, you just want to run the connectivity test with 
 your 
 Envoy(s) to prove it(they) respond(s).

 Gary

 On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote:

> Hmmm! the only spare RPI I have at the moment is a 3A+ is that likely 
> to have enough grunt to do the job? Oh! do you mean I could attach the 
> "new" Envoy to a PC (running Ubuntu) and do the connectivity test?
>
>
> On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:
>
>> Possibly, but if you are using the same RPi with the same cable as 
>> you have used with your new unresponsive Envoy then perhaps the issue is 
>> with the RPi or the cable. I would be looking for another RPi or PC 
>> (Windows (ugh), Mac or whatever) and run a terminal window/program and 
>> do 
>> the basic connectivity test (send ENTER and get a response from the 
>> Envoy). 
>> I would even try a different cable if you have another. Two different 
>> RPis/PCs/cables etc not working would be unusual. If that fails to get a 
>> response from your new Envoy then as Tom said it's time to get in touch 
>> with Davis or their agent.
>>
>> Gary
>>
>> On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:
>>
>>> Is this telling me that my "old" Envoy is indeed broken?
>>>
>>> pi@WeatherPi:~ $ wee_device --clear-memory
>>> Using configuration file /etc/weewx/weewx.conf
>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>>> Unable to wake up console... sleeping
>>> Unable to wake up console... retrying
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/wee_device", line 78, in 
>>> main()
>>>   File "/usr/share/weewx/wee_device", line 74, in main
>>> device.configure(config_dict)
>>>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in 
>>> configure
>>> self.do_options(options, parser, config_dict, not 
>>> options.noprompt)
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in 
>>> do_options
>>> station = Vantage(**config_dict[DRIVER_NAME])
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in 
>>> __init__
>>> self._setup()
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in 
>>> _setup
>>> self.hardware_type = self._determine_hardware()
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in 
>>> _determine_hardware
>>> raise weewx.WeeWxIOError("Unable to read hardware type")
>>> weewx.WeeWxIOError: Unable to read hardware type
>>>
>>>
>>> On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:
>>>
 *WeeWX generates HTML pages, but it does not update them 
 *


 On Sat, Mar 6, 2021 at 10:27 PM monmul  wrote:

> Even curiouserthe photo which is supposed to update every 20 
> minutes does updatebut not the weather data...still stuck on 
> 21/2/2021
>
> www.wilsonbayweather.com
>
> On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:
>
>> Mar  7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>> Getting archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>> Retry #0 failed
>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>> Rude wake up of console successful
>> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router 
>> Advertisement from fe80::724f:57ff:feb7:82a1
>> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 
>> lease
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>> Retrieving 513 page(s); starting index= 0
>> Mar  7 19:20:20 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Been MS free since 2008. Never used Apple. Got Lineage on my phone.

On Tuesday, 9 March 2021 at 21:55:46 UTC+13 gjr80 wrote:

> Someone who has seen the light! :)
>
> On Tuesday, 9 March 2021 at 18:27:36 UTC+10 monmul wrote:
>
>> Thanks, I only have Ubuntuand I use VNC client.
>>
>>
>>
>> On Tuesday, 9 March 2021 at 21:22:57 UTC+13 David wrote:
>>
>>> PuTTY (https://www.putty.org/), which is a free SSH/telnet client works 
>>> on Windows devices and can also connect to serial devices.
>>>
>>> --
>>> David
>>>
>>> On Tue, Mar 9, 2021 at 5:15 PM monmul  wrote:
>>>
 Cool, thanks, will get on that with my laptop in the next day or 
 sothank you!

 On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote:

> Anything will do, no grunt needed, all you need is a terminal program 
> of some sort, minicom will do the job on anything Linux. Windows used to 
> come with some sort of terminal program. Not sure about a Mac. Certainly 
> no 
> need to install WeeWX, you just want to run the connectivity test with 
> your 
> Envoy(s) to prove it(they) respond(s).
>
> Gary
>
> On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote:
>
>> Hmmm! the only spare RPI I have at the moment is a 3A+ is that likely 
>> to have enough grunt to do the job? Oh! do you mean I could attach the 
>> "new" Envoy to a PC (running Ubuntu) and do the connectivity test?
>>
>>
>> On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:
>>
>>> Possibly, but if you are using the same RPi with the same cable as 
>>> you have used with your new unresponsive Envoy then perhaps the issue 
>>> is 
>>> with the RPi or the cable. I would be looking for another RPi or PC 
>>> (Windows (ugh), Mac or whatever) and run a terminal window/program and 
>>> do 
>>> the basic connectivity test (send ENTER and get a response from the 
>>> Envoy). 
>>> I would even try a different cable if you have another. Two different 
>>> RPis/PCs/cables etc not working would be unusual. If that fails to get 
>>> a 
>>> response from your new Envoy then as Tom said it's time to get in touch 
>>> with Davis or their agent.
>>>
>>> Gary
>>>
>>> On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:
>>>
 Is this telling me that my "old" Envoy is indeed broken?

 pi@WeatherPi:~ $ wee_device --clear-memory
 Using configuration file /etc/weewx/weewx.conf
 Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
 Unable to wake up console... sleeping
 Unable to wake up console... retrying
 Traceback (most recent call last):
   File "/usr/share/weewx/wee_device", line 78, in 
 main()
   File "/usr/share/weewx/wee_device", line 74, in main
 device.configure(config_dict)
   File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in 
 configure
 self.do_options(options, parser, config_dict, not 
 options.noprompt)
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in 
 do_options
 station = Vantage(**config_dict[DRIVER_NAME])
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in 
 __init__
 self._setup()
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in 
 _setup
 self.hardware_type = self._determine_hardware()
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in 
 _determine_hardware
 raise weewx.WeeWxIOError("Unable to read hardware type")
 weewx.WeeWxIOError: Unable to read hardware type


 On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:

> *WeeWX generates HTML pages, but it does not update them 
> *
>
>
> On Sat, Mar 6, 2021 at 10:27 PM monmul  wrote:
>
>> Even curiouserthe photo which is supposed to update every 20 
>> minutes does updatebut not the weather data...still stuck on 
>> 21/2/2021
>>
>> www.wilsonbayweather.com
>>
>> On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:
>>
>>> Mar  7 19:20:15 WeatherPi weewx[789] DEBUG 
>>> weewx.drivers.vantage: Getting archive packets since 2021-02-21 
>>> 08:00:00 
>>> NZDT (1613847600)
>>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG 
>>> weewx.drivers.vantage: Retry #0 failed
>>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG 
>>> weewx.drivers.vantage: Rude wake up of console successful
>>> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router 
>>> Advertisemen

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Thanks, I only have Ubuntuand I use VNC client.



On Tuesday, 9 March 2021 at 21:22:57 UTC+13 David wrote:

> PuTTY (https://www.putty.org/), which is a free SSH/telnet client works 
> on Windows devices and can also connect to serial devices.
>
> --
> David
>
> On Tue, Mar 9, 2021 at 5:15 PM monmul  wrote:
>
>> Cool, thanks, will get on that with my laptop in the next day or 
>> sothank you!
>>
>> On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote:
>>
>>> Anything will do, no grunt needed, all you need is a terminal program of 
>>> some sort, minicom will do the job on anything Linux. Windows used to come 
>>> with some sort of terminal program. Not sure about a Mac. Certainly no need 
>>> to install WeeWX, you just want to run the connectivity test with your 
>>> Envoy(s) to prove it(they) respond(s).
>>>
>>> Gary
>>>
>>> On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote:
>>>
 Hmmm! the only spare RPI I have at the moment is a 3A+ is that likely 
 to have enough grunt to do the job? Oh! do you mean I could attach the 
 "new" Envoy to a PC (running Ubuntu) and do the connectivity test?


 On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:

> Possibly, but if you are using the same RPi with the same cable as you 
> have used with your new unresponsive Envoy then perhaps the issue is with 
> the RPi or the cable. I would be looking for another RPi or PC (Windows 
> (ugh), Mac or whatever) and run a terminal window/program and do the 
> basic 
> connectivity test (send ENTER and get a response from the Envoy). I would 
> even try a different cable if you have another. Two different 
> RPis/PCs/cables etc not working would be unusual. If that fails to get a 
> response from your new Envoy then as Tom said it's time to get in touch 
> with Davis or their agent.
>
> Gary
>
> On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:
>
>> Is this telling me that my "old" Envoy is indeed broken?
>>
>> pi@WeatherPi:~ $ wee_device --clear-memory
>> Using configuration file /etc/weewx/weewx.conf
>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>> Unable to wake up console... sleeping
>> Unable to wake up console... retrying
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_device", line 78, in 
>> main()
>>   File "/usr/share/weewx/wee_device", line 74, in main
>> device.configure(config_dict)
>>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in 
>> configure
>> self.do_options(options, parser, config_dict, not 
>> options.noprompt)
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in 
>> do_options
>> station = Vantage(**config_dict[DRIVER_NAME])
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in 
>> __init__
>> self._setup()
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in 
>> _setup
>> self.hardware_type = self._determine_hardware()
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in 
>> _determine_hardware
>> raise weewx.WeeWxIOError("Unable to read hardware type")
>> weewx.WeeWxIOError: Unable to read hardware type
>>
>>
>> On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:
>>
>>> *WeeWX generates HTML pages, but it does not update them 
>>> *
>>>
>>>
>>> On Sat, Mar 6, 2021 at 10:27 PM monmul  wrote:
>>>
 Even curiouserthe photo which is supposed to update every 20 
 minutes does updatebut not the weather data...still stuck on 
 21/2/2021

 www.wilsonbayweather.com

 On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:

> Mar  7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Getting archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Retry #0 failed
> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Rude wake up of console successful
> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement 
> from fe80::724f:57ff:feb7:82a1
> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 
> lease
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Retrieving 513 page(s); starting index= 0
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> DMPAFT complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) 
> less 
> than final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
> M

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[David Lee]

PuTTY (https://www.putty.org/), which is a free SSH/telnet client works on
Windows devices and can also connect to serial devices.

--
David

On Tue, Mar 9, 2021 at 5:15 PM monmul  wrote:

> Cool, thanks, will get on that with my laptop in the next day or
> sothank you!
>
> On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote:
>
>> Anything will do, no grunt needed, all you need is a terminal program of
>> some sort, minicom will do the job on anything Linux. Windows used to come
>> with some sort of terminal program. Not sure about a Mac. Certainly no need
>> to install WeeWX, you just want to run the connectivity test with your
>> Envoy(s) to prove it(they) respond(s).
>>
>> Gary
>>
>> On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote:
>>
>>> Hmmm! the only spare RPI I have at the moment is a 3A+ is that likely to
>>> have enough grunt to do the job? Oh! do you mean I could attach the "new"
>>> Envoy to a PC (running Ubuntu) and do the connectivity test?
>>>
>>>
>>> On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:
>>>
 Possibly, but if you are using the same RPi with the same cable as you
 have used with your new unresponsive Envoy then perhaps the issue is with
 the RPi or the cable. I would be looking for another RPi or PC (Windows
 (ugh), Mac or whatever) and run a terminal window/program and do the basic
 connectivity test (send ENTER and get a response from the Envoy). I would
 even try a different cable if you have another. Two different
 RPis/PCs/cables etc not working would be unusual. If that fails to get a
 response from your new Envoy then as Tom said it's time to get in touch
 with Davis or their agent.

 Gary

 On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:

> Is this telling me that my "old" Envoy is indeed broken?
>
> pi@WeatherPi:~ $ wee_device --clear-memory
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
> Unable to wake up console... sleeping
> Unable to wake up console... retrying
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_device", line 78, in 
> main()
>   File "/usr/share/weewx/wee_device", line 74, in main
> device.configure(config_dict)
>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in
> configure
> self.do_options(options, parser, config_dict, not options.noprompt)
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in
> do_options
> station = Vantage(**config_dict[DRIVER_NAME])
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in
> __init__
> self._setup()
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in
> _setup
> self.hardware_type = self._determine_hardware()
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in
> _determine_hardware
> raise weewx.WeeWxIOError("Unable to read hardware type")
> weewx.WeeWxIOError: Unable to read hardware type
>
>
> On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:
>
>> *WeeWX generates HTML pages, but it does not update them
>> *
>>
>>
>> On Sat, Mar 6, 2021 at 10:27 PM monmul  wrote:
>>
>>> Even curiouserthe photo which is supposed to update every 20
>>> minutes does updatebut not the weather data...still stuck on 
>>> 21/2/2021
>>>
>>> www.wilsonbayweather.com
>>>
>>> On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:
>>>
 Mar  7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
 Getting archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
 Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
 Retry #0 failed
 Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
 Rude wake up of console successful
 Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement
 from fe80::724f:57ff:feb7:82a1
 Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6
 lease
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
 Retrieving 513 page(s); starting index= 0
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
 DMPAFT complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) 
 less
 than final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
 Catch up complete.
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine:
 Running reports for latest time in the database.
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Cool, thanks, will get on that with my laptop in the next day or 
sothank you!

On Tuesday, 9 March 2021 at 19:37:16 UTC+13 gjr80 wrote:

> Anything will do, no grunt needed, all you need is a terminal program of 
> some sort, minicom will do the job on anything Linux. Windows used to come 
> with some sort of terminal program. Not sure about a Mac. Certainly no need 
> to install WeeWX, you just want to run the connectivity test with your 
> Envoy(s) to prove it(they) respond(s).
>
> Gary
>
> On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote:
>
>> Hmmm! the only spare RPI I have at the moment is a 3A+ is that likely to 
>> have enough grunt to do the job? Oh! do you mean I could attach the "new" 
>> Envoy to a PC (running Ubuntu) and do the connectivity test?
>>
>>
>> On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:
>>
>>> Possibly, but if you are using the same RPi with the same cable as you 
>>> have used with your new unresponsive Envoy then perhaps the issue is with 
>>> the RPi or the cable. I would be looking for another RPi or PC (Windows 
>>> (ugh), Mac or whatever) and run a terminal window/program and do the basic 
>>> connectivity test (send ENTER and get a response from the Envoy). I would 
>>> even try a different cable if you have another. Two different 
>>> RPis/PCs/cables etc not working would be unusual. If that fails to get a 
>>> response from your new Envoy then as Tom said it's time to get in touch 
>>> with Davis or their agent.
>>>
>>> Gary
>>>
>>> On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:
>>>
 Is this telling me that my "old" Envoy is indeed broken?

 pi@WeatherPi:~ $ wee_device --clear-memory
 Using configuration file /etc/weewx/weewx.conf
 Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
 Unable to wake up console... sleeping
 Unable to wake up console... retrying
 Traceback (most recent call last):
   File "/usr/share/weewx/wee_device", line 78, in 
 main()
   File "/usr/share/weewx/wee_device", line 74, in main
 device.configure(config_dict)
   File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in 
 configure
 self.do_options(options, parser, config_dict, not options.noprompt)
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in 
 do_options
 station = Vantage(**config_dict[DRIVER_NAME])
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in 
 __init__
 self._setup()
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in _setup
 self.hardware_type = self._determine_hardware()
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in 
 _determine_hardware
 raise weewx.WeeWxIOError("Unable to read hardware type")
 weewx.WeeWxIOError: Unable to read hardware type


 On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:

> *WeeWX generates HTML pages, but it does not update them 
> *
>
>
> On Sat, Mar 6, 2021 at 10:27 PM monmul  wrote:
>
>> Even curiouserthe photo which is supposed to update every 20 
>> minutes does updatebut not the weather data...still stuck on 
>> 21/2/2021
>>
>> www.wilsonbayweather.com
>>
>> On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:
>>
>>> Mar  7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>>> Getting archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
>>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>>> Retry #0 failed
>>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>>> Rude wake up of console successful
>>> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement 
>>> from fe80::724f:57ff:feb7:82a1
>>> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 
>>> lease
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>>> Retrieving 513 page(s); starting index= 0
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>>> DMPAFT complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) 
>>> less 
>>> than final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>>> Catch up complete.
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: 
>>> Running reports for latest time in the database.
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>>> Requesting 200 LOOP packets.
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: 
>>> Running report 'StandardReport'
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
>>> configurat

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

Anything will do, no grunt needed, all you need is a terminal program of 
some sort, minicom will do the job on anything Linux. Windows used to come 
with some sort of terminal program. Not sure about a Mac. Certainly no need 
to install WeeWX, you just want to run the connectivity test with your 
Envoy(s) to prove it(they) respond(s).

Gary

On Tuesday, 9 March 2021 at 16:30:25 UTC+10 monmul wrote:

> Hmmm! the only spare RPI I have at the moment is a 3A+ is that likely to 
> have enough grunt to do the job? Oh! do you mean I could attach the "new" 
> Envoy to a PC (running Ubuntu) and do the connectivity test?
>
>
> On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:
>
>> Possibly, but if you are using the same RPi with the same cable as you 
>> have used with your new unresponsive Envoy then perhaps the issue is with 
>> the RPi or the cable. I would be looking for another RPi or PC (Windows 
>> (ugh), Mac or whatever) and run a terminal window/program and do the basic 
>> connectivity test (send ENTER and get a response from the Envoy). I would 
>> even try a different cable if you have another. Two different 
>> RPis/PCs/cables etc not working would be unusual. If that fails to get a 
>> response from your new Envoy then as Tom said it's time to get in touch 
>> with Davis or their agent.
>>
>> Gary
>>
>> On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:
>>
>>> Is this telling me that my "old" Envoy is indeed broken?
>>>
>>> pi@WeatherPi:~ $ wee_device --clear-memory
>>> Using configuration file /etc/weewx/weewx.conf
>>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>>> Unable to wake up console... sleeping
>>> Unable to wake up console... retrying
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/wee_device", line 78, in 
>>> main()
>>>   File "/usr/share/weewx/wee_device", line 74, in main
>>> device.configure(config_dict)
>>>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in 
>>> configure
>>> self.do_options(options, parser, config_dict, not options.noprompt)
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in 
>>> do_options
>>> station = Vantage(**config_dict[DRIVER_NAME])
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
>>> self._setup()
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in _setup
>>> self.hardware_type = self._determine_hardware()
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in 
>>> _determine_hardware
>>> raise weewx.WeeWxIOError("Unable to read hardware type")
>>> weewx.WeeWxIOError: Unable to read hardware type
>>>
>>>
>>> On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:
>>>
 *WeeWX generates HTML pages, but it does not update them 
 *


 On Sat, Mar 6, 2021 at 10:27 PM monmul  wrote:

> Even curiouserthe photo which is supposed to update every 20 
> minutes does updatebut not the weather data...still stuck on 21/2/2021
>
> www.wilsonbayweather.com
>
> On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:
>
>> Mar  7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>> Getting archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>> Retry #0 failed
>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>> Rude wake up of console successful
>> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement 
>> from fe80::724f:57ff:feb7:82a1
>> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 
>> lease
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>> Retrieving 513 page(s); starting index= 0
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>> DMPAFT complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) 
>> less 
>> than final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>> Catch up complete.
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: 
>> Running reports for latest time in the database.
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>> Requesting 200 LOOP packets.
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: 
>> Running report 'StandardReport'
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
>> configuration file /etc/weewx/skins/Standard/skin.conf for report 
>> 'StandardReport'
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: 
>> Using search list ['weewx.cheetahgenerator.Almanac', 
>> 'weewx.cheetahgenerator.Station', 'weew

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Hmmm! the only spare RPI I have at the moment is a 3A+ is that likely to 
have enough grunt to do the job? Oh! do you mean I could attach the "new" 
Envoy to a PC (running Ubuntu) and do the connectivity test?


On Tuesday, 9 March 2021 at 18:47:15 UTC+13 gjr80 wrote:

> Possibly, but if you are using the same RPi with the same cable as you 
> have used with your new unresponsive Envoy then perhaps the issue is with 
> the RPi or the cable. I would be looking for another RPi or PC (Windows 
> (ugh), Mac or whatever) and run a terminal window/program and do the basic 
> connectivity test (send ENTER and get a response from the Envoy). I would 
> even try a different cable if you have another. Two different 
> RPis/PCs/cables etc not working would be unusual. If that fails to get a 
> response from your new Envoy then as Tom said it's time to get in touch 
> with Davis or their agent.
>
> Gary
>
> On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:
>
>> Is this telling me that my "old" Envoy is indeed broken?
>>
>> pi@WeatherPi:~ $ wee_device --clear-memory
>> Using configuration file /etc/weewx/weewx.conf
>> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
>> Unable to wake up console... sleeping
>> Unable to wake up console... retrying
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_device", line 78, in 
>> main()
>>   File "/usr/share/weewx/wee_device", line 74, in main
>> device.configure(config_dict)
>>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in configure
>> self.do_options(options, parser, config_dict, not options.noprompt)
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in 
>> do_options
>> station = Vantage(**config_dict[DRIVER_NAME])
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
>> self._setup()
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in _setup
>> self.hardware_type = self._determine_hardware()
>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in 
>> _determine_hardware
>> raise weewx.WeeWxIOError("Unable to read hardware type")
>> weewx.WeeWxIOError: Unable to read hardware type
>>
>>
>> On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:
>>
>>> *WeeWX generates HTML pages, but it does not update them 
>>> *
>>>
>>>
>>> On Sat, Mar 6, 2021 at 10:27 PM monmul  wrote:
>>>
 Even curiouserthe photo which is supposed to update every 20 
 minutes does updatebut not the weather data...still stuck on 21/2/2021

 www.wilsonbayweather.com

 On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:

> Mar  7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Getting archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Retry #0 failed
> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Rude 
> wake up of console successful
> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement 
> from fe80::724f:57ff:feb7:82a1
> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Retrieving 513 page(s); starting index= 0
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> DMPAFT complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) 
> less 
> than final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Catch up complete.
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
> reports for latest time in the database.
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Requesting 200 LOOP packets.
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
> report 'StandardReport'
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Standard/skin.conf for report 
> 'StandardReport'
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: 
> Using search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
> 'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics']
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Gentle wake up of console successful
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.manager: Daily 
> summary version is 4.0
> Mar  7 19:20:23 WeatherPi weewx[789] INFO weewx.cheetahgenerator: 
> Generated 15 files for report StandardRe

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

Possibly, but if you are using the same RPi with the same cable as you have 
used with your new unresponsive Envoy then perhaps the issue is with the 
RPi or the cable. I would be looking for another RPi or PC (Windows (ugh), 
Mac or whatever) and run a terminal window/program and do the basic 
connectivity test (send ENTER and get a response from the Envoy). I would 
even try a different cable if you have another. Two different 
RPis/PCs/cables etc not working would be unusual. If that fails to get a 
response from your new Envoy then as Tom said it's time to get in touch 
with Davis or their agent.

Gary

On Tuesday, 9 March 2021 at 15:36:38 UTC+10 monmul wrote:

> Is this telling me that my "old" Envoy is indeed broken?
>
> pi@WeatherPi:~ $ wee_device --clear-memory
> Using configuration file /etc/weewx/weewx.conf
> Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
> Unable to wake up console... sleeping
> Unable to wake up console... retrying
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_device", line 78, in 
> main()
>   File "/usr/share/weewx/wee_device", line 74, in main
> device.configure(config_dict)
>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in configure
> self.do_options(options, parser, config_dict, not options.noprompt)
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in 
> do_options
> station = Vantage(**config_dict[DRIVER_NAME])
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
> self._setup()
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in _setup
> self.hardware_type = self._determine_hardware()
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in 
> _determine_hardware
> raise weewx.WeeWxIOError("Unable to read hardware type")
> weewx.WeeWxIOError: Unable to read hardware type
>
>
> On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:
>
>> *WeeWX generates HTML pages, but it does not update them 
>> *
>>
>>
>> On Sat, Mar 6, 2021 at 10:27 PM monmul  wrote:
>>
>>> Even curiouserthe photo which is supposed to update every 20 minutes 
>>> does updatebut not the weather data...still stuck on 21/2/2021
>>>
>>> www.wilsonbayweather.com
>>>
>>> On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:
>>>
 Mar  7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
 Getting archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
 Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Retry 
 #0 failed
 Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Rude 
 wake up of console successful
 Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
 fe80::724f:57ff:feb7:82a1
 Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
 Retrieving 513 page(s); starting index= 0
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
 DMPAFT complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) less 
 than final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Catch 
 up complete.
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
 reports for latest time in the database.
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
 Requesting 200 LOOP packets.
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
 report 'StandardReport'
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
 configuration file /etc/weewx/skins/Standard/skin.conf for report 
 'StandardReport'
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: 
 Using search list ['weewx.cheetahgenerator.Almanac', 
 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
 'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics']
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
 Gentle wake up of console successful
 Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary 
 version is 4.0
 Mar  7 19:20:23 WeatherPi weewx[789] INFO weewx.cheetahgenerator: 
 Generated 15 files for report StandardReport in 2.42 seconds
 Mar  7 19:20:23 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary 
 version is 4.0
 Mar  7 19:20:24 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
 fe80::724f:57ff:feb7:82a1
 Mar  7 19:20:24 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
 Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.imagegenerator: 
 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Is this telling me that my "old" Envoy is indeed broken?

pi@WeatherPi:~ $ wee_device --clear-memory
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.2.1 (weewx.drivers.vantage)
Unable to wake up console... sleeping
Unable to wake up console... retrying
Traceback (most recent call last):
  File "/usr/share/weewx/wee_device", line 78, in 
main()
  File "/usr/share/weewx/wee_device", line 74, in main
device.configure(config_dict)
  File "/usr/share/weewx/weewx/drivers/__init__.py", line 67, in configure
self.do_options(options, parser, config_dict, not options.noprompt)
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 2056, in do_options
station = Vantage(**config_dict[DRIVER_NAME])
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
self._setup()
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1321, in _setup
self.hardware_type = self._determine_hardware()
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1312, in 
_determine_hardware
raise weewx.WeeWxIOError("Unable to read hardware type")
weewx.WeeWxIOError: Unable to read hardware type


On Monday, 8 March 2021 at 02:16:46 UTC+13 tke...@gmail.com wrote:

> *WeeWX generates HTML pages, but it does not update them 
> *
>
>
> On Sat, Mar 6, 2021 at 10:27 PM monmul  wrote:
>
>> Even curiouserthe photo which is supposed to update every 20 minutes 
>> does updatebut not the weather data...still stuck on 21/2/2021
>>
>> www.wilsonbayweather.com
>>
>> On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:
>>
>>> Mar  7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>>> Getting archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
>>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Retry 
>>> #0 failed
>>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Rude 
>>> wake up of console successful
>>> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
>>> fe80::724f:57ff:feb7:82a1
>>> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>>> Retrieving 513 page(s); starting index= 0
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: DMPAFT 
>>> complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) less than 
>>> final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Catch 
>>> up complete.
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
>>> reports for latest time in the database.
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
>>> Requesting 200 LOOP packets.
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
>>> report 'StandardReport'
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
>>> configuration file /etc/weewx/skins/Standard/skin.conf for report 
>>> 'StandardReport'
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: Using 
>>> search list ['weewx.cheetahgenerator.Almanac', 
>>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
>>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
>>> 'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics']
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Gentle 
>>> wake up of console successful
>>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary 
>>> version is 4.0
>>> Mar  7 19:20:23 WeatherPi weewx[789] INFO weewx.cheetahgenerator: 
>>> Generated 15 files for report StandardReport in 2.42 seconds
>>> Mar  7 19:20:23 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary 
>>> version is 4.0
>>> Mar  7 19:20:24 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
>>> fe80::724f:57ff:feb7:82a1
>>> Mar  7 19:20:24 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>>> Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.imagegenerator: 
>>> Generated 24 images for report StandardReport in 5.17 seconds
>>> Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.reportengine: Copied 0 
>>> files to /var/www/html/weewx
>>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
>>> report 'xstats'
>>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
>>> configuration file /etc/weewx/skins/xstats/skin.conf for report 'xstats'
>>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: Using 
>>> search list ['weewx.cheetahgenerator.Almanac', 
>>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
>>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
>>> 'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics']
>>> Mar  7 19:20:28 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

*WeeWX generates HTML pages, but it does not update them
*


On Sat, Mar 6, 2021 at 10:27 PM monmul  wrote:

> Even curiouserthe photo which is supposed to update every 20 minutes
> does updatebut not the weather data...still stuck on 21/2/2021
>
> www.wilsonbayweather.com
>
> On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:
>
>> Mar  7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Getting
>> archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Retry
>> #0 failed
>> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Rude
>> wake up of console successful
>> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from
>> fe80::724f:57ff:feb7:82a1
>> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>> Retrieving 513 page(s); starting index= 0
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: DMPAFT
>> complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) less than
>> final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Catch
>> up complete.
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running
>> reports for latest time in the database.
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage:
>> Requesting 200 LOOP packets.
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running
>> report 'StandardReport'
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Found
>> configuration file /etc/weewx/skins/Standard/skin.conf for report
>> 'StandardReport'
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: Using
>> search list ['weewx.cheetahgenerator.Almanac',
>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
>> 'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics']
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Gentle
>> wake up of console successful
>> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary
>> version is 4.0
>> Mar  7 19:20:23 WeatherPi weewx[789] INFO weewx.cheetahgenerator:
>> Generated 15 files for report StandardReport in 2.42 seconds
>> Mar  7 19:20:23 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary
>> version is 4.0
>> Mar  7 19:20:24 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from
>> fe80::724f:57ff:feb7:82a1
>> Mar  7 19:20:24 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>> Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.imagegenerator: Generated
>> 24 images for report StandardReport in 5.17 seconds
>> Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.reportengine: Copied 0
>> files to /var/www/html/weewx
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Running
>> report 'xstats'
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Found
>> configuration file /etc/weewx/skins/xstats/skin.conf for report 'xstats'
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: Using
>> search list ['weewx.cheetahgenerator.Almanac',
>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
>> 'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics']
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary
>> version is 4.0
>> Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.cheetahgenerator:
>> Generated 1 files for report xstats in 0.08 seconds
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report
>> 'SeasonsReport' not enabled. Skipping.
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report
>> 'SmartphoneReport' not enabled. Skipping.
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report
>> 'MobileReport' not enabled. Skipping.
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Running
>> report 'FTP'
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Found
>> configuration file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Attempting
>> connection to 43.245.53.39
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Connected
>> to 43.245.53.39
>> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded
>> file /var/www/html/weewx/dayradiation.png to /public_html/dayradiation.png
>> Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded
>> file /var/www/html/weewx/index.html to /public_html/index.html
>> Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpuplo

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Even curiouserthe photo which is supposed to update every 20 minutes 
does updatebut not the weather data...still stuck on 21/2/2021

www.wilsonbayweather.com

On Sunday, 7 March 2021 at 19:25:07 UTC+13 monmul wrote:

> Mar  7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Getting 
> archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Retry #0 
> failed
> Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Rude 
> wake up of console successful
> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Retrieving 513 page(s); starting index= 0
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: DMPAFT 
> complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) less than 
> final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Catch up 
> complete.
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
> reports for latest time in the database.
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
> Requesting 200 LOOP packets.
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
> report 'StandardReport'
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Standard/skin.conf for report 
> 'StandardReport'
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: Using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
> 'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics']
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Gentle 
> wake up of console successful
> Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary 
> version is 4.0
> Mar  7 19:20:23 WeatherPi weewx[789] INFO weewx.cheetahgenerator: 
> Generated 15 files for report StandardReport in 2.42 seconds
> Mar  7 19:20:23 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary 
> version is 4.0
> Mar  7 19:20:24 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Mar  7 19:20:24 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
> Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.imagegenerator: Generated 
> 24 images for report StandardReport in 5.17 seconds
> Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.reportengine: Copied 0 
> files to /var/www/html/weewx
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
> report 'xstats'
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/xstats/skin.conf for report 'xstats'
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: Using 
> search list ['weewx.cheetahgenerator.Almanac', 
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
> 'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics']
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary 
> version is 4.0
> Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.cheetahgenerator: 
> Generated 1 files for report xstats in 0.08 seconds
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report 
> 'SeasonsReport' not enabled. Skipping.
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report 
> 'SmartphoneReport' not enabled. Skipping.
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report 
> 'MobileReport' not enabled. Skipping.
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
> report 'FTP'
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
> configuration file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Attempting 
> connection to 43.245.53.39
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Connected to 
> 43.245.53.39
> Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded 
> file /var/www/html/weewx/dayradiation.png to /public_html/dayradiation.png
> Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded 
> file /var/www/html/weewx/index.html to /public_html/index.html
> Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded 
> file /var/www/html/weewx/weekrain.png to /public_html/weekrain.png
> Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded 
> file /var/www/html/weewx/weekwind.png to /public_html/weekwind.png
> Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload:

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Mar  7 19:20:15 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Getting 
archive packets since 2021-02-21 08:00:00 NZDT (1613847600)
Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Retry #0 
failed
Mar  7 19:20:18 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Rude wake 
up of console successful
Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 19:20:19 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
Retrieving 513 page(s); starting index= 0
Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: DMPAFT 
complete: page timestamp 2021-02-04 02:10:00 NZDT (1612357800) less than 
final timestamp 2021-02-21 08:00:00 NZDT (1613847600)
Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Catch up 
complete.
Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: 
Requesting 200 LOOP packets.
Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
report 'StandardReport'
Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Standard/skin.conf for report 
'StandardReport'
Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics']
Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.drivers.vantage: Gentle 
wake up of console successful
Mar  7 19:20:20 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary 
version is 4.0
Mar  7 19:20:23 WeatherPi weewx[789] INFO weewx.cheetahgenerator: Generated 
15 files for report StandardReport in 2.42 seconds
Mar  7 19:20:23 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary 
version is 4.0
Mar  7 19:20:24 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 19:20:24 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.imagegenerator: Generated 
24 images for report StandardReport in 5.17 seconds
Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
report 'xstats'
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/xstats/skin.conf for report 'xstats'
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.cheetahgenerator: Using 
search list ['weewx.cheetahgenerator.Almanac', 
'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 
'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 
'weewx.cheetahgenerator.Extras', u'user.xstats.ExtendedStatistics']
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.manager: Daily summary 
version is 4.0
Mar  7 19:20:28 WeatherPi weewx[789] INFO weewx.cheetahgenerator: Generated 
1 files for report xstats in 0.08 seconds
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report 
'SeasonsReport' not enabled. Skipping.
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report 
'SmartphoneReport' not enabled. Skipping.
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Report 
'MobileReport' not enabled. Skipping.
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Running 
report 'FTP'
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weewx.reportengine: Found 
configuration file /etc/weewx/skins/Ftp/skin.conf for report 'FTP'
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Attempting 
connection to 43.245.53.39
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Connected to 
43.245.53.39
Mar  7 19:20:28 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded file 
/var/www/html/weewx/dayradiation.png to /public_html/dayradiation.png
Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded file 
/var/www/html/weewx/index.html to /public_html/index.html
Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded file 
/var/www/html/weewx/weekrain.png to /public_html/weekrain.png
Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded file 
/var/www/html/weewx/weekwind.png to /public_html/weekwind.png
Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded file 
/var/www/html/weewx/weekradiation.png to /public_html/weekradiation.png
Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded file 
/var/www/html/weewx/dayrain.png to /public_html/dayrain.png
Mar  7 19:20:29 WeatherPi weewx[789] DEBUG weeutil.ftpupload: Uploaded file 
/var/www/html/weewx/weekwinddir.png to /public_html/weekwinddir.png
Mar  7 19:20:30 We

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Weather Underground also not updating and showing station as 
offline.Hmmm!

On Sunday, 7 March 2021 at 19:17:32 UTC+13 monmul wrote:

> Hmmm! while it appears to be working with the "old" Envoy (if my reading 
> of the log is correct)..the website is not updatingso I am 
> wondering if any data is getting through!
>
> On Sunday, 7 March 2021 at 18:45:08 UTC+13 monmul wrote:
>
>> OK, so I decided to put the "old" Envoy back on the one that seemed 
>> to be causing the tripping of the fuse (the fuse has not tripped since I 
>> took this "old" Envoy out...It now looks as if the "old" Envoy is 
>> working..is that what this log  is saying? Weird or what?
>>
>>
>> Mar  7 18:33:48 WeatherPi systemd[1]: Time has been changed
>> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
>> 0xe3eea886.b0043efc does not match aorg 00. from 
>> ser...@103.106.65.219 xmt 0xe3eee43c.47439f60
>> Mar  7 18:33:48 WeatherPi systemd[1]: apt-daily-upgrade.timer: Adding 
>> 22min 56.174539s random time.
>> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
>> 0xe3eea886.bab7752e does not match aorg 00. from 
>> ser...@103.242.70.4 xmt 0xe3eee43c.4df29247
>> Mar  7 18:33:48 WeatherPi systemd[866]: Time has been changed
>> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
>> 0xe3eea886.babc71d5 does not match aorg 00. from 
>> ser...@203.99.128.48 xmt 0xe3eee43c.4e0fc836
>> Mar  7 18:33:48 WeatherPi systemd[1]: apt-daily.timer: Adding 9h 58min 
>> 38.719051s random time.
>> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
>> 0xe3eea886.babae406 does not match aorg 00. from 
>> ser...@103.239.8.21 xmt 0xe3eee43c.4d91500b
>> Mar  7 18:33:48 WeatherPi systemd[1]: anacron.timer: Adding 2min 
>> 39.415226s random time.
>> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
>> 0xe3eea886.bab509f8 does not match aorg 00. from 
>> ser...@202.46.185.18 xmt 0xe3eee43c.4ef41ef6
>> Mar  7 18:33:48 WeatherPi systemd[1]: Started Run anacron jobs.
>> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
>> 0xe3eea886.bab93b56 does not match aorg 00. from 
>> ser...@162.159.200.1 xmt 0xe3eee43c.4fa4370e
>> Mar  7 18:33:48 WeatherPi anacron[1474]: Anacron 2.3 started on 2021-03-07
>> Mar  7 18:33:48 WeatherPi anacron[1474]: Normal exit (0 jobs run)
>> Mar  7 18:33:48 WeatherPi systemd[1]: anacron.timer: Adding 4min 
>> 53.491534s random time.
>> Mar  7 18:33:49 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP 
>> try #1; error: Expected to read 99 chars; got 14 instead
>> Mar  7 18:33:50 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Mar  7 18:33:50 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>> Mar  7 18:33:51 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP 
>> try #2; error: LOOP buffer failed CRC check
>> Mar  7 18:33:53 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP 
>> try #3; error: LOOP buffer failed CRC check
>> Mar  7 18:33:55 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP 
>> try #4; error: LOOP buffer failed CRC check
>> Mar  7 18:33:55 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP 
>> max tries (4) exceeded.
>> Mar  7 18:33:55 WeatherPi weewx[789] INFO weewx.engine: Main loop 
>> exiting. Shutting engine down.
>> Mar  7 18:33:55 WeatherPi weewx[789] DEBUG weewx.restx: Shut down 
>> Wunderground-PWS thread.
>> Mar  7 18:33:55 WeatherPi weewx[789] CRITICAL __main__: Caught 
>> WeeWxIOError: Max tries exceeded while getting LOOP data.
>> Mar  7 18:33:55 WeatherPi weewx[789] CRITICAL __main__:   Waiting 
>> 60 seconds then retrying...
>> Mar  7 18:33:59 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Mar  7 18:33:59 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>> Mar  7 18:34:04 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Mar  7 18:34:04 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>> Mar  7 18:34:09 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Mar  7 18:34:09 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>> Mar  7 18:34:14 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Mar  7 18:34:14 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>> Mar  7 18:34:20 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Mar  7 18:34:20 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>> Mar  7 18:34:26 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Mar  7 18:34:26 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
>> Mar  7 18:34:34 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Hmmm! while it appears to be working with the "old" Envoy (if my reading of 
the log is correct)..the website is not updatingso I am wondering 
if any data is getting through!

On Sunday, 7 March 2021 at 18:45:08 UTC+13 monmul wrote:

> OK, so I decided to put the "old" Envoy back on the one that seemed to 
> be causing the tripping of the fuse (the fuse has not tripped since I took 
> this "old" Envoy out...It now looks as if the "old" Envoy is 
> working..is that what this log  is saying? Weird or what?
>
>
> Mar  7 18:33:48 WeatherPi systemd[1]: Time has been changed
> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
> 0xe3eea886.b0043efc does not match aorg 00. from 
> ser...@103.106.65.219 xmt 0xe3eee43c.47439f60
> Mar  7 18:33:48 WeatherPi systemd[1]: apt-daily-upgrade.timer: Adding 
> 22min 56.174539s random time.
> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
> 0xe3eea886.bab7752e does not match aorg 00. from 
> ser...@103.242.70.4 xmt 0xe3eee43c.4df29247
> Mar  7 18:33:48 WeatherPi systemd[866]: Time has been changed
> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
> 0xe3eea886.babc71d5 does not match aorg 00. from 
> ser...@203.99.128.48 xmt 0xe3eee43c.4e0fc836
> Mar  7 18:33:48 WeatherPi systemd[1]: apt-daily.timer: Adding 9h 58min 
> 38.719051s random time.
> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
> 0xe3eea886.babae406 does not match aorg 00. from 
> ser...@103.239.8.21 xmt 0xe3eee43c.4d91500b
> Mar  7 18:33:48 WeatherPi systemd[1]: anacron.timer: Adding 2min 
> 39.415226s random time.
> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
> 0xe3eea886.bab509f8 does not match aorg 00. from 
> ser...@202.46.185.18 xmt 0xe3eee43c.4ef41ef6
> Mar  7 18:33:48 WeatherPi systemd[1]: Started Run anacron jobs.
> Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
> 0xe3eea886.bab93b56 does not match aorg 00. from 
> ser...@162.159.200.1 xmt 0xe3eee43c.4fa4370e
> Mar  7 18:33:48 WeatherPi anacron[1474]: Anacron 2.3 started on 2021-03-07
> Mar  7 18:33:48 WeatherPi anacron[1474]: Normal exit (0 jobs run)
> Mar  7 18:33:48 WeatherPi systemd[1]: anacron.timer: Adding 4min 
> 53.491534s random time.
> Mar  7 18:33:49 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try 
> #1; error: Expected to read 99 chars; got 14 instead
> Mar  7 18:33:50 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Mar  7 18:33:50 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
> Mar  7 18:33:51 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try 
> #2; error: LOOP buffer failed CRC check
> Mar  7 18:33:53 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try 
> #3; error: LOOP buffer failed CRC check
> Mar  7 18:33:55 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try 
> #4; error: LOOP buffer failed CRC check
> Mar  7 18:33:55 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP max 
> tries (4) exceeded.
> Mar  7 18:33:55 WeatherPi weewx[789] INFO weewx.engine: Main loop exiting. 
> Shutting engine down.
> Mar  7 18:33:55 WeatherPi weewx[789] DEBUG weewx.restx: Shut down 
> Wunderground-PWS thread.
> Mar  7 18:33:55 WeatherPi weewx[789] CRITICAL __main__: Caught 
> WeeWxIOError: Max tries exceeded while getting LOOP data.
> Mar  7 18:33:55 WeatherPi weewx[789] CRITICAL __main__:   Waiting 
> 60 seconds then retrying...
> Mar  7 18:33:59 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Mar  7 18:33:59 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
> Mar  7 18:34:04 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Mar  7 18:34:04 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
> Mar  7 18:34:09 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Mar  7 18:34:09 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
> Mar  7 18:34:14 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Mar  7 18:34:14 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
> Mar  7 18:34:20 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Mar  7 18:34:20 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
> Mar  7 18:34:26 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Mar  7 18:34:26 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
> Mar  7 18:34:34 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Mar  7 18:34:34 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
> Mar  7 18:34:44 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Mar  7 18:34:44 WeatherPi dhcpcd[361]:

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

OK, so I decided to put the "old" Envoy back on the one that seemed to 
be causing the tripping of the fuse (the fuse has not tripped since I took 
this "old" Envoy out...It now looks as if the "old" Envoy is 
working..is that what this log  is saying? Weird or what?


Mar  7 18:33:48 WeatherPi systemd[1]: Time has been changed
Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
0xe3eea886.b0043efc does not match aorg 00. from 
server@103.106.65.219 xmt 0xe3eee43c.47439f60
Mar  7 18:33:48 WeatherPi systemd[1]: apt-daily-upgrade.timer: Adding 22min 
56.174539s random time.
Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
0xe3eea886.bab7752e does not match aorg 00. from 
server@103.242.70.4 xmt 0xe3eee43c.4df29247
Mar  7 18:33:48 WeatherPi systemd[866]: Time has been changed
Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
0xe3eea886.babc71d5 does not match aorg 00. from 
server@203.99.128.48 xmt 0xe3eee43c.4e0fc836
Mar  7 18:33:48 WeatherPi systemd[1]: apt-daily.timer: Adding 9h 58min 
38.719051s random time.
Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
0xe3eea886.babae406 does not match aorg 00. from 
server@103.239.8.21 xmt 0xe3eee43c.4d91500b
Mar  7 18:33:48 WeatherPi systemd[1]: anacron.timer: Adding 2min 39.415226s 
random time.
Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
0xe3eea886.bab509f8 does not match aorg 00. from 
server@202.46.185.18 xmt 0xe3eee43c.4ef41ef6
Mar  7 18:33:48 WeatherPi systemd[1]: Started Run anacron jobs.
Mar  7 18:33:48 WeatherPi ntpd[519]: receive: Unexpected origin timestamp 
0xe3eea886.bab93b56 does not match aorg 00. from 
server@162.159.200.1 xmt 0xe3eee43c.4fa4370e
Mar  7 18:33:48 WeatherPi anacron[1474]: Anacron 2.3 started on 2021-03-07
Mar  7 18:33:48 WeatherPi anacron[1474]: Normal exit (0 jobs run)
Mar  7 18:33:48 WeatherPi systemd[1]: anacron.timer: Adding 4min 53.491534s 
random time.
Mar  7 18:33:49 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try 
#1; error: Expected to read 99 chars; got 14 instead
Mar  7 18:33:50 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 18:33:50 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 18:33:51 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try 
#2; error: LOOP buffer failed CRC check
Mar  7 18:33:53 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try 
#3; error: LOOP buffer failed CRC check
Mar  7 18:33:55 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP try 
#4; error: LOOP buffer failed CRC check
Mar  7 18:33:55 WeatherPi weewx[789] ERROR weewx.drivers.vantage: LOOP max 
tries (4) exceeded.
Mar  7 18:33:55 WeatherPi weewx[789] INFO weewx.engine: Main loop exiting. 
Shutting engine down.
Mar  7 18:33:55 WeatherPi weewx[789] DEBUG weewx.restx: Shut down 
Wunderground-PWS thread.
Mar  7 18:33:55 WeatherPi weewx[789] CRITICAL __main__: Caught 
WeeWxIOError: Max tries exceeded while getting LOOP data.
Mar  7 18:33:55 WeatherPi weewx[789] CRITICAL __main__:   Waiting 
60 seconds then retrying...
Mar  7 18:33:59 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 18:33:59 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 18:34:04 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 18:34:04 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 18:34:09 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 18:34:09 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 18:34:14 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 18:34:14 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 18:34:20 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 18:34:20 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 18:34:26 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 18:34:26 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 18:34:34 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 18:34:34 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 18:34:44 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 18:34:44 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 18:34:50 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 18:34:50 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 18:34:54 WeatherPi dhcpcd[361]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Mar  7 18:34:54 WeatherPi dhcpcd[361]: wlan0: soliciting a DHCPv6 lease
Mar  7 18:34:55 WeatherPi wee

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

Nothing that we haven't seen before: your RPi cannot connect with the
logger.

On Fri, Mar 5, 2021 at 7:18 PM monmul  wrote:

> Thanks for that, I will get around to setting up another Pi in a few days.
> In the meantime, does this give us any useful information
>
> Mar  6 12:53:29 WeatherPi weewx[870] INFO __main__: Using configuration
> file /etc/weewx/weewx.conf
> Mar  6 12:53:29 WeatherPi weewx[870] INFO __main__: Debug is 1
> Mar  6 12:53:29 WeatherPi weewx[870] DEBUG __main__: Initializing engine
> Mar  6 12:53:29 WeatherPi weewx[870] INFO weewx.engine: Loading station
> type Vantage (weewx.drivers.vantage)
> Mar  6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Driver
> version is 3.2.1
> Mar  6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Option
> loop_request=1
> Mar  6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Opened
> up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
> Mar  6 12:53:30 WeatherPi lightdm[918]: Error getting user list from
> org.freedesktop.Accounts:
> GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.Accounts was not provided by any .service files
> Mar  6 12:53:33 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #0
> failed
> Mar  6 12:53:37 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #1
> failed
> Mar  6 12:53:41 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #2
> failed
> Mar  6 12:53:43 WeatherPi vncserver-x11[515,root]: ServerManager: Server
> started
> Mar  6 12:53:44 WeatherPi vncserver-x11[515,root]: ConsoleDisplay: Found
> running X server (pid=789, binary=/usr/lib/xorg/Xorg)
> Mar  6 12:53:45 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #3
> failed
> Mar  6 12:53:45 WeatherPi weewx[870] ERROR weewx.drivers.vantage: Unable
> to wake up console
> Mar  6 12:53:45 WeatherPi weewx[870] ERROR weewx.engine: Import of driver
> failed: Unable to wake up Vantage console ()
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> Traceback (most recent call last):
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> self.console = loader_function(config_dict, self)
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> return VantageService(engine, config_dict)
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> self._setup()
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> self.port.wakeup_console(max_tries=self.max_tries)
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in
> wakeup_console
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> raise weewx.WakeupError("Unable to wake up Vantage console")
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
> WakeupError: Unable to wake up Vantage console
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL __main__: Unable to load
> driver: Unable to wake up Vantage console
> Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL __main__: 
> Exiting...
> Mar  6 13:53:57 WeatherPi vncserver-x11[515,root]: Connections: connected:
> 10.1.1.155::58448 (TCP)
> Mar  6 13:53:57 WeatherPi vncserver-x11[515,root]: Connections:
> authenticated: 10.1.1.155::58448 (TCP), as (anonymous) (d permissions)
> Mar  6 13:53:57 WeatherPi vncserver-x11[515,root]: SPrintConnMgr: Failed
> to add printer: server-error-service-unavailable
> Mar  6 15:00:14 WeatherPi vncserver-x11[515,root]: Connections:
> disconnected: 10.1.1.155::58448 (TCP) ([IdleTimeout] This connection has
> timed out through inactivity.)
> Mar  6 15:49:17 WeatherPi vncserver-x11[515,root]: Connections: connected:
> 10.1.1.155::35098 (TCP)
> Mar  6 15:49:17 WeatherPi vncser
>
> On Saturday, 6 March 2021 at 14:23:11 UTC+13 tke...@gmail.com wrote:
>
>> Yes, you definitely have a connectivity problem that has nothing to do
>> with WeeWX. There is an outside chance the problem is with your RPi. If you
>> have an extra RPi around, try using it to connect through minicom.
>>
>> If nothing works, a call to Davis is in order.
>>
>> -tk
>>
>> O

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Thanks for that, I will get around to setting up another Pi in a few days. 
In the meantime, does this give us any useful information

Mar  6 12:53:29 WeatherPi weewx[870] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Mar  6 12:53:29 WeatherPi weewx[870] INFO __main__: Debug is 1
Mar  6 12:53:29 WeatherPi weewx[870] DEBUG __main__: Initializing engine
Mar  6 12:53:29 WeatherPi weewx[870] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
Mar  6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Driver 
version is 3.2.1
Mar  6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Option 
loop_request=1
Mar  6 12:53:29 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Opened up 
serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Mar  6 12:53:30 WeatherPi lightdm[918]: Error getting user list from 
org.freedesktop.Accounts: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.Accounts was not provided by any .service files
Mar  6 12:53:33 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #0 
failed
Mar  6 12:53:37 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #1 
failed
Mar  6 12:53:41 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #2 
failed
Mar  6 12:53:43 WeatherPi vncserver-x11[515,root]: ServerManager: Server 
started
Mar  6 12:53:44 WeatherPi vncserver-x11[515,root]: ConsoleDisplay: Found 
running X server (pid=789, binary=/usr/lib/xorg/Xorg)
Mar  6 12:53:45 WeatherPi weewx[870] DEBUG weewx.drivers.vantage: Retry #3 
failed
Mar  6 12:53:45 WeatherPi weewx[870] ERROR weewx.drivers.vantage: Unable to 
wake up console
Mar  6 12:53:45 WeatherPi weewx[870] ERROR weewx.engine: Import of driver 
failed: Unable to wake up Vantage console ()
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:   
Traceback (most recent call last):
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:   
self.console = loader_function(config_dict, self)
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:   
return VantageService(engine, config_dict)
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:   
Vantage.__init__(self, **config_dict[DRIVER_NAME])
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:   
self._setup()
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:   
self.port.wakeup_console(max_tries=self.max_tries)
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in 
wakeup_console
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:   
raise weewx.WakeupError("Unable to wake up Vantage console")
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL weewx.engine:   
WakeupError: Unable to wake up Vantage console
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL __main__: Unable to load 
driver: Unable to wake up Vantage console
Mar  6 12:53:45 WeatherPi weewx[870] CRITICAL __main__:   Exiting...
Mar  6 13:53:57 WeatherPi vncserver-x11[515,root]: Connections: connected: 
10.1.1.155::58448 (TCP)
Mar  6 13:53:57 WeatherPi vncserver-x11[515,root]: Connections: 
authenticated: 10.1.1.155::58448 (TCP), as (anonymous) (d permissions)
Mar  6 13:53:57 WeatherPi vncserver-x11[515,root]: SPrintConnMgr: Failed to 
add printer: server-error-service-unavailable
Mar  6 15:00:14 WeatherPi vncserver-x11[515,root]: Connections: 
disconnected: 10.1.1.155::58448 (TCP) ([IdleTimeout] This connection has 
timed out through inactivity.)
Mar  6 15:49:17 WeatherPi vncserver-x11[515,root]: Connections: connected: 
10.1.1.155::35098 (TCP)
Mar  6 15:49:17 WeatherPi vncser

On Saturday, 6 March 2021 at 14:23:11 UTC+13 tke...@gmail.com wrote:

> Yes, you definitely have a connectivity problem that has nothing to do 
> with WeeWX. There is an outside chance the problem is with your RPi. If you 
> have an extra RPi around, try using it to connect through minicom.
>
> If nothing works, a call to Davis is in order.
>
> -tk
>
> On Fri, Mar 5, 2021 at 5:00 PM monmul  wrote:
>
>>
>> So everything reseated and restarted...unplugged USB to ensure that the 
>> Pi was seeing the USB..used "screen /dev/ttyUSB0 19200" after shutting 
>

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

Yes, you definitely have a connectivity problem that has nothing to do with
WeeWX. There is an outside chance the problem is with your RPi. If you have
an extra RPi around, try using it to connect through minicom.

If nothing works, a call to Davis is in order.

-tk

On Fri, Mar 5, 2021 at 5:00 PM monmul  wrote:

>
> So everything reseated and restarted...unplugged USB to ensure that the Pi
> was seeing the USB..used "screen /dev/ttyUSB0 19200" after shutting
> down weewxstill blank screen (after a number Enters) with no echo back
> to TEST and NVR
> On Friday, 5 March 2021 at 17:29:45 UTC+13 monmul wrote:
>
>> pi@WeatherPi:~ $ lsusb
>> Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash
>> drive
>> Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
>> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
>> SMSC9512/9514 Fast Ethernet Adapter
>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> pi@WeatherPi:~ $
>>
>> Having pulled out the line from the Envoy, rebooted, and hit lsusb, by
>> elimination the "Future Technology" must be the one!
>>
>> On Friday, 5 March 2021 at 15:38:45 UTC+13 graha...@gmail.com wrote:
>>
>>> or just note which /dev/ttyUSB* comes and goes
>>>
>>> once identified i like to put in a udev rule to create a known device
>>> file such as /dev/vp2
>>>
>>> > On 5 Mar 2021, at 12:33 pm, vince  wrote:
>>> >
>>> > One good way to identify a USB device is to unplug it, plug it back
>>> in, and see what the 'dmesg' command reported. You'll tend to be able to
>>> figure out which USB port it connected to that 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/52535b0d-df10-4281-a5e8-420e8b84a701n%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/CAPq0zEBO_TsbZwmPeHGFFG-R%3DQ1ZWHV2k3RYv8B_fKY-btfbaQ%40mail.gmail.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

So everything reseated and restarted...unplugged USB to ensure that the Pi 
was seeing the USB..used "screen /dev/ttyUSB0 19200" after shutting 
down weewxstill blank screen (after a number Enters) with no echo back 
to TEST and NVR
On Friday, 5 March 2021 at 17:29:45 UTC+13 monmul wrote:

> pi@WeatherPi:~ $ lsusb
> Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash 
> drive
> Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
> Fast Ethernet Adapter
> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> pi@WeatherPi:~ $ 
>
> Having pulled out the line from the Envoy, rebooted, and hit lsusb, by 
> elimination the "Future Technology" must be the one!
>
> On Friday, 5 March 2021 at 15:38:45 UTC+13 graha...@gmail.com wrote:
>
>> or just note which /dev/ttyUSB* comes and goes
>>
>> once identified i like to put in a udev rule to create a known device 
>> file such as /dev/vp2
>>
>> > On 5 Mar 2021, at 12:33 pm, vince  wrote:
>> > 
>> > One good way to identify a USB device is to unplug it, plug it back in, 
>> and see what the 'dmesg' command reported. You'll tend to be able to figure 
>> out which USB port it connected to that 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/52535b0d-df10-4281-a5e8-420e8b84a701n%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

pi@WeatherPi:~ $ lsusb
Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash 
drive
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@WeatherPi:~ $ 

Having pulled out the line from the Envoy, rebooted, and hit lsusb, by 
elimination the "Future Technology" must be the one!

On Friday, 5 March 2021 at 15:38:45 UTC+13 graha...@gmail.com wrote:

> or just note which /dev/ttyUSB* comes and goes
>
> once identified i like to put in a udev rule to create a known device file 
> such as /dev/vp2
>
> > On 5 Mar 2021, at 12:33 pm, vince  wrote:
> > 
> > One good way to identify a USB device is to unplug it, plug it back in, 
> and see what the 'dmesg' command reported. You'll tend to be able to figure 
> out which USB port it connected to that 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/f7d99875-d320-48d0-96bf-678f06efb18dn%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Graham Eddy]

or just note which /dev/ttyUSB* comes and goes

once identified i like to put in a udev rule to create a known device file such 
as /dev/vp2

> On 5 Mar 2021, at 12:33 pm, vince  wrote:
> 
> One good way to identify a USB device is to unplug it, plug it back in, and 
> see what the 'dmesg' command reported.You'll tend to be able to figure 
> out which USB port it connected to that 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/00A833D2-4689-4DF1-916D-5B7A88CA5EF8%40gmail.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[vince]

One good way to identify a USB device is to unplug it, plug it back in, and 
see what the 'dmesg' command reported.You'll tend to be able to figure 
out which USB port it connected to that 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/8ab62c82-a65c-49f4-9881-12604802cfban%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

The device "Future Technologies" is probably your Envoy.

On Thu, Mar 4, 2021 at 1:35 PM monmul  wrote:

> Not using serial...using USB.
>
> On Friday, 5 March 2021 at 10:34:32 UTC+13 monmul wrote:
>
>> pi@WeatherPi:~ $ lsusb
>> Bus 001 Device 006: ID 0403:6001 Future Technology Devices International,
>> Ltd FT232 Serial (UART) IC
>> Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash
>> drive
>> Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
>> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
>> SMSC9512/9514 Fast Ethernet Adapter
>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> pi@WeatherPi:~ $
>>
>>
>> On Friday, 5 March 2021 at 09:05:34 UTC+13 tke...@gmail.com wrote:
>>
>>> Well, if you're sure you have the right port (/dev/ttyUSB0), and you
>>> have correctly completed the test (a couple of enters, followed by ENTER,
>>> all caps) and you got nothing back, then that is as definitive a test that
>>> I know of that you have a connectivity problem.
>>>
>>> Do you have a USB version of the logger? Or, if you have a serial
>>> version, are you using a serial-to-usb converter? Either way, make sure
>>> your computer is recognizing the USB connection to the logger:
>>>
>>> *lsusb*
>>>
>>> If you have a serial version of the logger (very rare these days), then
>>> what serial port are you plugging it into?
>>>
>>>
>>>
>>> On Thu, Mar 4, 2021 at 11:59 AM monmul  wrote:
>>>
 Yes, apologieswas in a rush typing and did not review."new
 envoy"..it should be...and "initiation" is the other typo!

 On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote:

> ‘new’ envoy?
>
> Gary
>
> On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:
>
>> What do you mean by "net Envoy"? If you are using a serial port like
>> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a
>> network connector. Or, are you using an IP logger?
>>
>> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>>
>>> I have not had time to do the reseating yethopefully later
>>> today. One thing strikes me (probably becuase it has been so long since 
>>> I
>>> set it up) I just switched envoys, how does the net envoy know what to
>>> do...I have not gone to any itiation or set up page etcI just 
>>> plugged
>>> and supposed it would go. Am I missing something?
>>>
>>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>>>
 Thank you, I will give that a try!

 On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:

> Reseat means to remove the logger from the Envoy and then
> reinstall the logger in the Envoy. Sometimes you can get a dodgy 
> connection
> between pins on the logger and the socket in the Envoy (or console) 
> and
> remaking the connection by reseating can sometimes fix this.
>
> Gary
>
> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:
>
>> Sorry, I don't quite understand what you mean by "reseat"?
>>
>> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com
>> wrote:
>>
>>> You can try reseating the logger.
>>>
>>> On Sat, Feb 27, 2021 at 5:16 PM monmul 
>>> wrote:
>>>
 Neither TEST nor NVER returns anythingso, I guess I have a
 connectivity problemwhich seems strange as  I did a straight 
 swap out
 of the Envoys!

 On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com
 wrote:

> If the cursor went down the screen, then the console is
> sending something back. Make sure you press  a few times, 
> then
> "TEST", all in capital letters.
>
> You can also type "NVER". Again, all in capital letters. This
> will return the firmware version number.
>
> If neither of those work, then you have a connectivity problem.
>
>
> On Sat, Feb 27, 2021 at 3:54 PM monmul 
> wrote:
>
>> The screen shows blank when I get to the point
>> above.after hitting enter a few times, it just sends the 
>> cursor down
>> the screen..I tried typing TEST but no response...just a 
>> dark screen in
>> the CL window.
>>
>>
>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>>
>>> That’s a better start, did you hit enter a few times and
>>> then send TEST as per the wiki article
>>> 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Not using serial...using USB.

On Friday, 5 March 2021 at 10:34:32 UTC+13 monmul wrote:

> pi@WeatherPi:~ $ lsusb
> Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, 
> Ltd FT232 Serial (UART) IC
> Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash 
> drive
> Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
> Fast Ethernet Adapter
> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> pi@WeatherPi:~ $ 
>
>
> On Friday, 5 March 2021 at 09:05:34 UTC+13 tke...@gmail.com wrote:
>
>> Well, if you're sure you have the right port (/dev/ttyUSB0), and you have 
>> correctly completed the test (a couple of enters, followed by ENTER, all 
>> caps) and you got nothing back, then that is as definitive a test that I 
>> know of that you have a connectivity problem.
>>
>> Do you have a USB version of the logger? Or, if you have a serial 
>> version, are you using a serial-to-usb converter? Either way, make sure 
>> your computer is recognizing the USB connection to the logger:
>>
>> *lsusb*
>>
>> If you have a serial version of the logger (very rare these days), then 
>> what serial port are you plugging it into?
>>
>>
>>
>> On Thu, Mar 4, 2021 at 11:59 AM monmul  wrote:
>>
>>> Yes, apologieswas in a rush typing and did not review."new 
>>> envoy"..it should be...and "initiation" is the other typo!
>>>
>>> On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote:
>>>
 ‘new’ envoy?

 Gary

 On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:

> What do you mean by "net Envoy"? If you are using a serial port like 
> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a 
> network connector. Or, are you using an IP logger?
>
> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>
>> I have not had time to do the reseating yethopefully later today. 
>> One thing strikes me (probably becuase it has been so long since I set 
>> it 
>> up) I just switched envoys, how does the net envoy know what to do...I 
>> have 
>> not gone to any itiation or set up page etcI just plugged and 
>> supposed 
>> it would go. Am I missing something?
>>
>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>>
>>> Thank you, I will give that a try!
>>>
>>> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:
>>>
 Reseat means to remove the logger from the Envoy and then reinstall 
 the logger in the Envoy. Sometimes you can get a dodgy connection 
 between 
 pins on the logger and the socket in the Envoy (or console) and 
 remaking 
 the connection by reseating can sometimes fix this.

 Gary 

 On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:

> Sorry, I don't quite understand what you mean by "reseat"?
>
> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com 
> wrote:
>
>> You can try reseating the logger.
>>
>> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>>
>>> Neither TEST nor NVER returns anythingso, I guess I have a 
>>> connectivity problemwhich seems strange as  I did a straight 
>>> swap out 
>>> of the Envoys!
>>>
>>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com 
>>> wrote:
>>>
 If the cursor went down the screen, then the console is sending 
 something back. Make sure you press  a few times, then 
 "TEST", all 
 in capital letters.

 You can also type "NVER". Again, all in capital letters. This 
 will return the firmware version number.

 If neither of those work, then you have a connectivity problem.


 On Sat, Feb 27, 2021 at 3:54 PM monmul  
 wrote:

> The screen shows blank when I get to the point above.after 
> hitting enter a few times, it just sends the cursor down the 
> screen..I 
> tried typing TEST but no response...just a dark screen in the CL 
> window.
>
>
> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>
>> That’s a better start, did you hit enter a few times and then 
>> send TEST as per the wiki article 
>> ?
>>  
>> You should get a response from the Envoy.
>>
>> Gary
>>
>

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

pi@WeatherPi:~ $ lsusb
Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, 
Ltd FT232 Serial (UART) IC
Bus 001 Device 005: ID 13fe:4100 Kingston Technology Company Inc. Flash 
drive
Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@WeatherPi:~ $ 


On Friday, 5 March 2021 at 09:05:34 UTC+13 tke...@gmail.com wrote:

> Well, if you're sure you have the right port (/dev/ttyUSB0), and you have 
> correctly completed the test (a couple of enters, followed by ENTER, all 
> caps) and you got nothing back, then that is as definitive a test that I 
> know of that you have a connectivity problem.
>
> Do you have a USB version of the logger? Or, if you have a serial version, 
> are you using a serial-to-usb converter? Either way, make sure your 
> computer is recognizing the USB connection to the logger:
>
> *lsusb*
>
> If you have a serial version of the logger (very rare these days), then 
> what serial port are you plugging it into?
>
>
>
> On Thu, Mar 4, 2021 at 11:59 AM monmul  wrote:
>
>> Yes, apologieswas in a rush typing and did not review."new 
>> envoy"..it should be...and "initiation" is the other typo!
>>
>> On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote:
>>
>>> ‘new’ envoy?
>>>
>>> Gary
>>>
>>> On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:
>>>
 What do you mean by "net Envoy"? If you are using a serial port like 
 /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a 
 network connector. Or, are you using an IP logger?

 On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:

> I have not had time to do the reseating yethopefully later today. 
> One thing strikes me (probably becuase it has been so long since I set it 
> up) I just switched envoys, how does the net envoy know what to do...I 
> have 
> not gone to any itiation or set up page etcI just plugged and 
> supposed 
> it would go. Am I missing something?
>
> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>
>> Thank you, I will give that a try!
>>
>> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:
>>
>>> Reseat means to remove the logger from the Envoy and then reinstall 
>>> the logger in the Envoy. Sometimes you can get a dodgy connection 
>>> between 
>>> pins on the logger and the socket in the Envoy (or console) and 
>>> remaking 
>>> the connection by reseating can sometimes fix this.
>>>
>>> Gary 
>>>
>>> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:
>>>
 Sorry, I don't quite understand what you mean by "reseat"?

 On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com 
 wrote:

> You can try reseating the logger.
>
> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>
>> Neither TEST nor NVER returns anythingso, I guess I have a 
>> connectivity problemwhich seems strange as  I did a straight 
>> swap out 
>> of the Envoys!
>>
>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com 
>> wrote:
>>
>>> If the cursor went down the screen, then the console is sending 
>>> something back. Make sure you press  a few times, then 
>>> "TEST", all 
>>> in capital letters.
>>>
>>> You can also type "NVER". Again, all in capital letters. This 
>>> will return the firmware version number.
>>>
>>> If neither of those work, then you have a connectivity problem.
>>>
>>>
>>> On Sat, Feb 27, 2021 at 3:54 PM monmul  
>>> wrote:
>>>
 The screen shows blank when I get to the point above.after 
 hitting enter a few times, it just sends the cursor down the 
 screen..I 
 tried typing TEST but no response...just a dark screen in the CL 
 window.


 On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:

> That’s a better start, did you hit enter a few times and then 
> send TEST as per the wiki article 
> ?
>  
> You should get a response from the Envoy.
>
> Gary
>
> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

Well, if you're sure you have the right port (/dev/ttyUSB0), and you have
correctly completed the test (a couple of enters, followed by ENTER, all
caps) and you got nothing back, then that is as definitive a test that I
know of that you have a connectivity problem.

Do you have a USB version of the logger? Or, if you have a serial version,
are you using a serial-to-usb converter? Either way, make sure your
computer is recognizing the USB connection to the logger:

*lsusb*

If you have a serial version of the logger (very rare these days), then
what serial port are you plugging it into?



On Thu, Mar 4, 2021 at 11:59 AM monmul  wrote:

> Yes, apologieswas in a rush typing and did not review."new
> envoy"..it should be...and "initiation" is the other typo!
>
> On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote:
>
>> ‘new’ envoy?
>>
>> Gary
>>
>> On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:
>>
>>> What do you mean by "net Envoy"? If you are using a serial port like
>>> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a
>>> network connector. Or, are you using an IP logger?
>>>
>>> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>>>
 I have not had time to do the reseating yethopefully later today.
 One thing strikes me (probably becuase it has been so long since I set it
 up) I just switched envoys, how does the net envoy know what to do...I have
 not gone to any itiation or set up page etcI just plugged and supposed
 it would go. Am I missing something?

 On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:

> Thank you, I will give that a try!
>
> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:
>
>> Reseat means to remove the logger from the Envoy and then reinstall
>> the logger in the Envoy. Sometimes you can get a dodgy connection between
>> pins on the logger and the socket in the Envoy (or console) and remaking
>> the connection by reseating can sometimes fix this.
>>
>> Gary
>>
>> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:
>>
>>> Sorry, I don't quite understand what you mean by "reseat"?
>>>
>>> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com
>>> wrote:
>>>
 You can try reseating the logger.

 On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:

> Neither TEST nor NVER returns anythingso, I guess I have a
> connectivity problemwhich seems strange as  I did a straight swap 
> out
> of the Envoys!
>
> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com
> wrote:
>
>> If the cursor went down the screen, then the console is sending
>> something back. Make sure you press  a few times, then 
>> "TEST", all
>> in capital letters.
>>
>> You can also type "NVER". Again, all in capital letters. This
>> will return the firmware version number.
>>
>> If neither of those work, then you have a connectivity problem.
>>
>>
>> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>>
>>> The screen shows blank when I get to the point above.after
>>> hitting enter a few times, it just sends the cursor down the 
>>> screen..I
>>> tried typing TEST but no response...just a dark screen in the CL 
>>> window.
>>>
>>>
>>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>>>
 That’s a better start, did you hit enter a few times and then
 send TEST as per the wiki article
 ?
 You should get a response from the Envoy.

 Gary

 On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo killall screen
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system
> /run/user/1000/gvfs
>   Output information may be incomplete.
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 11:00:42
>
> Press CTRL-A Z for help on special keys
>
>
> On Saturday, 27 February 2021 at 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Yes, apologieswas in a rush typing and did not review."new 
envoy"..it should be...and "initiation" is the other typo!

On Friday, 5 March 2021 at 08:33:36 UTC+13 gjr80 wrote:

> ‘new’ envoy?
>
> Gary
>
> On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:
>
>> What do you mean by "net Envoy"? If you are using a serial port like 
>> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a 
>> network connector. Or, are you using an IP logger?
>>
>> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>>
>>> I have not had time to do the reseating yethopefully later today. 
>>> One thing strikes me (probably becuase it has been so long since I set it 
>>> up) I just switched envoys, how does the net envoy know what to do...I have 
>>> not gone to any itiation or set up page etcI just plugged and supposed 
>>> it would go. Am I missing something?
>>>
>>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>>>
 Thank you, I will give that a try!

 On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:

> Reseat means to remove the logger from the Envoy and then reinstall 
> the logger in the Envoy. Sometimes you can get a dodgy connection between 
> pins on the logger and the socket in the Envoy (or console) and remaking 
> the connection by reseating can sometimes fix this.
>
> Gary 
>
> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:
>
>> Sorry, I don't quite understand what you mean by "reseat"?
>>
>> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com 
>> wrote:
>>
>>> You can try reseating the logger.
>>>
>>> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>>>
 Neither TEST nor NVER returns anythingso, I guess I have a 
 connectivity problemwhich seems strange as  I did a straight swap 
 out 
 of the Envoys!

 On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com 
 wrote:

> If the cursor went down the screen, then the console is sending 
> something back. Make sure you press  a few times, then "TEST", 
> all 
> in capital letters.
>
> You can also type "NVER". Again, all in capital letters. This will 
> return the firmware version number.
>
> If neither of those work, then you have a connectivity problem.
>
>
> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>
>> The screen shows blank when I get to the point above.after 
>> hitting enter a few times, it just sends the cursor down the 
>> screen..I 
>> tried typing TEST but no response...just a dark screen in the CL 
>> window.
>>
>>
>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>>
>>> That’s a better start, did you hit enter a few times and then 
>>> send TEST as per the wiki article 
>>> ?
>>>  
>>> You should get a response from the Envoy.
>>>
>>> Gary
>>>
>>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>>>
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Device or resource busy
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ sudo killall screen
 pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
 /run/user/1000/gvfs
   Output information may be incomplete.
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0


 Welcome to minicom 2.7

 OPTIONS: I18n 
 Compiled on Apr 22 2017, 09:14:19.
 Port /dev/ttyUSB0, 11:00:42

 Press CTRL-A Z for help on special keys


 On Saturday, 27 February 2021 at 02:19:42 UTC+13 
 tke...@gmail.com wrote:

> Monmul, we have not definitively heard whether or not you are 
> able to do the test listed under *Establishing connectivity 
> *
>  in 
> the Wiki.That is an essential first step.
>
> Use either screen or minicom. You may have to preface the 
> command with 'sudo'. For example,
>
>
> *sudo screen /dev/ttyUSB0 19200*
>
> -tk
>
> On Thu, Feb 25, 2021 at 7:34 PM 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

‘new’ envoy?

Gary

On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:

> What do you mean by "net Envoy"? If you are using a serial port like 
> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a 
> network connector. Or, are you using an IP logger?
>
> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>
>> I have not had time to do the reseating yethopefully later today. One 
>> thing strikes me (probably becuase it has been so long since I set it up) I 
>> just switched envoys, how does the net envoy know what to do...I have not 
>> gone to any itiation or set up page etcI just plugged and supposed it 
>> would go. Am I missing something?
>>
>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>>
>>> Thank you, I will give that a try!
>>>
>>> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:
>>>
 Reseat means to remove the logger from the Envoy and then reinstall the 
 logger in the Envoy. Sometimes you can get a dodgy connection between pins 
 on the logger and the socket in the Envoy (or console) and remaking the 
 connection by reseating can sometimes fix this.

 Gary 

 On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:

> Sorry, I don't quite understand what you mean by "reseat"?
>
> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote:
>
>> You can try reseating the logger.
>>
>> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>>
>>> Neither TEST nor NVER returns anythingso, I guess I have a 
>>> connectivity problemwhich seems strange as  I did a straight swap 
>>> out 
>>> of the Envoys!
>>>
>>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com 
>>> wrote:
>>>
 If the cursor went down the screen, then the console is sending 
 something back. Make sure you press  a few times, then "TEST", 
 all 
 in capital letters.

 You can also type "NVER". Again, all in capital letters. This will 
 return the firmware version number.

 If neither of those work, then you have a connectivity problem.


 On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:

> The screen shows blank when I get to the point above.after 
> hitting enter a few times, it just sends the cursor down the 
> screen..I 
> tried typing TEST but no response...just a dark screen in the CL 
> window.
>
>
> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>
>> That’s a better start, did you hit enter a few times and then 
>> send TEST as per the wiki article 
>> ?
>>  
>> You should get a response from the Envoy.
>>
>> Gary
>>
>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>>
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ sudo killall screen
>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>>> /run/user/1000/gvfs
>>>   Output information may be incomplete.
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>>
>>>
>>> Welcome to minicom 2.7
>>>
>>> OPTIONS: I18n 
>>> Compiled on Apr 22 2017, 09:14:19.
>>> Port /dev/ttyUSB0, 11:00:42
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>>
>>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 
>>> tke...@gmail.com wrote:
>>>
 Monmul, we have not definitively heard whether or not you are 
 able to do the test listed under *Establishing connectivity 
 *
  in 
 the Wiki.That is an essential first step.

 Use either screen or minicom. You may have to preface the 
 command with 'sudo'. For example,


 *sudo screen /dev/ttyUSB0 19200*

 -tk

 On Thu, Feb 25, 2021 at 7:34 PM monmul  
 wrote:

> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx 
> weather system...
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: 
> Initializing weewx version 4.4.0
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

‘new’ logger?

Gary

On Friday, 5 March 2021 at 01:39:10 UTC+10 tke...@gmail.com wrote:

> What do you mean by "net Envoy"? If you are using a serial port like 
> /dev/ttyUSB0, the logger should be plugged in via a USB connector, not a 
> network connector. Or, are you using an IP logger?
>
> On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:
>
>> I have not had time to do the reseating yethopefully later today. One 
>> thing strikes me (probably becuase it has been so long since I set it up) I 
>> just switched envoys, how does the net envoy know what to do...I have not 
>> gone to any itiation or set up page etcI just plugged and supposed it 
>> would go. Am I missing something?
>>
>> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>>
>>> Thank you, I will give that a try!
>>>
>>> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:
>>>
 Reseat means to remove the logger from the Envoy and then reinstall the 
 logger in the Envoy. Sometimes you can get a dodgy connection between pins 
 on the logger and the socket in the Envoy (or console) and remaking the 
 connection by reseating can sometimes fix this.

 Gary 

 On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:

> Sorry, I don't quite understand what you mean by "reseat"?
>
> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote:
>
>> You can try reseating the logger.
>>
>> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>>
>>> Neither TEST nor NVER returns anythingso, I guess I have a 
>>> connectivity problemwhich seems strange as  I did a straight swap 
>>> out 
>>> of the Envoys!
>>>
>>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com 
>>> wrote:
>>>
 If the cursor went down the screen, then the console is sending 
 something back. Make sure you press  a few times, then "TEST", 
 all 
 in capital letters.

 You can also type "NVER". Again, all in capital letters. This will 
 return the firmware version number.

 If neither of those work, then you have a connectivity problem.


 On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:

> The screen shows blank when I get to the point above.after 
> hitting enter a few times, it just sends the cursor down the 
> screen..I 
> tried typing TEST but no response...just a dark screen in the CL 
> window.
>
>
> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>
>> That’s a better start, did you hit enter a few times and then 
>> send TEST as per the wiki article 
>> ?
>>  
>> You should get a response from the Envoy.
>>
>> Gary
>>
>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>>
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ sudo killall screen
>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>>> /run/user/1000/gvfs
>>>   Output information may be incomplete.
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>>
>>>
>>> Welcome to minicom 2.7
>>>
>>> OPTIONS: I18n 
>>> Compiled on Apr 22 2017, 09:14:19.
>>> Port /dev/ttyUSB0, 11:00:42
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>>
>>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 
>>> tke...@gmail.com wrote:
>>>
 Monmul, we have not definitively heard whether or not you are 
 able to do the test listed under *Establishing connectivity 
 *
  in 
 the Wiki.That is an essential first step.

 Use either screen or minicom. You may have to preface the 
 command with 'sudo'. For example,


 *sudo screen /dev/ttyUSB0 19200*

 -tk

 On Thu, Feb 25, 2021 at 7:34 PM monmul  
 wrote:

> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx 
> weather system...
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: 
> Initializing weewx version 4.4.0
> Feb 26 16:31:32 WeatherPi weewx[17966] INF

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

What do you mean by "net Envoy"? If you are using a serial port like
/dev/ttyUSB0, the logger should be plugged in via a USB connector, not a
network connector. Or, are you using an IP logger?

On Wed, Mar 3, 2021 at 8:38 PM monmul  wrote:

> I have not had time to do the reseating yethopefully later today. One
> thing strikes me (probably becuase it has been so long since I set it up) I
> just switched envoys, how does the net envoy know what to do...I have not
> gone to any itiation or set up page etcI just plugged and supposed it
> would go. Am I missing something?
>
> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>
>> Thank you, I will give that a try!
>>
>> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:
>>
>>> Reseat means to remove the logger from the Envoy and then reinstall the
>>> logger in the Envoy. Sometimes you can get a dodgy connection between pins
>>> on the logger and the socket in the Envoy (or console) and remaking the
>>> connection by reseating can sometimes fix this.
>>>
>>> Gary
>>>
>>> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:
>>>
 Sorry, I don't quite understand what you mean by "reseat"?

 On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote:

> You can try reseating the logger.
>
> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>
>> Neither TEST nor NVER returns anythingso, I guess I have a
>> connectivity problemwhich seems strange as  I did a straight swap out
>> of the Envoys!
>>
>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com
>> wrote:
>>
>>> If the cursor went down the screen, then the console is sending
>>> something back. Make sure you press  a few times, then "TEST", 
>>> all
>>> in capital letters.
>>>
>>> You can also type "NVER". Again, all in capital letters. This will
>>> return the firmware version number.
>>>
>>> If neither of those work, then you have a connectivity problem.
>>>
>>>
>>> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>>>
 The screen shows blank when I get to the point above.after
 hitting enter a few times, it just sends the cursor down the 
 screen..I
 tried typing TEST but no response...just a dark screen in the CL 
 window.


 On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:

> That’s a better start, did you hit enter a few times and then send
> TEST as per the wiki article
> ?
> You should get a response from the Envoy.
>
> Gary
>
> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ sudo killall screen
>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system
>> /run/user/1000/gvfs
>>   Output information may be incomplete.
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 11:00:42
>>
>> Press CTRL-A Z for help on special keys
>>
>>
>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com
>> wrote:
>>
>>> Monmul, we have not definitively heard whether or not you are
>>> able to do the test listed under *Establishing connectivity
>>> *
>>>  in
>>> the Wiki.That is an essential first step.
>>>
>>> Use either screen or minicom. You may have to preface the
>>> command with 'sudo'. For example,
>>>
>>>
>>> *sudo screen /dev/ttyUSB0 19200*
>>>
>>> -tk
>>>
>>> On Thu, Feb 25, 2021 at 7:34 PM monmul 
>>> wrote:
>>>
 Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx
 weather system...
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__:
 Initializing weewx version 4.4.0
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using
 Python 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 
 20170516]
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform
 Linux-4.19.66-v7+-armv7l-with-debian-9.13
 Feb

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

After reseating, I get the exact same as before.

pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ sudo killall screen
screen: no process found
pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0

Welcome to minicom 2.7

OPTIONS: I18n 
Compiled on Apr 22 2017, 09:14:19.
Port /dev/ttyUSB0, 18:49:36

Press CTRL-A Z for help on special keys







On Thursday, 4 March 2021 at 17:38:18 UTC+13 monmul wrote:

> I have not had time to do the reseating yethopefully later today. One 
> thing strikes me (probably becuase it has been so long since I set it up) I 
> just switched envoys, how does the net envoy know what to do...I have not 
> gone to any itiation or set up page etcI just plugged and supposed it 
> would go. Am I missing something?
>
> On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:
>
>> Thank you, I will give that a try!
>>
>> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:
>>
>>> Reseat means to remove the logger from the Envoy and then reinstall the 
>>> logger in the Envoy. Sometimes you can get a dodgy connection between pins 
>>> on the logger and the socket in the Envoy (or console) and remaking the 
>>> connection by reseating can sometimes fix this.
>>>
>>> Gary 
>>>
>>> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:
>>>
 Sorry, I don't quite understand what you mean by "reseat"?

 On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote:

> You can try reseating the logger.
>
> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>
>> Neither TEST nor NVER returns anythingso, I guess I have a 
>> connectivity problemwhich seems strange as  I did a straight swap 
>> out 
>> of the Envoys!
>>
>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com 
>> wrote:
>>
>>> If the cursor went down the screen, then the console is sending 
>>> something back. Make sure you press  a few times, then "TEST", 
>>> all 
>>> in capital letters.
>>>
>>> You can also type "NVER". Again, all in capital letters. This will 
>>> return the firmware version number.
>>>
>>> If neither of those work, then you have a connectivity problem.
>>>
>>>
>>> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>>>
 The screen shows blank when I get to the point above.after 
 hitting enter a few times, it just sends the cursor down the 
 screen..I 
 tried typing TEST but no response...just a dark screen in the CL 
 window.


 On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:

> That’s a better start, did you hit enter a few times and then send 
> TEST as per the wiki article 
> ?
>  
> You should get a response from the Envoy.
>
> Gary
>
> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ sudo killall screen
>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>> /run/user/1000/gvfs
>>   Output information may be incomplete.
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 11:00:42
>>
>> Press CTRL-A Z for help on special keys
>>
>>
>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com 
>> wrote:
>>
>>> Monmul, we have not definitively heard whether or not you are 
>>> able to do the test listed under *Establishing connectivity 
>>> *
>>>  in 
>>> the Wiki.That is an essential first step.
>>>
>>> Use either screen or minicom. You may have to preface the 
>>> command with 'sudo'. For example,
>>>
>>>
>>> *sudo screen /dev/ttyUSB0 19200*
>>>
>>> -tk
>>>
>>> On Thu, Feb 25, 2021 at 7:34 PM monmul  
>>> wrote:
>>>
 Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx 
 weather 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

I have not had time to do the reseating yethopefully later today. One 
thing strikes me (probably becuase it has been so long since I set it up) I 
just switched envoys, how does the net envoy know what to do...I have not 
gone to any itiation or set up page etcI just plugged and supposed it 
would go. Am I missing something?

On Sunday, 28 February 2021 at 19:42:44 UTC+13 monmul wrote:

> Thank you, I will give that a try!
>
> On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:
>
>> Reseat means to remove the logger from the Envoy and then reinstall the 
>> logger in the Envoy. Sometimes you can get a dodgy connection between pins 
>> on the logger and the socket in the Envoy (or console) and remaking the 
>> connection by reseating can sometimes fix this.
>>
>> Gary 
>>
>> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:
>>
>>> Sorry, I don't quite understand what you mean by "reseat"?
>>>
>>> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote:
>>>
 You can try reseating the logger.

 On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:

> Neither TEST nor NVER returns anythingso, I guess I have a 
> connectivity problemwhich seems strange as  I did a straight swap out 
> of the Envoys!
>
> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote:
>
>> If the cursor went down the screen, then the console is sending 
>> something back. Make sure you press  a few times, then "TEST", 
>> all 
>> in capital letters.
>>
>> You can also type "NVER". Again, all in capital letters. This will 
>> return the firmware version number.
>>
>> If neither of those work, then you have a connectivity problem.
>>
>>
>> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>>
>>> The screen shows blank when I get to the point above.after 
>>> hitting enter a few times, it just sends the cursor down the 
>>> screen..I 
>>> tried typing TEST but no response...just a dark screen in the CL window.
>>>
>>>
>>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>>>
 That’s a better start, did you hit enter a few times and then send 
 TEST as per the wiki article 
 ?
  
 You should get a response from the Envoy.

 Gary

 On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo killall screen
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
> /run/user/1000/gvfs
>   Output information may be incomplete.
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n 
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 11:00:42
>
> Press CTRL-A Z for help on special keys
>
>
> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com 
> wrote:
>
>> Monmul, we have not definitively heard whether or not you are 
>> able to do the test listed under *Establishing connectivity 
>> *
>>  in 
>> the Wiki.That is an essential first step.
>>
>> Use either screen or minicom. You may have to preface the 
>> command with 'sudo'. For example,
>>
>>
>> *sudo screen /dev/ttyUSB0 19200*
>>
>> -tk
>>
>> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>>
>>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx 
>>> weather system...
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: 
>>> Initializing weewx version 4.4.0
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using 
>>> Python 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 
>>> 20170516]
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
>>> 'en_NZ.UTF-8'
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file 
>>> is /var/run/weewx.pid
>>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather 
>>> system: weewx.
>>> Feb 26 16:31:32 WeatherPi systemd[1]: S

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Thank you, I will give that a try!

On Sunday, 28 February 2021 at 19:31:21 UTC+13 gjr80 wrote:

> Reseat means to remove the logger from the Envoy and then reinstall the 
> logger in the Envoy. Sometimes you can get a dodgy connection between pins 
> on the logger and the socket in the Envoy (or console) and remaking the 
> connection by reseating can sometimes fix this.
>
> Gary 
>
> On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:
>
>> Sorry, I don't quite understand what you mean by "reseat"?
>>
>> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote:
>>
>>> You can try reseating the logger.
>>>
>>> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>>>
 Neither TEST nor NVER returns anythingso, I guess I have a 
 connectivity problemwhich seems strange as  I did a straight swap out 
 of the Envoys!

 On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote:

> If the cursor went down the screen, then the console is sending 
> something back. Make sure you press  a few times, then "TEST", all 
> in capital letters.
>
> You can also type "NVER". Again, all in capital letters. This will 
> return the firmware version number.
>
> If neither of those work, then you have a connectivity problem.
>
>
> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>
>> The screen shows blank when I get to the point above.after 
>> hitting enter a few times, it just sends the cursor down the 
>> screen..I 
>> tried typing TEST but no response...just a dark screen in the CL window.
>>
>>
>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>>
>>> That’s a better start, did you hit enter a few times and then send 
>>> TEST as per the wiki article 
>>> ?
>>>  
>>> You should get a response from the Envoy.
>>>
>>> Gary
>>>
>>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>>>
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Device or resource busy
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ sudo killall screen
 pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
 /run/user/1000/gvfs
   Output information may be incomplete.
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0


 Welcome to minicom 2.7

 OPTIONS: I18n 
 Compiled on Apr 22 2017, 09:14:19.
 Port /dev/ttyUSB0, 11:00:42

 Press CTRL-A Z for help on special keys


 On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com 
 wrote:

> Monmul, we have not definitively heard whether or not you are able 
> to do the test listed under *Establishing connectivity 
> *
>  in 
> the Wiki.That is an essential first step.
>
> Use either screen or minicom. You may have to preface the command 
> with 'sudo'. For example,
>
>
> *sudo screen /dev/ttyUSB0 19200*
>
> -tk
>
> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>
>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: 
>> Initializing weewx version 4.4.0
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using 
>> Python 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 
>> 20170516]
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
>> 'en_NZ.UTF-8'
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather 
>> system: weewx.
>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather 
>> system.
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
>> configuration file /etc/weewx/weewx.conf
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: 
>> Initializing engine
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Feb 26 16:31:32 WeatherPi weewx[1

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

Reseat means to remove the logger from the Envoy and then reinstall the 
logger in the Envoy. Sometimes you can get a dodgy connection between pins 
on the logger and the socket in the Envoy (or console) and remaking the 
connection by reseating can sometimes fix this.

Gary 

On Sunday, 28 February 2021 at 12:53:17 UTC+10 monmul wrote:

> Sorry, I don't quite understand what you mean by "reseat"?
>
> On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote:
>
>> You can try reseating the logger.
>>
>> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>>
>>> Neither TEST nor NVER returns anythingso, I guess I have a 
>>> connectivity problemwhich seems strange as  I did a straight swap out 
>>> of the Envoys!
>>>
>>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote:
>>>
 If the cursor went down the screen, then the console is sending 
 something back. Make sure you press  a few times, then "TEST", all 
 in capital letters.

 You can also type "NVER". Again, all in capital letters. This will 
 return the firmware version number.

 If neither of those work, then you have a connectivity problem.


 On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:

> The screen shows blank when I get to the point above.after hitting 
> enter a few times, it just sends the cursor down the screen..I tried 
> typing TEST but no response...just a dark screen in the CL window.
>
>
> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>
>> That’s a better start, did you hit enter a few times and then send 
>> TEST as per the wiki article 
>> ?
>>  
>> You should get a response from the Envoy.
>>
>> Gary
>>
>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>>
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ sudo killall screen
>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>>> /run/user/1000/gvfs
>>>   Output information may be incomplete.
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>>
>>>
>>> Welcome to minicom 2.7
>>>
>>> OPTIONS: I18n 
>>> Compiled on Apr 22 2017, 09:14:19.
>>> Port /dev/ttyUSB0, 11:00:42
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>>
>>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com 
>>> wrote:
>>>
 Monmul, we have not definitively heard whether or not you are able 
 to do the test listed under *Establishing connectivity 
 *
  in 
 the Wiki.That is an essential first step.

 Use either screen or minicom. You may have to preface the command 
 with 'sudo'. For example,


 *sudo screen /dev/ttyUSB0 19200*

 -tk

 On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:

> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
> system...
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing 
> weewx version 4.4.0
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 
> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
> 'en_NZ.UTF-8'
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
> /var/run/weewx.pid
> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather 
> system: weewx.
> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather 
> system.
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
> configuration file /etc/weewx/weewx.conf
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: 
> Initializing engine
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
> station type Vantage (weewx.drivers.vantage)
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG 
> weewx.drivers.vantage: Driver version is 3.2.1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG 
> weewx.drivers.vantage: Option loop_request=1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG 
>>

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Sorry, I don't quite understand what you mean by "reseat"?

On Sunday, 28 February 2021 at 14:40:11 UTC+13 tke...@gmail.com wrote:

> You can try reseating the logger.
>
> On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:
>
>> Neither TEST nor NVER returns anythingso, I guess I have a 
>> connectivity problemwhich seems strange as  I did a straight swap out 
>> of the Envoys!
>>
>> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote:
>>
>>> If the cursor went down the screen, then the console is sending 
>>> something back. Make sure you press  a few times, then "TEST", all 
>>> in capital letters.
>>>
>>> You can also type "NVER". Again, all in capital letters. This will 
>>> return the firmware version number.
>>>
>>> If neither of those work, then you have a connectivity problem.
>>>
>>>
>>> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>>>
 The screen shows blank when I get to the point above.after hitting 
 enter a few times, it just sends the cursor down the screen..I tried 
 typing TEST but no response...just a dark screen in the CL window.


 On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:

> That’s a better start, did you hit enter a few times and then send 
> TEST as per the wiki article 
> ?
>  
> You should get a response from the Envoy.
>
> Gary
>
> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ sudo killall screen
>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>> /run/user/1000/gvfs
>>   Output information may be incomplete.
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 11:00:42
>>
>> Press CTRL-A Z for help on special keys
>>
>>
>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com 
>> wrote:
>>
>>> Monmul, we have not definitively heard whether or not you are able 
>>> to do the test listed under *Establishing connectivity 
>>> *
>>>  in 
>>> the Wiki.That is an essential first step.
>>>
>>> Use either screen or minicom. You may have to preface the command 
>>> with 'sudo'. For example,
>>>
>>>
>>> *sudo screen /dev/ttyUSB0 19200*
>>>
>>> -tk
>>>
>>> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>>>
 Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
 system...
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing 
 weewx version 4.4.0
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 
 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
 Linux-4.19.66-v7+-armv7l-with-debian-9.13
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
 'en_NZ.UTF-8'
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
 /var/run/weewx.pid
 Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather 
 system: weewx.
 Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather 
 system.
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
 configuration file /etc/weewx/weewx.conf
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing 
 engine
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
 station type Vantage (weewx.drivers.vantage)
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Driver version is 3.2.1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Option loop_request=1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
 Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement 
 from fe80::724f:57ff:feb7:82a1
 Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 
 lease
 Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Retry #0 failed
 Feb 26 16:31:40 WeatherPi weewx[17971] DEB

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

You can try reseating the logger.

On Sat, Feb 27, 2021 at 5:16 PM monmul  wrote:

> Neither TEST nor NVER returns anythingso, I guess I have a
> connectivity problemwhich seems strange as  I did a straight swap out
> of the Envoys!
>
> On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote:
>
>> If the cursor went down the screen, then the console is sending something
>> back. Make sure you press  a few times, then "TEST", all in capital
>> letters.
>>
>> You can also type "NVER". Again, all in capital letters. This will return
>> the firmware version number.
>>
>> If neither of those work, then you have a connectivity problem.
>>
>>
>> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>>
>>> The screen shows blank when I get to the point above.after hitting
>>> enter a few times, it just sends the cursor down the screen..I tried
>>> typing TEST but no response...just a dark screen in the CL window.
>>>
>>>
>>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>>>
 That’s a better start, did you hit enter a few times and then send TEST
 as per the wiki article
 ?
 You should get a response from the Envoy.

 Gary

 On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo killall screen
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system
> /run/user/1000/gvfs
>   Output information may be incomplete.
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 11:00:42
>
> Press CTRL-A Z for help on special keys
>
>
> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com
> wrote:
>
>> Monmul, we have not definitively heard whether or not you are able to
>> do the test listed under *Establishing connectivity
>> *
>>  in
>> the Wiki.That is an essential first step.
>>
>> Use either screen or minicom. You may have to preface the command
>> with 'sudo'. For example,
>>
>>
>> *sudo screen /dev/ttyUSB0 19200*
>>
>> -tk
>>
>> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>>
>>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather
>>> system...
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing
>>> weewx version 4.4.0
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python
>>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform
>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is
>>> 'en_NZ.UTF-8'
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is
>>> /var/run/weewx.pid
>>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather
>>> system: weewx.
>>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather
>>> system.
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using
>>> configuration file /etc/weewx/weewx.conf
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing
>>> engine
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading
>>> station type Vantage (weewx.drivers.vantage)
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Driver version is 3.2.1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Option loop_request=1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement
>>> from fe80::724f:57ff:feb7:82a1
>>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6
>>> lease
>>> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Retry #0 failed
>>> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Retry #1 failed
>>> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
>>> Retry #2 failed
>>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement
>>> from fe80::724f:57ff:feb7:82a1
>>> Feb 26 16:31:45 W

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Neither TEST nor NVER returns anythingso, I guess I have a connectivity 
problemwhich seems strange as  I did a straight swap out of the Envoys!

On Sunday, 28 February 2021 at 13:33:34 UTC+13 tke...@gmail.com wrote:

> If the cursor went down the screen, then the console is sending something 
> back. Make sure you press  a few times, then "TEST", all in capital 
> letters.
>
> You can also type "NVER". Again, all in capital letters. This will return 
> the firmware version number.
>
> If neither of those work, then you have a connectivity problem.
>
>
> On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:
>
>> The screen shows blank when I get to the point above.after hitting 
>> enter a few times, it just sends the cursor down the screen..I tried 
>> typing TEST but no response...just a dark screen in the CL window.
>>
>>
>> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>>
>>> That’s a better start, did you hit enter a few times and then send TEST 
>>> as per the wiki article 
>>> ?
>>>  
>>> You should get a response from the Envoy.
>>>
>>> Gary
>>>
>>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>>>
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Device or resource busy
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ sudo killall screen
 pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
 /run/user/1000/gvfs
   Output information may be incomplete.
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0


 Welcome to minicom 2.7

 OPTIONS: I18n 
 Compiled on Apr 22 2017, 09:14:19.
 Port /dev/ttyUSB0, 11:00:42

 Press CTRL-A Z for help on special keys


 On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com 
 wrote:

> Monmul, we have not definitively heard whether or not you are able to 
> do the test listed under *Establishing connectivity 
> *
>  in 
> the Wiki.That is an essential first step.
>
> Use either screen or minicom. You may have to preface the command 
> with 'sudo'. For example,
>
>
> *sudo screen /dev/ttyUSB0 19200*
>
> -tk
>
> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>
>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing 
>> weewx version 4.4.0
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 
>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
>> 'en_NZ.UTF-8'
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather 
>> system: weewx.
>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather 
>> system.
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
>> configuration file /etc/weewx/weewx.conf
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing 
>> engine
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Driver version is 3.2.1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Option loop_request=1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement 
>> from fe80::724f:57ff:feb7:82a1
>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 
>> lease
>> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Retry #0 failed
>> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Retry #1 failed
>> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Retry #2 failed
>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement 
>> from fe80::724f:57ff:feb7:82a1
>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 
>> lease
>> Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Retry #3 failed

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

If the cursor went down the screen, then the console is sending something
back. Make sure you press  a few times, then "TEST", all in capital
letters.

You can also type "NVER". Again, all in capital letters. This will return
the firmware version number.

If neither of those work, then you have a connectivity problem.


On Sat, Feb 27, 2021 at 3:54 PM monmul  wrote:

> The screen shows blank when I get to the point above.after hitting
> enter a few times, it just sends the cursor down the screen..I tried
> typing TEST but no response...just a dark screen in the CL window.
>
>
> On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:
>
>> That’s a better start, did you hit enter a few times and then send TEST
>> as per the wiki article
>> ?
>> You should get a response from the Envoy.
>>
>> Gary
>>
>> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>>
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ sudo killall screen
>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system
>>> /run/user/1000/gvfs
>>>   Output information may be incomplete.
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>>
>>>
>>> Welcome to minicom 2.7
>>>
>>> OPTIONS: I18n
>>> Compiled on Apr 22 2017, 09:14:19.
>>> Port /dev/ttyUSB0, 11:00:42
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>>
>>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com wrote:
>>>
 Monmul, we have not definitively heard whether or not you are able to
 do the test listed under *Establishing connectivity
 *
  in
 the Wiki.That is an essential first step.

 Use either screen or minicom. You may have to preface the command with
 'sudo'. For example,


 *sudo screen /dev/ttyUSB0 19200*

 -tk

 On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:

> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather
> system...
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing
> weewx version 4.4.0
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python
> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is
> 'en_NZ.UTF-8'
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is
> /var/run/weewx.pid
> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system:
> weewx.
> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather
> system.
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using
> configuration file /etc/weewx/weewx.conf
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing
> engine
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading
> station type Vantage (weewx.drivers.vantage)
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Driver version is 3.2.1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Option loop_request=1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement
> from fe80::724f:57ff:feb7:82a1
> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Retry #0 failed
> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Retry #1 failed
> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Retry #2 failed
> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement
> from fe80::724f:57ff:feb7:82a1
> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage:
> Retry #3 failed
> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.drivers.vantage:
> Unable to wake up console
> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.engine: Import of
> driver failed: Unable to wake up Vantage console ( 'weewx.WakeupError'>)
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:
>    Traceback (most recent call last):
> Feb 26 16:31:48 We

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

The screen shows blank when I get to the point above.after hitting 
enter a few times, it just sends the cursor down the screen..I tried 
typing TEST but no response...just a dark screen in the CL window.


On Sunday, 28 February 2021 at 11:49:11 UTC+13 gjr80 wrote:

> That’s a better start, did you hit enter a few times and then send TEST as 
> per the wiki article 
> ?
>  
> You should get a response from the Envoy.
>
> Gary
>
> On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:
>
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ sudo killall screen
>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>> /run/user/1000/gvfs
>>   Output information may be incomplete.
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>
>>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 11:00:42
>>
>> Press CTRL-A Z for help on special keys
>>
>>
>> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com wrote:
>>
>>> Monmul, we have not definitively heard whether or not you are able to do 
>>> the test listed under *Establishing connectivity 
>>> *
>>>  in 
>>> the Wiki.That is an essential first step.
>>>
>>> Use either screen or minicom. You may have to preface the command with '
>>> sudo'. For example,
>>>
>>>
>>> *sudo screen /dev/ttyUSB0 19200*
>>>
>>> -tk
>>>
>>> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>>>
 Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
 system...
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing 
 weewx version 4.4.0
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 
 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
 Linux-4.19.66-v7+-armv7l-with-debian-9.13
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
 'en_NZ.UTF-8'
 Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
 /var/run/weewx.pid
 Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system: 
 weewx.
 Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather system.
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
 configuration file /etc/weewx/weewx.conf
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing 
 engine
 Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
 station type Vantage (weewx.drivers.vantage)
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Driver version is 3.2.1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Option loop_request=1
 Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
 Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
 fe80::724f:57ff:feb7:82a1
 Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
 Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Retry #0 failed
 Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Retry #1 failed
 Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Retry #2 failed
 Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
 fe80::724f:57ff:feb7:82a1
 Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
 Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
 Retry #3 failed
 Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.drivers.vantage: 
 Unable to wake up console
 Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.engine: Import of 
 driver failed: Unable to wake up Vantage console (>>> 'weewx.WakeupError'>)
 Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
 Traceback (most recent call last):
 Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
   File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
 Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
 self.console = loader_function(config_dict, self)
 Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
   File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
 Feb 26 16:31:48 Weath

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

That’s a better start, did you hit enter a few times and then send TEST as 
per the wiki article 
?
 
You should get a response from the Envoy.

Gary

On Sunday, 28 February 2021 at 08:04:10 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo killall screen
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
>   Output information may be incomplete.
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>
>
> Welcome to minicom 2.7
>
> OPTIONS: I18n 
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 11:00:42
>
> Press CTRL-A Z for help on special keys
>
>
> On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com wrote:
>
>> Monmul, we have not definitively heard whether or not you are able to do 
>> the test listed under *Establishing connectivity 
>> *
>>  in 
>> the Wiki.That is an essential first step.
>>
>> Use either screen or minicom. You may have to preface the command with '
>> sudo'. For example,
>>
>>
>> *sudo screen /dev/ttyUSB0 19200*
>>
>> -tk
>>
>> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>>
>>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
>>> system...
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing weewx 
>>> version 4.4.0
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 
>>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
>>> 'en_NZ.UTF-8'
>>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
>>> /var/run/weewx.pid
>>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system: 
>>> weewx.
>>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather system.
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using 
>>> configuration file /etc/weewx/weewx.conf
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing 
>>> engine
>>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading 
>>> station type Vantage (weewx.drivers.vantage)
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Driver version is 3.2.1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Option loop_request=1
>>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>>> fe80::724f:57ff:feb7:82a1
>>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>>> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Retry #0 failed
>>> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Retry #1 failed
>>> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Retry #2 failed
>>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>>> fe80::724f:57ff:feb7:82a1
>>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>>> Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>>> Retry #3 failed
>>> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.drivers.vantage: 
>>> Unable to wake up console
>>> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.engine: Import of 
>>> driver failed: Unable to wake up Vantage console (>> 'weewx.WakeupError'>)
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>> Traceback (most recent call last):
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>>   File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>> self.console = loader_function(config_dict, self)
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>> return VantageService(engine, config_dict)
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
>>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>>> Vantage.__init__(self, **config_dict[DRIVER_NAM

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
minicom: cannot open /dev/ttyUSB0: Device or resource busy
pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ sudo killall screen
pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0


Welcome to minicom 2.7

OPTIONS: I18n 
Compiled on Apr 22 2017, 09:14:19.
Port /dev/ttyUSB0, 11:00:42

Press CTRL-A Z for help on special keys


On Saturday, 27 February 2021 at 02:19:42 UTC+13 tke...@gmail.com wrote:

> Monmul, we have not definitively heard whether or not you are able to do 
> the test listed under *Establishing connectivity 
> *
>  in 
> the Wiki.That is an essential first step.
>
> Use either screen or minicom. You may have to preface the command with '
> sudo'. For example,
>
>
> *sudo screen /dev/ttyUSB0 19200*
>
> -tk
>
> On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:
>
>> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing weewx 
>> version 4.4.0
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 2.7.13 
>> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
>> 'en_NZ.UTF-8'
>> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system: 
>> weewx.
>> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather system.
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using configuration 
>> file /etc/weewx/weewx.conf
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing engine
>> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading station 
>> type Vantage (weewx.drivers.vantage)
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Driver version is 3.2.1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Option loop_request=1
>> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: 
>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
>> #0 failed
>> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
>> #1 failed
>> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
>> #2 failed
>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>> Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
>> #3 failed
>> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.drivers.vantage: 
>> Unable to wake up console
>> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.engine: Import of 
>> driver failed: Unable to wake up Vantage console (> 'weewx.WakeupError'>)
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
>> Traceback (most recent call last):
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>>   self.console = loader_function(config_dict, self)
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>>   return VantageService(engine, config_dict)
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>>   self._setup()
>> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
>> Feb 26 16:31:48 WeatherPi w

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

Monmul, we have not definitively heard whether or not you are able to do
the test listed under *Establishing connectivity
*
in
the Wiki.That is an essential first step.

Use either screen or minicom. You may have to preface the command with 'sudo'.
For example,


*sudo screen /dev/ttyUSB0 19200*

-tk

On Thu, Feb 25, 2021 at 7:34 PM monmul  wrote:

> Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather system...
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing weewx
> version 4.4.0
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 2.7.13
> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is
> 'en_NZ.UTF-8'
> Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is
> /var/run/weewx.pid
> Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system:
> weewx.
> Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather system.
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using configuration
> file /etc/weewx/weewx.conf
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing engine
> Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading station
> type Vantage (weewx.drivers.vantage)
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Driver
> version is 3.2.1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Option
> loop_request=1
> Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Opened
> up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from
> fe80::724f:57ff:feb7:82a1
> Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry
> #0 failed
> Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry
> #1 failed
> Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry
> #2 failed
> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from
> fe80::724f:57ff:feb7:82a1
> Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry
> #3 failed
> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.drivers.vantage: Unable
> to wake up console
> Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.engine: Import of
> driver failed: Unable to wake up Vantage console ( 'weewx.WakeupError'>)
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
> Traceback (most recent call last):
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>   self.console = loader_function(config_dict, self)
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>   return VantageService(engine, config_dict)
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>   self._setup()
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>   self.port.wakeup_console(max_tries=self.max_tries)
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in
> wakeup_console
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
>   raise weewx.WakeupError("Unable to wake up Vantage console")
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
> WakeupError: Unable to wake up Vantage console
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL __main__: Unable to load
> driver: Unable to wake up Vantage console
> Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL __main__: 
> Exiting...
> Feb 26 16:31:50 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from
> fe80::724f:57ff:feb7:82a1
> Feb 26 16:31:50

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Feb 26 16:31:31 WeatherPi systemd[1]: Starting LSB: weewx weather system...
Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Initializing weewx 
version 4.4.0
Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Using Python 2.7.13 
(default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Platform 
Linux-4.19.66-v7+-armv7l-with-debian-9.13
Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: Locale is 
'en_NZ.UTF-8'
Feb 26 16:31:32 WeatherPi weewx[17966] INFO __main__: PID file is 
/var/run/weewx.pid
Feb 26 16:31:32 WeatherPi weewx[17954]: Starting weewx weather system: 
weewx.
Feb 26 16:31:32 WeatherPi systemd[1]: Started LSB: weewx weather system.
Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Feb 26 16:31:32 WeatherPi weewx[17971] INFO __main__: Debug is 1
Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG __main__: Initializing engine
Feb 26 16:31:32 WeatherPi weewx[17971] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Driver 
version is 3.2.1
Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Option 
loop_request=1
Feb 26 16:31:32 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Opened 
up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 26 16:31:36 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 26 16:31:36 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
#0 failed
Feb 26 16:31:40 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
#1 failed
Feb 26 16:31:44 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
#2 failed
Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 26 16:31:45 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 26 16:31:48 WeatherPi weewx[17971] DEBUG weewx.drivers.vantage: Retry 
#3 failed
Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.drivers.vantage: Unable 
to wake up console
Feb 26 16:31:48 WeatherPi weewx[17971] ERROR weewx.engine: Import of driver 
failed: Unable to wake up Vantage console ()
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
Traceback (most recent call last):
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
self.console = loader_function(config_dict, self)
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
return VantageService(engine, config_dict)
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
Vantage.__init__(self, **config_dict[DRIVER_NAME])
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
self._setup()
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
self.port.wakeup_console(max_tries=self.max_tries)
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in 
wakeup_console
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
raise weewx.WakeupError("Unable to wake up Vantage console")
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL weewx.engine:   
WakeupError: Unable to wake up Vantage console
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL __main__: Unable to load 
driver: Unable to wake up Vantage console
Feb 26 16:31:48 WeatherPi weewx[17971] CRITICAL __main__:   
Exiting...
Feb 26 16:31:50 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 26 16:31:50 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 26 16:31:58 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 26 16:31:58 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 26 16:32:07 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 26 16:32:07 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 26 16:32:15 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 26 16:32:15 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCP

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[vince]

So go ahead and restart it now.

On Thursday, February 25, 2021 at 1:02:41 PM UTC-8 monmul wrote:

> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo killall screen
> screen: no process found
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
>   Output information may be incomplete.
> pi@WeatherPi:~ $ ps -ef | grep -e weewxd -e screen
> pi3809 11222  0 10:01 pts/100:00:00 grep --color=auto -e 
> weewxd -e screen
> pi@WeatherPi:~ $ 
>
> On Thursday, 25 February 2021 at 21:57:53 UTC+13 graha...@gmail.com wrote:
>
>> vnc makes no relevant difference.
>> command = ‘screen’ below shows program ‘screen’ has a ‘pi’ user process 
>> open on /dev/ttyUSB0 at the moment. not weewxd. probably left over from 
>> earlier troubleshooting.
>> kill it with “sudo killall screen”.
>> check if any weewxd’s or screen’s hanging around with “ps -ef | grep -e 
>> weewxd -e screen”. kill them if you find any.
>> you should now be back to a clean state with /devttyUSB0 ready for 
>> opening. do “sudo lsof /dev/ttyUSB0” to be sure
>>
>> On 25 Feb 2021, at 5:24 pm, gjr80  wrote:
>>
>> I don't know, I'm a SSH only person, I am getting out of my depth now.
>>
>> Gary
>>
>> On Thursday, 25 February 2021 at 16:21:11 UTC+10 monmul wrote:
>>
>>> I am using VNC Viewer (and always have) rather than SSHnot sure if 
>>> that makes any difference?
>>>
>>> On Thursday, 25 February 2021 at 19:13:29 UTC+13 gjr80 wrote:
>>>
 Hmm, different to my Davis on my RPi which shows weewxd rather than 
 screen. I will have to defer to Tom or someone who knows about screen.

 Gary

 On Thursday, 25 February 2021 at 15:58:07 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
> /run/user/1000/gvfs
>   Output information may be incomplete.
> COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
> screen  16582   pi6u   CHR  188,0  0t0 20196 /dev/ttyUSB0
> pi@WeatherPi:~ $ 
>
>
>>

-- 
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/4888737c-3a87-47f9-a50c-83dce3313108n%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ sudo killall screen
screen: no process found
pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
pi@WeatherPi:~ $ ps -ef | grep -e weewxd -e screen
pi3809 11222  0 10:01 pts/100:00:00 grep --color=auto -e weewxd 
-e screen
pi@WeatherPi:~ $ 

On Thursday, 25 February 2021 at 21:57:53 UTC+13 graha...@gmail.com wrote:

> vnc makes no relevant difference.
> command = ‘screen’ below shows program ‘screen’ has a ‘pi’ user process 
> open on /dev/ttyUSB0 at the moment. not weewxd. probably left over from 
> earlier troubleshooting.
> kill it with “sudo killall screen”.
> check if any weewxd’s or screen’s hanging around with “ps -ef | grep -e 
> weewxd -e screen”. kill them if you find any.
> you should now be back to a clean state with /devttyUSB0 ready for 
> opening. do “sudo lsof /dev/ttyUSB0” to be sure
>
> On 25 Feb 2021, at 5:24 pm, gjr80  wrote:
>
> I don't know, I'm a SSH only person, I am getting out of my depth now.
>
> Gary
>
> On Thursday, 25 February 2021 at 16:21:11 UTC+10 monmul wrote:
>
>> I am using VNC Viewer (and always have) rather than SSHnot sure if 
>> that makes any difference?
>>
>> On Thursday, 25 February 2021 at 19:13:29 UTC+13 gjr80 wrote:
>>
>>> Hmm, different to my Davis on my RPi which shows weewxd rather than 
>>> screen. I will have to defer to Tom or someone who knows about screen.
>>>
>>> Gary
>>>
>>> On Thursday, 25 February 2021 at 15:58:07 UTC+10 monmul wrote:
>>>
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
 /run/user/1000/gvfs
   Output information may be incomplete.
 COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
 screen  16582   pi6u   CHR  188,0  0t0 20196 /dev/ttyUSB0
 pi@WeatherPi:~ $ 


>

-- 
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/0cb90854-d683-4fb3-8ac3-aa8b1d48fb20n%40googlegroups.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Graham Eddy]

vnc makes no relevant difference.
command = ‘screen’ below shows program ‘screen’ has a ‘pi’ user process open on 
/dev/ttyUSB0 at the moment. not weewxd. probably left over from earlier 
troubleshooting.
kill it with “sudo killall screen”.
check if any weewxd’s or screen’s hanging around with “ps -ef | grep -e weewxd 
-e screen”. kill them if you find any.
you should now be back to a clean state with /devttyUSB0 ready for opening. do 
“sudo lsof /dev/ttyUSB0” to be sure

> On 25 Feb 2021, at 5:24 pm, gjr80  wrote:
> 
> I don't know, I'm a SSH only person, I am getting out of my depth now.
> 
> Gary
> 
> On Thursday, 25 February 2021 at 16:21:11 UTC+10 monmul wrote:
> I am using VNC Viewer (and always have) rather than SSHnot sure if that 
> makes any difference?
> 
> On Thursday, 25 February 2021 at 19:13:29 UTC+13 gjr80 wrote:
> Hmm, different to my Davis on my RPi which shows weewxd rather than screen. I 
> will have to defer to Tom or someone who knows about screen.
> 
> Gary
> 
> On Thursday, 25 February 2021 at 15:58:07 UTC+10 monmul wrote:
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
>   Output information may be incomplete.
> COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
> screen  16582   pi6u   CHR  188,0  0t0 20196 /dev/ttyUSB0
> pi@WeatherPi:~ $ 
> 

-- 
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/3FE5D7F5-535A-4DB7-94BD-9D3C11D6A47B%40gmail.com.

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

I don't know, I'm a SSH only person, I am getting out of my depth now.

Gary

On Thursday, 25 February 2021 at 16:21:11 UTC+10 monmul wrote:

> I am using VNC Viewer (and always have) rather than SSHnot sure if 
> that makes any difference?
>
> On Thursday, 25 February 2021 at 19:13:29 UTC+13 gjr80 wrote:
>
>> Hmm, different to my Davis on my RPi which shows weewxd rather than 
>> screen. I will have to defer to Tom or someone who knows about screen.
>>
>> Gary
>>
>> On Thursday, 25 February 2021 at 15:58:07 UTC+10 monmul wrote:
>>
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>>> /run/user/1000/gvfs
>>>   Output information may be incomplete.
>>> COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
>>> screen  16582   pi6u   CHR  188,0  0t0 20196 /dev/ttyUSB0
>>> pi@WeatherPi:~ $ 
>>>
>>>
>>>
>>> On Thursday, 25 February 2021 at 17:46:35 UTC+13 gjr80 wrote:
>>>
 I thought it was installed by default on RPi OS but seems lt it is not 
 - it works on my RPi, I must have installed it manually. Try:

 $ sudo apt update
 $ sudo apt install lsof

 then try running lsof.

 Gary

 On Thursday, 25 February 2021 at 14:19:30 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
> bash: lsof: command not found
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
> bash: lsof: command not found
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> sudo: lsof: command not found
> pi@WeatherPi:~ $ 
>
>
>
> On Thursday, 25 February 2021 at 17:17:03 UTC+13 gjr80 wrote:
>
>> Try prefixing lsof with sudo.
>>
>> Gary
>>
>> On Thursday, 25 February 2021 at 14:15:17 UTC+10 monmul wrote:
>>
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>>> bash: lsof: command not found
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>>> bash: lsof: command not found
>>> pi@WeatherPi:~ $ 
>>>
>>>
>>> On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com 
>>> wrote:
>>>
 Make sure you stop weewx first before trying minicom. There cannot 
 be anything else using the port. To see what devices are using a port:

 *lsof /dev/ttyUSB0*



 On Tue, Feb 23, 2021 at 9:19 PM monmul  wrote:

> No change in USB port.
>
> pi@WeatherPi:~ $ 
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ 
> pi@WeatherPi:~ $ 
> pi@WeatherPi:~ $ 
> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>
> [screen is terminating]
> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [screen is terminating]
> pi@WeatherPi:~ $ TEST
> bash: TEST: command not found
> pi@WeatherPi:~ $ 
>
>
> On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote:
>
>> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert 
>> but I am told they behave just like a console. First thing I would 
>> do is 
>> test connectivity from your RPi to the Envoy. Any chance the Envoy 
>> is now 
>> on a different USB port? Not sure if you remember the Establishing 
>> connectivity 
>> 
>>  
>> testing Tom got you to work through a couple of years back, but that 
>> is a 
>> good place to start. The instructions are now in the wiki rather 
>> than the 
>> User Guide but the link I have provided should work.
>>
>> Gary
>> On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:
>>
>>> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx 
>

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

I am using VNC Viewer (and always have) rather than SSHnot sure if that 
makes any difference?

On Thursday, 25 February 2021 at 19:13:29 UTC+13 gjr80 wrote:

> Hmm, different to my Davis on my RPi which shows weewxd rather than 
> screen. I will have to defer to Tom or someone who knows about screen.
>
> Gary
>
> On Thursday, 25 February 2021 at 15:58:07 UTC+10 monmul wrote:
>
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system 
>> /run/user/1000/gvfs
>>   Output information may be incomplete.
>> COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
>> screen  16582   pi6u   CHR  188,0  0t0 20196 /dev/ttyUSB0
>> pi@WeatherPi:~ $ 
>>
>>
>>
>> On Thursday, 25 February 2021 at 17:46:35 UTC+13 gjr80 wrote:
>>
>>> I thought it was installed by default on RPi OS but seems lt it is not - 
>>> it works on my RPi, I must have installed it manually. Try:
>>>
>>> $ sudo apt update
>>> $ sudo apt install lsof
>>>
>>> then try running lsof.
>>>
>>> Gary
>>>
>>> On Thursday, 25 February 2021 at 14:19:30 UTC+10 monmul wrote:
>>>
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ lsof /dev/ttyUSB0
 bash: lsof: command not found
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Device or resource busy
 pi@WeatherPi:~ $ lsof /dev/ttyUSB0
 bash: lsof: command not found
 pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
 sudo: lsof: command not found
 pi@WeatherPi:~ $ 



 On Thursday, 25 February 2021 at 17:17:03 UTC+13 gjr80 wrote:

> Try prefixing lsof with sudo.
>
> Gary
>
> On Thursday, 25 February 2021 at 14:15:17 UTC+10 monmul wrote:
>
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>> bash: lsof: command not found
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>> bash: lsof: command not found
>> pi@WeatherPi:~ $ 
>>
>>
>> On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com 
>> wrote:
>>
>>> Make sure you stop weewx first before trying minicom. There cannot 
>>> be anything else using the port. To see what devices are using a port:
>>>
>>> *lsof /dev/ttyUSB0*
>>>
>>>
>>>
>>> On Tue, Feb 23, 2021 at 9:19 PM monmul  wrote:
>>>
 No change in USB port.

 pi@WeatherPi:~ $ 
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Device or resource busy
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Device or resource busy
 pi@WeatherPi:~ $ 
 pi@WeatherPi:~ $ 
 pi@WeatherPi:~ $ 
 pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200

 [screen is terminating]
 pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200






















 [screen is terminating]
 pi@WeatherPi:~ $ TEST
 bash: TEST: command not found
 pi@WeatherPi:~ $ 


 On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote:

> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert 
> but I am told they behave just like a console. First thing I would do 
> is 
> test connectivity from your RPi to the Envoy. Any chance the Envoy is 
> now 
> on a different USB port? Not sure if you remember the Establishing 
> connectivity 
> 
>  
> testing Tom got you to work through a couple of years back, but that 
> is a 
> good place to start. The instructions are now in the wiki rather than 
> the 
> User Guide but the link I have provided should work.
>
> Gary
> On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:
>
>> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: 
>> Initializing weewx version 4.4.0
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using 
>> Python 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 
>

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

Hmm, different to my Davis on my RPi which shows weewxd rather than screen. 
I will have to defer to Tom or someone who knows about screen.

Gary

On Thursday, 25 February 2021 at 15:58:07 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
>   Output information may be incomplete.
> COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
> screen  16582   pi6u   CHR  188,0  0t0 20196 /dev/ttyUSB0
> pi@WeatherPi:~ $ 
>
>
>
> On Thursday, 25 February 2021 at 17:46:35 UTC+13 gjr80 wrote:
>
>> I thought it was installed by default on RPi OS but seems lt it is not - 
>> it works on my RPi, I must have installed it manually. Try:
>>
>> $ sudo apt update
>> $ sudo apt install lsof
>>
>> then try running lsof.
>>
>> Gary
>>
>> On Thursday, 25 February 2021 at 14:19:30 UTC+10 monmul wrote:
>>
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>>> bash: lsof: command not found
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>>> bash: lsof: command not found
>>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>>> sudo: lsof: command not found
>>> pi@WeatherPi:~ $ 
>>>
>>>
>>>
>>> On Thursday, 25 February 2021 at 17:17:03 UTC+13 gjr80 wrote:
>>>
 Try prefixing lsof with sudo.

 Gary

 On Thursday, 25 February 2021 at 14:15:17 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
> bash: lsof: command not found
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
> bash: lsof: command not found
> pi@WeatherPi:~ $ 
>
>
> On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com 
> wrote:
>
>> Make sure you stop weewx first before trying minicom. There cannot be 
>> anything else using the port. To see what devices are using a port:
>>
>> *lsof /dev/ttyUSB0*
>>
>>
>>
>> On Tue, Feb 23, 2021 at 9:19 PM monmul  wrote:
>>
>>> No change in USB port.
>>>
>>> pi@WeatherPi:~ $ 
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ 
>>> pi@WeatherPi:~ $ 
>>> pi@WeatherPi:~ $ 
>>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>>>
>>> [screen is terminating]
>>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> [screen is terminating]
>>> pi@WeatherPi:~ $ TEST
>>> bash: TEST: command not found
>>> pi@WeatherPi:~ $ 
>>>
>>>
>>> On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote:
>>>
 OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but 
 I am told they behave just like a console. First thing I would do is 
 test 
 connectivity from your RPi to the Envoy. Any chance the Envoy is now 
 on a 
 different USB port? Not sure if you remember the Establishing 
 connectivity 
 
  
 testing Tom got you to work through a couple of years back, but that 
 is a 
 good place to start. The instructions are now in the wiki rather than 
 the 
 User Guide but the link I have provided should work.

 Gary
 On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:

> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather 
> system...
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing 
> weewx version 4.4.0
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 
> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
> 'en_NZ.UTF-8'
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
> /var/r

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
  Output information may be incomplete.
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
screen  16582   pi6u   CHR  188,0  0t0 20196 /dev/ttyUSB0
pi@WeatherPi:~ $ 



On Thursday, 25 February 2021 at 17:46:35 UTC+13 gjr80 wrote:

> I thought it was installed by default on RPi OS but seems lt it is not - 
> it works on my RPi, I must have installed it manually. Try:
>
> $ sudo apt update
> $ sudo apt install lsof
>
> then try running lsof.
>
> Gary
>
> On Thursday, 25 February 2021 at 14:19:30 UTC+10 monmul wrote:
>
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>> bash: lsof: command not found
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>> bash: lsof: command not found
>> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
>> sudo: lsof: command not found
>> pi@WeatherPi:~ $ 
>>
>>
>>
>> On Thursday, 25 February 2021 at 17:17:03 UTC+13 gjr80 wrote:
>>
>>> Try prefixing lsof with sudo.
>>>
>>> Gary
>>>
>>> On Thursday, 25 February 2021 at 14:15:17 UTC+10 monmul wrote:
>>>
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ lsof /dev/ttyUSB0
 bash: lsof: command not found
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Device or resource busy
 pi@WeatherPi:~ $ lsof /dev/ttyUSB0
 bash: lsof: command not found
 pi@WeatherPi:~ $ 


 On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com 
 wrote:

> Make sure you stop weewx first before trying minicom. There cannot be 
> anything else using the port. To see what devices are using a port:
>
> *lsof /dev/ttyUSB0*
>
>
>
> On Tue, Feb 23, 2021 at 9:19 PM monmul  wrote:
>
>> No change in USB port.
>>
>> pi@WeatherPi:~ $ 
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ 
>> pi@WeatherPi:~ $ 
>> pi@WeatherPi:~ $ 
>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>>
>> [screen is terminating]
>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> [screen is terminating]
>> pi@WeatherPi:~ $ TEST
>> bash: TEST: command not found
>> pi@WeatherPi:~ $ 
>>
>>
>> On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote:
>>
>>> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but 
>>> I am told they behave just like a console. First thing I would do is 
>>> test 
>>> connectivity from your RPi to the Envoy. Any chance the Envoy is now on 
>>> a 
>>> different USB port? Not sure if you remember the Establishing 
>>> connectivity 
>>> 
>>>  
>>> testing Tom got you to work through a couple of years back, but that is 
>>> a 
>>> good place to start. The instructions are now in the wiki rather than 
>>> the 
>>> User Guide but the link I have provided should work.
>>>
>>> Gary
>>> On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:
>>>
 Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather 
 system...
 Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing 
 weewx version 4.4.0
 Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 
 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
 Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
 Linux-4.19.66-v7+-armv7l-with-debian-9.13
 Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
 'en_NZ.UTF-8'
 Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
 /var/run/weewx.pid
 Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather 
 system: weewx.
 Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather 
 system.
 Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using 
 configuration file /etc/weewx/weewx.conf
 Feb 22 22:39:03 WeatherPi weewx[249

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

I thought it was installed by default on RPi OS but seems lt it is not - it 
works on my RPi, I must have installed it manually. Try:

$ sudo apt update
$ sudo apt install lsof

then try running lsof.

Gary

On Thursday, 25 February 2021 at 14:19:30 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
> bash: lsof: command not found
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
> bash: lsof: command not found
> pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
> sudo: lsof: command not found
> pi@WeatherPi:~ $ 
>
>
>
> On Thursday, 25 February 2021 at 17:17:03 UTC+13 gjr80 wrote:
>
>> Try prefixing lsof with sudo.
>>
>> Gary
>>
>> On Thursday, 25 February 2021 at 14:15:17 UTC+10 monmul wrote:
>>
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>>> bash: lsof: command not found
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>>> bash: lsof: command not found
>>> pi@WeatherPi:~ $ 
>>>
>>>
>>> On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com wrote:
>>>
 Make sure you stop weewx first before trying minicom. There cannot be 
 anything else using the port. To see what devices are using a port:

 *lsof /dev/ttyUSB0*



 On Tue, Feb 23, 2021 at 9:19 PM monmul  wrote:

> No change in USB port.
>
> pi@WeatherPi:~ $ 
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ 
> pi@WeatherPi:~ $ 
> pi@WeatherPi:~ $ 
> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>
> [screen is terminating]
> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [screen is terminating]
> pi@WeatherPi:~ $ TEST
> bash: TEST: command not found
> pi@WeatherPi:~ $ 
>
>
> On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote:
>
>> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I 
>> am told they behave just like a console. First thing I would do is test 
>> connectivity from your RPi to the Envoy. Any chance the Envoy is now on 
>> a 
>> different USB port? Not sure if you remember the Establishing 
>> connectivity 
>> 
>>  
>> testing Tom got you to work through a couple of years back, but that is 
>> a 
>> good place to start. The instructions are now in the wiki rather than 
>> the 
>> User Guide but the link I have provided should work.
>>
>> Gary
>> On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:
>>
>>> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather 
>>> system...
>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing 
>>> weewx version 4.4.0
>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 
>>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
>>> 'en_NZ.UTF-8'
>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
>>> /var/run/weewx.pid
>>> Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather 
>>> system: weewx.
>>> Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather 
>>> system.
>>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using 
>>> configuration file /etc/weewx/weewx.conf
>>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1
>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing 
>>> engine
>>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading 
>>> station type Vantage (weewx.drivers.vantage)
>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>>> Driver version is 3.2.1
>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>>> Option loop_request=1
>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>>> Feb 22 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ lsof /dev/ttyUSB0
bash: lsof: command not found
pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
minicom: cannot open /dev/ttyUSB0: Device or resource busy
pi@WeatherPi:~ $ lsof /dev/ttyUSB0
bash: lsof: command not found
pi@WeatherPi:~ $ sudo lsof /dev/ttyUSB0
sudo: lsof: command not found
pi@WeatherPi:~ $ 



On Thursday, 25 February 2021 at 17:17:03 UTC+13 gjr80 wrote:

> Try prefixing lsof with sudo.
>
> Gary
>
> On Thursday, 25 February 2021 at 14:15:17 UTC+10 monmul wrote:
>
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>> bash: lsof: command not found
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
>> bash: lsof: command not found
>> pi@WeatherPi:~ $ 
>>
>>
>> On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com wrote:
>>
>>> Make sure you stop weewx first before trying minicom. There cannot be 
>>> anything else using the port. To see what devices are using a port:
>>>
>>> *lsof /dev/ttyUSB0*
>>>
>>>
>>>
>>> On Tue, Feb 23, 2021 at 9:19 PM monmul  wrote:
>>>
 No change in USB port.

 pi@WeatherPi:~ $ 
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Device or resource busy
 pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
 minicom: cannot open /dev/ttyUSB0: Device or resource busy
 pi@WeatherPi:~ $ 
 pi@WeatherPi:~ $ 
 pi@WeatherPi:~ $ 
 pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200

 [screen is terminating]
 pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200






















 [screen is terminating]
 pi@WeatherPi:~ $ TEST
 bash: TEST: command not found
 pi@WeatherPi:~ $ 


 On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote:

> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I 
> am told they behave just like a console. First thing I would do is test 
> connectivity from your RPi to the Envoy. Any chance the Envoy is now on a 
> different USB port? Not sure if you remember the Establishing 
> connectivity 
> 
>  
> testing Tom got you to work through a couple of years back, but that is a 
> good place to start. The instructions are now in the wiki rather than the 
> User Guide but the link I have provided should work.
>
> Gary
> On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:
>
>> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing 
>> weewx version 4.4.0
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 
>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
>> 'en_NZ.UTF-8'
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather 
>> system: weewx.
>> Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather 
>> system.
>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using 
>> configuration file /etc/weewx/weewx.conf
>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing 
>> engine
>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>> Driver version is 3.2.1
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>> Option loop_request=1
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement 
>> from fe80::724f:57ff:feb7:82a1
>> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 
>> lease
>> Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>> Retry #0 failed
>> Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>> Retry #1 failed
>> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: Route

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

Try prefixing lsof with sudo.

Gary

On Thursday, 25 February 2021 at 14:15:17 UTC+10 monmul wrote:

> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
> bash: lsof: command not found
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ lsof /dev/ttyUSB0
> bash: lsof: command not found
> pi@WeatherPi:~ $ 
>
>
> On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com wrote:
>
>> Make sure you stop weewx first before trying minicom. There cannot be 
>> anything else using the port. To see what devices are using a port:
>>
>> *lsof /dev/ttyUSB0*
>>
>>
>>
>> On Tue, Feb 23, 2021 at 9:19 PM monmul  wrote:
>>
>>> No change in USB port.
>>>
>>> pi@WeatherPi:~ $ 
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>>> pi@WeatherPi:~ $ 
>>> pi@WeatherPi:~ $ 
>>> pi@WeatherPi:~ $ 
>>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>>>
>>> [screen is terminating]
>>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> [screen is terminating]
>>> pi@WeatherPi:~ $ TEST
>>> bash: TEST: command not found
>>> pi@WeatherPi:~ $ 
>>>
>>>
>>> On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote:
>>>
 OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I 
 am told they behave just like a console. First thing I would do is test 
 connectivity from your RPi to the Envoy. Any chance the Envoy is now on a 
 different USB port? Not sure if you remember the Establishing 
 connectivity 
 
  
 testing Tom got you to work through a couple of years back, but that is a 
 good place to start. The instructions are now in the wiki rather than the 
 User Guide but the link I have provided should work.

 Gary
 On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:

> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather 
> system...
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing 
> weewx version 4.4.0
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 
> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
> 'en_NZ.UTF-8'
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
> /var/run/weewx.pid
> Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather system: 
> weewx.
> Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather 
> system.
> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using 
> configuration file /etc/weewx/weewx.conf
> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing 
> engine
> Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading 
> station type Vantage (weewx.drivers.vantage)
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
> Driver version is 3.2.1
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
> Option loop_request=1
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement 
> from fe80::724f:57ff:feb7:82a1
> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
> Retry #0 failed
> Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
> Retry #1 failed
> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: Router Advertisement 
> from fe80::724f:57ff:feb7:82a1
> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 22:39:15 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
> Retry #2 failed
> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement 
> from fe80::724f:57ff:feb7:82a1
> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 22:39:19 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
> Retry #3 failed
> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.drivers.vantage: 
> Unable to wake up console
> 

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ lsof /dev/ttyUSB0
bash: lsof: command not found
pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
minicom: cannot open /dev/ttyUSB0: Device or resource busy
pi@WeatherPi:~ $ lsof /dev/ttyUSB0
bash: lsof: command not found
pi@WeatherPi:~ $ 


On Thursday, 25 February 2021 at 02:13:31 UTC+13 tke...@gmail.com wrote:

> Make sure you stop weewx first before trying minicom. There cannot be 
> anything else using the port. To see what devices are using a port:
>
> *lsof /dev/ttyUSB0*
>
>
>
> On Tue, Feb 23, 2021 at 9:19 PM monmul  wrote:
>
>> No change in USB port.
>>
>> pi@WeatherPi:~ $ 
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
>> minicom: cannot open /dev/ttyUSB0: Device or resource busy
>> pi@WeatherPi:~ $ 
>> pi@WeatherPi:~ $ 
>> pi@WeatherPi:~ $ 
>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>>
>> [screen is terminating]
>> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> [screen is terminating]
>> pi@WeatherPi:~ $ TEST
>> bash: TEST: command not found
>> pi@WeatherPi:~ $ 
>>
>>
>> On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote:
>>
>>> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I am 
>>> told they behave just like a console. First thing I would do is test 
>>> connectivity from your RPi to the Envoy. Any chance the Envoy is now on a 
>>> different USB port? Not sure if you remember the Establishing 
>>> connectivity 
>>> 
>>>  
>>> testing Tom got you to work through a couple of years back, but that is a 
>>> good place to start. The instructions are now in the wiki rather than the 
>>> User Guide but the link I have provided should work.
>>>
>>> Gary
>>> On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:
>>>
 Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather 
 system...
 Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing 
 weewx version 4.4.0
 Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 
 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
 Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
 Linux-4.19.66-v7+-armv7l-with-debian-9.13
 Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
 'en_NZ.UTF-8'
 Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
 /var/run/weewx.pid
 Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather system: 
 weewx.
 Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather system.
 Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using 
 configuration file /etc/weewx/weewx.conf
 Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1
 Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing 
 engine
 Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading 
 station type Vantage (weewx.drivers.vantage)
 Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
 Driver version is 3.2.1
 Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
 Option loop_request=1
 Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
 Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
 Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
 fe80::724f:57ff:feb7:82a1
 Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
 Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
 Retry #0 failed
 Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
 Retry #1 failed
 Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
 fe80::724f:57ff:feb7:82a1
 Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
 Feb 22 22:39:15 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
 Retry #2 failed
 Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
 fe80::724f:57ff:feb7:82a1
 Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
 Feb 22 22:39:19 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
 Retry #3 failed
 Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.drivers.vantage: 
 Unable to wake up console
 Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.engine: Import of 
 driver failed: Unable to wake up Vantage console (>>> 'weewx.WakeupError'>)
 Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
 Traceback (mos

Re: [weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[Tom Keffer]

Make sure you stop weewx first before trying minicom. There cannot be
anything else using the port. To see what devices are using a port:

*lsof /dev/ttyUSB0*



On Tue, Feb 23, 2021 at 9:19 PM monmul  wrote:

> No change in USB port.
>
> pi@WeatherPi:~ $
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
> minicom: cannot open /dev/ttyUSB0: Device or resource busy
> pi@WeatherPi:~ $
> pi@WeatherPi:~ $
> pi@WeatherPi:~ $
> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>
> [screen is terminating]
> pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [screen is terminating]
> pi@WeatherPi:~ $ TEST
> bash: TEST: command not found
> pi@WeatherPi:~ $
>
>
> On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote:
>
>> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I am
>> told they behave just like a console. First thing I would do is test
>> connectivity from your RPi to the Envoy. Any chance the Envoy is now on a
>> different USB port? Not sure if you remember the Establishing
>> connectivity
>> 
>> testing Tom got you to work through a couple of years back, but that is a
>> good place to start. The instructions are now in the wiki rather than the
>> User Guide but the link I have provided should work.
>>
>> Gary
>> On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:
>>
>>> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather
>>> system...
>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing weewx
>>> version 4.4.0
>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python
>>> 2.7.13 (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform
>>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is
>>> 'en_NZ.UTF-8'
>>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is
>>> /var/run/weewx.pid
>>> Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather system:
>>> weewx.
>>> Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather system.
>>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using
>>> configuration file /etc/weewx/weewx.conf
>>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1
>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing
>>> engine
>>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading
>>> station type Vantage (weewx.drivers.vantage)
>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage:
>>> Driver version is 3.2.1
>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage:
>>> Option loop_request=1
>>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage:
>>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>>> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from
>>> fe80::724f:57ff:feb7:82a1
>>> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>>> Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage:
>>> Retry #0 failed
>>> Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage:
>>> Retry #1 failed
>>> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from
>>> fe80::724f:57ff:feb7:82a1
>>> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>>> Feb 22 22:39:15 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage:
>>> Retry #2 failed
>>> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from
>>> fe80::724f:57ff:feb7:82a1
>>> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>>> Feb 22 22:39:19 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage:
>>> Retry #3 failed
>>> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.drivers.vantage:
>>> Unable to wake up console
>>> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.engine: Import of
>>> driver failed: Unable to wake up Vantage console (>> 'weewx.WakeupError'>)
>>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>>> Traceback (most recent call last):
>>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>>>   File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
>>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>>> self.console = loader_function(config_dict, self)
>>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>>>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
>>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>>> return VantageService(engine, config_dict)
>>> Feb 22 22:39:19 W

[weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

No change in USB port.

pi@WeatherPi:~ $ 
pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
minicom: cannot open /dev/ttyUSB0: Device or resource busy
pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@WeatherPi:~ $ minicom -b 19200 -D /dev/ttyUSB0
minicom: cannot open /dev/ttyUSB0: Device or resource busy
pi@WeatherPi:~ $ 
pi@WeatherPi:~ $ 
pi@WeatherPi:~ $ 
pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200

[screen is terminating]
pi@WeatherPi:~ $ screen /dev/ttyUSB0 19200






















[screen is terminating]
pi@WeatherPi:~ $ TEST
bash: TEST: command not found
pi@WeatherPi:~ $ 


On Monday, 22 February 2021 at 23:15:28 UTC+13 gjr80 wrote:

> OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I am 
> told they behave just like a console. First thing I would do is test 
> connectivity from your RPi to the Envoy. Any chance the Envoy is now on a 
> different USB port? Not sure if you remember the Establishing connectivity 
> 
>  
> testing Tom got you to work through a couple of years back, but that is a 
> good place to start. The instructions are now in the wiki rather than the 
> User Guide but the link I have provided should work.
>
> Gary
> On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:
>
>> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather 
>> system...
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing weewx 
>> version 4.4.0
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 2.7.13 
>> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
>> Linux-4.19.66-v7+-armv7l-with-debian-9.13
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
>> 'en_NZ.UTF-8'
>> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather system: 
>> weewx.
>> Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather system.
>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using configuration 
>> file /etc/weewx/weewx.conf
>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing engine
>> Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading station 
>> type Vantage (weewx.drivers.vantage)
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>> Driver version is 3.2.1
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>> Option loop_request=1
>> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: 
>> Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>> Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
>> #0 failed
>> Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
>> #1 failed
>> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>> Feb 22 22:39:15 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
>> #2 failed
>> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
>> fe80::724f:57ff:feb7:82a1
>> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
>> Feb 22 22:39:19 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
>> #3 failed
>> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.drivers.vantage: 
>> Unable to wake up console
>> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.engine: Import of 
>> driver failed: Unable to wake up Vantage console (> 'weewx.WakeupError'>)
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
>> Traceback (most recent call last):
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>>   self.console = loader_function(config_dict, self)
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>>   return VantageService(engine, config_dict)
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
>> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
>> Feb 22 22:39:19 WeatherPi weewx[24964

[weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

OK, so WeeWX cannot connect to your Envoy, I am no Envoy expert but I am 
told they behave just like a console. First thing I would do is test 
connectivity from your RPi to the Envoy. Any chance the Envoy is now on a 
different USB port? Not sure if you remember the Establishing connectivity 
 
testing Tom got you to work through a couple of years back, but that is a 
good place to start. The instructions are now in the wiki rather than the 
User Guide but the link I have provided should work.

Gary
On Monday, 22 February 2021 at 19:43:26 UTC+10 monmul wrote:

> Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather system...
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing weewx 
> version 4.4.0
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 2.7.13 
> (default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
> Linux-4.19.66-v7+-armv7l-with-debian-9.13
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
> 'en_NZ.UTF-8'
> Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
> /var/run/weewx.pid
> Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather system: 
> weewx.
> Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather system.
> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using configuration 
> file /etc/weewx/weewx.conf
> Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing engine
> Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Driver 
> version is 3.2.1
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Option 
> loop_request=1
> Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Opened 
> up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
> #0 failed
> Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
> #1 failed
> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 22:39:15 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
> #2 failed
> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 22:39:19 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
> #3 failed
> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.drivers.vantage: Unable 
> to wake up console
> Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.engine: Import of 
> driver failed: Unable to wake up Vantage console ( 'weewx.WakeupError'>)
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
> Traceback (most recent call last):
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   self.console = loader_function(config_dict, self)
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   return VantageService(engine, config_dict)
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   self._setup()
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   self.port.wakeup_console(max_tries=self.max_tries)
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in 
> wakeup_console
> Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
>   raise weewx.WakeupError("Unable to wake up Vantage console")
> Fe

[weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[monmul]

Feb 22 22:39:02 WeatherPi systemd[1]: Starting LSB: weewx weather system...
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Initializing weewx 
version 4.4.0
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Using Python 2.7.13 
(default, Aug 22 2020, 10:03:02) #012[GCC 6.3.0 20170516]
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Platform 
Linux-4.19.66-v7+-armv7l-with-debian-9.13
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: Locale is 
'en_NZ.UTF-8'
Feb 22 22:39:03 WeatherPi weewx[24960] INFO __main__: PID file is 
/var/run/weewx.pid
Feb 22 22:39:03 WeatherPi weewx[24948]: Starting weewx weather system: 
weewx.
Feb 22 22:39:03 WeatherPi systemd[1]: Started LSB: weewx weather system.
Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Feb 22 22:39:03 WeatherPi weewx[24964] INFO __main__: Debug is 1
Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG __main__: Initializing engine
Feb 22 22:39:03 WeatherPi weewx[24964] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Driver 
version is 3.2.1
Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Option 
loop_request=1
Feb 22 22:39:03 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Opened 
up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:04 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 22:39:07 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
#0 failed
Feb 22 22:39:11 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
#1 failed
Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:12 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 22:39:15 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
#2 failed
Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:17 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 22:39:19 WeatherPi weewx[24964] DEBUG weewx.drivers.vantage: Retry 
#3 failed
Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.drivers.vantage: Unable 
to wake up console
Feb 22 22:39:19 WeatherPi weewx[24964] ERROR weewx.engine: Import of driver 
failed: Unable to wake up Vantage console ()
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
Traceback (most recent call last):
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
self.console = loader_function(config_dict, self)
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 39, in loader
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
return VantageService(engine, config_dict)
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1898, in __init__
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
Vantage.__init__(self, **config_dict[DRIVER_NAME])
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 515, in __init__
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
self._setup()
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 1317, in _setup
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
self.port.wakeup_console(max_tries=self.max_tries)
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in 
wakeup_console
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
raise weewx.WakeupError("Unable to wake up Vantage console")
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL weewx.engine:   
WakeupError: Unable to wake up Vantage console
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL __main__: Unable to load 
driver: Unable to wake up Vantage console
Feb 22 22:39:19 WeatherPi weewx[24964] CRITICAL __main__:   
Exiting...
Feb 22 22:39:20 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:20 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 22:39:27 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:27 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
Feb 22 22:39:35 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
fe80::724f:57ff:feb7:82a1
Feb 22 22:39:35 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCP

[weewx-user] Re: Replaced Davis Envoy (tripping) and replaced with another - no connection

[gjr80]

Hi,

We need to see the log from when you try starting WeeWX. Restart WeeWX and 
let it run for an archive period or two, then goto the log and take an 
extract from when WeeWX was restarted through until the two archive periods 
have passed. Post the log back here without alteration. It’s important you 
capture the full WeeWX startup.

Gary

On Monday, 22 February 2021 at 18:28:14 UTC+10 monmul wrote:

> My Davis system has been running really well for the last 2 years. Needed 
> no maintenance from me etc. Then the Envoy started tripping the circuit 
> fuse (I think it was the Envoy rather than the power chord as I replaced 
> with new Envoy and tripping stopped). I directly changed out the Envoy and 
> rebooted the system expecting that all would be back to normal. Nope!
>
> No data appears to be coming through:
>
> Here are my diagnostic so far:
>
> pi@WeatherPi:~ $ sudo /etc/init.d/weewx stop
> [ ok ] Stopping weewx (via systemctl): weewx.service.
> pi@WeatherPi:~ $ sudo weewxd
> pi@WeatherPi:~ $ ps -a
>   PID TTY  TIME CMD
> 15482 pts/100:00:00 ps
> pi@WeatherPi:~ $ kill -HUP 15482
> bash: kill: (15482) - No such process
> pi@WeatherPi:~ $ tail -f /var/log/syslog
> Feb 22 21:17:10 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Feb 22 21:17:10 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 21:17:14 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
> Feb 22 21:17:14 WeatherPi dhcpcd[372]: wlan0: soliciting a DHCPv6 lease
> Feb 22 21:17:17 WeatherPi dhcpcd[372]: wlan0: Router Advertisement from 
> fe80::724f:57ff:feb7:82a1
>
> Any guidance would be much appreciated.
>

-- 
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/66bf4f8c-7dc4-4b58-9702-299799f16eadn%40googlegroups.com.