IP4M-1056E - Firmware update - error on download page

[ohmbroo]

Hello,
I looked into updating the firmware (F/W) on one of my cams, IP4M-1056E.
The downloads page indicated there was and update, 2.460.AC01.1.R, 2018-06-26.
I currently am at F/W 2.460.AC000.R, 2017-10-23.
The download page returns:
======
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>CWK0T7V89V1E99XV</RequestId>
<HostId>hF9X/MdweMZPLm6UEggqfi8dGG5X1O5Dn+sKrlG9M0MtlG5xEnTJtCYs5jxElLPzhIQYhqJEBRU=</HostId>
</Error>
========
Is this what happens with discontinued camera updates?
Is there a revision history available to see if I want to even pursue the update somehow?

I have a NVR Model NV5208E and am currently running 7 cameras.

Thank you,
Ed

[Revo2Maxx]

Might see if the camera has firmware on the website. https://amcrest.com/firmware if it is 2019 or newer and want to stay with the older 2018 then could try again to dl at different time of day to see if maybe the issue is traffic related. In the end, might need to make a ticket with Amcrest and ask them to send the 2018 fw.

[Revo2Maxx]

So down towards the bottom of the Firmware page there is a 2018 FW listed so I would DL from there using your computer, Then log into the camera using the Browser that you normally use, I am going to guess that it would be Edge in IE mode, Then do the update that way.. It is faster seeing the camera would be located on your local network and the file on your local computer once downloaded.. The update wouldn't lag as it might trying to update off the cloud update system..

So to do this update, you would need to use an external Switch or some other power method for the camera. Connect to your router, If you don't have DHCP enabled then you will need to use the Amcrest IP config tool to update the IP address to your local network address.. Meaning

Normally the NVRs switch if you don't change would have the cameras on a 10.1.1.xx IP and your home network might be on 192.168.0.xx and because they are not in the same range without having extra info setup in your computer that would let you connect to a IP outside of your local network the tool can find the camera and make change to the IP of you choice. Using IE mode in Edge is the best bet for accees to all cameras new and old besides the few that are blocked.. Most of my newer and for sure the older FW cameras work best in IE mode of Edge..

[ohmbroo]

Revo2Maxx,

Thanks for the reply!
The info I got was from the https://amcrest.com/firmware site.
I'll try later in case the error was thrown from bandwidth use.

Next step would be to start a ticket with Amcrest support.

I feel it is best to keep the F/W up to the latest.

Thanks,

Ed

[Revo2Maxx]

So I just looked at the page and sure enough there is an issue with the format of the webpage. It really isn't anything about the camera being old and no longer getting any FW updates. One of my cameras is in that list with the newest FW from 2017 and I was able to DL mine.. I would just make a Ticket and ask Amcrest to fix the page and or send you the file.. Might come as a link to a Google storage..

IF you have your camera connected to the internet *Meaning not behind a NVR or if the DNS is updated, You might be able to click the Check for Update in the cameras WebUI and get the FW update from Amcrest Cloud service.* I know what I said before lol. But some it works just fine others best to just DL.. I just opened a OS 841W that hasn't been connected before, After setting up it offered a FW update.. I didn't even have to click the button after setup. I was just looking around in the 2016 FW that it was installed from Factory and offered the 2017 FW.. Anything after that would have to be DL and installed. I will keep it on the 2017 FW, I personally like it better then the newer one for the 841,

But yes you are right, it is good to have the last Stable version FW the camera has to offer.. Any of my newer cameras I update as soon as they roll out..

[ohmbroo]

Revo2Maxx,
Thanks for the checking the web page.
I put in a support request and will stand by for the response and share when I get it.

The only reasons I looked into the firmware on this camera was that the web GUI for the camera fails. I use it for motion notifications. The other cameras that are newer have no problem. This older on is the only one I use the NVR to send out the e-mail, while the camera GUI is set up for the snapshot and motion parameters. I also have to use internet explorer legacy mode in MS Edge to see the live feed.

I do use the NVR bridge mode. You helped me set that up and is doing well


I'll be more proactive in keeping the other cameras FW up to date.

Thank you

[Revo2Maxx]

In some cases keep in mind that waiting a little after an update is good. I mean I have over a dozen of one type of camera that back in 2019 updated 8 or 9 of them and wish I hadn't because now they all have an issue that they didn't have before the update.. So if you happen to have more of the same camera then update 1 check to see if any issues, If no issues then update the rest. Now with newer 2019 to now most times no issues going to an older FW within that frame. However don't want to get stuck with all cameras being with an issue. Best to try one.. Plus as I have been told many times. Updates as soon as the new FW or software is released is like setting your self up to be a test subject.. So now I wait at least a month to see if there is any reports of issues. Then make a judgement call if that is something I can live with or not lol..

[ohmbroo]

Roger that Revo2Maxx,
I don't like being the accidental beta tester. We would think updates would have some sort of testing.
thank you,
Ed

[Revo2Maxx]

Well I agree and I am sure there is some testing before release. Issue can be that we might have camera hardware somewhat different then the tested device. Might be because of hardware change at some point or other unknown factor.

For instance, 841 firmware 2019 a device with preset 3 setup makes camera act strange after reboot. Yet for some they don't have that same problem. Looking at 2 cameras built less then 2 months of the other one camera has that issue the other don't. Both have same CPU but do they really? Not from same cast but both same model no telling what sets the 2 apart.

All I know maybe the tested device before release came from batch without issue. Even a few updates later the issue remains on affected devices.

[ohmbroo]

Revo2Maxx,
I did put in a service request. Had to show screen shots of the error on different browsers before it was elevated.
Standing by as the support checks with "higher team".
Thanks!