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

[Thomas Keffer]

If power goes out often at your site, I would recommend buying a $50 UPS
(like this one
).
It makes a huge difference in reliability.

-tk

On Mon, Apr 15, 2019 at 2:37 AM monmul  wrote:

> That worked a treatthank you!
>
> On Monday, 15 April 2019 15:20:37 UTC+12, gjr80 wrote:
>>
>> Hi,
>>
>> Chances are you have suffered corrupted station memory due to the power
>> outage. Have a read of the *Corrupt station memory* section under WeeWX
>> generates HTML pages, but it does not update them
>>  in
>> the User's Guide. Before doing anything stop WeeWX and use wee-device to
>> dump the station memory
>> ,
>> this is your best bet at minimising any data loss. Once you have dumped the
>> station memory work through the two steps listed under *Corrupt station
>> memory*.
>>
>> It's worth making a note of this condition and it's symptoms, it is a
>> common occurrence for Davis stations that have a power interruption.
>>
>> Gary
>>
>> On Monday, 15 April 2019 12:32:46 UTC+10, monmul wrote:
>>>
>>> I have run into a problem. I have been overseas for some time and just
>>> got back today.  There was a power failure yesterday and weewx is stuck on
>>> mid night. See attached details. The photo on my website updatesbut nor
>>> the weather information? www.wilsonbayweather.com. What am I missing?
>>>
>>> On Wednesday, 6 March 2019 17:07:01 UTC+13, Andrew Milner wrote:

 That's Chrome and Google for you!!

 I've got a pic of a nice sunny verandah now also …..



 On Wednesday, 6 March 2019 00:30:07 UTC+2, monmul wrote:
>
> Yes it was!how freakin weird! Thanks for the help and the prompts!
>
> On Wednesday, 6 March 2019 11:27:18 UTC+13, monmul wrote:
>>
>> Surely it cannot be something to do with clearing the cache on my
>> browsersthat does not seem realistic!
>>
>> On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote:
>>>
>>> Hah! If I look it up on my phoneI get the correct jpg?
>>>
>>> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote:

 I am browsing from 2 different pcsone  a chromebook using
 Chrome and one my desktop using Chromium. I have tried both
 www.wilsonbayweather.com and
 www.wilsonbayweather.com/index.html..both give the same
 image.this is weird!why would the various weather icons and 
 data
 change but not the jpg.I will contact my web host and see if they 
 can
 throw any light on it. Thanks again!

 On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote:
>
> So when I look at your site I see ChangeImage.jpg. Since that is
> what is on your WeeWX server it sounds to me like FTP and your web 
> site are
> working as they should. Certainly Australia is seeing the correct
> page/image! It sounds like when you are looking at a page locally 
> that it
> is not working. When you are browsing and seeing that wrong image what
> address are you entering in your browser and what device are you 
> browsing
> from?
>
> Gary
>
 --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

[monmul]

That worked a treatthank you!

On Monday, 15 April 2019 15:20:37 UTC+12, gjr80 wrote:
>
> Hi,
>
> Chances are you have suffered corrupted station memory due to the power 
> outage. Have a read of the *Corrupt station memory* section under WeeWX 
> generates HTML pages, but it does not update them 
>  in 
> the User's Guide. Before doing anything stop WeeWX and use wee-device to 
> dump the station memory 
> , 
> this is your best bet at minimising any data loss. Once you have dumped the 
> station memory work through the two steps listed under *Corrupt station 
> memory*.
>
> It's worth making a note of this condition and it's symptoms, it is a 
> common occurrence for Davis stations that have a power interruption.
>
> Gary
>
> On Monday, 15 April 2019 12:32:46 UTC+10, monmul wrote:
>>
>> I have run into a problem. I have been overseas for some time and just 
>> got back today.  There was a power failure yesterday and weewx is stuck on 
>> mid night. See attached details. The photo on my website updatesbut nor 
>> the weather information? www.wilsonbayweather.com. What am I missing?
>>
>> On Wednesday, 6 March 2019 17:07:01 UTC+13, Andrew Milner wrote:
>>>
>>> That's Chrome and Google for you!!
>>>
>>> I've got a pic of a nice sunny verandah now also …..
>>>
>>>
>>>
>>> On Wednesday, 6 March 2019 00:30:07 UTC+2, monmul wrote:

 Yes it was!how freakin weird! Thanks for the help and the prompts!

 On Wednesday, 6 March 2019 11:27:18 UTC+13, monmul wrote:
>
> Surely it cannot be something to do with clearing the cache on my 
> browsersthat does not seem realistic!
>
> On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote:
>>
>> Hah! If I look it up on my phoneI get the correct jpg?
>>
>> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote:
>>>
>>> I am browsing from 2 different pcsone  a chromebook using Chrome 
>>> and one my desktop using Chromium. I have tried both 
>>> www.wilsonbayweather.com and 
>>> www.wilsonbayweather.com/index.html..both give the same 
>>> image.this is weird!why would the various weather icons and 
>>> data 
>>> change but not the jpg.I will contact my web host and see if they 
>>> can 
>>> throw any light on it. Thanks again!
>>>
>>> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote:

 So when I look at your site I see ChangeImage.jpg. Since that is 
 what is on your WeeWX server it sounds to me like FTP and your web 
 site are 
 working as they should. Certainly Australia is seeing the correct 
 page/image! It sounds like when you are looking at a page locally that 
 it 
 is not working. When you are browsing and seeing that wrong image what 
 address are you entering in your browser and what device are you 
 browsing 
 from?

 Gary

>>>

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

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

[gjr80]

Hi,

Chances are you have suffered corrupted station memory due to the power 
outage. Have a read of the *Corrupt station memory* section under WeeWX 
generates HTML pages, but it does not update them 
 in 
the User's Guide. Before doing anything stop WeeWX and use wee-device to 
dump the station memory 
, 
this is your best bet at minimising any data loss. Once you have dumped the 
station memory work through the two steps listed under *Corrupt station 
memory*.

It's worth making a note of this condition and it's symptoms, it is a 
common occurrence for Davis stations that have a power interruption.

Gary

On Monday, 15 April 2019 12:32:46 UTC+10, monmul wrote:
>
> I have run into a problem. I have been overseas for some time and just got 
> back today.  There was a power failure yesterday and weewx is stuck on mid 
> night. See attached details. The photo on my website updatesbut nor the 
> weather information? www.wilsonbayweather.com. What am I missing?
>
> On Wednesday, 6 March 2019 17:07:01 UTC+13, Andrew Milner wrote:
>>
>> That's Chrome and Google for you!!
>>
>> I've got a pic of a nice sunny verandah now also …..
>>
>>
>>
>> On Wednesday, 6 March 2019 00:30:07 UTC+2, monmul wrote:
>>>
>>> Yes it was!how freakin weird! Thanks for the help and the prompts!
>>>
>>> On Wednesday, 6 March 2019 11:27:18 UTC+13, monmul wrote:

 Surely it cannot be something to do with clearing the cache on my 
 browsersthat does not seem realistic!

 On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote:
>
> Hah! If I look it up on my phoneI get the correct jpg?
>
> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote:
>>
>> I am browsing from 2 different pcsone  a chromebook using Chrome 
>> and one my desktop using Chromium. I have tried both 
>> www.wilsonbayweather.com and 
>> www.wilsonbayweather.com/index.html..both give the same 
>> image.this is weird!why would the various weather icons and data 
>> change but not the jpg.I will contact my web host and see if they 
>> can 
>> throw any light on it. Thanks again!
>>
>> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote:
>>>
>>> So when I look at your site I see ChangeImage.jpg. Since that is 
>>> what is on your WeeWX server it sounds to me like FTP and your web site 
>>> are 
>>> working as they should. Certainly Australia is seeing the correct 
>>> page/image! It sounds like when you are looking at a page locally that 
>>> it 
>>> is not working. When you are browsing and seeing that wrong image what 
>>> address are you entering in your browser and what device are you 
>>> browsing 
>>> from?
>>>
>>> Gary
>>>
>>

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

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

[Andrew Milner]

That's Chrome and Google for you!!

I've got a pic of a nice sunny verandah now also …..



On Wednesday, 6 March 2019 00:30:07 UTC+2, monmul wrote:
>
> Yes it was!how freakin weird! Thanks for the help and the prompts!
>
> On Wednesday, 6 March 2019 11:27:18 UTC+13, monmul wrote:
>>
>> Surely it cannot be something to do with clearing the cache on my 
>> browsersthat does not seem realistic!
>>
>> On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote:
>>>
>>> Hah! If I look it up on my phoneI get the correct jpg?
>>>
>>> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote:

 I am browsing from 2 different pcsone  a chromebook using Chrome 
 and one my desktop using Chromium. I have tried both 
 www.wilsonbayweather.com and 
 www.wilsonbayweather.com/index.html..both give the same 
 image.this is weird!why would the various weather icons and data 
 change but not the jpg.I will contact my web host and see if they can 
 throw any light on it. Thanks again!

 On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote:
>
> So when I look at your site I see ChangeImage.jpg. Since that is what 
> is on your WeeWX server it sounds to me like FTP and your web site are 
> working as they should. Certainly Australia is seeing the correct 
> page/image! It sounds like when you are looking at a page locally that it 
> is not working. When you are browsing and seeing that wrong image what 
> address are you entering in your browser and what device are you browsing 
> from?
>
> Gary
>


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

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

[rich T]

Try clearing the cache on the chromebook and pc.  

On Tuesday, March 5, 2019 at 5:24:44 PM UTC-5, monmul wrote:
>
> Hah! If I look it up on my phoneI get the correct jpg?
>
> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote:
>>
>> I am browsing from 2 different pcsone  a chromebook using Chrome and 
>> one my desktop using Chromium. I have tried both www.wilsonbayweather.com 
>> and www.wilsonbayweather.com/index.html..both give the same 
>> image.this is weird!why would the various weather icons and data 
>> change but not the jpg.I will contact my web host and see if they can 
>> throw any light on it. Thanks again!
>>
>> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote:
>>>
>>> So when I look at your site I see ChangeImage.jpg. Since that is what is 
>>> on your WeeWX server it sounds to me like FTP and your web site are working 
>>> as they should. Certainly Australia is seeing the correct page/image! It 
>>> sounds like when you are looking at a page locally that it is not working. 
>>> When you are browsing and seeing that wrong image what address are you 
>>> entering in your browser and what device are you browsing from?
>>>
>>> Gary
>>>
>>

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

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

[monmul]

Yes it was!how freakin weird! Thanks for the help and the prompts!

On Wednesday, 6 March 2019 11:27:18 UTC+13, monmul wrote:
>
> Surely it cannot be something to do with clearing the cache on my 
> browsersthat does not seem realistic!
>
> On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote:
>>
>> Hah! If I look it up on my phoneI get the correct jpg?
>>
>> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote:
>>>
>>> I am browsing from 2 different pcsone  a chromebook using Chrome and 
>>> one my desktop using Chromium. I have tried both 
>>> www.wilsonbayweather.com and 
>>> www.wilsonbayweather.com/index.html..both give the same 
>>> image.this is weird!why would the various weather icons and data 
>>> change but not the jpg.I will contact my web host and see if they can 
>>> throw any light on it. Thanks again!
>>>
>>> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote:

 So when I look at your site I see ChangeImage.jpg. Since that is what 
 is on your WeeWX server it sounds to me like FTP and your web site are 
 working as they should. Certainly Australia is seeing the correct 
 page/image! It sounds like when you are looking at a page locally that it 
 is not working. When you are browsing and seeing that wrong image what 
 address are you entering in your browser and what device are you browsing 
 from?

 Gary

>>>

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

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

[Tom Robertson]

Have you cleared your browser cache?

-
Tom
On Mar 5, 2019, 4:24 PM -0600, monmul , wrote:
> Hah! If I look it up on my phoneI get the correct jpg?
>
> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote:
> > I am browsing from 2 different pcsone  a chromebook using Chrome and 
> > one my desktop using Chromium. I have tried both www.wilsonbayweather.com 
> > and www.wilsonbayweather.com/index.html..both give the same 
> > image.this is weird!why would the various weather icons and data 
> > change but not the jpg.I will contact my web host and see if they can 
> > throw any light on it. Thanks again!
> >
> > On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote:
> > > So when I look at your site I see ChangeImage.jpg. Since that is what is 
> > > on your WeeWX server it sounds to me like FTP and your web site are 
> > > working as they should. Certainly Australia is seeing the correct 
> > > page/image! It sounds like when you are looking at a page locally that it 
> > > is not working. When you are browsing and seeing that wrong image what 
> > > address are you entering in your browser and what device are you browsing 
> > > from?
> > > Gary
> --
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

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

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

[monmul]

Surely it cannot be something to do with clearing the cache on my 
browsersthat does not seem realistic!

On Wednesday, 6 March 2019 11:24:44 UTC+13, monmul wrote:
>
> Hah! If I look it up on my phoneI get the correct jpg?
>
> On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote:
>>
>> I am browsing from 2 different pcsone  a chromebook using Chrome and 
>> one my desktop using Chromium. I have tried both www.wilsonbayweather.com 
>> and www.wilsonbayweather.com/index.html..both give the same 
>> image.this is weird!why would the various weather icons and data 
>> change but not the jpg.I will contact my web host and see if they can 
>> throw any light on it. Thanks again!
>>
>> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote:
>>>
>>> So when I look at your site I see ChangeImage.jpg. Since that is what is 
>>> on your WeeWX server it sounds to me like FTP and your web site are working 
>>> as they should. Certainly Australia is seeing the correct page/image! It 
>>> sounds like when you are looking at a page locally that it is not working. 
>>> When you are browsing and seeing that wrong image what address are you 
>>> entering in your browser and what device are you browsing from?
>>>
>>> Gary
>>>
>>

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

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

[monmul]

Hah! If I look it up on my phoneI get the correct jpg?

On Wednesday, 6 March 2019 11:16:49 UTC+13, monmul wrote:
>
> I am browsing from 2 different pcsone  a chromebook using Chrome and 
> one my desktop using Chromium. I have tried both www.wilsonbayweather.com 
> and www.wilsonbayweather.com/index.html..both give the same 
> image.this is weird!why would the various weather icons and data 
> change but not the jpg.I will contact my web host and see if they can 
> throw any light on it. Thanks again!
>
> On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote:
>>
>> So when I look at your site I see ChangeImage.jpg. Since that is what is 
>> on your WeeWX server it sounds to me like FTP and your web site are working 
>> as they should. Certainly Australia is seeing the correct page/image! It 
>> sounds like when you are looking at a page locally that it is not working. 
>> When you are browsing and seeing that wrong image what address are you 
>> entering in your browser and what device are you browsing from?
>>
>> Gary
>>
>

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

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

[monmul]

I am browsing from 2 different pcsone  a chromebook using Chrome and 
one my desktop using Chromium. I have tried both www.wilsonbayweather.com 
and www.wilsonbayweather.com/index.html..both give the same 
image.this is weird!why would the various weather icons and data 
change but not the jpg.I will contact my web host and see if they can 
throw any light on it. Thanks again!

On Wednesday, 6 March 2019 10:56:52 UTC+13, gjr80 wrote:
>
> So when I look at your site I see ChangeImage.jpg. Since that is what is 
> on your WeeWX server it sounds to me like FTP and your web site are working 
> as they should. Certainly Australia is seeing the correct page/image! It 
> sounds like when you are looking at a page locally that it is not working. 
> When you are browsing and seeing that wrong image what address are you 
> entering in your browser and what device are you browsing from?
>
> Gary
>

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

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

[gjr80]

So when I look at your site I see ChangeImage.jpg. Since that is what is on 
your WeeWX server it sounds to me like FTP and your web site are working as 
they should. Certainly Australia is seeing the correct page/image! It sounds 
like when you are looking at a page locally that it is not working. When you 
are browsing and seeing that wrong image what address are you entering in your 
browser and what device are you browsing from?

Gary

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

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

[monmul]

Curiouser and curiouser. Attached the image I see from my public website 
(staticJpg.jpg)...and also the weewx native output on the Pi 
(ChangeImage.jpg) file:///var/www/html/weewx/index.html

On Wednesday, 6 March 2019 10:13:50 UTC+13, gjr80 wrote:
>
> So at 7:10 my time 10:10 (?) your time I am seeing a daytime photo of a 
> verandah with water and mountains in the background. That is quite 
> different to the night time image I first saw last night and the 'black 
> box' later last night. Give you image only updates on your WeeWX server 
> once an hour just wondering what basis you have for thinking it is not 
> working.
>
> Gary
>

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

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

[gjr80]

So at 7:10 my time 10:10 (?) your time I am seeing a daytime photo of a 
verandah with water and mountains in the background. That is quite different to 
the night time image I first saw last night and the 'black box' later last 
night. Give you image only updates on your WeeWX server once an hour just 
wondering what basis you have for thinking it is not working.

Gary

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

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

[monmul]

So this was after I had gone to bedstill showing image1 
uploadingand still getting a static image (the source of which I cannot 
find on the web server) on my web page.

6 01:20:22 WeatherPi weewx[19404]: ftpupload: Attempting connection to 
43.245.53.39
Mar  6 01:20:22 WeatherPi weewx[19404]: ftpupload: Connected to 43.245.53.39
Mar  6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/dayradiation.png
Mar  6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/index.html
Mar  6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/dayrain.png
Mar  6 01:20:22 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/daywinddir.png
Mar  6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/daywindvec.png
Mar  6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/daywind.png
Mar  6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/daytempdew.png
Mar  6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/image1.jpg
Mar  6 01:20:23 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/dayinside.png
Mar  6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/dayuv.png
Mar  6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/mobile.html
Mar  6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/week.html
Mar  6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/daybarometer.png
Mar  6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/month.html
Mar  6 01:20:24 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/daytempchill.png
Mar  6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/dayrx.png
Mar  6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/dayhumidity.png
Mar  6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/year.html
Mar  6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/alltime.html
Mar  6 01:20:25 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/xstats/index.html
Mar  6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/smartphone/wind.html
Mar  6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/smartphone/index.html
Mar  6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/smartphone/radar.html
Mar  6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/smartphone/rain.html
Mar  6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/smartphone/barometer.html
Mar  6 01:20:26 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/smartphone/temp_outside.html
Mar  6 01:20:27 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/NOAA/NOAA-2019.txt
Mar  6 01:20:27 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/NOAA/NOAA-2019-03.txt
Mar  6 01:20:27 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/RSS/weewx_rss.xml
Mar  6 01:20:27 WeatherPi weewx[19404]: ftpgenerator: ftp'd 29 files in 
5.46 seconds
Mar  6 01:20:27 WeatherPi weewx[19404]: reportengine: Running report 'RSYNC'
Mar  6 01:20:27 WeatherPi weewx[19404]: reportengine: Found configuration 
file /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC'
Mar  6 01:20:27 WeatherPi weewx[19404]: rsyncgenerato

On Tuesday, 5 March 2019 23:55:29 UTC+13, gjr80 wrote:
>
> Ok, but now when I look at your site image1.jpg does not the display. When 
> you deleted your jpg files you didn't touch anything on your WeeWX machine 
> did you? Your image is only produced every hour so if you did delete it on 
> the WeeWX machine then it could take up to an hour for it to be re-created 
> and subsequently uploaded to the web server. Keep an eye on your WeeWX log 
> to see if/when image1.jpg is uploaded. Guess it is getting late there now, 
> I will have a look later and see what is there.
>
> Gary
>

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

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

[Andrew Milner]

There seems to be an image there, but it is just a black square with a 
border.  When I looked earlier there was a very dark image of something 
that I could not make out - but it was definitely not the same as what is 
showing now.  Is there any way you can point the camera at a clock or 
something that is visible and which changes as time passes??





On Tuesday, 5 March 2019 12:55:29 UTC+2, gjr80 wrote:
>
> Ok, but now when I look at your site image1.jpg does not the display. When 
> you deleted your jpg files you didn't touch anything on your WeeWX machine 
> did you? Your image is only produced every hour so if you did delete it on 
> the WeeWX machine then it could take up to an hour for it to be re-created 
> and subsequently uploaded to the web server. Keep an eye on your WeeWX log 
> to see if/when image1.jpg is uploaded. Guess it is getting late there now, 
> I will have a look later and see what is there.
>
> Gary
>

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

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

[Andrew Milner]

there seems to be an image there - but it is just a black square with a 
border.



On Tuesday, 5 March 2019 12:55:29 UTC+2, gjr80 wrote:
>
> Ok, but now when I look at your site image1.jpg does not the display. When 
> you deleted your jpg files you didn't touch anything on your WeeWX machine 
> did you? Your image is only produced every hour so if you did delete it on 
> the WeeWX machine then it could take up to an hour for it to be re-created 
> and subsequently uploaded to the web server. Keep an eye on your WeeWX log 
> to see if/when image1.jpg is uploaded. Guess it is getting late there now, 
> I will have a look later and see what is there.
>
> Gary
>

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

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

[gjr80]

Ok, but now when I look at your site image1.jpg does not the display. When you 
deleted your jpg files you didn't touch anything on your WeeWX machine did you? 
Your image is only produced every hour so if you did delete it on the WeeWX 
machine then it could take up to an hour for it to be re-created and 
subsequently uploaded to the web server. Keep an eye on your WeeWX log to see 
if/when image1.jpg is uploaded. Guess it is getting late there now, I will have 
a look later and see what is there.

Gary

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

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

[monmul]

Thanks I will give that a try tomorrowits late here. I am thinking that 
you are right...and the problem lies in the FTP server. I will investigate 
and get back to you. Thank you for all your help!

On Tuesday, 5 March 2019 23:07:12 UTC+13, gjr80 wrote:
>
> Yes the former, your web host on the internet. Some folks can ssh into 
> their web server but I am gu swing you haven't done that. Do you have a 
> login that you can use via a browser to manage your hosting? That should 
> have some sort of file management tool.
>
> I am not convinced that the FTP is not working, I think it is.
>
> Gary
>
>

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

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

[gjr80]

Yes the former, your web host on the internet. Some folks can ssh into their 
web server but I am gu swing you haven't done that. Do you have a login that 
you can use via a browser to manage your hosting? That should have some sort of 
file management tool.

I am not convinced that the FTP is not working, I think it is.

Gary

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

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

[monmul]

By "delete image1.jpg from your web server" do you mean from the 
www.wilsonbayweather.com web server on the net or do you you mean the 
/var/www/html/weewx/ 
folder where it resides on my Pi? If the formernot sure how I would 
even do that?

On Tuesday, 5 March 2019 22:45:26 UTC+13, gjr80 wrote:
>
> Hang on, missed this in the log you posted:
>
> Mar  5 21:30:30 WeatherPi weewx[19404]: ftpupload: Uploaded file 
> /public_html/image1.jpg
>
> Looks like it is being uploaded. What happens if you delete image1.jpg 
> from your web server, does it get replaced (albeit with an old file) on the 
> next report cycle?
>
> Gary
>
>

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

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

[gjr80]

Hang on, missed this in the log you posted:

Mar  5 21:30:30 WeatherPi weewx[19404]: ftpupload: Uploaded file 
/public_html/image1.jpg

Looks like it is being uploaded. What happens if you delete image1.jpg from 
your web server, does it get replaced (albeit with an old file) on the next 
report cycle?

Gary

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

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

[gjr80]

Hmm, not seeing anything obvious. There is a check in the FTP generator that 
determines whether a file is to be uploaded or skipped, it may be that your 
image file is failing this test for some reason and hence not being uploaded. 
Unfortunately the log/debug doesn't tell us anything about this check. Might 
need Tom's expert eye when he comes along later.

Gary

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

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

[monmul]

weewx.conf attached - passwords etc changed.

On Tuesday, 5 March 2019 22:07:12 UTC+13, gjr80 wrote:
>
> Sorry I am a bit slow in this but I don't use ftp myself. I see files are 
> being uploaded from /public_html, just wondering if perhaps something is in 
> the wrong place. Can you post a copy of weewx.conf being careful to take 
> out any sensitive info, user names, passwords etc.
>
> Gary
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2015 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 3.9.1

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Wilson Bay, Queenstown, NZ"

# Latitude and longitude in decimal degrees
latitude = -45.0595
longitude = 168.567

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

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

# If you have a website, you may specify an URL
#station_url = http://www.example.com

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[Vantage]
# This section is for the Davis Vantage series of weather stations.

# Connection type: serial or ethernet 
#  serial (the classic VantagePro)
#  ethernet (the WeatherLinkIP or Serial-Ethernet bridge)
type = serial

# If the connection type is serial, a port must be specified:
#   Debian, Ubuntu, Redhat, Fedora, and SuSE:
# /dev/ttyUSB0 is a common USB port name
# /dev/ttyS0   is a common serial port name
#   BSD:
# /dev/cuaU0   is a common serial port name
port = /dev/ttyUSB0

# If the connection type is ethernet, an IP Address/hostname is required:
host = 1.2.3.4

##
# The rest of this section rarely needs any attention. 
# You can safely leave it "as is."
##

# Serial baud rate (usually 19200)
baudrate = 19200

# TCP port (when using the WeatherLinkIP)
tcp_port = 2

# TCP send delay (when using the WeatherLinkIP):
tcp_send_delay = 0.5

# The id of your ISS station (usually 1). If you use a wind meter connected
# to a anemometer transmitter kit, use its id
iss_id = 1

# How long to wait for a response from the station before giving up (in
# seconds; must be greater than 2)
timeout = 4

# How long to wait before trying again (in seconds)
wait_before_retry = 1.2

