diff --git a/source/getting-started/index.markdown b/source/getting-started/index.markdown index 3914e1152e3..582e9ffa44c 100644 --- a/source/getting-started/index.markdown +++ b/source/getting-started/index.markdown @@ -83,10 +83,6 @@ scl enable rh-python34 bash
- - - -

Installation

@@ -106,7 +102,22 @@ python3 -m homeassistant --open-ui

  • Activate the isolated environment (on Windows, run Scripts/activate.bat)
  • Launch Home Assistant and serve web interface on http://localhost:8123
  • -

    If you run into any issues, please see the troubleshooting page.

    +
    + + +

    Post-Installation

    + +
    + + + + + + + + +
    +

    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. @@ -116,8 +127,92 @@ python3 -m homeassistant --open-ui 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.

    + +```bash +su -c 'cat <> /lib/systemd/system/home-assistant.service +[Unit] +Description=Home Assistant +After=network.target + +[Service] +Type=simple +WorkingDirectory=/home/fab/home-assistant/ +Environment="PYTHONPATH=/home/fab/home-assistant/" +ExecStart=/usr/bin/python3.4 -m homeassistant + +[Install] +WantedBy=multi-user.target +EOF' +``` + +

    You need to reload systemd to make the daemon aware of the new configuration. Enable and launch Home Assistant after that.

    + +```bash +sudo systemctl --system daemon-reload +sudo systemctl enable home-assistant +sudo systemctl start home-assistant +``` + +

    If everything went well, sudo systemctl start home-assistant should give you a positive feedback.

    + +```bash +$ sudo systemctl status home-assistant -l +● home-assistant.service - Home Assistant + Loaded: loaded (/usr/lib/systemd/system/home-assistant.service; disabled; vendor preset: disabled) + Active: active (running) since Thu 2015-06-25 23:38:37 CEST; 3min 13s ago + Main PID: 8557 (python3.4) + CGroup: /system.slice/home-assistant.service + └─8557 /usr/bin/python3.4 -m homeassistant +[...] +``` + +

    To get Home Assistant's logging output, simple use journalctl.

    + +```bash +sudo journalctl -f -u home-assistant +``` + +

    + 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:

    @@ -133,6 +228,7 @@ When using boot2docker on OS X you are unable to map the local time to your Dock
    +

    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.