App Downlink
The app downlink section controls what the user sees on the device
screen. You can send new widget values, trigger UI actions, and manage
message lists.
Commands target a named Device View (DV) and can include both
data and actions in the same message.
{ "app": { "<dvname>": { "data": { "<widgetname>": <value> }, "actions": [ { "a": "<action>", "p": "<param>" } ] } }}| Group | Content |
|---|---|
| Actions | netact, beep, vibr, led, show, hide, gotoWidget, updateLocal, updateRemote, updateOutput, … |
| Msglist Protocol | Add, update, delete messages; TLV encoding for BLE |
Related
Section titled “Related”- Downlink Commands — the full downlink directory
- Uplink App Events — how the device reports button presses and message reads
- Configuration Files — how DVs are defined in allocdata
---
```mdx---title: App Uplinkdescription: Widget value changes and user interactions reported by the CC2.sidebar: order: 2---
# App Uplink
The `app` uplink section contains events sent from the device when theuser interacts with the UI. This includes widget value changes (e.g., abutton press), message list events (mark read, delete), and theresponse from a `fget` devwork action.
```json{ "app": { "<dvname>": { "<widgetname>": { "id": "<message id>", "<field>": <new value> } } }}| Group | Content |
|---|---|
| Widget Value Reports | Current widget value sent on change or on request |
| Msglist Events | isRead updates, button press payloads, delete confirmations |
Related
Section titled “Related”- Uplink Messages — the full uplink directory
- Downlink App Commands — how to push updates to the device
- Msglist Protocol (Downlink) — adding and updating messages