Yes.
Just to clarify, that’s not possible as the measurements are explicitly timestamped with the timestamp from the datalog. The time received in influx should be irrelevant.
Dropping the database and recreating should give you a clean slate. When you restart the IoTaWatt, did you have the upload history from set prior to 17/03/2019?
When the influx service starts, it queries each of the measurements to see the time of the last entry. It then starts uploading from the most recent time or the “upload history from” date - whichever is greater. If upload history from is blank, it is assumed to be now.
Understand that if you drop the database or individual measurements while the IoTaWatt is actively uploading, it will be adding newer entries even as the older ones are dropped. You need to stop the updating and remove all of the old measurements.
Try this:
- Click STOP in the influx tab of the status display.
- Wait for the status to change to stopped.
- In the IoTaWatt influx configuration:
Set “upload history from” to 03/17/2019.
Add a tag of “id” with value “iotawatt” to the tag set.
Save - Click START in the influx tab of the status display.
You should see the Last Update change to 03/17/2019 (or 17/03/2019 the way you do it).
The first tag in the tag set is a way to group and identify all of the measurements from the IoTaWatt. (You may have other measurements from other sources). With the id tag, it becomes easier administrate that set of measurements with the simple WHERE id = ‘iotawatt’ clause.
Once you verify that the update is progressing from the supplied date, you can watch the progress. It may take a few hours to accomplish upload of the whole 2.5 months.
Let us know how this works out.