WHAT: The reading-based dark timer (built this cycle) shows ‘DARK 24H 47M’ on the Runtz Punch probe – a live flowering plant with no soil data for over a day – but this only renders as a chip; no alert fires. The Alerts catalogue has ‘Root-zone probes’ (a probe the HEAT MAT relies on is missing) but nothing for ‘a plant’s probe has been dark > N h’. WHY: a live plant losing its probe for 24h+ is exactly what an operator should be told about; the timer already computes dark_for_s, so the signal exists. HOW: add a catalogue alert ‘Probe dark’ keyed off binary_sensor.dsc_probe
Journey event · 14 Sep 2026
Extension: turn the reading-based ‘probe dark’ timer into an actual alert (probe dark > N h) – Runtz Punch probe has been DARK 24h+ on a live D62 flowering plan
WHAT: The reading-based dark timer (built this cycle) shows 'DARK 24H 47M' on the Runtz Punch probe - a live flowering plant with no soil data for over a day - but this only render
● state copied from the tracker, never improved
● event date 2026-09-14
| Event date | 2026-09-14 |
| Version found | |
| Version fixed | |
| Expected kit firmware | |
| Release file | |
| SHA-256 | |
| Served count | |
| Source | https://app.notion.com/3d62b4cda370815dba82e8f895a1d9b2 |
All events · DSC · CannaLib · Site · Firmware releases
Empty rows are honest
A blank cell means the tracker has no value for it. Nothing on this page is filled in to look complete.
