FOUND 2026-09-10 while investigating the light catch-up ask — same problem class, different door. arm_full_auto sets id(manual_light_hold) = false; // schedule owns the light now. Leaving Manual takeover does the same (dsc-hub-v4_0.yaml ~1679: “Leaving manual releases the light hold too”). So turning Full Auto ON while a manual light hold is active hands the light back to the schedule. If a catch-up is running at that moment (want_on true), the lamp is driven to target brightness immediately — exactly the surprise reported for releasing the hold directly. The confirm dialog makes it worse by pointing elsewhere: ClimatePage.tsx:435 reads “Full Auto ON hands fans and appliance demand back to the brain. OFF freezes them at their current state…” — no mention of the light at all. An operator reading that dialog has no reason to expect the lamp to come on. FIX: the Full Auto ON and Manual-takeover-OFF confirm bodies must state that the manual light hold is released, and — when catch-up is active — carry the same warning built for the direct hold release (frontend/src/lib/lightCatchup.ts holdReleaseWarning).
Journey event · 14 Sep 2026
Full Auto ON silently releases the manual light hold — the confirm dialog only mentions fans and appliances
FOUND 2026-09-10 while investigating the light catch-up ask — same problem class, different door. arm_full_auto sets id(manual_light_hold) = false; // schedule owns the light now.
● state copied from the tracker, never improved
● event date 2026-09-14
| Event date | 2026-09-14 |
| Version found | |
| Version fixed | |
| Expected kit firmware | |
| Release file | |
| SHA-256 | |
| Served count | |
| Source | https://app.notion.com/3d62b4cda37081bf8bdafac01fb7de4a |
Empty rows are honest
A blank cell means the tracker has no value for it. Nothing on this page is filled in to look complete.
