4 Commits

Include renames

Author	SHA1	Message	Date
Claude dev agent	6dab4ec16b	OPT-11 P3, owner option A: selling off, Leftover solar takes solar only ... Owner decision 2026-09-29. Selling is off until it can be judged on the price the grid pays: packmode.SELLING_ENABLED = False makes read() answer sell=False whatever the store holds, pack_sell is refused ("Selling is off for now."), and the page has no selling switch; the sell code stays. Until the P4 forecast, only Cheap hours only charges from the grid (packmode.GRID_CHARGE_MODES); Leftover solar holds and gives in the expensive runs. Help, Today and plan lines, DOCS and DECISIONS follow. Replay, 16 days: Solar first + Leftover solar 19.44 EUR net (P2 19.33). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 10:42:58 +02:00
Claude dev agent	902524ae5e	OPT-11 P3: price runs per battery ... Cheap and expensive hours as runs of consecutive firm price slots (priceruns.py); each battery's role per tick from its mode (modetrade.py): grid charging for Leftover solar / Cheap hours only, never Solar first; holding for the expensive runs; selling per battery (pack_sell) above the spread and the floor. The site trade is sized inside the modes (loop bound) and the peak guard's headroom; a run edge reseeds the loop. Cheap hours only and selling are enabled on the Batteries screen and in the HA select (appended). The site Why row no longer says "held back" when the peak limit pushes power up (F2). Modes off: byte-identical to 7a00f12 on the trade path. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-29 02:37:44 +02:00
adminandClaude Opus 5.5	b310282729	OPT-11 P2: HA entities for battery modes ... Each battery gets an MQTT-discovered Mode select and Use switch, only while battery_modes_enabled is true. Commands go through handle_action(), the /action path; refusals are logged once. Retained commands are never applied. Turning modes off removes exactly the configs announced (kept in the store). With modes off the announcement is byte-identical to ed739d4. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-28 23:12:04 +02:00
Claude dev agent	d69fd8fbfd	OPT-11 P1: per-battery mode limits, on/off, solar order ... A battery's mode is a soft unit limit (source `mode`, P_MODE 35) kept apart from the hard limits in pre_resolve(). The allocator applies it only while the site target is decided at or below 35 (new Resolution.deciding_priority), so the peak floor releases it and a mode `hi` never meets the site `lo`. At N=1 resolve() applies the same rule to the site target after stage 2. A mode range without 0 W is dropped as a software fault, so REFUSE_SIGN stays unreachable from a mode. compute() gets the loop bound (sum over live units of hard limits with modes applied), so the loop never asks for watts no battery may give and the saturation freeze never parks on them. While charging, Leftover solar weighs 0 so Solar first fills first. Store keys pack_use and pack_mode per battery, set by two new /action values; Off stops and skips maintenance with a log line. Minimal Batteries cards (EN/NL). Off by default (battery_modes_enabled); off, commands are byte-identical to a5dddad at N=1 and N=2 (test_modes.py part 1). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-28 18:51:29 +02:00