I tried to setup a HA green today. It failed miserably.
It was sane enough to come up to a webpage with a failed message on :8123. Looking through the logs, I see that a bunch of SSL stuff failed because the certs weren’t valid yet, meaning the clock was probably wrong somewhere. It didn’t attempt to get the time until well after all these things had failed (why doesn’t it do that first?) Thus, the install failed, it won’t recover, and i have a brick that I can’t flash for whatever reason.
The relevant log entries:
[supervisor.utils.whoami] Whoami service failed with SSL verification: Cannot connect to host services.home-assistant.io:443 ssl:True [SSLCertVerificationError: (1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1000)’)]
[supervisor.core] Whoami service SSL error
[supervisor.core] System time/date shift over more than 3 days found!
[supervisor.host.control] Setting new host datetime: 2025-02-21T17:58:06+00:00
[supervisor.core] Fatal error happening on load Task : Automatic time synchronization is enabled
[supervisor.docker.monitor] Started docker events monitor
[supervisor.jobs] ‘Updater.fetch_data’ blocked from execution, no supervisor internet connection
Where does HAOS get it’s time upon a fresh, new boot of a Green unit? Is it trying to get the time from the local router or is it using something else? Because if it’s trying to get time from the router, that’s why it failed - all devices on the network have their own time entries.