HA on Intel NUC - which way?

Installation
1

Hi,
my raspberry crashed several times now and gets more slowly in the past few months, so I bought me an Intel NUC5CPYH (celeron) with an 256 GB SSD an 8 GB RAM in it.

Now, what would be the best way to use HA? For over a year I was using HassOS and had no problems with it, so normaly I would use it with the NUC, too.
But I´m also a guy who likes to try out new things if there are enough benefits, like using HA with Docker/Ubuntu for example.

To be honest, I have limited Linux knowledge and no knowledge of Docker at all. Do you think it would be worth a try reading tutorials, how-tos etc, to setup an unbuntu/docker server, or just stick to HassOS again?

Thanks ,
Philipp

2 Likes
2

Well if you like learning new stuff… go dor Debian/Docker/Hass.io it’s reasonably straight forward. If you use HassOS on the NUC it’s pretty well crippled and will only run HA.

But it’s a personal thing if you want a new challenge/knowledge or not.

3

To be honest installing Ubuntu Server and then using docker-compose with docker based installation will be the easiest. You do not care about dependencies etc. Those are taken care of by image creator - inside docker container.

Upgrading/downgrading HA is like changing one line when using docker-compose…

4

Thanks for the answers:

There are 2 things I´m worried about, but maybe I havn´t read enough yet:

  • I can´t use plugins the way I´m using them now with HassOS?
  • I can´t update over the WebGui like with HassOS? Do I have to update manually?

But I think I give it a try :grinning:

5

If you install hass.io as a generic Linux install (my suggestion) you will have exactly the same functionality with addons and everything else you have now with HassOS. (Including updates) You will also have real Linux and can install other stuff as well… best of both worlds,

6

What Linux distribution would you recommend for a generic install?

7

Ubuntu is a good starting point because its well documented online and easy to use. or you could try Debian (which Ubuntu is based off)

8

I prefer Debian as it’s less likely to toast itself when you do an upgrade but whatever floats your boat.

1 Like
9

I was exactly in the same boat. I ended up using ubuntu with hassio docker.
Debian had some problems i could not fix on my nuc.
You can find all the hurdles i had to take (limited linux knowledge myself) here:

3 Likes
10

I haven’t seen a failed upgrade since 12 → 14…and I manage somewhere in the neighborhood of 30 Ubuntu server instances. Please stop the FUD.

1 Like
11

I use Ubuntu 18.04 (Desktop) on my NUC, and run HAss in a Python Virtual Environment.
Been running this for more than a year. Works for me :slight_smile:

12

I went from a bust RPi to NUC and followed these instructions

https://www.smarthomebeginner.com/install-ubuntu-server-from-usb/ - to install Ubuntu

https://www.smarthomebeginner.com/docker-home-media-server-2018-basic/ - to set up Docker and install HA etc

14

No. I’m just sick of seeing the same FUD spread around to the newbies.

Give them a choice, let them research and decide for themselves.

2 Likes
17

I plan moving to NUC and my research conclusion is to run HA in ESXI/Proxmox cause linux way will make this linux a point of failure if I’ll install something wrong on linux OS

Running in ESXI/Proxmox allows VM’s in addition to Dockers and will isolate each thing and allow easy and fast snapshot/restore

Another plus is Proxmox can be run from USB so the SSD will be storage for all VM’s

18

Tip for Proxmox (and possibly ESXi) - when you create the VM, it doesnt automatically add an virtual sound card, which resulted in my HassIO logs being spammed with “no audio device enabled”

You can add one in easily in the System tab (i think) - I only discovered it last night after a week of wondering why I was getting such log spam

19

@AdmiralRaccoon, This has been covered in a number of other similar threads recently. I will post the same info I have in other threads, plus some extra steps and info, hopefully it will help you.

This, in my experience, is the fastest and simplest way to deploy Hass.io on a NUC (or other PC, RPi, etc) running Ubuntu Desktop or Server as the OS in this case (or using Raspbian on an RPi3). I have used this method myself on a NUC, an RPi3 and recently an old Dell Optiplex 990. The method is repeatable and simply, it just works.

1.) Get ubuntu form Here. Use the torrent link - either 16.04 LTS, or 18.04 LTS. Server or desktop won’t really matter. I have recently changed to using Server 18.04.03 LTS myself.

2.) Make a bootable Ubuntu USB using Rufus. Available Here

3.) Install Ubuntu to the NUC using the bootable USB you have just made, once the install and setup is complete, update the OS via a terminal window with;

sudo apt-get update && sudo apt-get upgrade -y

4.) If you have a current HA install on another machine, backup all your yaml files, lovelace config, etc to your PC, USB or HDD. A handy way to do that is using WinSCP, available Here. Connect to your current install and copy/paste all your config to a PC.

5.) Follow this guide , specifically from the line " To prepare your machine for the Hass.io installation, run the following commands:"

Copy each line of the below commands and paste them into a terminal window, and execute them one at a time.

sudo -i
apt-get install software-properties-common
add-apt-repository universe
apt-get update
apt-get install -y apparmor-utils apt-transport-https avahi-daemon ca-certificates curl dbus jq network-manager socat
curl -fsSL get.docker.com | sh

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

6.) Copy your yaml files to the NUC, normally in the location /usr/share/hassio/homeassistant

7.) Install Portainer to manage your Docker containers for anything that you might want to run that isn’t available through Hass.io or HACS.

sudo docker run -d -p 9000:9000 --name portainer --restart always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer

I followed this myself just this week to do a fresh install on a Dell Optiplex SFF 990, and the entire process took me 19mins. I timed it just to see. This included making the bootable USB, Ubuntu install, updates, installing and having HA up and running. Very easy.

The time it takes will change depending on the speed of the CPU of the NUC/PC/RPi you use, but this should give you a good indication of just how fast and easy it is.

EDIT
Follow this guide

5 Likes
20

Thanks Jason, that was really helpful.

Now I´m struggling with some basic Linux Problems to get started:

Am I right that I don´t need the Samba Addon for Home Assistant anymore, but instead the Samba server for Ubuntu, to access and edit the Configuartion.yaml?
I have installed Samba, and made this share:

[config]
path = /usr/share/hassio/homeassistant/
public = yes
writable = yes
comment = hassio config dir
printable = no
guest ok = yes

And ran this command:

sudo chmod 777 /usr/share/hassio/homeassistant/

I´m able to read and create files, but I´m unable to edit, as I´m not allowed to save the files.

Have I missed something?

21

Another vote for Ubuntu server with docker compose.

There is a project called dock starter that is pretty cool if you want to run Plex radarr etc. It has lots of useful scripts auto backup auto upgrade etc.

3 Likes
22
23

@AdmiralRaccoon This may not be best practice, but this works for me. Log into terminal/Putty.

Backup currnet config
sudo mv /etc/samba/smb.conf /etc/samba/smb.conf.bak

Edit the Samba config file
sudo nano /etc/samba/smb.conf

Press and hold control+K to remove all the text

Copy the below and paste in;

[global]
workgroup = WORKGROUP
server string = Samba Server %v
netbios name = Ubuntu
security = user
map to guest = bad user
name resolve order = bcast host
dns proxy = no
bind interfaces only = yes

[Public]
path = /
writable = yes
guest ok = yes
guest only = yes
read only = no
create mode = 0777
directory mode = 0777
force user = nobody
create mask = 0777
directory mask = 0777
force user = root
force create mode = 0777
force directory mode = 0777
hosts allow =

Ctrl+X to save

Create a username and password
sudo smbpasswd -a YOUR_USERNAME

Restart the samba service
sudo service smbd restart

1 Like