Help! Home Assistant on NUC

V

Vades

Senior Member
Joined
Apr 30, 2020
Messages
624
Reaction score
513
Disclaimer: Limited IT knowledge and just getting into all things smart home.

With the non availability of Raspberry Pi's I decided to go the NUC route instead. I bought a used NUC which I received today, after which I followed the instructions from the HA site: https://www.home-assistant.io/installation/generic-x86-64

The issue is that the NUC is not seeing a bootable device, even in the BIOS.

Specs:
Intel NUC7i3DNHE
BIOS version DNKBLi30.86A.0075.2021.1014.1128

I noticed in one of the Youtube tutorial vids that the content creator had the option in the BIOS to select between Windows and Linux. I do not see that option.

Any advice please?
 
You're probably better off installing HA Supervised on a Debian machine. In other words, install Debian on the NUC and then install HA Supervised in a docker on that.

I'll see if I can find you a how to guide
 
Actually home assistant supervised is stupid. If you install anything else it breaks the supported mode.

I ended up installing it into a VM of its own after installing proxmox onto my nuc.
 
I used to use it on a VM in Windows and thaybworked qell. Used Oracle Virtuabox (I think that's what it's called)

Follow this guide

 
Tinuva said:
Actually home assistant supervised is stupid. If you install anything else it breaks the supported mode.

I ended up installing it into a VM of its own after installing proxmox onto my nuc.
Click to expand...
What do you mean "breaks the supported mode"?
 
Speedster said:
What do you mean "breaks the supported mode"?
Click to expand...
For example install another docker container with let's say traefik.

Then when you go to the supervisor status there will be a red warning you run an unsupportive system. Sometimes that will even prevent you from getting updates.

Currently mine doesn't t show it as I have removed the custom dockers


1bd633e91d55ecd3408abc5726700818.jpg
 
Tinuva said:
For example install another docker container with let's say traefik.

Then when you go to the supervisor status there will be a red warning you run an unsupportive system. Sometimes that will even prevent you from getting updates.

Currently mine doesn't t show it as I have removed the custom dockers


1bd633e91d55ecd3408abc5726700818.jpg
Click to expand...
Mine says I'm running an unsupported installation. Why is that notification an issue if everything still works?
 
Speedster said:
Could you give an example of an update that's been blocked?
Click to expand...
Yes, it was a core and supervisor update.

I had to jump through hoops and read multiple github issues to figure out how to fix it.

Basically, it's easier to keep it in supported mode before something like that happen again.
 
Tinuva said:
Yes, it was a core and supervisor update.

I had to jump through hoops and read multiple github issues to figure out how to fix it.

Basically, it's easier to keep it in supported mode before something like that happen again.
Click to expand...
Bit that requires a dedicated machine just for this. In running Plex server and adguard home from the same machine and am happy with the unsupported HA as everything still works. I think the message is just a disclaimer in case something breaks, but this shouldn't be an issue in reality.
 
Speedster said:
Bit that requires a dedicated machine just for this. In running Plex server and adguard home from the same machine and am happy with the unsupported HA as everything still works. I think the message is just a disclaimer in case something breaks, but this shouldn't be an issue in reality.
Click to expand...
Well yeah if you OK when those issues happen sure, but I wouldn't recommend it to a new user. Which this thread is. Better to do it safer. Besides, you could run plex and adguard as addons which is then back to supported.
 
Thanks for the responses - I appreciate all of them but am now totally unsure of which route to take. :)

@Speedster : HA Supervised in a docker on Debian.

@Tinuva : VM in Proxmox.

@Mzezman : Oracle Virtuabox on a VM in Windows.

A lot of these applications/terms are completely new to me... I was really hoping that simply flashing the generic x86 image onto my SSD would work.

Of course, I am prepared to try something else, but just cannot be too complicated for a layman like me.
 
Vades said:
Thanks for the responses - I appreciate all of them but am now totally unsure of which route to take. :)

@Speedster : HA Supervised in a docker on Debian.

@Tinuva : VM in Proxmox.

@Mzezman : Oracle Virtuabox on a VM in Windows.

A lot of these applications/terms are completely new to me... I was really hoping that simply flashing the generic x86 image onto my SSD would work.