# How many times to try before giving up:
max_tries = 4

# Vantage model Type: 1 = Vantage Pro; 2 = Vantage Pro2
model_type = 2

# The driver to use:
driver = weewx.drivers.vantage

##

#   This section is for uploading data to Internet sites

[StdRESTful]

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

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
# To guard against parsing errors, put the password in quotes.
enable = false
username = replace_me
password = replace_me

[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and 

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

[gjr80]

Sorry I am a bit slow in this but I don't use ftp myself. I see files are being 
uploaded from /public_html, just wondering if perhaps something is in the wrong 
place. Can you post a copy of weewx.conf being careful to take out any 
sensitive info, user names, passwords etc.

Gary

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

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

[monmul]

It gets there via a cron hourly script

#!/bin/sh
#
# Simple cron script 
sudo rm /var/www/html/weewx/image1.jpg
#rm /var/www/html/weewx/640x480

sudo raspistill -w 640 -h 480 -o /var/www/html/weewx/image.jpg

sudo mv /var/www/html/weewx/image.jpg /var/www/html/weewx/image1.jpg


On Tuesday, 5 March 2019 18:41:47 UTC+13, gjr80 wrote:
>
> One thing 3.9.0  changed was the log_success and log_failure settings in 
> weewx.conf. Just to make sure nothing is being hidden from you edit 
> weewx.conf and under [StdReport] set log_failure = True. Also set debug = 
> 1, I don't think debug is going to tell us much more but let's give it a 
> go. Save weewx.conf. In the /vat/www/html/weewx directory find and delete 
> the file #FTPlast. Restart WeeWX.
>
> See what happens, if no change post the log from startup showing the 
> entire startup and at least a couple of complete report cycles.
>
> I don't see copy_always helping, that applies to the CopyGenerator only 
> and since the file concerned is already in /var/www/html/weewx we don't 
> need to copy it there. Just out of interest, can you give us an outline of 
> how image1.jpg arrives in /var/www/html/weewx ?
>
> Gary
>
>

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

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

[gjr80]

One thing 3.9.0  changed was the log_success and log_failure settings in 
weewx.conf. Just to make sure nothing is being hidden from you edit weewx.conf 
and under [StdReport] set log_failure = True. Also set debug = 1, I don't think 
debug is going to tell us much more but let's give it a go. Save weewx.conf. In 
the /vat/www/html/weewx directory find and delete the file #FTPlast. Restart 
WeeWX.

See what happens, if no change post the log from startup showing the entire 
startup and at least a couple of complete report cycles.

I don't see copy_always helping, that applies to the CopyGenerator only and 
since the file concerned is already in /var/www/html/weewx we don't need to 
copy it there. Just out of interest, can you give us an outline of how 
image1.jpg arrives in /var/www/html/weewx ?

Gary

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

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

[monmul]

OK, so I seem to be on 3.9.1what has changed that would make the FTP 
keep working from the previous version but not carry the jpeg across?

On Tuesday, 5 March 2019 10:19:24 UTC+13, Tom wrote:
>
> To determine the weewx version try:
>
> wee_config --version
>
>
> --
> Tom
>
>
> On Mon, Mar 4, 2019 at 1:54 PM monmul > 
> wrote:
>
>> I am thinking...maybe I accidentally updated to the latest version and 
>> that has broken something? How do I check what version I am running?
>>
>> On Tuesday, 5 March 2019 08:40:38 UTC+13, monmul wrote:
>>>
>>> So this is the FTP section of my weewx.conf..I have not changed 
>>> anything. It used to transfer across no problem until the camera needed 
>>> replacingand the photo from the new camera appears on the internal 
>>> website but not transferred across...weird!
>>>
>>>  [[FTP]]
>>> # FTP'ing the results to a webserver is treated as just another 
>>> report,
>>> # albeit one with an unusual report generator!
>>> skin = Ftp
>>>
>>> # If you wish to use FTP, uncomment and fill out the next four 
>>> lines.
>>> # Use quotes around passwords to guard against parsing errors.
>>> user = abcdefgh
>>> password = 123456789
>>> server = 43.245.53.39
>>> path = /public_html
>>>
>>> # Set to True for an FTP over TLS (FTPS) connection. Not all 
>>> servers
>>> # support this.
>>> secure_ftp = False
>>>
>>> # To upload files from something other than what HTML_ROOT is set
>>> # to above, specify a different HTML_ROOT here.
>>> #HTML_ROOT = /var/www/html/weewx
>>>
>>> # Most FTP servers use port 21
>>> port = 21
>>>
>>> # Set to 1 to use passive mode, zero for active mode
>>> passive = 1
>>>
>>>
>>> On Monday, 4 March 2019 23:30:53 UTC+13, Andrew Milner wrote:

 you did not give us a directory listing from the external website - but 
 assuming the file has not been transferred there maybe you need to include 
 image.jpeg in the copy always list in weewx.conf



 On Monday, 4 March 2019 11:20:16 UTC+2, monmul wrote:
>
> I have run into a problem with posting a photo on my website. The 
> photo shows on file:///var/www/html/weewx/index.html but not on 
> www.wilsonbayweather.com - this shows an old photo that never 
> changes! Attached are screenshots that may help. Why is it updating on 
> one 
> and not the other?
>
> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote:
>>
>> Hi,
>>
>> There are a few steps involved in achieving what you want to do. 
>> First the historical max/min - by this I presume you mean all time 
>> statistics - those that cover all of your weeWX data and not just the 
>> last 
>> day, month or year. 
>>
>> If I have this right you need to extend weeWX so that you can access 
>> stats from all of your data, this is most easily achieved by installing 
>> the 
>> xstats example extension. You will find the xstats files are in the 
>> /usr/share/doc/weewx/examples directory. I would install manually 
>> and just follow step 1 in the readme.txt remembering later that you 
>> will need to enable the alltime stats for your templates/reports by 
>> following step 2. You can install xstats using wee_extension but 
>> that will also install the example web page which you probably do not 
>> want.
>>
>> Now that you have xstats installed you can use tags like 
>> $alltime.outTemp.max in report templates to display the maximum 
>> outside temperature. The time it occurred will be 
>> $alltime.outTemp.maxtime. Just like $day, $month and $year tags but 
>> you use $alltime. If you are not familiar with weeWX tags it is worth 
>> reading the Tags section  
>> of the Customization Guide.
>>
>> To use the $alltime tags you will probably want to create a new page 
>> or modify an existing one. It is really up to you want you want to do. 
>> To 
>> modify an existing page have a look at the .tmpl files in you 
>> Standard skin directory /etc/weewx/skins/Standard. These are the 
>> files weeWX uses to generate a corresponding .html page. You will see 
>> how 
>> tags are used in a template, in a nutshell where you place a tag weeWX 
>> will 
>> replace that with the relevant data when the reports are generated. The 
>> process is a little more involved if you want to create a new page as 
>> not 
>> only do you need to modify/create a page but you also need to modify 
>> skin.conf to have weeWX generate the new page. You may also need to 
>> modify other pages to include a link to your new page. A good starting 
>> point may be to take a copy of 
>> /etc/weewx/skins/Standard/year.html.tmpl, save it as 
>> 

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

[Tom]

To determine the weewx version try:

wee_config --version


--
Tom


On Mon, Mar 4, 2019 at 1:54 PM monmul  wrote:

> I am thinking...maybe I accidentally updated to the latest version and
> that has broken something? How do I check what version I am running?
>
> On Tuesday, 5 March 2019 08:40:38 UTC+13, monmul wrote:
>>
>> So this is the FTP section of my weewx.conf..I have not changed
>> anything. It used to transfer across no problem until the camera needed
>> replacingand the photo from the new camera appears on the internal
>> website but not transferred across...weird!
>>
>>  [[FTP]]
>> # FTP'ing the results to a webserver is treated as just another
>> report,
>> # albeit one with an unusual report generator!
>> skin = Ftp
>>
>> # If you wish to use FTP, uncomment and fill out the next four
>> lines.
>> # Use quotes around passwords to guard against parsing errors.
>> user = abcdefgh
>> password = 123456789
>> server = 43.245.53.39
>> path = /public_html
>>
>> # Set to True for an FTP over TLS (FTPS) connection. Not all
>> servers
>> # support this.
>> secure_ftp = False
>>
>> # To upload files from something other than what HTML_ROOT is set
>> # to above, specify a different HTML_ROOT here.
>> #HTML_ROOT = /var/www/html/weewx
>>
>> # Most FTP servers use port 21
>> port = 21
>>
>> # Set to 1 to use passive mode, zero for active mode
>> passive = 1
>>
>>
>> On Monday, 4 March 2019 23:30:53 UTC+13, Andrew Milner wrote:
>>>
>>> you did not give us a directory listing from the external website - but
>>> assuming the file has not been transferred there maybe you need to include
>>> image.jpeg in the copy always list in weewx.conf
>>>
>>>
>>>
>>> On Monday, 4 March 2019 11:20:16 UTC+2, monmul wrote:

 I have run into a problem with posting a photo on my website. The photo
 shows on file:///var/www/html/weewx/index.html but not on
 www.wilsonbayweather.com - this shows an old photo that never changes!
 Attached are screenshots that may help. Why is it updating on one and not
 the other?

 On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote:
>
> Hi,
>
> There are a few steps involved in achieving what you want to do. First
> the historical max/min - by this I presume you mean all time statistics -
> those that cover all of your weeWX data and not just the last day, month 
> or
> year.
>
> If I have this right you need to extend weeWX so that you can access
> stats from all of your data, this is most easily achieved by installing 
> the
> xstats example extension. You will find the xstats files are in the
> /usr/share/doc/weewx/examples directory. I would install manually and
> just follow step 1 in the readme.txt remembering later that you will
> need to enable the alltime stats for your templates/reports by following
> step 2. You can install xstats using wee_extension but that will also
> install the example web page which you probably do not want.
>
> Now that you have xstats installed you can use tags like
> $alltime.outTemp.max in report templates to display the maximum
> outside temperature. The time it occurred will be
> $alltime.outTemp.maxtime. Just like $day, $month and $year tags but
> you use $alltime. If you are not familiar with weeWX tags it is worth
> reading the Tags section 
> of the Customization Guide.
>
> To use the $alltime tags you will probably want to create a new page
> or modify an existing one. It is really up to you want you want to do. To
> modify an existing page have a look at the .tmpl files in you
> Standard skin directory /etc/weewx/skins/Standard. These are the
> files weeWX uses to generate a corresponding .html page. You will see how
> tags are used in a template, in a nutshell where you place a tag weeWX 
> will
> replace that with the relevant data when the reports are generated. The
> process is a little more involved if you want to create a new page as not
> only do you need to modify/create a page but you also need to modify
> skin.conf to have weeWX generate the new page. You may also need to
> modify other pages to include a link to your new page. A good starting
> point may be to take a copy of
> /etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl
> and start modifying. Have a good poke around the templates and
> skin.conf (and [StdReport] in weewx.conf) to see how it comes
> together.
>
> Including an image in a weeWX generated page can be relatively
> straightforward. If you have a look in index.html.tmpl you will see
> lines such as:
>
> 
>
> This line creates a HTML img tag that displays the 

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

[monmul]

I am thinking...maybe I accidentally updated to the latest version and that 
has broken something? How do I check what version I am running?

On Tuesday, 5 March 2019 08:40:38 UTC+13, monmul wrote:
>
> So this is the FTP section of my weewx.conf..I have not changed 
> anything. It used to transfer across no problem until the camera needed 
> replacingand the photo from the new camera appears on the internal 
> website but not transferred across...weird!
>
>  [[FTP]]
> # FTP'ing the results to a webserver is treated as just another 
> report,
> # albeit one with an unusual report generator!
> skin = Ftp
>
> # If you wish to use FTP, uncomment and fill out the next four 
> lines.
> # Use quotes around passwords to guard against parsing errors.
> user = abcdefgh
> password = 123456789
> server = 43.245.53.39
> path = /public_html
>
> # Set to True for an FTP over TLS (FTPS) connection. Not all 
> servers
> # support this.
> secure_ftp = False
>
> # To upload files from something other than what HTML_ROOT is set
> # to above, specify a different HTML_ROOT here.
> #HTML_ROOT = /var/www/html/weewx
>
> # Most FTP servers use port 21
> port = 21
>
> # Set to 1 to use passive mode, zero for active mode
> passive = 1
>
>
> On Monday, 4 March 2019 23:30:53 UTC+13, Andrew Milner wrote:
>>
>> you did not give us a directory listing from the external website - but 
>> assuming the file has not been transferred there maybe you need to include 
>> image.jpeg in the copy always list in weewx.conf
>>
>>
>>
>> On Monday, 4 March 2019 11:20:16 UTC+2, monmul wrote:
>>>
>>> I have run into a problem with posting a photo on my website. The photo 
>>> shows on file:///var/www/html/weewx/index.html but not on 
>>> www.wilsonbayweather.com - this shows an old photo that never changes! 
>>> Attached are screenshots that may help. Why is it updating on one and not 
>>> the other?
>>>
>>> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote:

 Hi,

 There are a few steps involved in achieving what you want to do. First 
 the historical max/min - by this I presume you mean all time statistics - 
 those that cover all of your weeWX data and not just the last day, month 
 or 
 year. 

 If I have this right you need to extend weeWX so that you can access 
 stats from all of your data, this is most easily achieved by installing 
 the 
 xstats example extension. You will find the xstats files are in the 
 /usr/share/doc/weewx/examples directory. I would install manually and 
 just follow step 1 in the readme.txt remembering later that you will 
 need to enable the alltime stats for your templates/reports by following 
 step 2. You can install xstats using wee_extension but that will also 
 install the example web page which you probably do not want.

 Now that you have xstats installed you can use tags like 
 $alltime.outTemp.max in report templates to display the maximum 
 outside temperature. The time it occurred will be 
 $alltime.outTemp.maxtime. Just like $day, $month and $year tags but 
 you use $alltime. If you are not familiar with weeWX tags it is worth 
 reading the Tags section  
 of the Customization Guide.

 To use the $alltime tags you will probably want to create a new page 
 or modify an existing one. It is really up to you want you want to do. To 
 modify an existing page have a look at the .tmpl files in you Standard 
 skin directory /etc/weewx/skins/Standard. These are the files weeWX 
 uses to generate a corresponding .html page. You will see how tags are 
 used 
 in a template, in a nutshell where you place a tag weeWX will replace that 
 with the relevant data when the reports are generated. The process is a 
 little more involved if you want to create a new page as not only do you 
 need to modify/create a page but you also need to modify skin.conf to 
 have weeWX generate the new page. You may also need to modify other pages 
 to include a link to your new page. A good starting point may be to take a 
 copy of /etc/weewx/skins/Standard/year.html.tmpl, save it as 
 alltime.html.tmpl and start modifying. Have a good poke around the 
 templates and skin.conf (and [StdReport] in weewx.conf) to see how it 
 comes together. 

 Including an image in a weeWX generated page can be relatively 
 straightforward. If you have a look in index.html.tmpl you will see 
 lines such as:

 

 This line creates a HTML img tag that displays the daily temperature 
 and dewpoint plot. If whatever you use to generate your webcam image can 
 create a file named, say, webcam.jpg then that keeps it easy, you may 
 be able to 

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

[monmul]

So this is the FTP section of my weewx.conf..I have not changed 
anything. It used to transfer across no problem until the camera needed 
replacingand the photo from the new camera appears on the internal 
website but not transferred across...weird!

 [[FTP]]
# FTP'ing the results to a webserver is treated as just another 
report,
# albeit one with an unusual report generator!
skin = Ftp

# If you wish to use FTP, uncomment and fill out the next four 
lines.
# Use quotes around passwords to guard against parsing errors.
user = abcdefgh
password = 123456789
server = 43.245.53.39
path = /public_html

# Set to True for an FTP over TLS (FTPS) connection. Not all servers
# support this.
secure_ftp = False

# To upload files from something other than what HTML_ROOT is set
# to above, specify a different HTML_ROOT here.
#HTML_ROOT = /var/www/html/weewx

# Most FTP servers use port 21
port = 21

# Set to 1 to use passive mode, zero for active mode
passive = 1


On Monday, 4 March 2019 23:30:53 UTC+13, Andrew Milner wrote:
>
> you did not give us a directory listing from the external website - but 
> assuming the file has not been transferred there maybe you need to include 
> image.jpeg in the copy always list in weewx.conf
>
>
>
> On Monday, 4 March 2019 11:20:16 UTC+2, monmul wrote:
>>
>> I have run into a problem with posting a photo on my website. The photo 
>> shows on file:///var/www/html/weewx/index.html but not on 
>> www.wilsonbayweather.com - this shows an old photo that never changes! 
>> Attached are screenshots that may help. Why is it updating on one and not 
>> the other?
>>
>> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote:
>>>
>>> Hi,
>>>
>>> There are a few steps involved in achieving what you want to do. First 
>>> the historical max/min - by this I presume you mean all time statistics - 
>>> those that cover all of your weeWX data and not just the last day, month or 
>>> year. 
>>>
>>> If I have this right you need to extend weeWX so that you can access 
>>> stats from all of your data, this is most easily achieved by installing the 
>>> xstats example extension. You will find the xstats files are in the 
>>> /usr/share/doc/weewx/examples directory. I would install manually and 
>>> just follow step 1 in the readme.txt remembering later that you will 
>>> need to enable the alltime stats for your templates/reports by following 
>>> step 2. You can install xstats using wee_extension but that will also 
>>> install the example web page which you probably do not want.
>>>
>>> Now that you have xstats installed you can use tags like 
>>> $alltime.outTemp.max in report templates to display the maximum outside 
>>> temperature. The time it occurred will be $alltime.outTemp.maxtime. 
>>> Just like $day, $month and $year tags but you use $alltime. If you are 
>>> not familiar with weeWX tags it is worth reading the Tags section 
>>>  of the Customization Guide.
>>>
>>> To use the $alltime tags you will probably want to create a new page or 
>>> modify an existing one. It is really up to you want you want to do. To 
>>> modify an existing page have a look at the .tmpl files in you Standard 
>>> skin directory /etc/weewx/skins/Standard. These are the files weeWX 
>>> uses to generate a corresponding .html page. You will see how tags are used 
>>> in a template, in a nutshell where you place a tag weeWX will replace that 
>>> with the relevant data when the reports are generated. The process is a 
>>> little more involved if you want to create a new page as not only do you 
>>> need to modify/create a page but you also need to modify skin.conf to 
>>> have weeWX generate the new page. You may also need to modify other pages 
>>> to include a link to your new page. A good starting point may be to take a 
>>> copy of /etc/weewx/skins/Standard/year.html.tmpl, save it as 
>>> alltime.html.tmpl and start modifying. Have a good poke around the 
>>> templates and skin.conf (and [StdReport] in weewx.conf) to see how it 
>>> comes together. 
>>>
>>> Including an image in a weeWX generated page can be relatively 
>>> straightforward. If you have a look in index.html.tmpl you will see 
>>> lines such as:
>>>
>>> 
>>>
>>> This line creates a HTML img tag that displays the daily temperature and 
>>> dewpoint plot. If whatever you use to generate your webcam image can create 
>>> a file named, say, webcam.jpg then that keeps it easy, you may be able 
>>> to create a new img tag but using webcam.jpg (rather than daytempdew.png), 
>>> you may need to add a path in front of the file name. If your webcam image 
>>> is timestamped like webcam201901131345.jpg then that gets a little more 
>>> complicated. If you can drop your webcam image into the weeWX directory 
>>> structure under /var/www/html/weewx then you 

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

[Andrew Milner]

you did not give us a directory listing from the external website - but 
assuming the file has not been transferred there maybe you need to include 
image.jpeg in the copy always list in weewx.conf



On Monday, 4 March 2019 11:20:16 UTC+2, monmul wrote:
>
> I have run into a problem with posting a photo on my website. The photo 
> shows on file:///var/www/html/weewx/index.html but not on 
> www.wilsonbayweather.com - this shows an old photo that never changes! 
> Attached are screenshots that may help. Why is it updating on one and not 
> the other?
>
> On Sunday, 13 January 2019 17:00:51 UTC+13, gjr80 wrote:
>>
>> Hi,
>>
>> There are a few steps involved in achieving what you want to do. First 
>> the historical max/min - by this I presume you mean all time statistics - 
>> those that cover all of your weeWX data and not just the last day, month or 
>> year. 
>>
>> If I have this right you need to extend weeWX so that you can access 
>> stats from all of your data, this is most easily achieved by installing the 
>> xstats example extension. You will find the xstats files are in the 
>> /usr/share/doc/weewx/examples directory. I would install manually and 
>> just follow step 1 in the readme.txt remembering later that you will 
>> need to enable the alltime stats for your templates/reports by following 
>> step 2. You can install xstats using wee_extension but that will also 
>> install the example web page which you probably do not want.
>>
>> Now that you have xstats installed you can use tags like 
>> $alltime.outTemp.max in report templates to display the maximum outside 
>> temperature. The time it occurred will be $alltime.outTemp.maxtime. Just 
>> like $day, $month and $year tags but you use $alltime. If you are not 
>> familiar with weeWX tags it is worth reading the Tags section 
>>  of the Customization Guide.
>>
>> To use the $alltime tags you will probably want to create a new page or 
>> modify an existing one. It is really up to you want you want to do. To 
>> modify an existing page have a look at the .tmpl files in you Standard 
>> skin directory /etc/weewx/skins/Standard. These are the files weeWX uses 
>> to generate a corresponding .html page. You will see how tags are used in a 
>> template, in a nutshell where you place a tag weeWX will replace that with 
>> the relevant data when the reports are generated. The process is a little 
>> more involved if you want to create a new page as not only do you need to 
>> modify/create a page but you also need to modify skin.conf to have weeWX 
>> generate the new page. You may also need to modify other pages to include a 
>> link to your new page. A good starting point may be to take a copy of 
>> /etc/weewx/skins/Standard/year.html.tmpl, save it as alltime.html.tmpl 
>> and start modifying. Have a good poke around the templates and skin.conf 
>> (and [StdReport] in weewx.conf) to see how it comes together. 
>>
>> Including an image in a weeWX generated page can be relatively 
>> straightforward. If you have a look in index.html.tmpl you will see 
>> lines such as:
>>
>> 
>>
>> This line creates a HTML img tag that displays the daily temperature and 
>> dewpoint plot. If whatever you use to generate your webcam image can create 
>> a file named, say, webcam.jpg then that keeps it easy, you may be able 
>> to create a new img tag but using webcam.jpg (rather than daytempdew.png), 
>> you may need to add a path in front of the file name. If your webcam image 
>> is timestamped like webcam201901131345.jpg then that gets a little more 
>> complicated. If you can drop your webcam image into the weeWX directory 
>> structure under /var/www/html/weewx then you can very easily use weeWX 
>> to upload your webcam image to your web server if you wish. There are many 
>> different ways to achieve this, I have outlined one and I am sure other 
>> will have other ways. At the end of the day it will likely depend on your 
>> setup.
>>
>> You have started on the slippery slope of customising your weeWX install, 
>> the process can appear daunting but do persist and feel free to continue to 
>> ask if not sure.
>>
>> Gary
>>  
>> On Sunday, 13 January 2019 11:25:59 UTC+10, monmul wrote:
>>>
>>> I have managed to get the Standard skin loaded on my weather website 
>>> www.wilsonbayweather.com...2 small adjustments I would like to 
>>> make..how do I show the historical max and min for temp, wind, rain 
>>> etcand how might I include a jpeg photo from webcam showing a picture 
>>> every hour or so? Thanks in advance.you guys have been fabulous in 
>>> helping a newbie!
>>>
>>>

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

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

[monmul]

Is there anyway I can help in getting the WeatherDisplay csv data into the 
weewx database..I have been away for a while so might have missed any 
updates on this project.

On Thursday, 17 January 2019 22:40:45 UTC+13, monmul wrote:
>
> AwesomeI thought that weeimport could only deal with csv files and so 
> went and converted them allbut kept the txt files for backup!
>
> On Thursday, 17 January 2019 22:35:30 UTC+13, gjr80 wrote:
>>
>> Ok, that explains the csv file you provided having a different name 
>> structure to what I had found. I believe that there was/is the ability for 
>> WD to publish csv format log files and that is what I have. Weeimport will 
>> happily work with the MMlg.txt files just as they are. No need to dig 
>> anything out of an old machine. You will be the 1st so it will work with 
>> your logs and I guess we see where it goes from there. Weeimport is fairly 
>> flexible in structure and can easily be adapted.
>>
>> Gary
>>
>

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

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

[monmul]

For those following on from me.the two power packs - 1 feeding the Rpi 
3 and the other feeding the USB hub has made a tremendous difference.no 
problems shown in the log, no time problems, no voltage problemsit just 
flows and operates really well. I wish I had known this from the start it 
would have saved me so much grief!

On Tuesday, 29 January 2019 15:27:46 UTC+13, monmul wrote:
>
> Yes it was, apologies to those I doubted!
>
> On Tuesday, 29 January 2019 14:29:12 UTC+13, Thomas Keffer wrote:
>>
>> Congratulations! Looks like it was a power supply problem.
>>
>> USB power supplies fail. I had one that would show +5V under no load, but 
>> it would sag to near nothing with just a modest load.
>>
>> On Mon, Jan 28, 2019 at 5:26 PM monmul  wrote:
>>
>>> It is working again!.This time I used both official power 
>>> units...one to power the Pi and one to power the hub.
>>>
>>> On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote:

 Then you definitely have a connectivity problem!

 -tk

 On Mon, Jan 28, 2019 at 4:32 PM monmul  wrote:

> Welcome to minicom 2.7
>
> OPTIONS: I18n 
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 13:15:39
>
> Press CTRL-A Z for help on special keys
>
> Even after lots or s nothing happens on TEST
>
> Similarly for screen...
>
> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote:
>>
>> The "establishing connectivity" instructions don't mention it, but be 
>> sure to hit  a few times before typing TEST.
>>
>> On Mon, Jan 28, 2019 at 4:11 PM monmul  wrote:
>>
>>> Tried both screen and minicom.no TEST echo backso must be 
>>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has 
>>> been 
>>> replaced.have another pi on orderbut in the meantime I guess I 
>>> will 
>>> go back to scratch and start all over againat least it has worked 
>>> before with this set upmaybe something has become corrupted!
>>>
>>>
>>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote:

 Try to communicate directly with the Envoy, without going through 
 WeeWX. For how to do this, see the section *Establishing 
 connectivity 
 * in 
 the User's Guide. If you are unable to do that, then this is 
 definitely a 
 hardware problem.

 -tk

 On Mon, Jan 28, 2019 at 2:41 PM dunbrokin  
 wrote:

> Thanks, but no I don't I use VNC.
>
> On Tue, Jan 29, 2019 at 11:35 AM  wrote:
>
>> Just a quick question. Do you have a monitor (like the Pi 7 in 
>> touch screen) attached that is running off the same power supply as 
>> the Pi? 
>> I had a setup like that which used a splitter to power both the 
>> monitor and 
>> Pi from one power pack. My setup kept complaining of undervolting 
>> until I 
>> removed the splitter and plugged the monitor and pi each into their 
>> own 
>> power supply.
>>
>> phil
>>
>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:
>>>
>>> I have replaced the power unit, taken it off the power strip an 
>>> plugged both it and the Vanatage into the mains. I have replaced 
>>> the 
>>> powered hub (official RPi one...with another official RPi one) 
>>> ...and here 
>>> is what I am getting...very dispirited! I have another Davis 
>>> Weather 
>>> Envoy which I will soon substitute for the one I am currently 
>>> using.but 
>>> nothing seems to make a difference and the Envoy just will not wake 
>>> up!
>>>
>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at 
>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: 
>>> SPrintConnMgr: Failed to add printer: 
>>> server-error-service-unavailable
>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers 
>>> available
>>> Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage 
>>> normalised (0x)
>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake 
>>> up console
>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: 
>>> Unable to wake up Vantage console ()
>>> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load 
>>> driver: Unable to wake up Vantage console
>>> Jan 29 09:14:12 raspberrypi weewx[506]:   

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

[monmul]

Yes it was, apologies to those I doubted!

On Tuesday, 29 January 2019 14:29:12 UTC+13, Thomas Keffer wrote:
>
> Congratulations! Looks like it was a power supply problem.
>
> USB power supplies fail. I had one that would show +5V under no load, but 
> it would sag to near nothing with just a modest load.
>
> On Mon, Jan 28, 2019 at 5:26 PM monmul > 
> wrote:
>
>> It is working again!.This time I used both official power units...one 
>> to power the Pi and one to power the hub.
>>
>> On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote:
>>>
>>> Then you definitely have a connectivity problem!
>>>
>>> -tk
>>>
>>> On Mon, Jan 28, 2019 at 4:32 PM monmul  wrote:
>>>
 Welcome to minicom 2.7

 OPTIONS: I18n 
 Compiled on Apr 22 2017, 09:14:19.
 Port /dev/ttyUSB0, 13:15:39

 Press CTRL-A Z for help on special keys

 Even after lots or s nothing happens on TEST

 Similarly for screen...

 On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote:
>
> The "establishing connectivity" instructions don't mention it, but be 
> sure to hit  a few times before typing TEST.
>
> On Mon, Jan 28, 2019 at 4:11 PM monmul  wrote:
>
>> Tried both screen and minicom.no TEST echo backso must be 
>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has 
>> been 
>> replaced.have another pi on orderbut in the meantime I guess I 
>> will 
>> go back to scratch and start all over againat least it has worked 
>> before with this set upmaybe something has become corrupted!
>>
>>
>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote:
>>>
>>> Try to communicate directly with the Envoy, without going through 
>>> WeeWX. For how to do this, see the section *Establishing 
>>> connectivity 
>>> * in 
>>> the User's Guide. If you are unable to do that, then this is definitely 
>>> a 
>>> hardware problem.
>>>
>>> -tk
>>>
>>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin  wrote:
>>>
 Thanks, but no I don't I use VNC.

 On Tue, Jan 29, 2019 at 11:35 AM  wrote:

> Just a quick question. Do you have a monitor (like the Pi 7 in 
> touch screen) attached that is running off the same power supply as 
> the Pi? 
> I had a setup like that which used a splitter to power both the 
> monitor and 
> Pi from one power pack. My setup kept complaining of undervolting 
> until I 
> removed the splitter and plugged the monitor and pi each into their 
> own 
> power supply.
>
> phil
>
> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:
>>
>> I have replaced the power unit, taken it off the power strip an 
>> plugged both it and the Vanatage into the mains. I have replaced the 
>> powered hub (official RPi one...with another official RPi one) 
>> ...and here 
>> is what I am getting...very dispirited! I have another Davis 
>> Weather 
>> Envoy which I will soon substitute for the one I am currently 
>> using.but 
>> nothing seems to make a difference and the Envoy just will not wake 
>> up!
>>
>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at 
>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: 
>> SPrintConnMgr: Failed to add printer: 
>> server-error-service-unavailable
>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers 
>> available
>> Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage 
>> normalised (0x)
>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake 
>> up console
>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: 
>> Unable to wake up Vantage console ()
>> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load 
>> driver: Unable to wake up Vantage console
>> Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
>> Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage 
>> detected! (0x00050005)
>> Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage 
>> normalised (0x)
>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
>> 103.239.8.22
>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
>> 202.46.185.18
>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
>> 203.99.128.48
>> Jan 29 

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

[Thomas Keffer]

Congratulations! Looks like it was a power supply problem.

USB power supplies fail. I had one that would show +5V under no load, but
it would sag to near nothing with just a modest load.

On Mon, Jan 28, 2019 at 5:26 PM monmul  wrote:

> It is working again!.This time I used both official power units...one
> to power the Pi and one to power the hub.
>
> On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote:
>>
>> Then you definitely have a connectivity problem!
>>
>> -tk
>>
>> On Mon, Jan 28, 2019 at 4:32 PM monmul  wrote:
>>
>>> Welcome to minicom 2.7
>>>
>>> OPTIONS: I18n
>>> Compiled on Apr 22 2017, 09:14:19.
>>> Port /dev/ttyUSB0, 13:15:39
>>>
>>> Press CTRL-A Z for help on special keys
>>>
>>> Even after lots or s nothing happens on TEST
>>>
>>> Similarly for screen...
>>>
>>> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote:

 The "establishing connectivity" instructions don't mention it, but be
 sure to hit  a few times before typing TEST.

 On Mon, Jan 28, 2019 at 4:11 PM monmul  wrote:

> Tried both screen and minicom.no TEST echo backso must be
> hardwarebut totally flummoxed as all hardware (apart from Rpi) has 
> been
> replaced.have another pi on orderbut in the meantime I guess I 
> will
> go back to scratch and start all over againat least it has worked
> before with this set upmaybe something has become corrupted!
>
>
> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote:
>>
>> Try to communicate directly with the Envoy, without going through
>> WeeWX. For how to do this, see the section *Establishing
>> connectivity
>> * in
>> the User's Guide. If you are unable to do that, then this is definitely a
>> hardware problem.
>>
>> -tk
>>
>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin  wrote:
>>
>>> Thanks, but no I don't I use VNC.
>>>
>>> On Tue, Jan 29, 2019 at 11:35 AM  wrote:
>>>
 Just a quick question. Do you have a monitor (like the Pi 7 in
 touch screen) attached that is running off the same power supply as 
 the Pi?
 I had a setup like that which used a splitter to power both the 
 monitor and
 Pi from one power pack. My setup kept complaining of undervolting 
 until I
 removed the splitter and plugged the monitor and pi each into their own
 power supply.

 phil

 On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:
>
> I have replaced the power unit, taken it off the power strip an
> plugged both it and the Vanatage into the mains. I have replaced the
> powered hub (official RPi one...with another official RPi one) ...and 
> here
> is what I am getting...very dispirited! I have another Davis 
> Weather
> Envoy which I will soon substitute for the one I am currently 
> using.but
> nothing seems to make a difference and the Envoy just will not wake 
> up!
>
> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at
> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]:
> SPrintConnMgr: Failed to add printer: server-error-service-unavailable
> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers
> available
> Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage
> normalised (0x)
> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up
> console
> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed:
> Unable to wake up Vantage console ()
> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load
> driver: Unable to wake up Vantage console
> Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
> Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage
> detected! (0x00050005)
> Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage
> normalised (0x)
> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server
> 103.239.8.22
> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server
> 202.46.185.18
> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server
> 203.99.128.48
> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server
> 103.106.66.123
> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
> 103.242.68.69
> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
> 103.106.65.219
> Jan 29 09:15:02 

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

