Installing Home Assistant Supervised on Ubuntu 18.04.4

[paul2nz]

Thanks you so much for this tutorial. the installation was so easy on my surface pro 3 running Ubuntu server 18.04

[123 (Taras)]

Just a small typo (that I would correct myself but I’m not permitted to edit the topic’s title) but it’s 18.04.4 not 18.04.04

[finity]

@123

I’m not permitted to edit the topic’s title

I just noticed a couple of days ago that my title editing privileges were removed too.

That must have been changed during the last forum maintenance session last week. Not that I’ve used it much but I was going to change one and noticed it wasn’t there.

[kanga_who (Jason)]

@finity

I just noticed a couple of days ago that my title editing privileges were removed too.

Yeah, I used to have some sort of wiki status and could convert others posts to a wiki to edit, but that has been removed. Probably just because I’m an ass though.

@123

it’s 18.04.4 not 18.04.04

Thank you, I have updated accordingly.

[imellor (Ian Mellor)]

Hi All,

Thanks for a great tutorial. I’ve followed the instructions and got HA working on an old machine I have here.
One thing I would like to do is map a USB port to be able to use Zigbee, what is the best way to do this? I see over in the Home Assistant Container tutorial they use a docker-compose.yaml file.
I can’t understand how this guide starts the docker machines, I see the install script uses “systemctl start hassio-supervisor.service” but can’t figure out what happens from there?

On the assumption that “hassio-supervisor” triggers everything else, I’ve run the command

sudo systemctl disable hassio-supervisor

I’ve also looked at Portainer to confirm that restart policy for hassio_supervisor is set to none.

So I am a bit of a loss as to how it is restarting on reboot?

Thanks

Ian

[kanga_who (Jason)]

See if this works for you.

@kanga_who

You may need to make a UDEV rule to mount it each boot so HA will see it. It’s been a while since I’ve done this, but these are my own notes on how to do that may help you.

SSH into your Pi using Putty and run this command;

lsusb

You’ll see a list of connected USB devices.

Bus 001 Device 004: ID 0578:0578 Intrinsix Corp.
Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I’ll use this card reader as an example.
Bus 001 Device 005: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader

The info you need from that line is 058f:6366 . This (058f) is the idVendor and this (6366) is the idProduct.

Use the below line and change the values to match those of your Z-Wave stick.

ACTION=="add", ATTRS{idVendor}=="XXXX", ATTRS{idProduct}=="XXXX", SYMLINK+="zwave"

Create a UDEV Rule and paste in the above line you just edited.

sudo nano /etc/udev/rules.d/99-usb-serial.rules

Ctrl+x to save, then reboot the Pi.

Reboot and test if symlink was created:

ls /dev/zwave

If that worked, you would tell HA that the Z-wave stick is lcoated at /dev/zwave

There might be a better way to do this, like I said , my notes are a little old

[imellor (Ian Mellor)]

Thank you, I’ll have a play.

[ejr1212]

Just installed Home Assistant Supervised on a dietpi system using these instructions. Everything seems to be working except the automation editor. I do not have drop downs for anything but the Devices. If I select Call Service, no drop down exists and I have to edit via yaml. Any help would be greatly appreciated.

[roamin-ronin]

Hey great tutorial! I just finished my install, but I don’t see the supervisor panel. I think my defunct core install is overriding the config.

2 Questions:
If I want to start over with a clean install with your tutorial, do I delete my config files and run something again?

How do I stop/restart/manage the containers? Is that what portainer is for?

I don’t see the addon store or anything. Am I supposed to?

Thanks again!

[olikilo (Chris Hendriks)]

everything ok up until ‘curl -sL “https://raw.githubusercontent.com/Kanga-Who/home-assistant/master/supervised-installer.sh” | bash -s’. I get no output and a quick return to the prompt. after I changed the command into ‘curl -L “https://raw.githubusercontent.com/Kanga-Who/home-assistant/master/supervised-installer.sh” | bash -s’ to get eventual errors I get:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- 0:00:02 --:–:-- 0curl: (7) Failed to connect to raw.githubusercontent.com port 443: Connection refused

