CoAP operates under a similar request/response model as HTTP; a CoAP end-point in the role of a client sends one or more CoAP requests to a server, which services the requests by sending CoAP responses. Unlike HTTP, requests and responses are not sent over a previously established connection but exchanged asynchronously over CoAP messages.
The coap.acknowledge trigger action will execute based on the CoAP response received. The Response Code drop-down is the various responses received with the CoAP acknowledges.
Action
This trigger action is found under the Networking heading.
Canvas
When dragged onto the canvas, the appearance of the action is a rectangle with two routing points.
The left routing point (red) is the failure route. This route will be taken if there is an error during execution.
The right routing point (green) is the success route. This route will be taken if action executes successfully.
Form
Parameters
| Name | Type | Required | Descriptions |
|---|---|---|---|
| Response Code | String | Yes | The response code to which server needs to respond. |
| Payload | Binary | Yes | The payload to publish can be a string or binary payload. |