New Amcrest AD410 doorbell Cam Review

Dixit said:
I got this installed and working fine, even added to BlueIris and for the most part works fine. I got the iFrame set to 15fps as per the API setting i saw earlier in this thread, got rid of the Amcrest logo, also got rid of the time/date stamp as well.
Not sure if this is just due to it being a Wifi doorbell, but I cannot get the Mainstream to get to 1.00 on the iFrame, its always very low even after validated the Mainstream has the right 15frame iFrame which matches the 15fps. What Im noticing is that the substream has no problem holding 15fps and 1.0 on iFrame, but the Mainstream is normally well below 1fps and then iFrame is in the 0.05 range or so.

Anyone got any luck on getting this the same as substream or is this just the limitation of the doorbell.
Click to expand...

I got this partially working better. I had to change in BI not to use MainStream. Once I set it just to Substream only, I get the full 15fps and 1.0 on iFrame. But the moment I add the 2nd stream (Mainstream) it just cant handle it, and it constantly loses signal, i see 1000 or so signal drops according to BI over a 24hr period. This sucks but oh well, guess all we getting is substream for recording on this. Guess its fine for now, I got a camera covering that area anyways, this was just an extra nice to have doorbell camera with overlap coverage.
 
Dixit said:
I got this partially working better. I had to change in BI not to use MainStream. Once I set it just to Substream only, I get the full 15fps and 1.0 on iFrame. But the moment I add the 2nd stream (Mainstream) it just cant handle it, and it constantly loses signal, i see 1000 or so signal drops according to BI over a 24hr period. This sucks but oh well, guess all we getting is substream for recording on this. Guess its fine for now, I got a camera covering that area anyways, this was just an extra nice to have doorbell camera with overlap coverage.
Click to expand...

I was having drop out issues as well. I ended up moving my unifi AP about 20 feet from the doorbell with only one layer of drywall between the two. Was about 50 feet away with two walls in between. AP signal strength increase around 15db. Now its got a great connection on 5Gz with no dropouts. I have 15fps and 1.0 iFrame on both main and substream. Main settings are 2560x1920, H.265, bitstream 8192 CBR
 
prsmith777 said:
I was having drop out issues as well. I ended up moving my unifi AP about 20 feet from the doorbell with only one layer of drywall between the two. Was about 50 feet away with two walls in between. AP signal strength increase around 15db. Now its got a great connection on 5Gz with no dropouts. I have 15fps and 1.0 iFrame on both main and substream. Main settings are 2560x1920, H.265, bitstream 8192 CBR
Click to expand...

Jealous for sure. I cant get there. I have 5 unifi APs spread around my house and they are all tuned (painstaking process of DB/signal mapping). So coverage is solid. The door bell shows decent to solid signal. App shows "Good" and its on 5ghz.
IMG_3602.jpg

This is the best I can get on my BI (top line is the Doorbell)
Screen Shot 2022-01-20 at 6.47.24 PM.png
You can see the FPS and Keyframe is all over the place. Sub fluctuates between 2 and 7fps at times. Tried CBR, VBR.

Here is my actual Encode settings that I been playing with using the API functions, this is all the Video Encode settings by going to
Code: 
http://192.168.110.67/cgi-bin/configManager.cgi?action=getConfig&name=Encode

