Pi5: Core 2026.4.2, supervisor 2026.04.0, OS 17.2
Time in the HA system is 2 minutes slow, so Authenticator does not work. This also happens on cold starts. Have GHz Ethernet,100GHz broadband, high end router. IPv4 and IPv6 both working properly. Stable power with PoE top hat. System has been working fine for at least a year with all firmware and software kept current. I have installed a few new apps lately. I have not tried restoring an older Core. Any thoughts?
Any chance that your router is blocking the RPi from reaching Internet-based time servers?
1 Like
HA use a SNTP client, which only sync time a few times a day and between those events the time can drift and skew.
The chrony app can be used to get a NTP client instead that keeps time all the time at the cost of a little network usage.
3 Likes
Same issue here. RPi 5, currently on HA OS 17.3 but started happening on 17.2. Core has been updated since it started too, so I can't pin the exact version.
Noticed the system clock had drifted by about 7 minutes, causing time-based automations to fire early. The drift kept coming back after HA and OS restarts and updates. dt_synchronized: true in host info the whole time.
This is a recent issue for me as well. The setup has been running stable for years before this started. Something changed in the past month or two that made the drift noticeable.
External NTP is reachable from the Pi (confirmed by testing from the SSH addon), so it's not a network or firewall issue.
Seems like systemd-timesyncd isn't polling frequently enough to keep up with the Pi 5's clock drift, but the question is why this only started recently.
HA use as standard a SNTP client and not a NTP client.
Look up the difference and you will have the explanation for your drift.