If the preceding command returns the string systemd, you are likely using systemd.
If you want Home Assistant to be launched automatically, an extra step is needed to setup systemd. A service file is needed to control Home Assistant with systemd. The template below should be created using a text editor. Note, root permissions via ‘sudo’ will likely be needed. The following should be noted to modify the template:
If you want Home Assistant to be launched automatically, an extra step is needed to setup systemd. A service file is needed to control Home Assistant with systemd. The template below should be created using a text editor. Note, root permissions via sudo will likely be needed. The following should be noted to modify the template:
ExecStart contains the path to hass and this may vary. Check with whereis hass for the location./etc/systemd/system/home-assistant@[your user].service with [your user] replaced by the user account that Home Assistant will run as - normally homeassistant. For Ubuntu 16.04, the file is /lib/systemd/system/home-assistant.service and requires running this command sudo ln -s /lib/systemd/system/home-assistant.service /etc/systemd/system/home-assistant.service after file is created.sudo nano -w [filename] can be used with [filename] replaced with the full path to the file. Ex. sudo nano -w /etc/systemd/system/home-assistant@homeassistant.service. After text entered, press CTRL-X then press Y to save and exit.sudo nano -w [filename] can be used with [filename] replaced with the full path to the file. Ex. sudo nano -w /etc/systemd/system/home-assistant@homeassistant.service. After text entered, press CTRL-X then press Y to save and exit.[Unit]
Description=Home Assistant
@@ -92,7 +92,8 @@ ExecStart=/usr/bin/hass
WantedBy=multi-user.target
If you’ve setup Home Assistant in virtualenv following our python installation guide or manual installation guide for raspberry pi, the following template should work for you. If Home Assistant install is not located at /srv/homeassistant, please modify the ExecStart= line appropriately.
If you’ve setup Home Assistant in virtualenv following our Python installation guide or manual installation guide for Raspberry Pi, the following template should work for you. If Home Assistant install is not located at /srv/homeassistant, please modify the ExecStart= line appropriately.
[Unit]
Description=Home Assistant
After=network.target
@@ -106,7 +107,8 @@ ExecStart=/srv/homeassistant/bin/hass -c "/home/homeassistant/.homeassistant"
WantedBy=multi-user.target
If you want to use docker, the following template should work for you.
+If you want to use Docker, the following template should work for you.
[Unit]
Description=Home Assistant
Requires=docker.service
diff --git a/docs/installation/fedora/index.html b/docs/installation/fedora/index.html
index 9467c23606..cb34558c30 100644
--- a/docs/installation/fedora/index.html
+++ b/docs/installation/fedora/index.html
@@ -76,6 +76,22 @@
$ pip3 install homeassistant
+To isolate the Home Assistant installation a venv is handy. First create a new directory to store the installation.
+$ sudo mkdir -p /opt/homeassistant
+$ cd /opt/homeassistant
+
+
+Now switch to the new directory, setup the venv, and activate it.
+$ cd /opt/homeassistant
+$ pyvenv-3.5 .
+$ source bin/activate
+
+
+Install Home Assistant itself.
+$ pip3 install homeassistant
+
+
+Check the autostart section in the documentation for further details.