detection.tamper.detected (Tamper alarm)
detection.tamper.detected: Tamper alarm
detection.tamper.detected · device scope · message query permission Alarm
What it does
Standard pushes use capabilityEvent and this page’s msgType; some models may also emit legacy msg_type values—see device.capability.list and the event catalog.
Reported when tamper is detected. Compose event: multiple legacy idents such as temper_alarm/5100 and e_sensorAbnormal/32300 map to the same msgType detection.tamper.detected. Subscribe to capabilityEvent for pushes. See Receive device messages, setMessageCallback, Event catalog, and Overview and common payload.
Reported fields
Fields inside outputData. Platform fields are described in Overview and common payload.
Compose event: legacy and standard idents merge into one msgType; paths such as temper_alarm often use {}, while some doorbell SKUs may add optional fields:
| Name | Description | Type |
|---|---|---|
relatedRingBell | Whether a ring is linked | int 0/1 |
ringIndex | Ring index | int 0–9999 |
Example
{
"msgType": "detection.tamper.detected",
"deviceId": "TESTIPC000012345",
"productId": "56WGTET2",
"outputData": {},
"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.