Installing Hass.io on Ubuntu Server 18.04

Prerequisites

Create a snapshot or two of your current Hass.io installation.

Install Ubuntu Server 18.04 LTS

• For instructions on how to install Ubuntu Server, see Canonicals documentation here.
• For instructions on how to make a installable USB key, see:
  • Windows
  • macOS
  • Ubuntu

Set the system time-zone

# Select your Country and Reigon via the config flow.
sudo dpkg-reconfigure tzdata

# Verify time-zone settings.
timedatectl

Set up a static IP

It is preferable to set a static IP duirng the OS installation. If you have already done so then this section can be skipped.

If you need to create a static IP configuration then use the provided commands to determine the name of your network interface then reference the information below and alter the file to reflect similarly to the example. Be sure to replace all PLACE_HOLDER variables with your information.

# Display network interface information.
nmcli

# Open network configuration file for editing.
sudo nano /etc/netplan/50-cloud-init.yaml

Replace INTERFACE, IP_ADDRESS, CIDR_MASK and GATEWAY_IP with your details.

# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    ethernets:
        INTERFACE:
            addresses:
            - IP_ADDRESS/CIDR_MASK
            dhcp4: false
            gateway4: GATEWAY_IP
            nameservers:
                addresses:
                - GATEWAY_IP
                - 1.1.1.1
                - 9.9.9.9
                - 8.8.8.8
    version: 2

Apply the configuration and reboot the server.

# Apply the config. Press ENTER again to accept the changes.
sudo netplan try

# Reboot the host.
sudo reboot now

Installing Hass.io

Once logged in to the machine, open a terminal and run the following commands. These commands were recommended when this document was last edited. You are strongly encouraged to visit the Home Assistant website and use the most up-to-date commands found in the official installation documentation.

sudo -i

add-apt-repository universe

apt update && apt upgrade -y

apt install -y software-properties-common apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat

systemctl disable ModemManager

systemctl stop ModemManager

curl -fsSL get.docker.com | sh

curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" | bash -s

Finishing Up

• Install either the Samba addon or the community IDE addon.

• Configure, start, and open the chosen addon.

• Use the addon to upload the largest snapshot to the "backup" directory.

• Open the side-menu then click Hass.io > Snapshots.

• Click the Reload icon in the upper-right corner of the pane.

• Click the desired snapshot, ensure all boxes are selected, then click 'WIPE & RESTORE'.

• After it is complete, log in and verify everything is working.

Important Note

If you are going to use either of the DNS Ad-blocking addons (AdGuard Home/Pi-hole) then it is important to follow these steps in their given order; if you will not be using any DNS Ad-blocking addons then this section can be skipped:

• Install the desired ad-blocking addon and notice that after starting it there are errors related to 'address/port is already in use' in the logs. This is because Ubuntu has it's own DNS service running on port 53.

• Run the following commands in the Ubuntu host's terminal to disable its DNS service so the addon will be able to start successfully.

# Determine the system's hostname.
hostname

# Open '/etc/hosts' for editing.
sudo nano /etc/hosts

# Add the following as the first line of the file, replacing YOUR_HOSTNAME with your system's hostname.
127.0.0.1         YOUR_HOSTNAME

# Disable systemd-resolved.service from auto-starting.
sudo systemctl disable systemd-resolved.service

# Reboot the host.
sudo reboot now

If you decide to revert to not using either of the DNS Ad-blocking addons then you will need to re-enable systemd-resolved.service on the host then uninstall the addon from within Home Assistant.

sudo systemctl enable systemd-resolved.service

sudo reboot now