[monmul]

It is working again!.This time I used both official power units...one 
to power the Pi and one to power the hub.

On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote:
>
> Then you definitely have a connectivity problem!
>
> -tk
>
> On Mon, Jan 28, 2019 at 4:32 PM monmul > 
> wrote:
>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 13:15:39
>>
>> Press CTRL-A Z for help on special keys
>>
>> Even after lots or s nothing happens on TEST
>>
>> Similarly for screen...
>>
>> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote:
>>>
>>> The "establishing connectivity" instructions don't mention it, but be 
>>> sure to hit  a few times before typing TEST.
>>>
>>> On Mon, Jan 28, 2019 at 4:11 PM monmul  wrote:
>>>
 Tried both screen and minicom.no TEST echo backso must be 
 hardwarebut totally flummoxed as all hardware (apart from Rpi) has 
 been 
 replaced.have another pi on orderbut in the meantime I guess I 
 will 
 go back to scratch and start all over againat least it has worked 
 before with this set upmaybe something has become corrupted!


 On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote:
>
> Try to communicate directly with the Envoy, without going through 
> WeeWX. For how to do this, see the section *Establishing connectivity 
> * in 
> the User's Guide. If you are unable to do that, then this is definitely a 
> hardware problem.
>
> -tk
>
> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin  wrote:
>
>> Thanks, but no I don't I use VNC.
>>
>> On Tue, Jan 29, 2019 at 11:35 AM  wrote:
>>
>>> Just a quick question. Do you have a monitor (like the Pi 7 in touch 
>>> screen) attached that is running off the same power supply as the Pi? I 
>>> had 
>>> a setup like that which used a splitter to power both the monitor and 
>>> Pi 
>>> from one power pack. My setup kept complaining of undervolting until I 
>>> removed the splitter and plugged the monitor and pi each into their own 
>>> power supply.
>>>
>>> phil
>>>
>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:

 I have replaced the power unit, taken it off the power strip an 
 plugged both it and the Vanatage into the mains. I have replaced the 
 powered hub (official RPi one...with another official RPi one) ...and 
 here 
 is what I am getting...very dispirited! I have another Davis 
 Weather 
 Envoy which I will soon substitute for the one I am currently 
 using.but 
 nothing seems to make a difference and the Envoy just will not wake up!

 pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
 Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at 
 /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
 Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: 
 Failed to add printer: server-error-service-unavailable
 Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers 
 available
 Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage 
 normalised (0x)
 Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up 
 console
 Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: 
 Unable to wake up Vantage console ()
 Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load 
 driver: Unable to wake up Vantage console
 Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
 Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage 
 detected! (0x00050005)
 Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage 
 normalised (0x)
 Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
 103.239.8.22
 Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
 202.46.185.18
 Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
 203.99.128.48
 Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
 103.106.66.123
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 103.242.68.69
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 103.106.65.219
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 103.242.70.5
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 122.252.188.99
 Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
 130.217.226.51
 Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
 

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

[monmul]

This is with debug set to 1 - see attached.does that give us any 
further information on the situation?




On Tuesday, 29 January 2019 13:34:45 UTC+13, Thomas Keffer wrote:
>
> Then you definitely have a connectivity problem!
>
> -tk
>
> On Mon, Jan 28, 2019 at 4:32 PM monmul > 
> wrote:
>
>> Welcome to minicom 2.7
>>
>> OPTIONS: I18n 
>> Compiled on Apr 22 2017, 09:14:19.
>> Port /dev/ttyUSB0, 13:15:39
>>
>> Press CTRL-A Z for help on special keys
>>
>> Even after lots or s nothing happens on TEST
>>
>> Similarly for screen...
>>
>> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote:
>>>
>>> The "establishing connectivity" instructions don't mention it, but be 
>>> sure to hit  a few times before typing TEST.
>>>
>>> On Mon, Jan 28, 2019 at 4:11 PM monmul  wrote:
>>>
 Tried both screen and minicom.no TEST echo backso must be 
 hardwarebut totally flummoxed as all hardware (apart from Rpi) has 
 been 
 replaced.have another pi on orderbut in the meantime I guess I 
 will 
 go back to scratch and start all over againat least it has worked 
 before with this set upmaybe something has become corrupted!


 On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote:
>
> Try to communicate directly with the Envoy, without going through 
> WeeWX. For how to do this, see the section *Establishing connectivity 
> * in 
> the User's Guide. If you are unable to do that, then this is definitely a 
> hardware problem.
>
> -tk
>
> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin  wrote:
>
>> Thanks, but no I don't I use VNC.
>>
>> On Tue, Jan 29, 2019 at 11:35 AM  wrote:
>>
>>> Just a quick question. Do you have a monitor (like the Pi 7 in touch 
>>> screen) attached that is running off the same power supply as the Pi? I 
>>> had 
>>> a setup like that which used a splitter to power both the monitor and 
>>> Pi 
>>> from one power pack. My setup kept complaining of undervolting until I 
>>> removed the splitter and plugged the monitor and pi each into their own 
>>> power supply.
>>>
>>> phil
>>>
>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:

 I have replaced the power unit, taken it off the power strip an 
 plugged both it and the Vanatage into the mains. I have replaced the 
 powered hub (official RPi one...with another official RPi one) ...and 
 here 
 is what I am getting...very dispirited! I have another Davis 
 Weather 
 Envoy which I will soon substitute for the one I am currently 
 using.but 
 nothing seems to make a difference and the Envoy just will not wake up!

 pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
 Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at 
 /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
 Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: 
 Failed to add printer: server-error-service-unavailable
 Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers 
 available
 Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage 
 normalised (0x)
 Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up 
 console
 Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: 
 Unable to wake up Vantage console ()
 Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load 
 driver: Unable to wake up Vantage console
 Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
 Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage 
 detected! (0x00050005)
 Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage 
 normalised (0x)
 Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
 103.239.8.22
 Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
 202.46.185.18
 Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
 203.99.128.48
 Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
 103.106.66.123
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 103.242.68.69
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 103.106.65.219
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 103.242.70.5
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 122.252.188.99
 Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
 130.217.226.51
 Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
 

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

[Thomas Keffer]

Then you definitely have a connectivity problem!

-tk

On Mon, Jan 28, 2019 at 4:32 PM monmul  wrote:

> Welcome to minicom 2.7
>
> OPTIONS: I18n
> Compiled on Apr 22 2017, 09:14:19.
> Port /dev/ttyUSB0, 13:15:39
>
> Press CTRL-A Z for help on special keys
>
> Even after lots or s nothing happens on TEST
>
> Similarly for screen...
>
> On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote:
>>
>> The "establishing connectivity" instructions don't mention it, but be
>> sure to hit  a few times before typing TEST.
>>
>> On Mon, Jan 28, 2019 at 4:11 PM monmul  wrote:
>>
>>> Tried both screen and minicom.no TEST echo backso must be
>>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has been
>>> replaced.have another pi on orderbut in the meantime I guess I will
>>> go back to scratch and start all over againat least it has worked
>>> before with this set upmaybe something has become corrupted!
>>>
>>>
>>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote:

 Try to communicate directly with the Envoy, without going through
 WeeWX. For how to do this, see the section *Establishing connectivity
 * in
 the User's Guide. If you are unable to do that, then this is definitely a
 hardware problem.

 -tk

 On Mon, Jan 28, 2019 at 2:41 PM dunbrokin  wrote:

> Thanks, but no I don't I use VNC.
>
> On Tue, Jan 29, 2019 at 11:35 AM  wrote:
>
>> Just a quick question. Do you have a monitor (like the Pi 7 in touch
>> screen) attached that is running off the same power supply as the Pi? I 
>> had
>> a setup like that which used a splitter to power both the monitor and Pi
>> from one power pack. My setup kept complaining of undervolting until I
>> removed the splitter and plugged the monitor and pi each into their own
>> power supply.
>>
>> phil
>>
>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:
>>>
>>> I have replaced the power unit, taken it off the power strip an
>>> plugged both it and the Vanatage into the mains. I have replaced the
>>> powered hub (official RPi one...with another official RPi one) ...and 
>>> here
>>> is what I am getting...very dispirited! I have another Davis Weather
>>> Envoy which I will soon substitute for the one I am currently 
>>> using.but
>>> nothing seems to make a difference and the Envoy just will not wake up!
>>>
>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at
>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr:
>>> Failed to add printer: server-error-service-unavailable
>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers
>>> available
>>> Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage
>>> normalised (0x)
>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up
>>> console
>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed:
>>> Unable to wake up Vantage console ()
>>> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load
>>> driver: Unable to wake up Vantage console
>>> Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
>>> Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage
>>> detected! (0x00050005)
>>> Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage
>>> normalised (0x)
>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.239.8.22
>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server
>>> 202.46.185.18
>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server
>>> 203.99.128.48
>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.106.66.123
>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.242.68.69
>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.106.65.219
>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.242.70.5
>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
>>> 122.252.188.99
>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
>>> 130.217.226.51
>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.242.68.68
>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
>>> 203.99.128.34
>>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server
>>> 202.46.177.18
>>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server
>>> 2407:f100:0:4::3
>>> Jan 29 09:15:06 raspberrypi ntpd[467]: Soliciting pool server
>>> 

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

[monmul]

Welcome to minicom 2.7

OPTIONS: I18n 
Compiled on Apr 22 2017, 09:14:19.
Port /dev/ttyUSB0, 13:15:39

Press CTRL-A Z for help on special keys

Even after lots or s nothing happens on TEST

Similarly for screen...

On Tuesday, 29 January 2019 13:22:19 UTC+13, Thomas Keffer wrote:
>
> The "establishing connectivity" instructions don't mention it, but be sure 
> to hit  a few times before typing TEST.
>
> On Mon, Jan 28, 2019 at 4:11 PM monmul > 
> wrote:
>
>> Tried both screen and minicom.no TEST echo backso must be 
>> hardwarebut totally flummoxed as all hardware (apart from Rpi) has been 
>> replaced.have another pi on orderbut in the meantime I guess I will 
>> go back to scratch and start all over againat least it has worked 
>> before with this set upmaybe something has become corrupted!
>>
>>
>> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote:
>>>
>>> Try to communicate directly with the Envoy, without going through WeeWX. 
>>> For how to do this, see the section *Establishing connectivity 
>>> * in 
>>> the User's Guide. If you are unable to do that, then this is definitely a 
>>> hardware problem.
>>>
>>> -tk
>>>
>>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin  wrote:
>>>
 Thanks, but no I don't I use VNC.

 On Tue, Jan 29, 2019 at 11:35 AM  wrote:

> Just a quick question. Do you have a monitor (like the Pi 7 in touch 
> screen) attached that is running off the same power supply as the Pi? I 
> had 
> a setup like that which used a splitter to power both the monitor and Pi 
> from one power pack. My setup kept complaining of undervolting until I 
> removed the splitter and plugged the monitor and pi each into their own 
> power supply.
>
> phil
>
> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:
>>
>> I have replaced the power unit, taken it off the power strip an 
>> plugged both it and the Vanatage into the mains. I have replaced the 
>> powered hub (official RPi one...with another official RPi one) ...and 
>> here 
>> is what I am getting...very dispirited! I have another Davis Weather 
>> Envoy which I will soon substitute for the one I am currently 
>> using.but 
>> nothing seems to make a difference and the Envoy just will not wake up!
>>
>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at 
>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: 
>> Failed to add printer: server-error-service-unavailable
>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers 
>> available
>> Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage normalised 
>> (0x)
>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up 
>> console
>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: 
>> Unable to wake up Vantage console ()
>> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load 
>> driver: Unable to wake up Vantage console
>> Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
>> Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage 
>> detected! (0x00050005)
>> Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage normalised 
>> (0x)
>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
>> 103.239.8.22
>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
>> 202.46.185.18
>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
>> 203.99.128.48
>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
>> 103.106.66.123
>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
>> 103.242.68.69
>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
>> 103.106.65.219
>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
>> 103.242.70.5
>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
>> 122.252.188.99
>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
>> 130.217.226.51
>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
>> 103.242.68.68
>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
>> 203.99.128.34
>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server 
>> 202.46.177.18
>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server 
>> 2407:f100:0:4::3
>> Jan 29 09:15:06 raspberrypi ntpd[467]: Soliciting pool server 
>> 202.46.178.18
>> Jan 29 09:17:41 raspberrypi systemd[584]: Time has been changed
>> Jan 29 09:17:41 raspberrypi systemd[1]: Time has been changed
>> Jan 29 09:17:41 

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

[Thomas Keffer]

The "establishing connectivity" instructions don't mention it, but be sure
to hit  a few times before typing TEST.

On Mon, Jan 28, 2019 at 4:11 PM monmul  wrote:

> Tried both screen and minicom.no TEST echo backso must be
> hardwarebut totally flummoxed as all hardware (apart from Rpi) has been
> replaced.have another pi on orderbut in the meantime I guess I will
> go back to scratch and start all over againat least it has worked
> before with this set upmaybe something has become corrupted!
>
>
> On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote:
>>
>> Try to communicate directly with the Envoy, without going through WeeWX.
>> For how to do this, see the section *Establishing connectivity
>> * in the
>> User's Guide. If you are unable to do that, then this is definitely a
>> hardware problem.
>>
>> -tk
>>
>> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin  wrote:
>>
>>> Thanks, but no I don't I use VNC.
>>>
>>> On Tue, Jan 29, 2019 at 11:35 AM  wrote:
>>>
 Just a quick question. Do you have a monitor (like the Pi 7 in touch
 screen) attached that is running off the same power supply as the Pi? I had
 a setup like that which used a splitter to power both the monitor and Pi
 from one power pack. My setup kept complaining of undervolting until I
 removed the splitter and plugged the monitor and pi each into their own
 power supply.

 phil

 On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:
>
> I have replaced the power unit, taken it off the power strip an
> plugged both it and the Vanatage into the mains. I have replaced the
> powered hub (official RPi one...with another official RPi one) ...and here
> is what I am getting...very dispirited! I have another Davis Weather
> Envoy which I will soon substitute for the one I am currently 
> using.but
> nothing seems to make a difference and the Envoy just will not wake up!
>
> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at
> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr:
> Failed to add printer: server-error-service-unavailable
> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers
> available
> Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage normalised
> (0x)
> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up
> console
> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed:
> Unable to wake up Vantage console ()
> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load driver:
> Unable to wake up Vantage console
> Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
> Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage
> detected! (0x00050005)
> Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage normalised
> (0x)
> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server
> 103.239.8.22
> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server
> 202.46.185.18
> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server
> 203.99.128.48
> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server
> 103.106.66.123
> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
> 103.242.68.69
> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
> 103.106.65.219
> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
> 103.242.70.5
> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
> 122.252.188.99
> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
> 130.217.226.51
> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
> 103.242.68.68
> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
> 203.99.128.34
> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server
> 202.46.177.18
> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server
> 2407:f100:0:4::3
> Jan 29 09:15:06 raspberrypi ntpd[467]: Soliciting pool server
> 202.46.178.18
> Jan 29 09:17:41 raspberrypi systemd[584]: Time has been changed
> Jan 29 09:17:41 raspberrypi systemd[1]: Time has been changed
> Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily.timer: Adding 9h
> 28min 39.184756s random time.
> Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily-upgrade.timer:
> Adding 27min 17.961005s random time.
> Jan 29 09:18:28 raspberrypi kernel: [  126.872661] Under-voltage
> detected! (0x00050005)
> Jan 29 09:18:34 raspberrypi kernel: [  133.112736] Voltage normalised
> (0x)
> Jan 29 09:18:34 raspberrypi CRON[1276]: (root) 

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

[monmul]

Tried both screen and minicom.no TEST echo backso must be 
hardwarebut totally flummoxed as all hardware (apart from Rpi) has been 
replaced.have another pi on orderbut in the meantime I guess I will 
go back to scratch and start all over againat least it has worked 
before with this set upmaybe something has become corrupted!


