awning: current-sensing auto-retract + true CLOSED state; drop useless OPEN jog

Motion is hold-to-run (one authed opcode runs the motor ~1s). Reproduce the OEM
movement session -- auth once, then stream the opcode @110ms + a page-44
keepalive @510ms -- to sustain continuous retract, and watch node-75 page-3
motor current at 20Hz to stop at the fully-closed stall (~4200 vs ~<1550
running), then mark the cover CLOSED. Backstops: 70s timeout, motion-lost
detector, hold-to-run stop-on-silence. Proven live at the camper 2026-07-01.

- esphome: awning_auto_retract script + 100ms streamer interval + case-0x75
  stall gate + "Awning Motor Current" sensor. Cover CLOSE=auto-retract,
  STOP=abort. Removed open_action (1s jog is useless, no safe timed auto-open).
- bridge: optimistic:true keeps the home HA cover assumed-state so retract is
  always pressable (was greyed when closed); payload_open:null drops OPEN on the
  home (primary) dashboard. Also synced the 6h->15min discovery-cadence drift.
- captures + README: full-retract stall profile and the live auto-retract test.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

canbus/README.md

@@ -169,15 +169,37 @@ python3 idscan_cmd.py F8 on      # node_hex  on|off ; needs can0 up
 
 Movement nodes (awning `75`, slides, jacks) use the **same** authentication —
 the app-driven awning commands in `captures/app-commands-*.log` show the identical
-page-42/43 exchange. Not yet operated this way; exercise a motor only while
-watching it.
+page-42/43 exchange.
+
+**Awning motion is HOLD-TO-RUN, and auto-retract is live (2026-07-01).** A single
+authenticated opcode runs the motor only ~1s (it's a "keep the button held"
+signal, not a latch). The OEM app sustains motion by **streaming after one auth**:
+opcode `03F2<node>02` every ~110ms **plus** a page-44 keepalive `03F0<node>44`
+payload `00 04` every ~510ms — **no per-command re-auth during the run** (a cold
+opcode with no session is still ignored; the auth just opens the motion session).
+Our ESPHome node reproduces this with its own controller identity (opcode
+`0006 75 02`, keepalive `0004 75 44`) — proven to sustain ~6.5s of continuous
+retract on 2026-07-01.
+
+The awning has no position feedback, but the **motor current** rides page-3 b2-3
+(BE, raw counts): ~<1550 running incl. inrush, tapering to ~350–500 near closed,
+then a sharp ramp to a **~4200 plateau at the fully-closed hard stop** (captures
+`awning-fullretract-2026-07-01_*.log`). The node's **auto-retract** (cover CLOSE)
+streams the retract, watches current at 20Hz, and cuts at `cur>2500` for 3 frames
+(~150ms) — firing ~0.3s into the stall ramp, before the motor sits hard-stalled —
+then marks the cover CLOSED (the one direction with a real end-stop). Backstops:
+70s timeout, motion-lost detector, and stop-streaming-stops-the-motor (hold-to-run
+fail-safe). OPEN stays a single ~1s jog (no safe end-stop for extend). See
+`esphome/onecontrol-canbus.yaml` (`awning_auto_retract` script + streamer
+`interval` + the case `0x75` stall gate).
 
 **Bottom line: read is fully open** (all sensors + states from broadcasts, no
 authentication) **and command is implemented and proven** (`ids_can_auth.py` +
 `idscan_cmd.py`). The CAN path can both sense and operate the system, so the
-Bluetooth integration is no longer needed for control. Next step: fold the
-challenge-response into the ESPHome node's `switch`/`light`/`cover` actions (the
-opcode just needs the page-42/43 exchange in front of it).
+Bluetooth integration is no longer needed for control. The challenge-response is
+folded into the ESPHome node's `switch`/`light`/`cover` actions (opcode preceded
+by the page-42/43 exchange), and the awning cover does authenticated streaming
+auto-retract — see the awning section above.
 
 Other app-session traffic (not control): `701` = controller heartbeat during a
 Bluetooth session; src `01` → node pages `30/31` = paged descriptor/table reads