I am trying setup a new fresh install of Home Assistant OS on my raspberry pi4 4gb but it never finishes preparing Home Assistant.
I tried with 2 MicroSD and tried both 64 and 32 bit version, various versions of hassio os (6.3, 6.2, 5.0) with the same results.
The raspberry is connected directly to my ISP router, I do not have pihole or similar
I tried to set a static ip address, an alternative dns (8.8.8.8 and 1.1.1.1)
By clicking on the blue dot, these errors on the log are repeated every 30 seconds
I can regularly access from the web page but it seems not to be connected to
internet
21-02-03 00:22:17 WARNING (MainThread) [supervisor.jobs] 'Updater.fetch_data' blocked from execution, no supervisor internet connection
21-02-03 00:22:17 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec
Anyone have any advice on how to fix this? I have been stuck on the setup for 4 days with no results
I am also having the same problem on my raspberry pi 3b+ and have tried installing Home Assistant OS versions 6.6 and 7.0. Does anyone having any idea on what might be the problem here or any tips on anything we can try to help narrow down the issue?
One side note that might hint at what’s going on. I had Home assistant v 6.6 install successfully on the raspberry pi that I’m using. The microSD card went out, so I grabbed a new one, attempted to reinstall the OS, and ran into this issue.
I still haven’t found the cause of the problem (there seems to be some issue on my new ISP router with the time server) but I was able to find a temporary solution to start the first installation.
You need a USB stick named CONFIG with a file named “timesyncd.conf” with this inside
Unfortunately that solution didn’t work for me, but I do think you’re on the right track. I’m seeing the following error message when I plug in a monitor and watch it boot up.
Failed to start Wait Until Kernel Time Synchronized
See ‘systemctl status systemd-time-wait-sync.service’ for details
When I execute the above status command, I see the the job failed with a timeout result.
I was able to work around this issue by enabling wifi and setting that connection up. This will get me by for now, but I’ll having to keep playing with it to see if I can get it working on the ethernet connection.
