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

[GaryOkie]

quoting the PIR article in Wikipedia...

... a strong infrared source (such as from a vehicle headlight or sunlight) can overload the sensor and cause a false alarm.

My doorbell doesn't encounter headlights, but it does face East and sometimes direct sunlight will trigger a false alarm.

[Airey001]

Did they stop this going out? mine still says version r.200702 and I am "Up to date"?

[GaryOkie]

200828 was released on Sep 16. Everyone got an update notice. Then mysteriously on Sep 20, the update was recalled but no explanation given. So those than did not update like you and me are up to date!

Those that did update are in some kind of firmware limbo with no way out other than to wait for the next release. I have had a support case with Amcrest since the 18th, initially asking about why the Motion Detection UI changed and how it was better, then later asking why it was recalled.

The latest reply was that I can either choose to reset my device or wait for a reply "from a higher level". LOL -I know I'll never get a reasonable response.

[amcrest168]

@Revo2Maxx i just noticed the wide dynamic range menu has disappeared with 200828. is yours showing the same thing?

[Revo2Maxx]

Yes I don't see that in the app any longer for the new FW Camera.. I do still see it in the older FW camera right under the Night Vision Icon it has WDR there you can click and turn on or off by toggle.. So it wasn't removed from the APP just form the FW of the camera to display it...

[GaryOkie]

That sure is odd that they disabled WDR selection. It must be that if the app does not see WDR enabled in the firmware config, it will not show that option.

In v200828 what does the config show for WDR in the video capabilities section? I'm guessing it will be 0, meaning "not supported". It will be the very last line in the result of running this command...
<IP>/cgi-bin/devVideoInput.cgi?action=getCaps&channel=1
(In v200702 the value is "2")

There is another config for WDR to set the value chosen through the app. (app range 1-6 maps to 17-100%, where 0 is WDR turned off in app).
<IP>/cgi-bin/configManager.cgi?action=getConfig&name=VideoInOptions[0]

[Revo2Maxx]

It is oddly set to 2

However in the second it is setup for 0

[GaryOkie]

Thanks for checking. Ok, so the AD110 Device Capability infers WDR is still supported in 200828, but since the VideoInOption.WideDynamicRange is 0, that means it is turned off. You could set it to 17, (equivalent to WDR app lowest setting=1) to see if the WDR menu option comes back.
<IP>/cgi-bin/configManager.cgi?action=setConfig&VideoInOptions[0].WideDynamicRange=17

BTW - I have tested this API call on 200702 and it works just fine to change range.

I just don't understand yet how Amcrest is managing to change the SmartHome app menus when the app itself hasn't been updated in several months - at least not via the Play store.

[Revo2Maxx]

It is the same way that they change in other cameras as well.. Sadly the thing is there but not open for working without it being turned on... Like back in the day some maybe a year ago there was a Toggle for Human Detection in the Amcrest View app when I would use my 841 and I thought it was a feature that was missing in camera but found it was because there was other cameras that use the option and written into app however since the last update that feature is gone so it don't bug me when I hit it saying your camera isn't human detect camera however I know it is still there because in another 841 with older FW the Button remains so when they write the code they can add and take away the feature from the app...

Also that option did change the camera to have WDR on as I could see it change VIEW in my NVR after running the Command however in the App the option was still missing from it... So there must be commands in FW that turns on and off buttons in the APP as well...

The good news is that doing a Reboot if you wanted WDR on it will stay on after a reboot now to turn it off because I don't need it on in my camera it makes my picture look like a Painting in the sky and not very natural ..

[GaryOkie]

So now those of us who are still on the 200702 firmware, we are getting a new firmware update notice - to version 200828 AGAIN! This same version was released Sep 16 and recalled Sep 20 with no explanation.

So what did Amcrest do? Take a full month to fix something and reissue a new release with the previous version#? Or just reissue the same damn release exactly as it was before? The release notes are exactly the same as I recall.

The "new" 200828 has that same limited and simplified 3 zone PIR Motion Detection UI. The block grid detection zone layout is gone. The SmartHome app hasn't changed so I guess Amcrest is able to dynamically modify the app menus via XML triggered somehow by the update.

Does Motion Detection work any better with 200828? Not that I have heard. Maybe the Night IR power problem is fixed. I think the forced weekly auto reboot was removed which is good. One change that really disturbs me is that when the cloud outage occurred recently for those on the "old" 200828, the ability to record/view via RTSP no longer worked (but it did on 200702).

So for now, we have to refer to the "old 200828" versus the "new 200828" until we can possibly get confirmation from Amcrest exactly what the hell is going on with this release.