I searched the internet for a couple of hours but could not find a solution or even what could cause this problem.

So I hope somebody here can help me with a solution or workaround.

[123 (Taras)]

If you paste the URL into your browser, it will display the contents of the installer script.

https://raw.githubusercontent.com/Kanga-Who/home-assistant/master/supervised-installer.sh

You could just copy the contents into a local file, change the file’s permissions to make it executable, then run it.

[olikilo (Chris Hendriks)]

Thx! Unfortunately I get then get the following:
Error response from daemon: Get https://registry-1.docker.io/v2/: dial tcp 107.23.149.57:443: connect: connection refused

[123 (Taras)]

Are you getting that message during the initial execution of the installer script or at the end when it attempts to start Home Assistant?

I’m asking because, if you review the installer script, there’s no reference to “dial”. Perhaps the error occurs when Home Assistant starts and then detects that there’s something wrong with the installation, possibility a missing prerequisite.

[imellor (Ian Mellor)]

@imellor

Hi All,

Thanks for a great tutorial. I’ve followed the instructions and got HA working on an old machine I have here.
One thing I would like to do is map a USB port to be able to use Zigbee, what is the best way to do this? I see over in the Home Assistant Container tutorial they use a docker-compose.yaml file.
I can’t understand how this guide starts the docker machines, I see the install script uses “systemctl start hassio-supervisor.service” but can’t figure out what happens from there?

On the assumption that “hassio-supervisor” triggers everything else, I’ve run the command

sudo systemctl disable hassio-supervisor

I’ve also looked at Portainer to confirm that restart policy for hassio_supervisor is set to none.

So I am a bit of a loss as to how it is restarting on reboot?

Thanks

Ian

I found a simple solution in the end: How are USB ports mapped? - #13 by 123

[anthonyjevans3 (AJEvans3)]

Hey all. I’m one of those noobs with docker. I’m trying to move my setup from pi to an nuc with Ubuntu and docker. Upon installing hassio supervised and trying to restore my backup, I can no longer access home Assistant. The webpage is blank and says it cannot load. I’ve tried removing the containers and reinstalling hassio and even used different backups but none of them successfully restore.

[kanga_who (Jason)]

What version were you coming from on the Pi? Did you check breaking/version changes between your backup and the current install if the versions are different?

You can also extract your backup .tar file and access all of your .yaml files and copy/paste them to the new install, then reboot. Doing this won’t restore your add-ons, but you it will get you up and running and you can then re-install the add-ons once you know you have a working config.

[123 (Taras)]

@anthonyjevans3

Upon installing hassio supervised

There is nothing in the world of Home Assistant called “hassio supervised”. It’s called Home Assistant Supervised.

The term hassio is not only deprecated it was never qualified with the word “supervised”. To avoid confusion, it’s best to use the correct terminology and not invent new ones.

[krisjanis2000 (Krisjanis lejejs)]

Just followed the installation tutorial and everything worked great except during the installation I somehow lost resolv.conf file and now I don’t have any DNS servers specified and so I cannot connect to any domain. The error when pinging is “ping: google.com: Temporary failure in name resolution”.
Do you have any suggestions on how to fix this?

[pharpe (Tom)]

I’m confused about this comment:

Please keep in mind that currently this installation method is not officially supported by the Home Assistant team, and therefore you are responsible for updating and managing updates and security on the base OS and no official support will be offered. This install method may cease to work at any time, so use at your own risk

.

According to the last blog post Home Assistant Supervised on Linux was one of the 4 supported installation methods.

Installation Methods & Community Guides Wiki

Is there a different official guide for that or is that an old comment that needs to be updated?

[kanga_who (Jason)]

Ubuntu is not a supported OS, making this installation method “officially” unsupported. You could follow the Debian guide that is also in the Community Guides section.

To stay officially supported, you must maintain a completely vanilla install of Debian 10, meaning no other software can be installed to the OS.