Code: 
table.Encode[0].ExtraFormat[0].Audio.Bitrate=64
table.Encode[0].ExtraFormat[0].Audio.Channels[0]=0
table.Encode[0].ExtraFormat[0].Audio.Compression=AAC
table.Encode[0].ExtraFormat[0].Audio.Depth=16
table.Encode[0].ExtraFormat[0].Audio.Frequency=16000
table.Encode[0].ExtraFormat[0].Audio.Pack=DHAV
table.Encode[0].ExtraFormat[0].AudioEnable=true
table.Encode[0].ExtraFormat[0].Video.resolution=720x576
table.Encode[0].ExtraFormat[0].Video.BitRate=2048
table.Encode[0].ExtraFormat[0].Video.BitRateControl=CBR
table.Encode[0].ExtraFormat[0].Video.Compression=H.264
table.Encode[0].ExtraFormat[0].Video.CustomResolutionName=720x576
table.Encode[0].ExtraFormat[0].Video.FPS=15
table.Encode[0].ExtraFormat[0].Video.GOP=15
table.Encode[0].ExtraFormat[0].Video.Height=576
table.Encode[0].ExtraFormat[0].Video.Pack=DHAV
table.Encode[0].ExtraFormat[0].Video.Priority=0
table.Encode[0].ExtraFormat[0].Video.Profile=Main
table.Encode[0].ExtraFormat[0].Video.Quality=6
table.Encode[0].ExtraFormat[0].Video.QualityRange=6
table.Encode[0].ExtraFormat[0].Video.SVCTLayer=1
table.Encode[0].ExtraFormat[0].Video.Width=720
table.Encode[0].ExtraFormat[0].VideoEnable=true
table.Encode[0].ExtraFormat[1].Video.resolution=720x576
table.Encode[0].ExtraFormat[1].Video.BitRate=2048
table.Encode[0].ExtraFormat[1].Video.BitRateControl=CBR
table.Encode[0].ExtraFormat[1].Video.Compression=H.264
table.Encode[0].ExtraFormat[1].Video.FPS=15
table.Encode[0].ExtraFormat[1].Video.GOP=15
table.Encode[0].ExtraFormat[1].Video.Height=576
table.Encode[0].ExtraFormat[1].Video.Pack=DHAV
table.Encode[0].ExtraFormat[1].Video.Priority=0
table.Encode[0].ExtraFormat[1].Video.Profile=Baseline
table.Encode[0].ExtraFormat[1].Video.Quality=6
table.Encode[0].ExtraFormat[1].Video.QualityRange=6
table.Encode[0].ExtraFormat[1].Video.SVCTLayer=1
table.Encode[0].ExtraFormat[1].Video.Width=720
table.Encode[0].ExtraFormat[2].BitRate=2048
table.Encode[0].ExtraFormat[2].BitRateControl=CBR
table.Encode[0].ExtraFormat[2].Compression=H.264
table.Encode[0].ExtraFormat[2].FPS=15
table.Encode[0].ExtraFormat[2].GOP=15
table.Encode[0].ExtraFormat[2].Height=576
table.Encode[0].ExtraFormat[2].Pack=DHAV
table.Encode[0].ExtraFormat[2].Priority=0
table.Encode[0].ExtraFormat[2].Profile=Baseline
table.Encode[0].ExtraFormat[2].Quality=6
table.Encode[0].ExtraFormat[2].QualityRange=6
table.Encode[0].ExtraFormat[2].SVCTLayer=1
table.Encode[0].ExtraFormat[2].Video.resolution=704x480
table.Encode[0].ExtraFormat[2].Video.Height=480
table.Encode[0].ExtraFormat[2].Video.Width=704
table.Encode[0].ExtraFormat[2].Width=720
table.Encode[0].MainFormat[0].Audio.Bitrate=64
table.Encode[0].MainFormat[0].Audio.Channels[0]=0
table.Encode[0].MainFormat[0].Audio.Compression=AAC
table.Encode[0].MainFormat[0].Audio.Depth=16
table.Encode[0].MainFormat[0].Audio.Frequency=16000
table.Encode[0].MainFormat[0].Audio.Mode=0
table.Encode[0].MainFormat[0].Audio.Pack=DHAV
table.Encode[0].MainFormat[0].AudioEnable=true
table.Encode[0].MainFormat[0].Video.resolution=2560x1920
table.Encode[0].MainFormat[0].Video.BitRate=8192
table.Encode[0].MainFormat[0].Video.BitRateControl=CBR
table.Encode[0].MainFormat[0].Video.Compression=H.264
table.Encode[0].MainFormat[0].Video.FPS=15
table.Encode[0].MainFormat[0].Video.GOP=15
table.Encode[0].MainFormat[0].Video.Height=1920
table.Encode[0].MainFormat[0].Video.Pack=DHAV
table.Encode[0].MainFormat[0].Video.Priority=0
table.Encode[0].MainFormat[0].Video.Profile=Main
table.Encode[0].MainFormat[0].Video.Quality=6
table.Encode[0].MainFormat[0].Video.QualityRange=6
table.Encode[0].MainFormat[0].Video.SVCTLayer=1
table.Encode[0].MainFormat[0].Video.Width=2560
table.Encode[0].MainFormat[0].VideoEnable=true
table.Encode[0].MainFormat[1].Audio.Bitrate=64
table.Encode[0].MainFormat[1].Audio.Channels[0]=0
table.Encode[0].MainFormat[1].Audio.Compression=AAC
table.Encode[0].MainFormat[1].Audio.Depth=16
table.Encode[0].MainFormat[1].Audio.Frequency=16000
table.Encode[0].MainFormat[1].Audio.Mode=0
table.Encode[0].MainFormat[1].Audio.Pack=DHAV
table.Encode[0].MainFormat[1].AudioEnable=true
table.Encode[0].MainFormat[1].Video.resolution=2560x1920
table.Encode[0].MainFormat[1].Video.BitRate=8192
table.Encode[0].MainFormat[1].Video.BitRateControl=CBR
table.Encode[0].MainFormat[1].Video.Compression=H.264
table.Encode[0].MainFormat[1].Video.FPS=15
table.Encode[0].MainFormat[1].Video.GOP=15
table.Encode[0].MainFormat[1].Video.Height=1920
table.Encode[0].MainFormat[1].Video.Pack=DHAV
table.Encode[0].MainFormat[1].Video.Priority=0
table.Encode[0].MainFormat[1].Video.Profile=Main
table.Encode[0].MainFormat[1].Video.Quality=6
table.Encode[0].MainFormat[1].Video.QualityRange=6
table.Encode[0].MainFormat[1].Video.SVCTLayer=1
table.Encode[0].MainFormat[1].Video.Width=2560
table.Encode[0].MainFormat[1].VideoEnable=true
table.Encode[0].MainFormat[2].Audio.Bitrate=64
table.Encode[0].MainFormat[2].Audio.Channels[0]=0
table.Encode[0].MainFormat[2].Audio.Compression=AAC
table.Encode[0].MainFormat[2].Audio.Depth=16
table.Encode[0].MainFormat[2].Audio.Frequency=16000
table.Encode[0].MainFormat[2].Audio.Mode=0
table.Encode[0].MainFormat[2].Audio.Pack=DHAV
table.Encode[0].MainFormat[2].AudioEnable=true
table.Encode[0].MainFormat[2].Video.resolution=2560x1920
table.Encode[0].MainFormat[2].Video.BitRate=8192
table.Encode[0].MainFormat[2].Video.BitRateControl=CBR
table.Encode[0].MainFormat[2].Video.Compression=H.264
table.Encode[0].MainFormat[2].Video.FPS=15
table.Encode[0].MainFormat[2].Video.GOP=15
table.Encode[0].MainFormat[2].Video.Height=1920
table.Encode[0].MainFormat[2].Video.Pack=DHAV
table.Encode[0].MainFormat[2].Video.Priority=0
table.Encode[0].MainFormat[2].Video.Profile=Main
table.Encode[0].MainFormat[2].Video.Quality=6
table.Encode[0].MainFormat[2].Video.QualityRange=6
table.Encode[0].MainFormat[2].Video.SVCTLayer=1
table.Encode[0].MainFormat[2].Video.Width=2560
table.Encode[0].MainFormat[2].VideoEnable=true
table.Encode[0].MainFormat[3].Audio.Bitrate=64
table.Encode[0].MainFormat[3].Audio.Channels[0]=0
table.Encode[0].MainFormat[3].Audio.Compression=AAC
table.Encode[0].MainFormat[3].Audio.Depth=16
table.Encode[0].MainFormat[3].Audio.Frequency=8000
table.Encode[0].MainFormat[3].Audio.Mode=0
table.Encode[0].MainFormat[3].Audio.Pack=DHAV
table.Encode[0].MainFormat[3].AudioEnable=true
table.Encode[0].MainFormat[3].Video.resolution=2560x1920
table.Encode[0].MainFormat[3].Video.BitRate=8192
table.Encode[0].MainFormat[3].Video.BitRateControl=CBR
table.Encode[0].MainFormat[3].Video.Compression=H.264
table.Encode[0].MainFormat[3].Video.FPS=15
table.Encode[0].MainFormat[3].Video.GOP=15
table.Encode[0].MainFormat[3].Video.Height=1920
table.Encode[0].MainFormat[3].Video.Pack=DHAV
table.Encode[0].MainFormat[3].Video.Priority=0
table.Encode[0].MainFormat[3].Video.Profile=Baseline
table.Encode[0].MainFormat[3].Video.Quality=6
table.Encode[0].MainFormat[3].Video.QualityRange=6
table.Encode[0].MainFormat[3].Video.SVCTLayer=1
table.Encode[0].MainFormat[3].Video.Width=2560
table.Encode[0].MainFormat[3].VideoEnable=true
table.Encode[0].SnapFormat[0].Audio.Bitrate=64
table.Encode[0].SnapFormat[0].Audio.Compression=AAC
table.Encode[0].SnapFormat[0].Audio.Depth=16
table.Encode[0].SnapFormat[0].Audio.Frequency=8000
table.Encode[0].SnapFormat[0].Audio.Pack=DHAV
table.Encode[0].SnapFormat[0].AudioEnable=true
table.Encode[0].SnapFormat[0].Video.resolution=720x576
table.Encode[0].SnapFormat[0].Video.BitRate=1024
table.Encode[0].SnapFormat[0].Video.BitRateControl=VBR
table.Encode[0].SnapFormat[0].Video.Compression=MJPG
table.Encode[0].SnapFormat[0].Video.FPS=1.000000
table.Encode[0].SnapFormat[0].Video.GOP=60
table.Encode[0].SnapFormat[0].Video.Height=576
table.Encode[0].SnapFormat[0].Video.Pack=DHAV
table.Encode[0].SnapFormat[0].Video.Priority=0
table.Encode[0].SnapFormat[0].Video.Profile=Main
table.Encode[0].SnapFormat[0].Video.Quality=5
table.Encode[0].SnapFormat[0].Video.QualityRange=6
table.Encode[0].SnapFormat[0].Video.SVCTLayer=1
table.Encode[0].SnapFormat[0].Video.Width=720
table.Encode[0].SnapFormat[0].VideoEnable=true
table.Encode[0].SnapFormat[1].Audio.Bitrate=64
table.Encode[0].SnapFormat[1].Audio.Compression=AAC
table.Encode[0].SnapFormat[1].Audio.Depth=16
table.Encode[0].SnapFormat[1].Audio.Frequency=8000
table.Encode[0].SnapFormat[1].Audio.Pack=DHAV
table.Encode[0].SnapFormat[1].AudioEnable=true
table.Encode[0].SnapFormat[1].Video.resolution=720x576
table.Encode[0].SnapFormat[1].Video.BitRate=1024
table.Encode[0].SnapFormat[1].Video.BitRateControl=VBR
table.Encode[0].SnapFormat[1].Video.Compression=MJPG
table.Encode[0].SnapFormat[1].Video.FPS=1.000000
table.Encode[0].SnapFormat[1].Video.GOP=60
table.Encode[0].SnapFormat[1].Video.Height=576
table.Encode[0].SnapFormat[1].Video.Pack=DHAV
table.Encode[0].SnapFormat[1].Video.Priority=0
table.Encode[0].SnapFormat[1].Video.Profile=Main
table.Encode[0].SnapFormat[1].Video.Quality=5
table.Encode[0].SnapFormat[1].Video.QualityRange=6
table.Encode[0].SnapFormat[1].Video.SVCTLayer=1
table.Encode[0].SnapFormat[1].Video.Width=720
table.Encode[0].SnapFormat[1].VideoEnable=true
table.Encode[0].SnapFormat[2].Audio.Bitrate=64
table.Encode[0].SnapFormat[2].Audio.Compression=AAC
table.Encode[0].SnapFormat[2].Audio.Depth=16
table.Encode[0].SnapFormat[2].Audio.Frequency=8000
table.Encode[0].SnapFormat[2].Audio.Pack=DHAV
table.Encode[0].SnapFormat[2].AudioEnable=true
table.Encode[0].SnapFormat[2].Video.resolution=720x576
table.Encode[0].SnapFormat[2].Video.BitRate=1024
table.Encode[0].SnapFormat[2].Video.BitRateControl=VBR
table.Encode[0].SnapFormat[2].Video.Compression=MJPG
table.Encode[0].SnapFormat[2].Video.FPS=1.000000
table.Encode[0].SnapFormat[2].Video.GOP=60
table.Encode[0].SnapFormat[2].Video.Height=576
table.Encode[0].SnapFormat[2].Video.Pack=DHAV
table.Encode[0].SnapFormat[2].Video.Priority=0
table.Encode[0].SnapFormat[2].Video.Profile=Main
table.Encode[0].SnapFormat[2].Video.Quality=5
table.Encode[0].SnapFormat[2].Video.QualityRange=6
table.Encode[0].SnapFormat[2].Video.SVCTLayer=1
table.Encode[0].SnapFormat[2].Video.Width=720
table.Encode[0].SnapFormat[2].VideoEnable=true


