[weewx-user] Re: Not uploading to Wu and Awekas

[Gert Andersen]

Hi

Sorry, my bad (typo).

i'm using;
record_generation = hardware
now and this is working fine.

I did the steps described in my previous post.

Thanks lot for looking.

Rgds
Gert




On Thursday, May 25, 2017 at 7:06:28 AM UTC+2, Andrew Milner wrote:
>
> Did you try hardware generation again??  As Gary suggested, using hardware 
> generation will help in any recovery situations or losses of communication 
> which you may encounter in the future.
>
>
>
> On Thursday, 25 May 2017 07:47:27 UTC+3, Gert Andersen wrote:
>
>> Hi Gary
>>
>> Working now with record_generation = software
>>
>> Thank you for a very detailed and good explanation. I did what you 
>> suggested, read the chapter about memory and then did the following:
>>
>> sudo /etc/init.d/weewx stop
>> sudo wee_device --set-interval=5
>> sudo wee_device --clear-memory (maybe just taking out the batteries might 
>> have helped as well)
>> sudo /etc/init.d/weewx start
>>
>> And WU/Awekas is now updated every 5 minnutes.
>>
>> Thanks a lot.
>>
>> Rgds
>> Gert
>>
>> On Wednesday, May 24, 2017 at 7:18:01 PM UTC+2, Gert Andersen wrote:
>>>
>>> Hi
>>>
>>> I have just moved from Meteobridge to weeWX running at Raspberry PI 3. 
>>> I'm using the API for Meteotemplate and this part works perfect.
>>>
>>> My problem is WU and Awekas. weeWX is not sending updates to these 2 
>>> networks. My WU station is ICAPITAL15. My station is Davis Vantage Pro2 
>>> using USB.
>>>
>>> I have attached the syslog.
>>>
>>> From weeWX.conf:
>>>
>>> [[Wunderground]]
>>> # This section is for configuring posts to the Weather 
>>> Underground.
>>> 
>>> # If you wish to do this, set the option 'enable' to true,
>>> # and specify a station (e.g., 'KORHOODR3') and password.
>>> enable = true
>>> station = ICAPITAL15
>>> # To guard against parsing errors, put your password in quotes:
>>> password = "password in quotes"
>>>
>>> [[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.
>>> enable = true
>>> username = gand
>>> # To guard against parsing errors, put your password in quotes:
>>> password = "password in quotes"
>>>
>>> I have deleted the fake-clock.
>>>
>>> Any hints?
>>>
>>> Thanks for your help.
>>>
>>

-- 
You received this message because you are subscribed 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: Not uploading to Wu and Awekas

[Andrew Milner]

Did you try hardware generation again??  As Gary suggested, using hardware 
generation will help in any recovery situations or losses of communication 
which you may encounter in the future.



On Thursday, 25 May 2017 07:47:27 UTC+3, Gert Andersen wrote:

> Hi Gary
>
> Working now with record_generation = software
>
> Thank you for a very detailed and good explanation. I did what you 
> suggested, read the chapter about memory and then did the following:
>
> sudo /etc/init.d/weewx stop
> sudo wee_device --set-interval=5
> sudo wee_device --clear-memory (maybe just taking out the batteries might 
> have helped as well)
> sudo /etc/init.d/weewx start
>
> And WU/Awekas is now updated every 5 minnutes.
>
> Thanks a lot.
>
> Rgds
> Gert
>
> On Wednesday, May 24, 2017 at 7:18:01 PM UTC+2, Gert Andersen wrote:
>>
>> Hi
>>
>> I have just moved from Meteobridge to weeWX running at Raspberry PI 3. 
>> I'm using the API for Meteotemplate and this part works perfect.
>>
>> My problem is WU and Awekas. weeWX is not sending updates to these 2 
>> networks. My WU station is ICAPITAL15. My station is Davis Vantage Pro2 
>> using USB.
>>
>> I have attached the syslog.
>>
>> From weeWX.conf:
>>
>> [[Wunderground]]
>> # This section is for configuring posts to the Weather 
>> Underground.
>> 
>> # If you wish to do this, set the option 'enable' to true,
>> # and specify a station (e.g., 'KORHOODR3') and password.
>> enable = true
>> station = ICAPITAL15
>> # To guard against parsing errors, put your password in quotes:
>> password = "password in quotes"
>>
>> [[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.
>> enable = true
>> username = gand
>> # To guard against parsing errors, put your password in quotes:
>> password = "password in quotes"
>>
>> I have deleted the fake-clock.
>>
>> Any hints?
>>
>> Thanks for your help.
>>
>

-- 
You received this message because you are subscribed 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: Not uploading to Wu and Awekas

[Gert Andersen]

Hi Gary

Working now with record_generation = software

Thank you for a very detailed and good explanation. I did what you 
suggested, read the chapter about memory and then did the following:

sudo /etc/init.d/weewx stop
sudo wee_device --set-interval=5
sudo wee_device --clear-memory (maybe just taking out the batteries might 
have helped as well)
sudo /etc/init.d/weewx start

And WU/Awekas is now updated every 5 minnutes.

Thanks a lot.

Rgds
Gert

On Wednesday, May 24, 2017 at 7:18:01 PM UTC+2, Gert Andersen wrote:
>
> Hi
>
> I have just moved from Meteobridge to weeWX running at Raspberry PI 3. I'm 
> using the API for Meteotemplate and this part works perfect.
>
> My problem is WU and Awekas. weeWX is not sending updates to these 2 
> networks. My WU station is ICAPITAL15. My station is Davis Vantage Pro2 
> using USB.
>
> I have attached the syslog.
>
> From weeWX.conf:
>
> [[Wunderground]]
> # This section is for configuring posts to the Weather Underground.
> 
> # If you wish to do this, set the option 'enable' to true,
> # and specify a station (e.g., 'KORHOODR3') and password.
> enable = true
> station = ICAPITAL15
> # To guard against parsing errors, put your password in quotes:
> password = "password in quotes"
>
> [[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.
> enable = true
> username = gand
> # To guard against parsing errors, put your password in quotes:
> password = "password in quotes"
>
> I have deleted the fake-clock.
>
> Any hints?
>
> Thanks for your help.
>

-- 
You received this message because you are subscribed 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: Not uploading to Wu and Awekas

[gjr80]

This has all the hallmarks of corrupt station memory. Corrupt memory 
prevents archive records from being emitted by the station, but if (my) 
memory serves me correctly, loop packets are still sent. That explains why 
meteotemplate is being updated every few seonds (it is using loop data). 
When record_generation = hardware, weeWX only kicks off reporting and 
WU/awekas uploads when an archive record is available, corrupt memory means 
no archive records therefore no reports/uploads. Changing to software 
record generation uses loop data (which we know is working) to synthesise 
an archive record (in this case) every 5 minutes. Once an archive record 
exists the reporting and uploads occur and everything seems fine. I suspect 
that if you went back to hardware record generation and turned on WU rapid 
fire updates they would work.

It might be worthwhile going back to hardware record generation and working 
through Corrupt station memory under the WeeWX generates HTML pages, but it 
does not update them 
 
section in the User's Guide. Running weeWX with debug=1 and looking 
carefully at the log will tell you whether the memory is corrupt or not.

The advantage of getting your station memory sorted and using hardware 
record generation is that if you loose connectivity to your station for 
whatever reason, once connectivity is restored weeWX will download any 
missed records from the logger. If the memory is corrupt chnaces are this 
won't (con't) happen and you will lose data.

As for changing your archive interval, you need to stop weeWX then use 
wee_device  to 
set the archive interval in the hardware. Something like:

$ wee_device --set-interval=5

should give an archive interval of 5 minutes. Once set start weeWX.

Gary

On Thursday, 25 May 2017 06:40:59 UTC+10, Gert Andersen wrote:
>
> Hi
>
> It seems to work now. I was fiddling around and changed:
>
> record_generation = software
>
> in weewx.conf
>
> Rgds
> Gert
>
> On Wednesday, May 24, 2017 at 7:18:01 PM UTC+2, Gert Andersen wrote:
>>
>> Hi
>>
>> I have just moved from Meteobridge to weeWX running at Raspberry PI 3. 
>> I'm using the API for Meteotemplate and this part works perfect.
>>
>> My problem is WU and Awekas. weeWX is not sending updates to these 2 
>> networks. My WU station is ICAPITAL15. My station is Davis Vantage Pro2 
>> using USB.
>>
>> I have attached the syslog.
>>
>> From weeWX.conf:
>>
>> [[Wunderground]]
>> # This section is for configuring posts to the Weather 
>> Underground.
>> 
>> # If you wish to do this, set the option 'enable' to true,
>> # and specify a station (e.g., 'KORHOODR3') and password.
>> enable = true
>> station = ICAPITAL15
>> # To guard against parsing errors, put your password in quotes:
>> password = "password in quotes"
>>
>> [[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.
>> enable = true
>> username = gand
>> # To guard against parsing errors, put your password in quotes:
>> password = "password in quotes"
>>
>> I have deleted the fake-clock.
>>
>> Any hints?
>>
>> Thanks for your help.
>>
>

-- 
You received this message because you are subscribed 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: System has stopped reporting everywhere

[gjr80]

wunderfixer is included with weeWX, its location will be depend on how 
weeWX was installed, it will most likely be in the /home/weewx/bin 
directory but it could be in /usr/share/weewx if you installed from a .deb 
or .rpm package. To run wunderfixer:

$ /home/weewx/bin/wunderfixer --test

if this generates an error it could be because the currently logged in user 
does not have permission to do some of the things wunderfixer does so in 
that case try running as root using:

$ sudo /home/weewx/bin/wunderfixer --test

the --test option gets wunderfixer to check WU for any missing records for 
the current day and give you a summary report of what it found and what it 
would do ('fix') but not actually do anything. By default wunderfixer 
checks the current day. The --date option lets you specify another date to 
check. So to check 17 May 2017 you would use:

$  sudo /home/weewx/bin/wunderfixer --test --date=2017-05-17

If you have 6 or 7 days to 'fix' then you will need to run wunderfixer 6 or 
7 times, one for each day. To actually 'fix' a day just remove the --test 
option. All of the other options can probably be left alone, though the 
--query option can be helpful if you think your weeWX data may be suspect, 
as you will be asked to confirm (y/n) before each WU record is updated (if 
you have a whole day to 'fix' at 5 minute intervals that is 288 
confirmations). Be aware that once data is published to WU you cannot 
change it other than deleting it. So if you have any basis for thinking you 
weeWX data is suspect, it is best to fix your weeWX data before using 
wunderfixer.

You can safely run wunderfixer for a give day as many times as you want, at 
worst WU will ignore any attempted 'fixes' for data already recorded. I 
always find it funny that if you run wunderfixer 5 times for a given day 
the chances are you will get 5 different results in terms on number of 
missing records - just the vagaries of WU.

Having wunderfixer run as a cron job is easily setup. Best to have it run 
under the root user cron so open the root user crontab using:

$ sudo crontab -e

Go to the bottom of the file and type something like (assuming wunderfixer 
is in /home/weewx/bin):

# Run wunderfixer at 1158pm daily
58 23 * * * /home/weewx/bin/wunderfixer --log weewx > /dev/null 2>&1

This will run wunderfixer at 11:58pm each night, you can change it to suit 
your requriements, but on a 5 minute interval system 11:58pm captures all 
records for that particular day. Save the file (most likely Control-O 
followed by enter then Control-X though depends on your editor). Note that 
it is a good idea to run wunderfixer at least once from the command line 
without the --test option before setting up the cron job, that way you know 
that the WU credentials in your weewx.conf work fine with wunderfixer.

Gary

On Thursday, 25 May 2017 11:28:56 UTC+10, Peter Dougherty wrote:
>
> Hi Gary,
> I've read through that link you sent until my eyes bled, and I just don't 
> understand how to use it. Like I said up top, Linux and I aren't friends, 
> we just tolerate each other's existence and call it a draw. So where do I 
> go to get a copy of wunderfixer, how do I install it, configure it to look 
> for every single piece of missing data and then run it? There are about 
> 1,800 updates that never got sent to WU in the 6+ days it was down.
>
> On Tuesday, May 23, 2017 at 9:44:05 PM UTC-4, gjr80 wrote:
>>
>> Can't say much other than 'yes it is not posting to WU' without seeing 
>> more of the log ie from weeWX startup. You can use wunderfixer 
>>  to re-post to 
>> WU. In fact it is a good idea to set up wunderfixer to run by cron on a 
>> daily basis, I run it at 23:58 each night. WU is by no means perfect and 
>> despite seeing 288 posts to WU each day in my logs some just don't make it.
>>
>> As to your previous questions. Twitter should not be that hard to set to 
>> work, I would be getting everything else back and stable before worrying 
>> about twitter. The error in the log indicates that python cannot find the 
>> requests_oauthlib module. This is not included in the standard python 
>> install, did you ever install it separately? Re-installing it would be a 
>> good starting point. You may also find more info by searching the forums 
>> for 'twitter' or maybe by looking at any comments at the start of the 
>> bin/user/twitter.py 
>> file.
>>
>> I think Tom covered the downloading of data from the logger, another easy 
>> way to tell if the last 27 hours of data has been downloaded OK is to look 
>> at your daily plots. They default to 27 hours of data with no aggregation 
>> and any (extended) missing data will show up as one or more gaps. Week, 
>> month and year plots use aggregated data so gaps may not be apparent there.
>>
>> Gary
>>
>> On Wednesday, 24 May 2017 11:22:12 UTC+10, Peter Dougherty wrote:
>>>
>>> It's doesn't appear to be sending any of the missing data to 

Re: [weewx-user] Re: System has stopped reporting everywhere

[Peter Dougherty]

Hi Gary,
I've read through that link you sent until my eyes bled, and I just don't 
understand how to use it. Like I said up top, Linux and I aren't friends, 
we just tolerate each other's existence and call it a draw. So where do I 
go to get a copy of wunderfixer, how do I install it, configure it to look 
for every single piece of missing data and then run it? There are about 
1,800 updates that never got sent to WU in the 6+ days it was down.

On Tuesday, May 23, 2017 at 9:44:05 PM UTC-4, gjr80 wrote:
>
> Can't say much other than 'yes it is not posting to WU' without seeing 
> more of the log ie from weeWX startup. You can use wunderfixer 
>  to re-post to 
> WU. In fact it is a good idea to set up wunderfixer to run by cron on a 
> daily basis, I run it at 23:58 each night. WU is by no means perfect and 
> despite seeing 288 posts to WU each day in my logs some just don't make it.
>
> As to your previous questions. Twitter should not be that hard to set to 
> work, I would be getting everything else back and stable before worrying 
> about twitter. The error in the log indicates that python cannot find the 
> requests_oauthlib module. This is not included in the standard python 
> install, did you ever install it separately? Re-installing it would be a 
> good starting point. You may also find more info by searching the forums 
> for 'twitter' or maybe by looking at any comments at the start of the 
> bin/user/twitter.py 
> file.
>
> I think Tom covered the downloading of data from the logger, another easy 
> way to tell if the last 27 hours of data has been downloaded OK is to look 
> at your daily plots. They default to 27 hours of data with no aggregation 
> and any (extended) missing data will show up as one or more gaps. Week, 
> month and year plots use aggregated data so gaps may not be apparent there.
>
> Gary
>
> On Wednesday, 24 May 2017 11:22:12 UTC+10, Peter Dougherty wrote:
>>
>> It's doesn't appear to be sending any of the missing data to Weather 
>> Underground, but it *is* sending current data. The station went back 
>> online around 18:29 today (23 May) and had been offline starting around 
>> 05:00 on 17 May. Three hours after going back online I cannot find the 
>> missing data on the WU site.
>>
>> This is a log excerpt. It appears as if it's trying to send the backlog 
>> (there are hundreds of these entries in the log).
>>
>> .
>> May 23 18:34:32 wx weewx[1905]: manager: added record 2017-05-22 02:20:00 
>> EDT (1495434000) to database 'weewx.sdb'
>> May 23 18:34:32 wx weewx[1905]: manager: added record 2017-05-22 02:20:00 
>> EDT (1495434000) to daily summary in 'weewx.sdb'
>> May 23 18:34:32 wx weewx[1905]: restx: PWSWeather: Published record 
>> 2017-05-22 02:15:00 EDT (1495433700)
>> May 23 18:34:33 wx weewx[1905]: restx: CWOP: record 2017-05-22 02:20:00 
>> EDT (1495434000) is stale (144873 > 60).
>> May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:25:00 
>> EDT (1495434300) to database 'weewx.sdb'
>> May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:25:00 
>> EDT (1495434300) to daily summary in 'weewx.sdb'
>> May 23 18:34:33 wx weewx[1905]: restx: PWSWeather: Published record 
>> 2017-05-22 02:20:00 EDT (1495434000)
>> May 23 18:34:33 wx weewx[1905]: restx: CWOP: record 2017-05-22 02:25:00 
>> EDT (1495434300) is stale (144573 > 60).
>> May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:30:00 
>> EDT (1495434600) to database 'weewx.sdb'
>> May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:30:00 
>> EDT (1495434600) to daily summary in 'weewx.sdb'
>> May 23 18:34:33 wx weewx[1905]: restx: PWSWeather: Published record 
>> 2017-05-22 02:25:00 EDT (1495434300)
>> May 23 18:34:33 wx weewx[1905]: restx: CWOP: record 2017-05-22 02:30:00 
>> EDT (1495434600) is stale (144273 > 60).
>> May 23 18:34:33 wx weewx[1905]: manager: added record 2017-05-22 02:35:00 
>> EDT (1495434900) to database 'weewx.sdb'
>> May 23 18:34:33 wx weewx[1905]: restx: PWSWeather: Published record 
>> 2017-05-22 02:30:00 EDT (1495434600)
>>
>

-- 
You received this message because you are subscribed 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: ET Evaporation calculations - differs significant with reading from VP Pro2 console

[Frank Bandle]

Thomas

yes we still checked the sum too and it seems that its working. So I guess
we can close this issue. I got similiar values here on my 5 weewx stations
and it matches with 2 VP Pro 2 consoles . We still test with 2 other
stations here in the network. I think it works and our receivers read the
values every 5 minutes and not only 1 time a hour. So I had the wrong
values I compared in my first view. Thank you

-frank

-- 
Frank Bandle
Sent with Airmail

Am 24. Mai 2017 um 23:07:00, Thomas Keffer (tkef...@gmail.com) schrieb:

I just had a chance to check the daily sum. It also matches what's being
shown on the console.

One other thing: the console can display total ET in either inches, or
millimeters. Make sure the unit matches what is in your database.

-tk

On Tue, May 23, 2017 at 7:06 AM, Thomas Keffer  wrote:

> It's too early in the day here to get a daily total ET, but my monthly
> value matches what's shown on the console perfectly.
>
> SELECT SUM(ET) FROM archive WHERE dateTime>1493622000;
>
> -tk
>
> On Tue, May 23, 2017 at 5:42 AM, Frank Bandle 
> wrote:
>
>> Yes - still if I look in the database and add the values - at the end of
>> the day its ten times less then the VP PRO 2 console reading.
>>
>> -frank
>>
>> --
>> Frank Bandle
>> Sent with Airmail
>>
>> Am 23. Mai 2017 um 14:36:07, Luc Heijst (ljm.hei...@gmail.com) schrieb:
>>
>> Hi Frank,
>>
>> I can't check my ET values on the Davis console because the solar sensor
>> is connect to my Anemometer Transport Kit which values can be read by the
>> Meteostick driver, but not by the Vantage driver.
>> The Davis console show the ET DAILY value whereas weewx show the ET
>> values per archive period (typically 5 minutes).
>>
>> To compare the two values we should totalize the weewx ET values per day
>> I think.
>>
>> Cheers, Luc
>>
>> On Tuesday, 23 May 2017 09:02:00 UTC-3, fraban wrote:
>>>
>>> Hi all
>>>
>>> I recognized a problem here with my ET readings with weewx and
>>> "meteostick".
>>> We have several VP PRO 2 active plus stations and with ET we see
>>> different values.
>>> Actually today we can see ET value 1.8mm on the Vantage PRO 2 console,
>>> but still weewx - we use 3.7.1 and 3.6.2 we have "0"
>>> Also the value ET we export to our network will be "0"
>>>
>>> I mirrored one system so you can see that ET is zero:
>>> *https://api2.weather365.net/wx85375-02/
>>> *max reading is
>>> 0.1  today here //   VP PRO 2 console has a value of 1.8mm
>>> also the ET value export to our network here is 0.
>>> *https://stations.weather365.net/#/station1
>>>    *
>>>
>>> Any idea whats going wrong here-  May be it´s 10 time too low (
>>> magnitude error ? )
>>>
>>> Thanks for checking
>>> - frank
>>>
>>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/weewx-user/U8paNZpBGo8/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to a topic in the
Google Groups "weewx-user" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/weewx-user/U8paNZpBGo8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: [weewx-user] Re: ET Evaporation calculations - differs significant with reading from VP Pro2 console

[Thomas Keffer]

I just had a chance to check the daily sum. It also matches what's being
shown on the console.

One other thing: the console can display total ET in either inches, or
millimeters. Make sure the unit matches what is in your database.

-tk

On Tue, May 23, 2017 at 7:06 AM, Thomas Keffer  wrote:

> It's too early in the day here to get a daily total ET, but my monthly
> value matches what's shown on the console perfectly.
>
> SELECT SUM(ET) FROM archive WHERE dateTime>1493622000;
>
> -tk
>
> On Tue, May 23, 2017 at 5:42 AM, Frank Bandle 
> wrote:
>
>> Yes - still if I look in the database and add the values - at the end of
>> the day its ten times less then the VP PRO 2 console reading.
>>
>> -frank
>>
>> --
>> Frank Bandle
>> Sent with Airmail
>>
>> Am 23. Mai 2017 um 14:36:07, Luc Heijst (ljm.hei...@gmail.com) schrieb:
>>
>> Hi Frank,
>>
>> I can't check my ET values on the Davis console because the solar sensor
>> is connect to my Anemometer Transport Kit which values can be read by the
>> Meteostick driver, but not by the Vantage driver.
>> The Davis console show the ET DAILY value whereas weewx show the ET
>> values per archive period (typically 5 minutes).
>>
>> To compare the two values we should totalize the weewx ET values per day
>> I think.
>>
>> Cheers, Luc
>>
>> On Tuesday, 23 May 2017 09:02:00 UTC-3, fraban wrote:
>>>
>>> Hi all
>>>
>>> I recognized a problem here with my ET readings with weewx and
>>> "meteostick".
>>> We have several VP PRO 2 active plus stations and with ET we see
>>> different values.
>>> Actually today we can see ET value 1.8mm on the Vantage PRO 2 console,
>>> but still weewx - we use 3.7.1 and 3.6.2 we have "0"
>>> Also the value ET we export to our network will be "0"
>>>
>>> I mirrored one system so you can see that ET is zero:
>>> * https://api2.weather365.net/wx85375-02/
>>> *max reading is
>>> 0.1  today here //   VP PRO 2 console has a value of 1.8mm
>>> also the ET value export to our network here is 0.
>>> * https://stations.weather365.net/#/station1
>>>    *
>>>
>>> Any idea whats going wrong here-  May be it´s 10 time too low (
>>> magnitude error ? )
>>>
>>> Thanks for checking
>>> - frank
>>>
>>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/weewx-user/U8paNZpBGo8/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

[weewx-user] Re: Not uploading to Wu and Awekas

[Gert Andersen]

Hi

It seems to work now. I was fiddling around and changed:

record_generation = software

in weewx.conf

Rgds
Gert

On Wednesday, May 24, 2017 at 7:18:01 PM UTC+2, Gert Andersen wrote:
>
> Hi
>
> I have just moved from Meteobridge to weeWX running at Raspberry PI 3. I'm 
> using the API for Meteotemplate and this part works perfect.
>
> My problem is WU and Awekas. weeWX is not sending updates to these 2 
> networks. My WU station is ICAPITAL15. My station is Davis Vantage Pro2 
> using USB.
>
> I have attached the syslog.
>
> From weeWX.conf:
>
> [[Wunderground]]
> # This section is for configuring posts to the Weather Underground.
> 
> # If you wish to do this, set the option 'enable' to true,
> # and specify a station (e.g., 'KORHOODR3') and password.
> enable = true
> station = ICAPITAL15
> # To guard against parsing errors, put your password in quotes:
> password = "password in quotes"
>
> [[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.
> enable = true
> username = gand
> # To guard against parsing errors, put your password in quotes:
> password = "password in quotes"
>
> I have deleted the fake-clock.
>
> Any hints?
>
> Thanks for your help.
>

-- 
You received this message because you are subscribed 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: forecast (3.2.4) from NWS using AFM format

[bgrattan]

Follow up from log:

forecast: NWSThread: NWS: downloading forecast from 
'http://forecast.weather.gov/product.php?site=NWS&product=AFM&format=txt&issuedby=AKQ'

forecast: NWSThread: NWS: no PFM found for VAZ115 in forecast from AKQ

Maybe "NWS_DEFAULT_PFM_URL" doesn't work for AFM? Seems to be the same text 
format.


-- 
You received this message because you are subscribed 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] forecast (3.2.4) from NWS using AFM format

[bgrattan]

Hello,

I am trying to get an NWS forecast for my area (Ashland, VA) which is in 
the AFM format for VAZ115. There does not seem to be one for Ashland in the 
PFM format.
I have added the following to forecast.py:

NWS_DEFAULT_PFM_URL = 
'http://forecast.weather.gov/product.php?site=NWS&product=AFM&format=txt' 

The lid VAZ115 and foid AKQ are in place.

Not sure this is going to work.  Is this all I need to modify?  Weewx is a 
manual install on latest ubuntu and is working fine,

see: http://grattans.org/wx/forecast/multiple-tables.html

Thanks in advance.

Bob

-- 
You received this message because you are subscribed 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: Not uploading to Wu and Awekas

[Gert Andersen]

Hi 

Thanks for looking into this.

More than 2 hours have passed and neither WU nor Awekas has been updated.

BTW, where can I change the archive interval to  5 minutes.

Sorry, but I'm new with weeWX.

Rgds
Gert

On Wednesday, May 24, 2017 at 7:26:42 PM UTC+2, Andrew Milner wrote:
>
> Your archive interval is at 1800 seconds set in hardware - so no output 
> will occur until the archive interval has passed ie 30 minutes
>
>
>
> On Wednesday, 24 May 2017 20:18:01 UTC+3, Gert Andersen wrote:
>
>> Hi
>>
>> I have just moved from Meteobridge to weeWX running at Raspberry PI 3. 
>> I'm using the API for Meteotemplate and this part works perfect.
>>
>> My problem is WU and Awekas. weeWX is not sending updates to these 2 
>> networks. My WU station is ICAPITAL15. My station is Davis Vantage Pro2 
>> using USB.
>>
>> I have attached the syslog.
>>
>> From weeWX.conf:
>>
>> [[Wunderground]]
>> # This section is for configuring posts to the Weather 
>> Underground.
>> 
>> # If you wish to do this, set the option 'enable' to true,
>> # and specify a station (e.g., 'KORHOODR3') and password.
>> enable = true
>> station = ICAPITAL15
>> # To guard against parsing errors, put your password in quotes:
>> password = "password in quotes"
>>
>> [[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.
>> enable = true
>> username = gand
>> # To guard against parsing errors, put your password in quotes:
>> password = "password in quotes"
>>
>> I have deleted the fake-clock.
>>
>> Any hints?
>>
>> Thanks for your help.
>>
>

-- 
You received this message because you are subscribed 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: Not uploading to Wu and Awekas

[Andrew Milner]

Your archive interval is at 1800 seconds set in hardware - so no output 
will occur until the archive interval has passed ie 30 minutes



On Wednesday, 24 May 2017 20:18:01 UTC+3, Gert Andersen wrote:

> Hi
>
> I have just moved from Meteobridge to weeWX running at Raspberry PI 3. I'm 
> using the API for Meteotemplate and this part works perfect.
>
> My problem is WU and Awekas. weeWX is not sending updates to these 2 
> networks. My WU station is ICAPITAL15. My station is Davis Vantage Pro2 
> using USB.
>
> I have attached the syslog.
>
> From weeWX.conf:
>
> [[Wunderground]]
> # This section is for configuring posts to the Weather Underground.
> 
> # If you wish to do this, set the option 'enable' to true,
> # and specify a station (e.g., 'KORHOODR3') and password.
> enable = true
> station = ICAPITAL15
> # To guard against parsing errors, put your password in quotes:
> password = "password in quotes"
>
> [[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.
> enable = true
> username = gand
> # To guard against parsing errors, put your password in quotes:
> password = "password in quotes"
>
> I have deleted the fake-clock.
>
> Any hints?
>
> Thanks for your help.
>

-- 
You received this message because you are subscribed 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] Not uploading to Wu and Awekas

[Gert Andersen]

Hi

I have just moved from Meteobridge to weeWX running at Raspberry PI 3. I'm 
using the API for Meteotemplate and this part works perfect.

My problem is WU and Awekas. weeWX is not sending updates to these 2 
networks. My WU station is ICAPITAL15. My station is Davis Vantage Pro2 
using USB.

I have attached the syslog.

>From weeWX.conf:

[[Wunderground]]
# This section is for configuring posts to the Weather Underground.

# If you wish to do this, set the option 'enable' to true,
# and specify a station (e.g., 'KORHOODR3') and password.
enable = true
station = ICAPITAL15
# To guard against parsing errors, put your password in quotes:
password = "password in quotes"

[[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.
enable = true
username = gand
# To guard against parsing errors, put your password in quotes:
password = "password in quotes"

I have deleted the fake-clock.

Any hints?

Thanks for your help.

-- 
You received this message because you are subscribed 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.
May 24 18:43:03 weeWX systemd[1]: Time has been changed
May 24 18:43:03 weeWX weewx[632]: engine: Using configuration file 
/etc/weewx/weewx.conf
May 24 18:43:03 weeWX weewx[632]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
May 24 18:43:03 weeWX weewx[632]: engine: StdConvert target unit is 0x1
May 24 18:43:03 weeWX weewx[632]: wxcalculate: The following values will be 
calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, 
maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
May 24 18:43:03 weeWX weewx[632]: wxcalculate: The following algorithms will be 
used for calculations: altimeter=aaNOAA, maxSolarRad=RS
May 24 18:43:03 weeWX weewx[632]: engine: Archive will use data binding 
wx_binding
May 24 18:43:03 weeWX weewx[632]: engine: Record generation will be attempted 
in 'hardware'
May 24 18:43:03 weeWX weewx[632]: engine: The archive interval in the 
configuration file (300) does not match the station hardware interval (1800).
May 24 18:43:03 weeWX weewx[632]: engine: Using archive interval of 1800 
seconds (specified by hardware)
May 24 18:43:03 weeWX weewx[632]: engine: Using binding 'wx_binding' to 
database 'weewx.sdb'
May 24 18:43:03 weeWX weewx[632]: manager: Starting backfill of daily summaries
May 24 18:43:03 weeWX weewx[632]: restx: StationRegistry: Registration not 
requested.
May 24 18:43:03 weeWX weewx[632]: restx: Wunderground-PWS: Data for station 
ICAPITAL15 will be posted
May 24 18:43:03 weeWX weewx[632]: restx: PWSweather: Posting not enabled.
May 24 18:43:03 weeWX weewx[632]: restx: CWOP: Posting not enabled.
May 24 18:43:03 weeWX weewx[632]: restx: WOW: Posting not enabled.
May 24 18:43:03 weeWX weewx[632]: restx: AWEKAS: Data will be uploaded for user 
gand
May 24 18:43:03 weeWX weewx[632]: restx: Meteotemplate: service version is 0.9
May 24 18:43:03 weeWX weewx[632]: restx: Meteotemplate: Data will be uploaded 
to http://vsvejr.dk/vsvejr/api.php
May 24 18:43:03 weeWX weewx[632]: engine: Starting up weewx version 3.7.1
May 24 18:43:03 weeWX weewx[632]: engine: Clock error is 0.15 seconds (positive 
is fast)
May 24 18:43:05 weeWX weewx[632]: engine: Starting main packet loop.
May 24 18:43:06 weeWX weewx[632]: restx: Meteotemplate: Published record 
2017-05-24 18:43:06 CEST (1495644186)
May 24 18:43:06 weeWX weewx[632]: restx: Meteotemplate: Published record 
2017-05-24 18:43:06 CEST (1495644186)
May 24 18:43:08 weeWX weewx[632]: restx: Meteotemplate: Published record 
2017-05-24 18:43:08 CEST (1495644188)
May 24 18:43:08 weeWX dhcpcd[733]: ham0: using IPv4LL address 169.254.185.103
May 24 18:43:08 weeWX dhcpcd[733]: ham0: adding route to 169.254.0.0/16
May 24 18:43:08 weeWX avahi-daemon[440]: Registering new address record for 
169.254.185.103 on ham0.IPv4.
May 24 18:43:08 weeWX kernel: [   26.128995] random: crng init done
May 24 18:43:09 weeWX dhcpcd[733]: ham0: no IPv6 Routers available
May 24 18:43:10 weeWX weewx[632]: restx: Meteotemplate: Published record 
2017-05-24 18:43:10 CEST (1495644190)
May 24 18:43:10 weeWX ntpd[757]: Listen normally on 9 ham0 169.254.185.103 UDP 
123
May 24 18:43:10 weeWX ntpd[757]: peers refreshed