Downlink communication
When data is sent to the device
Last updated
Was this helpful?
When data is sent to the device
Last updated
Was this helpful?
All downlink communication is requested on and managed by the Actuator API. Optionally a Destination can request and manage downlink communication as well. See Destination types to learn which destinations can support downlink communication.
After a downlink is requested on the Actuator API it is encoded. Meaning the downlink is translated to a message the device will understand. After encoding the downlink is send over the selected network to your device.
The network (and the device) will report feedback about the delivery of the downlink to the Actuator API. This information can be retrieved by the application, or the Things Connector fetches this information into your system.
Using the KPN Things Portal, you can request downlinks, and check their progress. Learn how you can send a downlink in the KPN Things Portal or read getting started on sending a downlink to a LoRa Device via Things Portal.
Since December 2020 it is also possible to directly call the Actuator API. Head on over to the API access documentation for more information!
Using our encoders the downlink request is translated to a device specific message. All available encoders are specified per device type.
Currently the following networks are supported for downlink communication:
LoRa downlink
HTTP response downlink for M2M devices
HTTP response downlink for Internet-connected devices
Some Destination types also support sending downlinks.
