Outage log with detected candidates and coverage assessment #47
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add an outage history to the Backup tab: manual entries (start, duration, notes) plus auto-suggested candidates from usage-gap detection (
parseEmporiaalready computes gaps; mains≈0 stretches are additional candidates). For each outage, run the existing outage engine against the actual pre-outage battery state assumption to report coverage ("fully covered" / "would have depleted at hour N"). Summarize: outages/year, hours protected, longest covered. Store as a home-scoped resource (new table via 007_ migration) so it shares between household members.Rationale: the stated primary goal is backup power, but the app only models hypothetical outages. Once the system is installed, the history — "has this system done its job?" — is the interesting part, and the data to answer it is already imported.
Acceptance criteria
Relations: relates to #11, #45 (realized-savings ledger)
(Audit finding F-28, 2026-07-16 — feature, ranked #3)