New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help configuring script #2
Comments
Ohh, and just to make sure you get a direct ping @waynieack |
The video loss message is the normal message you will get when nothing has As for the settings on the camera, all I have on my cameras is the enable Are you not seeing the event type message change in the xml stream when the On Jul 19, 2016 9:27 PM, "Joshua Ruehlig" notifications@github.com wrote:
|
I don't even see the PIR eventType in my xml message. Above is exactly what I see when I use curl to fetch the URL, but repeatedly until I stop the curl command. Do you think my output is getting cut off in curl and your script at the "--boundary". Gonna experiment with some other programs that pull from hikvision camera's alertStream to verify if they have the same issue. |
Yeah, the stream continuously sends the video loss XML until another event It sounds like a bug with the camera, try unchecking all the Maybe try changing the schedule and chaining it back, the schedule is the I have these 2 cameras and they send the events ok, if i do a curl on the Model DS-2CD2432F-IW Model DS-2CD2332-I On Thu, Jul 21, 2016 at 6:27 PM, Joshua Ruehlig notifications@github.com
|
ok, sounds good. I'll try motion detection / and adjusting schedules / rebooting. |
well the motion and the line detection do show on the stream. But the PIR still does not. Know anyplace else I can get the latest firmware? |
Well in the process of trying to upgrade my unit 2432 to v5.3.0 it got bricked. Now gotta get it working again =/ |
well got my unit unbricked using this post! now back to the issue at hand. my unit does not seem to output anything related to PIR to the alertStreaming stream. do you mind posting the output you get when your PIR triggers an event. I'm able to query it at a different URL, but don't get anything from the stream. |
specifically, I was able to connect to the URL listed here.. |
This is how I have mine configured. [image: Inline image 1] On the http stream, I see this when the PIR is triggered.
As for the /IO/outputs/1/status, its not an http stream so it would not I tried linking my PIR event to the alarm output, but I don't see the _Wayne On Fri, Jul 22, 2016 at 3:51 AM, Joshua Ruehlig notifications@github.com
|
Yeah, I realize the IO URL isn't the same. No idea why my thing isn't working =[ I'll check on the ipcamtalk forum, maybe I do need to get to V5.3.0 without bricking it. |
curl http://user:password@192.168.1.1/ISAPI/Event/notification/alertStream If you see the stream, then your curl command is fine. The problem is for On Fri, Jul 22, 2016 at 10:24 AM, Joshua Ruehlig notifications@github.com
|
Alright it was an issue with the firmware that was hacked on their. Hacked the camera partitions and put back the 5.3.0 chinese firmware and PIR events are now working. Excited to try out your script |
By the way, the script works great on my FreeBSD system, connected to my Hikvision 2432 with the original Chinese firmware using the PIR sensor =] This will be even more awesome once Zoneminder has video support, so my server won't need to use CPU converting the video stream to JPEGs or analysing it! |
Glad to hear it! _Wayne On Mon, Sep 5, 2016 at 12:36 PM, Joshua Ruehlig notifications@github.com
|
Hello, thank you for your work on this program! I am starting this script fine, but it seems to not be receiving PIR events from my Hikvision 2432 camera. I know the camera is triggering its own events as verified by the "Audible Warning", but I'm not sure if the camera is proving the needed XML.
When I
curl -s -S -N -u zmuser:zmpass http://192.168.1.45/ISAPI/Event/notification/alertStream
I get the following which keeps updating.Here are my camera settings.
Any suggestions?
The text was updated successfully, but these errors were encountered: