Skip to content

Rescue: keep reconnecting until the reset goes out - #106

Merged
freethinkel merged 2 commits into
mainfrom
rescue-retry
Nov 20, 2026
Merged

freethinkel merged 2 commits into
mainfrom
rescue-retry

Conversation

@freethinkel

Copy link
Copy Markdown
Collaborator

Why

Watch 3 Pro owners stuck after a heavy face (see #104) try /rescue, but it makes one attempt: pick, connect, reset. A wedged watch is reachable only now and then. A real stuck watch stayed listed in Chrome's picker for ~27 s and took 4.1 s to connect plus 0.9 s for service discovery. In the cmf-watch-utils emulator, the boot loop keeps Bluetooth up for only ~0.1–0.3 s before each crash.

What

  • rescue.model: after the one pick, it keeps reconnecting to the same watch through Watch.connect({ rescue: true, again: true }), with no picker, every 300 ms until the factory reset goes out. Stop ends the loop without an error. Closing the picker is not retried.
  • ble.ts: connect({ again }) reuses the picked device; hasSavedKey().
  • /rescue warns when this browser holds no auth key. Without one, connecting means pairing, which needs a tap the stuck watch can't take. The new strings are in all five languages.

Verification

  • tests/rescue-retry.browser.test.ts: two drops then a reset on the third try, picked once; Stop; a closed picker. The unit tests (22 files) and the browser tests (55 files) pass. check, lint and format are clean.
  • Not verified on a stuck watch. The retry loop helps only where the watch is reachable at all and this browser has its key.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CQSU8M5ytC26gZ1F3vdZ7B

freethinkel and others added 2 commits November 20, 2026 18:20
A wedged Watch 3 Pro is reachable only now and then: a stuck watch in the
field stayed connectable for seconds, the emulator's boot loop for a fraction
of one. The rescue page now picks the watch once and keeps reconnecting to it
(no picker) until the factory reset is sent or the user presses Stop; a
closed picker still ends it. It also warns when the browser holds no auth
key, since pairing needs a tap the stuck watch can't take.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CQSU8M5ytC26gZ1F3vdZ7B
…than a reset

The rescue page can now delete every face this browser flashed (the upload
handshake with new_wf_id 0, a minimal face as filler) instead of wiping the
watch; it retries like the reset does. Unconfirmed on a stuck watch, so the
factory reset stays next to it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CQSU8M5ytC26gZ1F3vdZ7B
@freethinkel
freethinkel merged commit 446dc68 into main Nov 20, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant