This is how I think MX works, have I got it right?
What I have not worked out is why Cumulus MX changes <#metdate> before it runs the EOD SQL. The implication is to replicate the dayfile.txt date in a custom EOD SQL you need to use <#metdateyesterday> instead! I suppose it is all part of so called EOD actions mostly being START of day actions, like the stored month.ini in the daily backup will be the empty one for the new month (not the position at end of previous month) if the month has changed at rollover.Cumulus MX End of Day process
=============================
Hour change (done every hour)
Calculating Sunrise and sunset (done every hour)
Entering Day Reset (message about current day of month)
Day Reset (message about date ending, time shown as 00:00:00 because time not defined, not because it is midnight, it might be 9am or 10am)
Run EOD standard or custom SQL (the SQl is updated every time readings are updated)
Custom Http EOD call
Create line to append to dayfile.txt
Open dayfile.txt
Update dayfile.txt
Read Rain Counter
Update today.ini with yesterday's rain
Write yesterday.ini
Create NOAA monthly
Save NOAA monthly
Create NOAA yearly
Save NOAA yearly
Run EOD External Program
Processs any Extra Files with EOD option selected
Day reset complete
Read readings from weather station to assign to start of new day
Create daily backup folder to hold files as at start of new day
Copy all files from data folder (plus Cumulus.ini) into new daily folder
Resume normal operation of reading station, processing real-time and standard time interval functions
In the first Extra Files with standard interval FTP upload, add upload of Extra Files processed at end of day
