IP8M-2493E reboot changes Static mode to DHCP

[jeffpdavis1]

My IP8M-2493-E with 2.460.AC01.0.R, Build Date: 2018-01-26

TWO apparent BUGS:
1) Setting the IP to Static rather than DHCP does not persist after a reboot. A reboot changes the TCP/IP mode back to DHCP and then of course it asks and receives an IP from my DHCP server. I don't want to have to use reservations for my cameras, although I am in the short term. I understand the risks of assigning a static IP. Besides saving the mode as Static should NOT be set back to DHCP during a reboot!!

2) Setting the Auto Maintain / Auto Reboot as UNCHECKED does not persist after a reboot. A reboot rechecks the box and reboots every Wednesday, again changing the mode to DHCP.

I have Restored to Default Settings AND I've loaded the SAME latest firmware without effect

I have two other Amcrest cameras running THEIR latest firmware without this problem.
My IP3M-941W with 2.520.AC00.18.R, Build Date: 2017-06-29 reboots fine and both settings persist.
My IP2M-852EW with 2.420.AC01.2.R Build Date: 2017-07-20 reboots fine and both settings persist

There may be MORE setting that don't persist after a reboot. I've seen others allude to some. Does anyone have any advice short of waiting for a firmware release?

[jack7]

Your camera may be connected to Amcrest Cloud which can change device settings. If connected, delete/turn off Cloud and see if that fixes it. Other software that can access your camera could also do it.

[jeffpdavis1]

Thanks for the reply. The camera is not (I hope) connected to the Amcrest Cloud but I do use BlueIris for access to all the cameras. It sure seems very unlikely that BlueIris is doing this since during my tests, I'm rebooting the camera directly from the web GUI of the camera and after rebooting, BI can't find it anymore because it's changed both the mode and IP address.

Is there something else I'm missing?

[jack7]

If you did a factory default reset at the camera after reloading the firmware, I would suggest trying this:
Whenever a reboot happens, Amcrest Cloud server and Amcrest P2P server are contacted. If you have ever registered at Cloud, even for a trial, it may connect. If so, delete your camera from cloud. If you have ever used P2P or amcrestview.com, P2P server may connect. Go to camera Settings/Network/TCP/IP/ P2P and disable P2P. Or, if you can see the IPs the camera is trying to contact, you may be able to block them on your router.
https://support.amcrest.com/hc/en-us/ar ... ctionality

Blue Iris can reboot your camera with it's Watchdog feature, if BI supports it for your camera.

[jeffpdavis1]

Ok, I did a factory reset of the camera waiting the full 45 seconds and settings were retained. I don't know how it got connected to any cloud access or P2P but apparently it was trying to connect to something and succeeding. I have no account for that and even less desire for it. I have BI's watchdog feature turned on and that was how this kept showing up as "Device Disconnected" or whatever BI says, once a week when the camera's software Auto rebooted itself, found a different IP from DHCP and BI could connect no longer. Wow, I am really glad that the mystery is solved. Thanks for persevering and reminding me to do the factory reset It is unusual to have such a longer period to hold the button down but after looking it up and trying again, everything is fine.
Thanks.