How to: Instal HomeAssistant Core on Raspberry Pi 4B
How to: Instal HomeAssistant Core on Raspberry Pi 4B
Prerequisites
This guide assumes that you already have an operating system setup and have installed Python 3.8 (including the package python3-dev
) or newer.
INSTALL DEPENDENCIES
Before you start make sure your system is fully updated, all packages in this guide are installed with apt
, if your OS does not have that, look for alternatives.
Install the dependencies:
CREATE AN ACCOUNT
Add an account for Home Assistant Core called homeassistant
. Since this account is only for running Home Assistant Core the extra arguments of -rm
is added to create a system account and create a home directory. The arguments -G dialout,gpio,i2c
adds the user to the dialout
, gpio
and the i2c
group. The first is required for using Z-Wave and Zigbee controllers, while the second is required to communicate with GPIO.
CREATE THE VIRTUAL ENVIRONMENT
First we will create a directory for the installation of Home Assistant Core and change the owner to the homeassistant
account.
Next up is to create and change to a virtual environment for Home Assistant Core. This will be done as the homeassistant
account.
Once you have activated the virtual environment (notice the prompt change to (homeassistant) homeassistant@raspberrypi:/srv/homeassistant $
) you will need to run the following command to install a required Python package.
Once you have installed the required Python package it is now time to install Home Assistant Core!
Start Home Assistant Core for the first time. This will complete the installation for you, automatically creating the .homeassistant
configuration directory in the /home/homeassistant
directory, and installing any basic dependencies.
You can now reach your installation via the web interface on http://homeassistant.local:8123
. or http://<IP ADDRESS>:8123
Running HomeAssistant Command for the First time
When you run the hass
command for the first time, it will download, install and cache the necessary libraries/dependencies. This procedure may take anywhere between 5 to 10 minutes. During that time, you may get “site cannot be reached” error when accessing the web interface. This will only happen for the first time, and subsequent restarts will be much faster.