Bad data, it happens to us all. Doing some testing or a sensor fails and goes out of range - but not far enough to be discarded.
This can completely mess up the trending display, as it is doing to me right now. Even when rejecting extreme values, sometimes a glitch can return a value that is not extreme enough to be discarded, but well out of the normal operation of the process resulting in the scale being thrown off every time you try to view historical data.
I have done the export/reimport CSV thing before but this is honestly a very clumsy and slow way of editing the history, and the interface has changed somewhat to the point where I had to hand-edit my CSV last time I did it.
Is there an easier way to do this with an SQL query? I have tried modifying the pointvalues table, where the bad data point seems to be easily found with SELECT * FROM pointvalues WHERE pointvalue = $baddata;
However UPDATEing this value does not seem to result in anything changing on the charts? Is it cached somewhere or stored in another location?