Of course, I am prepared to try something else, but just cannot be too complicated for a layman like me.
Click to expand...
Download the proxmox iso and flash it to a USB stick. Use the installer to format the ssd and install proxmox.


Connect to the proxmox webui and ignore the license pioup after logging in. Create a new VM on to which you use the HA image.

You can review this blog post https://www.danatec.org/2021/06/11/install-home-assistant-on-proxmox-ve/

Although I think this is better to follow https://community.home-assistant.io/t/installing-home-assistant-os-using-proxmox-7/201835
 
Vades said:
Disclaimer: Limited IT knowledge and just getting into all things smart home.

With the non availability of Raspberry Pi's I decided to go the NUC route instead. I bought a used NUC which I received today, after which I followed the instructions from the HA site: https://www.home-assistant.io/installation/generic-x86-64

The issue is that the NUC is not seeing a bootable device, even in the BIOS.

Specs:
Intel NUC7i3DNHE
BIOS version DNKBLi30.86A.0075.2021.1014.1128

I noticed in one of the Youtube tutorial vids that the content creator had the option in the BIOS to select between Windows and Linux. I do not see that option.

Any advice please?
Click to expand...
I recently installed something onto a NUC for a project, make sure the UEFI setting is selected and secure boot enabled and then saved on exit, mine didn't the first couple of times. Once that was sorted my OS booted. You won't see a Windows or Linux option in the BIOS until an OS has been installed, UEFI keeps this in a list of OS's that you have previously installed.

I have also recently installed the generic x86-64 HA onto an old Dell server, used Balena Etcher to flash the image onto an HDD, booted and installed no problems. The only issue I had was Balena didn't like the verify process so I skipped that.
 
I am with @Tinuva. Use to run as standalone pc(devian with supervised) on an old Celeron based lenovo tinypc. It was slow and horrible to run esphome updates. Moved to my existing proxmox server and use the script on the page, https://community.home-assistant.io/t/installing-home-assistant-os-using-proxmox-7/201835 to install home assistant. And then add what ever else you need on seperate vm's.

I have seperated my vm's per task, for instance one for downloads(media and other), one for grafana, another for wireguard and so on. Reason for the split of task per vm is that if one breaks I don't have to reload everything if all task run on one dedicated server.

My "server" is an old i3 gen3, 16gb ram, 1tb ssd. Running 6 vm's(home assistant os, 5 other linux servers with their own tasks) and one lxc. Best part of doing it this way. My vm's and lxc get's full back of the vm disk every night after midnight and gives me options to restore. The lxc is pure plex server with gpu(GTX 1050 ti) passthrough and. works like a dream. The ssd makes a huge difference.
 
w1tw0lf said:
I am with @Tinuva. Use to run as standalone pc(devian with supervised) on an old Celeron based lenovo tinypc. It was slow and horrible to run esphome updates. Moved to my existing proxmox server and use the script on the page, https://community.home-assistant.io/t/installing-home-assistant-os-using-proxmox-7/201835 to install home assistant. And then add what ever else you need on seperate vm's.

I have seperated my vm's per task, for instance one for downloads(media and other), one for grafana, another for wireguard and so on. Reason for the split of task per vm is that if one breaks I don't have to reload everything if all task run on one dedicated server.

My "server" is an old i3 gen3, 16gb ram, 1tb ssd. Running 6 vm's(home assistant os, 5 other linux servers with their own tasks) and one lxc. Best part of doing it this way. My vm's and lxc get's full back of the vm disk every night after midnight and gives me options to restore. The lxc is pure plex server with gpu(GTX 1050 ti) passthrough and. works like a dream. The ssd makes a huge difference.
Click to expand...
Not familiar with proxmox, but that sounds quite a bit more arduous than running a single machine. Do you have to login to each vm seperately to run OS updates?
 
Speedster said:
Not familiar with proxmox, but that sounds quite a bit more arduous than running a single machine. Do you have to login to each vm seperately to run OS updates?
Click to expand...
Only if your OS updates are not set to automatic.

You won't really know how to judge it until you have tried it.
 
Tinuva said:
Only if your OS updates are not set to automatic.

You won't really know how to judge it until you have tried it.
Click to expand...
Fair enough. I'll wait for my current setup to break and then look at the options. If it ain't broke, don't fix it
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X