detection.occlusion.detected: Video occlusion detected

detection.occlusion.detected · Channel 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 video occlusion is detected. The push sets msgType to detection.occlusion.detected. Subscribe to capabilityEvent in callbackFlag. See Receive device messages, setMessageCallback, Event catalog, and Overview and common payload.

Reported fields

No extra business fields. Platform fields and thumbnails: Overview and common payload, Receive device messages.

Example

{
 "msgType": "detection.occlusion.detected",
 "deviceId": "TESTIPC000012345",
 "productId": "56WGTET2",
 "channelId": "0",
 "outputData": {},
 "time": 1673406989,
 "localTime": "20230111T111629",
 "alarmId": "116257862023505xxxx",
 "token": "f2dc8c09eeae4b5bad6abf522c93d825",
 "thumbUrl": "https://example.imou.com/pic/thumb.jpg",
 "picUrlArray": [
 "https://example.imou.com/pic/frame1.jpg",
 "https://example.imou.com/pic/frame2.jpg"
 ]
}

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/search filters out events you are not allowed to see.Video occlusion。