Why can’t I get rid of bad sensor data?

[Bonneville (Jörgen Willborg)]

Thanks, this post saved me a lot of time!

[SpookyAwol]

It would be great to see an easy option

One sudden spike throws out the data:

If theres no edit option, then unless you are some sort of database god, it seems like there is no option to fix the data?

[mauriceatkinson]

I have the same problem and it is annoying as it throws out all calculations

[Yoast74 (Joost Dekker)]

In the process of migrating from Domoticz and although HA is easier and more intuitive than domoticz the latter had a great gimmick: In the graph you could click on an invalid point while holding shift and domoticz would ask if you would like to delete that specific point
Is there a uservote / functionality request option for HA?

[C0mmanda]

@Yoast74

In the process of migrating from Domoticz and although HA is easier and more intuitive than domoticz the latter had a great gimmick: In the graph you could click on an invalid point while holding shift and domoticz would ask if you would like to delete that specific point

This kind of functionality would be great.
My Energy-Dashboard is totally worthless for this year due to wrong statistic date I can’t remove.
Unbelievable that this discussion started one year ago…

[Thyraz]

I made myself a Node-Red flow to automatically detect and delete those bad values.
But not from the internal Sqlite db, as I use InfluxDB and Grafana for energy dashboarding.

Nonetheless: Maybe it helps someone to create a similar solution for his needs instead of manually deleting bad Zwave values every few weeks from his history.

Sharing Node-Red flow to automatically detect bad energy data (Zwave transmission errors) and remove it from a DB

Hello everyone. This discussion made me think, that removing bad data from a DB manually by looking at charts and pressing buttons (or executing requests) isn’t really the “smart home” or “home automation” way of life. So I tried to figure out a way to clean up my database automatically with a Node-Red flow. I’m not using the internal HA energy dashboards, but InfluxDB and Grafana. But maybe this still helps other people to solve this problem or port this over for the internal SQLite…

[MuWaHaHa]

Same thing for me unfortunately

I need to delete data from my freeze sensor because it was kept out of it for a few hours…

[EdV (Ed Voncken)]

Today, my DSMR gas sensor apparently had a hiccup; it reported 0 m3 for a minute or so. Now, today’s gas consumption is way off (I think it exceeds Tata Steel daily consumption).

Since this is not a ‘statistic’, it seems like this is an unrecoverable error? There is no way to remove a faulty data point that I could find.

I sorely miss this functionality (as well as being able to mass-delete non-existent devices)

Is there perhaps an add-on that would allow me to repair the data?

Thanks!

[Thonglor]

I also need this feature, e.g. to fix the pool water temperature of 284.05°C:

[Thonglor]

I had to remove this value manually in the following way: I searched with the tool DB Browser (SQLite) for the faulty value (“284.05”) in the STATES database and noted down the state_id. Then, I deleted this single value with DELETE FROM "states" WHERE state_id='1278727'; and the chart looks properly again:

[ariel]

Just discovered HA’s long term stats existed today after I saw the 2023.12 posting that talks about them. Unfortunately I also found today that most of my sensors collected outliers over the last year or so, which renders the long term stats totally useless, see for instance

I looked into a random sample of 12 sensors (all of which have outliers) and not a single one of them shows the “fix” icon described above, supposed to be in Development Tools > Statistics list. Not sure what is the criteria but these are all sensors from standard temp / humidity / etc zwave devices.

We really need a feature in the History Graph so that we can click on the outlier point (which is always easy) and then be offered the option to “Delete this point”. Without this, long term stats have been useless every time I tried to use them.

Edit: it would also be useful to have a “reset sensor stats” type button to target all data or a specific period of data, for a specific sensor.

[petro]

Please create a feature request if you have feature requests. The month of WTH ended 14 months ago.