Pretty much got all of the streams to match each other. The best I can get is when I dont tell BI to use a mainstream, but this is what Im using for BI
Screen Shot 2022-01-20 at 6.54.23 PM.png
 
prsmith777 said:
have you tried H.265? I notice you're on H.264. I use the Amcrest windows program to make settings changes when possible
Click to expand...

Yeap tried that. Then went to H264 to see if that made any difference. Which Amcrest program you using? I used the Dahua Config Tool to make a few changes but a lot of the other things have to be done via API.
 
Amcrest Surveillance Pro


I've read that if you change settings using API it can mess things up.

As a last resort, I would suggest factory resetting the AD410, then use the windows program to make all your settings changes. The only thing you can't do with the program is iFrame and remove logo.... do that with the API. Hope that works
 
GaryOkie said:
Amcrest SmartHome devices are sensitive to configurations made outside of the SmartHome app. Most config changes work fine but some, particularly video/encoding changes, are known to cause the live video to either freeze or look bad.

A factory reset of the AD410 should fix the problem if the poor video is configuration related.
Click to expand...
teredactle said:
I can confirm; on the Lorex2K I made some changes with that tool, and the video got messed up even though I made no changes to the video specs/properties. A reset changed it back to normal!
Click to expand...

Appreciate the help. I'll give that a try this weekend and reply with results. Cheers!
 
