Skip to content

Commit 1998048

Browse files
committed
[Telink]: Restyled
1 parent be523cc commit 1998048

File tree

1 file changed

+19
-16
lines changed

1 file changed

+19
-16
lines changed

examples/light-switch-app/telink/Readme.md

+19-16
Original file line numberDiff line numberDiff line change
@@ -91,9 +91,9 @@ communicate with each other.
9191
To perform binding, you need a controller that can write the binding table to
9292
the light switch device and write proper ACL to the endpoint light bulb on the
9393
Lighting Example application. For example, you can use the CHIP Tool as the
94-
controller. The ACL should contain information about all clusters that can
95-
be called by the light switch application. See the section about interacting
96-
with ZCL clusters in the CHIP Tool's user guide for more information about ACLs.
94+
controller. The ACL should contain information about all clusters that can be
95+
called by the light switch application. See the section about interacting with
96+
ZCL clusters in the CHIP Tool's user guide for more information about ACLs.
9797
9898
You can perform the binding process to a single remote endpoint (unicast
9999
binding) or to a group of remote endpoints (group multicast).
@@ -104,8 +104,8 @@ binding) or to a group of remote endpoints (group multicast).
104104
#### Unicast binding to a remote endpoint using the CHIP Tool
105105
106106
In this scenario, commands are provided for a light switch device with the
107-
`nodeId = <light-switch-node-id>` and a light bulb device with `nodeId = <lighting-node-id>`,
108-
both commissioned to the same Matter network.
107+
`nodeId = <light-switch-node-id>` and a light bulb device with
108+
`nodeId = <lighting-node-id>`, both commissioned to the same Matter network.
109109
110110
To perform the unicast binding process, complete the following steps:
111111
@@ -135,10 +135,10 @@ To perform the unicast binding process, complete the following steps:
135135
136136
In this command:
137137
138-
- `{"fabricIndex": 1, "node": <lighting-node-id>, "endpoint": 1, "cluster": 6}` is a
139-
binding for the On/Off cluster.
140-
- `{"fabricIndex": 1, "node": <lighting-node-id>, "endpoint": 1, "cluster": 8}` is a
141-
binding for the Level Control cluster.
138+
- `{"fabricIndex": 1, "node": <lighting-node-id>, "endpoint": 1, "cluster": 6}`
139+
is a binding for the On/Off cluster.
140+
- `{"fabricIndex": 1, "node": <lighting-node-id>, "endpoint": 1, "cluster": 8}`
141+
is a binding for the Level Control cluster.
142142
143143
#### Group multicast binding to the group of remote endpoints using the CHIP Tool
144144
@@ -152,11 +152,13 @@ requests, and all of the devices in the bound groups can run the received
152152
command.
153153
154154
In this scenario, commands are provided for a light switch device with the
155-
`nodeId = <light-switch-node-id>` and a light bulb device with `nodeId = <lighting-node-id>`, both commissioned to the same Matter network.
155+
`nodeId = <light-switch-node-id>` and a light bulb device with
156+
`nodeId = <lighting-node-id>`, both commissioned to the same Matter network.
156157
157158
To perform the unicast binding process, complete the following steps:
158159
159-
1. Add an ACL to the lighting endpoint permissions by running the following command:
160+
1. Add an ACL to the lighting endpoint permissions by running the following
161+
command:
160162
161163
```bash
162164
$ ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null}, {"fabricIndex": 1, "privilege": 3, "authMode": 2, "subjects": [<light-switch-node-id>], "targets": [{"cluster": 6, "endpoint": 1, "deviceType": null}, {"cluster": 8, "endpoint": 1, "deviceType": null}]}]' <lighting-node-id> 0
@@ -173,23 +175,24 @@ To perform the unicast binding process, complete the following steps:
173175
This allows the lighting application device to receive commands from the
174176
light switch device.
175177
176-
4. Add the light switch device to the multicast group by running the following
178+
2. Add the light switch device to the multicast group by running the following
177179
command:
178180
179181
```bash
180182
$ ./chip-tool tests TestGroupDemoConfig --nodeId <light-switch-node-id>
181183
```
182184
183-
5. Add all light bulbs to the same multicast group by applying command below
185+
3. Add all light bulbs to the same multicast group by applying command below
184186
for each of the light bulbs, using the appropriate `<lighting-node-id>` (the
185-
user-defined ID of the node being commissioned except `<light-switch-node-id>`
186-
due to use this `<light-switch-node-id>` for light-switch) for each of them:
187+
user-defined ID of the node being commissioned except
188+
`<light-switch-node-id>` due to use this `<light-switch-node-id>` for
189+
light-switch) for each of them:
187190
188191
```bash
189192
$ ./chip-tool tests TestGroupDemoConfig --nodeId <lighting-node-id>
190193
```
191194
192-
6. Add Binding commands for group multicast:
195+
4. Add Binding commands for group multicast:
193196
194197
```bash
195198
$ ./chip-tool binding write binding '[{"fabricIndex": 1, "group": 257}]' <light-switch-node-id> 1

0 commit comments

Comments
 (0)