Can not connect to hassos after boot - date not set on boot

Installation Home Assistant OS
1

On (re)booting the date does not get set and as a result, HA refuses to connect, perhaps because it makes a certificate invalid. Setting the date on the cli and restarting hassio supervisor fixes the problem but requires physical access to a console display and keyboard and has to be done even on a soft reboot.

In the middle of the console output on startup after boot is the following preceded by two red asterisks:

(1 of 2) A start job is running for Wait Until Kernal Time Synchronized (13s / no limit)

Perhaps this has something to do with it?

my system:

|arch|armv7l|
|---|---|
|chassis|embedded|
|dev|false|
|docker|true|
|docker_version|19.03.8|
|hassio|true|
|host_os|HassOS 4.11|
|installation_type|Home Assistant OS|
|os_name|Linux|
|os_version|4.19.127-v7l|
|python_version|3.7.7|
|supervisor|229|
|timezone|America/New_York|
|version|0.112.4|
|virtualenv|false|
2

Do you have it connected to the internet? It may be doing an ntp request to get the time.

3

I have very robust internet access- Gbit fiber and Google mesh WiFi. I ran ntp test on my windows system and it is fine. The question is why does the RPi hassos not connect? Judging from other queries on the forum here I am not the only person seeing this. Hassos is unusable for me as it stands now.

4

I loaded Raspberry pi os and it has the same problem. The date is wrong and I can not update it on the pi os.The time of day however is correct.

5

Then something is wrong with your network, Can you get an ntp update after boot?

6

Can you do a

sudo raspi-config

and check your regional/localisation settings and network settings?

7

Here’s what I have discovered:

  1. regional and localization settings seem fine.
  2. playing with the Raspberry Pi OS settings I find that time control config file in systemd contained this line:

FallbackNTP=0.debian.pool.ntp.org 1.debian.pool.ntp.org 2.debian.pool.ntp.org 3.debian.pool.ntp.org

None of those addresses are pingable so the date and time don’t get set on boot. However, If I change that line to FallbackNTP=0.us.pool.ntp.org 1.us.pool.ntp.org it boots fine and the proper date and time are set.

So perhaps the question is how do I change the Hassos boot script to use a different NTP service?

8

If those hosts are not pingable then either your network is broken or there is temporary outage of those hosts (which would be unusual for 4 pool addresses).

Fix your DNS.

9

Well, my first DNS server was Google, the default for their mesh wifi router. The ntp servers would not ping. I changed t he DNS server to my ISP’s. Still no ping. I don’t think the problem was DNS on my end. No matter though, those NTP servers are back up and hassos is working now.