Cumulus Support

My rain counter is being reset to an incorrect value. I have updated it to 26.65 in today.ini, as well as month.ini and confirmed by looking in that database. Per the MXdiags log below, something is resetting the value, but I can't trace where it is coming from...

2018-07-16 23:17:42.384 Midnight rain found in the following entry:
2018-07-16 23:17:42.384 16/07/18,06:00,73.9,85,67.5,0.0,0.0,0,0.00,0.00,29.900,26.65,78.0,50,0.0,73.9,80.4,0.0,0,0.000,0.000,80.4,580,0.0,0,0.00,0.00
2018-07-16 23:17:42.399 Setting raintoday from logfile = 0
2018-07-16 23:17:42.399 Calculating rain counter = 26.65
2018-07-16 23:17:42.399 Midnight rain found = 26.65
2018-07-16 23:17:42.399 Getting rain totals, rain season start = 1
2018-07-16 23:17:42.399 Today = 16/07/18
2018-07-16 23:17:42.524 Rainthismonth from dayfile.txt: 4.42
2018-07-16 23:17:42.524 Rainthisyear from dayfile.txt: 26.65
2018-07-16 23:17:42.524 Station type = Davis
.........................
2018-07-16 23:17:45.187 Loaded archive record for Page=0 Record=1 Timestamp=7/16/2018 11:15:00 PM
2018-07-16 23:17:45.187 Processing archive record for 7/16/2018 11:15:00 PM
2018-07-16 23:17:45.258 Page=0 Record=1 Timestamp=7/16/2018 11:15:00 PM
2018-07-16 23:17:45.274 Writing log entry for 7/16/2018 11:15:00 PM
2018-07-16 23:17:45.287 Written log entry for 7/16/2018 11:15:00 PM
2018-07-16 23:17:45.306 Writing today.ini, LastUpdateTime = 7/16/2018 11:15:00 PM raindaystart = 26.65 rain counter = 26.65
2018-07-16 23:17:45.310 Log file entry written
2018-07-16 23:17:45.328 1 archive entries processed
.........................
2018-07-16 23:17:46.246 End of MySQL archive upload
2018-07-16 23:17:46.827 ****Rain reset? First chance: raindaystart = 26.65, Raincounter = 19.6
2018-07-16 23:17:46.827 Leaving counter at 26.65
2018-07-16 23:17:46.843 ****Rain counter reset confirmed: raindaystart = 26.65, Raincounter = 19.6
2018-07-16 23:17:46.843 Setting raindaystart to 19.6
2018-07-16 23:18:00.637 Writing log entry for 7/16/2018 11:18:00 PM
2018-07-16 23:18:00.637 Written log entry for 7/16/2018 11:18:00 PM
2018-07-16 23:18:00.652 Writing today.ini, LastUpdateTime = 7/16/2018 11:18:00 PM raindaystart = 19.6 rain counter = 19.6
2018-07-16 23:18:00.652 INSERT IGNORE INTO Monthly (LogDateTime,Temp,Humidity,Dewpoint,Windspeed,Windgust,Windbearing,RainRate,TodayRainSoFar,Pressure,Raincounter,InsideTemp,InsideHumidity,LatestWindGust,WindChill,HeatIndex,UVindex,SolarRad,Evapotrans,AnnualEvapTran,ApparentTemp,MaxSolarRad,HrsSunShine,CurrWindBearing,RG11rain,RainSinceMidnight,WindbearingSym,CurrWindBearingSym) Values('18-07-16 23:18',76.3,87,72.1,0.0,0.0,0,0.00,0.00,29.952,19.60,73.6,48,0.0,76.3,76.3,0.0,0,0.000,0.000,85.1,0,0.0,0,0.00,0.00,'N','N')
2018-07-16 23:18:00.719 MySQL: 1 rows were affected.

Cumulus is resetting it to the actual value supplied by the station. It can only work with the actual value supplied by the station, so if it has been reset by the station for some reason, you will have to accept that and let Cumulus handle it - it does its best to cope when the rain counter changes unexpectedly. Assuming it doesn't change again, you should find that the rain figure is only affected for one day, and then you can amend if necessary subsequently.

Ah okay. So since I have a VP2, I could have gone into WeatherLink and fixed it from there. Since the station was disconnected for 26 days, obviously the value was off. I will check it when I get home this evening, and if the 19" value is gone, and only the correct value of 26.65" is there, I will ignore. Thanks!