ZoneMinder Forums

Does anyone have a working time lapse solution?

The Amcrest supposedly are rebranded Dahua (confirm, deny anyone?)

Did you try the Amcrest script? I have done no comparison of their API docs, so they may be completely different.

I have a very reliable 1.30.0 that's been running for a couple years. Is there an upgrade path or do I need to remove and reinstall as though new?

Configuration is explained in the documentation here https://zoneminder.readthedocs.io/en/1.34.5/userguide/cameracontrol.html The only tricky part for the Amcrest is the control address. Open the monitor, go to control tab, select controllable, enter "login:password@cameraIP:80" in the con...

I have no idea how the referenced "smartthings" work....but I used guardline passive IR and a simple shunt board with USB inteface. The USB is continuously polled by a bash script, and when it triggers, the built in ZM API is called forcing alarms where I want them. So how you solve this d...

Isaac figured out what was broken in the Amcrest PTZ script. My understanding is the fix will be in the latest new version, or you can DL it directly from here. This new version is working on my 1.34.1 with very new Amcrest cameras.

Within the control scripts, there are debug statements: Debug('Some text or variable string value'); Attempts to enable this debugging output by turning on debugging in the logging options and setting the "LOG_DEBUG_TARGET" value to the control script name with prepended underscore and no ...

upgrade to 1.34.1 seems to have eliminated this socket error.

Posted here: viewtopic.php?f=40&t=28987

Posted to git, see https://github.com/ZoneMinder/zoneminder/issues/2816

ZM 1.34.1, control script "Amcrest HTTP API" results in error 401 not authorized when attempting any PTZ function. More discussion here, but seems to be in wrong forum, so reposted in this one.

Testing ZM v1.34.0 now... Unfortunately I am now getting: Camera control command FAILED: '401 Unauthorized' for URL user:pass@host/cgi-bin/ptz.cgi?action=stop&code=Right&channel=0&arg1=0&arg2=1&arg3=0 I upgraded to 1.34.1 and using the new "Amcrest HTTP API" control I ...

I believe the control address is supposed to be "login:password@ip_address:port" and the control device is supposed to be the serial number of the camera.

ZM v1.32.3 (manually pulled Amcrest_HTTP.pm from github) I have been unable to get this new Amcrest script to work with my 1.32.3, but I am getting a different error than you. I think Im going to upgrade to 1.34.1 and see how it works. My understanding is that 1.32.3 to 1.34.X is a pretty seamless ...

What version of ZM?

I changed the name of the file when this script was installed.

I hope to upgrade to 1.34 ASAP. I hope it fixes this socket issue.