Good to know after updating
Most installations need to do nothing. A few things behave differently:
- Missing readings stay missing. When a modem does not report power, SNR or error counters, DOCSight shows a dash instead of 0. MQTT and Home Assistant sensors receive "unknown", the API returns
nulland Prometheus skips the sample. History saved as 0 dBmV or 0 dB for such polls is corrected once on the first start. (#1150, #1198, #1217) - API changes for integrations. New TC4400 snapshots use
corrErrors/nonCorrErrorsinraw_datainstead ofcorrError/nonCorrError, and Vodafone Station and Ultra Hub 7 no longer carry placeholder counters orlatencykeys there (#1227). New fields:ds_uncorrectable_channelsin trends, correlation, comparison and snapshot answers (#1231),latency_countandp95_latency_msin the Connection Monitor summary (#1243) andresult_idfromPOST /api/speedtest/run(#1181). Database errors answer503with a short JSON error, and a JSON body that is not an object gets400instead of500(#1184, #1191, #1214). - On/off values in
config.jsonand environment variables are read by their meaning:on,true,yesand1are on, everything else is off, spaces are ignored. A hand-written"off"or"false"could count as on before, so check hand-edited values such asmetrics_require_tokenordemo_mode. (#1175) - Community modules need a sign-in for their routes unless they declare
require_auth, and can no longer register request hooks. The published modules are not affected. (#1148) - Connection tests in Settings ask for the password again after you change the modem, MQTT or Speedtest Tracker address. (#1148)
- BNetzA: a CSV measurement imported earlier keeps a false 0 for a direction that was not measured; delete it and import the CSV again to fix it. Protocols imported from now on can get different verdicts than before. (#1201, #1208)
- Demo: the one-click demo opens the dashboard within a few seconds and fills it by itself; preparing the demo data takes about half the time. (#1235, #1229)
Special thanks
- @Hitman4 for reporting that the container did not start on Ubuntu 26.04 and for testing the fix (#1144).
- @double-sudo for reporting that running speed tests were stored as failed (#1173).
Security and privacy
- Error messages no longer show internal details and point to the DOCSight log instead; Speedtest Tracker errors never show the token, also in older Smart Capture entries.
/setuprequires a sign-in once an admin password exists, and an API token revoked during a restore stays revoked. (#1148) - Logs mask credentials and query strings in web addresses, and modem logins, driver errors and BQM errors no longer write session IDs, cookies, tokens or share links. (#1163, #1190, #1194, #1219, #1221)
- Backups with a broken checksum are rejected, failed restores leave no temporary files, and backups taken in demo mode no longer contain demo weather or segment data. (#1223)
Fixes
Docker and startup
- DOCSight starts again on Ubuntu 26.04 hosts with a current kernel; the image now uses
setprivinstead ofgosu. (#1195) - Stopping the container is quick and clean, with exit code 0 instead of a kill after 10 seconds, and without "Bad file descriptor" tracebacks. (#1209, #1149)
- A
disabled_moduleslist no longer stops startup, and failed cleanups no longer stop polling. (#1191, #1174, #1180)
Modems and signal data
- No more false power, SNR or error events after a poll without channel values or when the reporting channels change, and vanished readings no longer count as a recovery. (#1150, #1222, #1217)
- Unreadable values on Arris, SURFboard, CM3000, CM3500, TC4400, Sagemcom, CGM4981, FRITZ!Box, Ultra Hub 7, Vodafone Station and Connect Box show as unavailable instead of 0, and the channel is rated on its other readings. Odd values from Vodafone Station, Ultra Hub 7 and CGM4981, or an oversized frequency or channel ID, no longer fail the whole poll or break the channel history. (#1198, #1217, #1200)
- TC4400 modems now show their error counters everywhere, and the SB6190 shows its hardware version. (#1227, #1192)
- Skipped rows, unreadable values, device info failures and a driver that cannot be loaded are logged with the model and the problem. (#1211, #1186, #1194, #1179)
- Threshold modules with invalid values are rejected at load, and range bars use the analyzer's limits when a profile leaves out a band. (#1158, #1160)
Dashboard and charts
- Trends, comparison and Correlation no longer show new errors when the channels reporting a counter change; the snapshot panel says "not comparable" instead. (#1231)
- Zoomed charts match the inline charts and follow the window width, and BQM gets the Connection Monitor drag zoom with a "Reset Zoom" button. (#1236, #1245)
- Signal Trends shows hourly temperatures for 2 to 7 days and the temperature overlay in older Safari. (#1241)
- Modulation views use the detected time zone when none is set, load older history with mixed channel IDs and label Upstream correctly. (#1232, #1248)
- Line status shows "Target ≥ 32QAM" for a degraded DOCSIS 3.1 SC-QAM upstream, Correlation shows translated event names, and the Connection Monitor card on Home opens once per click and fills without a reload. (#1153, #1220, #1239)
Speedtest
- A test still running during a sync is no longer stored as failed with 0 Mbit/s, and older such rows are corrected automatically. (#1177, #1181)
- Opening the Speedtest page during a sync, or a Speedtest Tracker reply without results, no longer clears the local history. (#1181, #1177)
- Run Speedtest shows the result of the test it started and also counts 200, 202 and 204 answers as started, and Smart Capture skips a new test when Speedtest Tracker already has a recent one. (#1181, #1226, #1184)
Connection Monitor
- Failed requests show "Could not load the data" with "Try again" instead of old or empty views, also for traceroutes, pinned days and the target list in Settings. (#1224)
- Pinned days follow the configured time zone, the traceroute banner and Trigger column are translated, and p95 latency is calculated the same way everywhere. (#1203, #1218, #1243)
BQM and BNetzA
- BQM imports CSV files with a UTF-8 BOM, "Yesterday" follows the configured time zone, a range delete removes exactly the shown range, and a day whose graph could not be saved is fetched again. (#1202, #1210, #1215, #1219)
- An unmeasured BNetzA direction shows
-instead of 0 Mbit/s everywhere, protocol verdicts are read from their result sections, and an unreadable import marker no longer re-imports the watched folder. (#1201, #1208, #1179)
Journal and reports
- Journal search no longer garbles entries with
&,<or>, CSV imports handle a UTF-8 BOM and Windows-1252 files, and failed case assignments show an error instead of a false success. (#1205, #1207, #1230) - Cases without an end date run until today in the configured time zone, and demo sample cases no longer take over your own entries. (#1214, #1235)
- Complaint letters use placeholders and verdict labels in the letter's language, and the PDF report no longer fails on older snapshots that stored a counter as text. (#1199, #1208, #1227)
Settings and more
- The notification test shows the real webhook error, the MQTT test waits for the broker login, and "Insecure TLS" works with self-signed certificates. (#1162, #1148)
- In Settings, changing the modem driver also replaces another driver's default address, and an unusable stored password hash gives "Invalid password" instead of a server error. (#1238, #1176)
- The weather overlay retries its 90-day history after a failed first download. (#1206)
- More messages follow the selected language, and a language that only a community module provides falls back to English instead of empty labels. (#1213, #1247)
- Windows app: the tray shows the DOCSight logo, a second start waits correctly when another program uses the port, quitting is faster, and backups record the real version instead of
dev. (#1165, #1164, #1156, #1178)
Under the hood
- A large cleanup of the analyzer, drivers, storage, charts, journal, settings and Windows launcher replaces copied code with shared helpers and removes dead code, including 196 unused translation keys. Apart from the fixes above, data, API and interface stay the same.
- Code outside DOCSight that imports internal driver or module loader names needs the new import paths. (#1171, #1192)
- Tests and CI are leaner and stricter, with fewer duplicated tests and checks for unused or empty translations.
Container images
ghcr.io/itsdnns/docsight:v2026-11-22.1ghcr.io/itsdnns/docsight:stableghcr.io/itsdnns/docsight:latest
Use stable to follow releases only; latest also follows changes on main.
Support the project
If DOCSight helps you understand and document your connection, you can support its continued development through Ko-fi, GitHub Sponsors or PayPal.
Full diff: v2026-11-18.1...v2026-11-22.1