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

[amcrest168]

the familiar motion detection grid view is back. updated the firmware and rebooted without doing a factory reset since everything seems to be working. so far so good.

Screenshot_20201105-134043.png (38.4 KiB) Viewed 2362 times

[GaryOkie]

I see that the Wide Dynamic Range option doesn't appear in this release either - at least not in the screen capture above.

Could this be another unintentional change that was overlooked by the devs?

In any case, it's great that the apparently unintentional motion detection UI change was corrected. That's huge. Let's hope motion detection is working even better now. That missing WDR thing isn't a big deal but I do find it useful at the lower settings. It can probably still be adjusted via the API.

[Lenb55]

My AD110 was working ok until the 200922 firmware update. The motion detection became intermittent after the update only working less than 10% of the time even without changing anything. I see they changed the configuration and I set that up but it still mostly doesn't work. Before the update it always detected motion. I tried calling support but it turns out that because this is a "smart home" product I had to leave an email and have not heard back yet. The firmware update process went well but motion detection was broken. I tried cycling power but have not reset it yet as I don't want to brick it.

[tgfarrell]

I started seeing the prompt for the update. No thanks, staying at 702 for now.

[GaryOkie]

It's really aggravating that this firmware notice has no release notes at all about what was changed and fixed. We are forced to "try it and see for yourself" with no way to back out or just wait to see how serious (and consistent) the inevitable complaints are that roll in. Of course, looking for any positives as well, but they aren't reported in the forum nearly as often.

The big positive, of course, is the revert of the now confirmed unintentional Motion Detection UI change several weeks ago.

[Revo2Maxx]

Well I have updated both of mine from older FW.. First one I did and happy to do was my first 4 days release of 828.. Now while I don't have issues most times and I have had an area on my setup that has been solid when I was on 702 with the Grid only getting false alerts when cars that come down a road that points straight at the doorbell sets it off.. Looks like last night I had a few more then I would have thought I would have on a Friday looking over the footage on the clips all of them were cars coming down that road and 1 was Spider swinging from 1 side of the porch to the other lol.. All in all I am happy.. When it came up on my NVR it had high settings and wasn't liking that with 6144 with only a 15fps setting.. Yet my Sub Ch was less then 1k at 15fps.. SO I changed them to 4096 @ 22fps and 1024 at the 15fps it was already set at and seems to be working stable enough.. I don't like making changes because things get all out of sorts or can if the Doorbell camera don't like the changes... No WDR but didn't use it when it was an option and in fact it didn't improve my image when I turned it on it made it worse... I have cameras with fake WDR aka DWDR and WDR and some cameras that call it True WDR and I couldn't get any of the others to produce the image like it did with it on in the Doorbell camera so for me I am happy to see it go was just taking up page space.. All in all I am happy to be away from 828 and it don't feel any different then 702. While I don't know what the changes are and I am going to guess from the look and feel it is only a fixing of the messed up 828...

In just writing this I have seen 20 cars go by and on the 828 even with only 1 part of the pie active and at any setting from 100 to 0 I would have had all 20 alerts and Happy to say that not one of them made my phone go off with an alert... so I give the Update 9 out of 10 only lacking 1 because I have no clue what has changed from 828 second 828 or 702.. If I had some idea of the update change log I would have gave it a 10 on both first release 828 and the 702 as I have updated both to the new 922... Last time I didn't because right off I didn't like the feel of 828..

[Lenb55]

Over 24 hours and no reply from amcrest about my motion detect not working after update. Can anyone give me any advice? Should I try a factory reset?

[Revo2Maxx]

2 things.. If nothing is working I would first try to look at your settings and make sure that it wasn't turned off...

Bring up your camera then in the top right is the Cog or gear looking icon click it and make sure that the Call Notification is showing it on the ON position..

Then and I am sure you have already but then CLick the Motion Detection, make sure that is also on. Then check your schedule and make sure that isn't some how not set.. Make sure to setup your Zones and I have left my Motion range on 3 my self...

IF call Notification was on and all the other steps I just mentioned then I would do a factory Reset

[Lenb55]

A factory reset fixed my motion detection. Now I just have to see if I can set it up so I don't get as many false alarms as I was getting before the firmware update. Thanks for your help!

[amcrest168]

i think if a factory reset was done on a firmware with the motion detection 3-zone fan view, a factory reset shall be needed on an updated firmware with the motion detection grid view. i did not do a factory reset after the previous firmware with the 3-zone view hence all my motion detection grid settings remain intact. mine is currently working fine without a factory reset; so far so good.