WeeRX Not Sending Pressure to Weather Underground?

[Tony Cellini]

I set up my Acurite station today using WeeRX and everything seems to be working fine, except that it doesn't appear to be sending barometric pressure to Weather Underground.  The local values and chart for pressure are populated, but the pressure current value and chart on Wunderground hasn't updated since I changed the reporting over to WeeRX.

Any ideas?

[Tony Cellini]

Here's the link to the PWS on Weather Underground:  https://www.wunderground.com/personal-weather-station/dashboard?ID=KILBLOOM57#history

[Andrew Milner]

what does the weewx log say??  did you set altitude correctly in weewx.conf??

you should attach the log from start up of weewx until after two archive intervals and also the output from wee_debug (or a copy of weewx.conf), and we may be able to assist you.  Without the log we are working in the dark!!

[gjr80]

Hi,

The lack of pressure data is likely due to weeWX not sending it. There are 3 'pressures' used within weeWX; station pressure, barometric pressure and altimeter pressure. You can read about these in the wiki (https://github.com/weewx/weewx/wiki/Barometer,-pressure,-and-altimeter). Provided weeWX has one of the pressures the other two can be calculated.

I believe that AcuRite stations provide station pressure or weeWX field pressure. WU requires barometric pressure or weeWX field barometer. To calculate barometric pressure the temperature from 12 hours ago is required, otherwise the barometer file is set to None. Since you have only just setup your station I suspect you don't yet have 12 hours of data and hence the temperature from 12 hours ago does not yet exist and barometer will be set to None. If barometer is None weeWX does no send any barometer data to WU. You should see data appear in WU 12 hours after you started your system, I would give it 24 hours and if nothing is there then provide the detail as sought by Andrew but I would set debug=2 in weewx.conf before starting weeWX. This will let use see in the log what data is posted to WU.

You could also run weeWX directly (http://weewx.com/docs/usersguide.htm#Running_directly) and take note of which of the 'pressures' have a value and which are None.

Gary

[Andrew Milner]

PS -> Tony - the sw you are using is called weeWX rather than weeRX!!

[John Patrick Hoke]

Sometimes I think we all need a Wee RX :)

--
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+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

John P. Hoke

jo...@hoke.org

https://hoke.org/john/

Random Non-Sequiturs & Photography 

[Tony Cellini]

D'oh!  Very long day today and I was exhausted.

Current uptime on weeWX is now 13+ hours and still no pressure readings on WU.  I will check it later today after it's been up for 24 hours. If it's still not reporting, I'll look at the other stuff.

Thanks

[Andrew Milner]

It looks as though you are doing rapidfire every 30 seconds to WU.  Try and disable rapidfire.  You appear to be getting a pressure upload every now and again if one looks at the table rather than the graph at WU - but since the readings are very occasional I suspect that when WU comes to average the pressure readings at the 5 minute intervals the reading is often missing.  Not using rapidfire should help resolve this.

See also this thread:

https://groups.google.com/forum/?fromgroups#!searchin/weewx-user/accurite$20rapidfire$20and$20wu%7Csort:date/weewx-user/qhdN8xgyPxE/pEuLcVHEAQAJ

[Tony Cellini]

I'll try that, but previously I had been using VIS Reader with my Acurite and it had no problems with Rapid Fire.  It's also funny that if I refresh the PWS page on WU, it briefly flashes a pressure value in the current conditions, but then changes to -- after the page load finishes.  I've noticed it stopped graphing dewpoint, too.  That was working initially, but has since stopped.

[Andrew Milner]

Did you read the other thread??  I think the issue is connected to the accurite not providing all readings in every loop packet.  I thought this had been 'fixed' in a later version of weewx involving some form of caching, but since I do no use rapidfire I cannot add more.  Maybe gary or tom know how the rapidfire caching works (or doesn't) with accurite partial packets.

[Kevin Hedgepeth]

what version of Acurite station are you using?  if same as mine I could share Conf and you could try comparing and setting similar to mine.  I have the AcuRite 01036 -A1.  if this will help I will need your email to send the file to.

here is my wx info on Wunderground:  https://www.wunderground.com/personal-weather-station/dashboard?ID=KORHERMI18#history

kevin - Hermiston, Oregon

[Andrew Milner]

Kevin

Am I right in believing that you are using a 5 minute archive interval and that you are NOT using rapidfire - pretty much as I suggested to Tony??

[Tony Cellini]

Well, I disabled Rapid Fire and the graphing started working for Dew Point and Pressure, but the current conditions are way out of whack?  The graphs show values that are reflected on the weewx page from the server, but the current values for those two measurements are completely wrong.  I've double-checked my altitude (242m).  Below is a snip from my syslog after a couple of archive periods and I've attached my weewx.conf.

May 21 16:35:29 Plex-Server weewx[25240]: cheetahgenerator: Generated 14 files for report StandardReport in 0.19 seconds

May 21 16:35:30 Plex-Server weewx[25240]: imagegenerator: Generated 12 images for StandardReport in 0.15 seconds

May 21 16:35:30 Plex-Server weewx[25240]: copygenerator: copied 0 files to /var/www/html/weewx

May 21 16:35:30 Plex-Server weewx[25240]: restx: Wunderground-PWS: Published record 2018-05-21 16:35:00 CDT (1526938500)

May 21 16:35:42 Plex-Server gsd-media-keys[1251]: g_object_notify: object class 'UpDevice' has no property named 'g-name-owner'

May 21 16:35:42 Plex-Server gnome-shell[1140]: g_object_notify: object class 'UpClient' has no property named 'g-name-owner'

May 21 16:35:43 Plex-Server gnome-shell[1140]: g_object_notify: object class 'UpClient' has no property named 'g-name-owner'

May 21 16:35:44 Plex-Server gsd-power[1256]: g_object_notify: object class 'UpClient' has no property named 'g-name-owner'

May 21 16:35:44 Plex-Server gsd-power[1256]: g_object_notify: object class 'UpDevice' has no property named 'g-name-owner'

May 21 16:35:44 Plex-Server gsd-power[1256]: message repeated 2 times: [ g_object_notify: object class 'UpDevice' has no property named 'g-name-owner']

May 21 16:40:18 Plex-Server weewx[25240]: manager: Added record 2018-05-21 16:40:00 CDT (1526938800) to database 'weewx.sdb'

May 21 16:40:18 Plex-Server weewx[25240]: manager: Added record 2018-05-21 16:40:00 CDT (1526938800) to daily summary in 'weewx.sdb'

May 21 16:40:18 Plex-Server weewx[25240]: cheetahgenerator: Generated 14 files for report StandardReport in 0.18 seconds

May 21 16:40:18 Plex-Server weewx[25240]: restx: Wunderground-PWS: Published record 2018-05-21 16:40:00 CDT (1526938800)

May 21 16:40:18 Plex-Server weewx[25240]: imagegenerator: Generated 12 images for StandardReport in 0.15 seconds

May 21 16:40:18 Plex-Server weewx[25240]: copygenerator: copied 0 files to /var/www/html/weewx

On Sunday, May 20, 2018 at 9:54:49 PM UTC-5, Tony Cellini wrote:

[gjr80]

It appears that caching in the WU uploader is not working properly (some station emits partial packets; ie not all obs in all packets, WU does not like missing obs so the WU uploader caches the packets from your station so it can upload a complete set of obs to WU) and that is why the RF is not working properly. We can work on that later.

To work out whether the current discrepancy is weeWX or WU related we need to see what is being uploaded by weeWX. As per my earlier post please set debug=2 in weewx.conf, save weewx.conf and then restart weeWX. Once weeWX has been running for at least 10 minutes please post the log from when weeWX started, make sure you capture the entire weeWX startup and at least 10 minutes of activity. The log will be quite extensive.

Gary

[Tony Cellini]

Ok.  Here's my syslog snip with weewx running at debug=2

[gjr80]

Ok, given that there was 20 minutes difference between the last WU log entry and the time I checked your WU page I see neglible difference between the dewpoint and barometer values that weeWX uploaded and the current dewpoint and pressure values on your stations WU page. The WU plots seem consistent with these values as well. Can you have another look at the uploaded values in the log (lines starting with "restx: Ambient: url:"), your current conditions on your stations WU page, the WU plots and your weeWX page and confirm whether the discrepancy has disappeared. If not exactly what discrepancy are you seeing?

Gary

[Andrew Milner]

gary - I think that Tony disabled rapidfire and that it then started working OK if I understood his last post here.  

Is there caching of data for the rapidfire loop uploads to WU when there are partial packets involved?  I ask 'cos I think that is where the problem lies.  

WU is confusing me no end at the moment. If I look at my station I seem to get updates between my record updates and yet I do not have rapid fire enabled, so I do not have a clue where WU is getting data from - unless they are coming from a nearby station.  I am going right off WU as I find it is becoming impossible to comprehend.

[gjr80]

First sentence of Tony's 2nd last post indicates that WU is being updated but current conditions are 'way out of whack'. Seems to indicate an ongoing and different issue to me.

There is caching of packets when using RF, it appears there may be an issue the caching and as indicated in an earlier post we will look at that separately.

Gary

[Andrew Milner]

well that's why I said my wu was 'odd' when I looked today. In fact I have just had to put in a pressure correction for some unknown reason, but am still not getting much sense and am still getting weird updates (well readings going green for no apparent reason) and have double checked rapid fire is not enabled, and archive interval is 5 minutes.  The last reported time seems correct although it looks like two stations are using the same page and hence possibly the odd updates …. ALl I know is that I am lost!!!  The table looks correct - it is the 'current conditions' which seems to have a mind of its own.  I rarely look at wu so cannot say how long it has been like this.  When I last looked there was not another station near me, now there appears to be one!!

[Tony Cellini]

The dew point chart and current seem to be in sync now, but pressure is still off.  Right now, the current pressure shows 30.03, but the chart shows 29.95.  Could this be because of the "calculated" section in the .conf where everything is set to "hardware_preferred" which I take to understand, use hardware, but if that's not available do the calculation?

It seems like the pressure current value and chart sometimes DO agree, but not all the time.

On Sunday, May 20, 2018 at 9:54:49 PM UTC-5, Tony Cellini wrote:

[Andrew Milner]

Can you be much more precise in your posts

which dew point chart?  weewx or wu??

current where - in weewx or on WU?

what do you mean by 'in sync'?  What do you mean by 'pressure is off'?

which chart where shows 29.95?

The title of the thread was all about Weather Underground - this post seems to be more about weewx!!

Does the log show any errors or problems?

Please help us to help you - the log tells us all about what weewx is doing and we are not psychic mediums able to interpret your mind!!

In weewx 'current' refers to the last received archive record.  An archive record contains the averages of readings obtained over the archive period.

On WU only WU knows what current conditions refers to.  

[Tony Cellini]

This is all about what is appearing on WU, which is fed by weewx.  WU current conditions vs. the WU chart data.

Now a new wrinkle:  For some reason, weewx shows that I had 35 inches of rain in an hour.  Both on the local weewx site and on WU.  Since there's not a hurricane currently going through Central Illinois, I'm pretty sure that's erroneous.

There was a weird break in the chart data which shows both locally and on WU, then when the data resumed, there was 35" of rain recorded.  :-/

[Andrew Milner]

The data supplied by weewx to WU ends up in the WU TABLE

WU plots the data from the WU TABLE into the WU charts. The charts are nothing to do with weewx.  weewx does not upload charts to WU. Do these agree or disagree??

Personally I am not sure where WU gets 'current conditions' from since MY station shows apparent updates at intervals when I KNOW I have not uploaded fresh data!!  It used to be fine, but I have noticed the 'map' now contains another station near me in addition to mine - and I suspect that 'current conditions' now relates to the latest update from any station in the vicinity rather than just my station.  This is only a suspicion.

[Kevin Hedgepeth]

Correct.  here is the WU section of 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 = KORHERMI18
        # To guard against parsing errors, put your password in quotes:
        password = !@#$%^&*())_+

        # Set the following to True to have weewx use the WU "Rapidfire"
        # protocol. Not all hardware can support it. See the User's Guide.
        rapidfire = False

Kevin