I also had an unusually high temperature data point while I covered my Tempest during spring cleaning on one afternoon in May 2024. The high reading ended up being 102.6 F, which is way higher than any other data point over the past 2+ years I have owned my Tempest. I would be in favor of simply deleting all of the data for one particular day. Or as an option, deleting just a single piece of data (temperature, or rainfall, humidity, etc) for one day. In the big scheme of things deleting single points of data doesn’t have an impact on the big picture. However, I have one concern…
I have a third-party subscription with the SmartMixin app which reads my Tempest data. I would be concerned if any change in the data process, such as deleting historical data, may cause unexpected data feed issues with other 3rd parties. If the Tempest data ops folks decide to pursue this idea, please also work with your known 3rd parties to try and minimize unexpected errors in their data. Thanks
Yes please and I second this! I have one day with temperature data below -10 which is impossible to occur in the summer. I would like the data on this day deleted very badly. It is ruining the statistics of my station.
Yes, please make this option to be able to delete, a day, a point, a range, something… I have a year’s worth of data and I’d really love to be able to delete just the first day… Thanks, and I appreciate anything that could be done…
I had to clean my unit under running water per Tempest’s own instructions a few days ago. After turning it back on again, the unit was showing sustained winds of 50-60 mph with 105 mph wind gusts for two days.
Reached out to support who said that they cannot remove the erroneous data.
It’s ridiculous that this has not been implemented yet, either on the end-user side or support side.
I had an erroneous temperature reading when the battery got low of -28.5 degrees, which is now my record low. Tech support says their is not yet a way to delete this selected data.
My tempest went bad and I now have -40F as max Low.
I will have to delete four years of data because of one bad month
This doesn’t make any sense. There’s no way to delete a single record from a database? Oh, I’ll bet there is lol.
Even if a user has to create a support ticket and someone at Weatherflow has to run the SQL query manually, that takes about 30 seconds. Their stance on this is truly puzzling.
I agree with the need to delete inaccurate datapoints as well. My station had a failure and it recorded -39.8’F - IN FLORIDA 
Residual reading from the great snow storm of 2025?
Any update on this? From what I can see, it has by far more votes than any other feature request on the forum. It is also truly not that difficult to delete a record from a database. The lack of this feature means that one bad reading negates certain use cases for owners (being able to tracks extremes and averages for instance).
I understand building the UI for users to do it themselves would be a bit of work (and could potentially be seen as a security risk), but couldn’t a simple script be created for the folks who handle support tickets so they could do it?
Being able to analyze a dataset representing a specified amount of time is kind of one of the selling points of a device like this. Given that every battery eventually fails, it’s a guarantee that every user will eventually have bad data collected. Thus, min/max/average analysis will eventually break for every single user; just a matter of when.
I had exact same issue in opposite direction: An unrealistically high temp of 112 deg recorded on a day with temps in the 60’s. My history is now irrevocably broken wrt to all-time station high
When I asked Tempest Support to delete a bad data point, they replied with “The faulty temperature can happen whenever the voltage gets real low around 2.2V or lower.”.
Earlier this week, my batteries died and it reported a temperature of -10.7F. In Central Texas in July! Last year it recorded -32.3F degrees.
One possible fix is to automatically adjust temperature with hyper-local data points like it does for rainfall. If all the stations near me are recording 75 degrees, it’s very unlikely that I would see -10.7F.
These bad data points hurt our long-term averages and there’s now no way at all for me to easily get the weekly, monthly, yearly, or all time minimum readings (or max for others). We must have the ability to delete the bad data points, or Tempest Support must be able to do it for us when asked.
I had the same problem at the end of May but after those weird bad data points the Temperature and Humidity stopped to work. Hardware issues 
so now i have broken sensors and corrupted 4 years history
My barometric pressure sensor went bad. The readings are far off scale and the graphed data is scaled to include it, so the good data variations are so compressed it’s useless. I want to either delete the erroneous data or replace it with a reasonable dummy value (like 29.92”).