--- layout: page title: "Getting Started" description: "Step by step guide to get started with Home Assistant." date: 2014-12-18 22:57 sidebar: false comments: false sharing: true footer: true ---
The preparation of a Fedora 22 host will only take a couple of minutes. First install Python 3.4, git
and the other needed packages out of the Fedora Package Collection. This ensure that you receive updates in the future.
It's assumed that your user has an entry in the sudoers file. Otherwise, run the commands which needs more privileges as root.
```bash sudo dnf -y install python3 python3-devel git gcc ```CentOS is providing longtime support and often not shipping the latest release of a software component. To run, Python 3.x on CentOS Software Collections needs to be activated.
```bash git clone --recursive https://github.com/balloob/home-assistant.git python3 -m venv home-assistant cd home-assistant source bin/activate python3 -m homeassistant --open-ui ```
Running these commands will:
Scripts/activate.bat
)There is nothing else to do. If you run into any issues, please see the troubleshooting page.
You can run Home Assistant in demo mode by appending --demo-mode
to line 5.
If you want to update to the latest version in the future, run: scripts/update
.
By default, the access to port 8123 is not allowed. If you want to allow other hosts in your local network access, open port 8123.
```bash sudo firewall-cmd --permanent --add-port=8123/tcp sudo firewall-cmd --reload ```Home Assistant will serve its web interface on http://[IP address of the host]:8123.
If you want that Home Assistant is lauched automatically, an extra step is needed to setup systemd
. You need a service file to control Home Assistant with systemd
. The WorkingDirectory
and the PYTHONPATH
must point to your clone git repository.
You need to reload systemd
to make the daemon aware of the new configuration. Enable and launch Home Assistant after that.
If everything went well, sudo systemctl start home-assistant
should give you a positive feedback.
To get Home Assistant's logging output, simple use journalctl
.
If you want to update to the latest version in the future, run: scripts/update
and restart Home Assistant.
Those instructions were written for Fedora 22 Server and Workstation. They may work for Cloud flavor as well but this was not tested.
Coming soon...
Installation with Docker is straightforward. Adjust the following command so that /path/to/your/config/
points at the folder where you want to store your config and run it:
This will launch Home Assistant and serve its web interface from port 8123 on your Docker host.
When using boot2docker on OS X you are unable to map the local time to your Docker container. Replace -v /etc/localtime:/etc/localtime:ro
with -e "TZ=America/Los_Angeles"
(replacing America/Los_Angeles with your timezone)
Home Assistant uses Python 3.4. This makes installation on a Raspberry Pi a bit more difficult as it is not available in the package repository. Please follow the following instructions to get it up and running.
Step 1. Install pyenv
```bash curl -L https://raw.githubusercontent.com/yyuu/pyenv-installer/master/bin/pyenv-installer | bash ```After the installation is done, run:
```bash nano ~/.bashrc ```Then add these lines to the end of the file and save:
``` export PATH="$HOME/.pyenv/bin:$PATH" eval "$(pyenv init -)" eval "$(pyenv virtualenv-init -)" ```Log out and then back in so your bashrc is reloaded.
NOTE: the rest of the commands are not being run as sudo and will install python etc under you user's home directory.
Step 3. Install python 3.4.2 (this will take a few hours)
```bash pyenv install 3.4.2 ```Step 4. Create Python Virtual Environment
```bash pyenv virtualenv 3.4.2 homeassistant ```Step 5. Clone the source
```bash git clone --recursive https://github.com/balloob/home-assistant.git ```Step 6. Set the virtual environment
```bash cd home-assistant pyenv local homeassistant ```Step 7. Start it up
```bash python3 -m homeassistant ```It will be up and running on port 8123
If you want to update to the latest version in the future, run: scripts/update
.