//FREE\ Download Amcrest Firmware

Bought an AD110 so I could have a video doorbell I could use with Zoneminder or Home Assistant. I've got it all set up and connected to wifi, but now the app is showing the doorbell is offline ( even though it's definitely online and connected ). The app is able to show the firmware version of the doorbell though, and it's Eng_V_V1.000.00AC003.0.R.20191113 -- wondering if the fact the firmware is from 2019 is why the app is unable to connect.

After much troubleshooting, it was a firmware problem. Device indicates the firmware is up to date and there are no firmware downloads on the Amcrest website for AD110; however, while exchanging messages on another forum, a newer firmware version was posted, almost at random. That was the clue. I contacted Amcrest and surprisingly, they immediately responded with a download link and instructions.

Download Amcrest Firmware

DOWNLOAD 🔥 https://urlca.com/2y4OZu 🔥

Can anyone tell me how to get a live stream in actiontiles from my amcrest? I have it working in the smartthings app, but when add a tile in actiontiles i only have a snapshot option, not a live streaming option, maybe this is not supported?

If your issue is indeed UI5 and lack of HTTP Digest Authentication support then the only easy option is to find older firmware for the camera that still uses basic authentication.

Naturally such camera should not be connected directly to public Internet via port forwarding or similar due to security concerns.

Amcrest also lists International Firmware at the bottom of the firmware page (Firmware Upgrade | Amcrest Technologies)

There you can still find an old version from 2016 for IP3M-943. For the US models older download link points to 2017 firmwares.

I continue to have no luck with getting a still image to display w/in Vera using UI5. I can get it to display beautifully (1080p!) using the RTSP link and VLC.

Tried to roll the camera firmware back to an older one, the camera would not accept it. Tried to manually send the UN/PW via commands Gary suggested, that did not work.

