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.

[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

[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

[Gert Andersen]

Hi

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

record_generation = software

in weewx.conf

Rgds

Gert

[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

[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:

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

[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