Configure motion detector feature

Configures motion detector feature

This feature is available only on AT-07l, AT-10, AT-10L. SD-card is required

application/json

Request Body required

• enable boolean required
• recording_time integer required

  Possible values: >= 5 and <= 120

  The video recording time in seconds

• work_time_from string required

  Time interval in which the movement will be recorded. Start time in 24-hours format

• work_time_to string required

  Time interval in which the movement will be recorded. End time in 24-hours format

• ip_cam_uuid_1 string required

  Camera UUID that will be recorded when the first sensor is triggered. Can by empty string when camera isn't specified.

• ip_cam_uuid_2 string required

  Camera UUID that will be recorded when the second sensor is triggered. Can by empty string when camera isn't specified.

• ip_cam_uuid_3 string required

  Camera UUID that will be recorded when the third sensor is triggered. Can by empty string when camera isn't specified.

• ip_cam_uuid_4 string required

  Camera UUID that will be recorded when the fourth sensor is triggered. Can by empty string when camera isn't specified.

• is_sd_card_mounted boolean

  SD-card mounting status. Motion sensor can be configured if SD-card is mounted.

Responses

• 200
• 400
• 401

---

OK. If SD-card isn't mounted in the device, the warning will arise and the feature won't work

application/json

• Schema
• Example (from schema)
• O K
• W A R N I N G

---

Schema

• status string

  Possible values: [OK, WARNING]

• warning string

{
  "status": "OK",
  "warning": "SD-card isn't mounted. The feature won't work"
}

{
  "status": "OK"
}

{
  "status": "WARNING",
  "warning": "SD-card isn't mounted. The feature won't work"
}

Validation error. Required fields are not provided.

• Missed json body or wrong param. Response sample:

  "error": "Wrong JSON body"

• Required field is not provided. Response sample:

  "error": "Wrong JSON body: no value for `param`"

where param - is a required field that was not provided

• Field was of the wrong type. Response sample:

  "error": "Wrong JSON body: value `param` was of the wrong type"

where param - is a field of the wrong type

application/json

• Schema
• Example (from schema)
• Wrong recording_time
• Wrong work_time_to
• Wrong work_time_from
• Wrong ip_cam_uuid_1
• Wrong ip_cam_uuid_2
• Wrong ip_cam_uuid_3
• Wrong ip_cam_uuid_4
• Base
• No value
• Wrong param type

---

Schema

• error string

{
  "error": true
}

{
  "error": "Wrong recording_time. Available values are in range: [5, 120]"
}

{
  "error": "Wrong work_time_to"
}

{
  "error": "Wrong work_time_from"
}

{
  "error": "Wrong ip_cam_uuid_1"
}

{
  "error": "Wrong ip_cam_uuid_2"
}

{
  "error": "Wrong ip_cam_uuid_3"
}

{
  "error": "Wrong ip_cam_uuid_4"
}

{
  "error": "Wrong JSON body"
}

{
  "error": "Wrong JSON body: no value for `param`"
}

{
  "error": "Wrong JSON body: value `param` was of the wrong type"
}

Unauthorized request. Log In

application/json

• Schema
• Example (from schema)
• Log In

---

Schema

• error string

{
  "error": "Log In"
}

{
  "error": "Log In"
}

Loading...