detection.door.hijack (Lock hijack alarm)
detection.door.hijack: Lock hijack alarm
detection.door.hijack · device scope · message query permission Alarm
What it does
Reported on lock hijack. After subscribing to capabilityEvent, see Receive device messages and setMessageCallback · Event catalog · Common payload.
Reported fields
Fields inside outputData. Platform fields are described in Overview and common payload.
| Name | Description | Type | Required | Values |
|---|---|---|---|---|
type | type | enum | no | 0；1；2；3；4 |
keyId | keyId | int | no | 0-999999, step 1 |
Example
{
"msgType": "detection.door.hijack",
"deviceId": "TESTIPC000012345",
"productId": "56WGTET2",
"outputData": {
"type": "0",
"keyId": 0
},
"time": 1673406989,
"localTime": "20230111T111629",
"alarmId": "116257862023505xxxx"
}
Minimum permission
The administrator does not need an extra permission on a device they bound. A shared device needs the alarm-message permission. A bound sub-user does not. A sub-account needs Alarm. List and search APIs filter out events you are not allowed to see.