matterbridge-example-camera 0.0.8 → 0.0.9-dev-20260727-f34a88a

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -28,6 +28,18 @@ If you like this project and find it useful, please consider giving it a star on
28
28
 
29
29
  <a href="https://www.buymeacoffee.com/luligugithub"><img src="https://matterbridge.io/assets/bmc-button.svg" alt="Buy me a coffee" width="120"></a>
30
30
 
31
+ ## [0.0.9] - Deb branch
32
+
33
+ ### Added
34
+
35
+ - [Dev Container]: Update Dev Container v.1.2.0.
36
+
37
+ ### Changed
38
+
39
+ - [screenshots]: Update screenshots.
40
+
41
+ <a href="https://www.buymeacoffee.com/luligugithub"><img src="https://matterbridge.io/assets/bmc-button.svg" alt="Buy me a coffee" width="120"></a>
42
+
31
43
  ## [0.0.8] - 2026-07-26
32
44
 
33
45
  ### Added
package/README.md CHANGED
@@ -38,22 +38,27 @@ Thanks to [Ludovic BOUÉ](https://github.com/lboue) for his contributions to thi
38
38
 
39
39
  ## Requirements
40
40
 
41
- Requires [`ffmpeg`](https://ffmpeg.org/) to be installed. The resolver checks the system command and common installation directories on Linux, macOS, and Windows.
41
+ Requires [`ffmpeg`](https://ffmpeg.org/) to be installed on the host or in the container. The resolver checks the system command and common installation directories on Linux, macOS, and Windows.
42
42
 
43
43
  Install it with the platform's package manager:
44
44
 
45
+ ### Linux (Debian/Ubuntu)
46
+
47
+ If you run in a container, install it in the same way.
48
+
45
49
  ```bash
46
- # Linux (Debian/Ubuntu)
47
50
  sudo apt update && sudo apt install -y ffmpeg
48
51
  ```
49
52
 
53
+ ### Windows
54
+
50
55
  ```powershell
51
- # Windows
52
56
  winget install --id Gyan.FFmpeg -e
53
57
  ```
54
58
 
59
+ ### macOS
60
+
55
61
  ```bash
56
- # macOS
57
62
  brew install ffmpeg
58
63
  ```
59
64
 
@@ -105,6 +110,8 @@ Supported by:
105
110
 
106
111
  - [Matterserver dashboard](screenshots/matterserver-camera.png)
107
112
 
113
+ - [Matterserver dashboard with MPTZ](screenshots/matterserver-ptz-camera.png)
114
+
108
115
  ### Snapshot Camera
109
116
 
110
117
  Features:
@@ -162,42 +169,33 @@ Features:
162
169
  - Configurable Power Source cluster type: Rechargeable, Replaceable, Battery, Wired, or None to omit the Power Source cluster entirely.
163
170
  - Deviation from the Matter specification: the CameraAvStreamManagement ImageControl feature is also enabled, even though the specification only allows it when Video or Snapshot is present, to work around the same matter.js bug described above for Audio Doorbell.
164
171
 
165
- #### Pairing two Intercoms for two-way calling
172
+ Supported by:
166
173
 
167
- `src/module.ts` registers exactly this pair for testing: `Intercom 1` (bridged, under the Matterbridge aggregator) and `Intercom 2` (`mode: 'server'`, its own Matter node) — commission both and follow the steps below to bind them together.
174
+ - [Matterserver dashboard](screenshots/matterserver-intercom.png)
168
175
 
169
- `Intercom 2` has to be `mode: 'server'` rather than a second bridged endpoint: peer resolution (see below) identifies the caller from the `peerNodeId`/`fabricIndex` of the command's CASE session, and a CASE session only exists between two distinct node identities on the fabric. Two bridged endpoints share the bridge's single node identity, so there is no CASE session, Binding, or ACL between them to test — invoking one from the other would just be a local, in-process behavior call. `mode: 'server'` is what gives an endpoint its own independent Matter node, which is what a real second, physical Intercom would be.
176
+ ### Pairing the Server Chime and Server Doorbell to let the Doorbell play a chime
170
177
 
171
- Unlike a Doorbell/Chime pair, where only the Doorbell invokes commands on the Chime, an Intercom both hosts (server) and invokes (client) WebRtcTransportProvider and WebRtcTransportRequestor (see `#resolvePeerRequestorEndpoint` in `src/behaviors/webRtcTransportProviderServer.ts`). Once a peer invokes SolicitOffer/ProvideOffer on an Intercom's WebRtcTransportProvider, that Intercom resolves the caller's WebRtcTransportRequestor endpoint directly from the invoking peer's node id/fabric index carried by the command's CASE session — not via the Binding cluster — so the Offer/Answer "return leg" needs no binding of its own. Only the initiating invoke needs one.
178
+ `src/module.ts` registers exactly this pair for testing: `Server Chime` (`mode: 'server'`, its own Matter node) and `Server Doorbell` (`mode: 'server'`, its own Matter node) — commission both and follow the steps below to bind them together.
172
179
 
173
- So, to let either Intercom 1 or Intercom 2 start a call, on the fabric they share (commission both onto the same controller/ecosystem first, e.g. via chip-tool, Apple Home, or Google Home):
180
+ 1. **Binding on Server Doorbell → Server Chime**, so Server Doorbell knows where to play a chime.
174
181
 
175
- 1. **Binding on 1 → 2**, so Intercom 1 knows where to send SolicitOffer/ProvideOffer. Binding on 2 → 1 is the mirror, for the other direction:
182
+ Bind Server Doorbell to Server Chime with ![Matter Server Dashboard](screenshots/binding.png)
176
183
 
177
- ```bash
178
- chip-tool binding write binding '[{"fabricIndex": 1, "node": <NODE_ID_2>, "endpoint": <ENDPOINT_2>, "cluster": 1363}]' <NODE_ID_1> <ENDPOINT_1>
179
- chip-tool binding write binding '[{"fabricIndex": 1, "node": <NODE_ID_1>, "endpoint": <ENDPOINT_1>, "cluster": 1363}]' <NODE_ID_2> <ENDPOINT_2>
180
- ```
184
+ ### Pairing the two Server Intercoms for two-way calling
181
185
 
182
- `1363` (`0x553`) is the WebRtcTransportProvider cluster id; `<ENDPOINT_1>`/`<ENDPOINT_2>` are each Intercom's endpoint number (find them from the commissioning output or the Matterbridge frontend).
186
+ `src/module.ts` registers exactly this pair for testing: `Server Intercom 1` (`mode: 'server'`, its own Matter node) and `Server Intercom 2` (`mode: 'server'`, its own Matter node) — commission both and follow the steps below to bind them together.
187
+
188
+ Unlike a Doorbell/Chime pair, where only the Doorbell invokes commands on the Chime, an Intercom both hosts (server) and invokes (client) WebRtcTransportProvider and WebRtcTransportRequestor (see `#resolvePeerRequestorEndpoint` in `src/behaviors/webRtcTransportProviderServer.ts`). Once a peer invokes SolicitOffer/ProvideOffer on an Intercom's WebRtcTransportProvider, that Intercom resolves the caller's WebRtcTransportRequestor endpoint directly from the invoking peer's node id/fabric index carried by the command's CASE session — not via the Binding cluster — so the Offer/Answer "return leg" needs no binding of its own. Only the initiating invoke needs one.
183
189
 
184
- 2. **ACL on 2 granting 1**, and **ACL on 1 granting 2**, Operate access to both WebRtcTransportProvider (`1363`) and WebRtcTransportRequestor (`1364`, `0x554`) — Intercom 1 needs it on 2 for the initiating invoke, and Intercom 2 needs it on 1 for the return invoke, regardless of who starts the call:
190
+ So, to let either Server Intercom 1 or Server Intercom 2 start a call, on the fabric they share.
185
191
 
186
- ```bash
187
- chip-tool accesscontrol write acl '[
188
- {"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [<ADMIN_NODE_ID>], "targets": null},
189
- {"fabricIndex": 1, "privilege": 3, "authMode": 2, "subjects": [<NODE_ID_1>], "targets": [{"cluster": 1363, "endpoint": null, "deviceType": null}, {"cluster": 1364, "endpoint": null, "deviceType": null}]}
190
- ]' <NODE_ID_2> 0
192
+ 1. **Binding on Server Intercom 1 → Server Intercom 2**, so Server Intercom 1 knows where to send SolicitOffer/ProvideOffer.
191
193
 
192
- chip-tool accesscontrol write acl '[
193
- {"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [<ADMIN_NODE_ID>], "targets": null},
194
- {"fabricIndex": 1, "privilege": 3, "authMode": 2, "subjects": [<NODE_ID_2>], "targets": [{"cluster": 1363, "endpoint": null, "deviceType": null}, {"cluster": 1364, "endpoint": null, "deviceType": null}]}
195
- ]' <NODE_ID_1> 0
196
- ```
194
+ Bind Server Intercom 1 to Server Intercom 2 with ![Matter Server Dashboard](screenshots/binding-intercom1.png)
197
195
 
198
- The ACL attribute is a full replace, not a merge: keep the existing Administer entry for `<ADMIN_NODE_ID>` (your controller/commissioner) in the list, or you lock yourself out of that node.
196
+ 2. **Binding on Server Intercom 2 → Server Intercom 1**, so Server Intercom 2 knows where to send SolicitOffer/ProvideOffer.
199
197
 
200
- With both directions in place, either Intercom can call the other; a call initiated the other way only needs its own binding/ACL pair, already covered above since both were set up symmetrically.
198
+ Bind Server Intercom 2 to Server Intercom 1 with ![Matter Server Dashboard](screenshots/binding-intercom2.png)
201
199
 
202
200
  ## WebRTC video and audio injection
203
201
 
package/dist/module.js CHANGED
@@ -112,12 +112,12 @@ export class ExampleMatterbridgeCameraPlatform extends MatterbridgeDynamicPlatfo
112
112
  lightOptions: { name: 'Floodlight' },
113
113
  });
114
114
  await this.addDevice(exampleFloodlightCamera);
115
- const exampleIntercom1 = new Intercom('Intercom 1', 'INTERCOM1-001', {
115
+ const exampleIntercom = new Intercom('Intercom', 'INTERCOM-001', {
116
116
  identifyTime: 5,
117
117
  identifyType: Identify.IdentifyType.VisibleIndicator,
118
118
  powerSourceType: 'Replaceable',
119
119
  });
120
- await this.addDevice(exampleIntercom1);
120
+ await this.addDevice(exampleIntercom);
121
121
  const exampleVideoDoorbell = new VideoDoorbell('Video Doorbell', 'VIDEODOORBELL-001', {
122
122
  powerSourceType: 'Wired',
123
123
  cameraOptions: { identifyTime: 5, identifyType: Identify.IdentifyType.VisibleIndicator },
@@ -142,8 +142,10 @@ export class ExampleMatterbridgeCameraPlatform extends MatterbridgeDynamicPlatfo
142
142
  });
143
143
  const serverDoorbell = new Doorbell('Server Doorbell', 'SERVER-DOORBELL-001', { mode: 'server' });
144
144
  await this.addDevice(serverDoorbell);
145
- const exampleIntercom2 = new Intercom('Intercom 2', 'INTERCOM2-001', { mode: 'server' });
146
- await this.addDevice(exampleIntercom2);
145
+ const serverIntercom1 = new Intercom('Server Intercom 1', 'SERVER-INTERCOM1-001', { mode: 'server' });
146
+ await this.addDevice(serverIntercom1);
147
+ const serverIntercom2 = new Intercom('Server Intercom 2', 'SERVER-INTERCOM2-001', { mode: 'server' });
148
+ await this.addDevice(serverIntercom2);
147
149
  this.log.info(`Platform ${this.config.name} started successfully`);
148
150
  }
149
151
  async onConfigure() {
@@ -1,12 +1,12 @@
1
1
  {
2
2
  "name": "matterbridge-example-camera",
3
- "version": "0.0.8",
3
+ "version": "0.0.9-dev-20260727-f34a88a",
4
4
  "lockfileVersion": 3,
5
5
  "requires": true,
6
6
  "packages": {
7
7
  "": {
8
8
  "name": "matterbridge-example-camera",
9
- "version": "0.0.8",
9
+ "version": "0.0.9-dev-20260727-f34a88a",
10
10
  "license": "Apache-2.0",
11
11
  "dependencies": {
12
12
  "node-ansi-logger": "3.3.0",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "matterbridge-example-camera",
3
- "version": "0.0.8",
3
+ "version": "0.0.9-dev-20260727-f34a88a",
4
4
  "description": "Matterbridge camera example plugin",
5
5
  "author": "https://github.com/Luligu",
6
6
  "license": "Apache-2.0",
File without changes