NTP/Time issue

Discussion in 'Dahua' started by techcanuck, Oct 8, 2018.

Share This Page

  1. techcanuck

    techcanuck n3wb

    Joined:
    Sep 24, 2018
    Messages:
    22
    Likes Received:
    5
    Location:
    Toronto, Canada
    The time on my new Dahua 4231 keeps getting messed up. It's set to sync every 10 min with my NTP, yet I'll find that it has randomly changed to 7am or 3am, and then half hour later it goes back to normal. I have one other (cheap wanscam) camera that syncs with the same NTP (on my NAS) and no issues with that one, so I don't think it's the NTP server.

    I checked the camera at 7:30am this morning and it was fine, but then I checked it again 20 min later and it was showing 3:50am instead of 7:50. So I let it run for 10 minutes to see if it would sync with the NTP, but 8:00 came around and it was still showing 4 hours behind, so I rebooted it. Upon reboot, it came back with the right time.

    Then around 11:14am, it changed to 7:14am (4 hour diff again) and then pretty much exactly 10 minutes later, it switched to yet another 4 hours earlier -- 3:14am. Around noon, it went back to the right time!

    Seeing that it consistently changes to 4 hours less, I wonder if the DST setting (Eastern is currengly GMT-4) is buggy? Is there a known bug about this? Should I turn NTP off?

    This is especially annoying because I have Night mode set between 9pm & 6am, and when it goes into night mode then WDR kicks in and overexposes the daytime image.

    Any help is much appreciated.

    Cam info:
    System Version2.622.0000000.23.R, Build Date: 2018-03-30
    No internet access to camera (MAC blocked at router)

    upload_2018-10-8_12-29-38.png
     
  2. looney2ns

    looney2ns IPCT Contributor

    Joined:
    Sep 25, 2016
    Messages:
    7,307
    Likes Received:
    5,629
    Location:
    Evansville, Indiana
    Someone else reported this, and he set the cam back to factory defaults and that fixed it for him.
    Also, you might try setting the change over time from 00 to one minute after midnight or such.
     
    techcanuck likes this.
  3. pozzello

    pozzello Getting comfortable

    Joined:
    Oct 7, 2015
    Messages:
    1,565
    Likes Received:
    468
    Are you using an NVR or BI? if an NVR, it may be 'messing' with your time settings.

    if BI, you can have BI change the day/night settings based on offsets from actual dusk/dawn times in your area (vs fixed times in the cam's UI,)
    but i guess that's not really related to your NTP issue...

    also, in the US, DST changes happen at 2am, not midnight, tho you do have the month/week/day settings correct. :)
     
    techcanuck likes this.
  4. techcanuck

    techcanuck n3wb

    Joined:
    Sep 24, 2018
    Messages:
    22
    Likes Received:
    5
    Location:
    Toronto, Canada
    Ok, I'll try changing the time from 00:00:00 to 02:01:00 and see if that helps. If not, I'll try the factory reset. I am using BI so if that is able to change the camera's day/night setting, I might look into that (got any instructions handy?). At least it would resolve the problem with WDR turning on at the wrong time.
     
  5. fenderman

    fenderman Staff Member

    Joined:
    Mar 9, 2014
    Messages:
    30,820
    Likes Received:
    9,793
    If you wish you could also use BP2008's utility to change any dahua camera from night to day relative to sunrisesunset times
     
  6. looney2ns

    looney2ns IPCT Contributor

    Joined:
    Sep 25, 2016
    Messages:
    7,307
    Likes Received:
    5,629
    Location:
    Evansville, Indiana
  7. pozzello

    pozzello Getting comfortable

    Joined:
    Oct 7, 2015
    Messages:
    1,565
    Likes Received:
    468
    In the cam's 'schedule' tab in BI, you can set an event relative to dusk/dawn.
    Sending 'IR on/off' to the Dahua seems to work to switch day/night modes...
     
  8. techcanuck

    techcanuck n3wb

    Joined:
    Sep 24, 2018
    Messages:
    22
    Likes Received:
    5
    Location:
    Toronto, Canada
    Thanks all. So, ever since I set the DST time to 02:01:00, the problem hasn't re-occurred. Strange, but seems like that worked!