unfug-at-github
unfug-at-github
I have created a pull request to fix this issue #124644
The spikes were created by race conditions. The component has an internal queue that is supposed to be sorted by time. During the startup phase values are loaded from the...
Since getting this into the core system seems to take quite some time, I have published a [custom component](https://github.com/unfug-at-github/statistics-home-assistant) to test the changes I made to fix this issue. It...
> @unfug-at-github Thank you for your efforts. I am very interested in testing this custom component; does it simply replace the default statistics sensor? I noticed that the platform is...
> Hello @unfug-at-github, its generally not a good idea to mix so many changes in one PR. Still, please give me some time to review, this looks like some good...
I have created a separate pull request that only addresses the issue of the spikes (#127268). I'll add further ones to reduce the scope of this one.
Added another PR for the single value case #127305
I created a new PR to fix the async issues in general #128796
I have also seen those spikes and didn't see any reason for them in my source data. I'm pretty sure that this happens because an undefined value is incorrectly being...
I have found a solution that will trigger a computation of the statistics values, even if the input value is stable. It was also mentioned in another thread here somewhere....