Skip to content
CC2 Device Documentation

Uplink Messages

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.

// Uplink messages use the same envelope as downlink.
// The device populates devdata and app sections.
{
  "devdata": {},   // dynamic device state and sensor values
  "app":     {}    // widget value changes and user interactions
}

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.

GroupKey path
Core Statedevdata.core
Alert Statedevdata.alert
Powerdevdata.power
Firmware Infodevdata.fw
UI Statedevdata.ui
Audio Resultsdevdata.audioin / audioout
BLE Scan Resultsdevdata.blescan
Sensorsdevdata.temp / accel
NFC & Smartcarddevdata.nfc / iso7816
Timedevdata.time
Network Statenet.<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.

GroupContentPage
Widget Value ReportsCurrent value of a widget sent on change or on requestapp index
Msglist EventsisRead updates, button presses, delete confirmationsmsglist
Section titled “Related”