Bug? API Call to disable Motion Email returns 200 but doesn't update

[Revo2Maxx]

Well it isn't really a Bug Per se.. It is more just a different code for the newer cameras that hasn't been updated to a new released API sheet... However you could maybe under the Feature/Request area ask that a new API update be released. I did ask Amcrest and they are looking to the R&D department to find if and when the updated CGI will come out..

[BurntTech]

I might say it shouldn't return 200 response if it wasn't successful but ya I can create a feature request. Thanks!

[Revo2Maxx]

Very true. I was not happy to see that I also got a ok after running the command to turn on and off email for motion to find out that it didn't work on my 8mp camera with 21FW and it does work with my older FW camera. My guess is that there was something changed in the API command and the right command for doing that task isn't the one from older version of the API?

Now I am not sure really.. I just moved my 1046ew-AI camera with 2021 FW on it to my normal network, and while it is a different camera and is higher tech then my 2496ew-v2 just has less MP then my 2496 when I run the command on that 4mp camera the command works to turn on and off the email for motion event.. So I am not sure really why the 8mp cameras are having an issue with the command.

Moved another 4mp off a POE NVR to my local network POE switch for testing and sure enough it also works with the API command so seems to be something with 8mp cameras as all the others that I have tried on old and NEW FW just all 4mp or under that API commend works