Verification checklist — DYMO LetraTag

Hardware verification runs through the harness app. It pairs the printer over BLE, prints a diagnostic, captures the advertising-data snapshot + RX-notification result code, and submits a hardware report issue — no manual transcription, no scattered captures.

Browser harness

Open https://thermal-label.github.io/harness/letratag/ in a Chromium-class browser, click Pair, select your LetraTag, and follow the prompts. The harness pairs over BLE, prints the diagnostic, captures the advertising-data snapshot + RX-notification result, and prefills a GitHub issue when you're done.

Fallback

Hand-rolled report? Open the hardware verification issue template directly.

Driver-specific notes for the verifier

• Advertised name varies. Current firmware revisions advertise as Letratag <12-hex-MAC-suffix>; older units may still advertise DYMO LT-200B. If your unit doesn't show up in the picker, flag the observed name in the report — the driver filters by the current prefix plus the canonical service UUID.
• Lid + battery prerequisites. The printer silently no-ops jobs if the lid is open or batteries are low. Verify the lid latches fully and the battery indicator on the chassis shows green before attributing a failed print to the driver.
• Tiny-print alternation. If you're testing with very short content (single character / icon), the firmware can silently reject every other job. The encoder appends 6 mm of trailing feed by default to clear it. If you see strict every-other-print failures with forcedTrailingFeedMm: 0, that's the documented quirk, not a new defect — see the Trailing feed section.