7 Commits

Include renames

Author	SHA1	Message	Date
tliu93	f4cea3874b	test(energy-cost): pin local_now in future-window summarize test ... test_future_window_counts_0_days relied on the real wall-clock date and assumed 7/1→8/1 2026 was entirely in the future; once that range started elapsing the window counted fixed-fee days and the assertion failed. Pin local_now to June 25 2026 (as the sibling window tests already do) so the case stays deterministic.	2026-07-17 18:49:26 +02:00
tliu93	d3fc90b320	FUE-T08: defer daily fixed-fee/heffingskorting settlement to local 01:05 in summarize()	2026-06-26 11:44:34 +02:00
tliu93	f1e7ce3133	FUE-T01: count billing window start day in full for fixed-fee/credit accrual (symmetric with end day)	2026-06-25 18:33:42 +02:00
tliu93	17057ed41e	M7-T03: make billing engine meter-aware (no cross-meter delta, delta sanity guard, period.meter_id)	2026-06-25 17:01:54 +02:00
tliu93	8b91146c29	FU10: localize energy time math to server tz; accrue fixed/credit per elapsed local day ... - Store UTC, compute day boundaries in server local timezone (new app/services/timezone.py). - summarize: fixed fee / tax credit accrue only for elapsed whole local days, integrated across contract versions — no future-day inflation, no version-switch collapse. - MQTT import_cost_total / export_revenue_total getters delegate to summarize (no inline apportionment), anchored at the active contract's earliest version effective_from so the total sensors stay monotonic and never jump backward. - effective_from: naive datetimes interpreted as server-local wall-clock, then stored UTC. - frontend ContractForm sends local-midnight naive datetime (was UTC midnight). - get_costs_summary default window uses server-local "today".	2026-06-25 11:13:30 +02:00
tliu93	9d3e28a529	Billing fix: don't bill periods from stale/out-of-range DSMR readings ... Root cause (found in the live DB): register_at() returned the latest reading for any boundary beyond the DSMR data range (a future instant or a long gap), so future periods got start==end -> delta 0 and were written as degraded=False 'ok' rows with cost 0. recompute_range() over a future end then filled the whole month with such fake rows, which then occupied the slots so the per-minute tick (immutability guard skips non-degraded rows) never recomputed the real data. - register_at: ignore a reading older than one period (15min) before the boundary -> returns None -> period is marked degraded instead of a fake 0. - recompute_range: only process closed periods (t1 <= now); never future ones. - Tests cover staleness window, out-of-range -> degraded, recompute skips future, and a regression that normal closed periods are unaffected.	2026-06-24 12:44:05 +02:00
tliu93	d35ac7d752	M6-T07: add metering billing engine + period job + summary + recompute ... - app/services/energy_cost.py: register_at (register values at a UTC boundary), compute_period (register deltas x active-version strategy, snapshot price + contract_version_id, immutable unless overwrite), compute_closed_periods (bounded lookback), recompute_range (explicit overwrite), summarize (sum net + standing fees month/30 - heffingskorting year/365). - Missing tibber price -> skip; missing reading -> degraded (zeroed amounts, null version), consistently on both create and recompute paths. - main.py: 1-minute energy-cost job (existing jobs/MQTT untouched). Tests added.	2026-06-23 22:26:56 +02:00