Duress Test DV (duresstest.json)
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