My fix for the rainfall reset on restart/boot

Thank you! We are putting this in our new release (which will be in Python3).

BP

Just looked through the code and methods in extracting data from everywhere.
Maybe we should open a new thread for that. But for the next release at least, this could be very nice to have.
IMHO - we should rework the way we store the data to disk in a state file.

2 Things I noticed:
1. The change time of the file is not updated. means, we can't check with a simple script if we should reread the file for new content or not. We have to actually read it all and compare to the backup file.
2. We have no indication as to when the data was extracted (Written into the file). There os no timestamp in it.

What should be done is as follows:
If there will be no update of the file time change, at least implant a current timestamp (can also be an epoch tag - seconds since 1.1.1970).
We could append the epoch to each entry. Making it kind of a csv type file.
`
0.0;1599141749
0;1599141749
0;1599141750
0;1599141750
;1599141750
0.0;1599141755
0.000349245965562;1599141755
0.0;1599141756
26.41;1599141757
93.81;1599141757
645.332015672;1599141758
93.822;1599141759
23.1000003815;1599141760
26.2000007629;1599141760
270.0;1599141761
4.4454375;1599141761
25.3;1599141762
23.7;1599141762
`

Then of course, we could also have the option to have that data formatted in json or so.

That would make post-processing way easier. Especially, of the data is already there, we can of course add some other entries like the currently use Unit, and entry name etc.

I for example, extract the data, put it into a MySQL DB for analysis, then dump it again. But I'm never sure from what time exactly the data is.

There is an error in your script replacement - but only noticeable if you are logging to a database.

The Line that does the insert was changed to include the value od totalRain[-1] - MarioDb complains with these types of tables that have [-1] - it was probably done through a global search and replace and never noticed until someone like me came along to test your code and found the fault because I log to a db.

The line was easily changed in removing totalRain[-1] to totalRain as per here...

query = 'INSERT INTO WeatherData(TimeStamp,as3935LightningCount, as3935LastInterrupt, as3935LastDistance, as3935LastStatus, currentWindSpeed, currentWindGust, totalRain,  bmp180Temperature, bmp180Pressure, bmp180Altitude,  bmp180SeaLevel,  outsideTemperature, outsideHumidity, currentWindDirection, currentWindDirectionVoltage, insideTemperature, insideHumidity, AQI) VALUES(UTC_TIMESTAMP(), %.3f, %.3f, %.3f, "%s", %.3f, %.3f, %.3f, %i, %.3f, %.3f, %.3f, %.3f, %.3f, %.3f, %.3f, %.3f, %.3f, %.3f)' % (as3935LightningCount, as3935LastInterrupt, as3935LastDistance, as3935LastStatus, state.ScurrentWindSpeed, state.ScurrentWindGust, state.currentTotalRain,  state.currentInsideTemperature, state.currentBarometricPressure, state.currentAltitude,  state.currentSeaLevel,  state.currentOutsideTemperature, state.currentOutsideHumidity, state.ScurrentWindDirection, currentWindDirectionVoltage, state.currentInsideTemperature, state.currentInsideHumidity, state.Outdoor_AirQuality_Sensor_Value)


Confirm to have noticed that too. The Rain stays for a long time. It is never reset to 0.