Latest Firmware for IP2M-841 broke on/off motion detect web api

[iAMmeStyle]

I updated to the latest firmware yesterday V2.420.AC00.18.R

Now I realized it broke the web api for turn on/off motion detect. I also read other people have the same issue.

My http request is like
http://[username]:[password]@[my ip]:[port]/cgi-bin/configManager.cgi?action=setConfig&MotionDetect[0].Enable=true

Send the request will return ok but nothing happens.
Other web api so far since working fine including tour mode.

Since this issue, it broke my logic from webcore to record motion only when some sensors detect something. I need to downgrade to the previous version. Please help. Thanks

[Revo2Maxx]

Sorry that you feel you need to Downgrade sadly because of the FW being different Software format the say isn't something that should be done. While no one can stop you from having an old bin file for it on your HDD and trying to do a Downgrade. However there have been some people that reported they bricked the Camera trying to. Some Reported as it is said some Features that used to work under old FW may not work and is why they say you shouldn't Downgrade plus it is hard stress for the camera...

I know you want to send that API command and be able to turn on your Motion how ever there is Grids and things that need to be setup anyway... I would just Log on the WebUI on Chrome and turn on Motion... I get all my Motion off my NEW FW 841 sent to my FTP also use other forms of backup and all work with Motion.

[iAMmeStyle]

My use case is only to turn on motion detect when some sensors are triggered then record the motion to the SD card. I don't need the camera always detecting motion when it does not need to. I have 2 logics. One is to set the motion on when it's in arm mode otherwise off. Another logic is to turn on motion when it's disarm mode but some doors are opened.

[Revo2Maxx]

Hummm Well then that is little bit if a Pickle...

So I am going to guess that you have or could get something to accept this input and when it gets that imput have a output go to the Cameras Alarm In... While this is only a Temp fix while the NEW FW is being made and one day before long should be released and could fix the problem your having.. Or Maybe there are others that have that Camera and being used like you're using it to have same Logic services and found the right way to put in the Coding. I am going to guess that it isn't broke just that the Coding for it is now different and has to be wrote out in a different form then how it was in the past... While I am not sure what the codes are because I don't use them... I just use the camera as a Video making device... While it might not be as advanced as my OLD TECH Speed DOME not expecting it to either... Ok maybe just a little wish it was lol.. Anyway again not trying to down play the issue just trying to give an idea of something that might work in the mean time... My other OLD tech dome has inputs that could easy work from Door sensors and motion sensors... 7 in 2 out... That was only reason that was injected... Wish the 841 had maybe 1 more input then it would work as you need from the camera without Software besides what is already in it...

Maybe someone will happen by with the Right Code for your Motion if that is all it needs...

[Cupra]

Is there any news on that?
I bought the camera for the reason that I can control it via API and now it does not work!

[Revo2Maxx]

@Cupra Hello and Welcome to the Forum...

Have you tried your API comands? not everyone is using the same FW and it might be that you Cupra are using a different FW from the one that has the issue?

Reason I said this is because I just tested this on both the New FW 2.420 form 2019 and didn't work but FW 2.520 from 2017 it did...

[Cupra]

Yes i tried it, every other Command e.g. deactivate the Audio Detection is working correctly.

I'm on the newest firmware and hopping for a fix soon!

[Revo2Maxx]

Well I am thinking from what I read in another thread it might be that the API data for the FW your on isn't going to work as it stands. Looking over the API doc I find that there are updates when new FW comes out and last update in API I can find only goes back to 2017 so maybe new Docs will come out or might need to wait for new FW that will work with the Commands as it stands. Not sure seeing new FW is different codding altogether.. Sadly with the Update to the New FW it is also said that going back to old fw from this new one might make the camera not function.

[iAMmeStyle]

Latest version 2020-02-17 is still not working. My camera is a junk now. Going to buy a new one from other brands to replace it for my smart devices implementation. Not going to waste my money on Amcrest anymore~ Sad customers r because they trusted untrusted brands~ What can I say...

[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.