Hi;
I am attempting to update my home assistant installation instructions for ubuntu 20.04 virtual machine (installer.sh).
Old instructions: https://www.rossco.org/modules/TreeList/wrap.php?url=/SecureOffice_Files/Ubuntu_Server_Virtual_Machine.htm
Bottom Line:
At first Home Assistant install:
- HA up and operating as expected
Post Reboot: - HA not start
Can start by: - sudo systemctl stop hassio-supervisor.service
- sudo systemctl stop hassio-apparmor.service; sudo systemctl start hassio-apparmor.service
- sudo systemctl start hassio-supervisor.service
Next Reboot: - HA not start, with or without “sudo systemctl enable hassio-supervisor.service” pre-reboot
Here are my current installation steps on a Ubuntu VM:
• "sudo apt -y install postgresql postgresql-client"
• "sudo apt -y install python3-psycopg2"
• "sudo su - -c "/usr/bin/psql -c \"ALTER USER postgres WITH PASSWORD 'postgres';\"" postgres"
• "sudo su - -c "/usr/bin/createdb hass" postgres"
• "sudo apt -y install apt-transport-https ca-certificates curl software-properties-common lsb-release socat"
• "curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -"
• "lsb_release -a" to verify the Ubuntu version for the next command.
• 'sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu focal test"'. Include everything between, not including outer single quotes. "focal" (Ubuntu Version) may have to be replaced with the version determined previously. If the command does not work, this means that docker has not yet caught up to Ubuntu release, so, use "focal".
• "sudo apt upgrade"
• "sudo apt -y install docker-ce bash jq avahi-daemon dbus apparmor-utils network-manager". Wait for completion.
• "sudo systemctl disable ModemManager; sudo systemctl stop ModemManager" ModemManager interferes with serial Z-Wave and Zigbee devices.
• "cd /tmp; wget https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh; chmod +x installer.sh".
• "sudo bash installer.sh". Enter "not supported" if prompted. Enter "y" if asked to proceed. Wait for Hass.io installation to complete.
• Repeatedly enter "ls -la /usr/share/hassio/homeassistant/automations.yaml" until the file exists. Otherwise, next commands will fail due to home assistant not yet ready.
• Next two commands configure HA to load all automations (*.yaml files) from "/usr/share/hassio/homeassistant/automations" directory as opposed to single file "/usr/share/hassio/homeassistant/automations.yaml" which can get large and confusing. Best to configure automations in separate files per automation.
• "sudo mkdir -p /usr/share/hassio/homeassistant/automations"
• "sudo sed -i 's#include automations.yaml#include_dir_merge_list automations/#g' /usr/share/hassio/homeassistant/configuration.yaml".
• #systemctl enable hassio-supervisor.service
• "sudo docker ps" to display running docker containers as confirmation that Hass.io is running.
Also; ran into and fixed these issues with Ubuntu 20.04:
https://askubuntu.com/questions/1239503/ubuntu-20-04-and-20-10-etc-securetty-no-such-file-or-directory
https://askubuntu.com/questions/1242731/ubuntu-20-04-multipath-configuration
This appears to be root cause:
"multi-user.target: Job hassio-supervisor.service/start deleted to break ordering cycle starting with multi-user.target/start"
I can make the HA VM downloadable if neccessary.
Anyone seen this behavior before; suggestions?
Thanks; Bill