Cumulus Support

My system had an unnattended update from MS and it reboot by itself few days ago. 4 days later when i noticed Cumulus had not restarted, i started it and it collected whatever was in the logger and did the ''catch up'' to Wunderground perfectly - even logging everything at the 1 minute intervals i had set in my station.

YET ...

Why is it that all the intervals (every 1 minutes for 4 days of backlog) were correctly written to Wunder Ground, but when Cumulus is running ''normal'' it can only log 1 interval every 10 minutes. Even if Cumulus sends an update every 5 minutes. I don't understand the logic - are the records from the ''Catch up'' function different from the ''normal'' records sent at regular intervals ?

I started the debug log to see if i had errors, i see the records being sent every 5 minutes and being accepted with ''Success'' status.. But when i look in Wunderground the registered intervals are 10 minutes appart when sending in ''normal'' mode. If i look at the records sent during the ''catch up'' mode, they are all there at 1 minutes intervals.

I don't get it .. why is it different ?

Here's the update sent at 16:45 from the Debug Log file - the record sent at 16:40 and 16:50 were similar, with the same success response :
But if i look in Wunderground, i see only the records from 16:40 and 16:50 - nothing about 16:45


But if i look in Wunderground for records from the ''catch up'' all the intervals are recorded (every 1 minutes intervals in this case).

There is one 'catch up' upload for each entry downloaded from the logger at start up. During normal running, they are sent at the interval you specify, as you can see from the debug log. I don't know why WU is only logging them at 10-minute intervals, given that it is returning 'success' for all of them.

One thought - is your PC clock set correctly?

I just did the adjustment for my clock, i'm not sure there was really a gap that large (maybe few seconds), and i'm aware of the issue with clock adjustment near midnight and avoided it by doing a manual update few months ago when i upgraded to this version.

I understand the catch up and the normal mechanism and the way it is sent to WU.. I just don't get it on the way it is showing up afterward on the WU website. Maybe someone is experiencing similar situation. I'm pretty sure it is not an issue of sending too many records , i mean they can accept and they can also correctly present the data - even with 1 minute intervals.

Mistery..

ADDED : i sent a support request to WU. We'll see what comes from it.

No answer from WU .. But the situation cleared itself last night at 00:10 . Since that time all intervals are correctly logged. Seems the issue was at WU. Slight possibility it is tied with the clock and the new day processing - as the situation went away just after the new day. Anyhow.. it's not logging (and showing) all the records at the right interval. Case closed.