I can't seem to find a solution for automatic DST changes on all of the cameras. Cameras are configured to use NTP server for time synchronization, but DST settings vary from camera to camera and need to be adjusted manually. What is a good solution to handle this?
How to handle DST changes on multiple cameras?
- Thread starter PancakeBimmer
- Start date
I just went thru each camera andset them manually. The cameras are behind the nvr and cant get to the ntp server to update.
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
With my Dahuas (who I block from accessing the internet - and the nvr), I use a script that sets the current time on each channel.
SET_TIME = 'http://{0}/cgi-bin/global.cgi?action=setCurrentTime&time={1}'
SET_TIME = 'http://{0}/cgi-bin/global.cgi?action=setCurrentTime&time={1}'
This is actually really good approach that takes care of DST completely. My cameras don't have access to internet either, but do use local ntp server running on nvr pc. Problem is 19 cameras are 4 different brands with different firmware, so doing it manually twice a year is pain, even with batch config tools. But your approach is great, script once and run it with task scheduler.
Thank you
Still easier to make a script with pain once and never think of it again. There are some hivision (i think) cameras that have such a slow interface that changing time on them is especially more pita.
I suppose it's a little more hassle to setup DST on a new cam if you install like 30 a day, but to me (DIY home dabbler) setting up DST on a new camera is a minor task (on top of adjusting networking, accounts, day/night exposure stuff...). My Dahua's have a straightforward and simple to use interface for setting up DST, but I suppose not all cams are like that.
Ironically, the only device I have that doesn't handle DST well is my enterprise poe switch; can't believe that thing doesn't even have DST!
Ironically, the only device I have that doesn't handle DST well is my enterprise poe switch; can't believe that thing doesn't even have DST!
FWIW, I have this application loaded on my BI server. All of the cameras are pointed to the static IP address of the BI server for it's time updates. It works very well. Well enough that I have it running at two different locations, for different installations.
Time Sync is configured to check time every 5 minutes, but I'll likely knock that back at some point.
None of the cameras at either location have internet access. All cameras used static IP addresses, as does the BI server.
It handled the DST change earlier this year without an issue.
Time Sync is configured to check time every 5 minutes, but I'll likely knock that back at some point.
None of the cameras at either location have internet access. All cameras used static IP addresses, as does the BI server.
It handled the DST change earlier this year without an issue.
So you are also running a local NTP server on blue iris machine? That is what I am doing and time sync is fine, but DST changes are messed up and still dont sync up.
Yes, that's correct - local NTP server on the BI server. I don't want any of the cameras having 'net access.
As I recall, all the cameras changed to the correct time during the last DST change, but that was months ago, and I've slept a few times since then.
The next change is coming in a few weeks, so I'll see if it behaves like it's supposed to.
Hmm... per that apps page:
"NetTime works internally with UTC (Universal Time) and doesn't have any code for handling daylight savings or time zones. As long as Windows is configured correctly, it should automatically handle daylight savings changes for you."
Most connected gizmos these days are expected to do their own zone and dst calcs, and work with standard utc ntp servers (be it your own server, nist, or whatever). I am guessing that's why such apps aren't available. Like the boys above said, scripting may be the least painful solution.
Kev
"NetTime works internally with UTC (Universal Time) and doesn't have any code for handling daylight savings or time zones. As long as Windows is configured correctly, it should automatically handle daylight savings changes for you."
Most connected gizmos these days are expected to do their own zone and dst calcs, and work with standard utc ntp servers (be it your own server, nist, or whatever). I am guessing that's why such apps aren't available. Like the boys above said, scripting may be the least painful solution.
Kev
fenderman
Staff member
- Mar 9, 2014
- 36,892
- 21,407
The ideal solution would be to for someone to write a fake NTP program similar to nettime but that simply feeds off the windows clock....this way you can uncheck dst in the cams and it will automatically adjust based on windows automatic dst adjustment....
HineySmack
n3wb
- Oct 18, 2017
- 7
- 4
Here is how to sync your cameras to your windows PC so you don't have to expose your cameras to internet.
Use the built in Windows NTP Server!
1. In the Windows Registry:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
- Change the value from 10 to 5 (you may need to click Decimal to see the number)
b. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\NtpServer
- Change the value to Enabled = 1
2. In Windows Services:
- Set the Windows Time Service to Automatic Startup and Start the Service.
3. In the Windows Firewall:
- Create an inbound rule in the Windows Firewall for UDP Port 123. Uncheck the Public check box during rule creation.
4. In your camera configuration:
- For the NTP server, enter the IP address of your PC and save.
- I’m not sure about other cameras, but in Hikvision there is a test button that is comes in handy.
Notes: You will still need to set your DST settings in your camera’s time configuration.
You may also want to set the camera to check time every 10 minutes (interval).
You may also want to set a static IP address or reserve that IP in your router so the IP doesn't change and then cameras will lose time.
Use the built in Windows NTP Server!
1. In the Windows Registry:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags
- Change the value from 10 to 5 (you may need to click Decimal to see the number)
b. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\W32Time\TimeProviders\NtpServer
- Change the value to Enabled = 1
2. In Windows Services:
- Set the Windows Time Service to Automatic Startup and Start the Service.
3. In the Windows Firewall:
- Create an inbound rule in the Windows Firewall for UDP Port 123. Uncheck the Public check box during rule creation.
4. In your camera configuration:
- For the NTP server, enter the IP address of your PC and save.
- I’m not sure about other cameras, but in Hikvision there is a test button that is comes in handy.
Notes: You will still need to set your DST settings in your camera’s time configuration.
You may also want to set the camera to check time every 10 minutes (interval).
You may also want to set a static IP address or reserve that IP in your router so the IP doesn't change and then cameras will lose time.
beepsilver
Getting comfortable
That appears to be just another ntp daemon (utc). Having to do dst on the camera is I think the central issue here. So no 'pure ntp server' stuff will help.
Whatever it is has to do post processing after ntp sync, before time is sent to a requesting camera.
I agree syncing more often is ok and even recommended. Mine sync every hour, and one of my cams gets a -10sec error in that time. Increasing syncs to every 5min is next on my to do list.
Whatever it is has to do post processing after ntp sync, before time is sent to a requesting camera.
I agree syncing more often is ok and even recommended. Mine sync every hour, and one of my cams gets a -10sec error in that time. Increasing syncs to every 5min is next on my to do list.
HineySmack
n3wb
- Oct 18, 2017
- 7
- 4
beepsilver
Getting comfortable
I took my cams off the internet and time drifted quite a bit on some cameras....so rather than manually sync the cameras every now and then this workaround helps a great deal and still keeps the bots from pinging my cameras.
For those who have asus routers, Merlin firmware includes ntpd. That's what I use, together with some routing table entries that isolate my cameras from the internet. My router would be bored and underutilized otherwise. 
As an update - all of my cameras changed to the correct time early Sunday morning, automatically, using the the NetTime NTP server running on the BI server. None of them were configured internally for the DST change.