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: _includes/docs/reference/coap-api.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,13 @@
7
7
8
8
[CoAP](https://en.wikipedia.org/wiki/Constrained_Application_Protocol) is a light-weight IoT protocol for constrained devices. You can find more information about CoAP [here](https://tools.ietf.org/html/rfc7252).
9
9
CoAP protocol is UDP based, but similar to HTTP it uses request-response model.
10
-
CoAP observes [option](https://tools.ietf.org/html/rfc7641) allows to subscribe to resources and receive notifications on resource change.
10
+
CoAP Observe [Option](https://tools.ietf.org/html/rfc7641) allows subscription to resources and receiving notifications on resource change.
11
11
12
12
ThingsBoard server nodes act as a CoAP Server that supports both regular and observe requests.
13
13
14
14
### Client libraries setup
15
15
16
-
You can find CoAP client libraries for different programming languages on the web. Examples in this article will be based on [CoAP cli](https://www.npmjs.com/package/coap-cli).
16
+
You can find CoAP client libraries for different programming languages on the web. The examples in this article will be based on [CoAP cli](https://www.npmjs.com/package/coap-cli).
17
17
In order to setup this tool on Linux or macOS, you can use the following command:
18
18
19
19
```bash
@@ -33,7 +33,7 @@ CoAP cli does not support query parameters. If you require to use query paramete
33
33
34
34
### CoAP Authentication and error codes
35
35
36
-
We will use *access token* device credentials in this article and they will be referred to later as **$ACCESS_TOKEN**.
36
+
In this article, we will use *access token* device credentials in this article and they will be referred to later as **$ACCESS_TOKEN**.
37
37
The application needs to include **$ACCESS_TOKEN** as a path parameter into each CoAP request.
38
38
Possible error codes and their reasons:
39
39
@@ -115,16 +115,16 @@ Where **1451649600512** is a [unix timestamp](https://en.wikipedia.org/wiki/Unix
115
115
Below are examples of commands for publishing different types of telemetry data.
116
116
117
117
{% if docsPrefix == null %}
118
-
Don't forget replace <code>demo.thingsboard.io</code> with your host and <code>$ACCESS_TOKEN</code> with your device's access token. In this example, hostname reference live demo server.
118
+
Don't forget to replace <code>demo.thingsboard.io</code> with your host and <code>$ACCESS_TOKEN</code> with your device's access token. In this example, the hostname references live demo server.
119
119
{% endif %}
120
120
{% if docsPrefix == "pe/" %}
121
-
Don't forget replace <code>$THINGSBOARD_HOST_NAME</code> with your host and <code>$ACCESS_TOKEN</code> with your device's access token. In this example, hostname reference your local installation.
121
+
Don't forget to replace <code>$THINGSBOARD_HOST_NAME</code> with your host and <code>$ACCESS_TOKEN</code> with your device's access token. In this example, the hostname references your local installation.
122
122
{% endif %}
123
123
{% if docsPrefix == "paas/" %}
124
-
Don't forget replace <code>$ACCESS_TOKEN</code> with your device's access token.
124
+
Don't forget to replace <code>$ACCESS_TOKEN</code> with your device's access token.
125
125
{% endif %}
126
126
{% if docsPrefix == "edge/" %}
127
-
Don't forget replace <code>$THINGSBOARD_EDGE_HOST_NAME</code> with your host and <code>$ACCESS_TOKEN</code> with your device's access token. In this example, hostname reference your local installation.
127
+
Don't forget to replace <code>$THINGSBOARD_EDGE_HOST_NAME</code> with your host and <code>$ACCESS_TOKEN</code> with your device's access token. In this example, the hostname references your local installation.
128
128
{% endif %}
129
129
130
130
**Example 1**. Publish data as an object without timestamp (server-side timestamp will be used) using data from [**telemetry-data-as-object.json**](/docs/reference/resources/telemetry-data-as-object.json) file.
@@ -481,7 +481,7 @@ The "`B`" options stands for break (the operation will be break after desired ti
481
481
482
482
- Save the "[rpc-response.json](/docs/reference/resources/rpc-response.json)" file to your PC;
483
483
484
-
- In the second terminal window simulate send a response from the device to the server:
484
+
- In the second terminal window simulate sending a response from the device to the server:
485
485
486
486
{% if docsPrefix == null or docsPrefix == "pe/" %}
0 commit comments