I got a new Raspberry Pi 3 a few days ago and flashed the Hassio image to a micro-SD following the installation from this page: https://home-assistant.io/hassio/installation/. Everything was up and running pretty fast. I got a nice CLI with commands like these:
hassio homeassistant restart
hassio supervisor logs
Great! After getting everything up and running I realized that I couldn’t access the root of my Raspberry Pi anymore, since Hassio seems to be the only thing to you can run using the ResinOS / Hassio images.
I want to run more software on the Raspberry Pi besides Home Assistant. So, I started looking into a ‘more advanced’ install. I chose the ‘install on generic Linux server’ option on the same page mentioned earlier. The instructions can be found here: https://github.com/home-assistant/hassio-build/tree/master/install#install-hassio
I followed everything and got it all up and running again. I can ssh into my Pi and I have to Docker containers running, both the homeassistant as well as the supervisor.
pi@raspberrypi:~ $ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
857506ac74da homeassistant/raspberrypi3-homeassistant "/usr/bin/entry.sh p…" 37 minutes ago Up 37 minutes homeassistant
8c5d22bd9c28 homeassistant/armhf-hassio-supervisor "/usr/bin/entry.sh p…" 10 hours ago Up 10 hours hassio_supervisor
Now, this is the part where it gets a bit confusing for me. As far as I know I installed Hassio, but in a different way so that I can access the Pi itself. So, where is the Hassio CLI? I can’t access it on my Pi and I also don’t have access to it when going into the Docker container using something like this:
docker exec -ti homeassistant /bin/bash
Does this mean that you only get the CLI using the Hassio images? If so, is that the only difference between my installation and the Hassio images? Or am I missing something here?