4 Commits

Include renames

Author	SHA1	Message	Date
glenn schrooyenandClaude	cdcbe7dbb6	OPT-27: the night plan keeps the last fresh solar forecast ... Forecast.Solar's sensors stop updating in the evening, so at night every such site had no forecast: the night cheap run needed 1.5x the cycle cost and Leftover solar planned nothing. One missed poll also dropped it at once. solarfc.Hold keeps the last fresh reading of each sensor, for the day it is for. A missing or stale sensor is covered by it for up to FRESH_S (a short outage), and from the end of the bell (20:00) until local midnight + 3 h however old. A tomorrow figure is tomorrow's until midnight and then today's; a today figure is only today's. Stored in the controller's store (solar_fc_hold), so an evening restart keeps it. The forecast line says 'Solar forecast read 17:05, used for tonight's plan.' (EN, NL). test_tariff24_weather.py runs with a hold that never covers: it tests what the plan does when the forecast IS lost. Co-Authored-By: Claude <noreply@anthropic.com>	2026-10-29 21:06:09 +01:00
glenn schrooyenandClaude Opus 5.5	9b1fa758ad	OPT-17: the solar forecast can come from several entities, summed ... New list options pv_forecast_entities and pv_forecast_tomorrow_entities (same shape as pv_entities); the single-entity keys are unchanged. - Each member is read in its own unit (Wh/kWh/MWh) in one gather and the day is summed. Hourly splits are merged when every member has one, else the total goes on the bell. - A member missing, unavailable, stale, non-energy or bad makes that day's forecast unusable (no partial sum). A caution row names it by position; the action log names the entity once per change. - Single key and list both set for one day: refused at start. - A one-member list behaves exactly like the single key (test_opt17.py); the single-key path is byte-identical to e36565f over 24 scenarios. - Supervisor shape measured: tools/supervisor_shape_probe.py section J. DECISIONS/OPT-17-several-forecast-entities.md has the rules. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bdqr7PiaHcBnzPituu2yTC	2026-10-11 02:55:58 +02:00
glenn schrooyenandClaude Opus 5.5	fbd884797d	OPT-11 P4 review: Cheap hours ignores the plan; midnight-stale forecast; stricter ids ... - Cheap hours only fills to the ceiling with or without a forecast, as the design (section 1) says. Skipping the sun's share cost 0.31 EUR on real 2026 prices (29.72 against P3's 29.41) and saved nothing on the P3 set. - A forecast reading from before local midnight is stale: until the integration refreshes, "left today" is still yesterday's 0 and "tomorrow" is really today. - Forecast entity ids must be sensor.[a-z0-9_]+ (they go into the /api/states/<id> path). - House profile: a stored day that is not a date, or is after today, is dropped instead of kept forever. - Text: the forecast line says "for the rest of today"; the learning line no longer promises "tomorrow" (a plan needs one full day). - Tests for four surviving review mutants (hour sample floor, the dear run after the cheap run, share by room, daytime use) and the fixes above. - Replay tool: `--fc zero` (a forecast of no sun). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 22:08:47 +02:00
Claude	eb10537aee	OPT-11 P4: solar forecast and day plan ... A Home Assistant solar forecast (Forecast.Solar, Solcast or Open-Meteo shapes) and the add-on's own hourly house use decide, before each cheap run, whether the sun will fill each battery before the expensive hours. Leftover solar then buys from the grid only the shortfall; Cheap hours only skips the part the sun covers; Solar first never grid-charges. No, stale or failed forecast: P3 option A exactly (12 digests pinned from 5a4cdc2). Replay (16 recorded days, forecast errors from Elia's day-ahead BE solar): year-earlier prices P4 19.15 vs P2 19.33 / option A 19.44 / old trade 18.14; real 2026 prices P4 29.19 vs 32.26 / 32.01 / 31.40 EUR net. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 19:29:32 +02:00