Duress Test DV (duresstest.json)
Interactive preview & JSON source
Section titled “Interactive preview & JSON source”[!NOTE] Screenshot Placeholder: High-resolution rendering of this DataView on the CC2 e-paper display will be uploaded here.
// Raw DataView JSON payload scaffold (will be updated with full JSON){"id": "duresstest","name": "duresstest DataView","pages": []}Guides a user through a self‑check: pull the duress, verify that the server received the alert, confirm their location, and checkout the badge.
File: /dvs/duresstest.json
Page 1: self check (id: "1")
Section titled “Page 1: self check (id: "1")”| Widget | Type | Behaviour |
|---|---|---|
SELF CHECK |
static | Title |
Please pull the duress now |
static | Instruction |
response |
dynamic | Shows server confirmation status |
Page 2: location confirmation (id: "2")
Section titled “Page 2: location confirmation (id: "2")”| Widget | Type | Behaviour |
|---|---|---|
is this your location? |
static | Prompt |
location |
dynamic | Current detected location |
No |
button | Sends updateRemote (error) |
Yes, checkout badge |
button | Runs alloc_local |
Page 3: error (id: "error")
Section titled “Page 3: error (id: "error")”| Widget | Type | Behaviour |
|---|---|---|
devdata.fw.device_id |
dynamic | Device ID display |
Oops |
static | Error message |
seems like sth. went wrong... |
static | Recovery instructions |
duress_app/ MQTT interaction
Section titled “duress_app/ MQTT interaction”The duress pull triggers a server notification. The response widget
shows confirmation. The location widget likely comes from the portal
or BLE zone detection.
Related
Section titled “Related”- Identity widgets – not used, but similar concept
- Dynamic devdata widgets –
devdata.fw.device_id - allocated_home DV – similar checkout flow