PTZ IP4M-10x3EW-AI cameras aren't really AI?

Have some questions or having issues with your IP Camera(s), Post them here for the mods and other users to assist you with.
plusfour
Posts: 102
Joined: Tue Mar 06, 2018 4:04 am

Re: PTZ IP4M-10x3EW-AI cameras aren't really AI?

Post by plusfour »

An update on this after a bit of debugging, it looks like not only is the camera not compatible with the NVR but trying to do anything via the NVR disables AI functionality on the camera even if you go direct to the camera's web interface. So if you factory reset the camera to get the AI back and go to the web interface you'll get the AI functionality. If you then make any change via the NVR, for example changing the timestamp setting, and go back to the camera's web UI, the AI functionality has been disabled. This is why the camera appeared to be non-AI capable even via the web UI.
User avatar
Revo2Maxx
Site Admin
Posts: 5908
Joined: Sat Jun 15, 2019 3:05 pm

Re: PTZ IP4M-10x3EW-AI cameras aren't really AI?

Post by Revo2Maxx »

Yeah my guess won't be an issue using a real Amcrest AI NVR the 5xxx besides (5216E-16p) isn't really AI but does seem to unlock some features with AI cameras
Be Safe.
eliamcrest
Posts: 14
Joined: Fri Aug 12, 2022 10:40 am

Re: PTZ IP4M-10x3EW-AI cameras aren't really AI?

Post by eliamcrest »

plusfour wrote: Fri Apr 21, 2023 3:08 am An update on this after a bit of debugging, it looks like not only is the camera not compatible with the NVR but trying to do anything via the NVR disables AI functionality on the camera even if you go direct to the camera's web interface. So if you factory reset the camera to get the AI back and go to the web interface you'll get the AI functionality. If you then make any change via the NVR, for example changing the timestamp setting, and go back to the camera's web UI, the AI functionality has been disabled. This is why the camera appeared to be non-AI capable even via the web UI.
Hi there,

Would it be possible for you to tell us the exact model of 5XXX NVR that's being used in this situation?

This sounds like a potential firmware bug, and I'd like to report this to the Amcrest R&D team.
Post Reply