No user inputs I even turned on power on after power loss in bios so as soon as power is attached it turns on, I even updated the is to 2.26 after initially installing 2.2
Loads without interaction just like the pi but in about 40seconds rather than 3minutes plus
Appears flashing the image directly to the mssd drive of the NUC works.
Used a ssd to mssd USB convertor with etcher to flash the latest NUC image.
Reinstalled the mssd back into the NUC. Switched it on and after about 5mins it appeared on my network. Logged into IP:8123 and the magic please wait 20mins hass.io screen was present.
Will update how it goes once itās finished. Still donāt have HDMI out put but thatās ok. For $40 Iām not complaining
Mine takes <1m to restart with no code to speak of on a very old NUC platform (circa 2013) so might be standard. Config checking is must faster though. Iām still running HassOS on Odroid C2 at the moment but will be switching back to NUC at the end of the month.
Iām going to move my actual RPI3 HASSIO to Intel NUC i3
I was thinking to install ESXi 6.5 (it seems that 6.7 does not work), but I know (maybe Iām wrong) that ESXi does not recognize the WLan card, and I was thinking to use it.
Then, installing Ubuntu Server 18.10 on a VM and install HASSIO using docker.
The other option is to install directly on NUC Ubuntu Server, same as above hoping that WLan will work.
Of course, I know that having a real VM Manager like ESXi will let me āplayā with VMs making snapshots, clones, testing and so on.
iām trying to migrate to a NUC and have followed the guide and iām having a little trouble:
I have an i3 Nuc
with a 1TB M2 SSD in it.
when i load a USB stick in with the hass.io image I get a āHassOS Boot menuā
which gives me 4 options:
1: Autoboot
2: Boot System_0
3: Boot System_1
4: Shell
When i select one of these options, it flashes up something very fast but itās far to quick to read. I would have thought it should be booting to the HassIO screen?
You used to need to either remove the SSD and use Etcher to flash the image to that directly or boot to a Linux live image and then use Linux commands to image the SSD with the HassOS image.
In my video, Iām using Linux commands to image the whole SSD with the HassOS *.gz file (that is contained on another USB drive). Others have since taken the SSD out and imaged that directly which might be easier?
But if i decide not to use the SSD I should just be able to follow your original guide yeah?
which is essentally the same process as working on a PI yeah? down load image burn it to an SD Card, with etcher, put in turn and on come back in an hour?
itās starting to boot but apprears to pause around 3seconds in when it looks to the USB stuff