History_stats integration: scan_interval not respected (anymore)

[bcutter]

The problem

A long time ago someone (https://community.home-assistant.io/t/history-stats-integration-scan-interval-not-respected-anymore-how-to-configure-sensor-update-interval/480104) discovered that scan_interval: 900 option is not respected (anymore?) for the History Stats integration (History Stats - Home Assistant 5). Instead, sensors update every 60 seconds.

I thought about “so let’s just deactivate auto update in the UI and manually update the entities with my existing automation for that”. But: this integration is not available to be configured from the UI (yet) 😦

I have no idea when this started to not work - or to be honest - if it ever worked so the sensor gets updated only every 900 seconds. Currently the sensor is flooded on every regular sensor update (to be more precise: every 60 seconds, so not every default sensor update which is set to 30 seconds in my case).

Maybe the main question here at the end is:

How to set a scan interval for history_stats sensors?

What version of Home Assistant Core has the issue?

core-2022.12.9

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

history_stats

Link to integration documentation on our website

https://www.home-assistant.io/integrations/history_stats

Diagnostics information

No response

Example YAML snippet

- platform: history_stats
  ...
  scan_interval: 900 # syntactically accepted, but effectively ignored/not working

Anything in the logs that might be useful for us?

No response

Additional information

https://community.home-assistant.io/t/history-stats-integration-scan-interval-not-respected-anymore-how-to-configure-sensor-update-interval/480104

[home-assistant]

history_stats documentation
history_stats source

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[bcutter]

Alive because still existing. Any workaround?

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[bcutter]

Still an ISSUE.

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[bcutter]

Kept open forever.

[werdnum]

Should be an easy fix.

Currently update interval is hard-coded to 1 minute here

Need to fix the constructor to accept an update interval, then read the config value and pass it here.

(It's not actually defined as a config variable for this integration, but it is part of the default config schema defined here)

[bcutter]

Great insights thank you 😀
Are you able to submit a PR?