Skip to content
CC2 Device Documentation

MQTT Downlink Commands

title: Downlink Commands description: All commands the backend can send to the CC2 device over MQTT. sidebar: order: 2

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": {},
  "devwork": [],
  "app": {},
}

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.

Group Key path
Core devcfg.core
Firmware & Provisioning devcfg.fw
UI & Display devcfg.ui
Alert Triggers devcfg.alert
Audio Out / In devcfg.audioout / audioin
BLE (nrf53) & Peripheral (nrf52) devcfg.ble / bleperi / blescan
WiFi, Scan, ALP, CCX devcfg.wifi / wifiscan / wifialp / wificcx
NFC & Smartcard devcfg.nfc / apdumgr / mifare / iso7816
LEDs devcfg.led
Vibration devcfg.vibr
Accelerometer devcfg.accel
Rules devcfg.rules
Time devcfg.time
LoRa Peripheral devcfg.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.

Group Action type Page
File Operations fdld, fcre, fapp, fmv, fdel, fmkd, ffmt, fget file-operations
Device Actions reboot, debug, alloc_local, return_local device-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.

Group Content Page
Actions netact, beep, vibr, led, show, hide, gotoWidget, updateLocal, updateRemote, updateOutput, … actions
Msglist Protocol Add, update, delete messages; TLV encoding msglist
Section titled “Related”