On Tuesday, 29 January 2019 12:11:06 UTC+13, Thomas Keffer wrote:
>
> Try to communicate directly with the Envoy, without going through WeeWX. 
> For how to do this, see the section *Establishing connectivity 
> * in the 
> User's Guide. If you are unable to do that, then this is definitely a 
> hardware problem.
>
> -tk
>
> On Mon, Jan 28, 2019 at 2:41 PM dunbrokin > 
> wrote:
>
>> Thanks, but no I don't I use VNC.
>>
>> On Tue, Jan 29, 2019 at 11:35 AM > wrote:
>>
>>> Just a quick question. Do you have a monitor (like the Pi 7 in touch 
>>> screen) attached that is running off the same power supply as the Pi? I had 
>>> a setup like that which used a splitter to power both the monitor and Pi 
>>> from one power pack. My setup kept complaining of undervolting until I 
>>> removed the splitter and plugged the monitor and pi each into their own 
>>> power supply.
>>>
>>> phil
>>>
>>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:

 I have replaced the power unit, taken it off the power strip an plugged 
 both it and the Vanatage into the mains. I have replaced the powered hub 
 (official RPi one...with another official RPi one) ...and here is what I 
 am 
 getting...very dispirited! I have another Davis Weather Envoy which I 
 will soon substitute for the one I am currently using.but nothing 
 seems 
 to make a difference and the Envoy just will not wake up!

 pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
 Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at 
 /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
 Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: 
 Failed to add printer: server-error-service-unavailable
 Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers 
 available
 Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage normalised 
 (0x)
 Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up 
 console
 Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: Unable 
 to wake up Vantage console ()
 Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load driver: 
 Unable to wake up Vantage console
 Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
 Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage 
 detected! (0x00050005)
 Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage normalised 
 (0x)
 Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
 103.239.8.22
 Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 
 202.46.185.18
 Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
 203.99.128.48
 Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
 103.106.66.123
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 103.242.68.69
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 103.106.65.219
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 103.242.70.5
 Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
 122.252.188.99
 Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
 130.217.226.51
 Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
 103.242.68.68
 Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
 203.99.128.34
 Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server 
 202.46.177.18
 Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server 
 2407:f100:0:4::3
 Jan 29 09:15:06 raspberrypi ntpd[467]: Soliciting pool server 
 202.46.178.18
 Jan 29 09:17:41 raspberrypi systemd[584]: Time has been changed
 Jan 29 09:17:41 raspberrypi systemd[1]: Time has been changed
 Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily.timer: Adding 9h 
 28min 39.184756s random time.
 Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
 27min 17.961005s random time.
 Jan 29 09:18:28 raspberrypi kernel: [  126.872661] Under-voltage 
 detected! (0x00050005)
 Jan 29 09:18:34 raspberrypi kernel: [  133.112736] Voltage normalised 
 (0x)
 Jan 29 09:18:34 raspberrypi CRON[1276]: (root) CMD (   cd / && 
 run-parts --report /etc/cron.hourly)
 Jan 29 09:22:29 raspberrypi kernel: [  368.155297] 
 rpi_firmware_get_throttled: 2 callbacks suppressed
 Jan 29 09:22:29 raspberrypi kernel: [  

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

[Thomas Keffer]

Try to communicate directly with the Envoy, without going through WeeWX.
For how to do this, see the section *Establishing connectivity
* in the
User's Guide. If you are unable to do that, then this is definitely a
hardware problem.

-tk

On Mon, Jan 28, 2019 at 2:41 PM dunbrokin  wrote:

> Thanks, but no I don't I use VNC.
>
> On Tue, Jan 29, 2019 at 11:35 AM  wrote:
>
>> Just a quick question. Do you have a monitor (like the Pi 7 in touch
>> screen) attached that is running off the same power supply as the Pi? I had
>> a setup like that which used a splitter to power both the monitor and Pi
>> from one power pack. My setup kept complaining of undervolting until I
>> removed the splitter and plugged the monitor and pi each into their own
>> power supply.
>>
>> phil
>>
>> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:
>>>
>>> I have replaced the power unit, taken it off the power strip an plugged
>>> both it and the Vanatage into the mains. I have replaced the powered hub
>>> (official RPi one...with another official RPi one) ...and here is what I am
>>> getting...very dispirited! I have another Davis Weather Envoy which I
>>> will soon substitute for the one I am currently using.but nothing seems
>>> to make a difference and the Envoy just will not wake up!
>>>
>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at
>>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
>>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr:
>>> Failed to add printer: server-error-service-unavailable
>>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers available
>>> Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage normalised
>>> (0x)
>>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up
>>> console
>>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: Unable
>>> to wake up Vantage console ()
>>> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load driver:
>>> Unable to wake up Vantage console
>>> Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
>>> Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage
>>> detected! (0x00050005)
>>> Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage normalised
>>> (0x)
>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.239.8.22
>>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server
>>> 202.46.185.18
>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server
>>> 203.99.128.48
>>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.106.66.123
>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.242.68.69
>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.106.65.219
>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.242.70.5
>>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
>>> 122.252.188.99
>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
>>> 130.217.226.51
>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
>>> 103.242.68.68
>>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
>>> 203.99.128.34
>>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server
>>> 202.46.177.18
>>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server
>>> 2407:f100:0:4::3
>>> Jan 29 09:15:06 raspberrypi ntpd[467]: Soliciting pool server
>>> 202.46.178.18
>>> Jan 29 09:17:41 raspberrypi systemd[584]: Time has been changed
>>> Jan 29 09:17:41 raspberrypi systemd[1]: Time has been changed
>>> Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily.timer: Adding 9h 28min
>>> 39.184756s random time.
>>> Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding
>>> 27min 17.961005s random time.
>>> Jan 29 09:18:28 raspberrypi kernel: [  126.872661] Under-voltage
>>> detected! (0x00050005)
>>> Jan 29 09:18:34 raspberrypi kernel: [  133.112736] Voltage normalised
>>> (0x)
>>> Jan 29 09:18:34 raspberrypi CRON[1276]: (root) CMD (   cd / && run-parts
>>> --report /etc/cron.hourly)
>>> Jan 29 09:22:29 raspberrypi kernel: [  368.155297]
>>> rpi_firmware_get_throttled: 2 callbacks suppressed
>>> Jan 29 09:22:29 raspberrypi kernel: [  368.155304] Under-voltage
>>> detected! (0x00050005)
>>> Jan 29 09:22:33 raspberrypi kernel: [  372.315315]
>>> rpi_firmware_get_throttled: 2 callbacks suppressed
>>> Jan 29 09:22:33 raspberrypi kernel: [  372.315322] Voltage normalised
>>> (0x)
>>> Jan 29 09:24:27 raspberrypi kernel: [  486.716533] Under-voltage
>>> detected! (0x00050005)
>>> Jan 29 09:24:34 raspberrypi kernel: [  492.956607] Voltage normalised
>>> (0x)
>>> Jan 29 09:26:28 raspberrypi kernel: [  607.357755] Under-voltage
>>> detected! (0x00050005)
>>> Jan 29 09:26:32 raspberrypi kernel: [  611.517793] 

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

[dunbrokin]

Thanks, but no I don't I use VNC.

On Tue, Jan 29, 2019 at 11:35 AM  wrote:

> Just a quick question. Do you have a monitor (like the Pi 7 in touch
> screen) attached that is running off the same power supply as the Pi? I had
> a setup like that which used a splitter to power both the monitor and Pi
> from one power pack. My setup kept complaining of undervolting until I
> removed the splitter and plugged the monitor and pi each into their own
> power supply.
>
> phil
>
> On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:
>>
>> I have replaced the power unit, taken it off the power strip an plugged
>> both it and the Vanatage into the mains. I have replaced the powered hub
>> (official RPi one...with another official RPi one) ...and here is what I am
>> getting...very dispirited! I have another Davis Weather Envoy which I
>> will soon substitute for the one I am currently using.but nothing seems
>> to make a difference and the Envoy just will not wake up!
>>
>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at
>> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
>> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr:
>> Failed to add printer: server-error-service-unavailable
>> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers available
>> Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage normalised
>> (0x)
>> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up console
>> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: Unable
>> to wake up Vantage console ()
>> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load driver:
>> Unable to wake up Vantage console
>> Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
>> Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage
>> detected! (0x00050005)
>> Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage normalised
>> (0x)
>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 103.239.8.22
>> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server
>> 202.46.185.18
>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server
>> 203.99.128.48
>> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server
>> 103.106.66.123
>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
>> 103.242.68.69
>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
>> 103.106.65.219
>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 103.242.70.5
>> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server
>> 122.252.188.99
>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
>> 130.217.226.51
>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
>> 103.242.68.68
>> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server
>> 203.99.128.34
>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server
>> 202.46.177.18
>> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server
>> 2407:f100:0:4::3
>> Jan 29 09:15:06 raspberrypi ntpd[467]: Soliciting pool server
>> 202.46.178.18
>> Jan 29 09:17:41 raspberrypi systemd[584]: Time has been changed
>> Jan 29 09:17:41 raspberrypi systemd[1]: Time has been changed
>> Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily.timer: Adding 9h 28min
>> 39.184756s random time.
>> Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding
>> 27min 17.961005s random time.
>> Jan 29 09:18:28 raspberrypi kernel: [  126.872661] Under-voltage
>> detected! (0x00050005)
>> Jan 29 09:18:34 raspberrypi kernel: [  133.112736] Voltage normalised
>> (0x)
>> Jan 29 09:18:34 raspberrypi CRON[1276]: (root) CMD (   cd / && run-parts
>> --report /etc/cron.hourly)
>> Jan 29 09:22:29 raspberrypi kernel: [  368.155297]
>> rpi_firmware_get_throttled: 2 callbacks suppressed
>> Jan 29 09:22:29 raspberrypi kernel: [  368.155304] Under-voltage
>> detected! (0x00050005)
>> Jan 29 09:22:33 raspberrypi kernel: [  372.315315]
>> rpi_firmware_get_throttled: 2 callbacks suppressed
>> Jan 29 09:22:33 raspberrypi kernel: [  372.315322] Voltage normalised
>> (0x)
>> Jan 29 09:24:27 raspberrypi kernel: [  486.716533] Under-voltage
>> detected! (0x00050005)
>> Jan 29 09:24:34 raspberrypi kernel: [  492.956607] Voltage normalised
>> (0x)
>> Jan 29 09:26:28 raspberrypi kernel: [  607.357755] Under-voltage
>> detected! (0x00050005)
>> Jan 29 09:26:32 raspberrypi kernel: [  611.517793] Voltage normalised
>> (0x)
>> Jan 29 09:26:45 raspberrypi ntpd[467]: 203.99.128.34 local addr 10.1.1.7
>> -> 
>> Jan 29 09:30:13 raspberrypi ntpd[467]: 103.239.8.22 local addr 10.1.1.7
>> -> 
>> Jan 29 09:30:45 raspberrypi ntpd[467]: 203.99.128.48 local addr 10.1.1.7
>> -> 
>> Jan 29 09:31:18 raspberrypi ntpd[467]: 122.252.188.99 local addr 10.1.1.7
>> -> 
>> Jan 29 09:31:23 raspberrypi systemd[1]: Starting Cleanup of Temporary
>> Directories...
>> 

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

[kutzenco]

Just a quick question. Do you have a monitor (like the Pi 7 in touch 
screen) attached that is running off the same power supply as the Pi? I had 
a setup like that which used a splitter to power both the monitor and Pi 
from one power pack. My setup kept complaining of undervolting until I 
removed the splitter and plugged the monitor and pi each into their own 
power supply.

phil

On Monday, January 28, 2019 at 3:41:15 PM UTC-5, monmul wrote:
>
> I have replaced the power unit, taken it off the power strip an plugged 
> both it and the Vanatage into the mains. I have replaced the powered hub 
> (official RPi one...with another official RPi one) ...and here is what I am 
> getting...very dispirited! I have another Davis Weather Envoy which I 
> will soon substitute for the one I am currently using.but nothing seems 
> to make a difference and the Envoy just will not wake up!
>
> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
> Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at 
> /media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
> Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: Failed 
> to add printer: server-error-service-unavailable
> Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers available
> Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage normalised 
> (0x)
> Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up console
> Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: Unable to 
> wake up Vantage console ()
> Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load driver: 
> Unable to wake up Vantage console
> Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
> Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage detected! 
> (0x00050005)
> Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage normalised 
> (0x)
> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 103.239.8.22
> Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 202.46.185.18
> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 203.99.128.48
> Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 
> 103.106.66.123
> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 103.242.68.69
> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
> 103.106.65.219
> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 103.242.70.5
> Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 
> 122.252.188.99
> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 
> 130.217.226.51
> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 103.242.68.68
> Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 203.99.128.34
> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server 202.46.177.18
> Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server 
> 2407:f100:0:4::3
> Jan 29 09:15:06 raspberrypi ntpd[467]: Soliciting pool server 202.46.178.18
> Jan 29 09:17:41 raspberrypi systemd[584]: Time has been changed
> Jan 29 09:17:41 raspberrypi systemd[1]: Time has been changed
> Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily.timer: Adding 9h 28min 
> 39.184756s random time.
> Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
> 27min 17.961005s random time.
> Jan 29 09:18:28 raspberrypi kernel: [  126.872661] Under-voltage detected! 
> (0x00050005)
> Jan 29 09:18:34 raspberrypi kernel: [  133.112736] Voltage normalised 
> (0x)
> Jan 29 09:18:34 raspberrypi CRON[1276]: (root) CMD (   cd / && run-parts 
> --report /etc/cron.hourly)
> Jan 29 09:22:29 raspberrypi kernel: [  368.155297] 
> rpi_firmware_get_throttled: 2 callbacks suppressed
> Jan 29 09:22:29 raspberrypi kernel: [  368.155304] Under-voltage detected! 
> (0x00050005)
> Jan 29 09:22:33 raspberrypi kernel: [  372.315315] 
> rpi_firmware_get_throttled: 2 callbacks suppressed
> Jan 29 09:22:33 raspberrypi kernel: [  372.315322] Voltage normalised 
> (0x)
> Jan 29 09:24:27 raspberrypi kernel: [  486.716533] Under-voltage detected! 
> (0x00050005)
> Jan 29 09:24:34 raspberrypi kernel: [  492.956607] Voltage normalised 
> (0x)
> Jan 29 09:26:28 raspberrypi kernel: [  607.357755] Under-voltage detected! 
> (0x00050005)
> Jan 29 09:26:32 raspberrypi kernel: [  611.517793] Voltage normalised 
> (0x)
> Jan 29 09:26:45 raspberrypi ntpd[467]: 203.99.128.34 local addr 10.1.1.7 
> -> 
> Jan 29 09:30:13 raspberrypi ntpd[467]: 103.239.8.22 local addr 10.1.1.7 -> 
> 
> Jan 29 09:30:45 raspberrypi ntpd[467]: 203.99.128.48 local addr 10.1.1.7 
> -> 
> Jan 29 09:31:18 raspberrypi ntpd[467]: 122.252.188.99 local addr 10.1.1.7 
> -> 
> Jan 29 09:31:23 raspberrypi systemd[1]: Starting Cleanup of Temporary 
> Directories...
> Jan 29 09:31:23 raspberrypi systemd[1]: Started Cleanup of Temporary 
> Directories.
> Jan 29 09:32:22 raspberrypi ntpd[467]: 130.217.226.51 local addr 10.1.1.7 
> -> 

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

[monmul]

I guess the best thing to do now is to start all over from scratch!!

On Tuesday, 29 January 2019 10:27:59 UTC+13, monmul wrote:
>
> pi@raspberrypi:~ $ wee_device --dumpUsing configuration file 
> /etc/weewx/weewx.conf
> Using Vantage driver version 3.0.11 (weewx.drivers.vantage)
> Traceback (most recent call last):
>   File "/usr/bin/wee_device", line 54, in 
> main()
>   File "/usr/bin/wee_device", line 51, in main
> device.configure(config_dict)
>   File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
> self.do_options(options, parser, config_dict, prompt)
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1970, in 
> do_options
> station = Vantage(**config_dict[DRIVER_NAME])
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 487, in __init__
> self._setup()
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 1278, in _setup
> self.port.wakeup_console(max_tries=self.max_tries)
>   File "/usr/share/weewx/weewx/drivers/vantage.py", line 94, in 
> wakeup_console
> raise weewx.WakeupError("Unable to wake up Vantage console")
> weewx.WakeupError: Unable to wake up Vantage console
> pi@raspberrypi:~ $ 
>
> On Tuesday, 29 January 2019 10:25:31 UTC+13, monmul wrote:
>>
>> Sorry, I think you are on the wrong thread!
>>
>> On Tuesday, 29 January 2019 10:20:30 UTC+13, ve2se wrote:
>>>
>>> May i have an url  for a web page running  weewx v3.9.0  with the new 
>>> skin to see what is look like 
>>> Jean-Pierre
>>>
>>> Le samedi 5 janvier 2019 20:37:27 UTC-5, monmul a écrit :

 I am new to weewx and am trying to set it up on my Rpi 3. I have a 
 Davis Vantage weather station. I have a serial Envoy data logger attaced 
 to 
 my Rpi with a serial/usb converter. In following the set up instructions, 
 I 
 get these errors!

 sudo weewxd weewx.conf
 Traceback (most recent call last):
   File "/usr/bin/weewxd", line 64, in 
 weewx.engine.main(options, args)
   File "/usr/share/weewx/weewx/engine.py", line 835, in main
 sane = os.stat(config_path).st_ctime
 OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
 pi@Weatherpi:~ $ tail -f /var/log/syslog
 Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
 sender=:1.16 path=/MediaEndpoint/A2DPSink
 Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
 Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
 Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
 Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
 Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
 next retry is Sun Jan  6 13:41:35 2019 [try 
 http://www.rsyslog.com/e/2007 ]
 Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx 
 version 3.8.2
 Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
 (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
 Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
 Linux-4.9.35-v7+-armv7l-with-debian-8.0
 Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
 Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
 Directories...
 Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
 next retry is Sun Jan  6 13:53:04 2019 [try 
 http://www.rsyslog.com/e/2007 ]
 Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
 Directories.
 Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group 
 rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
 Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
 next retry is Sun Jan  6 13:55:58 2019 [try 
 http://www.rsyslog.com/e/2007 ]
 Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group 
 rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]

 Please where have I gone wrong?


 .

 Hi,

 It appears that you are in the /home/pi directory and hence weewxd is 
 looking for weewx.conf in /home/pi. Use the full path for weewx.conf
  ie:

 $ sudo weewxd /etc/weewx/weewx.conf

 Gary



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

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

[monmul]

pi@raspberrypi:~ $ wee_device --dumpUsing configuration file 
/etc/weewx/weewx.conf
Using Vantage driver version 3.0.11 (weewx.drivers.vantage)
Traceback (most recent call last):
  File "/usr/bin/wee_device", line 54, in 
main()
  File "/usr/bin/wee_device", line 51, in main
device.configure(config_dict)
  File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure
self.do_options(options, parser, config_dict, prompt)
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1970, in do_options
station = Vantage(**config_dict[DRIVER_NAME])
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 487, in __init__
self._setup()
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1278, in _setup
self.port.wakeup_console(max_tries=self.max_tries)
  File "/usr/share/weewx/weewx/drivers/vantage.py", line 94, in 
wakeup_console
raise weewx.WakeupError("Unable to wake up Vantage console")
weewx.WakeupError: Unable to wake up Vantage console
pi@raspberrypi:~ $ 

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

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

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

[monmul]

Sorry, I think you are on the wrong thread!

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

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

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

[ve2se]

May i have an url  for a web page running  weewx v3.9.0  with the new skin 
to see what is look like 
Jean-Pierre

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

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

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

[monmul]

Nothing coming through!
pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop[ ok ] Stopping weewx (via 
systemctl): weewx.service.
pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
pi@raspberrypi:~ $ lsusb
Bus 001 Device 006: ID 13fe:4100 Kingston Technology Company Inc. Flash 
drive
Bus 001 Device 005: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 001 Device 004: ID 0403:6001 Future Technology Devices International, 
Ltd FT232 USB-Serial (UART) IC
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@raspberrypi:~ $ 


On Tuesday, 29 January 2019 10:11:51 UTC+13, monmul wrote:
>
> pi@raspberrypi:~ $ for id in core sdram_c sdram_i sdram_p ; do \ 
> >  echo -e "$id:\t$(vcgencmd measure_volts $id)" ; \ > done
> bash:  : command not found
> core: volt=1.2000V
> bash:  : command not found
> bash:  : command not found
> sdram_c: volt=1.2000V
> bash:  : command not found
> bash:  : command not found
> sdram_i: volt=1.2000V
> bash:  : command not found
> bash:  : command not found
> sdram_p: volt=1.2250V
> bash:  : command not found
>
>
> On Tuesday, 29 January 2019 10:04:38 UTC+13, monmul wrote:
>>
>> I have now replaced the old Envoy with a new envoy I had lying around. I 
>> have dug our the Vantage Pro 2 console from the basement and it is now up 
>> and running and displaying data. But this is what I get in my syslog!! Sigh!
>>
>>
>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>> Jan 29 09:44:48 raspberrypi kernel: [   18.711659] Voltage normalised 
>> (0x)
>> Jan 29 09:44:49 raspberrypi dhcpcd[327]: wlan0: no IPv6 Routers available
>> Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: 
>> connected: 10.1.1.155::47050 (TCP)
>> Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: 
>> authenticated: 10.1.1.155::47050 (TCP), as (anonymous) (d permissions)
>> Jan 29 09:44:51 raspberrypi vncserver-x11[446,root]: SPrintConnMgr: 
>> Failed to add printer: server-error-service-unavailable
>> Jan 29 09:44:52 raspberrypi kernel: [   22.871779] Under-voltage 
>> detected! (0x00050005)
>> Jan 29 09:44:54 raspberrypi weewx[495]: vantage: Unable to wake up console
>> Jan 29 09:44:54 raspberrypi weewx[495]: import of driver failed: Unable 
>> to wake up Vantage console ()
>> Jan 29 09:44:54 raspberrypi weewx[495]: engine: Unable to load driver: 
>> Unable to wake up Vantage console
>> Jan 29 09:44:54 raspberrypi weewx[495]:   Exiting...
>> Jan 29 09:45:00 raspberrypi kernel: [   31.191813] Voltage normalised 
>> (0x)
>> Jan 29 09:45:44 raspberrypi ntpd[466]: Soliciting pool server 
>> 103.106.66.123
>> Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 
>> 202.46.185.18
>> Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 
>> 130.217.226.51
>> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 
>> 203.99.128.34
>> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 
>> 202.46.177.18
>> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 
>> 202.46.178.18
>> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 
>> 103.106.65.219
>> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 
>> 2407:f100:0:4::3
>> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 
>> 202.46.179.18
>> Jan 29 09:51:43 raspberrypi systemd[576]: Time has been changed
>> Jan 29 09:51:43 raspberrypi ntpd[466]: receive: Unexpected origin 
>> timestamp 0xdff9e880.d9ce150e does not match aorg 00. from 
>> server@103.106.65.219 xmt 0xdff9e9de.fe39c8d9
>> Jan 29 09:51:43 raspberrypi systemd[1]: Time has been changed
>> Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
>> 37min 9.646374s random time.
>> Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily.timer: Adding 8h 39min 
>> 10.183019s random time.
>>
>> On Tuesday, 29 January 2019 09:55:16 UTC+13, vince wrote:
>>>
>>> On Monday, January 28, 2019 at 12:41:15 PM UTC-8, monmul wrote:

 I have replaced the power unit, taken it off the power strip an plugged 
 both it and the Vanatage into the mains. I have replaced the powered hub 
 (official RPi one...with another official RPi one) ...and here is what I 
 am 
 getting...very dispirited! I have another Davis Weather Envoy which I 
 will soon substitute for the one I am currently using.but nothing 
 seems 
 to make a difference and the Envoy just will not wake up!



>>> Still sounds like you have insufficient power to me.
>>> You might try measuring it.
>>>
>>>
>>> https://raspberrypi.stackexchange.com/questions/2136/how-do-i-measure-the-current-power-consumption
>>>
>>> (there are many such devices)
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop 

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

[monmul]

pi@raspberrypi:~ $ for id in core sdram_c sdram_i sdram_p ; do \ 
>  echo -e "$id:\t$(vcgencmd measure_volts $id)" ; \ > done
bash:  : command not found
core: volt=1.2000V
bash:  : command not found
bash:  : command not found
sdram_c: volt=1.2000V
bash:  : command not found
bash:  : command not found
sdram_i: volt=1.2000V
bash:  : command not found
bash:  : command not found
sdram_p: volt=1.2250V
bash:  : command not found


On Tuesday, 29 January 2019 10:04:38 UTC+13, monmul wrote:
>
> I have now replaced the old Envoy with a new envoy I had lying around. I 
> have dug our the Vantage Pro 2 console from the basement and it is now up 
> and running and displaying data. But this is what I get in my syslog!! Sigh!
>
>
> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
> Jan 29 09:44:48 raspberrypi kernel: [   18.711659] Voltage normalised 
> (0x)
> Jan 29 09:44:49 raspberrypi dhcpcd[327]: wlan0: no IPv6 Routers available
> Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: 
> connected: 10.1.1.155::47050 (TCP)
> Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: 
> authenticated: 10.1.1.155::47050 (TCP), as (anonymous) (d permissions)
> Jan 29 09:44:51 raspberrypi vncserver-x11[446,root]: SPrintConnMgr: Failed 
> to add printer: server-error-service-unavailable
> Jan 29 09:44:52 raspberrypi kernel: [   22.871779] Under-voltage detected! 
> (0x00050005)
> Jan 29 09:44:54 raspberrypi weewx[495]: vantage: Unable to wake up console
> Jan 29 09:44:54 raspberrypi weewx[495]: import of driver failed: Unable to 
> wake up Vantage console ()
> Jan 29 09:44:54 raspberrypi weewx[495]: engine: Unable to load driver: 
> Unable to wake up Vantage console
> Jan 29 09:44:54 raspberrypi weewx[495]:   Exiting...
> Jan 29 09:45:00 raspberrypi kernel: [   31.191813] Voltage normalised 
> (0x)
> Jan 29 09:45:44 raspberrypi ntpd[466]: Soliciting pool server 
> 103.106.66.123
> Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 202.46.185.18
> Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 
> 130.217.226.51
> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 203.99.128.34
> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.177.18
> Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.178.18
> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 
> 103.106.65.219
> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 
> 2407:f100:0:4::3
> Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 202.46.179.18
> Jan 29 09:51:43 raspberrypi systemd[576]: Time has been changed
> Jan 29 09:51:43 raspberrypi ntpd[466]: receive: Unexpected origin 
> timestamp 0xdff9e880.d9ce150e does not match aorg 00. from 
> server@103.106.65.219 xmt 0xdff9e9de.fe39c8d9
> Jan 29 09:51:43 raspberrypi systemd[1]: Time has been changed
> Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
> 37min 9.646374s random time.
> Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily.timer: Adding 8h 39min 
> 10.183019s random time.
>
> On Tuesday, 29 January 2019 09:55:16 UTC+13, vince wrote:
>>
>> On Monday, January 28, 2019 at 12:41:15 PM UTC-8, monmul wrote:
>>>
>>> I have replaced the power unit, taken it off the power strip an plugged 
>>> both it and the Vanatage into the mains. I have replaced the powered hub 
>>> (official RPi one...with another official RPi one) ...and here is what I am 
>>> getting...very dispirited! I have another Davis Weather Envoy which I 
>>> will soon substitute for the one I am currently using.but nothing seems 
>>> to make a difference and the Envoy just will not wake up!
>>>
>>>
>>>
>> Still sounds like you have insufficient power to me.
>> You might try measuring it.
>>
>>
>> https://raspberrypi.stackexchange.com/questions/2136/how-do-i-measure-the-current-power-consumption
>>
>> (there are many such devices)
>>
>

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

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

[monmul]

I have now replaced the old Envoy with a new envoy I had lying around. I 
have dug our the Vantage Pro 2 console from the basement and it is now up 
and running and displaying data. But this is what I get in my syslog!! Sigh!


pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
Jan 29 09:44:48 raspberrypi kernel: [   18.711659] Voltage normalised 
(0x)
Jan 29 09:44:49 raspberrypi dhcpcd[327]: wlan0: no IPv6 Routers available
Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: 
connected: 10.1.1.155::47050 (TCP)
Jan 29 09:44:50 raspberrypi vncserver-x11[446,root]: Connections: 
authenticated: 10.1.1.155::47050 (TCP), as (anonymous) (d permissions)
Jan 29 09:44:51 raspberrypi vncserver-x11[446,root]: SPrintConnMgr: Failed 
to add printer: server-error-service-unavailable
Jan 29 09:44:52 raspberrypi kernel: [   22.871779] Under-voltage detected! 
(0x00050005)
Jan 29 09:44:54 raspberrypi weewx[495]: vantage: Unable to wake up console
Jan 29 09:44:54 raspberrypi weewx[495]: import of driver failed: Unable to 
wake up Vantage console ()
Jan 29 09:44:54 raspberrypi weewx[495]: engine: Unable to load driver: 
Unable to wake up Vantage console
Jan 29 09:44:54 raspberrypi weewx[495]:   Exiting...
Jan 29 09:45:00 raspberrypi kernel: [   31.191813] Voltage normalised 
(0x)
Jan 29 09:45:44 raspberrypi ntpd[466]: Soliciting pool server 103.106.66.123
Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 202.46.185.18
Jan 29 09:45:45 raspberrypi ntpd[466]: Soliciting pool server 130.217.226.51
Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 203.99.128.34
Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.177.18
Jan 29 09:45:46 raspberrypi ntpd[466]: Soliciting pool server 202.46.178.18
Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 103.106.65.219
Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 
2407:f100:0:4::3
Jan 29 09:45:47 raspberrypi ntpd[466]: Soliciting pool server 202.46.179.18
Jan 29 09:51:43 raspberrypi systemd[576]: Time has been changed
Jan 29 09:51:43 raspberrypi ntpd[466]: receive: Unexpected origin timestamp 
0xdff9e880.d9ce150e does not match aorg 00. from 
server@103.106.65.219 xmt 0xdff9e9de.fe39c8d9
Jan 29 09:51:43 raspberrypi systemd[1]: Time has been changed
Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
37min 9.646374s random time.
Jan 29 09:51:43 raspberrypi systemd[1]: apt-daily.timer: Adding 8h 39min 
10.183019s random time.

On Tuesday, 29 January 2019 09:55:16 UTC+13, vince wrote:
>
> On Monday, January 28, 2019 at 12:41:15 PM UTC-8, monmul wrote:
>>
>> I have replaced the power unit, taken it off the power strip an plugged 
>> both it and the Vanatage into the mains. I have replaced the powered hub 
>> (official RPi one...with another official RPi one) ...and here is what I am 
>> getting...very dispirited! I have another Davis Weather Envoy which I 
>> will soon substitute for the one I am currently using.but nothing seems 
>> to make a difference and the Envoy just will not wake up!
>>
>>
>>
> Still sounds like you have insufficient power to me.
> You might try measuring it.
>
>
> https://raspberrypi.stackexchange.com/questions/2136/how-do-i-measure-the-current-power-consumption
>
> (there are many such devices)
>

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

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

[vince]

On Monday, January 28, 2019 at 12:41:15 PM UTC-8, monmul wrote:
>
> I have replaced the power unit, taken it off the power strip an plugged 
> both it and the Vanatage into the mains. I have replaced the powered hub 
> (official RPi one...with another official RPi one) ...and here is what I am 
> getting...very dispirited! I have another Davis Weather Envoy which I 
> will soon substitute for the one I am currently using.but nothing seems 
> to make a difference and the Envoy just will not wake up!
>
>
>
Still sounds like you have insufficient power to me.
You might try measuring it.

https://raspberrypi.stackexchange.com/questions/2136/how-do-i-measure-the-current-power-consumption

(there are many such devices)

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

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

[monmul]

I have replaced the power unit, taken it off the power strip an plugged 
both it and the Vanatage into the mains. I have replaced the powered hub 
(official RPi one...with another official RPi one) ...and here is what I am 
getting...very dispirited! I have another Davis Weather Envoy which I 
will soon substitute for the one I am currently using.but nothing seems 
to make a difference and the Envoy just will not wake up!

pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
Jan 29 09:14:05 raspberrypi udisksd[766]: Mounted /dev/sda1 at 
/media/pi/e78ab10a-51d2-40f0-aa6d-5f2d2b0f27b7 on behalf of uid 1000
Jan 29 09:14:05 raspberrypi vncserver-x11[453,root]: SPrintConnMgr: Failed 
to add printer: server-error-service-unavailable
Jan 29 09:14:07 raspberrypi dhcpcd[338]: wlan0: no IPv6 Routers available
Jan 29 09:14:10 raspberrypi kernel: [   22.871754] Voltage normalised 
(0x)
Jan 29 09:14:12 raspberrypi weewx[506]: vantage: Unable to wake up console
Jan 29 09:14:12 raspberrypi weewx[506]: import of driver failed: Unable to 
wake up Vantage console ()
Jan 29 09:14:12 raspberrypi weewx[506]: engine: Unable to load driver: 
Unable to wake up Vantage console
Jan 29 09:14:12 raspberrypi weewx[506]:   Exiting...
Jan 29 09:14:27 raspberrypi kernel: [   39.511958] Under-voltage detected! 
(0x00050005)
Jan 29 09:14:31 raspberrypi kernel: [   43.671921] Voltage normalised 
(0x)
Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 103.239.8.22
Jan 29 09:15:00 raspberrypi ntpd[467]: Soliciting pool server 202.46.185.18
Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 203.99.128.48
Jan 29 09:15:01 raspberrypi ntpd[467]: Soliciting pool server 103.106.66.123
Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 103.242.68.69
Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 103.106.65.219
Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 103.242.70.5
Jan 29 09:15:02 raspberrypi ntpd[467]: Soliciting pool server 122.252.188.99
Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 130.217.226.51
Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 103.242.68.68
Jan 29 09:15:03 raspberrypi ntpd[467]: Soliciting pool server 203.99.128.34
Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server 202.46.177.18
Jan 29 09:15:04 raspberrypi ntpd[467]: Soliciting pool server 
2407:f100:0:4::3
Jan 29 09:15:06 raspberrypi ntpd[467]: Soliciting pool server 202.46.178.18
Jan 29 09:17:41 raspberrypi systemd[584]: Time has been changed
Jan 29 09:17:41 raspberrypi systemd[1]: Time has been changed
Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily.timer: Adding 9h 28min 
39.184756s random time.
Jan 29 09:17:41 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
27min 17.961005s random time.
Jan 29 09:18:28 raspberrypi kernel: [  126.872661] Under-voltage detected! 
(0x00050005)
Jan 29 09:18:34 raspberrypi kernel: [  133.112736] Voltage normalised 
(0x)
Jan 29 09:18:34 raspberrypi CRON[1276]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Jan 29 09:22:29 raspberrypi kernel: [  368.155297] 
rpi_firmware_get_throttled: 2 callbacks suppressed
Jan 29 09:22:29 raspberrypi kernel: [  368.155304] Under-voltage detected! 
(0x00050005)
Jan 29 09:22:33 raspberrypi kernel: [  372.315315] 
rpi_firmware_get_throttled: 2 callbacks suppressed
Jan 29 09:22:33 raspberrypi kernel: [  372.315322] Voltage normalised 
(0x)
Jan 29 09:24:27 raspberrypi kernel: [  486.716533] Under-voltage detected! 
(0x00050005)
Jan 29 09:24:34 raspberrypi kernel: [  492.956607] Voltage normalised 
(0x)
Jan 29 09:26:28 raspberrypi kernel: [  607.357755] Under-voltage detected! 
(0x00050005)
Jan 29 09:26:32 raspberrypi kernel: [  611.517793] Voltage normalised 
(0x)
Jan 29 09:26:45 raspberrypi ntpd[467]: 203.99.128.34 local addr 10.1.1.7 -> 

Jan 29 09:30:13 raspberrypi ntpd[467]: 103.239.8.22 local addr 10.1.1.7 -> 

Jan 29 09:30:45 raspberrypi ntpd[467]: 203.99.128.48 local addr 10.1.1.7 -> 

Jan 29 09:31:18 raspberrypi ntpd[467]: 122.252.188.99 local addr 10.1.1.7 
-> 
Jan 29 09:31:23 raspberrypi systemd[1]: Starting Cleanup of Temporary 
Directories...
Jan 29 09:31:23 raspberrypi systemd[1]: Started Cleanup of Temporary 
Directories.
Jan 29 09:32:22 raspberrypi ntpd[467]: 130.217.226.51 local addr 10.1.1.7 
-> 
Jan 29 09:32:59 raspberrypi kernel: [  998.401865] Under-voltage detected! 
(0x00050005)
Jan 29 09:33:03 raspberrypi kernel: [ 1002.561870] Voltage normalised 
(0x)
Jan 29 09:33:05 raspberrypi kernel: [ 1004.643095] Under-voltage detected! 
(0x00050005)
Jan 29 09:33:12 raspberrypi kernel: [ 1010.882010] Voltage normalised 
(0x)
Jan 29 09:33:22 raspberrypi kernel: [ 1021.282184] Under-voltage detected! 
(0x00050005)
Jan 29 09:33:34 raspberrypi kernel: [ 1033.762240] Voltage normalised 
(0x)
Jan 29 09:34:42 raspberrypi ntpd[467]: 103.106.66.123 local addr 10.1.1.7 
-> 
Jan 29 09:35:16 raspberrypi 

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

[vince]

On Monday, January 28, 2019 at 11:34:08 AM UTC-8, monmul wrote:
>
> I do have a spare official power supply, so I will swap out that and test. 
> ... I have a Pi3B+ on the way
>

Reminder, the pi3b+ need 'more' power and runs a little hotter than the 
others, so definitely be certain you have a quality power supply.

I have had great luck with 
https://www.amazon.com/CanaKit-Raspberry-Power-Supply-Listed/dp/B07BC6WH7V 
just as one example.  Also like the nice on/off switch dongle that came 
with it.

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

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

[monmul]

Apologies, you may well be right...it seems the most obvious culprit now! I 
don't have an RTC attached to my RPias I was told (much earlier in this 
thread) that the software changes I made to the resolv.conf files would 
suffice.

On Tuesday, 29 January 2019 00:32:59 UTC+13, Andrew Milner wrote:
>
> I beg to differ regarding the voltage issue.  If your RPi is suffering 
> from voltage going out of spec as the log implies then this will almost 
> definitely result in corruption over usb and possibly on the memory card 
> also.  Any corruptions can then result in timestamp issues.  Do you also 
> have a RTC installed on the RPi - this is almost an essential item. The 
> times on the RPi and the Vantage must remain almost in sync for things to 
> work seamlessly.  If the volyage issue causes a reboot, for example, it is 
> possible for the rpi to get an erroneous time for a period which could 
> either get written to the database or prevent satisfactory restart and 
> catchup from the vantage befpre resuming normal operations.
>
> I'm sorry but I still think you need to solve the voltage issue first and 
> ensure that is 100% stable before starting to chase other issues such as 
> time stamps.  I can virtually guarantee the issues you see are most 
> unlikely to be a result of anything wrong within weewx itself - and 
> especially with a Davis Vantage for which weewx was originally developed 
> many moons ago.
>
>
>
>
> On Monday, 28 January 2019 12:08:56 UTC+2, monmul wrote:
>>
>> Thank you, yesbut where will I find this log that I needas in 
>> which folder and what will it be called?
>>
>> On Monday, 28 January 2019 22:57:50 UTC+13, gjr80 wrote:
>>>
>>> Hi,
>>>
>>> Yep the logs are your friend. Usually you are interested in what 
>>> happened in the lead up to the event. You mentioned 19:20 but your log 
>>> extract is from around 21:44, what do the logs show around 19:20? Try and 
>>> find the point where WeeWX exited and work backwards from time there, may 5 
>>> or 10 minutes. The log extract you posted showed an issue at 21:44:02 but 
>>> there is only one unrelated entry before that, what else is in the log in 
>>> the lead up to 21:44:02? Maybe paste the log from reboot until error.
>>>
>>> Gary
>>>
>>>

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

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

[monmul]

No, Vantage has its own power supply.

On Tuesday, 29 January 2019 06:01:14 UTC+13, vince wrote:
>
>
> On Monday, January 28, 2019 at 1:56:14 AM UTC-8, monmul wrote:
>>
>> To be honest, I don't think it is the voltage problemI think it is a 
>> time stamp problem, I had to go through the whole --dump and -- 
>> clear-memory again to get reporting restarted.less than a week since 
>> this last happened!
>>
>>
>>
> Are you perhaps powering your Davis console off the same USB hub ? 
>

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

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

[monmul]

I do have a spare official power supply, so I will swap out that and test. 
I notice that after doing the -dump (after stopping weewx) and 
--clear-memory routine and then reboot, that the missing data does not 
appear in the graphs! The official power units supplies the official USB 
hub with power and the Pi is powered from this USB hub.  The Vantage, which 
has its own power supply and battery backup) sends the data through the USB 
hub to the Pi..I have tried connecting it directly to the Pi 
also...does not seem to make any difference. I have a Pi3B+ on the way, so 
I can swap out the current SD card and try it in that.Nothing else, apart 
from a USB (for back up purposes via Deja Dup). I am running the power from 
a socket strip..so might try plugging the Pi directly into the mains.

On Monday, 28 January 2019 23:41:14 UTC+13, gjr80 wrote:
>
> Hmm, not too much to pinpoint the culprit there. Could it be a power 
> supply issue, of course, official power supply or not it could still be the 
> culprit. You could check the output with a meter but will unlikely show any 
> transient fluctuations that could be causing a problem. Worth doing if you 
> can though. Swapping out the power supply or RPi itself is probably not 
> feasible unless you happen to have a spare.
>
> Could be an issue with the logger, can help by reseating it/making sure it 
> is inserted securely. Could be power to your console (you have an envoy if 
> I remember correctly), what is your mains like? Do you have an UPS from 
> which you can power both RPi and station.
>
> What is plugged into the RPi, powered hub, keyboard? monitor? Might sound 
> odd but can you run without the hub and plug the station into the RPi 
> direct. Are there any long cable runs, obvious one to look at is 5V to the 
> RPi but if that is the official power supply probably not much to be done 
> there.
>
> Sorry these are all a bit woolly but these sorts of issues can be 
> difficult to nail down.
>
> Gary
>
>

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

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

[vince]

On Monday, January 28, 2019 at 1:56:14 AM UTC-8, monmul wrote:
>
> To be honest, I don't think it is the voltage problemI think it is a 
> time stamp problem, I had to go through the whole --dump and -- 
> clear-memory again to get reporting restarted.less than a week since 
> this last happened!
>
>
>
Are you perhaps powering your Davis console off the same USB hub ? 

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

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

[Andrew Milner]

I beg to differ regarding the voltage issue.  If your RPi is suffering from 
voltage going out of spec as the log implies then this will almost 
definitely result in corruption over usb and possibly on the memory card 
also.  Any corruptions can then result in timestamp issues.  Do you also 
have a RTC installed on the RPi - this is almost an essential item. The 
times on the RPi and the Vantage must remain almost in sync for things to 
work seamlessly.  If the volyage issue causes a reboot, for example, it is 
possible for the rpi to get an erroneous time for a period which could 
either get written to the database or prevent satisfactory restart and 
catchup from the vantage befpre resuming normal operations.

I'm sorry but I still think you need to solve the voltage issue first and 
ensure that is 100% stable before starting to chase other issues such as 
time stamps.  I can virtually guarantee the issues you see are most 
unlikely to be a result of anything wrong within weewx itself - and 
especially with a Davis Vantage for which weewx was originally developed 
many moons ago.




On Monday, 28 January 2019 12:08:56 UTC+2, monmul wrote:
>
> Thank you, yesbut where will I find this log that I needas in 
> which folder and what will it be called?
>
> On Monday, 28 January 2019 22:57:50 UTC+13, gjr80 wrote:
>>
>> Hi,
>>
>> Yep the logs are your friend. Usually you are interested in what happened 
>> in the lead up to the event. You mentioned 19:20 but your log extract is 
>> from around 21:44, what do the logs show around 19:20? Try and find the 
>> point where WeeWX exited and work backwards from time there, may 5 or 10 
>> minutes. The log extract you posted showed an issue at 21:44:02 but there 
>> is only one unrelated entry before that, what else is in the log in the 
>> lead up to 21:44:02? Maybe paste the log from reboot until error.
>>
>> Gary
>>
>>

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

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

[gjr80]

Hmm, not too much to pinpoint the culprit there. Could it be a power supply 
issue, of course, official power supply or not it could still be the culprit. 
You could check the output with a meter but will unlikely show any transient 
fluctuations that could be causing a problem. Worth doing if you can though. 
Swapping out the power supply or RPi itself is probably not feasible unless you 
happen to have a spare.

Could be an issue with the logger, can help by reseating it/making sure it is 
inserted securely. Could be power to your console (you have an envoy if I 
remember correctly), what is your mains like? Do you have an UPS from which you 
can power both RPi and station.

What is plugged into the RPi, powered hub, keyboard? monitor? Might sound odd 
but can you run without the hub and plug the station into the RPi direct. Are 
there any long cable runs, obvious one to look at is 5V to the RPi but if that 
is the official power supply probably not much to be done there.

Sorry these are all a bit woolly but these sorts of issues can be difficult to 
nail down.

Gary

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

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

[monmul]

Thank youI did not understand that is what I was doing..here from 
19.10 last good report to when the next report was expected.

Jan 28 19:10:19 raspberrypi weewx[531]: manager: Added record 2019-01-28 
19:10:00 NZDT (1548655800) to database 'weewx.sdb'
Jan 28 19:10:19 raspberrypi weewx[531]: manager: Added record 2019-01-28 
19:10:00 NZDT (1548655800) to daily summary in 'weewx.sdb'
Jan 28 19:10:19 raspberrypi weewx[531]: restx: Wunderground-PWS: Published 
record 2019-01-28 19:10:00 NZDT (1548655800)
Jan 28 19:10:20 raspberrypi weewx[531]: cheetahgenerator: Generated 15 
files for report StandardReport in 1.65 seconds
Jan 28 19:10:21 raspberrypi weewx[531]: imagegenerator: Generated 12 images 
for StandardReport in 0.88 seconds
Jan 28 19:10:21 raspberrypi weewx[531]: copygenerator: copied 0 files to 
/var/www/html/weewx
Jan 28 19:10:21 raspberrypi weewx[531]: cheetahgenerator: Generated 1 files 
for report xstats in 0.04 seconds
Jan 28 19:10:27 raspberrypi weewx[531]: ftpgenerator: ftp'd 28 files in 
5.27 seconds
Jan 28 19:12:01 raspberrypi kernel: [6.033449] 
rpi_firmware_get_throttled: 1 callbacks suppressed
Jan 28 19:12:01 raspberrypi kernel: [6.033457] Under-voltage detected! 
(0x00050005)
Jan 28 19:12:07 raspberrypi kernel: [77782.273481] 
rpi_firmware_get_throttled: 1 callbacks suppressed
Jan 28 19:12:07 raspberrypi kernel: [77782.273487] Voltage normalised 
(0x)
Jan 28 19:13:08 raspberrypi vncserver-x11[465,root]: Connections: 
disconnected: 10.1.1.155::33538 (TCP) ([IdleTimeout] This connection has 
timed out through inactivity.)
Jan 28 19:15:53 raspberrypi weewx[531]: vantage: LOOP try #1; error: 
Expected to read 99 chars; got 0 instead
Jan 28 19:16:00 raspberrypi kernel: [78015.235265] Under-voltage detected! 
(0x00050005)
Jan 28 19:16:06 raspberrypi kernel: [78021.475297] Voltage normalised 
(0x)
Jan 28 19:16:09 raspberrypi weewx[531]: vantage: Unable to wake up console
Jan 28 19:16:09 raspberrypi weewx[531]: vantage: LOOP try #2; error: Unable 
to wake up Vantage console
Jan 28 19:16:25 raspberrypi weewx[531]: vantage: Unable to wake up console
Jan 28 19:16:25 raspberrypi weewx[531]: vantage: LOOP try #3; error: Unable 
to wake up Vantage console
Jan 28 19:16:41 raspberrypi weewx[531]: vantage: Unable to wake up console
Jan 28 19:16:41 raspberrypi weewx[531]: vantage: LOOP try #4; error: Unable 
to wake up Vantage console
Jan 28 19:16:41 raspberrypi weewx[531]: vantage: LOOP max tries (4) 
exceeded.
Jan 28 19:16:41 raspberrypi weewx[531]: engine: Shutting down StdReport 
thread
Jan 28 19:16:41 raspberrypi weewx[531]: engine: Caught WeeWxIOError: Max 
tries exceeded while getting LOOP data.
Jan 28 19:16:41 raspberrypi weewx[531]:   Waiting 60 seconds then 
retrying...
Jan 28 19:17:01 raspberrypi CRON[10729]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Jan 28 19:17:41 raspberrypi weewx[531]: engine: retrying...
Jan 28 19:17:41 raspberrypi weewx[531]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jan 28 19:17:41 raspberrypi weewx[531]: engine: Loading station type 
Vantage (weewx.drivers.vantage)
Jan 28 19:17:57 raspberrypi weewx[531]: vantage: Unable to wake up console
Jan 28 19:17:57 raspberrypi weewx[531]: import of driver failed: Unable to 
wake up Vantage console ()
Jan 28 19:17:57 raspberrypi weewx[531]: engine: Unable to load driver: 
Unable to wake up Vantage console
Jan 28 19:17:57 raspberrypi weewx[531]:   Exiting...
Jan 28 19:23:12 raspberrypi kernel: [78447.878557] Under-voltage detected! 
(0x00050005)
Jan 28 19:23:19 raspberrypi kernel: [78454.118624] Voltage normalised 
(0x)
Jan 28 19:24:50 raspberrypi kernel: [78545.639346] Under-voltage detected! 
(0x00050005)
Jan 28 19:24:54 raspberrypi kernel: [78549.799434] Voltage normalised 
(0x)
Jan 28 19:40:26 raspberrypi kernel: [79481.646371] Under-voltage detected! 
(0x00050005)
Jan 28 19:40:32 raspberrypi kernel: [79487.886450] Voltage normalised 
(0x)


On Monday, 28 January 2019 23:11:24 UTC+13, gjr80 wrote:
>
> We you tailed it here:
>
> > pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>
> /var/log/syslog might be a good place to look :)
>
> Gary
>
>

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

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

[gjr80]

We you tailed it here:

> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog

/var/log/syslog might be a good place to look :)

