Skip to content
CC2 Device Documentation

Downlink Commands

Downlink messages are sent from the backend to the device. They configure settings, request current data, trigger one-shot actions, and push widget updates to the UI.

Every downlink command fits into the same envelope. Only include the sections you need — empty objects can be omitted.

{
  "devcfg":  {},   // configure device behaviour
  "devwork": [],   // one-shot housekeeping actions
  "app":     {}    // widget data and UI actions
}

To read a config value instead of setting it, send null as the value for any devcfg key. The device will respond with the current value in an uplink message.

Device Config

Section titled “Device Config”

Persistent parameters that control the device’s behaviour. Changes take effect immediately unless stated otherwise.

GroupKey path
Coredevcfg.core
Firmware & Provisioningdevcfg.fw
UI & Displaydevcfg.ui
Alert Triggersdevcfg.alert
Audio Out / Indevcfg.audioout / audioin
BLE (nrf53) & Peripheral (nrf52)devcfg.ble / bleperi / blescan
WiFi, Scan, ALP, CCXdevcfg.wifi / wifiscan / wifialp / wificcx
NFC & Smartcarddevcfg.nfc / apdumgr / mifare / iso7816
LEDsdevcfg.led
Vibrationdevcfg.vibr
Accelerometerdevcfg.accel
Rulesdevcfg.rules
Timedevcfg.time
LoRa Peripheraldevcfg.loraperi

Device Work

Section titled “Device Work”

One-shot actions sent as an array in devwork. They perform housekeeping tasks and do not change persistent configuration.

GroupAction typePage
File Operationsfdld, fcre, fapp, fmv, fdel, fmkd, ffmt, fgetfile-operations
Device Actionsreboot, debug, alloc_local, return_localdevice-actions

App

Section titled “App”

Widget data updates and UI actions targeting a named DV. These control what the user sees and how the device responds to touch.

GroupContentPage
Actionsnetact, beep, vibr, led, show, hide, gotoWidget, updateLocal, updateRemote, updateOutput, …actions
Msglist ProtocolAdd, update, delete messages; TLV encodingmsglist
Section titled “Related”