| 60 | * so the two protocol blocks are symmetric and can be reasoned about uniformly. |
| 61 | */ |
| 62 | export interface BridgeHapConfig { |
| 63 | /** |
| 64 | * Whether HAP is published for this bridge. Default `true` (so omitting the |
| 65 | * block, or omitting `enabled`, means HAP is on). Set to `false` to suppress |
| 66 | * the bridge's HAP advertisement while preserving any existing pairing. |
| 67 | * |
| 68 | * Both `hap` and `matter` may be disabled on the same bridge; the bridge |
| 69 | * then advertises nothing (it still loads, it just exposes no accessories). |
| 70 | */ |
| 71 | enabled?: boolean |
| 72 | |
| 73 | /** |
| 74 | * When `true`, the bridge accessory itself is NOT published, but external |
| 75 | * accessories registered by plugins against this bridge ARE still published |
| 76 | * (each as its own standalone HAP accessory). Intended to be paired with |
| 77 | * `enabled: false`; if `externalsOnly: true` is set on its own, validation |
| 78 | * warns and normalises `enabled` to `false` rather than rejecting the config. |
| 79 | */ |
| 80 | externalsOnly?: boolean |
| 81 | } |
| 82 | |
| 83 | export interface BridgeConfiguration { |
| 84 | name: string |
nothing calls this directly
no outgoing calls
no test coverage detected