4 Commits

Include renames

Author	SHA1	Message	Date
admin	13504b90de	Bench: plugcut.py — a real power cut on the HP with three ways back on; the night's round table written before round 1	2026-10-14 00:24:18 +02:00
admin	95d293b911	Bench: --plug hp — the HP t740 (demo-hp) is on a metered plug too ... plugmeter.py and plugswitch.py take --plug n100|hp (plug.json / plug-hp.json, outside the repo). The HP plug read 23-33 W while the box started its three guests.	2026-10-13 21:29:02 +02:00
admin	b4dcf4b373	Power-off spike (Part A) on the N100: plugswitch, wall-power figures, the hub's view ... plugswitch.py refuses 'off' unless 20 s of readings show the N100 is already off (standby + 1 W, no ping); 7 tests, each check red-proofed. By hand: guest shutdown 12 s, host off, 0.0 W; the hub stayed silent and 'ONLINE' for 18 min; plug off/on did not start the N100, its power button did (dashboard in 42 s). Wall figures into SIZING.md 4 and sizing.json power (8.5 / 20.7 / 0.0 W).	2026-10-13 19:15:08 +02:00
admin	6a1f715a87	Bench: plugmeter reads the N100's metered plug (tinytuya + Home Assistant from the catalog) ... scripts/bench/plugmeter.py prints watts/mA/V/kWh as CSV from the Tuya plug on the LAN (default) or from Home Assistant on demo-hp's guest. 10-minute side by side and a 3-minute control in documentation/audits/plugmeter-2026-10-13/: Home Assistant alone did not move for 3 minutes, so the LAN reader is the measurement source. No key, device id or token in the repo; secrets scan 0 hits with a positive control.	2026-10-13 17:07:26 +02:00