Dahua day/night switch utility - DahuaSunriseSunset
- Thread starter bp2008
- Start date
No need to export and re-import settings. Just download whatever update file you need from the archive kept here and install it. In 99% of cases this is all that is required to revert to a previous BI version.
Although it is good practice to make a settings backup before you update, that is a bit of a nuisance unless you get software to automate it such as BiUpdateHelper. Blue Iris already does make a few periodic backups automatically which you can find in your Blue Iris 5 directory. Sometimes a BI update changes things in a way that is not entirely backwards compatible so there can be some loss when reverting to a previous version, but usually that sort of thing would only happen in a more significant update, e.g. 5.0 -> 5.1, and not in a less significant update like 5.1.0 -> 5.1.1.
UPDATE: This is still broken in 5.5.6.10
But fixed in 5.5.6.11
But fixed in 5.5.6.11
Last edited:
I read through the past few pages to see if my specific problem was mentioned and didn't see it. The problem only recently started after having run the utility for some months successfully. Specifically, the problem is affecting my LPR camera (Dahua 5241-Z12E) and then only the Focus setting when changing to Sunrise settings. All other configured settings for Zoom and Focus for Sunset and Sunrise work fine. When I wake in the morning the LPR camera is always blurry and no plates are captured. I hit the 'Simulate Sunrise' button and within a few seconds all is well again ... until the next morning.
Any thoughts?
Any thoughts?
Sybertiger
Known around here
Only thought I have is to put a delay between the commands sent to each camera. And, possibly send the command more than once to that cam 10 secs later. I have delays between mine for similar issues.
Last edited:
I am already using the "Seconds Between Lens Commands" set to the default of 4 seconds. I'll try changing the default to 5 seconds and see if that makes a difference.
Sybertiger
Known around here
I thought you were going to say "frame rates"
Cross-threading I see LOL
But nope, I had this exact issue with my Z12E and it was a failing SD card that would reboot the camera of course in the middle of the night, resulting in blurry images.
Running latest 1.9.0.0 and it keeps crashing - not responding. I have everything configured as I did on my old PC, but after moving to new one and configuring from scratch, I'm getting zero luck.
I did get a warning from Win10 when trying to install about it being unsafe - and used proceed anyway. Am I missing something?
I did get a warning from Win10 when trying to install about it being unsafe - and used proceed anyway. Am I missing something?
Not sure why it isn't running, but the unsafe warning is simply because the virus programs use an algorithm of how many users are using something as part of their evaluation, so when so few are using the utility, it will show up with a warning.
Yeah, I wasn't too concerned about the warning. I just can't figure out why my new PC won't let it run without locking up. For now I'm just running it on another PC that's always on and it works fine on that one.. it's always something.
Just out of curiosity, have you tried moving over to the newer/preferred method of having BI handle this "natively" though the Schedules and PTZ APIs (even by @bp2008, the original script author)? Look over the first post of this thread for details.
What setting are you using on the camera under Conditions -> Profile Management? I'm finding if I set the profile to Full Time->Day, when the BI call sets the profile to night, the camera immediately reverts back to Day b/c of the full time Day setting. I've manually made the call using a curl command and seeing the setting set so I belive my password it set correctly. I'm using a IPC-T5449H-ASE-D camera as well.
Are you using the same BI call as in the directions?
admin@password@192.168.0.15/cgi-bin/configManager.cgi?action=setConfig&VideoInMode[0].Config[0]=0
thanks
Yes, I do use the command as you noted, changing the end digit between 0 and 1 to switch between day and night modes. The post you quoted was prior to my discovery that the issue I was having was due to my camera admin user password having an @ symbol within it, which won't work in this case, as that is also used as the separator in the command string. Once that was resolved, this method has been working perfectly for months now, I have no issues as you described. Are you literally watching the switchover time while logged into the camera profile management page? If logged in and watching that page (using the same user/password combo as in your command string) I could see how that might cause the camera to flip back and forth, as it could "confuse" the situation. I actually created a second admin user within the camera for use with the profile switchover setup, but doubt that it was strictly necessary. You might try that workaround to see if it helps your setup.
Yes, nice catch, I didn't go back and look it up explicitly. The @ is used as the separator between the password and the IP address of the camera however, and that is what interfered in my setup originally.
Edit: That's what I get for answering forum posts before having coffee and breakfast.
Sybertiger
Known around here
Another thing is to pay attention to is the CHANNEL NUMBERS setting. I leave it blank on all my cams with the exception of my boobie cam which looks like this:
Good catch, I actually was using the correct notation in BI. When I copied and deleted my
user:pass I put in a typo.I did end up figuring out my issue was enabling https on the camera. I had used a self signed (generated on the camera) cert, that i think was throwing an error in BI. I disabled https on the camera and things are working as expected. FWIW, I first tried running a https: web request and BI was throwing a Web: error: stream XXXX in the logs. I assume this was b/c of the self signed cert. Can anyone confirm and know how to get BI to accept the self signed cert for a web request?