APIs Device to Cloud Lorawan Devices Prepare devices

On this page you’ll find connection settings so your devices and gateways can connect to the Device to Cloud infrastructure.

For DMO configuration of the LORIOT account, application, and network resources, see Configure system .

Connect LoRaWAN Gateways

LoRaWAN gateways connect directly to the LORIOT network server over IP — not to D2C. There is no gateway-level TLS or IP configuration required in D2C.

To make D2C aware of a gateway, you provision it through the DMO API (see Onboard devices ). D2C then registers the gateway in the linked LORIOT network using the dtiot:lorNk reference from the provisioning labels.

The configuration parameters, that you have to specify, depends on the vendor, type and used packet forwarder on your gateway.

Please contact our D2C support to get a template for your specific gateway.

Gateway connection summary:

StepWhereWhat
1Gateway hardwareConfigure the LoRaWAN packet forwarder to point to the LORIOT server address
2LORIOT UIGateway appears in the LORIOT network once it connects
3D2C DMO APIProvision the gateway with the loriot-destination label pointing to myLoriotAccount/myLoriotNetwork

Connect LoRaWAN Devices

LoRaWAN devices communicate wirelessly with gateways using the LoRa radio protocol. No IP address or TLS configuration is required on the device for D2C.

D2C supports OTAA (Over-the-Air Activation) for LoRaWAN 1.0 and LoRaWAN 1.1. ABP (Activation by Personalization) is not supported.

Collect the following OTAA parameters from your device before provisioning:

ParameterDescription
DevEUI64-bit unique device identifier — printed on the device or available from the manufacturer
JoinEUI / AppEUI64-bit application identifier (called AppEUI in LoRaWAN 1.0, JoinEUI in LoRaWAN 1.1)
AppKey128-bit root key used for OTAA join procedure

These parameters are provided in the provisioning request labels (see Onboard devices ).

After provisioning, the device joins the network automatically through the LORIOT join server using OTAA. No manual session key configuration is needed.

Next step

Use the API to onboard your devices to Device to Cloud.