Skip to content

Commit

Permalink
[python] Deprecate chip-device-ctrl step: 1 Add "replhint" for most c…
Browse files Browse the repository at this point in the history
…ommands (#21845)
  • Loading branch information
erjiaqing authored and pull[bot] committed Sep 22, 2022
1 parent 4a32af7 commit 4190028
Show file tree
Hide file tree
Showing 2 changed files with 143 additions and 6 deletions.
100 changes: 100 additions & 0 deletions docs/guides/python_chip_controller_building.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,9 @@ The Python CHIP Controller is a tool that allows to commission a Matter device
into the network and to communicate with it using the Zigbee Cluster Library
(ZCL) messages.

> The chip-device-ctrl tool will be deprecated, and will be replaced by
> chip-repl. Continue reading to see how to do the same thing with chip-repl.
<hr>

- [Source files](#source)
Expand Down Expand Up @@ -192,6 +195,8 @@ set the credentials to the controller by executing the following command:
chip-device-ctrl > set-pairing-wifi-credential TESTSSID P455W4RD
```
**REPL Command**: `devCtrl.SetWiFiCredentials(<ssid>, <password>)`
### Step 5: Commission the Matter accessory device over Bluetooth LE
The controller uses a 12-bit value called **discriminator** to discern between
Expand Down Expand Up @@ -222,6 +227,9 @@ with the following assumptions for the Matter accessory device:
chip-device-ctrl > connect -ble 3840 20202021 1234
```
**REPL Command:**
`devCtrl.ConnectBLE(<discriminator>, <setup pincode>, <temporary node id>)`
You can skip the last parameter, the Node ID, in the command. If you skip it,
the controller will assign it randomly. In that case, note down the Node ID,
because it is required later in the configuration process.
Expand Down Expand Up @@ -258,13 +266,19 @@ state:
chip-device-ctrl > zcl OnOff Toggle 1234 1 0
```
**REPL Command:**
`await devCtrl.SendCommand(1234, 1, Clusters.OnOff.Commands.Toggle())`
To change the brightness of the LED, use the following command, with the level
value somewhere between 0 and 255.
```
chip-device-ctrl > zcl LevelControl MoveToLevel 1234 1 0 level=50
```
**REPL Command:**
`await devCtrl.SendCommand(1234, 1, LevelControl.Commands.MoveToLevel(level=50, transitionTime=Null, optionsMask=0, optionsOverride=0))`
### Step 7: Read basic information out of the accessory.
Every Matter accessory device supports a Basic Cluster, which maintains
Expand All @@ -278,8 +292,13 @@ chip-device-ctrl > zclread Basic ProductName 1234 1 0
chip-device-ctrl > zclread Basic SoftwareVersion 1234 1 0
```
**REPL Command:**
`await devCtrl.ReadAttribute(1234, [(1, Clusters.Basic.Attributes.VendorName)])`
> Use the `zcl ? Basic` command to list all available commands for Basic
> Cluster.
>
> In REPL, you can type `Clusters.Basic.Attributes.` and then use the TAB key.
<hr>
Expand All @@ -289,6 +308,8 @@ chip-device-ctrl > zclread Basic SoftwareVersion 1234 1 0
### `ble-adapter-print`
> BLE adapter operations is not yet supported in REPL
Print the available Bluetooth adapters on device. Takes no arguments:
```
Expand All @@ -298,6 +319,8 @@ chip-device-ctrl > ble-adapter-print
### `ble-debug-log`
> BLE adapter operations is not yet supported in REPL
Enable the Bluetooth LE debug logs.
```
Expand All @@ -306,6 +329,8 @@ chip-device-ctrl > ble-debug-log 1
### `ble-scan [-t <timeout>] [identifier]`
> BLE adapter operations is not yet supported in REPL
Start a scan action to search for valid CHIP devices over Bluetooth LE (for at
most _timeout_ seconds). Stop when the device is matching the identifier or the
counter times out.
Expand Down Expand Up @@ -336,6 +361,9 @@ device commissioning procedure to configure the device with a Thread interface.
chip-device-ctrl > set-pairing-thread-credential 0e080000000000010000000300001335060004001fffe002084fe76e9a8b5edaf50708fde46f999f0698e20510d47f5027a414ffeebaefa92285cc84fa030f4f70656e5468726561642d653439630102e49c0410b92f8c7fbb4f9f3e08492ee3915fbd2f0c0402a0fff8
```
**REPL Commands:**
`devCtrl.SetThreadOperationalDataset(bytes.FromHex("0e080000000000010000000300001335060004001fffe002084fe76e9a8b5edaf50708fde46f999f0698e20510d47f5027a414ffeebaefa92285cc84fa030f4f70656e5468726561642d653439630102e49c0410b92f8c7fbb4f9f3e08492ee3915fbd2f0c0402a0fff8"))`
### `set-pairing-wifi-credential <ssid> <credentials>`
Provides the controller with Wi-Fi network credentials that will be used in the
Expand All @@ -345,6 +373,8 @@ device commissioning procedure to configure the device with a Wi-Fi interface.
chip-device-ctrl > set-pairing-wifi-credential TESTSSID P455W4RD
```
**REPL Commands:** `devCtrl.SetWiFiCredentials('TESTSSID', 'P455W4RD')`
### `connect -ip <address> <SetUpPinCode> [<nodeid>]`
Do key exchange and establish a secure session between controller and device
Expand All @@ -356,6 +386,9 @@ persisted by controller / device.
If no nodeid given, a random Node ID will be used.
**REPL Commands:**
`devCtrl.CommissionIP(b'<ip address>', <setup pin code>, <nodeid>)`
### `connect -ble <discriminator> <SetUpPinCode> [<nodeid>]`
Do key exchange and establish a secure session between controller and device
Expand All @@ -367,13 +400,20 @@ persisted by controller / device.
If no nodeid given, a random Node ID will be used.
**REPL Commands:**
`devCtrl.ConnectBLE(<discriminator>, <setup pin code>, <nodeid>)`
### `close-session <nodeid>`
If case there exists an open session (PASE or CASE) to the device with a given
Node ID, mark it as expired.
**REPL Commands:** `devCtrl.CloseSession(<nodeid>)`
### `discover`
> To be implemented in REPL
Discover available Matter accessory devices:
```
Expand All @@ -382,6 +422,8 @@ chip-device-ctrl > discover -all
### `resolve <node_id>`
> To be implemented in REPL
Resolve DNS-SD name corresponding with the given Node ID and update address of
the node in the device controller:
Expand All @@ -391,6 +433,8 @@ chip-device-ctrl > resolve 1234
### `setup-payload generate [-v <Vendor ID>] [-p <Product ID>] [-cf <Custom Flow>] [-dc <Discovery Capabilities>] [-dv <Discriminator Value>] [-ps <Passcode>]`
> To be implemented in REPL
Print the generated Onboarding Payload Contents in human-readable (Manual
Pairing Code) and machine-readable (QR Code) format:
Expand All @@ -402,6 +446,8 @@ SetupQRCode: [MT:YNJV7VSC00CMVH7SR00]
### `setup-payload parse-manual <manual-pairing-code>`
> To be implemented in REPL
Print the commissioning information encoded in the Manual Pairing Code:
```
Expand All @@ -417,6 +463,8 @@ SetUpPINCode: 20202021
### `setup-payload parse-qr <qr-code>`
> To be implemented in REPL
Print the commissioning information encoded in the QR Code payload:
```
Expand Down Expand Up @@ -451,6 +499,14 @@ example, `networkId=hex:0123456789abcdef` (for
For boolean type, use `key=True` or `key=False`.
**REPL Commands:**
```python
# await devCtrl.SendCommand(<nodeid>, <endpoint>, Clusters.<cluster>.Commands.<command>(<arguments>))
# e.g.
await devCtrl.SendCommand(12344321, 1, Clusters.LevelControl.Commands.MoveWithOnOff(moveMode=1, rate=2, optionsMask=0, optionsOverride=0))
```

### `zcl ?`

List available clusters:
Expand Down Expand Up @@ -499,6 +555,10 @@ WakeOnLan
WindowCovering
```

**REPL Commands**

Type `Clusters.` and hit TAB

### `zcl ? <Cluster>`

List available commands in cluster. For example, for _Basic_ cluster:
Expand All @@ -525,6 +585,10 @@ LocalConfigDisabled
ClusterRevision
```

**REPL Commands**

Type `Clusters.(cluster name).Commands.` and hit TAB

### `zclread <Cluster> <Attribute> <NodeId> <EndpointId> <GroupId> [arguments]`

Read the value of ZCL attribute. For example:
Expand All @@ -533,6 +597,14 @@ Read the value of ZCL attribute. For example:
chip-device-ctrl > zclread Basic VendorName 1234 1 0
```

**REPL Commands**

```python
# devCtrl.ReadAttribute(<nodeid>, [(<endpoint id>, Clusters.<cluster>.Attributes.<attribute>)])
# e.g.
await devCtrl.ReadAttribute(1234, [(1, Clusters.Basic.Attributes.VendorName)])
```

### `zclwrite <cluster> <attribute> <nodeid> <endpoint> <groupid> <value>`

Write the value to a ZCL attribute. For example:
Expand All @@ -547,6 +619,17 @@ chip-device-ctrl > zclwrite TestCluster CharString 1 1 0 233233
Note: The format of the value is the same as the format of argument values for
ZCL cluster commands.

**REPL Commands**

```python
# devCtrl.WriteAttribute(<nodeid>, [(<endpointid>, Clusters.<cluster>.Attributes.<attribute>(value=<attribute value>))])
# e.g.
await devCtrl.WriteAttribute(1, [(1, Clusters.TestCluster.Attributes.Int8u(value=1))])
await devCtrl.WriteAttribute(1, [(1, Clusters.TestCluster.Attributes.Boolean(value=True))])
await devCtrl.WriteAttribute(1, [(1, Clusters.TestCluster.Attributes.OctetString(value=b'123123\x00'))])
await devCtrl.WriteAttribute(1, [(1, Clusters.TestCluster.Attributes.CharString(value='233233'))])
```

### `zclsubscribe <Cluster> <Attribute> <Nodeid> <Endpoint> <MinInterval> <MaxInterval>`

Configure ZCL attribute reporting settings. For example:
Expand All @@ -555,6 +638,14 @@ Configure ZCL attribute reporting settings. For example:
chip-device-ctrl > zclsubscribe OccupancySensing Occupancy 1234 1 10 20
```

**REPL Commands**

```python
# devCtrl.ReadAttribute(<nodeid>, [(<endpoint>, Clusters.<cluster>.Attributes.<attribute>)], reportInterval=(<min interval>, <max interval>))
# e.g.
await devCtrl.ReadAttribute(1, [(1, Clusters.OccupancySensing.Attributes.Occupancy)], reportInterval=(10, 20))
```

### `zclsubscribe -shutdown <subscription id>`

Shutdown an existing attribute subscription.
Expand Down Expand Up @@ -583,3 +674,12 @@ chip-device-ctrl > zclsubscribe OnOff OnOff 1 1 10 20
```

The subscription id is `0xdeadbeefcafe` in this case

**REPL Commands**

```python
# SubscriptionTransaction.Shutdown()
# e.g.
sub = await devCtrl.ReadAttribute(1, [(1, Clusters.OccupancySensing.Attributes.Occupancy)], reportInterval=(10, 20))
sub.Shutdown()
```
Loading

0 comments on commit 4190028

Please sign in to comment.