Skip to content

v0.5.12

Released: 2026-04-29

UART configurability + connect-flow UX. Resolves #9.

  • UART data bits, stop bits, and parity settingslogscope.uart.dataBits (5/6/7/8), logscope.uart.stopBits (“1”/“1.5”/“2”), logscope.uart.parity (“none”/“odd”/“even”/“mark”/“space”). Defaults preserve 8N1 behavior, so existing users see no change. Plumbed through uart-serial.tsuart-helper.py → pyserial. Validated through the Change Settings flow; non-default frame configs are pyserial-validated but firmware-side hardware testing is an open invitation — if it’s broken on a specific platform, please file an issue.
  • Change Settings entries — Data Bits, Stop Bits, and Parity now appear alongside Baud Rate in the Change Settings menu when transport is UART, each showing the current value as the description. Sub-pickers mark the active value with (current).
  • Connect-wizard hint items — non-clickable advisory rows (lightbulb icon) at the end of the Transport, Parser, and Baud Rate pickers explain when to pick each option and where the advanced UART settings live. Marked with an internal _hint flag so accidentally clicking them keeps the wizard open instead of abandoning it.
  • Forget Device confirmation modal — clicking the trash icon now shows “Your parser, baud rate, watch patterns, and other settings are kept. Only the saved probe/port is cleared, so you’ll see the full Connect wizard next time” before clearing. Removes the “did I just lose my config?” anxiety.
  • Wireshark export prerequisites in description — the Wireshark format option now reads “HCI packets only — needs firmware with bt_monitor enabled (J-Link RTT)” so users self-select-out before clicking instead of getting a warning afterward.