Sniff the network traffic of your ST hub. See, what NTP server it is connected to. Get this device:
Connect it to your network, reroute the NTP traffic on your router to the device.
1 Like
Hi, @frayer
The engineering team mentioned that the internal time stays in sync thanks to the connection to the ST platform. Therefore, we cannot guarantee it won’t drift if the Hub gets disconnected for a long time.
That confirms what I said all along, the difference is: I CAN guarantee that the internal clock drifts when offline for a while. Too bad that this is something the engineering team just shrugs off as acceptable, instead of offering a solution. Not to be rude, but we’re in 2024, send small cars to planet Mars and land spaceships on comets, and the ST hub cannot keep time without being online? My computers did that flawlessly 40 years ago…
1 Like
That’s a cool idea indeed. I think it wouldn’t actually need a dedicated hardware time server, and instead I could run an NTS server on any old local Raspberry pi. Sniffing the network traffic of the ST hub may be the biggest problem there. I have no idea when and how often the hub connects to an NTS server, and whether it actually does it at all. Maybe the hub gets the time from a Samsung site that also does other things, and re-routing the request would break these other things. Maybe the engineering team could enlighten me in this regard?
Me neither but I believe I’ve seen pool.ntp.org mentioned in the context of the hub.
2 Likes