so inject a timestamp, enable keep connection alive, and it should continue to listen for these events that the NVR is posting?
I tried this and I get a non-http Transport requested? the full URL is http://ip_addr:port/cgi-bin/eventManager.cgi?action=attach&channel=0&codes=[VideoMotion]
And what are you doing in command promp? use exec as suggested earlier if you want to command prompt.
ISAPI is internet security application processing interface, basically an api for NVR's and other security stuff. If your device supports it (my NVR has a check box in config to enable isapi) you can then possibly use node-red-contrib-hikvision-ultimate.
maybe these may help also https://flows.nodered.org/search?term=Dahua
I use an HTTP Request Node to talk to a Router that I was given a Curl commend for. I went through some pain, but was ably helped by people on the Forum in this thread.
With the exec node, I've tried the exact command that I use in CMD prompt. I can see the process is running but I get no output from the exec node when I walk in front of the camera (i.e. motion detected). The output comes when I kill the process.
I then tried spawn mode, but the only output I am getting is from port 2, however it's just a bunch of random numbers all the time every 1s. No output from any other ports.
Where as if the curl command is running in CMD prompt, I get an output everytime motion is detected.
Thanks for the reply - I tried the daemon node with the curl command above in the "Command" field. I sent a msg.start and it returns a payload of -2 on the 3rd output then "STOPPED" appears under the node.
Ok so I got the curl comamnd to work with node-red-node-daemon.
When the node first initiates, I can see the print out from the curl command, but only on port 2. Shouldn't this be outputting on Port 1? Executing the command in terminal displays this information on the terminal itself, which comes from Std Out. I thought Port 2 is used for Std Error?
Anyways - instead of returning the msg content, I am getting:
"{ [319 bytes data]"
in the debug window.
The output from the command should look like this: