Enable Motion Detection using Amcrest HTTP API

[tgraf2]

I am trying to enable motion detection on my camera (IP2M-841W) using the HTTP API (Revision 2.12, 2017-03-15). The get and set commands appear to be working, but motion detection does not get enabled.
Here are the steps I followed:
- get config: http://192.168.1.107:8000/cgi-bin/confi ... tionDetect
- status returned:
table.MotionDetect[0].DetectVersion=V3.0
table.MotionDetect[0].Enable=false
.....
- set config: http://192.168.1.107:8000/cgi-bin/confi ... nable=true
- status returned:
OK
At this point it appears that Motion Detect is enabled, but when I get config again:
- get config: http://192.168.1.107:8000/cgi-bin/confi ... tionDetect
- status returned:
table.MotionDetect[0].DetectVersion=V3.0
table.MotionDetect[0].Enable=false
.....
What am I missing?

[jack7]

You probably have a firmware problem.
https://amcrest.com/forum/ip-cameras-f1 ... 13273.html

[tgraf2]

I have upgraded to the latest firmware (version=2.420.AC00.18.R,build:2019-12-18) and the new version has the same problem, ie. motion detection cannot be modified through the HTTP API. In fact, I tried a few other set commands and it appears that the HTTP API does not support ANY set commands. Can anyone confirm?

[longedge]

I have certainly had problems using the sdk although I used it in a very limited way to grab snapshots. I have now given up on the idea and use the manual snapshots from SmartPSS.

I haven't been able to pin the problem down to any particular firmware version and although I can't be certain, I suspect that it might at least partly be down to changes/updates in Windows itself. I'm currently running Windows Version 1909 build 18363.657.

The problems I had developed over a period of several months from being intermittent to permanent, across all 3 cameras and with both pre javascript and newer firmware versions.

[tgraf2]

I tested the 'get snapshot' command using the HTTP API and it works from the browser (a live snapshot is displayed). This was the case with the previous firmware version too.
I submitted a case to Amcrest support about this problem, and I asked the question of whether all SET commands have been disabled in the HTTP API. No response yet.

[tgraf2]

Amcrest support has confirmed that the HTTP API does not support any SET commands in the latest firmware (version=2.420.AC00.18.R,build:2019-12-18).

[iAMmeStyle]

I should not buy Amcrest cam before. A company should always provide their existing features. You can't sell something that has a non-beta feature and later removes it. Many people buy your products and use those existing features for reasons.

After 841 firmware upgraded in 2019 to fix an issue that live video couldn't be shown in a browser, the motion action web request was no longer working. A later firmware upgrade in 2020 still did not bring the feature back. I will no longer buy Amcrest cameras. I recently installed 3 more cameras around the house and did not even consider buying from Amcrest because the company can't even follow a simple principle for their products. They can always discontinue products, but they will never be able to expend their market.

[iAMmeStyle]

https://amcrest.com/forum/viewtopic.php ... API#p27714

[uh2]

I can make this work on firmware 2.680.00AC004.0.R w an ASH42 camera. I've been researching for the last few weeks on how to turn motion detection on/off with my Hubitat hub. If you're still having problems, let me know.

[milty456]

I'm having this problem

Software VersionV2.420.AC00.18.R, Build Date: 2020-03-30
WEB Version3.2.1.619604
ONVIF Version16.12(V2.4.1.513183)

Any workarounds where this works with CURL?