opencode/decisions.yaml, zigbee2mqtt/state.json
This commit is contained in:
@@ -354,3 +354,19 @@ notes:
|
||||
- octoprint
|
||||
pin: true
|
||||
status: active
|
||||
- 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
|
||||
decision: The 2026-08-16 Matter node outages were traced to the external Thread border
|
||||
router's mesh re-forming (mesh prefix rotated fdfb:c653:60c7 → fd25:f6c0:5149). NOT
|
||||
a host routing/firewall issue. Devices self-heal once the matter server re-learns
|
||||
the new operational addresses; a per-device forced reconnect accelerates it.
|
||||
rationale: "Evidence: all 7 nodes rotated to the new fd25 prefix between 03:28–03:36; the
|
||||
host routed live Matter traffic fine throughout (office button session, scroll-wheel
|
||||
button events); Thread integration shows 0 border routers and no OTBR add-on exists,
|
||||
so routing depends on an external border router. Do not chase firewall/iptables
|
||||
theories for this failure signature."
|
||||
integrations:
|
||||
- matter
|
||||
- thread
|
||||
status: active
|
||||
|
||||
Reference in New Issue
Block a user