Unpairing the last fabric makes matter.js factory-reset itself (E5 handles this correctly — witness cleared, endpoint map preserved). The unpair menu then re-reads pairing state, and during the ~200ms while matter.js re-initialises the read throws:
Command get_pairing failed: Error: indigo-matter-bridge is not initialized
Observed live 2026-08-06. Harmless — the node recovered and was advertising 200ms later — but the user gets an error line immediately after a successful unpair, which reads as a failure.
Fix: after a last-fabric removal, either wait for the node to come back before re-reading, or tolerate the not-initialised state for a short window and retry. Files: plugin.py:menuUnpairEcosystem, bridge_client.remove_fabric, bridge-node/src/node.ts (removeFabric → noteLastFabricGone).
Unpairing the last fabric makes matter.js factory-reset itself (E5 handles this correctly — witness cleared, endpoint map preserved). The unpair menu then re-reads pairing state, and during the ~200ms while matter.js re-initialises the read throws:
Observed live 2026-08-06. Harmless — the node recovered and was advertising 200ms later — but the user gets an error line immediately after a successful unpair, which reads as a failure.
Fix: after a last-fabric removal, either wait for the node to come back before re-reading, or tolerate the not-initialised state for a short window and retry. Files:
plugin.py:menuUnpairEcosystem,bridge_client.remove_fabric,bridge-node/src/node.ts(removeFabric→noteLastFabricGone).