Dahua day/night switch utility - DahuaSunriseSunset

I'm trying to use this utility with five T5442T-ZE connected to a new NVR (NVR8CH-8P-2AI). The NVR's ip is 192.168.76.2. Clicking through the settings to Add a Device, I see the cameras on the NVR's internal LAN are have 10.1.1.X IPs, which I obviously I can't access. But, if you access them via the web page button they all have addresses such as; 192.168.76.2:1008X, and that address I can access...at least initially after viewing it accessing it from the NVR GUI. But it seems like after you log out of the NVR that address also becomes inaccessible.

Any ideas how I can use this utility with this NVR? I saw in another thread that the utility doesn't work with newer GUI cameras, maybe it's the same with the NVR?

Ty
 
EvanVanVan said:
I'm trying to use this utility with five T5442T-ZE connected to a new NVR (NVR8CH-8P-2AI). The NVR's ip is 192.168.76.2. Clicking through the settings to Add a Device, I see the cameras on the NVR's internal LAN are have 10.1.1.X IPs, which I obviously I can't access. But, if you access them via the web page button they all have addresses such as; 192.168.76.2:1008X, and that address I can access...at least initially after viewing it accessing it from the NVR GUI. But it seems like after you log out of the NVR that address also becomes inaccessible.

Any ideas how I can use this utility with this NVR? I saw in another thread that the utility doesn't work with newer GUI cameras, maybe it's the same with the NVR?

Ty
Click to expand...

By default the NVR isolates your cameras from the rest of your system. That is good.

You would have to either bridge mode (I think it is called that) or put the cameras on a POE switch and give them same IP address subnet as your LAN, which isn't advised as then your cameras have access to the internet.

This is the same whether the NVR is old or new. So most with an NVR do not use this utility.
 
Jgree32 said:
I've got a strange issue with one of my T5442T
Suddenly it has stopped changing to night mode upon request:
Using the command:

I get "bad request"

But the day mode command:

Works just fine with response "OK"

Not sure how the day command could work but not the night one?
Click to expand...

Something must have changed. Did you update firmware or edit anything via the camera's web UI any time recently?
 
EvanVanVan said:
I'm trying to use this utility with five T5442T-ZE connected to a new NVR (NVR8CH-8P-2AI). The NVR's ip is 192.168.76.2. Clicking through the settings to Add a Device, I see the cameras on the NVR's internal LAN are have 10.1.1.X IPs, which I obviously I can't access. But, if you access them via the web page button they all have addresses such as; 192.168.76.2:1008X, and that address I can access...at least initially after viewing it accessing it from the NVR GUI. But it seems like after you log out of the NVR that address also becomes inaccessible.

Any ideas how I can use this utility with this NVR? I saw in another thread that the utility doesn't work with newer GUI cameras, maybe it's the same with the NVR?

Ty
Click to expand...
For anyone wondering in the future, I was able to get around this by putting the NVR into bridge mode and bringing the cameras directly on to my network. Fortunately, they are still isolated from the internet and rest of my LAN using a VLAN on my unifi network.
 
  • Like
Reactions: International784, CanCuba and SpacemanSpiff
Two days ago I upgraded my BI machine and installed the day/night utility the same way I had installed it on my old unit. However, after two day/night cycles, the utility isn’t working. The simulate function works as advertised on six cameras. Anyone know of a corrective action for the utility to be automatic?

Edit: I had two instances of the same program running. I deleted one and had to change the files path. I think this will work.
 
Last edited:
  • Like
