4 Commits

Include renames

Author	SHA1	Message	Date
adminandClaude Opus 5.5	c664e38ef4	OPT-11 P2 review: refusals stay counted, removals survive a start with no broker ... - A refusal past the log-once set or the 32 cap is counted in the log at 1, 10, 100 and so on, so a repeated attack stays visible. - The logged topic is printable only (no forged log lines). - mode_announcement(): the start-up store logic, now tested with a real Store. A removed config topic stays stored, so a start with no broker cannot forget it (rename case tested). - A test ties each HA mode option to the page's English name. - packmode.enabled() is tested for "true", 1 and "false". - Retained-command text, DOCS and DECISIONS updated to match. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-28 23:58:34 +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
glenn schrooyenandClaude Opus 5.5	ffc9a4d721	OPT-11 P1 review: a mode never beats the peak floor; SAFETY-03 kept at the rail ... - arbiter: a mode now gives way only as far as a site limit above P_MODE needs (_unit_modes at N>1, _site_mode at N=1). Before, the modes were released only when the peak floor bound S, so a trade won above the floor kept them and placed less than the floor (an Off battery at N=1 went to 0 W under a 2000 W floor), and a capped grid charge released an Off battery. While released, held batteries weigh 0 and carry only the shortfall. - control: a side of the loop bound that reaches the rail is left to the rail, so SAFETY-03's i_clamped still fires with every battery on. - opt11_identity: add maintenance scenarios and a 6000-case arbiter digest (peak floor, trades, maintenance, refusals); a5dddad digests pinned. - tests: test_arbiter part 11, test_control (g), test_modes (0/1 refused, loop bound counts live units only). DOCS and DECISIONS say the new rule. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UBtqPrG1mDLXzTEBnhEkkV	2026-09-28 19:41:36 +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