v0.12.0b2 - Historical usage import fixes
Pre-release
Pre-release
Follow-up beta on top of v0.12.0b1. Fixes cases where the historical import returned only data from the current active contract instead of your full usage history.
Fixed
- Historical usage now goes back across your previous contracts. If your BAN went through renewals or supplier switches, the import previously stopped at your current contract's start date. It now walks back to the earliest contract on that BAN.
- Real historical data was being silently dropped. ENGIE marks rows from expired contracts as "partial" even though the values are final, so the converter was filtering them out. The filter now only rejects rows whose timestamp is still in the future (current in-progress hour or projected future hours).
Changed
- The "energy type" and "include costs" fields in the two actions no longer show an extra opt-in checkbox in the UI. Energy type must have at least one selection anyway, and costs is already a plain on/off toggle. Same defaults (all three energy types pre-selected, costs off).
Behind the scenes
- Added debug logging across the import path so we can diagnose future weirdness (which BAN got targeted, which start date was picked and why, how many rows each chunk returned).
Notes for beta testers
- If you already imported on
v0.12.0b1, run Clear historical usage statistics for the affected business agreement and then Import historical usage again to pull the full history. - Existing installs upgrade in place. No re-authentication needed.
- Bug reports welcome on GitHub Issues.