@matter/nodejs-shell 0.16.0-alpha.0-20251220-0bb8d9f89 → 0.16.0-alpha.0-20251221-3dce6fa1b
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/README.md +36 -0
- package/package.json +10 -10
package/README.md
CHANGED
|
@@ -154,6 +154,20 @@ To see the full node structure of a node you can use the `nodes log` command and
|
|
|
154
154
|
|
|
155
155
|
The shell provides comprehensive OTA (Over-The-Air) update management through DCL (Distributed Compliance Ledger) integration and local file operations.
|
|
156
156
|
|
|
157
|
+
#### List known OTA updates
|
|
158
|
+
|
|
159
|
+
Use `nodes ota known [node-id]` to list OTA updates that are known to be available for commissioned nodes. This shows updates that have been discovered through a previous query by the OTA provider.
|
|
160
|
+
|
|
161
|
+
```
|
|
162
|
+
nodes ota known
|
|
163
|
+
nodes ota known 5000
|
|
164
|
+
nodes ota known --local
|
|
165
|
+
```
|
|
166
|
+
|
|
167
|
+
Options:
|
|
168
|
+
- `[node-id]`: Optional node ID to check for updates for a specific node
|
|
169
|
+
- `--local`: Include locally stored update files in the results
|
|
170
|
+
|
|
157
171
|
#### Check for OTA updates for a commissioned node
|
|
158
172
|
|
|
159
173
|
Use `nodes ota check <node-id>` to query the DCL for available OTA updates for a specific commissioned node. The command uses the node's basic information (vendor ID, product ID, current software version) to check for newer firmware versions.
|
|
@@ -161,10 +175,12 @@ Use `nodes ota check <node-id>` to query the DCL for available OTA updates for a
|
|
|
161
175
|
```
|
|
162
176
|
nodes ota check 5000
|
|
163
177
|
nodes ota check 5000 --mode test
|
|
178
|
+
nodes ota check 5000 --local
|
|
164
179
|
```
|
|
165
180
|
|
|
166
181
|
Options:
|
|
167
182
|
- `--mode <prod|test>`: Specify DCL mode - production (default) or test
|
|
183
|
+
- `--local`: Include locally stored update files when checking for updates
|
|
168
184
|
|
|
169
185
|
The command will display information about available updates including version, file size, and download URL.
|
|
170
186
|
|
|
@@ -175,11 +191,31 @@ Use `nodes ota download <node-id>` to check for and download OTA updates from DC
|
|
|
175
191
|
```
|
|
176
192
|
nodes ota download 5000
|
|
177
193
|
nodes ota download 5000 --mode test --force
|
|
194
|
+
nodes ota download 5000 --local
|
|
178
195
|
```
|
|
179
196
|
|
|
180
197
|
Options:
|
|
181
198
|
- `--mode <prod|test>`: Specify DCL mode - production (default) or test
|
|
182
199
|
- `--force`: Force re-download even if the update is already cached locally
|
|
200
|
+
- `--local`: Consider locally cached updates when checking for available updates (before downloading)
|
|
201
|
+
|
|
202
|
+
#### Apply OTA update to a commissioned node
|
|
203
|
+
|
|
204
|
+
Use `nodes ota apply <node-id>` to check for, download (if needed), and apply an OTA update to a commissioned node. This command combines the check, download, and update trigger into a single operation.
|
|
205
|
+
|
|
206
|
+
```
|
|
207
|
+
nodes ota apply 5000
|
|
208
|
+
nodes ota apply 5000 --mode test
|
|
209
|
+
nodes ota apply 5000 --local
|
|
210
|
+
nodes ota apply 5000 --force
|
|
211
|
+
```
|
|
212
|
+
|
|
213
|
+
Options:
|
|
214
|
+
- `--mode <prod|test>`: Specify DCL mode - production (default) or test
|
|
215
|
+
- `--force`: Force download even if update is already stored locally
|
|
216
|
+
- `--local`: Apply update from locally stored files instead of downloading from DCL
|
|
217
|
+
|
|
218
|
+
The command will check for available updates, download if necessary, and trigger the OTA update process on the connected node. The node must be connected for this command to work.
|
|
183
219
|
|
|
184
220
|
#### Display OTA image information
|
|
185
221
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@matter/nodejs-shell",
|
|
3
|
-
"version": "0.16.0-alpha.0-
|
|
3
|
+
"version": "0.16.0-alpha.0-20251221-3dce6fa1b",
|
|
4
4
|
"description": "Shell app for Matter controller",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"iot",
|
|
@@ -43,15 +43,15 @@
|
|
|
43
43
|
"#types": "@matter/types"
|
|
44
44
|
},
|
|
45
45
|
"dependencies": {
|
|
46
|
-
"@matter/general": "0.16.0-alpha.0-
|
|
47
|
-
"@matter/model": "0.16.0-alpha.0-
|
|
48
|
-
"@matter/node": "0.16.0-alpha.0-
|
|
49
|
-
"@matter/nodejs": "0.16.0-alpha.0-
|
|
50
|
-
"@matter/nodejs-ble": "0.16.0-alpha.0-
|
|
51
|
-
"@matter/protocol": "0.16.0-alpha.0-
|
|
52
|
-
"@matter/tools": "0.16.0-alpha.0-
|
|
53
|
-
"@matter/types": "0.16.0-alpha.0-
|
|
54
|
-
"@project-chip/matter.js": "0.16.0-alpha.0-
|
|
46
|
+
"@matter/general": "0.16.0-alpha.0-20251221-3dce6fa1b",
|
|
47
|
+
"@matter/model": "0.16.0-alpha.0-20251221-3dce6fa1b",
|
|
48
|
+
"@matter/node": "0.16.0-alpha.0-20251221-3dce6fa1b",
|
|
49
|
+
"@matter/nodejs": "0.16.0-alpha.0-20251221-3dce6fa1b",
|
|
50
|
+
"@matter/nodejs-ble": "0.16.0-alpha.0-20251221-3dce6fa1b",
|
|
51
|
+
"@matter/protocol": "0.16.0-alpha.0-20251221-3dce6fa1b",
|
|
52
|
+
"@matter/tools": "0.16.0-alpha.0-20251221-3dce6fa1b",
|
|
53
|
+
"@matter/types": "0.16.0-alpha.0-20251221-3dce6fa1b",
|
|
54
|
+
"@project-chip/matter.js": "0.16.0-alpha.0-20251221-3dce6fa1b",
|
|
55
55
|
"ws": "^8.18.3",
|
|
56
56
|
"yargs": "^18.0.0"
|
|
57
57
|
},
|