I am not against an option to change the behave… that’s what I also suggested.
What I do question is the benefit of the old history compared to the new one.
Let me try other examples:
This is a Graph showing the “State” of a humidity sensor… before the update was done.
Am I able to get a real “value” out of the information given in that graph?
This is the same Graph, using the new Statistics history:
I can still see major “drops” or “peaks” in the graph - and I am still able to detect when it happened.
If I am using this for “debugging” - or for getting an insight if my sensors are delivering a wrong value, the timeframe when this happened is pretty much what I need…
Still in my eyes, the new graph does provide all the information I need to dig into an issue with one of my integrations or an issue with a Sensor.
But - the new Graph does still have values in my eyes…
It does clearly show, if a sensor was working in an expected area.
In this specific case for humidity of a terrarium:
If the hummidity drops to a lower value, it should start watering.
If the humidity reaches an upper value, it should stop.
When I am only focussing on the current state of the sensor, it could cause, that it will switch the raining-system on / off / on / off / on / off
Instead, I should use the mean value - and just define the upper and lower range where the mean should be in…
With this graph, I can easily see - if that condition was given or not…
Or am I wrong?
Again - I don’t say anything against an option to swith this on or off…
What I really don’t want is - that this feature will be removed because people are not used to the new statsitics although they could still get what they need from it