DIGITAL STEALTH CARE · CHANGELOG

Digital Stealth Care, release by release.

Every release and feature, dated, newest first. The bugs, the incidents told in full and the lessons behind them are one filter away, in the state they are really in.

● bug states shown as they are, never rounded up

● releases, features and fixes on one timeline

How fixes are checked

By using the software. A fix is checked in daily use on the real hardware; if it doesn’t hold, the bug gets a new report rather than a quiet edit, so a relapse stays on the record. Every row is shown in the state it is in.

Changelog · every release and feature, dated · fixes one filter away

Releases, features and milestones show first. Switch on bugs, incidents and lessons with the filters to see the whole record: bugs are shown in the state they are in, and nothing here is rounded up.

loading entries

Below the timeline: the newest 60 entries as a plain list. Every entry and write-up also has a page of its own.

CHANGELOG · THE NEWEST 60, AS A PLAIN LIST

Newest first, for when the timeline above is not running. Use the timeline’s search and filters for everything else.

18 Sep 2026 · Milestone · CannaLib, DSC, Site · Released

Journey and log become one timeline

Write-ups are now journey entries. One vertical timeline, newest first, with a column per product; /log/ opens it filtered to write-ups.

DIGITAL STEALTH CARE · CHANGELOG

Digital Stealth Care, release by release.

CHANGELOG · THE NEWEST 60, AS A PLAIN LIST

Journey and log become one timeline

75 held entries published, details withheld

Copy pass; old DSC help retired

/dsc/ rebuilt as a product page

/dsc/supported/: the equipment directory

Firmware page listed bugs instead of releases

User guide re-verified for 9.0.0

55 bench logs from the last ten days

Release manifest and library hosting

DSC alpha sign-up; releases hosted here

The DSC user guide lives on the site

Version stamps follow the test kit

Root page “thereabouts” idle-probe reading has no independent staleness check

flash-fleet-remote.sh and bake-firmware.sh still use docker exec dsc-hub-esphome (container removed by deploy)

master does not typecheck — MediaStorageCard uses a badge tone that does not exist

Inspector ‘Limited history’ chip ignores the brain’s recorded:false – a series that has never been written is labelled as thin instead of ‘Not recorded by the b

Explicit “show/hide system rows” toggle on journal views

No lamp role for a plug — adopting the 4×8 light plug has nothing to bind to

Possible leftover “pots” language in CropScheduler copy (rendered on Climate)

Settings > General is prose; subtitle promises ‘kit language and operator notes’ that do not exist

The brain test suite reaches out to the live hub at 10.42.0.10

Probe N/P/K and *_raw history is unreachable: recorder writes pot metric ‘nitrogen’ / ‘moisture_pct_raw’, /history resolves ‘soil_nitrogen’ / ‘soil_moisture_raw

Formalize the snapshot-backfill admin endpoint, or retire it

Operator-chosen tent pressure: a slider for the target regime (positive / neutral / negative) and how strong the pressure difference should be, per tent or syst

Pot-moisture “dry” threshold line is a bare hardcoded constant with no live setting to bind to

History audit: 7-day charts collapsed to the newest ~25 h (list_history LIMIT 2000) — /history now buckets the whole window

An imported-but-unconfigured Tuya device reads OFFLINE, which looks like a network fault

Zigbee canopy and Tuya tank readings are never written to fleet_history by their lanes – they only reach history via the 60 s computed recorder (change or 5 min

Surface the live SPA bundle hash/version in Settings

VPD charts with history that read against correct VPD ranges (sleek): reference zones, time-in-zone, temperature × RH VPD map

The journey opens

Trend-chart threshold bands are inconsistently drawn – band prop only recolors the line, doesn’t show a visible band

History audit: recorded hub switches / setpoints / flags and the brain’s computed entities were unreachable or never persisted

AC / clone mister shown OUT (capacity offline) while inventory says in service: dash_computed reads the input_boolean compose helpers, not fleet inventory

Moisture rate was first-minus-last over 6 h, so a probe reinstall (air 1 % -> soil 68 %) read as +66 %/h ‘wetting’ and forced dryback to 0.00 % for six hours (‘

Visual “pending vs confirmed” indicator on EntityToggle

Chart timespan chips: add a gear beside the chips that lets the operator add/remove spans (1 m, 5 m, 15 m, 7 d…) instead of the fixed 1h/6h/24h/48h + Cycle/Ph

Live and Fleet primary nav tabs share the same accent color (–dsc-blue)

Light desk sunrise / sunset / min-dark-hours writes never reached the hub (stored as brain helpers)

DHT disagreement trips on a healthy grow: it compares tent, room and clone spans, which differ by design (lit tent +4 °C over a night room, domed clones +15 % R

Root probe cards show the same firmware flag twice: ‘SENSOR FAULT’ and ‘PROBE DARK’ are both !probe_online

Climate band gauges duplicated in full between Overview and Climate

Ingest orchestrator with adaptive cadence: persistent ESPHome subscriptions, change-driven records, and an ‘actively reading’ burst mode (1 s) for probes after

Card title register is inconsistent across pages (single words vs full sentences)

Air-path numbers imply critical over-pressure — the two allocation bases were being shown side by side

Clone dark-period violation has no debounce: one computed snapshot with the SF1000 on and the 2×4 window binary missing records a violation, a grow-log line and

Pot firmware ‘Modbus Probe Online’ stays false (and ‘Sensor Fault’ true) on a healthy probe: on_online only fires on the offline->online edge, so a probe that a

Dash (Legacy) is an un-retired debug dump duplicating Overview

Pot numeric values are re-recorded on every ~10 s poll although the probe only refreshes every 60 s – ~6 duplicate rows per reading per metric, while values tha

Inline fontSize numbers not routed through the new –dsc-fs-* type scale

Flow Sankey overflows its panel — right-hand node labels clipped off the card edge

Humidifier/heater ineffective alerts use the wrong band: they read RH/temperature targets from compose helpers the hub never writes, so they always fall back to

Every drawer/dialog form loses focus to the ✕ after each keystroke and scrolls the page: SlideDrawer and DecisionLayer focus traps re-run on every parent render

Compact DashBandsGrid on Overview to a per-zone in-band/drifting/alert row

Session watchdog restarts a seat repeatedly while the device is rebooting for an OTA (pot2 hit 6 restarts during its 8.2.0.0 flash) – looks_dead treats Reconnec

Kit update check always fails since the repo went private: GitHub releases lookup returns HTTP 404, so the brain can never say an update is available

Hub-entity writes take up to ~60s to reflect in /fleet; no pending indicator

Air Path map is unreadable — crossing edges, links drawn through node boxes, floating unattached labels

A dead or railed probe raises no alert: probe offline (pot1) and moisture railed to 0 % (pot2) only set binary_sensor.dsc_probe{n}_reading_dark, which is not in

Typed drafts wiped every 2 s in the seat drawer, the Assignment rows and the journal entry editor: draft-reset effects depended on a prop OBJECT that the fleet