Camasaur said:
No joy. And I cut the crap out of my finger removing the doorbell from the mount in order to access the reset button.Sigh. Need to discuss next steps with my wife
Click to expand...
sorry to hear that. If you are unable to return it and still have suspicions it is moisture-related - have you considered the Uncle Ben's approach to a bag of dry rice? It often works for phone-in-toilet syndrome.
 
So I currently have a Hikvision DS-HD1 and I'm thinking about getting the Amcrest AD410 to replace it. The Hikvision has been working fine for the last couple of years and for the average homeowner, it'd be great. But as a home automation tinkerer I've come across several issues on the Hikvision that are making me want to switch to something better, especially after reading this thread:
  • I can't control the button LEDs or the IR led without using the app. I want full local control as I block the doorbell from phoning home to China.
  • The main stream is full 2k, but the substream's max resolution is only 384x512. Yuck.
  • Getting a full quality snapshot is not very reliable, especially at night when the little CPU is doing all kinds of noise reduction and image manipulation in low light conditions. Pointing a browser at the snapshot URL just hangs and never retrieves anything.
  • I have to use C++ code to change camera settings (using Hikvision's SDK) through my home automation platform (Home Assistant). That's not a huge deal, but being able to just get and set values with a web based API would be nice.
For those of you who have this doorbell, I have a few questions:
  1. What's the maximum resolution of the substream?
  2. Are the IR leds and the LEDs around the button controllable via http requests?
  3. How fast does the snapshot URL return a high quality snapshot? Is there any kind of delay?
  4. Are you pleased with how WDR works? Depending on the time of year, I get sun almost directly into the lens, and WDR performance on the Hikvision has been acceptable.
Thanks in advance for any tips and pointers!
 
hawkeye217 said:
So I currently have a Hikvision DS-HD1 and I'm thinking about getting the Amcrest AD410 to replace it. The Hikvision has been working fine for the last couple of years and for the average homeowner, it'd be great. But as a home automation tinkerer I've come across several issues on the Hikvision that are making me want to switch to something better, especially after reading this thread:
  • I can't control the button LEDs or the IR led without using the app. I want full local control as I block the doorbell from phoning home to China.
  • The main stream is full 2k, but the substream's max resolution is only 384x512. Yuck.
  • Getting a full quality snapshot is not very reliable, especially at night when the little CPU is doing all kinds of noise reduction and image manipulation in low light conditions. Pointing a browser at the snapshot URL just hangs and never retrieves anything.
  • I have to use C++ code to change camera settings (using Hikvision's SDK) through my home automation platform (Home Assistant). That's not a huge deal, but being able to just get and set values with a web based API would be nice.
For those of you who have this doorbell, I have a few questions:
  1. What's the maximum resolution of the substream?
  2. Are the IR leds and the LEDs around the button controllable via http requests?
  3. How fast does the snapshot URL return a high quality snapshot? Is there any kind of delay?
  4. Are you pleased with how WDR works? Depending on the time of year, I get sun almost directly into the lens, and WDR performance on the Hikvision has been acceptable.
Thanks in advance for any tips and pointers!
Click to expand...

I have the Lorex 2K which doesn't support the API calls, too bad so sad :(
Substream is 720 x 576 I imagine all have the same substream, unless maybe Amcrest allows you to change it with the APIs...
 
  • Like
Reactions: hawkeye217
hawkeye217 said:
For those of you who have this doorbell, I have a few questions:
  1. What's the maximum resolution of the substream?
  2. Are the IR leds and the LEDs around the button controllable via http requests?
  3. How fast does the snapshot URL return a high quality snapshot? Is there any kind of delay?
  4. Are you pleased with how WDR works? Depending on the time of year, I get sun almost directly into the lens, and WDR performance on the Hikvision has been acceptable.
Thanks in advance for any tips and pointers!
Click to expand...

NOTICE: If you are an Android user, before you buy the AD410 make sure the Amcrest SmartHome app is available on Google Play Store. It is mysteriously absent today, and without it, you can't set the AD410 up. :banghead: You might also check with @CarlosBarletta in the Amcrest IPCT vendor forum (I have a post there asking about it).

The AD410 supports many of the HTTP CGI API commands for custom configurations lacking in the SmartHome app. It is very easy to issue these commands via http manually or via Curl commands in HASS automations. (Use some caution though - while bricking the doorbell seems to be rare, you may have to resort to a factory reset if things get mucked up). Note that there is no WebUI in any SmartHome device.

The mainstream "HD" max resolution is 2560x1920 (technically 5Megapixel, not 4MP as advertised).
The substream "SD" max resolution is 720x576.

The encoding can't be changed via the SmartHome app other than selecting HD or SD. But through the API or other software (NVR UI, ViewPro, DMSS SmartPSS) the encoding can be changed, including FPS, which is 15FPS for both streams by default.

Capturing a snapshot via HASS or the API (/cgi-bin/snapshot.cgi) is fast - a second or 2. Oddly, the snapshot resolution is only 720x576 even when the camera is in HD mode. This "SnapFormat" resolution can be changed via the API, but I haven't tried it. You could also use ffmpeg (as a shell command) to extract a single frame from the live RTSP HD stream.

The IR light and the lower indicator "deterrent" light, can be controlled via the API. There are also options in the SH app for controlling when these come on.

I too have an East-facing doorbell that sometimes gets direct sun. I have tried WDR, and it works OK, but I only use it 1 month out of the year. Colors are more saturated and pleasing with it off. The WDR range can't be changed via the SmartHome app, but it should be able to be set via the API, but I haven't tried it either.

Integration with HASS is really good - using either the core Amcrest integration or the custom Dahua integration.
 
Last edited:
  • Like
Reactions: SimonM
GaryOkie said:
NOTICE: If you are an Android user, before you buy the AD410 make sure the Amcrest SmartHome app is available on Google Play Store. It is mysteriously absent today, and without it, you can't set the AD410 up. :banghead: You might also check with @CarlosBarletta in the Amcrest IPCT vendor forum (I have a post there asking about it).

The AD410 supports many of the HTTP CGI API commands for custom configurations lacking in the SmatHome app. It is very easy to issue these commands via http manually or via Curl commands in HASS automations. (Use some caution though - while bricking the doorbell seems to be rare, you may have to resort to a factory reset if things get mucked up).

The mainstream "HD" max resolution is 2560x1920 (technically 5Megapixel, not 4MP as advertised).
The substream "SD" max resolution is 720x576.

The encoding can't be changed via the SmartHome app other than selecting HD or SD. But through the API or other software (NVR UI, ViewPro, DMSS) the encoding can be changed, including FPS, which is 15FPS for both streams by default.

Capturing a snapshot via HASS or the API (/cgi-bin/snapshot.cgi) is fast - a second or 2. Oddly, the snapshot resolution is only 720x576 even when the camera is in HD mode. This "SnapFormat" resolution can be changed via the API, but I haven't tried it. You could also use ffmpeg (as a shell command) to extract a single frame from the live RTSP HD stream.

The IR light and the lower indicator "deterrent" light, can be controlled via the API. There are also options in the SH app for controlling when these come on.

I too have an East-facing doorbell that sometimes gets direct sun. I have tried WDR, and it works OK, but I only use it 1 month out of the year. Colors are more saturated and pleasing with it off. This may be because the WDR range is hardcoded to "50" and might be improved by reducing it. The range can't be changed via the app, but it can be set via the API, but I haven't tried it either.

Integration with HASS is really good - using either the core Amcrest integration or the custom Dahua integration.
Click to expand...

Wow, super helpful, thanks so much @GaryOkie. I appreciate you taking the time.

It's a bit of a bummer that the snapshot resolution is still only 720x576. Has anyone tried changing this via the API?

Also, has anyone tried adjusting the WDR value via the API?
 
GaryOkie said:
NOTICE: If you are an Android user, before you buy the AD410 make sure the Amcrest SmartHome app is available on Google Play Store. It is mysteriously absent today, and without it, you can't set the AD410 up. :banghead: You might also check with @CarlosBarletta in the Amcrest IPCT vendor forum (I have a post there asking about it).

The AD410 supports many of the HTTP CGI API commands for custom configurations lacking in the SmatHome app. It is very easy to issue these commands via http manually or via Curl commands in HASS automations. (Use some caution though - while bricking the doorbell seems to be rare, you may have to resort to a factory reset if things get mucked up). Note that there is no WebUI in any SmartHome device.
Click to expand...

Could you confirm if it's possible to get rid of the Amcrest (I presume, I have the Lorex and it says Lorex) logo/watermark at the top left of the screen via the API commands?
 
GaryOkie said:
yes, it's possible... for the AD410/AD110. Are you asking for academic reasons since your Lorex apparently doesn't support the CGI API?

http://<ip_addr>/cgi-bin/configManager.cgi?action=setConfig&VideoWidget[0].PictureTitle.PreviewBlend=false

http://<ip_addr>/cgi-bin/configManager.cgi?action=setConfig&VideoWidget[0].PictureTitle.EncodeBlend=false
Click to expand...
Thanks. Just wanted to know if it was possible; this should be something that a user should have an option for in my opinion, rather than be forced to have that watermark.
I have asked/suggested to Lorex that it should be a setting in the app to turn on/off that watermark.
 
hawkeye217 said:
Also, has anyone tried adjusting the WDR value via the API?
Click to expand...
The Amcrest View Pro Windows app (and its Dahua DMSS SmartPSS equivalent) enable you to configure numerous additional video settings on the AD410 that the SmartHome app can't. It also allows you to enable WDR and specify a range from 0 to 100. However, the range has been neutered by Amcrest devs. (EDIT: Correction - it was by design by Dahua devs as the same WDR range limitation exists with the Dahua DH-DB6I).

If you enable WDR in the SH app, the WDR range is set to "1", which basically means it is enabled, not a particular range value. If you change the WDR range in the ViewPro app to anything other than 1, it appears from the live video that WDR gets turned OFF. So any attempt to tweak WDR by specifying a range of 10, 50, whatever, appears to be the same as turning WDR off!

I did not find an obvious alternative API configuration value that the AD410 uses for WDR gamma compensation. There probably is, but it remains to be discovered.
 
Last edited:
  • Like
Reactions: hawkeye217
I did have to return mine after 6 months - not due to a power up issue, but it just suddenly lost focus somehow. It had been perfectly stable up to then, no reboots or any other problem. RMA warranty exchange with Amcrest went smoothly, and I was pleased to have received a complete new package, not a refurb.

The reports I've seen with AD410 power issues have mostly been shortly after first installation, where the 16-24VAC/VDC input circuit gets fried. Of those that failed, many users found connecting a 5VDC USB power the darn thing would power up fine. So all indications are that it is quite sensitive to the transformer voltage and how the chime kit may be installed. I found only 1 video on YouTube where a UK user reported his failing after 4 months immediately after a doorbell push. (And his too worked with 5VDC).

Of course seeing these failure reports is a concern, but it does not seem to be all that prevalent to me.
 
Hi,

I have a AD410 that I've been testing out - three observations/questions below.

Firstly, I noticed that it did not seem to be very stable with MicroUSB power - it would seem to frequently reboot when I tried to access the video stream. However, I swapped it over to a 24V AC adapter, and it seems to be more stable that way - has anybody else noticed this?

Secondly, I have noticed that the video feed often glitched out - it seems to present a white/grey wall (and the timestamp in the top right, and Amcrest logo in the bottom right are also affected):

AD410Lexus_2022_03_02_07_39_55.png
AD410Lexus_2022_03_02_07_39_54.png
Has anybody noticed this, or know a way to fix it?

Thirdly - the NVR application I'm using has successfully picked up the main and secondary stream - however, the main stream is limited to 1440x1080, for some reason. It doesn't seem to have detected the higher resolution (2560x1920).

I did download a copy of Amcrest Surveillance Pro (which seems to be last updated 2015), and was able to add the AD410 camera to the app there. Under the "Encode" section, "Resolution", for the Main Stream, it does offer a choice of either "1440x1080" or "2560x1920" resolution. I did try setting it here to 2560x1920 and hitting Apply/Save, but it doesn't reflect in the NVR (which then seems to set it back to 1440x1080, as if I check again with Amcrest Surveillance Pro later, it seems to have reverted to 1440x1080.

Does anybody know if this is an issue with my NVR software, or something to do with the ONVIF/RTSP profiles in the Amcrest AD410? Has anybody successfully used the full 2560x1920 resolution with other programs, like say BlueIris etc?
 
You must log in or register to reply here.
Top Bottom