The only requirement is that you have a Raspberry Pi with a fresh installation of Raspbian Jessie/Jessie Lite connected to your network.
-wget -Nnv https://raw.githubusercontent.com/home-assistant/fabric-home-assistant/master/hass_rpi_installer.sh && bash hass_rpi_installer.sh; -
ssh pi@your_raspberry_pi_ipbash
+wget -Nnv https://raw.githubusercontent.com/home-assistant/fabric-home-assistant/master/hass_rpi_installer.sh && bash hass_rpi_installer.sh;
+Installation will take approx 1-2 hour’s depending on the model of Raspberry Pi the installer is being run against.
BRUH automation has created a tutorial video explaining how to install Raspbian on your Raspberry Pi and install Home Assistant using the all-in-one installer.
-Once rebooted, your Raspberry Pi will be up and running with Home Assistant. You can access it at http://your_raspberry_pi_ip:8123.
+Once rebooted, your Raspberry Pi will be up and running with Home Assistant. You can access it at http://your_raspberry_pi_ip:8123.
-The Home Assistant configuration is located at /home/hass. The virtualenv with the Home Assistant installation is located at /srv/hass/hass_venv. As part of the secure installation, a new user is added to your Raspberry Pi to run Home Assistant as named, “hass”. This is a system account and does not have login or other abilities by design. When editing your configuration.yaml files, you will need to run the commands as “Sudo” or switching users. Setting up WinSCP to allow this seemlessly is detailed below.
The Home Assistant configuration is located at /home/hass. The virtualenv with the Home Assistant installation is located at /srv/hass/hass_venv. As part of the secure installation, a new user is added to your Raspberry Pi to run Home Assistant as named, hass. This is a system account and does not have login or other abilities by design. When editing your configuration.yaml files, you will need to run the commands with “sudo” or by switching user.
+Windows users - Setting up WinSCP to allow this seemlessly is detailed below.
By default, installation makes use of a Python Virtualenv. If you wish to not follow this recommendation, you may add the flag -n to the end of the install command specified above.
The All-In-One installer script will do the following automatically:
- -hass service account/srv/hass/src/open-zwave-control-panelWindows Users - Please note that after running the installer, you will need to modify a couple settings allowing you to “switch users” to edit your configuration files. The needed change within WinSCP can be seen here: Imgur
+The All-In-One installer script will do the following automatically:
+* Create all needed directories
+* Create needed service accounts
+* Install OS and Python dependencies
+* Setup a python virtualenv to run Home Assistant and components inside.
+* Run as hass service account
+* Install Home Assistant in a virtualenv
+* Build and install Mosquitto from source with websocket support running on ports 1883 and 9001
+* Build and Install Python-openzwave in the Home Assistant virtualenv
+* Build openzwave-control-panel in /srv/hass/src/open-zwave-control-panel
+* Add both Home Assistant and Mosquitto to systemd services to start at boot
To upgrade the All-In-One:
-* Login to rPi ssh pi@IPADRESS
-* Change to hass user sudo su -s /bin/bash hass
-* Change to virtual enviroment source /srv/hass/hass_venv/bin/activate
-* Update HA sudo pip3 install --upgrade homeassistant
ssh pi@your_raspberry_pi_ipsudo su -s /bin/bash hasssource /srv/hass/hass_venv/bin/activatepip3 install --upgrade homeassistant
+
+Windows Users - Please note that after running the installer, you will need to modify a couple settings allowing you to “switch users” to edit your configuration files. The needed change within WinSCP can be seen here: Imgur
diff --git a/sitemap.xml b/sitemap.xml index 6a5e02b708..cabedb2532 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1681,26 +1681,26 @@