IP8M-VD2893EW-AI - Issues with API being inconsistent
Posted: Tue Sep 27, 2022 10:38 am
Hello,
I purchased one of these models (IP8M-VD2893EW-AI) about 6 months ago and it has worked fine. I purchased another one two months ago and the API appears to respond differently for the two models. I initially noticed the problem as I was unable to add the second camera to Synology Surveillance Station (I have 16 other Amcrest cameras of various models that work fine). When adding to Synology SS I was able to preview the stream but when I save (which causes the Synology to push settings changes) it just gives an error.
After trying to factory reset, upgrade firmware, downgrade firmware, etc I did a packet capture and took a look at the connection between SS and the camera. I saw that the API calls to configure settings were returning with errors.
Here is one of the calls that SS makes to the camera
http://ip/cgi-bin/configManager.cgi?act ... ontrol=VBR
If I run this call against the first camera I purchased earlier in 2022 i get "OK" as a response.
On the second camera I get
"
Error
Bad Request!
"
I am testing this now in a browser to avoid any other software and rule out any other vendor being the issue. I can confirm the issue is on the Amcrest side.
I confirmed that the models of cameras are identical and so is the firmware. I would expect the same response from both. I factory reset both cameras and re-tested and I still get OK from the first camera and Error from the second.
Support were not helpful and suggested I did an RMA. In this case I returned it to Amazon and purchased another one from Amcrest. The second one arrived with the same problem. I went back to support and they told me I had another bad camera. I RMA'd the camera and just received another one which still has the same error.
I sent support screenshots, logs and other information but I'm not able to talk to a developer or an engineer who actually understands the problem. I'm just talking to a rep who doesn't seem to understand.
Short of returning this for a refund does anyone have any thoughts? anyone seen this before?
M
I purchased one of these models (IP8M-VD2893EW-AI) about 6 months ago and it has worked fine. I purchased another one two months ago and the API appears to respond differently for the two models. I initially noticed the problem as I was unable to add the second camera to Synology Surveillance Station (I have 16 other Amcrest cameras of various models that work fine). When adding to Synology SS I was able to preview the stream but when I save (which causes the Synology to push settings changes) it just gives an error.
After trying to factory reset, upgrade firmware, downgrade firmware, etc I did a packet capture and took a look at the connection between SS and the camera. I saw that the API calls to configure settings were returning with errors.
Here is one of the calls that SS makes to the camera
http://ip/cgi-bin/configManager.cgi?act ... ontrol=VBR
If I run this call against the first camera I purchased earlier in 2022 i get "OK" as a response.
On the second camera I get
"
Error
Bad Request!
"
I am testing this now in a browser to avoid any other software and rule out any other vendor being the issue. I can confirm the issue is on the Amcrest side.
I confirmed that the models of cameras are identical and so is the firmware. I would expect the same response from both. I factory reset both cameras and re-tested and I still get OK from the first camera and Error from the second.
Support were not helpful and suggested I did an RMA. In this case I returned it to Amazon and purchased another one from Amcrest. The second one arrived with the same problem. I went back to support and they told me I had another bad camera. I RMA'd the camera and just received another one which still has the same error.
I sent support screenshots, logs and other information but I'm not able to talk to a developer or an engineer who actually understands the problem. I'm just talking to a rep who doesn't seem to understand.
Short of returning this for a refund does anyone have any thoughts? anyone seen this before?
M