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

[Revo2Maxx]

Sadly I have found that after this last reset it has gone back to the MOTION Gone Wild again so after being woke up by my doorbell going off 20 times after 6am when I had the Schedule setup to return to giving me notices I have now turned off motion again.. I can't wait until the next Update that corrects this Motion issue..

[amcrest168]

@Revo2Maxx can you see your outside with the 3 zone half pie view? i wonder if anyone can.

[Revo2Maxx]

No it looks like your picture.. Funny thing is there is no control of how much you setup your zones...

Oddly another thing that is kind of odd while it isn't making the alerts go off I disabled Motion and yet in Config the PIR setting still says it is enabled

[GaryOkie]

Sorry Revo for all the trouble the new firmware is causing. I'm glad I postponed updating but am appreciative you gave the reset a try. We just didn't know if Amcrest's support asking if a reset after the firmware update was supposed to actually fix anything or just a "go fish" response. Clearly, it was the latter.

@amcrest168 The 3 zone half pie layout is very typical for PIR-only motion detection. The Dahua DB11 doorbell, which the AD110 is based on, still uses this layout (as does Ring, Skybell, and others). It was not designed to overlay a live view, and it really wouldn't make much sense if it did. You just have to use trial and error to adjust the distance range, which tweaks the sensitivity of the IR beam. As to the 3 zones, it can be used to limit detection to the center view and ignore heat signatures to the far left and right.

Here's a good visual for how PIR detection works... https://lastminuteengineers.com/pir-sen ... -tutorial/

More advanced camera-based motion detection combine PIR detection with video analysis movement detection. This is what Amcrest was seemingly attempting to provide by incorporating the block grids. Let's hope they get this right in the next firmware release.

[GaryOkie]

@Revo2Maxx Disabling Motion in the SmartHome app turns off the Alarm.enable setting in the doorbell. That's all it needs to do. MotionDetect and PIR stay enabled always (unless turned off by API).

I just now tried to turn off "Call Notification" to continue to record motion but avoid mobile alerts. It didn't work! I still get SmartHome push notifications with this option turned off. Does anyone else have this issue?

Also, for anyone who has updated to the new firmware, would you please help me determine what setting is changed that eliminates consecutive motion alerts that occur within 30 seconds? I think it was zero or 10 in the previous firmware, and is now 30. I'd like to make it even longer via the API.

Please run these 2 commands, and copy the first 10 lines of results:

<ip_addr>/cgi-bin/configManager.cgi?action=getConfig&name=Alarm[0]

<ip_addr>/cgi-bin/configManager.cgi?action=getConfig&name=MotionDetect[0]


The 200702 firmware has these settings. I'm hoping to see which one of these settings that were 0 or 10 is now 30 in the 200828 firmware.

table.Alarm[0].DisableDelay=0
table.Alarm[0].Enable=true
table.Alarm[0].EnableControl=Normal
table.Alarm[0].EventHandler.AlarmOut=0
table.Alarm[0].EventHandler.AlarmOutEnable=false
table.Alarm[0].EventHandler.AlarmOutLatch=10
table.Alarm[0].EventHandler.BeepEnable=false
table.Alarm[0].EventHandler.Dejitter=0
table.Alarm[0].EventHandler.Delay=0

table.MotionDetect[0].Enable=true
table.MotionDetect[0].EventHandler.AlarmOutChannels[0]=0
table.MotionDetect[0].EventHandler.AlarmOutEnable=true
table.MotionDetect[0].EventHandler.AlarmOutLatch=0
table.MotionDetect[0].EventHandler.BeepEnable=false
table.MotionDetect[0].EventHandler.Dejitter=10
table.MotionDetect[0].EventHandler.Delay=0

[Revo2Maxx]

table.Alarm[0].DisableDelay=0
table.Alarm[0].Enable=true
table.Alarm[0].EnableControl=Normal
table.Alarm[0].EventHandler.AlarmOutEnable=false
table.Alarm[0].EventHandler.AlarmOutLatch=10
table.Alarm[0].EventHandler.BeepEnable=false
table.Alarm[0].EventHandler.Dejitter=30
table.Alarm[0].EventHandler.Delay=0
table.Alarm[0].EventHandler.ExAlarmOutEnable=false
table.Alarm[0].EventHandler.LogEnable=true

table.MotionDetect[0].Enable=false
table.MotionDetect[0].EventHandler.AlarmOutChannels[0]=0
table.MotionDetect[0].EventHandler.AlarmOutEnable=false
table.MotionDetect[0].EventHandler.AlarmOutLatch=0
table.MotionDetect[0].EventHandler.BeepEnable=false
table.MotionDetect[0].EventHandler.Dejitter=10
table.MotionDetect[0].EventHandler.Delay=0
table.MotionDetect[0].EventHandler.LogEnable=true
table.MotionDetect[0].EventHandler.MailEnable=false
table.MotionDetect[0].EventHandler.MessageEnable=false

Also as I said I have mine turned off at the moment but here is mine from my Updated camera

[GaryOkie]

Thanks Revo! Really appreciate that you took time to run these commands.

This shows exactly what I was looking for - Alarm[0].EventHandler.Dejitter=30 is what changed. I think "Dejitter" is synonymous with "Anti-Dither" terminology used in the NVR menus but I'm not certain and will do some tests.

The other thing that is really interesting is that Amcrest changed which settings are toggled when you turn off Motion Detection in the SmartHome app. It now sets to false both MotionDetect[0].Enable and MotionDetect[0].EventHandler.AlarmOutEnable. This is good and consistent with expectations. Previously Alarm[0].Enable and Alarm[0].EventHandler.SnapshotEnable were set to false. It will be interesting to see what the new as yet unreleased firmware will do. This matters to developers.

EDIT: I really don't understand this SmartHome app, which hasn't been updated in months, can not only change the UI in the app but also alter how it interacts and changes DIFFERENT settings in the doorbell.

[djsteve]

@Revo2Maxx can you see your outside with the 3 zone half pie view? i wonder if anyone can.

Such an overlay wouldn’t make sense. The 3 zone outline is a “top-down” view, as if you were hovering above the area within camera view. It does not directly translate into the forward looking image from the lens.

[GaryOkie]

Yeah, we agree Steve - I also said it didn't make much sense to overlay the PIR zones with camera view earlier, but you nicely clarified why.

I still have a support case open with Amcrest to try to find out more about this now-retracted 200828 update. The first reply I got was "Did you reset the device?", The second was "We have not received an update regarding the latest update". Whoa, support was clueless there was even an update? After questioning this and asking why it was retracted, the reply just now was "We are checking with the team".

I'm still running 200702 with the MD block grids. There was speculation that the PIR isn't being used with this UI in effect. Well, not the case. I taped over the PIR lens (top part of the AD110) and found that no motion detection of any kind occurs. I also taped over the camera lens and removed the PIR tape and still no motion was detected! So I believe this proves that the PIR is being used in conjunction with video analysis using the MD block filtering. Solely relying on the PIR or video analysis of movement isn't sufficient to trigger events, they appear to go hand in hand.

I still haven't heard if anyone else has tried to turn off "Call Notification" in the SmartHome app and still gets SH push notifications. Would sure appreciate if this can be confirmed as an issue not specific to me.

[amcrest168]

just want to share the 3 zone fan layout that came with 200828 appears to be working fine for now with the caveat i didn't change any of my motion detection setting after updating. i continue to get push alerts from deliveries, children selling girl scout cookies, and people trying to sell things. once in a while, i get false alerts from incoming headlights at night. i would think video based motion detection would be affected by incoming headlights. is pir also affected by incoming headlights?