Hi there. I struggled with this as it does not seem well documented so here is what I did to get it to work after a day and six failed attempts:
Hardware:
- Intel NUC Kit-DN2820FYKH (Circa 2013)
- 16GB USB Thumb Drive
- 60GB Patriot SSD
EDIT May 2020. NVMe drives are now supported with the Dev version. Updated instructions are here as the downloaded HassOS NUC file is NOT AN INSTALLER, it’s a drive image. You need to now either remove the SSD/HDD and image it directly or use the instructions in the aforementioned thread and use a Live Linux Distro to image the downloaded gz file using Linux commands. If you can, remove the drive as that is so much easier.
-
Ensure your NUC is running the latest BIOS. F2 on boot to explore setup and find version. Download .bio file from Intel and use F7 on boot to update BIOS from USB drive.
-
Once updated, go back into the BIOS and choose F9 to set to factory defaults then F10 to save and exit.
-
Format the SSD to NTFS (may not be required but after many attempts, I did that anyway).
-
Using Etcher, burn the NUC Hass.io image to the USB drive.
-
If you want to use WiFi, you’ll need to edit
file: /system-connections/resin-sampleon the USB drive based on the example here https://docs.resin.io/deployment/network/2.x/#wifi-setup. -
Insert the the USB drive into your NUC and turn it on.
-
All going well, it should come up with a black screen saying Booting to 'flash’. After a few splashes of Linux code, it should then present you with Hass.io image but with no text like this.
-
Leave the system alone until the NUC turns itself off (<3m). It’s writing the required files to the SSD during this phase.
-
Once off, remove the USB key and turn the NUC back on. All going well it should say something like Booting to ‘boot’.
-
After a few seconds, it should come up with the Hass.io image but this time with the standard text shown below. Wait at least 20m and you should be good to go.
Lastly, in order to get SAMBA working, you’ll have to figure out what the name of your WLAN or ETH adapter is as eth0 and wlan0 are not valid for the NUC. Simply remove eth0 from the ‘interface’ line, save, restart samba and check the logs.
{
"workgroup": "WORKGROUP",
"name": "hassioNUC",
"guest": false,
"map": {
"config": true,
"addons": true,
"ssl": false,
"share": true,
"backup": true
},
"username": "username",
"password": "password",
"interface": ""
}
You should see something like this:
Copyright Andrew Tridgell and the Samba Team 1992-2017
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
added interface wlp2s0 ip=10.0.1.200 bcast=10.0.1.255 netmask=255.255.255.0
added interface enp3s0 ip=10.0.1.226 bcast=10.0.1.255 netmask=255.255.255.0
added interface docker0 ip=172.17.0.1 bcast=172.17.255.255 netmask=255.255.0.0
added interface hassio ip=172.30.32.1 bcast=172.30.33.255 netmask=255.255.254.0
So from above, my Ethernet adapter is enp3s0 and the wlan wlp2s0. Pop one of those in your interface line thus "interface": "enp3s0". Many thank to @albertlt for that fix!
P.S I can confirm that the following works with the Aeon Labs Z-Stick too!
zwave:
usb_path: /dev/ttyACM0
I’m pleased to say that even on this older hardware, the reboot times (<30s) as well as logbook and history access are significantly faster than the Pi3 I came from. Awesome! Now just for bluetooth support please. 
