You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/controller.rst
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,10 +36,10 @@ The controller should support the following features:
36
36
The ``invoke-cmd`` command is used for sending cluster commands to the end-devices. It utilizes a ``cluster_command`` class to establish the sessions and send the command packets. The class constructor function could accept two callback inputs:
37
37
38
38
- **Success callback**:
39
-
This callback will be called upon the reception of the success response. It could be used to handle the response data for the command that requires a reponse. Now the default success callback will print the response data for GroupKeyManagement, Groups, Scenes, Thermostat, and DoorLock clusters. If you want to handle the response data in your example, you can register your success callback when creating the ``cluster_command`` object.
39
+
This callback will be called upon the reception of the success response. It could be used to handle the response data for the command that requires a response. Now the default success callback will print the response data for GroupKeyManagement, Groups, Scenes, Thermostat, and DoorLock clusters. If you want to handle the response data in your example, you can register your success callback when creating the ``cluster_command`` object.
40
40
41
41
- **Error callback**:
42
-
This callback will be called upon the reception of the failure response or reponse timeout.
42
+
This callback will be called upon the reception of the failure response or response timeout.
43
43
44
44
^^^^^^^^^^^^^^^^
45
45
@@ -169,11 +169,11 @@ inputs:
169
169
- **Event report callback**:
170
170
This callback will be invoked upon the reception of the event report for subscribe-event commands.
171
171
172
-
- **Subscribe done callback**:
173
-
This callback will be invoked when the subscription is terminated or shutdown.
172
+
- **Subscription established callback**:
173
+
This callback will be invoked when the subscription is established successfully.
174
174
175
-
- **Subscribe failure callback**:
176
-
This callback will be invoked upon the failure of establishing CASE session.
175
+
- **Subscription terminated callback**:
176
+
This callback will be invoked when the subscription is terminated or shutdown.
0 commit comments