Uploading stored overnight data to Wunderground

[mraviator]

I use Cumulus with a ProWeatherStation, which stores the data. I do not run Cumulus 24/7 since I shut my PC down overnight. I assumed the next morning Cumulus would upload the overnight data to Wunderground, but it does not seem to do this. Is this a feature of the software or simply not included?

Thanks,
Michael

[steve]

When I first tried this, it did not work - Wunderground would not accept retrospective data, so I didn't implement it in Cumulus. Since then, tests have shown that it does in fact work, so at some point, when I get time, I need to look at how best to implement it in Cumulus.

[mraviator]

Thanks for the answer. I did a quick test yesterday where I shut Cumulus down for 45 min (but did not unplug the box from the PC), then started Cumulus up again and the 45 minute gap was filled in on Wunderground. But when I shut the PC down overnight, it did not work. Maybe because the date changed or something.

Michael

[wd40]

Glad I found this post, I had wondered the same thing.

[mlp]

I would propose quite high priority to this as this is now the biggest (IMHO) missing feature of Cumulus.

[mlp]

Does anybody know any other software that could do the job? Generally, this should not be too complicated task as maybe the most important thing is to ensure that data won't be sent twice.

[steve]

I'm lost for words. Probably just as well...

[geoffw]

I'm lost for words. Probably just as well...

Stay 'Cool' Steve!

[nking]

Does anybody know any other software that could do the job? Generally, this should not be too complicated task as maybe the most important thing is to ensure that data won't be sent twice.

I've been having a really awful day but at least this has made me smile

[wd40]

Seems like of late, every step I take, is into something that is already there, and smells bad. Not sure what this person was thinking, if at all.

There is an old saying here, "The guy that digs the hole decides where the flag post will be."

Randy

[mlp]

Hi folks,

Thanks for not lynching me completely before letting me explain!

I'm sorry if my comment sounded offending - it was not my purpose. I'm very happy with Cumulus - and thanks for this excellent software! When I referred to another software, I ment a piece of script or something that could do the (historical) data sending to wunderground.

Even if for someone this missing feature may not be the biggest issue in Cumulus, for me this is as I'm using another application that would need to get the weather data input from wunderground. Now I'm forced to keep my HTPC running 24/7 even if Cumulus could read the stored data from Data logger whenever I start my HTPC (e.g. in the morning).

Basically I could implement this feature by creating a script which would take Cumulus data file as input and just send this data line by line to wunderground (like described in wunderground sending protocol. Weather Underground will accept old data, I have tested it and can send the entries manually)

Now, this all above would be only quick and dirty solution. You have the sending routines in Cumulus available, why just not adding a check box in wunderground settings page

"Send stored data downloaded from data logger automatically to weather underground" and after downloading the stored data from data logger, automatically forward it to wunderground.

If this all sounds ridiculous to you and completely unnecessary (=lowest priority issue), please let it be and ignore my comments.

(don't know if you have already planned this or discussed throughoutly, I'm new on this forum and have not maybe found the correct thread, and thus, please excuse me, I just tried to highlight an issue that might be very important for many users)

[steve]

You have the sending routines in Cumulus available, why just not adding a check box in wunderground settings page

"Send stored data downloaded from data logger automatically to weather underground" and after downloading the stored data from data logger, automatically forward it to wunderground.

Yes, sorry, of course, it's really simple, but I'm lazy and stupid so it will take me longer to do than it would for you, you'll just have to bear with me.

If this all sounds ridiculous to you and completely unnecessary (=lowest priority issue), please let it be and ignore my comments.

It is an issue in Cumulus which needs resolving. See my first post in this thread for why it does not do it already. It is not my highest priority. Nor is it my lowest priority. It is not as simple to resolve as you seem to think, anything beyond the most basic software just doesn't work that way.

[steve]

I've written the code to do this now, and I'm testing it. There is definitely an issue at Wunderground to do with 'past' timestamps, which is clearly why I thought it didn't work when I tried it, way back. Here's an example of an upload after I stopped Cumulus for a while. Cumulus builds a set of upload strings while downloading the archive data:

Code: Select all

