CC2 Device Documentation

What is CC2?

The CC2 is an advanced, multi-network IoT hardware unit supporting WiFi, BLE, and LoRa communications. It operates on a robust state machine capable of structured memory management across dynamic allocation stages. This hub serves as the definitive technical runtime reference for developers managing edge device configurations, state lifecycles, and asynchronous MQTT telemetry payloads.

---

How to use these docs

If you are setting up infrastructure or building logic around the CC2 system, target these key paths:

• Integrators: Dive into MQTT Downlink and Uplink maps to synchronize state payloads with your backend microservices.
• Provisioners: Head directly to the Configuration Files and Network Setup rules to define bootstrap images and local runtime fallback hierarchies.
• Firmware Engineers: Audit the Device States logic engines and global Reference Tables for validation benchmarks.

---

What’s in these docs

MQTT Downlink

Commands the backend sends to the device — config, actions, widget updates. Browse downlink →

MQTT Uplink

Data the device reports back — state, sensors, alerts, scan results. Browse uplink →

Configuration Files

How global.json, allocdata.json, and unallocdata.json work together. Browse configuration →

Network Setup

WiFi, BLE, and LoRa network definitions, auth objects, and connection order. Browse networks →

Device States

The full state machine — allocated, unallocated, provisioning, error, and more. Browse states →

Reference Tables

Enums, code tables, action aliases, LED syntax, audio codes, and changelog. Browse reference →

---

Doc patterns

These docs follow four consistent page patterns. Every page you read is one of these four types.

Pattern	Purpose	Example
A — Index	Navigation hub, grouped links	mqtt/downlink/index.mdx
B — Command Group	Config namespace + all its params	dev-config/alert.mdx
C — Action	Fire-and-forget commands + responses	dev-work/file-operations.mdx
D — Uplink Data	Device-reported fields	dev-data/alert.mdx