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 
<http://weewx.com/docs/usersguide.htm#html_generated_but_not_updated> 
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 <http://weewx.com/docs/hardware.htm#vantage_configuration39> 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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to