I’ve running OH (3.4.3) and since the beginning of the year with InfluxDB v2.6.1. Everything works perfect.
I’m currently developing a small application which will allow me to graphically change specific values in the InfluxDB (e.g. wrong measurements at specific times) or delete specific (e.g wrong or redundant measurements) points in InfluxDB with the possibility to filter for specific values.
I’m sure, you all know this annoying problem when an item value in a line chart goes out of the way in one direction and the entire chart scaling no longer fits and the chart gets useless (e.g. in some of my temperature data, I sometimes have values of -100, once or twice a year - for what reason ever). I want to be manually able to correct these wrong values from time to time.
While I’ve testing my tool with some items, I’ve made the following observation. There a some sensor data which sends (sometimes - rare event) many of the same measurement data very fast (sometimes 10 times per second) for a period of time. There is not really a valuable information to store these, always the same, data in the DB. It only costs space. If found a (wrong behaving zigbee temperature sensor) which inserted about 80,000 times the same (wrong) value in 24h.
I wonder if the persistence service in the current OH version is able to activate an option that will only insert data into the DB, if it’s different from the previous item value?
If not, this would be a very useful option to save database storage (nearly) without loosing useful information.