From b67df1099ef569c3585ef97c0bf8df6305555650 Mon Sep 17 00:00:00 2001
From: Home Assistant Version Control <havc@local>
Date: Sun, 30 Aug 2026 01:23:56 +0000
Subject: [PATCH] opencode/decisions.yaml

---
 opencode/decisions.yaml | 18 +++++++++++++++++-
 1 file changed, 17 insertions(+), 1 deletion(-)

diff --git a/opencode/decisions.yaml b/opencode/decisions.yaml
index b575fe24..dfa21666 100644
--- a/opencode/decisions.yaml
+++ b/opencode/decisions.yaml
@@ -541,7 +541,7 @@ notes:
       - matter
       - thread
     pin: true
-    status: active
+    status: superseded
   - id: 2026-08-24-octoprint-rest-sensors-stay-on-duckdns
     date: 2026-08-24
     title: OctoPrint REST sensors stay on DuckDNS URL — local-address fix deferred
@@ -663,3 +663,19 @@ notes:
       - tplink
     pin: true
     status: active
+  - id: 2026-08-29-new-kasa-devices-native-tplink-legacy
+    date: 2026-08-29
+    title: New Kasa devices → native tplink; legacy Homebridge-bridged Kasa untouched
+    decision: "Kasa has two paths: legacy devices bridged into HA via a Homebridge plugin
+      (leave untouched); new devices go on the native tplink integration going forward.
+      Homebridge add-on may be removed at some point, only after verifying nothing still
+      depends on it."
+    rationale: No working Kasa HACS integration existed when the legacy devices were set up,
+      so they were bridged via Homebridge. Both coexist now; do not migrate or disturb the
+      existing bridged entities, and if the Homebridge add-on is ever removed, first
+      confirm nothing (dashboards/automations) references the bridged entities.
+    integrations:
+      - tplink
+      - homekit_controller
+    pin: true
+    status: active