IPC-HDB4300C HTTP API - Get current alarm state

tangent said:

I was looking at a newer API doc (which is from 2014): DAHUA_HTTP_API_FOR_IPC&SD-V1.40
It's in section, 15.1.1 GetVideoAnalyseRule page 105.

Click to expand...

Roman Gaufman said:

I can't seem to find 1.40, any chance you could share it?

Click to expand...

Roman Gaufman said:

I have 2 trip wire rules, one for entering and one for leaving. But the output from this command:

wget 'http://admin:admin@192.168.1.108/cgi-bin/eventManager.cgi?action=attach&codes=[VideoMotion,VideoLoss,VideoBlind,AlarmLocal,CrossLineDetection,CrossRegionDetection,LeftDetection,TakenAwayDetection,VideoAbnormalDetection,FaceDetection,AudioMutation,AudioAnomaly,VideoUnFocus,WanderDetection,RioterDetection,ParkingDetection,MoveDetection,MDResult]' -O events.log​

Looks like this:

-- myboundary
Content-Type: text/plain
Content-Length:46
Code=CrossRegionDetection;action=Start;index=0
​

Which rule is that? - the index is always 0 it seems no matter what. Grr. Why is it so difficult to just get a stream of events from a camera... - each rule has a name, why not just list the name Dahua...

Click to expand...

http://<ip>/cgi-bin/configManager.cgi?action=getConfig&name=VideoAnalyseRule

Roman Gaufman said:

Ooooh, I found this: ftp://92.FTP/Dahua/.../dahua_http_api_for_ipc_v1.56.pdf

Click to expand...

tangent said:

use code bb tags for nicer formatting
Start by running this:

Code:

http://<ip>/cgi-bin/configManager.cgi?action=getConfig&name=VideoAnalyseRule

You probably have to set EventHandler for your rules using 15.1.2 SetVideoAnalyseRule, and then subscribe to the events.

Several API versions ago, you could specify an alarm server and the cameras could be set to just push events out but they deprecated that functionality.

Click to expand...

-- myboundary
Content-Type: text/plain
Content-Length:38
Code=LeftDetection;action=Stop;index=0


-- myboundary
Content-Type: text/plain
Content-Length:44
Code=CrossLineDetection;action=Start;index=0


-- myboundary
Content-Type: text/plain
Content-Length:45
Code=CrossRegionDetection;action=Stop;index=0


-- myboundary
Content-Type: text/plain
Content-Length:43
Code=CrossLineDetection;action=Stop;index=0


-- myboundary
Content-Type: text/plain
Content-Length:46
Code=CrossRegionDetection;action=Start;index=0


-- myboundary
Content-Type: text/plain
Content-Length:39
Code=LeftDetection;action=Start;index=0


-- myboundary
Content-Type: text/plain
Content-Length:45
Code=CrossRegionDetection;action=Stop;index=0


-- myboundary
Content-Type: text/plain
Content-Length:38
Code=LeftDetection;action=Stop;index=0

nayr said:

link?

Click to expand...

nayr said:

suck, I get a 400 bad request response.. on all my Dahuas.. this must be something new.

Click to expand...

tangent said:

NodeJS Module: node-dahua-api

P.S. I've found my google-fu again and 1.56 above from 2015 is the latest version I can locate as well

Click to expand...

Putimir said:

Hi, nayr, do you have anything new on this subject? I'm currently having a support ticket open with Synology support team (i'm using Synology Surveillance Station and if I set up my Dahuas with the "supported" "native" profile, none of the alarms are picked up by the SS - it's working though if I'm using ONVIF profile), they concluded, that the problem lies in the fact, that the Dahuas respond with HTTP/400 after a /cgi-bin/eventManager.cgi?action=attach&codes=[VideoMotion] query...

Click to expand...

Roman Gaufman said:

I tried to set codes to "Exit" "Intrusion" etc, as specified in my rule names, but this has no effect, I see the CrossLineDetection, etc, but not my specific rules, so it's impossible to tell which event applies to which rule, hmm. Any ideas?

Click to expand...

tangent said:

Did you ever figure out a way to identify which rule of the same type is triggered?
Looking at API 2.12 and I don't see any way to get this info either. Thought I'd ask before I dust off wireshark.

Click to expand...