Seeing as I started the thread that has created a lot of discussion, can I ask a favour?
Can people share their logbook, history loading and reboot times so I can figure out if I need to move up to an i3 or i5? Currently I’m running HassOS on the Intel® Celeron® Processor N2830 with 8GB RAM but it’s getting pretty old now. CPU usage is always below 10% though and I’ve got a lot of devices.
Mine:
Restart: 1m 30s
Logbook = 4 seconds
History = 15 seconds
I’m running https://ark.intel.com/content/www/us/en/ark/products/71484/intel-nuc-kit-dccp847dye.html and also have HassOS loaded. Also only 4GB of ram.
My reload time is 32 seconds
Logbook and history are both 3 seconds
Maybe is not correct to evaluate times independently on how complex is HA configuration and how many devices are defined in recorder and history.
Another thing to evaluate, also, is if on the Intel NUC there a virtualizer like Proxmox or VMWare ESXi, for example.
My system is an Intel NUC I3-8100 CPU with 16GB total ram and 250GB SSD with Proxmox as virtualizer and Hassio on a VM with 2 vCPU and 3GB ram based on Ubuntu 18.04 LTS. Hassio is installed in Docker and there is no other software installed, except the Hassio addons.
Mine are:
Restart = 1m 09s
Logbook = 2s
History = 2s
Thank you for your guide it helped me so much. I had a few hiccups as I couldn’t install docker with the code supplied kept getting 404 and permission denied error, a quick google search and got the latest code from docker site which worked.
Does anyone know if I’m able to run other things apart from hassio on Ubuntu with docker on Intel NUC? I’d like to install kodi and plex on my nuc as well is this possible?
It depends on the CPU you have.
Kodi & Plex need a lot of resources!
Intel i5 2.9ghz 16gb ram
You can try, installing in docker, if possible, so that it will be easy to uninstall if there is an issue.
I don’t know how much resources it can ask when it’s streaming or elaborating a HD or higher type of movie to the TV.
Thanks for your input, i may try it out on my old laptop which is running docker on ubuntu first to see how much resources it actually pulls before trying it on my Intel NUC. Will let you know on feedback how it goes.
A useless piece of info for ya.
I just moved from Intel NUC Kit-DN2820FYKH with 8GB RAM and 60GB SSD to a Intel® NUC Kit DC3217IYE with 4GB RAM and a 30GB mSATA SSD.
Even though the i3 is older and it has less RAM, I’ve seen quite an improvement in speed under pure HassOS.
All-in-all a worthwhile migration.
Z-wave
usb_path: /dev/serial/by-id/usb-0658_0200-if00
Thx for guide!
Im using Ubuntu 18.04 and successfully using
gunzip -c /home/ubuntu/Downloads/hassos_intel-nuc-2.12.img.gz | sudo dd of=/dev/sda
but when i click reboot, Ubuntu loads up instead of installation of Hassio - how can I proceed?
Ha doesn’t use much resources in my experience, here’s my docker stats on my HassIO machine:
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
639bb71f4ef9 homeassistant 2.86% 81.96MiB / 969.8MiB 8.45% 0B / 0B 590kB / 475kB 45
5291bb0c84b5 addon_core_nginx_proxy 0.03% 1.855MiB / 969.8MiB 0.19% 10.2GB / 10.2GB 1.61MB / 24.6kB 3
65f9627d5a30 addon_core_duckdns 0.00% 1.891MiB / 969.8MiB 0.19% 42.7MB / 4.16MB 13.1MB / 336kB 3
8e81363cb8b8 hassos_supervisor 0.00% 32.05MiB / 969.8MiB 3.31% 142MB / 129MB 82.1MB / 4.46MB 28
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
639bb71f4ef9 homeassistant 2.86% 81.96MiB / 969.8MiB 8.45% 0B / 0B 590kB / 475kB 45
5291bb0c84b5 addon_core_nginx_proxy 0.03% 1.855MiB / 969.8MiB 0.19% 10.2GB / 10.2GB 1.61MB / 24.6kB 3
65f9627d5a30 addon_core_duckdns 0.00% 1.891MiB / 969.8MiB 0.19% 42.7MB / 4.16MB 13.1MB / 336kB 3
8e81363cb8b8 hassos_supervisor 0.00% 32.05MiB / 969.8MiB 3.31% 142MB / 129MB 82.1MB / 4.46MB 28
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
639bb71f4ef9 homeassistant 3.01% 82.19MiB / 969.8MiB 8.48% 0B / 0B 590kB / 475kB 45
5291bb0c84b5 addon_core_nginx_proxy 1.25% 1.855MiB / 969.8MiB 0.19% 10.2GB / 10.2GB 1.61MB / 24.6kB 3
65f9627d5a30 addon_core_duckdns 0.00% 1.891MiB / 969.8MiB 0.19% 42.7MB / 4.16MB 13.1MB / 336kB 3
8e81363cb8b8 hassos_supervisor 0.00% 32.05MiB / 969.8MiB 3.31% 142MB / 129MB 82.1MB / 4.46MB 28
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
639bb71f4ef9 homeassistant 3.01% 82.19MiB / 969.8MiB 8.48% 0B / 0B 590kB / 475kB 45
5291bb0c84b5 addon_core_nginx_proxy 1.25% 1.855MiB / 969.8MiB 0.19% 10.2GB / 10.2GB 1.61MB / 24.6kB 3
65f9627d5a30 addon_core_duckdns 0.00% 1.891MiB / 969.8MiB 0.19% 42.7MB / 4.16MB 13.1MB / 336kB 3
8e81363cb8b8 hassos_supervisor 0.00% 32.05MiB / 969.8MiB 3.31% 142MB / 129MB 82.1MB / 4.46MB 28
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
639bb71f4ef9 homeassistant 54.62% 86.13MiB / 969.8MiB 8.88% 0B / 0B 590kB / 475kB 46
5291bb0c84b5 addon_core_nginx_proxy 3.05% 1.855MiB / 969.8MiB 0.19% 10.2GB / 10.2GB 1.61MB / 24.6kB 3
65f9627d5a30 addon_core_duckdns 0.00% 1.891MiB / 969.8MiB 0.19% 42.7MB / 4.16MB 13.1MB / 336kB 3
8e81363cb8b8 hassos_supervisor 0.00% 32.05MiB / 969.8MiB 3.31% 142MB / 129MB 82.1MB / 4.46MB 28
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
639bb71f4ef9 homeassistant 54.62% 86.13MiB / 969.8MiB 8.88% 0B / 0B 590kB / 475kB 46
5291bb0c84b5 addon_core_nginx_proxy 3.05% 1.855MiB / 969.8MiB 0.19% 10.2GB / 10.2GB 1.61MB / 24.6kB 3
65f9627d5a30 addon_core_duckdns 0.00% 1.891MiB / 969.8MiB 0.19% 42.7MB / 4.16MB 13.1MB / 336kB 3
8e81363cb8b8 hassos_supervisor 0.00% 32.05MiB / 969.8MiB 3.31% 142MB / 129MB 82.1MB / 4.46MB 28
CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS
639bb71f4ef9 homeassistant 6.87% 81.86MiB / 969.8MiB 8.44% 0B / 0B 590kB / 475kB 45
5291bb0c84b5 addon_core_nginx_proxy 0.00% 1.855MiB / 969.8MiB 0.19% 10.2GB / 10.2GB 1.61MB / 24.6kB 3
65f9627d5a30 addon_core_duckdns 0.00% 1.891MiB / 969.8MiB 0.19% 42.7MB / 4.16MB 13.1MB / 336kB 3
8e81363cb8b8 hassos_supervisor 0.00% 32.05MiB / 969.8MiB 3.31% 142MB / 129MB 82.1MB / 4.46MB 28
1GB of RAM is plenty for me!
Where is Ubuntu booting from?
From hard drive, ssd
EDIT: I gave up, was able to get some installation mode up and running but it stopped. Will try docker version.
Anyone having issues with an error of:
IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
I have updated the BIOS on my NUC6CAYH and have burned the image of HASSIO NUC 2.12 onto my SSD. I have retried this several times, but I can never get past this error no matter how long I wait. The NUC is connected via ethernet and appears on my network. Any ideas?
Has anyone successfully installed hassos (image installed directly - not Ubuntu followed by Docker, etc. ) on a recent NUC?
I just got a NUC8i3BEK, and am having no luck at all.
I don’t know if it’s because the NIC isn’t supported (listed as “Intel Ethernet Connection I219-V”) which isn’t explicitly listed on https://github.com/home-assistant/hassos/blob/fa6f7ac74ddba50e76f5779c613c56d937684844/Documentation/boards/nuc.md, but I’m assuming may be covered by the generic-ish “Intel Gigabit NIC” - or if it’s because the drive I’m installing it onto is an M.2 NVMe drive.
I’ve tried burning the image directly onto the drive before putting it in the NUC - and booting gives me the boot menu noted by @sapnho in post 122 in this thread (link to post 122: My steps to success for Hass.io on Intel NUC)
I also tried the Ubuntu live distro to use dd to burn the image; as well as the similar process in Parted Magic. Best result was the same HassOS boot menu. Worst result was no boot at all…
That was once I stopped accidentally overwriting the usb drive I was using to boot (/dev/sda) with the image (something seemed wrong in the back of my mind as I was copying and pasting the commands from here - seems that the NVMe drive gets a different name with “nvme” in there).
Just in case the NIC was the issue, I’ve tried I’ve also tried with a USB -> Ethernet adapter (that reports as Realtek) with the onboard LAN disabled - same result.
As a last ditch effort I attempted wifi, but without being able to boot I’m left with the “create CONFIG\etc.etc. on the first bootable device” method for wifi setup, and ended up with the same result (whether that was me not doing it correctly, or that it was done right and something else is the issue, I don’t know)
I’m running out of straws to clutch at…
Installing Ubuntu (to confirm that something boots successfully) onto the NUC works and boots. So worst case I go with Docker under Ubuntu, but the NUC running only hassos was really what I was after…
Hi,
I’, struggling getting this work as well. Currently I got the image gunzipped to the nvme drive which copied without any problems using Kali Linux, but when I then reboot and the Hassos installation should start it just 30 lines or so and then it stops at:
Waiting for Root Device PARTUUIDxxxxxxxxxxxxxxxxxxxxxxxxxx
usb 1-10: new full-speed USB device number 2 using xhci_hcd
usb 1-10: New USB device found…
usb 1-10: New USB device strings…
And then it gets stucks? Anyone came across that one before? Heeeelp…
EDIT: So I ended up trying with an older SSD SAMSUNG EVO 500GB I was lucky to have in an old laptop. Did same procedure and now it seems run further.
Will there be any support for nvme drives? I was trying with a Samsung, but maybe this is just waaaay over kill and we won’t even be able to notice the difference betwwen a Samsung 970 nvme disk and an older Samsung 860 EVO?
Are there any cons?
Thinking of doing this on an oldish laptop, but I’m worried about bluetooth and pulse CEC.
Are these drivers built into the HassOS image?
Same issues here. Have an nvme disk, so the first time I ran the script, it overwrote my boot USB drive 
Anyway, after finding out that I should instead use this command from a live ubuntu usb:
gunzip -c /media/ubuntu/UDISK/hassos_intel-nuc-2.12.img.gz | sudo dd of=/dev/nvme0n1 bs=4M conv=fsync
Note that I first tried /dev/sda (overwrote my usb running ubuntu live) and nvme0n1 (nvme0 doesn’t seem to work). It creates all the partitions (you can search for ‘disk’ and actually view the disks and the partitions), but get an error with Disk I/O whenever I try to boot from the disk:
Disk I/O error
Replace the disk, and then press any key
Update:
Replacing the nvme disk with a SATA one. Make sure to check what disk name (/dev/sd[xx]) you have to put in. Run ‘disks’ in Ubuntu, it should show the hard disk and the /dev/sd[xx], in my case /dev/sdc.
Then this is the final command:
gunzip -c /media/ubuntu/UDISK/hassos_intel-nuc-2.12.img.gz | sudo dd of=/dev/sdc bs=4M conv=fsync
Now it seems to work 
A few final tips:
Hello, new here, sorry for starting off by asking stupid questions
I’m about to get a NUC with an M.2 SSD that I will (only) run Hass.io on. Can someone please help me with my questions?
Is there still no installer for Hass.io on a NUC? I still need to put the SSD in a case and burn the image to it? Problem here is that the case cost as much as the SSD itself…
I understand that I can boot a Linux system from an USB and with that format the SSD and burn the image. What is the absolutely easiest way to do this? I know nothing about Linux/Ubuntu.
Any chance this process will be easier with the release of Home Assistant 1.0, in that case I will just wait.
Thanks!