4 Commits

Include renames

Author	SHA1	Message	Date
glenn schrooyenandClaude	c70eeb6916	SAFETY-129 round 3: the real reason for the 16 s limit, a slow-start check, the row's tail ... Co-Authored-By: Claude <noreply@anthropic.com>	2026-11-07 00:12:33 +01:00
glenn schrooyenandClaude	5b6cb0bf08	SAFETY-129: find readings 30 s late within about 90 s at a 5 s meter ... The meter's delay fit needed 16 new values in 60 s, so at the owner's 5 s P1 only the batteries' fit ran and 30 s late was found after about 3 minutes (export to -420 W). A meter that slow is now also fitted over 120 s; it calls a delay late only over 16 s, on two fits in a row, with the same corroboration as before, and never ends a verdict, so a slow battery (R2-1) runs as before. Found about 90 s after the start, export above -200 W. 10 s late at a 5 s meter is not found (nothing swings; it cannot be told from a 10 s battery). Co-Authored-By: Claude <noreply@anthropic.com>	2026-11-06 19:38:21 +01:00
glenn schrooyenandClaude	d3f4f9f48b	SAFETY-128 round 2: find late readings from the batteries, not the meter alone ... Review B1: the meter fit took repeating house loads (ovens, a heat pump) for late readings on healthy 1-2 s sites, about 9 % of the recorded house. B2: at a 5 s meter it never ran. M1: no hysteresis. M2: an unbounded check. lateness.Delay now fits how long each battery's reading takes to show its own request, which the house does not move, from the 1 s reads (read_inputs -> Answer.watch). The meter fit stays for speed at 1-3 s meters, but counts only when an ask was slow to start and no battery fit said on time. Late from 9.5 s after 2 fits, on time under 6.5 s, dropped after 120 s without a fit. Fits are bounded (a few ms). Readings on time: no verdict in any reviewer scenario (22 shapes at 1/2/5 s meters, 7 harm runs) nor in 2 days of the recorded house at 1, 2 and 5 s ticks; digests equal to 77fe31b. Late: found 36-68 s after the start at 1-2 s, about 3 min at 5 s. The row gives the batteries' delay, or no figure while only the meter has shown it. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bdqr7PiaHcBnzPituu2yTC	2026-11-02 04:32:04 +01:00
glenn schrooyenandClaude	09e1fbb898	SAFETY-128: control does not act on late Home Assistant readings ... Readings that Home Assistant delivers late but still changing passed every staleness gate, so the loop corrected again each cycle an error its last command had already fixed (10 s late: the give run swung and exported to -1.9 kW), and the peak guard pushed to the inverter limit on the same late figures (OPT-34 F-2). app/lateness.py fits how long after a power request the meter shows it. Over 8 s the readings are late: a request the battery reading has not answered holds the loop (it may not lead the reading by more than 100 W) and caps the peak guard at what stands; unanswered for 23 s it holds, then 0 W after stale_input_s. An amber row and one log line per episode say so. With readings on time nothing changes (digests equal). DECISIONS/SAFETY-128-late-readings.md; test_safety128.py. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Bdqr7PiaHcBnzPituu2yTC	2026-11-01 23:45:03 +01:00