Riemann Sum integral graph for energy from power sensor looks good in compact mode but shows only spikes in full graph, due to docker daemon restart at night

[darkmattercoder]

The problem

I have a power measuring device (Tasmota on GOSUND SP111) whose power value I feed into a Riemann Sum Integral Sensor (left integration). The Value is sent via MQTT every 30 seconds.

I used the Energy helper as a device for the energy dashboard.

When I look into the sensor, the small rendered graph looks like so:

where the full size graph looks a bit weird:

The spikes happen every night at about 2:00 am and they add up over the days (which make sense for a sum integration). When I adjust the scale to show a time in between those events, the large graph also looks okay:

When I zoom in to the actual event, the graph looks broken:

The Power graph in that time looks like that:

So what happens at about 2:00am is that an automatic backup for my server starts, which will issue a systemctl stop for the docker daemon service on that host, which will cause the container to be stopped and started again when the backup finished.

So it looks like the integration helper does not like that. However, the graph in the small widget is fine after all.

Any ideas how to make the large graph also smoothes those spikes out?

What version of Home Assistant Core has the issue?

core-2024.2.5

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Tasmota, Riemann Sum Integral

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant[bot]]

Hey there @dgomes, mind taking a look at this issue as it has been labeled with an integration (integration) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of `integration` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign integration` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

integration documentation integration source _{^{(message by IssueLinks)}}

[issue-triage-workflows[bot]]

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.

[darkmattercoder]

The issue persists with 2024.5. Do not close!

[dgomes]

Please check in 2024.06 as soon as it gets released

[darkmattercoder]

Checked with 2024.06

The issue still persists.

[dgomes]

Probably next release, https://github.com/home-assistant/core/pull/110685 should help you