Support

Fix CCTV Date, Time, Timezone, NTP and Daylight Saving

This guide addresses CCTV timestamps, playback or notifications show the wrong time in the order technical support would test it: preserve what matters, open the correct screen, correct the proven cause and verify the result.

Time and Evidence

Summary

Follow the four stages below to diagnose CCTV timestamps, playback or notifications show the wrong time without losing evidence, configuration or device ownership.

Applies to

  • NVRs, DVRs and IP cameras
  • Sites affected by Australian daylight saving changes

Difficulty and time

Difficulty: Moderate

Estimated time: 15 to 30 minutes

What you will need

  • The exact model and current firmware or app version
  • Administrator access where authorised
  • A photo or screenshot of the current status
  • One controlled test case and its exact time

What this guide covers

  • Preserve and reproduce the fault
  • Open the correct diagnostic screen
  • Correct the proven cause
  • Verify and document the result

Use this page when CCTV timestamps, playback or notifications show the wrong time. It includes the menu or screen to look for, the status that matters and a repeatable proof test.

Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.

Before you start

Protect the current system and record a baseline before changing anything.

  • Write down the exact symptom: live view or playback is early, late, drifting, or one hour out after daylight saving.
  • Photograph the current status, error text, wiring or timeline as applicable.
  • Record the last known working time and anything changed immediately before the fault.
  • For an active incident, document the original offset before correcting time so earlier footage can still be located and explained.
Important

Changing the clock does not rewrite old evidence safely

Record the old displayed time and actual time before correction. A time change can create overlaps or gaps in the recording timeline.

If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.

What usually causes this

  • Timezone was never set
  • DST rule is wrong
  • NTP server cannot be reached
  • Camera and NVR use different time sources

Step 1: Preserve the current state and reproduce the fault

Begin with a repeatable baseline so you know whether a later change genuinely helped.

  • Reproduce the problem once and record: live view or playback is early, late, drifting, or one hour out after daylight saving.
  • Note whether every device or user is affected, or only one.
  • Compare one working path with the failing path if a comparison exists.
  • For an active incident, document the original offset before correcting time so earlier footage can still be located and explained.

Step 2: Open the correct screen and inspect the evidence

The primary diagnostic location is Main Menu > System > General > Date & Time, Time Settings or NTP. Do not change anything until the displayed state is recorded.

  • Open Main Menu > System > General > Date & Time, Time Settings or NTP. Menu wording can vary by model and firmware; use the nearest equivalent label.
  • Record the current recorder time, timezone, DST rule and NTP server before editing.
  • Compare recorder time with a trusted phone clock and note the exact offset.
  • Check whether individual IP cameras are synchronised from the NVR or use their own NTP.

Step 3: Correct only the cause you proved

Use the matching correction below. Make one change, save it, then repeat the same test.

  • Set the correct region/timezone first; do not compensate by deliberately setting a false clock.
  • Enable the correct automatic DST rule for the site if the model supports it.
  • Configure a reachable NTP server and sensible sync interval.
  • Synchronise cameras from the recorder or give them the same trusted time source.

Step 4: Verify, monitor and document the handover

A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.

  • Wait for an NTP sync and confirm the live timestamp matches the trusted clock.
  • Create a new test event and find it at the expected playback time.
  • Export a short clip and confirm its overlay and filename time are understandable.
  • Recheck after the next restart and document any historical offset affecting old footage.
Worked example

Controlled support test

Situation: The reported symptom was: live view or playback is early, late, drifting, or one hour out after daylight saving.

Solution used: The current state was recorded in Main Menu > System > General > Date & Time, Time Settings or NTP, one matching correction was made, and the same test was repeated.

Why this was chosen: This separated the proven cause from unrelated settings.

Installation notes: The final screenshot and test time were saved with the handover record.

Official reference used for this guide

Menu names differ between releases. Confirm model-specific behaviour in Hikvision NVR User Manual before firmware, reset, storage or security-sensitive work.

Common mistakes

  • Changing several settings before repeating the original test.
  • Using a factory reset, initialise or format option as an early troubleshooting step.
  • Treating an app symptom as proof that the local hardware or recording has failed.
  • Failing to record the model, version, exact error and test time before escalation.
  • Assuming similar-looking models use identical menus or features.

Troubleshooting table

Symptom What to check What to do next
live view or playback is early, late, drifting, or one hour out after daylight saving wrong timezone, incorrect DST rule, unreachable NTP server, camera/NVR time-source conflict or failed clock battery Open the named diagnostic screen, record the displayed state and use the matching correction above.
The named menu is not visible Different firmware, permissions or model capability Do not substitute a destructive menu. Capture the model and version and use its official manual.
The change saves but the fault remains The selected cause was not the root cause Undo the change if appropriate, return to the baseline and compare the failing path with a working one.
Local test works but app or client test fails Account, permission, cloud or remote-network path Keep the proven local configuration and diagnose the remote path separately.
Problem returns later Intermittent power, cable, storage, network or schedule condition Record the new failure time and status; correlate it with logs, events and the last known working interval.

When to contact support

Contact SecurityWholesalers support when time continues to drift after NTP is proven reachable, cameras will not follow the recorder, or an incident requires a formal timestamp explanation.

Send the order number if available, exact model, firmware or app version, screenshot of Main Menu > System > General > Date & Time, Time Settings or NTP, the failure time, and the result of the local proof test.

Related support guides

Related buying guides

Relevant product categories

Still stuck?

Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.

Frequently asked questions

  • Where should I click first for fix CCTV date and time?

    Start at Main Menu > System > General > Date & Time, Time Settings or NTP. Record the existing state before changing it because labels and available options can vary by model and firmware.

  • What should I look for on that screen?

    Look for timezone, DST enable/rule, NTP enable, server address, port, interval and last synchronisation result.

  • What must I avoid changing during the first check?

    Record the old displayed time and actual time before correction. A time change can create overlaps or gaps in the recording timeline.

  • How do I prove the correction worked?

    Create a fresh event against a trusted clock, find it at the correct time locally, then confirm an export carries a consistent timestamp.

  • Why might my menu names look different?

    Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.

  • Should I factory-reset the device?

    Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.

  • What should I send technical support?

    Send the exact model and version, screenshot of Main Menu > System > General > Date & Time, Time Settings or NTP, exact error text, failure time, what changed before the fault and the result of the controlled local test.

  • Can configuration changes recover data or events that were never recorded?

    No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.

Further Reading
Guide Page Recording, Playback and Export Overview Overview Guide Page Hikvision Support Guides Guide Page HiLook Support Guides

We make product support and ordering easy! Reach out to our help team :)
Trade Customers: Log In or Register to Unlock Even Better Prices.

Save & Share Cart
Your Shopping Cart will be saved and you'll be given a link. You, or anyone with the link, can use it to retrieve your Cart at any time.
Save Cart & Generate Link
Send Cart in an Email Done! close
Empty cart. Please add products before saving :)

Back Save & Share Cart
Your Shopping Cart will be saved with Product pictures and information, and Cart Totals. Then send it to yourself, or a friend, with a link to retrieve it at any time.
Send Cart Email
Your cart email sent successfully :)