Ad110 motion record length

[callaway4986]

question on clip record length - on my ad110 I subscribed to the 7 day pay motion plan ( no cooldown, no video length limit ), but videos are being recorded as 15 - 20 second length clips even though the motion event is still taking place.
Ex - mail man pulls up to house, gets out and starts walking to door - the one way trip takes ~ 45 seconds, but the motion recording is 20 seconds, and cuts off with the mailman halfway up the driveway. There's then no recording of getting back in the truck and driving away.

With this plan, shouldn't the entire event ( truck pulling up, walk to door, walk back, truck driving away ) of maybe a more than a minute and a half be being recorded ?

The ad110 is on firmware 1.000.00AC006.0.R.200922.

Is this an issue with the device, or the cloud plan not syncing/recording properly ?

[Revo2Maxx]

Hello and Welcome to the forum

Sadly the system needs to be adjusted so that the camera will work in a 20 second time frame. Since I have owned the camera local anyway I think I don't get more then 20 seconds and might be 15.. I have it connected to NVR for full time Recording anyway but that short clip is what it saves local..

If your paying for a Non limited motion that is something your going to want to talk to Support by sending them a email or Calling them For Smart home you can get the info about support from this link
https://amcrest.com/smarthomesupport

Other then that I am not sure what to do. I know that people have talked about the Short Clips since the Release

[callaway4986]

Looking in the app settings, I'm noticing there was an app update, now motion zone settings are actual grid layout vs 3 cone areas. I revised the motion area settings, and increased the sensitivity - maybe this will have a positive impact and yield better/longer clips ?

[tgfarrell]

No it defaults to 20 seconds on(recording), 20 seconds off. I think the cloud 7 day plan you mentioned is just to store the recordings for you in the cloud and not just locally.

[PromptCritical]

I think this is something that Amcrest really needs to fix. It defeats the entire purpose of a camera if you only get footage of the porch pirate walking up to your door and looking around, then the next clip is you coming home to find your package gone.

Sure, evidence that a person was there is helpful, but is useless without other evidence. A camera is supposed to provide the slam-dunk evidence showing him actually committing the crime.

Further point: I believe it is false advertising for Amcrest to say the camera records while there is motion when it clearly stops recording after 20 seconds and motion is still occurring.

There's no excuse. In a month the camera has recorded a half GB of video on a 128GB card. That's 20 years of capacity. If there is some technical reason why there has to be a defined time, then let me change it to a minute or two, or have it capture multiple successive consecutive clips.

This and the fact that you cannot turn off motion notifications without disabling motion detection entirely are the only complaints I have about this product.

[GaryOkie]

@callaway4986
@tgfarrell
@PromptCritical

I've had some success extending the AD110 recording length a bit. The value I've been tweaking via the API is "AlarmOutLatch" in the Alarm eventhandler. This is documented as:

Latch: when motion detection complete, system auto delays detecting for a specified time. The value ranges from 1-300(Unit: second)

Now that doesn't read to me like anything that would extend the recording time, but I found it does.

AD110/SmartHome apparently relies on the Alarm eventhandler settings, not MotionDetect to trigger recordings. The default alarm latch value is 10 seconds. There is also a default Pre-Record value of 10 seconds which starts the recording 10 secs or so before the motion is first detected. Together, you get approx 20 seconds of recording or less.

You can increase the the alarm latch from 10 to 20 via:

Code: Select all

<ip>/cgi-bin/configManager.cgi?action=setConfig&Alarm[0].EventHandler.AlarmOutLatch=20

This will provide approx 30 seconds of recording or less if the person/object leaves the detection area before then. I've also tried larger values (50+sec) but am seeing that SmartHome app has difficulty displaying them if motion occurred during the whole time. The video only partially works and freezes. Maybe it's a timeout connection thing with large (8MB+) files. However, you can download the video from the app and view it with any MP4 viewer and it's recorded fine.

There is also another setting that can be tweaked to reduce repetitive motion alerts in a short timeframe. This is the "Anti-Dither" setting. Early on, this value was only 10 secs, but in a recent firmware update, it was extended to 30 secs.

This value can be adjusted to 1 minute or whatever via:

Code: Select all

<ip>/cgi-bin/configManager.cgi?action=setConfig&Alarm[0].EventHandler.Dejitter=60

It's important to point out that these Alarm settings only seem to apply to SmartHome motion recordings. The NVR and other software (like Home Assistant) rely on the MotionDetect event which has its own separate Anti-Dither and Latch settings. Furthermore, these settings are not well synchronized between the AD110 and the NVR and any changes to the AD110 motion settings via non-SmartHome apps (other than the API) should be avoided. Do be careful with the API as well.

[PromptCritical]

Sounds like the best solution for what I would want is the Latch expanded to the max that's stable for the app and dejitter lower so less action is missed.