Amcrest Time

Eye_in_the_Sky
Eye_in_the_Sky
in SecuritySpy

Is it “better” to set up Amcrest cameras via Bonjour or use an IP address with it reserved in my router (I have camera’s set up both ways). I’m curious because I am having a heck of a time with many Amcrest cameras (IP4M’s) keeping the correct time, no matter what I do.

I am on the latest firmware for the cameras, I have installed SS NTP server. It seems that no matter how I set up the camera (Enable DST, Sync with NTP Server (using my Mac’s IP) the time jumps from GMT-04:00 to GMT+04:00 after a few days. And it is not all my camera’s!?!


Should I just resign myself that I need to change the camera’s time 1 once or twice a week?

Comments

  • Ben
    Ben

    Bonjour usually works very reliably, and the advantages using it are 1. audio-discovery and 2. you don't need to set up static IP addresses for the cameras; the Bonjour names will continue to work even when the underlying IP changes.

    But, if you have already gone to the trouble of configuring each camera with a static IP address, then you should use these IP addresses directly in SecuritySpy - nothing beats the reliability of statically-assigned IP addresses.

    None of the above will be causing your camera clock issues however. The best way to configure them in order of preference is:

    1. If the cameras have access to the Internet (i.e. they have access to your router, and are configured by DHCP, or manually with router and DNS details) then use an Internet-based NTP server like time.apple.com
    2. If the cameras don't have access to the Internet, and you're using the ONVIF profile in SecuritySpy, try the option to "Set device date and time" that you'll find in SecuritySpy under Settings > Cameras > Device. This works for most ONVIF cameras, but not all. Make sure to deactivate NTP in the camera if you're using this setting, so that they don't conflict.
    3. Only if options 1 and 2 don't work, enable SecuritySpy's NTP server, and give the IP address of the Mac running SecuritySpy to the cameras as the NTP server. For this, the Mac itself must have a static IP address on your local network (e.g. with a DHCP reservation in the router).
  • Mr_C
    Mr_C

    I had the same problem with Amcrest. It is the camera (IMHO), not your setup. I finally gave up and created a cheesy app that runs via cron once a day to set the camera's time. I am sure there is a better way, but that was my solutions.

    I also don't trust my cameras, so they are all on a separate VLAN and are not allowed to talk to the internet - that could also be part of the issue for me 😎


    Here is the link to their HTTP API to pull it off. https://s3.amazonaws.com/amcrest-files/AMCREST_CGI_SDK_API.pdf

    Here is my sample code in GO if you want a reference point: https://github.com/seldonsmule/amcrest


    Eric

  • nealk
    nealk

    Hmm, I'm in the process of getting rid of my flaky SV3Cs in favor of Amcrest, 3rd one on the way....

  • Mr_C
    Mr_C

    I have great luck with the Amcrest brand. I their outdoor 4K PTZ version on my current house (8 of them). I have the 2K version on 2 pervious houses. No issues with any of them (beyond the time sync using NTP). I like them and they work well with SS.


    The 2K version on our previous house even with through hurricane Ian in 2022 in Florida. Video if curious:

    https://youtu.be/YSVb_e_FDvI?si=WZyA28YQOlctMW7Z


Categories