diff --git a/atom.xml b/atom.xml index 10b487eabb..e24c830ad5 100644 --- a/atom.xml +++ b/atom.xml @@ -4,7 +4,7 @@
Note this command is one line and not run as sudo
++ Note this command is one-line and not run as sudo. +
Installation will take approx. 1-2 hours depending on the Raspberry Pi model the installer is being run against. The installer will identitfy what Raspberry PI hardware revision you are using and adjust commands accordingly. A complete log of the install is located at: /home/pi/fabric-home-assistant/installation_report.txt
The installer has been updated to simply log any errors encountered, but resume installing. Please consult the “installation report” if your install encountered issues.
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/.homeassistant
. 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.
The Home Assistant configuration is located at /home/hass/.homeassistant
. The virtualenv with the Home Assistant installation is located at /srv/hass/hass_venv
. As part of the secure installation, a new user (hass) is added to your Raspberry Pi to run Home Assistant. 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 at the end of this page. +
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.
To upgrade the All-In-One setup manually:
fab upgrade_homeassistant
To launch the OZWCP webapp:
+To launch the OZWCP web application:
ssh pi@your_raspberry_pi_ip
/dev/ttyACM0
and hit initializedon’t check the USB box regardless of using a USB based device
++ Don’t check the USB box regardless of using a USB based device. +
-Windows Users - Please note that after running the installer, you will need to modify settings allowing you to “switch users” to edit your configuration files. The needed change within WinSCP is: Environment -> SCP/Shell -> Shell and set it to sudo su -
.
If you are Windows users who is using WinSCP, please note that after running the installer, you will need to modify settings allowing you to “switch users” to edit your configuration files. The needed change within WinSCP is: Environment -> SCP/Shell -> Shell and set it to sudo su -
.
You must have Vagrant and Virtualbox installed on your workstation.
-Download the home-assistant source code by either downloading the .zip file from GitHub releases page, or by using Git
@@ -114,7 +114,7 @@ cd home-assistant/virtualization/vagrant The following instructions will assume you changed your working directory to be home-assistant/virtualization/vagrant. This is mandatory because Vagrant will look for informations about the running VM inside that folder and won’t work otherwise -vagrant up @@ -124,7 +124,7 @@ The following instructions will assume you changed your working directory to beThis will download + start a virtual machine using Virtualbox, which will internally setup the development environment necessary to start Home Assistant process and run test suite as well. After the VM has started succesfully, Home Assistant frontend will be accessible locally from your browser at http://localhost:8123
-Stopping Vagrant
+Stopping Vagrant
To shutdown the Vagrant host:
@@ -136,7 +136,7 @@ The following instructions will assume you changed your working directory to beTo start it again, just run
-vagrant up
Restarting Home Assistant process to test changes
+Restarting Home Assistant process to test changes
The root
@@ -148,7 +148,7 @@ The following instructions will assume you changed your working directory to behome-assistant
directory on your workstation will be mirrored with/home-assistant
inside the VM. Invirtualization/vagrant
there’s also aconfig
folder that you can use to drop configuration files (here you can find more information on how to configure HASS).
To run tests against your changes:
@@ -158,7 +158,7 @@ The following instructions will assume you changed your working directory to beTo completely remove the VM:
diff --git a/sitemap.xml b/sitemap.xml index 01c88f0705..c0fbbf35e9 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -1797,26 +1797,26 @@