Hi All,
It would be nice to have an option for a Network Time Server (NTP) build in, so we don’t have to, twice a year, manually change the system time.
In my setup there are a few time-enabled presets that has to be recalled. A good real-time time would be appreciated!
I second this request. I currently have scheduling done by another system that is NTP sychronised and connects to AHM with GPI. If I want to move this scheduling to the AHM itself I’ll need it to be NTP sychronised.
I would go further and say that an NTP client is *essential* for the AHM. Our AHM loses 5 seconds EVERY DAY. For a system with scheduling as a prominent feature we need much better timekeeping to be useful, especially when coordinating events with scheduled program content.
Does the AHM have to have an internet connection?
In the production environment we don’t want to have an internet connection from system-relevant devices.
I don’t really like the different time either, even though the clock in our AHM is much more accurate. But it’s true: if you use time-controlled processes, then an accurate time is of course important.
Is there another way to solve this?
Another +1 for NTP on AHM. How are we supposed to use Time/Schedule-based Events if we can’t accurately track the time during daylight savings in the US?
If I want a restaurant’s music zone to turn off at 2am, or to turn on a rack of amps at 9am each day…that only works for 6 months out of the year…then the other 6 months it’s completely inaccurate.
Plus there is clock drift (certainly in dLive, and I presume maybe AHM too..)
Please add NTP to AHM!
+1. Time-based events depend on an accurate clock, and there’s no reason to have to manually set the clock periodically when NTP servers are available.
+1. This should have been there on launch. The drift on the AHM makes scheduled events a non-starter…
Bonus points for implementing DHCP Option 42 to learn NTP servers automatically. (But should still allow manually specifying them even if DHCP is selected for IP acquisition.)
Additionally, should add timezone support so we don’t have to update the offset twice a year.
.
.
