Amcrest Forum

I am using Zoneminder. It does not alter camera settings. No SD cards. I catch it from time to time looking at events or on the live view with the Amcrest app. I have never seen it on Tuesday which is the day they all restart. All of the cameras tick at the same time so I know they are syncing with ...

If you want to give it a go, I have 5 cameras at the movement. The 3 that most commonly have the clock issue are running the newest firmware available.

IP3M-956EW
IP4M-1025W
IP4M-1028EW

The clock reset to 2000 description did not include the word system or the phrase power outage. A camera just goes back to 2000, there are no known events associated with the clock change, and I have looked. I mark it as an OS problem with the camera, the type of never to be fixed problems that led ...

I point mine at an internal NTP server and have then check the time about every 5 minutes. I also set DST dates in the GUI to keep the time right. I do not have drift or the hour shift problem. However from time to time mine go to 2000 with a wrong time and will stay that way from 5 minutes to days....

Support replied it is a known HW problem. RMA in progress.

What do you have the camera FPS set to? If it is default try dropping it to 10FPS and see if there is improvement.
Can you steer the camera to 1 band (2.4 Ghz?) and the computers to the other band (5Ghz?) on your Unifi AP? This may also help.

I did re-flash the firmware to the same version and I did try both static and DHCP. The weird part is it grabs a DHCP address and then does not use it. I can see in the DHCP server logs it is assigned an address. It does seem like a coding error and it is not looking at the static/dhcp option after ...

Thank you for the response, you used a lot of words to say what I did not clearly state, I should not be able to set the address with the DHCP option set, but I can and it does not get a DHCP address. I prefer a DHCP address as I can make changes 1 time and affect many. Having a camera that is diffe...

I saw the same thing. One of the things I have done is set the DNS to NULL or 0.0.0.0 on the cameras that allow it, others get a black hole address. I also isolated the cameras and block all traffic off the VLAN. I am sure they are still going nuts... If you allow it to resolve and contact the web s...

I had to replace one of my cameras. When I plugged the new one in it picked up a DHCP address (192.168.2.53) but was not accessible. An ARP check of the network found the camera with an address (192.168.1.108) not in a valid subnet. I altered my address to connect to the camera and set a proper addr...