Skip to content
CC2 Device Documentation

unallocdata.json

unallocdata.json is loaded when the device is in the unallocated state (no user assigned). It provides a minimal or default setup that runs before any user data is present.

The file has exactly the same structure as allocdata.json. The only difference is when it is loaded — unallocated vs. allocated state.

{
  "result": "true",
  "httpResponseCode": 200,
  "data": {
    "global": {
      "dev": {
        "wifi": {
          "connect_retry_seconds": 60,
        },
      },
    },
    "network": {
      "networkOrder": ["k1", "q1"],
    },
    "user": {
      "visitor": "",
      "apps": {
        "unallocated_home": {
          "id": "home",
          "src": "local",
        },
        "syscfg": {
          "id": "syscfg",
          "src": "local",
        },
      },
    },
    "apps": {},
    "dicts": ["config/tlv_down.json", "config/tlv_up.json"],
  },
}

All sections (data.global, data.network, data.user, data.apps, data.dicts) follow the exact same rules described in allocdata.json. Refer to that page for field‑by‑field documentation.

Typical differences from allocdata.json

Section titled “Typical differences from allocdata.json”
  • No user‑specific data — data.user.visitor is usually empty and the apps list contains only system DVs (syscfg, sysinfo, sysctrl, a basic home).
  • Simpler network order — often a single Wi‑Fi network is used while the device waits for an allocation.
  • Smaller dicts list — only the TLV mapping dictionaries are loaded; location/name dictionaries are typically provided later when the device is allocated.
Section titled “Related”