opencode/decisions.yaml, zigbee2mqtt/state.json

opencode/decisions.yaml

@@ -705,8 +705,8 @@ notes:
       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. However, when Matter firmware 1.3 confirmed it
-      reports power/voltage/current/energy/energy-exported, the plug was migrated to
+      native tplink auto-discovery was used. However, 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".'
@@ -739,3 +739,18 @@ notes:
       - matter
     pin: true
     status: active
+  - id: 2026-08-29-office-plug-removed-from-z2m-as-faulty
+    date: 2026-08-29
+    title: Office Plug removed from Z2M as faulty, replaced
+    decision: The Z2M 'Office Plug' (Third Reality 3RSP02028BZ, IEEE 0xffffb40e060893d8) was
+      removed from the mesh on 2026-08-29 as faulty and is being replaced. Its entities
+      (switch.office_plug, sensor.office_plug_*) are gone and nothing references them. Do
+      not re-add the old device IEEE.
+    rationale: User decided to replace the plug despite diagnostics showing healthy radio
+      publishing; records the deliberate removal so a future session does not try to
+      restore the old device IEEE or the removed entities.
+    entities:
+      - switch.office_plug
+    integrations:
+      - zigbee2mqtt
+    status: active