On my c7, I ran Hub Diagnostics - and noted something in the network info. My NTP server is wrong. About 3 months ago I replaced my server which was on 1.120, the new server is 1.125.
My first reaction was I missed a value in my DHCP server options. Nope. All devices in my network and my dhcp server show correct. I was going to paste screen caps, but held off so I didn’t get chastized.
I am in the process of bouncing my Hub from hardset to dhcp hoping it will refresh, but I’ve always been DHCP and manage network devices on my server. Anyone else see this issue?
Switching to hardset IP didn’t affect it, not that I expected it would. The reporting ntp server IP is still wrong. rebooting now after switching back to DHCP which SHOULD pick up the solution - and I just checked it and it did NOT. Time between Hub and ntp server is off 8 seconds. theres a teeny tiny link on the hub details page in settings that lets you set your hub to the browser time stamp, that brought it closer - but still. NTP server should be adjustable and functional you’d think.
I think it's still true that HE doesn't provide built-in support NTP Settings via the DHCP standard. I haven't checked it lately, so I'm assuming that's still true.
If your hub is/was using something other than Google for NTP services, then it's like that either:
You've previously/manually overridden the NTP Settings in your HE OR;
This will show up in the /hub/advanced/ntpServer values, like the doc-link above.
These settings are per-hub, so you'll need to set it in every HE you're running, if you've got more than one.
You're doing it via your router to remap the requests from each HE
This is what I do, it's effectively NAT'ing certain hard-coded Network things in each of my HE's so they land where they should (ie. a D.R.Y. style config )
thank you! I didn’t dig in initially and look around for ntp in community posts and should have. I appreciate you doing it for me!
I note your comments - I was able to update the value using the endpoint /hub/advanced/ntpServer. When I entered it a webpage with my hub IP prefixed, it took a few seconds and returned a number of values - and the word 'set' hyperlinked near it. I selected the correct value, and reopened Hub Diagnostics - and lo and behold it reported correctly! thanks for that. Does it keep the time? I'm not clear - I guess I could set a trap on the ntp server or run wireshark to watch for it, but I'm content now as it is. If my time begins to float again, I now know I can go into the settings and find the little link to sync the browser to the device - that alone solved the 8 seconds disparity I had. Given the importance of time, one would think this particular area would be a bit more fleshed out. DHCP has provided the NTP option since 1995 or so. But who has the time to keep up with this stuff... ha. ha.
If you set it that way in HE directly, then the setting sticks.
Given the importance of time, one would think this particular area would be a bit more fleshed out. DHCP has provided the NTP option since 1995 or so. But who has the time to keep up with this stuff... ha. ha.
Yup, esp with HE's messaging of local & reliable processing. Without it's proprietary config HE is one Power/Network outage away from being non-functional, rules-execution wise, until service restoration.
Around here, that happens a few times a yr - XFinity usually goes out in sympathy within an hour of a Power outage
)