Gary

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

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

[monmul]

Thank you, yesbut where will I find this log that I needas in which 
folder and what will it be called?

On Monday, 28 January 2019 22:57:50 UTC+13, gjr80 wrote:
>
> Hi,
>
> Yep the logs are your friend. Usually you are interested in what happened 
> in the lead up to the event. You mentioned 19:20 but your log extract is 
> from around 21:44, what do the logs show around 19:20? Try and find the 
> point where WeeWX exited and work backwards from time there, may 5 or 10 
> minutes. The log extract you posted showed an issue at 21:44:02 but there 
> is only one unrelated entry before that, what else is in the log in the 
> lead up to 21:44:02? Maybe paste the log from reboot until error.
>
> Gary
>
>

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

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

[gjr80]

Hi,

Yep the logs are your friend. Usually you are interested in what happened in 
the lead up to the event. You mentioned 19:20 but your log extract is from 
around 21:44, what do the logs show around 19:20? Try and find the point where 
WeeWX exited and work backwards from time there, may 5 or 10 minutes. The log 
extract you posted showed an issue at 21:44:02 but there is only one unrelated 
entry before that, what else is in the log in the lead up to 21:44:02? Maybe 
paste the log from reboot until error.

Gary

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

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

[monmul]

How can I find our (from the logs I presume) what caused the Pi to go down 
in the first place after running well for 2 or 3 days?

