Skip to content

Validate enclosure, BT Audio, and temperature-role transitions on hardware #70

Open

Description

@atomicdeploy

Original request

Relevant excerpt, lightly grammar-corrected for publication. Credentials, personal data, private paths, and unrelated transcript content are omitted.

Verify door and BT Audio transitions, smooth informational LED changes, keep warning states immediate, and validate the temperature roles on real hardware.

Source: session origin-main, authored turn 82.

Parent epic: #13

Requirement

Validate enclosure, BT Audio, and temperature-role transitions on hardware

Acceptance criteria

  • Toggle the reed and verify immediate open/close events, default-page return, light fade, RGB cue, and motion emergency behavior.
  • Toggle BT Audio and verify Off/On/Blink classification plus named TUI/IPC events.
  • Run controlled illumination on/off logging and prove tLED warms while tBT remains comparatively cool.
  • Record the final firmware identity and reset/error counters during the pass.
  • Request the prepared reed/BT/thermal actions through the WAIT/ringtone attention sequence and record each observation explicitly.

Current evidence and gaps

Ambient snapshots, ROM IDs, and basic event paths exist; controlled transitions and role proof remain unperformed.

Traceability

  • Canonical checklist section: Final hardware validation and handoff
  • Includes only curated, issue-relevant prompt excerpts; complete transcripts, credentials, secrets, and private paths remain unpublished.

Activity

  1. added
    🧪 testingAutomated, simulated, UX, or hardware verification
    🔍 needs-hardwareRequires physical-board observation or operation
    on Aug 1, 2026
  2. atomicdeploy commented on Aug 11, 2026

    @atomicdeploy
    OwnerAuthor

    Original request (lightly corrected): Learn the different BT Audio status indicator LED types/modes and make it active HIGH, unlike the active-LOW inputs.

    Hardware acceptance must now include: record the BT Audio indicator's observed modes and polarity, prove active-HIGH drive without disturbing input interpretation, and attach board-specific evidence. Pair this with the commissioning fallback where automatic identification is inconclusive.

  3. atomicdeploy commented on Aug 12, 2026

    @atomicdeploy
    OwnerAuthor

    2026-08-12 reconciliation: immediate door/thermal event check

    • ✅ Firmware/host protocol paths publish typed board events to UI, IPC, and scripting surfaces.
    • ⚠️ The connected board still needs a live proof that reed open/close reaches TUI, scripting, and IPC immediately, and that illumination raises T1 while T2 remains comparatively cool.
    • ⚠️ Capture final-image identity, timestamps, and before/after observations during this pass.
  4. atomicdeploy commented on Aug 13, 2026

    @atomicdeploy
    OwnerAuthor

    Final board 37D3BC5C currently reports door open, T1 32.54 C and T2 27.90 C, with the intended thermal separation. Typed events and WS/Socket.IO transport passed synthetic/protocol acceptance, but no physical close/reopen occurred during this checkpoint. Instant propagation to Web/TUI/CLI/script remains a human gate; keep this issue open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    🔍 needs-hardwareRequires physical-board observation or operation🧩 firmwareATmega328P firmware🧪 testingAutomated, simulated, UX, or hardware verification

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions