I’m in a similar boat - followed the instructions and I don’t see the homeassistant container come online. The instructions in the script don’t mention anywhere that supervisor is in charge of starting homeassistant, it makes sense in hindsight but that was very confusing.
When I docker logs -f hassio_supervisor
I see:
20-02-14 19:03:31 INFO (MainThread) [hassio.core] Hass.io is up and running
20-02-14 19:03:46 WARNING (MainThread) [hassio.tasks] Watchdog found a problem with Home Assistant Docker!
20-02-14 19:03:46 INFO (SyncWorker_2) [hassio.docker.interface] Start homeassistant/raspberrypi4-64-homeassistant
20-02-14 19:03:51 ERROR (MainThread) [hassio.homeassistant] Home Assistant has crashed!
20-02-14 19:03:51 ERROR (MainThread) [hassio.tasks] Watchdog Home Assistant reanimation fails!
So it’s also possible for HA to crash out and cause the symptoms described. Regretfully, there was no indication of a problem until I inspected the supervisor’s logs.
Next question: What’s the easy way to troubleshoot why this is crashing?
Interestingly, I notice that my docker does have an image for homeassistant/raspberrypi4-64-homeassistant and if I try to docker run ...
it then docker pulls down and extracts more layers it didn’t already have. That suggests that homeassistant/raspberrypi4-64-homeassistant hasn’t been started yet.
EDIT: Making progress…
When I ran the homeassistant/raspberrypi4-64-homeassistant
directly I got a exec format error
message, and more googling led me to understand I chose the wrong machine type.
When I do docker run .... homeassistant/raspberrypi4-homeassistant
then homeassistant appears to start normally. (I can access the HA in my browser and the logs look good)
I re-ran the install script, passing the corrected machine flag. This fixed my hassio config file, but I had to stop and remove the supervisor container and then restart the service because the supervisor service “remembered” the wrong homeassistant container image.
curl -sL https://raw.githubusercontent.com/home-assistant/hassio-installer/master/hassio_install.sh | sudo bash -s -- -m raspberrypi4-64
docker rm --force hassio_supervisor
sudo systemctl restart hassio-supervisor.service
At this point I still wasn’t working. The supervisor container’s logs showed that I didn’t have the new docker image. I’m not sure why. I simply “ran” that image to download it and re-restarted the service.
docker run homeassistant/raspberrypi4-homeassistant
sudo systemctl restart hassio-supervisor.service
And now the supervisor is happy, the actual HA container is happy, and I’m happy.
@mmhass I hope this helps you with your issue.