.ha_mcp/logs/mcp_usage.jsonl, opencode/decisions.yaml

opencode/decisions.yaml

@@ -679,7 +679,8 @@ notes:
       - tplink
       - homekit_controller
     pin: true
-    status: active
+    status: superseded
+    superseded_by: 2026-08-29-new-kasa-devices-native-tplink-except
   - id: 2026-08-29-tplink-kasa-entries-are-discovery-based
     date: 2026-08-29
     title: tplink/Kasa entries are discovery-based; IP changes handled automatically
@@ -718,3 +719,23 @@ notes:
       - tplink
     pin: true
     status: active
+  - id: 2026-08-29-new-kasa-devices-native-tplink-except
+    date: 2026-08-29
+    title: New Kasa devices → native tplink, except filter plug on Matter; Homebridge legacy
+      untouched
+    decision: "Kasa has two paths: legacy devices bridged via a Homebridge plugin (leave
+      untouched); new devices go on native tplink — except the filter plug (KP125M), which
+      is on native Matter. Remove Homebridge only after verifying nothing depends on its
+      devices."
+    rationale: "Original note recorded the two-path Kasa setup. Amended 2026-08-29 to record
+      the new exception: the filter plug uses the native Matter integration rather than
+      tplink (Matter 1.3 firmware exposes power/voltage/current/energy). Both the
+      Homebridge-bridged devices and native-tplink guidance stay in force."
+    entities:
+      - switch.filter
+    integrations:
+      - tplink
+      - homekit_controller
+      - matter
+    pin: true
+    status: active