Overvis Ownership Challenge

The challenge confirms physical access to the TR-100E when connecting the device to Overvis using a PIN code. The code is displayed on the device for no more than 5 minutes. The user can enter this code in Overvis or confirm the connection by selecting Yes on the TR-100E.

The code is runtime state: it is not saved to Flash/EEPROM and is not returned by the status API.

POST /api/service/challenge/set/

Set, replace, or clear the challenge.

Access: WireGuard only, Bearer/implicit (user). A request from the LAN returns 403 ERROR_NO_ACCESS.

Set

{
  "code": "001274"
}

code is required and must contain 1 to 12 ASCII digits. The code is passed as a string to preserve leading zeros. A new request replaces any previous challenge and restarts the 300-second timer.

Response 200:

{
  "status": "pending",
  "remainingSec": 300
}

Clear

{
  "code": null
}

Response 200:

{
  "status": "idle",
  "remainingSec": 0
}

An empty body or invalid JSON returns 400 ERROR_API_PARSING. A missing field, an incorrect type, an empty string, or a code that is too long or contains non-digit characters returns 400 ERROR_INVALID_ARGUMENT. A validation error does not change the current challenge.

GET /api/service/challenge/status/

Retrieve a consistent snapshot of the challenge state.

Access: WireGuard only, Bearer/implicit (user). A request from the LAN returns 403 ERROR_NO_ACCESS.

Response 200:

{
  "status": "accepted",
  "remainingSec": 247
}

status	Meaning
idle	The challenge is absent or has been cleared
pending	The code is displayed, but no physical response has been received yet
accepted	The user selected Yes on the TR-100E
rejected	The user selected No on the TR-100E

remainingSec decreases from 300 to 1 for pending, accepted, and rejected; it is 0 for idle. The user’s response neither restarts nor stops the timer. After the original 300 seconds, the device automatically resets the challenge to idle.

After Yes is selected, the TR-100E displays a waiting screen until Overvis reads accepted and sends code: null. Clearing the challenge completes the UI flow and returns to the main screen.

If the user confirms ownership by entering the code in Overvis, the cloud service compares it with its original value and, after successful verification, sends code: null to remove the prompt from the display.