Cumulus Support

My system is showing yesterday's data with the times of maximum and minimum temperature swapped.

I don't have a solution, but I would have named your topic "Temp Time Transposed".

Do you mean Cumulus console or webpages or both ?

Looking @ your website, "today" looks reasonable, but "yesterday" times do look to be reversed.

I have no idea how that's happened; I've just checked all of the relevant code in Cumulus and it looks OK, and it seems to be OK for me. The web tag code just copies the value from the main Cumulus screen, so I assume that's the same? If not, does your web page use the correct tags - but I assume you've checked that already?

steve wrote:I have no idea how that's happened; I've just checked all of the relevant code in Cumulus and it looks OK, and it seems to be OK for me. The web tag code just copies the value from the main Cumulus screen, so I assume that's the same? If not, does your web page use the correct tags - but I assume you've checked that already?

Yes, my website and the cumulus screen show the same data. I've attached screenshots from the previous day, will check again tomorrow. Cheers.

That narrows it down a bit. Do you run Cumulus 24/7 or stop it sometimes? I've just thought of a bit of code I didn't look at...

Steve, I stop it overnight

I've looked at all of the code now, and I can't see any way that the times would get transposed; if it were as simple as that it would be affecting everyone. So I don't think your times are actually transposed, I think it's something to do with what happens when you start and stop Cumulus, and the when the midnight rollover takes place.

After you've stopped Cumulus tonight, please take a copy of today.ini and yesterday.ini. Then, after you've started Cumulus tomorrow, assuming you see the problem again, zip up the diags folder, the current today.ini and yesterday.ini, and the copies that you take tonight, and attach it all here.

Thanks, will do. Only an hour left until tomorrow

It's OK, I've found the bug. It's code that I've changed in 1.9.2. It's actually the writing of today.ini that has the bug, I've swapped the low and high times when I write them to the file. So, unless the high and/or low gets exceeded before midnight, that error gets copied over to yesterday.ini; and also, unfortunately, into dayfile.txt.

Fixed in build 992.

Ahh, thanks!