Yup... this is why I would like to flash it, but don't want to be the guy that bricks it...hehSo is it still true that Lorex firmware neuters the Dahua HTTP API over port 80 ability? If so, that's a huge loss of functionality.
How does one get the latest firmware for their 410? I don’t think the app has ever shown an available update, unless it is doing it automatically without me knowing. I think my firmware number suggests 02-20-2021.You were misinformed. The latest AD410 version Amcrest Support sends out is 2021-06-10 . Yours is only 4 months older and is the same version I have, but who knows what was fixed? Amcrest doesn't provide release notes, dammit. I have not installed it. Also, my WDR option on the Android SH app does stay enabled.
Amcrest support told me I had the most recent over the phone. I'd like to try the 6/10/21 version.How does one get the latest firmware for their 410? I don’t think the app has ever shown an available update, unless it is doing it automatically without me knowing. I think my firmware number suggests 02-20-2021.
Thanks.
table.Lighting[0][0].Correction=50
table.Lighting[0][0].MiddleLight[0].Angle=50
table.Lighting[0][0].MiddleLight[0].Light=20
table.Lighting[0][0].Mode=Auto
table.Lighting[0][0].Sensitive=3
table.Lighting[0][1]. <same as above, but refers to day profile >
table.Lighting[0][2]. <same as above, but refers to night profile>
table.Lighting[0][3]. <same as above, but [3] not documented>
This is very helpful, thank you! It The AD410 appears to go into a night profile if the "Night Vision" setting is triggered on. I tried playing with settings in ASP, but it has some strange effect on the AD410's picture that can only be reset by factory resetting the device. I may keep IR off for now as I have plenty of light around the camera, but I wish a B/W option without IR was available via the APP.Hi @TheLaw - It's possible to tweak AD110/AD410 IR light settings via the API. In the Amcrest CGI API manual, refer to section 5.1.5 Lighting. To examine the current settings:
<ip_addr>/cgi-bin/configManager.cgi?action=getConfig&name=Lighting
returns for the normal (general) [0][0] profile:
table.Lighting[0][0].Correction=50
table.Lighting[0][0].MiddleLight[0].Angle=50
table.Lighting[0][0].MiddleLight[0].Light=20
table.Lighting[0][0].Mode=Auto
table.Lighting[0][0].Sensitive=3
and also:
table.Lighting[0][1]. <same as above, but refers to day profile >
table.Lighting[0][2]. <same as above, but refers to night profile>
table.Lighting[0][3]. <same as above, but [3] not documented>
Note: it's doubtful the AD410 even supports day/night profiles so the Lighting configs other than normal can probably be ignored. The IR luminance is the MiddleLight.Light value. The default luminance is a low 20% (range is 0-100%) but ONLY in manual mode. In Auto (SmartLight) mode, it apparently will dynamically adjust the intensity as it sees fit.
The Angle and Sensitive values aren't clearly described as to their purpose, but I believe these values are used in the PIR motion detection algorithm. The Correction value is only used for a special ZoomPrio mode that isn't supported by the AD410.
You will first need to change the IR Mode to manual, which can be done via the API:
<ip_address>/cgi-bin/configManager.cgi?action=setConfig&Lighting[0][0].Mode=Manual
Then you can adjust the intensity value (from 0 to 100) via:
<ip_address>/cgi bin/configManager.cgi?action=setConfig&Lighting[0][0].MiddleLight[0].Light=25
Note: Blue Iris users have reported that the IR mode can be changed back to Auto when RTSP streaming is initiated.