29/09/2010 18:03:33.680 : Creating WU URL #1
29/09/2010 18:03:33.680 : http://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?ID=IORKNEYS2&PASSWORD=*********&dateutc=2010-09-29+16:40:00&winddir=157&windspeedmph=40&windgustmph=40&windspdmph_avg2m=29&winddir_avg2m=151&humidity=96&tempf=52.5&rainin=0.00&dailyrainin=0.46&baromin=29.82&dewptf=51.4&solarradiation=7&softwaretype=Cumulus%20v1.9.1&action=updateraw

29/09/2010 18:03:33.695 : Creating WU URL #2
29/09/2010 18:03:33.695 : http://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?ID=IORKNEYS2&PASSWORD=*********&dateutc=2010-09-29+16:45:00&winddir=157&windspeedmph=40&windgustmph=40&windspdmph_avg2m=29&winddir_avg2m=156&humidity=96&tempf=52.5&rainin=0.04&dailyrainin=0.47&baromin=29.82&dewptf=51.4&solarradiation=6&softwaretype=Cumulus%20v1.9.1&action=updateraw

29/09/2010 18:03:33.727 : Creating WU URL #3
29/09/2010 18:03:33.727 : http://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?ID=IORKNEYS2&PASSWORD=*********&dateutc=2010-09-29+16:50:00&winddir=135&windspeedmph=36&windgustmph=40&windspdmph_avg2m=28&winddir_avg2m=146&humidity=96&tempf=52.5&rainin=0.05&dailyrainin=0.48&baromin=29.82&dewptf=51.4&solarradiation=5&softwaretype=Cumulus%20v1.9.1&action=updateraw

29/09/2010 18:03:33.742 : Creating WU URL #4
29/09/2010 18:03:33.742 : http://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?ID=IORKNEYS2&PASSWORD=*********&dateutc=2010-09-29+16:55:00&winddir=157&windspeedmph=41&windgustmph=41&windspdmph_avg2m=30&winddir_avg2m=146&humidity=96&tempf=52.3&rainin=0.06&dailyrainin=0.49&baromin=29.82&dewptf=51.2&solarradiation=5&softwaretype=Cumulus%20v1.9.1&action=updateraw

Note the timestamps in UTC: 16:40:00 16:45:00 16:50:00 16:55:00

Then it uploads them:

Code: Select all

29/09/2010 18:03:35.976 : Wunderground archive entries = 4
29/09/2010 18:03:35.976 : Uploading Wunderground archive #1
29/09/2010 18:03:36.976 : Uploading Wunderground archive #2
29/09/2010 18:03:37.976 : Uploading Wunderground archive #3
29/09/2010 18:03:38.976 : Uploading Wunderground archive #4
29/09/2010 18:03:39.975 : Wunderground archive upload complete

This is the result at WU:

Code: Select all

2010-09-29 17:40:00,52.5,51.4,29.82,SSE,157,40.0,40.0,96,0.00,,,0.46,7,Cumulus v1.9.1,
2010-09-29 17:45:00,52.5,51.4,29.82,SSE,157,40.0,40.0,96,0.04,,,0.47,6,Cumulus v1.9.1,
2010-09-29 17:50:00,52.5,51.4,29.82,SE,135,36.0,40.0,96,0.05,,,0.48,5,Cumulus v1.9.1,
2010-09-29 18:03:00,52.3,51.2,29.82,SSE,157,41.0,41.0,96,0.06,,,0.49,5,Cumulus v1.9.1, 

I'm at UTC+1, so you would expect the timestamps to be 17:40:00 17:45:00 17:50:00 17:55:00, but notice that the last one is actually at the time it was uploaded, ignoring the timestamp in the upload.

This happens every time, the last one always gets the current timestamp. I don't seem to be able to do anything about this. If anyone is still reading this far and has any theories, let's hear them!

[beteljuice]

Hmm ... can't find anything in any of their documentation (eg. http://wiki.wunderground.com/index.php/ ... d_Protocol ), and as you are getting most data updated it doesn't seem order specific (i.e. having action as the last rather than first parameter).

Does it truly ignore the timestamp or does it duplicate it for stated time AND current ?

It look like 'last one in' should always be current.

[steve]

Does it truly ignore the timestamp or does it duplicate it for stated time AND current ?

It appears to ignore it. In my example, there should be an entry for 17:55, but instead there's one for 18:03. What I don't understand is - how does it know that's going to be the last one? Unless it's something to do with how far in the past the timestamp is...