opencode/decisions.yaml, zigbee2mqtt/state.json

This commit is contained in:
Home Assistant Version Control
2026-08-23 22:42:34 +00:00
parent 429992ef77
commit 327c72600a
2 changed files with 59 additions and 14 deletions
+46 -1
View File
@@ -475,7 +475,8 @@ notes:
integrations:
- matter
- thread
status: active
status: superseded
superseded_by: 2026-08-23-thread-outage-fix-cold-boot-google-tv-2
- id: 2026-08-23-zbt-2-ordered-otbr-migration-plan
date: 2026-08-23
title: "ZBT-2 ordered: OTBR migration plan pending hardware"
@@ -496,4 +497,48 @@ notes:
integrations:
- matter
- thread
status: superseded
superseded_by: 2026-08-23-zbt-2-ordered-otbr-migration-plan-2
- id: 2026-08-23-thread-outage-fix-cold-boot-google-tv-2
date: 2026-08-23
title: "Thread outage fix: cold-boot Google TV Streamer"
decision: "If Matter/Thread nodes go unavailable after network disruption: unplug+replug
the Google TV Streamer (Thread BR), wait ~10 min. Nodes rejoin only if cold boot
restores its original Thread dataset; else re-pair needed. Restarting HA/Matter
add-on does NOT help."
rationale: "2026-08-23: Bell router reboot made TV Streamer re-form Thread mesh under new
identity (XPAN BDE139547AD960A4 / fdbd:e139:547a:60a4); six Thread nodes stranded on
dead fd25:f6c0:5149 formation — silent, invisible to mDNS. Add-on restart useless;
cold boot restored dataset by 18:25. Google never exports credentials; permanent fix
= HA-hosted OTBR on own radio."
entities:
- light.bedroom_lamp
- light.office_lamp
- sensor.bedroom_switch_battery
integrations:
- matter
- thread
pin: true
status: active
- id: 2026-08-23-zbt-2-ordered-otbr-migration-plan-2
date: 2026-08-23
title: "ZBT-2 ordered: OTBR migration plan pending hardware"
decision: "When Home Assistant Connect ZBT-2 arrives: install OpenThread Border Router
add-on on it, form HA's own Thread network, then migrate the 6 Matter-over-Thread
devices over-the-air per device (Add Device → scan label code → Move to HA's Thread
Network). No factory resets expected; reset only as fallback."
rationale: "2026-08-23: Recurring outages because Google TV Streamer owns the Thread mesh
and re-forms it with fresh credentials after disruptions, stranding nodes. It never
exports its dataset, so no seamless import — but devices already sit in HA's Matter
fabric, so per-device OTA migration works without reset. Keep TV Streamer online
until all 6 moved, then disable its hub radio in Google Home app. End state: border
routers visible in HA Thread integration, router reboots harmless."
entities:
- light.bedroom_lamp
- light.office_lamp
- sensor.bedroom_switch_battery
integrations:
- matter
- thread
pin: true
status: active