AWEKAS

[Barton Phillips]

How do I set up AWEKAS? At one point I had it working with a awekas.html file but I no longer have that file. I went to the website and tried to set it up to use 'weewx direct connect' but that does not seem to work. What am I missing?

[Andrew Milner]

If you are trying to submit data to awekas see

http://weewx.com/docs/usersguide.htm#[StdRESTful]

[Barton Phillips]

That doesn't really answer my question. I have the weewx.conf file setup correctly (I think). What I want to know is what I should do at the AWEKAS site. They have an dropdown for the "Report mode" with "Weewx Direct Link". That is what I have selected, but I don't get any uploads. What should I select. There is a "wview" option which I think I was using before but it asks for a filename and I don't have a file and I don't know what the format should be or how to create it.

[Barton Phillips]

Here is what it says in my log file:

Dec 28 11:20:17 raspberrypi weewx[18233]: restx: AWEKAS: Failed to publish record 2016-12-28 11:20:00 PST (1482952800): server returned ' - Temperatur administrativ gesperrt - Luftfeuchte administrativ gesperrt - Luftdruck administrativ gesperrt - Niederschlag administrativ gesperrt - Windmessung administrativ gesperrt - Regenrate administrativ gesperrt  - Transfer OK'

It means the the values were "blocked" by an administrative function.

[ma...@erwinheger.de]

As you can see: Weewx works. What happens on the other side at Awekas ... ask them. For me, the Weewx direct link didn't work either, I used to have the data-file transfered to my webspace. Because of too many restrictive administrative action by Awekas I quit the service.

Erwin Heger

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

[mwall]

Take a look at the thread "data quality system locking" in the awekas forum.

Awekas would often complain if a station sends partial packets, for example if a the station lost contact with the wind sensor.

m

[mwall]

On Wednesday, December 28, 2016 at 2:26:40 PM UTC-5, Barton Phillips wrote:

Here is what it says in my log file:

Dec 28 11:20:17 raspberrypi weewx[18233]: restx: AWEKAS: Failed to publish record 2016-12-28 11:20:00 PST (1482952800): server returned ' - Temperatur administrativ gesperrt - Luftfeuchte administrativ gesperrt - Luftdruck administrativ gesperrt - Niederschlag administrativ gesperrt - Windmessung administrativ gesperrt - Regenrate administrativ gesperrt  - Transfer OK'

It means the the values were "blocked" by an administrative function.

barton,

go to the awekas web site and log in to your account.

go to the bottom of the page and click on the 'Go to quality checking system' link

http://www.awekas.at/en/qualcheck.php?id=XXXXX

there you should see when locks were applied to your system, and whether those locks are still in place.

i'm not sure how one goes about removing locks, especially when they are 'permanent'.

i once had a fine offset reporting to awekas, and it lost contact with the sensor unit when the batteries died.  it took me a week or two to get to the station to replace the batteries, and in that time awekas decided the station was flat-lining, so it did a permanent lock on the station.

i never figured out how to remove the locks, so if you figure it out, please post!

m

[Barton Phillips]

I think I will just 'shine them on'. I can't find any information about blocked transmissions and now where to ask a question.

[mwall]

On Thursday, December 29, 2016 at 1:55:37 PM UTC-5, Barton Phillips wrote:

I think I will just 'shine them on'. I can't find any information about blocked transmissions and now where to ask a question.

i understand why the folks at AWEKAS would like to detect bad sensor data and keep it from entering their database.  but it seems like a silly design to require human intervention to unlock a station/sensor.  one would think that they could detect automatically a return to normal/reasonable values just as easily as they could detect bogus values...

m

[WindnFog]

    I just read the entire thread.  I really don't have much to offer other than it's been working for me for over a year:

Dec 30 12:55:15 norge weewx[31456]: restx: AWEKAS: Published record 2016-12-30 12:55:00 AST (1483116900)

    All this adds to the dilemma is it questions if it's really a weewx configuration problem or a AWEKAS problem.  Here's the relavent section of my weewx.conf file:

    [[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 = VE1DX
        password = xxxxxxxxxx

    Don't know if this helps, but the above has been ticking away for about a year, once every 5 minutes.  I don't recall how I set up an account on their web site or set other parameters.  As I recall, I set up 4-5 uploads to variopus sites and the only one I had to struggle with was the MET in the UK.  AWEKAS was few minutes at most.  Wish I had the answer.  I know I gave the worst one "works for me!", but perhaps it will lead to someone thinking of the real answer.

<http://www.awekas.at/en/instrument.php?id=13082>

- Paul

[Andrew Milner]

Barton

Do you have a weather station that emits partial packets, or are you emitting incomoplete records to awekas??|  \\\\\just a thought ....