Certain records being recorded as 0.0 for "today"

[Nin3DSFan]

For some reason, when catching up data from before the rollover (at midnight), records such as "Low Temperature", "Low Apparent Temperature", "Low Feels Like", "Low Dew Point", "Low Windchill", "Low Pressure", and "Low Humidity" for today, all have values of 0.0 or 0, with a timestamp of 00:00. Also, the "Temperature Range" for yesterday is also at 0.0.
Additionally, in "This Month's Records Editor", the current values are sometimes wildly different to the Dayfile values or Logfile values.

For example, my actual low maximum and high minimum temperatures are 9.1 and 3.7 respectively, but the Dayfile value lists these as 1.4 (low maximum) and 7.2 (high minimum) respectively.

Basically, Cumulus has a complete seizure and has no idea what the frick it's doing when catching up from a "Daily backup", which is created at the very same time that the rollover happens, i.e. midnight.

Also trying to correct any wrong records is much harder than it used to be. There used to be a simple "Copy from monthly logs" or "Copy from dayfile".

[mcrossley]

Can you post a zip backup folder and I'll take a look.

[Nin3DSFan]

A backup from now, or a previous backup?

[mcrossley]

Tell you what I really need, that is...

Enable Debug and Data logging.
Then stop CMX.
Take a backup of your data folder.
Restore the data folder from the last daily backup and restart CMX

Once the recovery is complete. Stop CMX again.
Zip up that last backup folder and the last MXdiags log file.

You can then restore your copy of of the data folder and carry on.

Then post the zip file here please.

Thanks.

[Nin3DSFan]

Not sure if I did it right, but...

Also, here's a screenshot of the "Today and Yesterday" page, showing the 0.0 for all "low" records for Today, and somehow, only showing readings taken at 00:00 for Yesterday.


This whole thing seems to be caused by that stupid bug where a duplicate dayfile entry is created with all the records simply being "whatever happened at midnight":

Also, the "1021.1" for the pressure on every record is "correct" - i.e. it's not the correct pressure obviously, but it's not a bug with Cumulus, it's the station itself. It suddenly just stopped reading pressure correctly in August or September (probably need to replace the console, I'm not sure).

[mcrossley]

Thanks, I have found the problem, the backup was being done after the day reset, but before the midnight log entry was written. It needs to happen after both complete to get a consistent set of data at that point in time.

A fix in the next release.

[Nin3DSFan]

Which release is this expected to be fixed? I'm using 3.13.8 (build 3154) and it's still doing the 0.0 minimum records thing and duplicated dayfile.txt entries with lots of 00:00 readings.

[mcrossley]

Does your backed up monthly log file now contain the final entry for 00:00?

[Nin3DSFan]

If you mean in the daily backup, I updated to the build after midnight, so it hasn't performed a daily backup yet. So, when the daily backup is created at the end of today (11/11/2021) it should include the midnight entry for technically tomorrow, 12/11/2021, i.e. instead of the last entry being 11/11/2021 23:59 it should be 12/11/2021 00:00?

EDIT: I just checked the monthly log in the daily backup and yes, it does include the 12/11/2021 00:00 entry so it should be working, I assume. As for the previous post, basically I didn't read the post carefully and never really took into account that it only works on backups created after the update.

[mcrossley]

OK, it would be good to get confirmation as I'm not 100% sure that will be a complete fix.