opencode/decisions.yaml

opencode/decisions.yaml

@@ -662,7 +662,8 @@ notes:
     integrations:
       - tplink
     pin: true
-    status: active
+    status: superseded
+    superseded_by: 2026-08-29-filter-plug-kasa-kp125m-on-matter
   - 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
@@ -694,3 +695,26 @@ notes:
     integrations:
       - tplink
     status: active
+  - id: 2026-08-29-filter-plug-kasa-kp125m-on-matter
+    date: 2026-08-29
+    title: Filter plug = Kasa KP125M on Matter; tplink path removed
+    decision: "Filter plug is a Kasa KP125M on Matter only: HA Matter (sw 1.3) exposes
+      power/voltage/current/energy/energy-exported, so the native tplink entry was
+      removed. Entities renamed to filter_* (switch.filter,
+      sensor.filter_current_consumption, sensor.filter_energy). Do not re-add the tplink
+      path."
+    rationale: 'Initial verification showed Matter exposing no power/energy entities, so
+      native tplink auto-discovery was used. Hewan when Matter firmware 1.3 confirmed it
+      reports power/voltage/current/energy/energy-exported, the plug was migrated to
+      Matter-only: tplink config entry (01M182SQ9M0SJDN9DTXTCG2QZA) removed, Matter
+      entities renamed to keep the filter_* IDs so existing automations and dashboards
+      resolved unchanged. Replacing the previous note that said "tplink, NOT Matter".'
+    entities:
+      - switch.filter
+      - sensor.filter_current_consumption
+      - sensor.filter_energy
+    integrations:
+      - matter
+      - tplink
+    pin: true
+    status: active