On Monday, 28 January 2019 22:23:41 UTC+13, monmul wrote:
>
> I am using a powered hub and I am using the official RPi power source.
>
> On Mon, Jan 28, 2019 at 10:05 PM Andrew Milner <
> andrew.s.r.mil...@gmail.com> wrote:
>
>> I would suggest you work on eliminating the under voltage errors before 
>> trying to work out why you cannot communicate with the weather station.  
>> The implication is that the RPi is having trouble coping with whatever you 
>> have got connected via usb and/or network.  This is not unusual and 
>> indicates you may need either a larger power supply or a powered usb hub to 
>> cope with your usb loads.
>>
>>
>>
>> On Monday, 28 January 2019 10:52:28 UTC+2, monmul wrote:
>>>
>>> My Pi stopped reporting at 19.20 today and despite rebooting twice, it 
>>> does not seem to be able to wake up the console..is there a way/log I 
>>> can query to find out why it might have stopped at 19.10it was working 
>>> fine for 2 or 3 days. Here is the syslog...
>>>
>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>>> Jan 28 21:43:57 raspberrypi dhcpcd[350]: wlan0: no IPv6 Routers available
>>> Jan 28 21:44:02 raspberrypi weewx[510]: vantage: Unable to wake up 
>>> console
>>> Jan 28 21:44:02 raspberrypi weewx[510]: import of driver failed: Unable 
>>> to wake up Vantage console ()
>>> Jan 28 21:44:02 raspberrypi weewx[510]: engine: Unable to load driver: 
>>> Unable to wake up Vantage console
>>> Jan 28 21:44:02 raspberrypi weewx[510]:   Exiting...
>>> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: 
>>> connected: 10.1.1.155::40108 (TCP)
>>> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: 
>>> authenticated: 10.1.1.155::40108 (TCP), as (anonymous) (d permissions)
>>> Jan 28 21:44:04 raspberrypi vncserver-x11[461,root]: SPrintConnMgr: 
>>> Failed to add printer: server-error-service-unavailable
>>> Jan 28 21:44:04 raspberrypi kernel: [   27.031827] Under-voltage 
>>> detected! (0x00050005)
>>> Jan 28 21:44:10 raspberrypi kernel: [   33.271789] Voltage normalised 
>>> (0x)
>>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 
>>> 88.191.250.97
>>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 37.187.18.4
>>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 
>>> 103.106.66.123
>>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 
>>> 103.106.65.219
>>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 
>>> 203.159.70.33
>>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 
>>> 103.242.70.5
>>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 
>>> 203.86.206.43
>>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 
>>> 103.242.70.4
>>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 
>>> 185.242.56.3
>>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 
>>> 103.242.68.69
>>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 
>>> 130.217.226.49
>>> Jan 28 21:44:56 raspberrypi ntpd[484]: Soliciting pool server 
>>> 122.252.188.99
>>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 
>>> 202.78.240.38
>>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 
>>> 202.46.179.18
>>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 
>>> 2407:f100:0:1::2
>>> Jan 28 21:44:58 raspberrypi ntpd[484]: Soliciting pool server 
>>> 130.217.226.51
>>> Jan 28 21:45:08 raspberrypi systemd[589]: Time has been changed
>>> Jan 28 21:45:08 raspberrypi systemd[1]: Time has been changed
>>> Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily.timer: Adding 10h 7min 
>>> 19.972590s random time.
>>> Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
>>> 37min 57.400920s random time.
>>> Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin 
>>> timestamp 0xdff93f8c.e12c4d6d does not match aorg 00. from 
>>> ser...@203.159.70.33 xmt 0xdff93f94.5a13b23a
>>> Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin 
>>> timestamp 0xdff93f8c.e1319bed does not match aorg 00. from 
>>> ser...@37.187.18.4 xmt 0xdff93f94.62dbcbad
>>> Jan 28 21:47:56 raspberrypi kernel: [  251.674064] Under-voltage 
>>> detected! (0x00050005)
>>> Jan 28 21:48:02 raspberrypi kernel: [  257.914050] Voltage normalised 
>>> (0x)
>>>
>>>
>>> On Saturday, 26 January 2019 15:12:12 UTC+13, monmul wrote:

 Not a problem, you pointed me in the right direction which was all I 
 needed..thanks again!

 On Saturday, 26 January 2019 15:09:22 UTC+13, gjr80 wrote:
>
> My apologies if I lead you astray, I did mentioning dumping but did 
> not list the command. Was out at the time and on the mobile.
>
> Gary
>
 -- 
>> You received this message because you are subscribed 

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

[dunbrokin]

I am using a powered hub and I am using the official RPi power source.

On Mon, Jan 28, 2019 at 10:05 PM Andrew Milner 
wrote:

> I would suggest you work on eliminating the under voltage errors before
> trying to work out why you cannot communicate with the weather station.
> The implication is that the RPi is having trouble coping with whatever you
> have got connected via usb and/or network.  This is not unusual and
> indicates you may need either a larger power supply or a powered usb hub to
> cope with your usb loads.
>
>
>
> On Monday, 28 January 2019 10:52:28 UTC+2, monmul wrote:
>>
>> My Pi stopped reporting at 19.20 today and despite rebooting twice, it
>> does not seem to be able to wake up the console..is there a way/log I
>> can query to find out why it might have stopped at 19.10it was working
>> fine for 2 or 3 days. Here is the syslog...
>>
>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>> Jan 28 21:43:57 raspberrypi dhcpcd[350]: wlan0: no IPv6 Routers available
>> Jan 28 21:44:02 raspberrypi weewx[510]: vantage: Unable to wake up console
>> Jan 28 21:44:02 raspberrypi weewx[510]: import of driver failed: Unable
>> to wake up Vantage console ()
>> Jan 28 21:44:02 raspberrypi weewx[510]: engine: Unable to load driver:
>> Unable to wake up Vantage console
>> Jan 28 21:44:02 raspberrypi weewx[510]:   Exiting...
>> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections:
>> connected: 10.1.1.155::40108 (TCP)
>> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections:
>> authenticated: 10.1.1.155::40108 (TCP), as (anonymous) (d permissions)
>> Jan 28 21:44:04 raspberrypi vncserver-x11[461,root]: SPrintConnMgr:
>> Failed to add printer: server-error-service-unavailable
>> Jan 28 21:44:04 raspberrypi kernel: [   27.031827] Under-voltage
>> detected! (0x00050005)
>> Jan 28 21:44:10 raspberrypi kernel: [   33.271789] Voltage normalised
>> (0x)
>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server
>> 88.191.250.97
>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 37.187.18.4
>> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server
>> 103.106.66.123
>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server
>> 103.106.65.219
>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server
>> 203.159.70.33
>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.5
>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server
>> 203.86.206.43
>> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.4
>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 185.242.56.3
>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server
>> 103.242.68.69
>> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server
>> 130.217.226.49
>> Jan 28 21:44:56 raspberrypi ntpd[484]: Soliciting pool server
>> 122.252.188.99
>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server
>> 202.78.240.38
>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server
>> 202.46.179.18
>> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server
>> 2407:f100:0:1::2
>> Jan 28 21:44:58 raspberrypi ntpd[484]: Soliciting pool server
>> 130.217.226.51
>> Jan 28 21:45:08 raspberrypi systemd[589]: Time has been changed
>> Jan 28 21:45:08 raspberrypi systemd[1]: Time has been changed
>> Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily.timer: Adding 10h 7min
>> 19.972590s random time.
>> Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding
>> 37min 57.400920s random time.
>> Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin
>> timestamp 0xdff93f8c.e12c4d6d does not match aorg 00. from
>> ser...@203.159.70.33 xmt 0xdff93f94.5a13b23a
>> Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin
>> timestamp 0xdff93f8c.e1319bed does not match aorg 00. from
>> ser...@37.187.18.4 xmt 0xdff93f94.62dbcbad
>> Jan 28 21:47:56 raspberrypi kernel: [  251.674064] Under-voltage
>> detected! (0x00050005)
>> Jan 28 21:48:02 raspberrypi kernel: [  257.914050] Voltage normalised
>> (0x)
>>
>>
>> On Saturday, 26 January 2019 15:12:12 UTC+13, monmul wrote:
>>>
>>> Not a problem, you pointed me in the right direction which was all I
>>> needed..thanks again!
>>>
>>> On Saturday, 26 January 2019 15:09:22 UTC+13, gjr80 wrote:

 My apologies if I lead you astray, I did mentioning dumping but did not
 list the command. Was out at the time and on the mobile.

 Gary

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

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving 

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

[Andrew Milner]

I would suggest you work on eliminating the under voltage errors before 
trying to work out why you cannot communicate with the weather station.  
The implication is that the RPi is having trouble coping with whatever you 
have got connected via usb and/or network.  This is not unusual and 
indicates you may need either a larger power supply or a powered usb hub to 
cope with your usb loads.



On Monday, 28 January 2019 10:52:28 UTC+2, monmul wrote:
>
> My Pi stopped reporting at 19.20 today and despite rebooting twice, it 
> does not seem to be able to wake up the console..is there a way/log I 
> can query to find out why it might have stopped at 19.10it was working 
> fine for 2 or 3 days. Here is the syslog...
>
> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
> Jan 28 21:43:57 raspberrypi dhcpcd[350]: wlan0: no IPv6 Routers available
> Jan 28 21:44:02 raspberrypi weewx[510]: vantage: Unable to wake up console
> Jan 28 21:44:02 raspberrypi weewx[510]: import of driver failed: Unable to 
> wake up Vantage console ()
> Jan 28 21:44:02 raspberrypi weewx[510]: engine: Unable to load driver: 
> Unable to wake up Vantage console
> Jan 28 21:44:02 raspberrypi weewx[510]:   Exiting...
> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: 
> connected: 10.1.1.155::40108 (TCP)
> Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: 
> authenticated: 10.1.1.155::40108 (TCP), as (anonymous) (d permissions)
> Jan 28 21:44:04 raspberrypi vncserver-x11[461,root]: SPrintConnMgr: Failed 
> to add printer: server-error-service-unavailable
> Jan 28 21:44:04 raspberrypi kernel: [   27.031827] Under-voltage detected! 
> (0x00050005)
> Jan 28 21:44:10 raspberrypi kernel: [   33.271789] Voltage normalised 
> (0x)
> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 88.191.250.97
> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 37.187.18.4
> Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 
> 103.106.66.123
> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 
> 103.106.65.219
> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 203.159.70.33
> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.5
> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 203.86.206.43
> Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.4
> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 185.242.56.3
> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 103.242.68.69
> Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 
> 130.217.226.49
> Jan 28 21:44:56 raspberrypi ntpd[484]: Soliciting pool server 
> 122.252.188.99
> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 202.78.240.38
> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 202.46.179.18
> Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 
> 2407:f100:0:1::2
> Jan 28 21:44:58 raspberrypi ntpd[484]: Soliciting pool server 
> 130.217.226.51
> Jan 28 21:45:08 raspberrypi systemd[589]: Time has been changed
> Jan 28 21:45:08 raspberrypi systemd[1]: Time has been changed
> Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily.timer: Adding 10h 7min 
> 19.972590s random time.
> Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
> 37min 57.400920s random time.
> Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin 
> timestamp 0xdff93f8c.e12c4d6d does not match aorg 00. from 
> ser...@203.159.70.33  xmt 0xdff93f94.5a13b23a
> Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin 
> timestamp 0xdff93f8c.e1319bed does not match aorg 00. from 
> ser...@37.187.18.4  xmt 0xdff93f94.62dbcbad
> Jan 28 21:47:56 raspberrypi kernel: [  251.674064] Under-voltage detected! 
> (0x00050005)
> Jan 28 21:48:02 raspberrypi kernel: [  257.914050] Voltage normalised 
> (0x)
>
>
> On Saturday, 26 January 2019 15:12:12 UTC+13, monmul wrote:
>>
>> Not a problem, you pointed me in the right direction which was all I 
>> needed..thanks again!
>>
>> On Saturday, 26 January 2019 15:09:22 UTC+13, gjr80 wrote:
>>>
>>> My apologies if I lead you astray, I did mentioning dumping but did not 
>>> list the command. Was out at the time and on the mobile.
>>>
>>> Gary
>>>
>>

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

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

[monmul]

My Pi stopped reporting at 19.20 today and despite rebooting twice, it does 
not seem to be able to wake up the console..is there a way/log I can 
query to find out why it might have stopped at 19.10it was working fine 
for 2 or 3 days. Here is the syslog...

pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
Jan 28 21:43:57 raspberrypi dhcpcd[350]: wlan0: no IPv6 Routers available
Jan 28 21:44:02 raspberrypi weewx[510]: vantage: Unable to wake up console
Jan 28 21:44:02 raspberrypi weewx[510]: import of driver failed: Unable to 
wake up Vantage console ()
Jan 28 21:44:02 raspberrypi weewx[510]: engine: Unable to load driver: 
Unable to wake up Vantage console
Jan 28 21:44:02 raspberrypi weewx[510]:   Exiting...
Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: 
connected: 10.1.1.155::40108 (TCP)
Jan 28 21:44:03 raspberrypi vncserver-x11[461,root]: Connections: 
authenticated: 10.1.1.155::40108 (TCP), as (anonymous) (d permissions)
Jan 28 21:44:04 raspberrypi vncserver-x11[461,root]: SPrintConnMgr: Failed 
to add printer: server-error-service-unavailable
Jan 28 21:44:04 raspberrypi kernel: [   27.031827] Under-voltage detected! 
(0x00050005)
Jan 28 21:44:10 raspberrypi kernel: [   33.271789] Voltage normalised 
(0x)
Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 88.191.250.97
Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 37.187.18.4
Jan 28 21:44:53 raspberrypi ntpd[484]: Soliciting pool server 103.106.66.123
Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.106.65.219
Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 203.159.70.33
Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.5
Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 203.86.206.43
Jan 28 21:44:54 raspberrypi ntpd[484]: Soliciting pool server 103.242.70.4
Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 185.242.56.3
Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 103.242.68.69
Jan 28 21:44:55 raspberrypi ntpd[484]: Soliciting pool server 130.217.226.49
Jan 28 21:44:56 raspberrypi ntpd[484]: Soliciting pool server 122.252.188.99
Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 202.78.240.38
Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 202.46.179.18
Jan 28 21:44:57 raspberrypi ntpd[484]: Soliciting pool server 
2407:f100:0:1::2
Jan 28 21:44:58 raspberrypi ntpd[484]: Soliciting pool server 130.217.226.51
Jan 28 21:45:08 raspberrypi systemd[589]: Time has been changed
Jan 28 21:45:08 raspberrypi systemd[1]: Time has been changed
Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily.timer: Adding 10h 7min 
19.972590s random time.
Jan 28 21:45:08 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
37min 57.400920s random time.
Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin timestamp 
0xdff93f8c.e12c4d6d does not match aorg 00. from 
server@203.159.70.33 xmt 0xdff93f94.5a13b23a
Jan 28 21:45:08 raspberrypi ntpd[484]: receive: Unexpected origin timestamp 
0xdff93f8c.e1319bed does not match aorg 00. from 
server@37.187.18.4 xmt 0xdff93f94.62dbcbad
Jan 28 21:47:56 raspberrypi kernel: [  251.674064] Under-voltage detected! 
(0x00050005)
Jan 28 21:48:02 raspberrypi kernel: [  257.914050] Voltage normalised 
(0x)


On Saturday, 26 January 2019 15:12:12 UTC+13, monmul wrote:
>
> Not a problem, you pointed me in the right direction which was all I 
> needed..thanks again!
>
> On Saturday, 26 January 2019 15:09:22 UTC+13, gjr80 wrote:
>>
>> My apologies if I lead you astray, I did mentioning dumping but did not 
>> list the command. Was out at the time and on the mobile.
>>
>> Gary
>>
>

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

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

[monmul]

Not a problem, you pointed me in the right direction which was all I 
needed..thanks again!

On Saturday, 26 January 2019 15:09:22 UTC+13, gjr80 wrote:
>
> My apologies if I lead you astray, I did mentioning dumping but did not 
> list the command. Was out at the time and on the mobile.
>
> Gary
>

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

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

[monmul]

Thank you both for your help.I seem to be up and running now without 
any hitches apart from some lost data. Thanks again, I will know what to do 
now if happens again.

On Saturday, 26 January 2019 15:04:13 UTC+13, Thomas Keffer wrote:
>
> The Envoy acts exactly like the regular Vantage console.
>
> On Fri, Jan 25, 2019 at 5:58 PM gjr80 > 
> wrote:
>
>> Ok, so archive records are being saved and pages being generated with 
>> current data? The log in your previous post still showed an archive record 
>> being skipped at 13:20:00.
>>
>> Annoying to lose data but sometimes it happens, doing the dump before you 
>> do anything destructive dumps all of the archive records out of the logger 
>> and any that are not in your archive are saved to archive, any that are 
>> already in your archiv are ignored (well you get a duplicate key error). 
>> From my limited experience a dump tends to result in loss of maybe one or 
>> two records only unless something catastrophic has occurred. It seems that 
>> the archive record is still saved in the logger it just doesn't send it to 
>> WeeWX when weeWX asks for it. Having an envoy may be slightly different, I 
>> don't have one, Tom may be able to shed some more light on it.
>>
>> Not sure what you meant about deleting records. Did you mean your archive 
>> or the logger/envoy? As far as I know it's all or nothing in terms of 
>> clearing the logger/envoy. And you weren't getting any records into your 
>> archive.
>>
>> Gary
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

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

[gjr80]

My apologies if I lead you astray, I did mentioning dumping but did not list 
the command. Was out at the time and on the mobile.

Gary

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

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

[Thomas Keffer]

The Envoy acts exactly like the regular Vantage console.

On Fri, Jan 25, 2019 at 5:58 PM gjr80  wrote:

> Ok, so archive records are being saved and pages being generated with
> current data? The log in your previous post still showed an archive record
> being skipped at 13:20:00.
>
> Annoying to lose data but sometimes it happens, doing the dump before you
> do anything destructive dumps all of the archive records out of the logger
> and any that are not in your archive are saved to archive, any that are
> already in your archiv are ignored (well you get a duplicate key error).
> From my limited experience a dump tends to result in loss of maybe one or
> two records only unless something catastrophic has occurred. It seems that
> the archive record is still saved in the logger it just doesn't send it to
> WeeWX when weeWX asks for it. Having an envoy may be slightly different, I
> don't have one, Tom may be able to shed some more light on it.
>
> Not sure what you meant about deleting records. Did you mean your archive
> or the logger/envoy? As far as I know it's all or nothing in terms of
> clearing the logger/envoy. And you weren't getting any records into your
> archive.
>
> Gary
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

[Thomas Keffer]

Another option is to use the --dump

command. It will download *all* data in the logger. It results in a *lot* of
"duplicate primary key" errors, but will save your data.

Unfortunately, you can only use it before --clear-memory.

On Fri, Jan 25, 2019 at 4:54 PM monmul  wrote:

