From 6fdd8f6ed49f99f8b298a3c2c4881b4ace14ff33 Mon Sep 17 00:00:00 2001
From: Home Assistant Version Control <havc@local>
Date: Fri, 7 Aug 2026 02:15:50 +0000
Subject: [PATCH] opencode/decisions.yaml

---
 opencode/decisions.yaml | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/opencode/decisions.yaml b/opencode/decisions.yaml
index c782c94..04bc083 100644
--- a/opencode/decisions.yaml
+++ b/opencode/decisions.yaml
@@ -50,4 +50,26 @@ notes:
     integrations:
       - octoprint
       - mqtt
+    status: superseded
+    superseded_by: 2026-08-06-3d-printer-automation-runs-on-helper
+  - id: 2026-08-06-3d-printer-automation-runs-on-helper
+    date: 2026-08-06
+    title: 3D printer automation runs on helper, not MQTT
+    decision: "When the OctoPrint HA plugin toggles input_boolean.3d_printer_running: ON ->
+      playroom + bedroom lamps on, basement 22C heat; OFF -> playroom light off after 10
+      min, thermostat untouched. Mode restart cancels pending off on a new print. Old MQTT
+      automation stays disabled."
+    rationale: Built-in OctoPrint integration is broken here (AssertionError device_id is not
+      None; no printer entities). The OctoMQTT event trigger was replaced by a
+      helper-based design so OctoPrint can toggle a HA entity directly (plugin pointed at
+      the helper) and print-end handling (delayed light off) becomes possible. Built,
+      tested, and working 2026-08-06.
+    entities:
+      - input_boolean.3d_printer_running
+      - light.playroom_light
+      - light.bedroom_lamp
+      - climate.basement
+    integrations:
+      - octoprint
+      - mqtt
     status: active