How to deal with history sensors

[balloob]

Definition: 2nd order components are components that take raw data available in Home Assistant and process it into new data.

We are getting more and more 2nd order components that show a statistic over a period in the history of an entity (example: history_average which allows calculating average value during last 2 hours)

The problem with these sensors is that their state is time based and thus they update the value on every update, which spams the state machine.

How can we solve this? One thing we can do is to set a minimal update interval to limit state updates.

But what else?

[andrey-git]

Limiting update interval for 2nd order components will make them inaccurate.
Unless they want time decay they only update when the "source" component updates, right?

[balloob]

Correct.

[frenck]

This architecture issue is old, stale, and possibly obsolete. Things changed a lot over the years. Additionally, we have been moving to discussions for these architectural discussions.

For that reason, I'm going to close this issue.

../Frenck