- Sending messages to IoT devices using UDP, CoAP and LwM2M.
- Message for single device and bulk devices are supported.
- Schedule message to be send when we receive a message from the device or on LwM2M registration and update events (requestMode
- Cross-protocol trigger: sending a message from the device with any protocol to the 1NCE OS endpoint will trigger sending scheduled messages for all protocols to the device
- Possibility to cancel a scheduled request
- Possibility to cancel all scheduled requests for a device
- See the response from the device for CoAP and LwM2M
- Possiblity to configure retries for scheduled CoAP or LwM2M messages.
- Track the status of action requests. Available values:
SCHEDULED: the request was created with requestMode
SEND_WHEN_ACTIVE. The request hasn't been sent to device and is still pending for a trigger to occur.
IN_PROGRESS: the request was created with requestMode
SEND_NOW, or was scheduled and a trigger occurred
SUCCEEDED: device responded with 2.xx response code via CoAP or LwM2M. Or message was sent via UDP (there's no validation a message via UDP was received).
FAILED: device responded with 4.xx or 5.xx response code via CoAP or LwM2M. Or an unexpected error occurred. Check the
resultDataof the request for more details.
CANCELLED: a scheduled request was cancelled via the DELETE endpoints of our API
- A maximum of 10 Messages can be scheduled per device
- Maximum 100 devices are allowed to be selected for each request
- Requests will be deleted 7 days after the creation date, independent of the status of the request.
- A maximum UDP payload size of 508 bytes
- A maximum CoAP payload size of 1024 bytes
- CoAP DTLS is currently not supported
- The maximum number of send attempts for SEND_WHEN_ACTIVE requests is 5.
Updated about 1 month ago