Both of the other cameras with the new firmware from 2019 will allow me to change a setting but within a second it reverts back to the original. (Curiously the older firmware won't successfully test an email setup, while the newer ones will.)

This uses the -amcrest library, but uses an older version. First you could try just installing the latest version and see if it works, but there's a risk that it will break everything. I currently don't have any Amcrest cameras in use but could bring up one and try it unless you or someone else can give it a shot.

Sent from my Pixel 3 XL using Tapatalk

I wouldn't know how to install the latest version you're talking about and don't feel all that great about the risk of breaking everything. If you're willing to fire up your Amcrest camera and test it out, I would sure be appreciative. If it works, it would explain why the newer firmware cameras don't respond to the older python-amcrest library while at the same time fixing their unrelated (to your nodeserver) smtp email problem.

I have several Amcrest cameras successfully working with SS v.5.4 including the IP4M 1041W PTZ camera using the ONVIF profile. I just unboxed their new model IP5M which runs a newer version of their firmware and for some reason, the PTZ control in SecuritySpy will not work. I've cycled through the possible profiles starting with ONVIF and none are able to control pan-tilt. Before I box this up and return it to Amazon I thought I'd check in here for any suggestions. Thanks!

Inexpensive ($100 U.S. on Amazon), small, light-weight, wifi / ethernet (not POE), sharp 5MP. Unlike other Amcrest domes, Pan is not 360 degree. I look forward to S/S compatibility. Is is evidently new as not listed in Amcrest firmware updates.

Before anybody asks, yes, I did update the firmware to the latest version immediately after unboxing.As of writing, the latest firmware available is version V2.620.00AC000.3.R.20191218 which can be downloaded here.

Check if the latest firmware is loaded in the camera. Is the cpu load of the computer running high?

When you add the camera with ONVIF there must be a profile for tcp together with PTZ. Using only Custom Source do not give PTZ.

-Henrik

Once loaded, the Amcrest integration will generate (Home Assistant) eventsAn event is when something happens.

[Learn more] when it receives event notifications in the stream sent by the camera. This is only possible if the camera model and firmware implement the streaming method (see above). The event type is amcrest and the data is as follows:

Once loaded, the amcrest integration will expose servicesA service carries out one specific task, for example: turn on the light in the living room. A service has targets and data and can be called by actions, a dashboard, or via voice command.

[Learn more] that can be called to perform various actions. The entity_id service attribute can specify one or more specific cameras, or all can be used to specify all configured Amcrest cameras.

The Wyze Cam v2 RTSP firmware never went out of beta but it also did not contain all the features of the main firmware due to hardware limitations. However the v2 RTSP firmware worked fine fully blocked from the internet.

@HomeControl is right. I confirm that V2 RTSP firmware works well ALL THE TIME without internet. I have three V2 RTSP cameras that are blocked from the internet and they NEVER disconnect, even after a reboot.

On the other hand, I have four V3 RTSP cameras and they are ALWAYS disconnecting after a reboot when blocked from the internet.

This is a V3 RTSP firmware issue.

Download the Amcrest Config tool to get all of the information and configuration parameter data specific to your Amcrest camera, such as protocol, max frame rate, max bit rate, ... including firmware revision (Camera firmware with that tool too, and firmware is easy to locate by searching for Amcrest firmware on the web).

I found a work around for one of my cameras (Amcrest 841 PTZ model non version 3) as it will return with a http error 500 code (Internal Server Error) often when you ask for a snapshot. This happens when you ask with any web browser, even at slow refresh rates. Since this camera appears to be made by Dahua, other cameras that share the same firmware code may find this useful.

@Rioja , thanks for the info....I have a 2.4/5ghz camera and was having trouble connecting it so I didn't think it was a 2.4ghz issue...so what I did was go back to the more unsecure WPA2-PSK[AES] + WPA-PSK[TKIP] in the prior firmware and one camera came online after 15min plus (driveway cam).....the others I had to CAT 5 to one of the deco units to "get it on the network", then once I unplugged they would pick up wirelessly (it was like they had to know about each other via cat 5). You must have at least some form of security for your cameras to work (don't choose NONE). I think on one camera I had to use my AMCREST app to scan the QR code and add it again with the old userid/pass (you have to make sure your phone is on the Deco network if you have to do this). AMCREST tag This resolved it after 3hrs of work.

Hi, can anyone help me? I am trying to get my Dahua SD22204T-GN-W camera to boot up by updating the firmware via TFTP. I have run the run commands but camera still will not boot up. The U-Boot screen shows the below. Can anyone tell me how to fix the fail to load bootargs part. Thanks

I am starting this thread to capture a bunch of information in one spot to assist those with "bricked" cameras due failed firmware upgrades. I bought my first Dahua IP camera just a couple weeks ago. I was impressed & pretty happy with it, but upon reading about new capabilities in newer firmware, I decided to upgrade it. Then like many others on here, I lost access to the Web GUI and the camera was no longer functioning. I spent the last two weeks getting to know everything about these cameras and this thread will capture all this information. It will take me several weeks to document all the information so please be patient.

There are a variety of problems that I will try my best to explain and share the possible solutions. I have gotten pretty comfortable with these cameras and have purposely bricked them to various degrees of severity just to validate the recovery process. Most people "brick" their cameras trying to upgrade the firmware. This is not a serious issue and it can be corrected very easily. The camera runs an upgrade service on port 3800. The configTool always shows a default port of 37777 but this is not an issue as it can do the upgrade on port 3800 anyway. Change your port to 3800 and use a firmware file lsted below and you are back in business.

I will keep updating this post as I get more time to write all the details around recovery. I will also post links to over 40+ firmware files that and which cameras they will work with. It will take me a bit of time to capture all this information, so please be patient.

There are several types of "BRICKED" camera conditions and they have varying levels of severity and also varying levels of complexity for recovery. Most are simple and caused by bad firmware uploads. The worst will require a full rebuild of the partitions which load the kernel, software and all other data. e24fc04721