[BUG]: hourly/daily EnergyLogs are not continuous but show steps

[bouwew]

Describe the bug.

Recent energy log graphs look like this:

What version of Plugwise Beta are you using?

v0.55.4

What was the last working version of Plugwise Beta (or Core if not using beta before)?

No response

What version of Home Assistant Core are you using?

core-latest

What type of installation are you running?

Home Assistant Supervised

How did you install plugwise-beta?

HACS

What kind of Plugwise device is having issues?

USB: Stick

What firmware version is your Plugwise product at?

2011-06-27 08:43:39+00:00

Logging

Every 4 hrs, when the energy logs from the current log address are requested and the slots all return None, the debug-log shows this:

2025-07-19 12:41:54.738 DEBUG (MainThread) [plugwise_usb.nodes.circle] EnergyLogs data from 000D6F00029C32C7, address=1483
2025-07-19 12:41:54.738 DEBUG (MainThread) [plugwise_usb.nodes.circle] In slot=4: pulses=None, timestamp=None
2025-07-19 12:41:54.738 DEBUG (MainThread) [plugwise_usb.nodes.circle] In slot=3: pulses=None, timestamp=None
2025-07-19 12:41:54.738 DEBUG (MainThread) [plugwise_usb.nodes.circle] In slot=2: pulses=None, timestamp=None
2025-07-19 12:41:54.738 DEBUG (MainThread) [plugwise_usb.nodes.circle] In slot=1: pulses=None, timestamp=None
...
2025-07-19 12:41:54.739 DEBUG (MainThread) [plugwise_usb.nodes.circle] async_energy_update | 000D6F00029C32C7 | Log rollover | energy_log_update failed
2025-07-19 12:41:54.739 DEBUG (MainThread) [plugwise_usb.nodes.circle] async_get_state 000D6F00029C32C7 - energy: None

Diagnostics information

No response

Additional information

No response

[bouwew]

The main issue, the "steps", are caused by a change I made in PR 255, plugwise/python-plugwise-usb@3ba634b
Reverting this change, and adding an alternative implementation to "repair" the intended functionality, solves the issue.

The smaller issue of the short dips still exists. This is only an issue at low power consumption. At higher consumption the dips are less to not visible.

This smaller issue is caused by the fact that after the hourly pulses reset happens, it takes a short time until self.logs is updated, based on which log_pulses is calculated.
A solution would be to not publish energy-log updates after a pulses reset until self.logs has been updated.

[bouwew]

Solved in v0.55.5