Available Actions

An OTAA device needs to have an AppKey set in both the LoRa Server Stack and the device to allow automatic join and activation.


The network key (or application key) (nwk_key) is a 128 bits AES-128 key and needs to be set both at the application server and the end device. The key can be auto-generated by the LoRaWAN device driver by sending in the "generate" (string) value.

The result of the action is sent up as an event and will give you the (generated) values for network and application keys that can then be used at the end device too.

The generated key(s) can be retrieved using the getDeviceKeys action.


This retrieves the device keys.


This will delete the device keys and, therefore, de-activate the device.


The activation details can be retrieved using the getActivation action.


Messages to be sent to the end-device can be added to the queue by running this action.

The f_port (frame port) needs to be specified. The message itself either needs to be specified as base64 encoded "data" or as a "jsonObject" string.

The device driver has been coded to handle both types, regardless of whether the device profile has an encryption/decryption codec set (see Chirpstack Device Profiles for more details).

The device driver will check the device profile to see if a codec is in use and "convert" from one type to another. Apart from a codec a "conversion template" can be used to convert from/to array and object formats. See the Payload Conversion page for more details.

Note: equivalent API endpoint (no data/jsonObject conversion takes place, this is "raw"):

POST /drivers/lorawan/devices/{device-id}/queue


This will list all outstanding, queued items.

Note: equivalent API endpoint:

GET /drivers/lorawan/devices/{device-id}/queue 


This will flush (delete) all outstanding, queued items.

Note: equivalent API endpoint:

DELETE /drivers/lorawan/devices/{device-id}/queue