0.1.9

0.1.9

Bug Fix

Fix — energy spike on current day caused by partial-day double-counting

When a fetch chunk includes both the last complete day AND partial current-day data (e.g. April 17 + April 18 06:00), last_sums was set to the sum of the very last entry (April 18 06:00). The next cycle then re-fetched April 18 from local midnight (= April 17 22:00 UTC) and used that inflated sum as its running offset, double-counting the 22:00–06:00 UTC slots → spike on April 18.

Fix: last_sums is now set to the sum at the last entry of the last complete day (e.g. April 17 21:00 UTC), so the next cycle re-imports the partial slots with the correct base offset.

If you see a spike on the current day: update to 0.1.9 and reload the integration once — HA will overwrite the incorrect entries automatically.