weather underground updating

[bruce45]

not to sure if this is a bug or just something else I have not grasped. I noticed this with 3002 build this morning but downloaded 3003 and the same thing shows

Error connecting ftp - No connection could be made because the target machine actively refused it [fe80::107c:2870:a3e3:7ce8%7]:21
2015-01-06 19:43:10.277 Error uploading realtime.txt to realtime.txt : No connection could be made because the target machine actively refused it [fe80::107c:2870:a3e3:7ce8%7]:21

the weather underground page shows that the station has reported but the temp is not updating

20150106-194233.txt

I have set avg to interactive rather than auto and was prompted to allow cumulus mx so not sure what I should be looking at to fix it

[Adrian Hudson]

I'm quite sure to be shot down but that doesn't look to me like anything to do with Wunderground. It looks like the realtime.txt ftp upload that is failing. It looks like its trying to send to an IPV6 address and I would bet my bottom dollar that your ISP doesn't support IPV6!

You do actually want your realtime uploading I suppose? Earlier versions uploaded realtime whether you wanted it or not.

If your wunderground is not updating Steve told me to put "Logging=1" in the [Station] section of cumulus.ini and the logs in MXdiags will give more information about the wunderground (and other) upload.

[bruce45]

thanks for that info.
I have disabled the ipv6 after problems yesterday and it is still disabled.
I will add the logging=1 and see if it shows any more information. its really strange as when I look at the weather history table it has not been updated but it shows the last time station updated at the top of the page.

[tumutbound]

Thanks for the Logging=1 tip.

I'm getting a message on my wunderground page that 'The PWS is not reporting'. Cumulus shows it's getting an OK from WU so looks like a WU problem.

Looks like the 2015-01-07 11:40:06.168 WU Response: OK: OK response from CumulusMX is merely indicating that WU did not respond with an error code. WU responds with an error message (INVALIDPASSWORDID|Password and/or id are incorrect) but not an HTML error code so CumuluxMX sees this as success - as it should.

EDIT: Something I've noticed in the loggin is that the softwaretype field sent to WU is set to 'Cumulus v3.0.0' even though I'm running the latest version 3003.

[steve]

Looks like the 2015-01-07 11:40:06.168 WU Response: OK: OK response from CumulusMX is merely indicating that WU did not respond with an error code. WU responds with an error message (INVALIDPASSWORDID|Password and/or id are incorrect) but not an HTML error code so CumuluxMX sees this as success - as it should.

I think that Cumulus 1 manages to show that error (in the debug log at least); if so, MX should too.

EDIT: Something I've noticed in the loggin is that the softwaretype field sent to WU is set to 'Cumulus v3.0.0' even though I'm running the latest version 3003.

That's correct.

[bruce45]

ok just an update on this. if I have rapid fire on no updates on the site. turn it off and it works without any problem. still have the error message as before so don't think it is anything to do with weather underground updating. so I think this is sort of fixed as long as you don't use rapid fire.

20150107-104616.txt

added the mxdiags just in case anyone might be able to help with the error that is been logged.

[steve]

ok just an update on this. if I have rapid fire on no updates on the site. turn it off and it works without any problem.

Good work. I'll have a look at the rapid fire code - thanks.

[mcrossley]

I'm a little confused, you say you have disabled rapid fire? But when I look at your WU page it says the station is reporting every few seconds?

Also looking at the data log it seems that Cumulus v1.9.4 and v3.0.0 were adding data at the same time? eg.

Code: Select all

2015-01-07 04:33:00,19.1,9.3,1028.3,North,360,0.0,0.0,53,0.0,,,0.0,Cumulus v1.9.4,2015-01-07 04:33:00, 
2015-01-07 04:34:00,19.1,8.9,1028.3,North,360,0.0,0.0,53,0.0,,,0.0,Cumulus v3.0.0,2015-01-07 04:34:00, 
2015-01-07 04:38:00,19.0,9.2,1028.0,North,360,0.0,0.0,53,0.0,,,0.0,Cumulus v1.9.4,2015-01-07 04:38:00, 

[bruce45]

I am running the test on the station setup in my flat not my main station.
http://www.wunderground.com/personal-we ... O3#history

it only monitors the temp so no rain or wind thought I would keep it simple to start of with

[steve]

I tried enabling rapid fire and it works OK for me. Yours seems to be working too.

[bruce45]

the cumulus.ini has RapidFire=0 so not sure what is going on I will change it back to see what happends

[bruce45]

I have turned rapidfire back on and restated cmx. with rapidfire off this is what is shown in the mxdiags log.

log1.JPG

with rapidfire turned on this is the mxdiags log

log2.JPG

both log files also attached rapidefire off

20150107-104616.txt

rapidfire on

20150107-154644.txt

wu is updating every 5 minutes with rapidfire either on or off

[steve]

with rapidfire turned on this is the mxdiags log

It doesn't log rapidfire updates, it would make the log huge.

wu is updating every 5 minutes with rapidfire either on or off

No, it's updating every few seconds.

[bruce45]

http://www.wunderground.com/personal-we ... =IARGYLLO3

this is the site I am updating with cmx there is nothing attached for wind or rain only the basic transmitter which I can put in the fridge or freezer to make rapid changes

[steve]

It's updating every few seconds. You can see that if you repeatedly refresh the page and look at the 'Station reported... ago' text. It's always a few seconds ago.