> OK, we are back up after wee-device --clear-memory. Lost 12 hours of data
> though.maybe should have tried deleting the records with time stamp
> older than X.
>
> On Saturday, 26 January 2019 13:42:56 UTC+13, monmul wrote:
>>
>> Another log after reboot.
>>
>> On Saturday, 26 January 2019 13:08:16 UTC+13, monmul wrote:
>>>
>>> Here is 5 minutes of the console logis that long enough? I can do
>>> much longer if required?
>>>
>>> On Saturday, 26 January 2019 12:26:06 UTC+13, monmul wrote:

 After removing batteries from Envoy console and unplugging itand
 then sudo reboot of Rpi this is what I get.

 pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
 Jan 26 12:14:45 raspberrypi dhcpcd[334]: wlan0: no IPv6 Routers
 available
 Jan 26 12:14:50 raspberrypi weewx[494]: vantage: Unable to wake up
 console
 Jan 26 12:14:50 raspberrypi weewx[494]: import of driver failed: Unable
 to wake up Vantage console ()
 Jan 26 12:14:50 raspberrypi weewx[494]: engine: Unable to load driver:
 Unable to wake up Vantage console
 Jan 26 12:14:50 raspberrypi weewx[494]:   Exiting...
 Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections:
 connected: 10.1.1.155::38928 (TCP)
 Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections:
 authenticated: 10.1.1.155::38928 (TCP), as (anonymous) (d permissions)
 Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: SPrintConnMgr:
 Failed to add printer: server-error-service-unavailable
 Jan 26 12:14:54 raspberrypi kernel: [   29.111831] Under-voltage
 detected! (0x00050005)
 Jan 26 12:15:01 raspberrypi kernel: [   35.351863] Voltage normalised
 (0x)
 Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server
 103.242.68.68
 Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server
 103.239.8.22
 Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server
 103.106.65.219
 Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server
 202.78.240.38
 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server
 103.242.68.69
 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server
 203.86.206.43
 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server
 202.46.185.18
 Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server
 202.46.177.18
 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server
 202.46.179.18
 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server
 203.99.128.34
 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server
 2407:f100:0:4::3
 Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server
 203.99.128.48
 Jan 26 12:15:43 raspberrypi ntpd[460]: Soliciting pool server
 130.217.226.51
 Jan 26 12:15:54 raspberrypi systemd[1]: Time has been changed
 Jan 26 12:15:54 raspberrypi systemd[573]: Time has been changed
 Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin
 timestamp 0xdff61722.e1bd49e9 does not match aorg 00. from
 server@103.239.8.22 xmt 0xdff6172a.80071bf6
 Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily.timer: Adding 3h
 41min 59.082661s random time.
 Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin
 timestamp 0xdff61722.e1af360e does not match aorg 00. from
 server@202.46.185.18 xmt 0xdff6172a.80d85adc
 Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding
 27min 28.579939s random time.
 Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin
 timestamp 0xdff61722.d7adc312 does not match aorg 00. from
 server@130.217.226.51 xmt 0xdff6172a.7d37a242
 Jan 26 12:17:01 raspberrypi CRON[1250]: (root) CMD (   cd / &&
 run-parts --report /etc/cron.hourly)

 Next should I try deleting future records as recommended in the
 "generated but not updated" section of the user guide.

 pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop
 [ ok ] Stopping weewx (via systemctl): weewx.service.
 pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
 pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
 pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
 Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Initializing weewx
 version 3.8.2
 Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using Python 2.7.13
 (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
 Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Platform
 

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

[gjr80]

Ok, so archive records are being saved and pages being generated with current 
data? The log in your previous post still showed an archive record being 
skipped at 13:20:00.

Annoying to lose data but sometimes it happens, doing the dump before you do 
anything destructive dumps all of the archive records out of the logger and any 
that are not in your archive are saved to archive, any that are already in your 
archiv are ignored (well you get a duplicate key error). From my limited 
experience a dump tends to result in loss of maybe one or two records only 
unless something catastrophic has occurred. It seems that the archive record is 
still saved in the logger it just doesn't send it to WeeWX when weeWX asks for 
it. Having an envoy may be slightly different, I don't have one, Tom may be 
able to shed some more light on it.

Not sure what you meant about deleting records. Did you mean your archive or 
the logger/envoy? As far as I know it's all or nothing in terms of clearing the 
logger/envoy. And you weren't getting any records into your archive.

Gary

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

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

[monmul]

OK, we are back up after wee-device --clear-memory. Lost 12 hours of data 
though.maybe should have tried deleting the records with time stamp 
older than X.

On Saturday, 26 January 2019 13:42:56 UTC+13, monmul wrote:
>
> Another log after reboot.
>
> On Saturday, 26 January 2019 13:08:16 UTC+13, monmul wrote:
>>
>> Here is 5 minutes of the console logis that long enough? I can do 
>> much longer if required?
>>
>> On Saturday, 26 January 2019 12:26:06 UTC+13, monmul wrote:
>>>
>>> After removing batteries from Envoy console and unplugging itand 
>>> then sudo reboot of Rpi this is what I get.
>>>
>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>>> Jan 26 12:14:45 raspberrypi dhcpcd[334]: wlan0: no IPv6 Routers available
>>> Jan 26 12:14:50 raspberrypi weewx[494]: vantage: Unable to wake up 
>>> console
>>> Jan 26 12:14:50 raspberrypi weewx[494]: import of driver failed: Unable 
>>> to wake up Vantage console ()
>>> Jan 26 12:14:50 raspberrypi weewx[494]: engine: Unable to load driver: 
>>> Unable to wake up Vantage console
>>> Jan 26 12:14:50 raspberrypi weewx[494]:   Exiting...
>>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: 
>>> connected: 10.1.1.155::38928 (TCP)
>>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: 
>>> authenticated: 10.1.1.155::38928 (TCP), as (anonymous) (d permissions)
>>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: SPrintConnMgr: 
>>> Failed to add printer: server-error-service-unavailable
>>> Jan 26 12:14:54 raspberrypi kernel: [   29.111831] Under-voltage 
>>> detected! (0x00050005)
>>> Jan 26 12:15:01 raspberrypi kernel: [   35.351863] Voltage normalised 
>>> (0x)
>>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 
>>> 103.242.68.68
>>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 
>>> 103.239.8.22
>>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 
>>> 103.106.65.219
>>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 
>>> 202.78.240.38
>>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 
>>> 103.242.68.69
>>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 
>>> 203.86.206.43
>>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 
>>> 202.46.185.18
>>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 
>>> 202.46.177.18
>>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 
>>> 202.46.179.18
>>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 
>>> 203.99.128.34
>>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 
>>> 2407:f100:0:4::3
>>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 
>>> 203.99.128.48
>>> Jan 26 12:15:43 raspberrypi ntpd[460]: Soliciting pool server 
>>> 130.217.226.51
>>> Jan 26 12:15:54 raspberrypi systemd[1]: Time has been changed
>>> Jan 26 12:15:54 raspberrypi systemd[573]: Time has been changed
>>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin 
>>> timestamp 0xdff61722.e1bd49e9 does not match aorg 00. from 
>>> server@103.239.8.22 xmt 0xdff6172a.80071bf6
>>> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily.timer: Adding 3h 41min 
>>> 59.082661s random time.
>>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin 
>>> timestamp 0xdff61722.e1af360e does not match aorg 00. from 
>>> server@202.46.185.18 xmt 0xdff6172a.80d85adc
>>> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
>>> 27min 28.579939s random time.
>>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin 
>>> timestamp 0xdff61722.d7adc312 does not match aorg 00. from 
>>> server@130.217.226.51 xmt 0xdff6172a.7d37a242
>>> Jan 26 12:17:01 raspberrypi CRON[1250]: (root) CMD (   cd / && run-parts 
>>> --report /etc/cron.hourly)
>>>
>>> Next should I try deleting future records as recommended in the 
>>> "generated but not updated" section of the user guide. 
>>>
>>> pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop
>>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>>> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
>>> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
>>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Initializing weewx 
>>> version 3.8.2
>>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using Python 2.7.13 
>>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Platform 
>>> Linux-4.14.79-v7+-armv7l-with-debian-9.6
>>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Locale is 'en_NZ.UTF-8'
>>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using configuration 
>>> file /etc/weewx/weewx.conf
>>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Loading station type 
>>> Vantage (weewx.drivers.vantage)
>>> Jan 26 12:25:05 raspberrypi weewx[1810]: vantage: Unable to wake up 
>>> console
>>> 

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

[monmul]

Another log after reboot.

On Saturday, 26 January 2019 13:08:16 UTC+13, monmul wrote:
>
> Here is 5 minutes of the console logis that long enough? I can do much 
> longer if required?
>
> On Saturday, 26 January 2019 12:26:06 UTC+13, monmul wrote:
>>
>> After removing batteries from Envoy console and unplugging itand then 
>> sudo reboot of Rpi this is what I get.
>>
>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>> Jan 26 12:14:45 raspberrypi dhcpcd[334]: wlan0: no IPv6 Routers available
>> Jan 26 12:14:50 raspberrypi weewx[494]: vantage: Unable to wake up console
>> Jan 26 12:14:50 raspberrypi weewx[494]: import of driver failed: Unable 
>> to wake up Vantage console ()
>> Jan 26 12:14:50 raspberrypi weewx[494]: engine: Unable to load driver: 
>> Unable to wake up Vantage console
>> Jan 26 12:14:50 raspberrypi weewx[494]:   Exiting...
>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: 
>> connected: 10.1.1.155::38928 (TCP)
>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: 
>> authenticated: 10.1.1.155::38928 (TCP), as (anonymous) (d permissions)
>> Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: SPrintConnMgr: 
>> Failed to add printer: server-error-service-unavailable
>> Jan 26 12:14:54 raspberrypi kernel: [   29.111831] Under-voltage 
>> detected! (0x00050005)
>> Jan 26 12:15:01 raspberrypi kernel: [   35.351863] Voltage normalised 
>> (0x)
>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 
>> 103.242.68.68
>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.239.8.22
>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 
>> 103.106.65.219
>> Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 
>> 202.78.240.38
>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 
>> 103.242.68.69
>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 
>> 203.86.206.43
>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 
>> 202.46.185.18
>> Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 
>> 202.46.177.18
>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 
>> 202.46.179.18
>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 
>> 203.99.128.34
>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 
>> 2407:f100:0:4::3
>> Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 
>> 203.99.128.48
>> Jan 26 12:15:43 raspberrypi ntpd[460]: Soliciting pool server 
>> 130.217.226.51
>> Jan 26 12:15:54 raspberrypi systemd[1]: Time has been changed
>> Jan 26 12:15:54 raspberrypi systemd[573]: Time has been changed
>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin 
>> timestamp 0xdff61722.e1bd49e9 does not match aorg 00. from 
>> server@103.239.8.22 xmt 0xdff6172a.80071bf6
>> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily.timer: Adding 3h 41min 
>> 59.082661s random time.
>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin 
>> timestamp 0xdff61722.e1af360e does not match aorg 00. from 
>> server@202.46.185.18 xmt 0xdff6172a.80d85adc
>> Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
>> 27min 28.579939s random time.
>> Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin 
>> timestamp 0xdff61722.d7adc312 does not match aorg 00. from 
>> server@130.217.226.51 xmt 0xdff6172a.7d37a242
>> Jan 26 12:17:01 raspberrypi CRON[1250]: (root) CMD (   cd / && run-parts 
>> --report /etc/cron.hourly)
>>
>> Next should I try deleting future records as recommended in the 
>> "generated but not updated" section of the user guide. 
>>
>> pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop
>> [ ok ] Stopping weewx (via systemctl): weewx.service.
>> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
>> pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
>> pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Initializing weewx 
>> version 3.8.2
>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using Python 2.7.13 
>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Platform 
>> Linux-4.14.79-v7+-armv7l-with-debian-9.6
>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Locale is 'en_NZ.UTF-8'
>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using configuration file 
>> /etc/weewx/weewx.conf
>> Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Loading station type 
>> Vantage (weewx.drivers.vantage)
>> Jan 26 12:25:05 raspberrypi weewx[1810]: vantage: Unable to wake up 
>> console
>> Jan 26 12:25:05 raspberrypi weewx[1810]: import of driver failed: Unable 
>> to wake up Vantage console ()
>> Jan 26 12:25:05 raspberrypi weewx[1810]: engine: Unable to load driver: 
>> Unable to wake up Vantage console
>> Jan 26 12:25:05 raspberrypi weewx[1810]:   Exiting...
>> Jan 26
>>
>>
>>
>> On Saturday, 26 January 

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

[gjr80]

Yep, no 13:00:00 archive record (REC: ) so all the symptoms of corrupt station 
memory. Not sure how different things are with an envoy. I would run through 
the 'Corrupt station memory' section of one of the links I gave you. Before 
doing anything destructive trying dumping the station memory (there is a link 
there in the Corrupt station memory section). This will help minimise any data 
loss when you reset the logger (in your case the envoy). Note weeWX must be 
stopped when you dump the memory.

Gary

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

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

[monmul]

After removing batteries from Envoy console and unplugging itand then 
sudo reboot of Rpi this is what I get.

pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
Jan 26 12:14:45 raspberrypi dhcpcd[334]: wlan0: no IPv6 Routers available
Jan 26 12:14:50 raspberrypi weewx[494]: vantage: Unable to wake up console
Jan 26 12:14:50 raspberrypi weewx[494]: import of driver failed: Unable to 
wake up Vantage console ()
Jan 26 12:14:50 raspberrypi weewx[494]: engine: Unable to load driver: 
Unable to wake up Vantage console
Jan 26 12:14:50 raspberrypi weewx[494]:   Exiting...
Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: 
connected: 10.1.1.155::38928 (TCP)
Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: Connections: 
authenticated: 10.1.1.155::38928 (TCP), as (anonymous) (d permissions)
Jan 26 12:14:53 raspberrypi vncserver-x11[440,root]: SPrintConnMgr: Failed 
to add printer: server-error-service-unavailable
Jan 26 12:14:54 raspberrypi kernel: [   29.111831] Under-voltage detected! 
(0x00050005)
Jan 26 12:15:01 raspberrypi kernel: [   35.351863] Voltage normalised 
(0x)
Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.242.68.68
Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.239.8.22
Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 103.106.65.219
Jan 26 12:15:40 raspberrypi ntpd[460]: Soliciting pool server 202.78.240.38
Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 103.242.68.69
Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 203.86.206.43
Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 202.46.185.18
Jan 26 12:15:41 raspberrypi ntpd[460]: Soliciting pool server 202.46.177.18
Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 202.46.179.18
Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 203.99.128.34
Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 
2407:f100:0:4::3
Jan 26 12:15:42 raspberrypi ntpd[460]: Soliciting pool server 203.99.128.48
Jan 26 12:15:43 raspberrypi ntpd[460]: Soliciting pool server 130.217.226.51
Jan 26 12:15:54 raspberrypi systemd[1]: Time has been changed
Jan 26 12:15:54 raspberrypi systemd[573]: Time has been changed
Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 
0xdff61722.e1bd49e9 does not match aorg 00. from 
server@103.239.8.22 xmt 0xdff6172a.80071bf6
Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily.timer: Adding 3h 41min 
59.082661s random time.
Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 
0xdff61722.e1af360e does not match aorg 00. from 
server@202.46.185.18 xmt 0xdff6172a.80d85adc
Jan 26 12:15:54 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 
27min 28.579939s random time.
Jan 26 12:15:54 raspberrypi ntpd[460]: receive: Unexpected origin timestamp 
0xdff61722.d7adc312 does not match aorg 00. from 
server@130.217.226.51 xmt 0xdff6172a.7d37a242
Jan 26 12:17:01 raspberrypi CRON[1250]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)

Next should I try deleting future records as recommended in the "generated 
but not updated" section of the user guide. 

pi@raspberrypi:~ $ sudo /etc/init.d/weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.
pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
pi@raspberrypi:~ $ sudo tail -f /var/log/syslog
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Initializing weewx version 
3.8.2
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using Python 2.7.13 
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Platform 
Linux-4.14.79-v7+-armv7l-with-debian-9.6
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Locale is 'en_NZ.UTF-8'
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Using configuration file 
/etc/weewx/weewx.conf
Jan 26 12:24:49 raspberrypi weewx[1810]: engine: Loading station type 
Vantage (weewx.drivers.vantage)
Jan 26 12:25:05 raspberrypi weewx[1810]: vantage: Unable to wake up console
Jan 26 12:25:05 raspberrypi weewx[1810]: import of driver failed: Unable to 
wake up Vantage console ()
Jan 26 12:25:05 raspberrypi weewx[1810]: engine: Unable to load driver: 
Unable to wake up Vantage console
Jan 26 12:25:05 raspberrypi weewx[1810]:   Exiting...
Jan 26



On Saturday, 26 January 2019 11:51:41 UTC+13, gjr80 wrote:
>
> Yes, you appear to be getting loop packets. Corrupt station memory usually 
> results in loop packets continuing to come through but there are no archive 
> records coming from the logger. If you are using hardware record generation 
> then WeeWX gets no archive records, nothing is saved to database but 
> reports are still generated and anything 'loop based' still goes on. The 
> proof will be a longer console output (are there any archive records?) or a 
> longer log extract.
>
> If corrupt station 

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

[gjr80]

Yes, you appear to be getting loop packets. Corrupt station memory usually 
results in loop packets continuing to come through but there are no archive 
records coming from the logger. If you are using hardware record generation 
then WeeWX gets no archive records, nothing is saved to database but reports 
are still generated and anything 'loop based' still goes on. The proof will be 
a longer console output (are there any archive records?) or a longer log 
extract.

If corrupt station memory it will be unrelated to any perceived RPi power 
issues.

Gary

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

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

[monmul]

5,1V 2.5A - the official RPi power unit!

On Saturday, 26 January 2019 11:42:00 UTC+13, Dave Webb wrote:
>
> What size power supply are using? Try at least a 2amp unit. 
>
> Dave-KB1PVH
>
>
> Sent from my Galaxy S9
>
> On Fri, Jan 25, 2019, 5:22 PM monmul  
> wrote:
>
>> I seem to be getting a lot of these voltage issuesI am using the Rpi 
>> official power pack!!
>> Jan 26 11:15:00 raspberrypi systemd[1]: Starting Cleanup of Temporary 
>> Directories...
>> Jan 26 11:15:00 raspberrypi systemd[1]: Started Cleanup of Temporary 
>> Directories.
>> Jan 26 11:16:16 raspberrypi kernel: [ 1004.644829] 
>> rpi_firmware_get_throttled: 6 callbacks suppressed
>> Jan 26 11:16:16 raspberrypi kernel: [ 1004.644836] Under-voltage 
>> detected! (0x00050005)
>> Jan 26 11:16:20 raspberrypi kernel: [ 1008.804876] 
>> rpi_firmware_get_throttled: 6 callbacks suppressed
>> Jan 26 11:16:20 raspberrypi kernel: [ 1008.804883] Voltage normalised 
>> (0x)
>> Jan 26 11:17:01 raspberrypi CRON[1883]: (root) CMD (   cd / && run-parts 
>> --report /etc/cron.hourly)
>> Jan 26 11:17:03 raspberrypi kernel: [ 1052.485382] Under-voltage 
>> detected! (0x00050005)
>> Jan 26 11:17:08 raspberrypi kernel: [ 1056.645441] Voltage normalised 
>> (0x)
>> Jan 26 11:18:29 raspberrypi kernel: [ 1137.766503] Under-voltage 
>> detected! (0x00050005)
>> Jan 26 11:18:35 raspberrypi kernel: [ 1144.006449] Voltage normalised 
>> (0x)
>>
>>
>>
>> On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>>>
>>> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis 
>>> Vantage weather station. I have a serial Envoy data logger attaced to my 
>>> Rpi with a serial/usb converter. In following the set up instructions, I 
>>> get these errors!
>>>
>>> sudo weewxd weewx.conf
>>> Traceback (most recent call last):
>>>   File "/usr/bin/weewxd", line 64, in 
>>> weewx.engine.main(options, args)
>>>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
>>> sane = os.stat(config_path).st_ctime
>>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
>>> pi@Weatherpi:~ $ tail -f /var/log/syslog
>>> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered: 
>>> sender=:1.16 path=/MediaEndpoint/A2DPSink
>>> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
>>> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
>>> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
>>> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
>>> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>>> next retry is Sun Jan  6 13:41:35 2019 [try 
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx 
>>> version 3.8.2
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9 
>>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform 
>>> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>>> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary 
>>> Directories...
>>> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>>> next retry is Sun Jan  6 13:53:04 2019 [try 
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary 
>>> Directories.
>>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group 
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended, 
>>> next retry is Sun Jan  6 13:55:58 2019 [try 
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group 
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>>
>>> Please where have I gone wrong?
>>>
>>>
>>> .
>>>
>>> Hi,
>>>
>>> It appears that you are in the /home/pi directory and hence weewxd is 
>>> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>>>
>>> $ sudo weewxd /etc/weewx/weewx.conf
>>>
>>> Gary
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

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

[Dave Webb KB1PVH]

What size power supply are using? Try at least a 2amp unit.

Dave-KB1PVH


Sent from my Galaxy S9

On Fri, Jan 25, 2019, 5:22 PM monmul  I seem to be getting a lot of these voltage issuesI am using the Rpi
> official power pack!!
> Jan 26 11:15:00 raspberrypi systemd[1]: Starting Cleanup of Temporary
> Directories...
> Jan 26 11:15:00 raspberrypi systemd[1]: Started Cleanup of Temporary
> Directories.
> Jan 26 11:16:16 raspberrypi kernel: [ 1004.644829]
> rpi_firmware_get_throttled: 6 callbacks suppressed
> Jan 26 11:16:16 raspberrypi kernel: [ 1004.644836] Under-voltage detected!
> (0x00050005)
> Jan 26 11:16:20 raspberrypi kernel: [ 1008.804876]
> rpi_firmware_get_throttled: 6 callbacks suppressed
> Jan 26 11:16:20 raspberrypi kernel: [ 1008.804883] Voltage normalised
> (0x)
> Jan 26 11:17:01 raspberrypi CRON[1883]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Jan 26 11:17:03 raspberrypi kernel: [ 1052.485382] Under-voltage detected!
> (0x00050005)
> Jan 26 11:17:08 raspberrypi kernel: [ 1056.645441] Voltage normalised
> (0x)
> Jan 26 11:18:29 raspberrypi kernel: [ 1137.766503] Under-voltage detected!
> (0x00050005)
> Jan 26 11:18:35 raspberrypi kernel: [ 1144.006449] Voltage normalised
> (0x)
>
>
>
> On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>>
>> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis
>> Vantage weather station. I have a serial Envoy data logger attaced to my
>> Rpi with a serial/usb converter. In following the set up instructions, I
>> get these errors!
>>
>> sudo weewxd weewx.conf
>> Traceback (most recent call last):
>>   File "/usr/bin/weewxd", line 64, in 
>> weewx.engine.main(options, args)
>>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
>> sane = os.stat(config_path).st_ctime
>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
>> pi@Weatherpi:~ $ tail -f /var/log/syslog
>> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered:
>> sender=:1.16 path=/MediaEndpoint/A2DPSink
>> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
>> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
>> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
>> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
>> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Sun Jan  6 13:41:35 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx version
>> 3.8.2
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9
>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform
>> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary
>> Directories...
>> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Sun Jan  6 13:53:04 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary
>> Directories.
>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying
>> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Sun Jan  6 13:55:58 2019 [try http://www.rsyslog.com/e/2007
>>  ]
>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group rekeying
>> completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>
>> Please where have I gone wrong?
>>
>>
>> .
>>
>> Hi,
>>
>> It appears that you are in the /home/pi directory and hence weewxd is
>> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>>
>> $ sudo weewxd /etc/weewx/weewx.conf
>>
>> Gary
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

[monmul]

pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf
LOOP:   2019-01-26 11:35:35 NZDT (1548455735) appTemp: 61.9209615592, 
barometer: 29.7, cloudbase: 4921.41993274, consBatteryVoltage: 3.02, 
dateTime: 1548455735, dayET: 0.0, dayRain: 0.031496063, dewpoint: 
47.665752296, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 
0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, 
forecastIcon: 3, forecastRule: 163, heatindex: 64.7, humidex: 
65.9643612986, inDewpoint: 47.0050615695, inHumidity: 43.0, insideAlarm: 0, 
inTemp: 70.6, leafWet4: 0.0, maxSolarRad: None, monthET: 0.0, monthRain: 
2.6929133865, outHumidity: 54.0, outsideAlarm1: 0, outsideAlarm2: 0, 
outTemp: 64.7, rain: None, rainAlarm: 0, rainRate: 0.0, soilLeafAlarm1: 0, 
soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 
0.031496063, stormStart: 1548414000, sunrise: 1548432420, sunset: 
1548485400, trendIcon: -60, txBatteryStatus: 0, usUnits: 1, windchill: 
64.7, windDir: 139.0, windGust: 4.0, windGustDir: 139.0, windSpeed: 4.0, 
windSpeed10: 2.0, yearET: 0.0, yearRain: 35.4724409537
LOOP:   2019-01-26 11:

Well that appears to be working!

On Saturday, 26 January 2019 11:24:16 UTC+13, gjr80 wrote:
>
> You can run WeeWX directly (
> http://weewx.com/docs/usersguide.htm#Running_directly) to see loop and 
> archive data on screen. The other thing to do is look at the logs over at 
> least a few archive periods, you will likely see reports being run but no 
> data being saved to archive. Quite possibly you have corrupt station 
> memory, especially if you have had a mains power outage, have a read 
> through this 
> http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated
>
> Gary
>

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

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

[gjr80]

One bit of advice re logs; small extracts (a few lines) often give the error 
message but not much else, but it is a longer extract, say over a couple of 
archive periods that give a clue as to the cause of the error.

Gary

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

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

[gjr80]

You can run WeeWX directly 
(http://weewx.com/docs/usersguide.htm#Running_directly) to see loop and archive 
data on screen. The other thing to do is look at the logs over at least a few 
archive periods, you will likely see reports being run but no data being saved 
to archive. Quite possibly you have corrupt station memory, especially if you 
have had a mains power outage, have a read through this 
http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated

Gary

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

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

[monmul]

Is there a way to see whether the data is getting through from the Vantage 
to weewx, my Rpi has not undated the skins or WU since last night. I have 
tested all connectionsthere seems to be ftp happeningbut nothing 
gets updated!!

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

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

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

[monmul]

Jan 26 11:07:46 raspberrypi kernel: [  495.038468] Voltage normalised 
(0x)
Jan 26 11:07:48 raspberrypi kernel: [  497.118527] Under-voltage detected! 
(0x00050005)
Jan 26 11:08:15 raspberrypi kernel: [  524.158906] Voltage normalised 
(0x)
Jan 26 11:10:31 raspberrypi ntpd[461]: 202.78.240.38 local addr 10.1.1.7 -> 

Jan 26 11:10:33 raspberrypi weewx[501]: cheetahgenerator: Generated 15 
files for report StandardReport in 11.88 seconds
Jan 26 11:10:35 raspberrypi weewx[501]: imagegenerator: Generated 12 images 
for StandardReport in 1.65 seconds
Jan 26 11:10:35 raspberrypi weewx[501]: copygenerator: copied 9 files to 
/var/www/html/weewx
Jan 26 11:10:35 raspberrypi weewx[501]: cheetahgenerator: Generated 1 files 
for report xstats in 0.17 seconds
Jan 26 11:10:42 raspberrypi weewx[501]: ftpgenerator: ftp'd 37 files in 
6.99 seconds


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

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

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

[dunbrokin]

Thank you for that!

On Wed, Jan 23, 2019 at 1:38 AM Andrew Milner 
wrote:

> there are 'official' readings at LOOP intervals as well as REC (archive)
> intervals.
>
> You have the option in weewx.conf [StdArchive] section of saying whether
> to use loop value for max reading or archive value.  If you specify loop
> then $day.windGust.maxtime should correspond to the LOOP time of the high
> gust of the day.
>
>
>
> On Tuesday, 22 January 2019 11:54:55 UTC+2, monmul wrote:
>>
>> It would appear (from comparing the data to the gust speed actually
>> occurring) that, despite the wind speed recorder operating on a real time
>> basis, the record of the gust speed is the speed when the set reading
>> interval occurs rather than the max speed during the time  between
>> "official" readings. Is this the case? Is there a way I can get the live
>> gust speed?
>>
>> On Sunday, 6 January 2019 14:37:27 UTC+13, monmul wrote:
>>>
>>> I am new to weewx and am trying to set it up on my Rpi 3. I have a Davis
>>> Vantage weather station. I have a serial Envoy data logger attaced to my
>>> Rpi with a serial/usb converter. In following the set up instructions, I
>>> get these errors!
>>>
>>> sudo weewxd weewx.conf
>>> Traceback (most recent call last):
>>>   File "/usr/bin/weewxd", line 64, in 
>>> weewx.engine.main(options, args)
>>>   File "/usr/share/weewx/weewx/engine.py", line 835, in main
>>> sane = os.stat(config_path).st_ctime
>>> OSError: [Errno 2] No such file or directory: '/home/pi/weewx.conf'
>>> pi@Weatherpi:~ $ tail -f /var/log/syslog
>>> Jan  6 13:37:43 Weatherpi bluetoothd[843]: Endpoint unregistered:
>>> sender=:1.16 path=/MediaEndpoint/A2DPSink
>>> Jan  6 13:37:47 Weatherpi dhcpcd[498]: wlan0: no IPv6 Routers available
>>> Jan  6 13:37:48 Weatherpi dhcpcd[498]: eth0: no IPv6 Routers available
>>> Jan  6 13:37:57 Weatherpi systemd[852]: Time has been changed
>>> Jan  6 13:37:57 Weatherpi systemd[1]: Time has been changed
>>> Jan  6 13:41:05 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan  6 13:41:35 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Initializing weewx
>>> version 3.8.2
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Using Python 2.7.9
>>> (default, Sep 26 2018, 05:58:52) #012[GCC 4.9.2]
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Platform
>>> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>>> Jan  6 13:41:06 Weatherpi weewx[1515]: engine: Locale is 'en_GB.UTF-8'
>>> Jan  6 13:52:34 Weatherpi systemd[1]: Starting Cleanup of Temporary
>>> Directories...
>>> Jan  6 13:52:34 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan  6 13:53:04 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:52:35 Weatherpi systemd[1]: Started Cleanup of Temporary
>>> Directories.
>>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>> Jan  6 13:55:28 Weatherpi rsyslogd-2007: action 'action 17' suspended,
>>> next retry is Sun Jan  6 13:55:58 2019 [try
>>> http://www.rsyslog.com/e/2007 ]
>>> Jan  6 13:55:28 Weatherpi wpa_supplicant[590]: wlan0: WPA: Group
>>> rekeying completed with 30:5a:3a:cd:e7:f0 [GTK=CCMP]
>>>
>>> Please where have I gone wrong?
>>>
>>>
>>> .
>>>
>>> Hi,
>>>
>>> It appears that you are in the /home/pi directory and hence weewxd is
>>> looking for weewx.conf in /home/pi. Use the full path for weewx.conf ie:
>>>
>>> $ sudo weewxd /etc/weewx/weewx.conf
>>>
>>> Gary
>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

[Andrew Milner]

there are 'official' readings at LOOP intervals as well as REC (archive) 
intervals.

You have the option in weewx.conf [StdArchive] section of saying whether to 
use loop value for max reading or archive value.  If you specify loop then 
$day.windGust.maxtime should correspond to the LOOP time of the high gust 
of the day.



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

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

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

[monmul]

It would appear (from comparing the data to the gust speed actually 
occurring) that, despite the wind speed recorder operating on a real time 
basis, the record of the gust speed is the speed when the set reading 
interval occurs rather than the max speed during the time  between 
"official" readings. Is this the case? Is there a way I can get the live 
gust speed?

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

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

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

[monmul]

AwesomeI thought that weeimport could only deal with csv files and so 
went and converted them allbut kept the txt files for backup!

On Thursday, 17 January 2019 22:35:30 UTC+13, gjr80 wrote:
>
> Ok, that explains the csv file you provided having a different name 
> structure to what I had found. I believe that there was/is the ability for 
> WD to publish csv format log files and that is what I have. Weeimport will 
> happily work with the MMlg.txt files just as they are. No need to dig 
> anything out of an old machine. You will be the 1st so it will work with 
> your logs and I guess we see where it goes from there. Weeimport is fairly 
> flexible in structure and can easily be adapted.
>
> Gary
>

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

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

[gjr80]

Ok, that explains the csv file you provided having a different name structure 
to what I had found. I believe that there was/is the ability for WD to publish 
csv format log files and that is what I have. Weeimport will happily work with 
the MMlg.txt files just as they are. No need to dig anything out of an old 
machine. You will be the 1st so it will work with your logs and I guess we see 
where it goes from there. Weeimport is fairly flexible in structure and can 
easily be adapted.

Gary

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

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

[gjr80]

Thanks, I have mainly been working with some .txt log files I found.

One thing you could help me with is the WD log file names. I have 
MMlg.txt, MMvantagelog.txt and MMvantageextrasensorlog.csv. I 
also have MMlgcsv.csv and MMvantagelogcsv.csv. MM is a 1 or 2 digit 
month and  a 4 digit year. Are these the standard WD log files, the csv 
you provided follows a different naming convention?

MMlg.txt and MMlgcsv.csv are near identical except for format (txt 
delimited v csv) and .txt contains the midnight at the start of the month 
record but .csv does not (odd). Likewise with MMvantagelog.txt and 
MMvantagelogcsv.csv but this time .txt has the record from midnight at 
the end of the month but .csv does not (just as odd). Is this common to 
your logs?

Gary

On Thursday, 17 January 2019 13:45:24 UTC+10, monmul wrote:
>
> Actually Gary, I now realise that there was a formatting error in the 
> example csv file I gave you earlier - profuse apologies for not checking it 
> properly. Here is a properly formatted one!
>
> On Wednesday, 16 January 2019 21:48:07 UTC+13, monmul wrote:
>>
>> Wow! cool thanks!
>>
>> On Wed, Jan 16, 2019 at 9:17 PM gjr80 > 
>> wrote:
>>
>>> wee_import will import it all month by month. You just drop all your 
>>> log files into a single directory and wee_import works through the lot.
>>>
>>> Gary
>>>
>>> On Wednesday, 16 January 2019 18:12:48 UTC+10, monmul wrote:

 Great thank you so much!should I import month by month...or 
 transfer all the monthly data to one big file (probably 100 months in 
 total) and import it in one big hit?

 On Wed, Jan 16, 2019 at 8:47 PM gjr80  wrote:

> Good. I have a first cut of a wee_import that supports importing 
> Weather Display logs sort of working. Should not be too long, just needs 
> a 
> bit more work to sort out a few minor issues.
>
> Gary
>
> On Wednesday, 16 January 2019 17:44:03 UTC+10, monmul wrote:
>>
>> I changed it in skin.conf and everything is working fine now (well it 
>> will require a minor tweak or two :) )..thank you once again Gary 
>> for 
>> your patience and commitment...I have only one more part of the 
>> project 
>> to complete, if you could please guide me on how to import the 
>> historical 
>> data
>>
>> -- 
> You received this message because you are subscribed to the Google 
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to weewx-user+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

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

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

[dunbrokin]

Wow! cool thanks!

On Wed, Jan 16, 2019 at 9:17 PM gjr80  wrote:

> wee_import will import it all month by month. You just drop all your log
> files into a single directory and wee_import works through the lot.
>
> Gary
>
> On Wednesday, 16 January 2019 18:12:48 UTC+10, monmul wrote:
>>
>> Great thank you so much!should I import month by month...or transfer
>> all the monthly data to one big file (probably 100 months in total) and
>> import it in one big hit?
>>
>> On Wed, Jan 16, 2019 at 8:47 PM gjr80  wrote:
>>
>>> Good. I have a first cut of a wee_import that supports importing
>>> Weather Display logs sort of working. Should not be too long, just needs a
>>> bit more work to sort out a few minor issues.
>>>
>>> Gary
>>>
>>> On Wednesday, 16 January 2019 17:44:03 UTC+10, monmul wrote:

 I changed it in skin.conf and everything is working fine now (well it
 will require a minor tweak or two :) )..thank you once again Gary for
 your patience and commitment...I have only one more part of the project
 to complete, if you could please guide me on how to import the historical
 data

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

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

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

[gjr80]

wee_import will import it all month by month. You just drop all your log 
files into a single directory and wee_import works through the lot.

Gary

On Wednesday, 16 January 2019 18:12:48 UTC+10, monmul wrote:
>
> Great thank you so much!should I import month by month...or transfer 
> all the monthly data to one big file (probably 100 months in total) and 
> import it in one big hit?
>
> On Wed, Jan 16, 2019 at 8:47 PM gjr80 > 
> wrote:
>
>> Good. I have a first cut of a wee_import that supports importing Weather 
>> Display logs sort of working. Should not be too long, just needs a bit more 
>> work to sort out a few minor issues.
>>
>> Gary
>>
>> On Wednesday, 16 January 2019 17:44:03 UTC+10, monmul wrote:
>>>
>>> I changed it in skin.conf and everything is working fine now (well it 
>>> will require a minor tweak or two :) )..thank you once again Gary for 
>>> your patience and commitment...I have only one more part of the project 
>>> to complete, if you could please guide me on how to import the historical 
>>> data
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

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

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

[dunbrokin]

Great thank you so much!should I import month by month...or transfer
all the monthly data to one big file (probably 100 months in total) and
import it in one big hit?

On Wed, Jan 16, 2019 at 8:47 PM gjr80  wrote:

> Good. I have a first cut of a wee_import that supports importing Weather
> Display logs sort of working. Should not be too long, just needs a bit more
> work to sort out a few minor issues.
>
> Gary
>
> On Wednesday, 16 January 2019 17:44:03 UTC+10, monmul wrote:
>>
>> I changed it in skin.conf and everything is working fine now (well it
>> will require a minor tweak or two :) )..thank you once again Gary for
>> your patience and commitment...I have only one more part of the project
>> to complete, if you could please guide me on how to import the historical
>> data
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

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

[gjr80]

Good. I have a first cut of a wee_import that supports importing Weather 
Display logs sort of working. Should not be too long, just needs a bit more 
work to sort out a few minor issues.

Gary

On Wednesday, 16 January 2019 17:44:03 UTC+10, monmul wrote:
>
> I changed it in skin.conf and everything is working fine now (well it will 
> require a minor tweak or two :) )..thank you once again Gary for your 
> patience and commitment...I have only one more part of the project to 
> complete, if you could please guide me on how to import the historical 
> data
>
>

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

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

[monmul]

I changed it in skin.conf and everything is working fine now (well it will 
require a minor tweak or two :) )..thank you once again Gary for your 
patience and commitment...I have only one more part of the project to 
complete, if you could please guide me on how to import the historical 
data

