AD110 firmware v1.000.00AC006.0.R.200922

[GaryOkie]

Thanks @Lenb55 for the info! The ip config tool has been around forever. It's really good to know it can be used to update the AD110 firmware.

This is the first I've heard of anyone being given instructions on installing an older firmware. When 200828 & 20200828 was released with its old/obsolete unintended Motion Detection UI there were sure a lot of users who would have loved to have been able to back it out rather than be forced to wait over a month for a patch.

What is the URL you were given for the 191113 firmware? I would like to try to see if I can find other versions on that server. If so, this could take some concern out of installing new updates since we have the ability to back it out.

[Lenb55]

They uploaded it onto a google drive https://drive.google.com/file/d/1JwkAh9 ... 4fjaA/view

[GaryOkie]

Oh, a one-off upload for you. Hmm, so we'll have to request the desired firmware binary from Support as needed. Not ideal, and I would expect pushback, but at least we know it's possible now.

It's unreal they actually asked you to install a version that was a year old.

> Amcrest_DB-LEXUS_Eng_N_16M_V1.000.00AC003.0.R.20191113.bin

Has anyone been given a google drive upload link for any newer versions of the AD110 firmware? Let us know!

[Revo2Maxx]

Just as a Reminder that while IP config is great tool and doing an update to the cameras can be great because you can do Batch installs.. One thing that needs to be noted not every system can take old FW and the main issue here is the camera FW that was loaded was Production Release FW and is the same type FW as all FW that follows.. From time to time there are other older FW that isn't same type and they will have a Block in the FW coding that will Deny loading of any FW before (Not always but does happen).. That isn't to say that the Device couldn't be sent back to Amcrest and have them via another means install a different package FW if the device needs such an downgrade!..

For the Doorbell no I have not had an update FW installed by this manner. For my NVR 4018E I do have a different FW from the Drop box that was given to me and while it was deemed not a stable FW for the masses I am happy that after a week working with Support I was giving a FW that works for my Needs.. Personally I don't think that info should be shared without Support offering this Directly to the End User but I don't feel it is my Job at this time to Remove that link unless I am asked too.. Also on a Personal note it might be that someone might have ability to make a file for a Device of its own Serial Number to UUID as most times they are one of the same but as with all things I would be careful DL and installing something in the Smart Home Product line if it didn't come to you Direct from Amcrest...

[GaryOkie]

My point is that we now know we can install an older firmware, and that we have to ask Support for it.

Had you known that were possible, wouldn't you have asked Support to be able to go back to 200702 a month ago? Or had you already asked and were told to just wait and wait?

I don't disagree about being careful with installing firmware. That is especially true for "unintentional update" versions coming directly from Amcrest these days.

[Revo2Maxx]

Sadly I wasn't given the 702 as a Re install and I never really pushed the idea that I wanted it after I was told they were working on a Replacement.. I think for me it gave me the time to see some of the difference between 702 that I had in one and 828 that was in my Front door cam. I will admit I was about to swap them around to give my front the 702 over a strange acting 828.. However for me I turned off motion to the camera and kept it there..

[rotary65]

My AD110 is near my front security camera that has night lighting. Additionally, the door light above the doorbell is turned on by a motion sensor. I get alerts for the doorbell through BlueIris, my security camera software. AI makes sure that I only get alterted for people at the door. I do use the doorbell's motion to save to a memory card. So, I don't use the doorbell's night vision or notification features at all. I leave the Night Vision setting to Off. This is good because despite having a smart doorbell rated PSU, the doorbell's night lights cause it to repeatedly disconnect and reconnect all night long, with that stupid voice announcing it each time.

The previous version fixed the Tuesday reset of the doorbell that reset Night Vision to Auto. This newest version seemed to work, but last night (Friday night), the Night Vision setting reset to Auto again. So far, this has just happened once.

Whoever decided to use voice on this doorbell made a very poor design decision. It ruins the product experience for me by annoying me and my neighbors.

[Revo2Maxx]

Sadly a Smart Rated PSU isn't always what they are Cracked up to be...

@rotary65 Hello and Welcome to the Forum..

I am sorry to hear you are having some issues with your Doorbell.. All I can tell you is that I have in the past had some issues with my Doorbell from being connected to my NVR/DVR's and had some issues that to be honest was not even Directly to do with the doorbell camera from trying to setup a different camera that was connected to my NVR that it was connected too...

First thing that catches my Eye with your text is that you say your using BlueIris and I hate to mention it but there are reports that BI and the Doorbell have issues working Happy together...

By the way my first part Smart Rated PSU sadly can't use that as the type one is installing... Nest Cameras work with very low PSU.. I have had only a few times with Issues on my Doorbell camera, Once was Server issue and kept power Cycling not sure why but it wouldn't connect longer then a second or 2 on my NVR before it will go offline for an hour or 2 every 5 min it yelling out Connected to Network.. Then other times was me trying to make an adjustment of a camera on one of the connected recorders and my guess was while trying to work on CH15 I think I hit 5 and made some adjustments in some software all i know is that camera was not working right, kept going offline, no one on Forum was reporting an outage so I thought it was Router, Reboot that, then my NVR, then my Switches and in the end did a Reset of the camera doorbell and problem was solved.. I had even Reset my NVR because I thought it was something in my NVR that went haywire...

Things that matter, Wire size (Wire Type as Well), Distance from Power to Doorbell camera, Transformer Size and Type 16vac is a Must unless someone is going to use Stand alone Amcrest 18vac Power (Transformer 16vac 30va) Min Required

[rotary65]

Thanks for the detailed reply and for the welcome also.

I'll look into the wiring, that could be it. The psu is more specifically a 16V 30VA Doorbell Transformer. Mine is a small house, so likely more wire gauge than distance (~30 feet).

The camera is streaming to both BlueIris and an Amcrest NVR, so that may not be helping.

In any case, it works well when Night Vision is off. The trick is just keeping it off.

[amcrest168]

thank you @Lenb55 for sharing the ipconfig tool can be used to update the ad110 firmware. this is good to know about our ad110.

hmm... i'm now wondering if the 20191113 firmware has anything to do with being able to add regular amcrest ip cameras back into the smart home app. all my amcrest ip cameras were automatically added to my smart home app when when the ad110 was first released on november 2019.