Skip to content
CC2 Device Documentation

MQTT Uplink Messages

title: Uplink Messages description: Data the CC2 device reports to the backend over MQTT. sidebar: order: 3

Uplink messages are sent from the device to the backend. They report real‑time state, sensor readings, alert status, and user‑driven app/widget events.

The device sends uplink data automatically on state change, at a configurable periodic interval (devcfg.core.update_period_mins), or immediately when you request a value by sending null for a devdata key in a downlink message.

{
  "devdata": {},
  "app": {},
}

Device data

Section titled “Device data”

Dynamic values that describe the device’s current state. Each field is sent automatically on change or can be fetched on demand by requesting it with a null value downlink.

Group Key path
Core State devdata.core
Alert State devdata.alert
Power devdata.power
Firmware Info devdata.fw
UI State devdata.ui
Audio Results devdata.audioin / audioout
BLE Scan Results devdata.blescan
Sensors devdata.temp / accel
NFC & Smartcard devdata.nfc / iso7816
Time devdata.time
Network State net.<name>.state, wifi/mqtt/ble flags

App

Section titled “App”

Widget value changes and user‑interaction events. The device reports when a widget value is updated (e.g., a button was pressed, a message was marked read) so the backend can stay in sync.

Group Content Page
Widget Value Reports Current value of a widget sent on change or on request app index
Msglist Events isRead updates, button presses, delete confirmations msglist
Section titled “Related”