On Wednesday, 16 January 2019 20:35:42 UTC+13, monmul wrote:
>
> H.I thought the error was in skin.confbut you think it might 
> be in weewx.conf.
>
> On Wed, Jan 16, 2019 at 8:04 PM gjr80  wrote:
>
>> Jan 16 19:17:34 raspberrypi weewx[530]: reportengine: Failed to read skin 
>>> configuration file /etc/weewx/skins/Standard/skin.conf for report 
>>> StandardReport: Duplicate keyword name at line 229.
>>
>>
>> And there is your clue... Have a look at line 229 (or thereabout) in 
>> weewx.conf, you have a duplicate config option name. Hard to say what it 
>> is without seeing weewx.conf. Under any given set of [] (or [[]], [[[]]] 
>> etc) each config option name must be unique, eg you cannot define template 
>> = twice under [[[year]]]. Similarly each child [[]], [[[]]] etc must be 
>> named uniquely. Have a look and see what you can find. If you can't find it 
>> post the offending part of weewx.conf (with any sensitive info removed 
>> of course).
>>
>> Gary
>>
>>
>> On Wednesday, 16 January 2019 16:21:04 UTC+10, monmul wrote:
>>>
>>> So, here is what happenedthe report got ignored!!
>>>
>>> i@raspberrypi:~ $ sudo tail -f /var/log/syslog
>>> Jan 16 19:17:32 raspberrypi weewx[530]: cheetahgenerator: Generated 1 
>>> files for report xstats in 0.09 seconds
>>> Jan 16 19:17:32 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in 
>>> 0.62 seconds
>>> Jan 16 19:17:34 raspberrypi weewx[530]: reportengine: Failed to read 
>>> skin configuration file /etc/weewx/skins/Standard/skin.conf for report 
>>> StandardReport: Duplicate keyword name at line 229.
>>> Jan 16 19:17:34 raspberrypi weewx[530]:   Report ignored
>>> Jan 16 19:17:34 raspberrypi weewx[530]: cheetahgenerator: Generated 1 
>>> files for report xstats in 0.07 seconds
>>> Jan 16 19:17:34 raspberrypi weewx[530]: engine: Launch of report thread 
>>> aborted: existing report thread still running
>>> Jan 16 19:17:34 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in 
>>> 0.62 seconds
>>> Jan 16 19:17:52 raspberrypi kernel: [  112.313399] Voltage normalised 
>>> (0x)
>>> Jan 16 19:18:08 raspberrypi kernel: [  128.953478] Under-voltage 
>>> detected! (0x00050005)
>>> Jan 16 19:18:13 raspberrypi kernel: [  133.113393] Voltage normalised 
>>> (0x)
>>>
>>> On Wednesday, 16 January 2019 13:00:18 UTC+13, gjr80 wrote:

 WeeWX generates reports from template files through a skin. Each skin 
 has a skin config file, skin.conf, which, among other things, tells 
 weeWX which templates to process. To complete the picture each skin to be 
 processed by weeWX is listed in weewx.conf under [StdReport]. Now that 
 you are getting into customizing reports/templates it's probably worth 
 your 
 while have a read through the The standard reporting service, StdReport 
 
  
 in the Customization Guide.

 You basically have two choices; create a new skin and add your template 
 to it or add your template to an existing skin. Since you are adding a new 
 page with similar look and feel to your existing site it makes sense to do 
 the latter and just add your template to the existing Standard skin. 
 To do this:

 1. edit skins/Standard/skin.conf
 2. locate the [[ToDate]] stanza which is under [CheetahGenerator]
 3. you will see here all the other templates that weeWX is to process. 
 Just pick a spot and add in your template, I would put it after 
 [[[year]]] just to keep the pattern but it doesn't really matter. I 
 will not tell you what to enter, am sure you can work that out :)
 4. save skin.conf
 5. if you have not already done so make sure a copy of your template 
 file is in the skins/Standard directory

 That's it, weeWX should process your template on the next report cycle. 
 The proof will be your generated report (page/file) appearing in the same 
 directory as all the other Standard skin files. You can also monitor your 
 log for errors, if everything goes fine you will not see much in the log 
 just one extra file being generated for the Standard skin, if there are 
 errors you should see them in the log.

 I guess you will; let us know how you go!

 You might also want to have a read through the [CheetahGenerator] 
 section  of 
 the Customization Guide.

 Gary

 On Wednesday, 16 January 2019 05:57:22 UTC+10, monmul wrote:
>
> Thank you again Gary,...now after I have made these 

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

[gjr80]

No its' in skin.conf, I was half way through rewriting when I saw you 2nd 
last post, I thought you had fixed the problem and did not see much point 
in continuing with the new post. Basically, replace weewx.conf with 
skin.conf in my now deleted post.There shoudl eb no sensitive info in 
skin.conf either. My apologies for the confusion.

Gary

On Wednesday, 16 January 2019 17:35:42 UTC+10, monmul wrote:
>
> H.I thought the error was in skin.confbut you think it might 
> be in weewx.conf.
>
> On Wed, Jan 16, 2019 at 8:04 PM gjr80 > 
> wrote:
>
>> Jan 16 19:17:34 raspberrypi weewx[530]: reportengine: Failed to read skin 
>>> configuration file /etc/weewx/skins/Standard/skin.conf for report 
>>> StandardReport: Duplicate keyword name at line 229.
>>
>>
>> And there is your clue... Have a look at line 229 (or thereabout) in 
>> weewx.conf, you have a duplicate config option name. Hard to say what it 
>> is without seeing weewx.conf. Under any given set of [] (or [[]], [[[]]] 
>> etc) each config option name must be unique, eg you cannot define template 
>> = twice under [[[year]]]. Similarly each child [[]], [[[]]] etc must be 
>> named uniquely. Have a look and see what you can find. If you can't find it 
>> post the offending part of weewx.conf (with any sensitive info removed 
>> of course).
>>
>> Gary
>>
>>
>> On Wednesday, 16 January 2019 16:21:04 UTC+10, monmul wrote:
>>>
>>> So, here is what happenedthe report got ignored!!
>>>
>>> i@raspberrypi:~ $ sudo tail -f /var/log/syslog
>>> Jan 16 19:17:32 raspberrypi weewx[530]: cheetahgenerator: Generated 1 
>>> files for report xstats in 0.09 seconds
>>> Jan 16 19:17:32 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in 
>>> 0.62 seconds
>>> Jan 16 19:17:34 raspberrypi weewx[530]: reportengine: Failed to read 
>>> skin configuration file /etc/weewx/skins/Standard/skin.conf for report 
>>> StandardReport: Duplicate keyword name at line 229.
>>> Jan 16 19:17:34 raspberrypi weewx[530]:   Report ignored
>>> Jan 16 19:17:34 raspberrypi weewx[530]: cheetahgenerator: Generated 1 
>>> files for report xstats in 0.07 seconds
>>> Jan 16 19:17:34 raspberrypi weewx[530]: engine: Launch of report thread 
>>> aborted: existing report thread still running
>>> Jan 16 19:17:34 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in 
>>> 0.62 seconds
>>> Jan 16 19:17:52 raspberrypi kernel: [  112.313399] Voltage normalised 
>>> (0x)
>>> Jan 16 19:18:08 raspberrypi kernel: [  128.953478] Under-voltage 
>>> detected! (0x00050005)
>>> Jan 16 19:18:13 raspberrypi kernel: [  133.113393] Voltage normalised 
>>> (0x)
>>>
>>> On Wednesday, 16 January 2019 13:00:18 UTC+13, gjr80 wrote:

 WeeWX generates reports from template files through a skin. Each skin 
 has a skin config file, skin.conf, which, among other things, tells 
 weeWX which templates to process. To complete the picture each skin to be 
 processed by weeWX is listed in weewx.conf under [StdReport]. Now that 
 you are getting into customizing reports/templates it's probably worth 
 your 
 while have a read through the The standard reporting service, StdReport 
 
  
 in the Customization Guide.

 You basically have two choices; create a new skin and add your template 
 to it or add your template to an existing skin. Since you are adding a new 
 page with similar look and feel to your existing site it makes sense to do 
 the latter and just add your template to the existing Standard skin. 
 To do this:

 1. edit skins/Standard/skin.conf
 2. locate the [[ToDate]] stanza which is under [CheetahGenerator]
 3. you will see here all the other templates that weeWX is to process. 
 Just pick a spot and add in your template, I would put it after 
 [[[year]]] just to keep the pattern but it doesn't really matter. I 
 will not tell you what to enter, am sure you can work that out :)
 4. save skin.conf
 5. if you have not already done so make sure a copy of your template 
 file is in the skins/Standard directory

 That's it, weeWX should process your template on the next report cycle. 
 The proof will be your generated report (page/file) appearing in the same 
 directory as all the other Standard skin files. You can also monitor your 
 log for errors, if everything goes fine you will not see much in the log 
 just one extra file being generated for the Standard skin, if there are 
 errors you should see them in the log.

 I guess you will; let us know how you go!

 You might also want to have a read through the [CheetahGenerator] 
 section  of 
 the Customization Guide.

 Gary

 On Wednesday, 16 January 2019 05:57:22 UTC+10, monmul wrote:
>
> Thank 

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

[dunbrokin]

H.I thought the error was in skin.confbut you think it might be
in weewx.conf.

On Wed, Jan 16, 2019 at 8:04 PM gjr80  wrote:

> Jan 16 19:17:34 raspberrypi weewx[530]: reportengine: Failed to read skin
>> configuration file /etc/weewx/skins/Standard/skin.conf for report
>> StandardReport: Duplicate keyword name at line 229.
>
>
> And there is your clue... Have a look at line 229 (or thereabout) in
> weewx.conf, you have a duplicate config option name. Hard to say what it
> is without seeing weewx.conf. Under any given set of [] (or [[]], [[[]]]
> etc) each config option name must be unique, eg you cannot define template
> = twice under [[[year]]]. Similarly each child [[]], [[[]]] etc must be
> named uniquely. Have a look and see what you can find. If you can't find it
> post the offending part of weewx.conf (with any sensitive info removed of
> course).
>
> Gary
>
>
> On Wednesday, 16 January 2019 16:21:04 UTC+10, monmul wrote:
>>
>> So, here is what happenedthe report got ignored!!
>>
>> i@raspberrypi:~ $ sudo tail -f /var/log/syslog
>> Jan 16 19:17:32 raspberrypi weewx[530]: cheetahgenerator: Generated 1
>> files for report xstats in 0.09 seconds
>> Jan 16 19:17:32 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in
>> 0.62 seconds
>> Jan 16 19:17:34 raspberrypi weewx[530]: reportengine: Failed to read skin
>> configuration file /etc/weewx/skins/Standard/skin.conf for report
>> StandardReport: Duplicate keyword name at line 229.
>> Jan 16 19:17:34 raspberrypi weewx[530]:   Report ignored
>> Jan 16 19:17:34 raspberrypi weewx[530]: cheetahgenerator: Generated 1
>> files for report xstats in 0.07 seconds
>> Jan 16 19:17:34 raspberrypi weewx[530]: engine: Launch of report thread
>> aborted: existing report thread still running
>> Jan 16 19:17:34 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in
>> 0.62 seconds
>> Jan 16 19:17:52 raspberrypi kernel: [  112.313399] Voltage normalised
>> (0x)
>> Jan 16 19:18:08 raspberrypi kernel: [  128.953478] Under-voltage
>> detected! (0x00050005)
>> Jan 16 19:18:13 raspberrypi kernel: [  133.113393] Voltage normalised
>> (0x)
>>
>> On Wednesday, 16 January 2019 13:00:18 UTC+13, gjr80 wrote:
>>>
>>> WeeWX generates reports from template files through a skin. Each skin
>>> has a skin config file, skin.conf, which, among other things, tells
>>> weeWX which templates to process. To complete the picture each skin to be
>>> processed by weeWX is listed in weewx.conf under [StdReport]. Now that
>>> you are getting into customizing reports/templates it's probably worth your
>>> while have a read through the The standard reporting service, StdReport
>>> 
>>> in the Customization Guide.
>>>
>>> You basically have two choices; create a new skin and add your template
>>> to it or add your template to an existing skin. Since you are adding a new
>>> page with similar look and feel to your existing site it makes sense to do
>>> the latter and just add your template to the existing Standard skin. To
>>> do this:
>>>
>>> 1. edit skins/Standard/skin.conf
>>> 2. locate the [[ToDate]] stanza which is under [CheetahGenerator]
>>> 3. you will see here all the other templates that weeWX is to process.
>>> Just pick a spot and add in your template, I would put it after
>>> [[[year]]] just to keep the pattern but it doesn't really matter. I
>>> will not tell you what to enter, am sure you can work that out :)
>>> 4. save skin.conf
>>> 5. if you have not already done so make sure a copy of your template
>>> file is in the skins/Standard directory
>>>
>>> That's it, weeWX should process your template on the next report cycle.
>>> The proof will be your generated report (page/file) appearing in the same
>>> directory as all the other Standard skin files. You can also monitor your
>>> log for errors, if everything goes fine you will not see much in the log
>>> just one extra file being generated for the Standard skin, if there are
>>> errors you should see them in the log.
>>>
>>> I guess you will; let us know how you go!
>>>
>>> You might also want to have a read through the [CheetahGenerator]
>>> section  of
>>> the Customization Guide.
>>>
>>> Gary
>>>
>>> On Wednesday, 16 January 2019 05:57:22 UTC+10, monmul wrote:

 Thank you again Gary,...now after I have made these changeshow do I
 actually "run" or whatever this template file?

 On Tuesday, 15 January 2019 20:03:21 UTC+13, gjr80 wrote:
>
> A few comments.
>
>- the python inline code I provided to calculate max annual
>rainfall needs to have a # at the start of each line
>- not sure you really want the following your template, I just
>included it in my example code to show how you would use the tags:
>
> #if $max_rain_year is not None
> Maximum annual 

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

[monmul]

line 229..I added  [[[alltime]]]?.and mirable dictu it worked!
 

   template = week.html.tmpl

[[[month]]]
template = month.html.tmpl

[[[year]]]
template = year.html.tmpl
template = alltime.html.tmpl
[[[RSS]]]
template = RSS/weewx_rss.xml.tmpl

[[[Mobile]]]
template = mobile.html.tmpl


On Wednesday, 16 January 2019 19:21:04 UTC+13, monmul wrote:
>
> So, here is what happenedthe report got ignored!!
>
> i@raspberrypi:~ $ sudo tail -f /var/log/syslog
> Jan 16 19:17:32 raspberrypi weewx[530]: cheetahgenerator: Generated 1 
> files for report xstats in 0.09 seconds
> Jan 16 19:17:32 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in 
> 0.62 seconds
> Jan 16 19:17:34 raspberrypi weewx[530]: reportengine: Failed to read skin 
> configuration file /etc/weewx/skins/Standard/skin.conf for report 
> StandardReport: Duplicate keyword name at line 229.
> Jan 16 19:17:34 raspberrypi weewx[530]:   Report ignored
> Jan 16 19:17:34 raspberrypi weewx[530]: cheetahgenerator: Generated 1 
> files for report xstats in 0.07 seconds
> Jan 16 19:17:34 raspberrypi weewx[530]: engine: Launch of report thread 
> aborted: existing report thread still running
> Jan 16 19:17:34 raspberrypi weewx[530]: ftpgenerator: ftp'd 1 files in 
> 0.62 seconds
> Jan 16 19:17:52 raspberrypi kernel: [  112.313399] Voltage normalised 
> (0x)
> Jan 16 19:18:08 raspberrypi kernel: [  128.953478] Under-voltage detected! 
> (0x00050005)
> Jan 16 19:18:13 raspberrypi kernel: [  133.113393] Voltage normalised 
> (0x)
>
> On Wednesday, 16 January 2019 13:00:18 UTC+13, gjr80 wrote:
>>
>> WeeWX generates reports from template files through a skin. Each skin has 
>> a skin config file, skin.conf, which, among other things, tells weeWX 
>> which templates to process. To complete the picture each skin to be 
>> processed by weeWX is listed in weewx.conf under [StdReport]. Now that 
>> you are getting into customizing reports/templates it's probably worth your 
>> while have a read through the The standard reporting service, StdReport 
>> 
>>  
>> in the Customization Guide.
>>
>> You basically have two choices; create a new skin and add your template 
>> to it or add your template to an existing skin. Since you are adding a new 
>> page with similar look and feel to your existing site it makes sense to do 
>> the latter and just add your template to the existing Standard skin. To 
>> do this:
>>
>> 1. edit skins/Standard/skin.conf
>> 2. locate the [[ToDate]] stanza which is under [CheetahGenerator]
>> 3. you will see here all the other templates that weeWX is to process. 
>> Just pick a spot and add in your template, I would put it after 
>> [[[year]]] just to keep the pattern but it doesn't really matter. I will 
>> not tell you what to enter, am sure you can work that out :)
>> 4. save skin.conf
>> 5. if you have not already done so make sure a copy of your template file 
>> is in the skins/Standard directory
>>
>> That's it, weeWX should process your template on the next report cycle. 
>> The proof will be your generated report (page/file) appearing in the same 
>> directory as all the other Standard skin files. You can also monitor your 
>> log for errors, if everything goes fine you will not see much in the log 
>> just one extra file being generated for the Standard skin, if there are 
>> errors you should see them in the log.
>>
>> I guess you will; let us know how you go!
>>
>> You might also want to have a read through the [CheetahGenerator] section 
>>  of the 
>> Customization Guide.
>>
>> Gary
>>
>> On Wednesday, 16 January 2019 05:57:22 UTC+10, monmul wrote:
>>>
>>> Thank you again Gary,...now after I have made these changeshow do I 
>>> actually "run" or whatever this template file?
>>>
>>> On Tuesday, 15 January 2019 20:03:21 UTC+13, gjr80 wrote:

 A few comments.

- the python inline code I provided to calculate max annual 
rainfall needs to have a # at the start of each line
- not sure you really want the following your template, I just 
included it in my example code to show how you would use the tags:

 #if $max_rain_year is not None 
 Maximum annual rainfall was $max_rain_vh.mm in $max_rain_year.format(
 "%Y") 
 #else 
 No rainfall data available 
 #end if

- $alltime.rain.maxsumm should be $alltime.rain.maxsum
- you still have some $year tags in the file relating to UV, ET and 
radiation. though unless you have a UV or radiation sensor on your 
 station 
they will do nothing.
- you have $alltime.rain.sum in a cell labelled Max Rain Year 
Total. As previously discussed $alltime.rain.sum will give you