Device Config Downlinks

title: Device Config description: Configure persistent device behaviour via devcfg downlink commands. sidebar: order: 1

Device Config

devcfg commands are sent from the backend to the device to change persistent settings. Most take effect immediately; a few require a reboot (noted on the individual parameter page).

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

{
 "devcfg": {
 "<group>": {
 "<param>": <value>
 }
 }
}

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`

Downlink Commands — the full downlink directory
Uplink Device Data — how the device reports current devcfg values
Configuration Files — where devcfg settings are stored in global.json and allocdata.json