The light depicted in that scene is already more than what those little white LEDs would emit, so not terribly helpful here—it would be more of a fill from a different angle than anything else. The 5442 cannot do the same as it is about 1/3 as light-sensitive (in my estimation) compared the Color4M-TL or Color4K-T. Using its bright IR LEDs is where the 5442 still shines, but it looks like the OP is using them in forced-color mode (or with enough ambient light they're not switching to IR mode), where the Color4M-TL consistently outperforms them—hence my original comment (I also like the WizColor during the day because it automatically applies a better WDR to the image than anything the 5442 can do). You can purchase them directly from Andy (link is above in my first post). If you need more than his site will let you order, just email him with the lens/quantity you want.
The Color4M-TL camera offers four LED modes:
- Warm Light Mode Auto: Turns on when dark—very dark/way too late using default exposure settings (they'd probably stay off in the scene pictured in the OP), and always dimmer than the brightness slider is set. I found that limiting Gain causes the white LEDs to come on sooner/brighter.
- Smart Illumination: This is the mode that's supposed to give you intelligent/AI LED control, but it only seems to be useful on the dual color cameras (where it switches the camera from IR mode to color mode when triggered, switching off the IR LEDs and switching on the white LEDs in the process). On cameras with only white LEDs, its operation is sadly identical (or nearly so) to the above. Dahua really dropped the ball on this one, and it would be so easy to fix in the firmware but I'm not holding my breath.
- Warm Light Mode Manual: Always on 24/7, exactly whatever you set the brightness to—note that 100% manual is approximately twice as bright as 100% auto.
- Warm Light Mode Off: The LEDs are always off and the camera uses ambient light only.
Can the LEDs be activated by IVS? Yes, with hacks. So what I've been playing with is running batch files from
Blue Iris' [On trigger...] and [On reset...] events (Motion/Trigger camera tab). I pass the camera's IP address to the batch file, and one batch file executes
curl with the IP address, sending the camera CGI commands to limit shutter time+gain and set the LED to 100% auto, while the other restores high exposure/gain and drops the LED to 0% auto (which is very dim—dimmer than a phone flashlight—but typically still enough for IVS triggers to work). I'd love to use 100% manual as it's even brighter, but then it would come on during the day too and it also seems to break the license plate over exposure reducer, resulting in an overly bright image and washed out plates at night. It's all janky, but the best I can do for now. Dahua could do so much more with some simple firmware modifications. If it wasn't closed source, I could probably patch it myself!