Reactions: CanCuba
I have exchanged two older SD22204T-GN cameras against two DH-SD22204DB-GNY. The new ones also have the V5 web interface, but none of the commands posted here in the last three pages work. :(

Trying the commands in the browser always returns an "OK", but the cam doesn't switch between day and night profile.

Do I overlook something?

EDIT:
After googling a while I found these commands in the Home Assistant forums which works for me:

Switch to Night Mode:
Code: 
http://username:[email protected]/cgi-bin/configManager.cgi?action=setConfig&VideoInMode[0].ConfigEx=Night&VideoInMode[0].Mode=4

Switch to Day Mode:
Code: 
http://username:[email protected]/cgi-bin/configManager.cgi?action=setConfig&VideoInMode[0].ConfigEx=Day&VideoInMode[0].Mode=4

Logging into the web server of the camera always changes the profile back to day! But having these commands as PTZ presets in BI, you can always switch back if you need night mode.
 
Last edited:
  • Like
Reactions: Hrrz
Things that tripped me up today:
  1. I put DahuaSunriseSunset.exe in my C:\Program Files\ directory.
    1. This means it writes its config file to C:\Program Files\, which requires Administrator privileges.
    2. Which means you must Run as Administrator to configure it, otherwise your configuration changes will not stick. Writing to the config file just silently fails.
  2. I physically removed a camera that had been entered into the config, and this caused the utility to hang, logging multiple errors to the log.
HTH someone else!
 
  • Like
Reactions: CanCuba
TheWaterbug said:
Things that tripped me up today:
  1. I put DahuaSunriseSunset.exe in my C:\Program Files\ directory.
    1. This means it writes its config file to C:\Program Files\, which requires Administrator privileges.
    2. Which means you must Run as Administrator to configure it, otherwise your configuration changes will not stick. Writing to the config file just silently fails.
  2. I physically removed a camera that had been entered into the config, and this caused the utility to hang, logging multiple errors to the log.
HTH someone else!
Click to expand...
For rogue applications, I will usually create a folder on C: named '\files\"
 
I set a schedule for my cams changed day to color and night to B/W under the customized scene tab and then changed it back to the Day/Night tab. Why would my cams be switching to B/W before the scheduled time?
 
Defender574 said:
I set a schedule for my cams changed day to color and night to B/W under the customized scene tab and then changed it back to the Day/Night tab. Why would my cams be switching to B/W before the scheduled time?
Click to expand...
I believe you need to leave it on Customized Scene.
 
  • Like
Reactions: bigredfish
^^^^
This and/or do you have the Day/Night control set to 'Auto"?
 
  • Like
Reactions: TheWaterbug
Sucks to hear that that the new GUI does not support this utility - and I'm forced to micromanage everything lol
Why the move backwards?
 
Arjun said:
Sucks to hear that that the new GUI does not support this utility - and I'm forced to micromanage everything lol
Why the move backwards?
Click to expand...
Technically it's the old utility that's not supporting the new GUI, but:

I asked ChatGPT to modify bp2008's DahuaSunriseSunset utility to support new GUI cameras as well as legacy-API cameras, and I have the fix documented in this other thread.
  • It now queries
  • curl -g --digest -u '<user>:<password>' "http://<Camera-IP-Address>/cgi-bin/configManager.cgi?action=getConfig&amp;name=VideoInMode""
Click to expand...
and:
  • If getConfig&name=VideoInMode contains ConfigEx, use:
    • VideoInMode[...].ConfigEx=Day
    • VideoInMode[...].ConfigEx=Night
  • if it contains Config[0], use:
    • VideoInMode[...].Config[0]=0
    • VideoInMode[...].Config[0]=1
Click to expand...
New files available in that other thread.
 
  • Wow
  • Like
Reactions: johnfitz and Arjun
wittaj said:
That is absolutely amazing and scary that ChatGPT could do that.

Easy to see why programming jobs are disappearing.
Click to expand...
Yes and no. I'm not very surprised that ChatGPT could find the correct commands and where to swap them out in the code, as when I look at my chat, it actually shows that it queried IPCamTalk to find that.

What is surprising is that ChatGPT suggested a change to support both cameras, based on which API it supported. It originally suggested a brute force approach to try one API and then fail over to the other, but when I suggested that it first query getConfig&name=VideoInMode, which ChatGPT had used earlier to verify that the new commands worked, it used that instead.

And it also added error logging without my suggesting it, which was useful in troubleshooting.

All in all it took me 2-3 hours to talk to ChatGPT, get its suggested code, copy/paste into VisualStudio, compile, test, lather, rinse, and repeat about 10x to get it all right.

There are other Agentic AIs and compilers that can work together directly, and if I could get that running locally, so that it could code, compile, and test my cameras that don't have internet access, and that might have been able to do it all in minutes. And that's the scary part.
 
  • Like
  • Love
  • Wow
Reactions: gwminor48, jrbeddow, Arjun and 1 other person
Everyone thinks that ChatGPT is an AI, but it really is thousands of 27yo programmers living in their mom's basement in Hoboken with nothing better to do in between mom bringing down a hot pocket.
 
  • Haha
Reactions: StevenFromTexas, Randel, looney2ns and 3 others
Arrrrrghhhh.

Updated the firmware on a IPC-HDW5442TM-AS to V2.840.0000000.30.R, Build Date: 2025-02-27 ( DH_IPC-HX5XXX-Volt_MultiLang_NP_Stream3_V2.840.0000000.30.R.250227.bin ) and I now have problems with the camera speaking to the web interface everytime it tries to run a day/night profile switch, its not connecting. Here's the log;


0 18/10/2026 08:17:02.128 Cam20 Event: PTZ Preset 2 (2202) paused=0
1 18/10/2026 08:17:07.244 Cam20 Web: Connect: 8000007b

1 18/10/2026 08:28:13.317 Cam20 Signal: network retry
1 18/10/2026 08:28:34.410 Cam20 Signal: Socket error
1 18/10/2026 08:28:43.317 Cam20 Signal: network retry
1 18/10/2026 08:29:04.238 Cam20 Signal: Failed to connect
1 18/10/2026 08:29:13.446 Cam20 Signal: network retry
4 18/10/2026 08:29:19.888 Cam20 Signal: restored
0 18/10/2026 08:30:25.737 Cam20 Resetting
1 18/10/2026 08:30:38.910 Cam20 Web: Connect: 8000007b

You can see what's going on, the Preset 2 switch command is sent from the camera but the command doesn't appear to get through to the V3 (the grey and black one) web interface for some reason and is rejected/ignored with a "Web: Connect: 8000007b" response. This worked perfectly before the upgrade.....yes, I know don't upgrade unless you really, really need to. In my case, the firmware was years old and thought it might have a few extras or fixes I might like....lesson learned the hard way!

Anybody know what's going on and what the fix might be? I tried various things like Find/Inspect, rebooting etc but anything that might help just results in the 8000007b error. Funnily enough, the web interface can talk quite happily to the camera but it appears the camera can't talk to the web so I'm back to using the Sunrise/Sunset utility for the time being........lifesaver!

EDIT: A thought, I only installed the one main upgrade file, should I have also installed "firmware.bin" and/or the smaller 10kb file??
DH_IPC-HX5XXX-Volt_MultiLang_NP_Stream3_V2.840.0000000.30.R.250227.bin 91,202kb
firmware.bin 44,971kb
DH_IPC-HX5XXX-Volt_MultiLang_NP_Stream3_V2.840.0000000.30.R.250227.bin 10kb

Thanks for any help that can be provided.
 
Last edited:
Boris Blank said:
Arrrrrghhhh.

Updated the firmware on a IPC-HDW5442TM-AS to V2.840.0000000.30.R, Build Date: 2025-02-27 ( DH_IPC-HX5XXX-Volt_MultiLang_NP_Stream3_V2.840.0000000.30.R.250227.bin ) and I now have problems with the camera speaking to the web interface everytime it tries to run a day/night profile switch, its not connecting. Here's the log;


0 18/10/2026 08:17:02.128 Cam20 Event: PTZ Preset 2 (2202) paused=0
1 18/10/2026 08:17:07.244 Cam20 Web: Connect: 8000007b

1 18/10/2026 08:28:13.317 Cam20 Signal: network retry
1 18/10/2026 08:28:34.410 Cam20 Signal: Socket error
1 18/10/2026 08:28:43.317 Cam20 Signal: network retry
1 18/10/2026 08:29:04.238 Cam20 Signal: Failed to connect
1 18/10/2026 08:29:13.446 Cam20 Signal: network retry
4 18/10/2026 08:29:19.888 Cam20 Signal: restored
0 18/10/2026 08:30:25.737 Cam20 Resetting
1 18/10/2026 08:30:38.910 Cam20 Web: Connect: 8000007b

You can see what's going on, the Preset 2 switch command is sent from the camera but the command doesn't appear to get through to the V3 (the grey and black one) web interface for some reason and is rejected/ignored with a "Web: Connect: 8000007b" response. This worked perfectly before the upgrade.....yes, I know don't upgrade unless you really, really need to. In my case, the firmware was years old and thought it might have a few extras or fixes I might like....lesson learned the hard way!

Anybody know what's going on and what the fix might be? I tried various things like Find/Inspect, rebooting etc but anything that might help just results in the 8000007b error. Funnily enough, the web interface can talk quite happily to the camera but it appears the camera can't talk to the web so I'm back to using the Sunrise/Sunset utility for the time being........lifesaver!

EDIT: A thought, I only installed the one main upgrade file, should I have also installed "firmware.bin" and/or the smaller 10kb file??
DH_IPC-HX5XXX-Volt_MultiLang_NP_Stream3_V2.840.0000000.30.R.250227.bin 91,202kb
firmware.bin 44,971kb
DH_IPC-HX5XXX-Volt_MultiLang_NP_Stream3_V2.840.0000000.30.R.250227.bin 10kb

Thanks for any help that can be provided.
Click to expand...

Yep, unless the release notes say it is fixing something you need and won't break something you use, best to leave it alone lol.

But yes, some of the new firmware could have two or three files you need to update, so update with that file as well.
 
  • Like
Reactions: bigredfish
You must log in or register to reply here.
Top Bottom