device typethe form will adapt the device definition parameters to its specific requirements that must be provided to the system in order to create the device profile:
PBKDF2 SHA256with a 32 bytes salt generated with
PRNGand a non-depreciable amount of iterations.
API EXPLORER. You can access to this screen over the Device Dashboard, by clicking on the small blue button called
led, for controlling the
BUILTIN_LED, and one output resource, called
millisto extract the current "millis" value of the device, as defined in the following code. Notice that a resource name can be any arbitrary text to identify the underlying resource, as they are not tied to any constant defined in the platform.
Runbutton will execute your resource, i.e., forcing a read from a sensor, calling the
millis()function, or sending a new state for the actuator, depending on the resource type (input or output).
POSTmethod to send values to the device, or using a
GETmethod to read information from the device.
Run, and see the output reported by the device. This example also emphasizes how the resources work, as they are not just static values, but callbacks you can call with any input or output value.
Show Querybutton. This provides information about the method type, URL, content type, request body, and response body. You can also click on
Curl, so you can copy the command to interact with your device directly from your console. The above example is translated to the following REST API call:
Addon the right of the box. Then, a modal window will appear, where you can configure different parameters:
callback detailsas shown in the image below:
Callback Detailscontext as shown in the image below:
Authorization Headermust be included 9in your HTTP request as shown in the example below:
get_propery()commands as shown in the examples below: