An all-new DOCSight

DOCSight has a completely new look and feel. Every screen was redesigned around the three things you come to DOCSight for: detect a problem, understand it, and prove it to your provider. This release brings a new navigation, a calmer Home, a new default theme and one consistent set of components across every view, from setup to settings. On top of that, new tools let you look back in time and collect evidence in cases.

Highlights

• A new home for your connection. Home now opens with what matters:
  • a clear connection status, and a line status that shows every channel at a glance
  • four key figures, findings and the latest events
  • one click from a channel straight into its last 24 hours (#906, #911, #915, #916)
• Navigation built around your tasks. A top bar with Overview, Signal, Connection, Events and Cases replaces the long sidebar, with a native-feeling bottom bar on phones. A command palette (Ctrl/⌘ + K) gets you anywhere from the keyboard. Existing links such as #trends or #channels keep working (#905, #1015).
• A fresh visual identity. The new default theme Graphite comes with self-hosted fonts and readable contrast in light and dark. Every view shares one polished set of components (buttons, fields, cards, tables, dialogs, badges and toasts), and every built-in theme follows it (#902, #903, #956, #959, #989, #992).
• Charts that tell the whole story.
  • target bands behind power and SNR
  • uncorrectable errors per interval
  • press and hold on phones to read values
  • gaps in the data marked instead of hidden
  • a click on any point opens the full snapshot of that moment (#1025, #1032, #1048, #1046)
• Look back in time. Step Trends, Correlation and the Connection Monitor back and forward by a whole window, share the exact window as a link, or simply swipe on your phone (#1049, #1051, #1052).
• Cases that build your evidence. Collect everything that proves a problem in one place:
  • case cards with their evidence state above the journal
  • guided steps from time window to evidence to export
  • events from the event log, a correlation range or a chart snapshot can be added to a case (#1035, #1037, #1028, #1029, #1046)
• Setup and settings, rethought. Setup asks for the connection type, offers a searchable modem list, finds the modem on the network on request, and explains failed connection tests. Settings are grouped by task, searchable, and saved with one save bar (#932, #933, #934, #966, #967, #973, #965).
• A stable image tag. ghcr.io/itsdnns/docsight:stable follows releases only, while latest keeps following main. This release is the first that sets stable (#904).

Compatibility notes

For community modules and themes:

• Empty-state macro: the empty_state template macro takes action_click / action_focus instead of action_onclick. Templates no longer use inline event handlers; actions are named with data-action attributes (#946).
• Shared components: buttons, fields, tables, dialogs and badges now come from one component set. .btn-accent, .btn-muted and .btn-small remain as aliases for module templates. CSS classes that no built-in screen uses any more were removed, for example .slider, .info-tip and .issue-badge. A community module that styled itself with them needs its own rules (#959, #1060).
• Themes: they use the canonical theme tokens. The deprecated aliases (--card-bg, --text-primary, --text-muted, --success, --warning, --danger) stay defined. Built-in themes load from a validated catalog (#954, #955).
• Translations: built-in module texts live in the module catalogs. Duplicates in the core catalogs were removed (#975–#979).

For API users, the changes are additive: /api/trends and /api/correlation accept an optional end (wall-clock time in the configured zone), and /api/snapshots/at returns the snapshot nearest to a time (#1049, #1046).

Special thanks

• @spxhub for the PYUR FAST3896-15 report and for confirming the new experimental driver on the device.
• @jsterling81 for reporting that community driver modules were rejected.
• @bnico99 for reporting that the Connection Monitor ignored the probe interval.
• @freakhauser for the FRITZ!Box upstream power report.
• @NonCertus for reporting visual bugs in the new event log.

Added

• Experimental PYUR FAST3896-15 driver (#866).
• Channels page with a channel status matrix, and a channel's last 24 hours one click from the Home line status (#907, #915, #1003).
• Command palette with keyboard shortcuts (#1015).
• Notice center for maintainer notices (#1013).
• Setup checklist on the overview until the optional sources are set up (#1011).
• Glossary as a reference page with an in-context help panel (#1008).
• Range chips in Before/After, and case or quick-range selection in the Evidence Journey (#1009, #921).
• Correlation lanes with their own axes, and the visible range handed to the Evidence Journey (#919, #920).
• Compact event log with collapsed repeats, an attention badge, and Undo instead of confirmations (#924, #1026, #1039).
• Connection Monitor targets as chips, with downloads in a menu, and BQM and SmokePing graphs in one frame that follows the time range (#1041, #1045).
• Target bands on power and SNR charts, uncorrectable errors per interval, and press-and-hold to read chart values on phones (#1025, #1031, #1032).
• View ranges and filters in the URL, so a view can be bookmarked and shared (#1000).
• All built-in modules translated into all 24 languages (#975–#979).

Fixed

• Restore community modem drivers whose manifests were rejected (#863).
• Apply the configured Connection Monitor probe interval to every target (#874).
• Explain the FRITZ!Box upstream power correction next to the value (#1040).
• Show a power or SNR value the modem does not report as unavailable instead of good (#1053).
• Redact modem connection test errors, and reject non-integer values for integer settings (#864, #876).
• Place chart data and format timestamps in the configured time zone and UI language (#885, #898, #901).
• Keep the Connection Monitor latency chart readable during spikes (#879).
• Line up event log rows and keep event messages in the UI language (#1039, #983).

Improved

• Accessibility: WCAG AA text contrast in built-in themes, a 12 px minimum text size, named controls, view changes announced to screen readers, and fixes from axe checks across the dashboard (#894, #895, #888, #970, #1018).
• Empty views explain why they are empty and what to do (#928, #931).
• The theme gallery flags themes with low text contrast, and the active theme applies everywhere, including setup and login (#897, #956, #994).
• The offline shell precaches its scripts and styles (#1020).

Maintenance

• Web Push is sent without pywebpush and its aiohttp tree: 9 fewer packages, and a 16 MB smaller image (#1058).
• No inline scripts, styles or event handlers in templates or script-built HTML, and 888 lines of unused CSS removed (#943, #945, #946, #947, #950, #951, #952, #953, #988, #1060).
• Faster and sturdier CI:
  • parallel Python tests and six browser shards
  • a CPU budget normalized for runner speed
  • cached browser installs
  • E2E tests fail on browser errors (#880, #1017, #1033, #1043, #1056)
• Security floors for urllib3, werkzeug and SoupSieve, and dependency updates (#927, #1001, #861, #882).

Container images

• ghcr.io/itsdnns/docsight:v2026-10-08.1
• ghcr.io/itsdnns/docsight:stable
• ghcr.io/itsdnns/docsight:latest

Support the project

If DOCSight helps you understand and document your connection, you can support its continued development through Ko-fi or GitHub Sponsors.

Full diff: v2026-09-16.1...v2026-10-08.1