opencode/decisions.yaml, zigbee2mqtt/state.json

opencode/decisions.yaml

@@ -258,7 +258,7 @@ notes:
     integrations:
       - octoprint
     pin: true
-    status: active
+    status: superseded
   - id: 2026-08-14-octoprint-live-rest-sensors-are-the
     date: 2026-08-14
     title: "OctoPrint: `_live` REST sensors are the accurate source, MQTT push lags"
@@ -354,7 +354,7 @@ notes:
     integrations:
       - octoprint
     pin: true
-    status: active
+    status: superseded
   - id: 2026-08-16-matter-outage-2026-08-16-was-thread
     date: 2026-08-16
     title: Matter outage 2026-08-16 was Thread mesh re-forming, not host firewall
@@ -874,4 +874,27 @@ notes:
     integrations:
       - ha_creality_ws
       - webrtc
+    status: superseded
+    superseded_by: 2026-09-28-sparkx-camera-picture-entity-live-card-2
+  - id: 2026-09-28-sparkx-camera-picture-entity-live-card-2
+    date: 2026-09-28
+    title: "SparkX camera: picture-entity live card, reload integration to fix hung feed"
+    decision: "SparkX camera: use picture-entity with camera_view: live, never
+      custom:webrtc-camera. Hung feed = stale printer WebRTC session; reload the
+      ha_creality_ws entry to fix (no restart). Snapshots need light.sparkx_i7_light on."
+    rationale: "No MJPEG (8080 refused) or RTSP on the printer, so its native WebRTC endpoint
+      is the only source and go2rtc (via ha_creality_ws) the only relay. webrtc-camera was
+      tried with url: and entity: modes and stayed black. A stale upstream session leaves
+      the stream registered but carrying no media, so the frontend shows a permanent
+      Loading spinner - the card was never at fault. Keep the #format=creality fragment in
+      the go2rtc source or the printer returns an empty SDP."
+    entities:
+      - camera.sparkx_i7_printer_camera
+      - light.sparkx_i7_light
+    files:
+      - go2rtc.yaml
+    integrations:
+      - ha_creality_ws
+      - webrtc
+    pin: true
     status: active