@gerard33 thanks for helping
Never done that before, but is this the correct place to raise an issue?
I this case it would be better to install hassio in a VM?
1 Like
Probably. The depreciation is only [on hold], a vm is supported.
Should be done here https://github.com/home-assistant/supervised-installer but that repo is archived for now, so you canāt make an issue right now.
I have a NUC myself and run Proxmox on it. Then you can run multiple VMs from which HA is one of them. Also the snapshot function you then have is a real handy feature.
I would advise you to have a look at that first and then decide how to proceed.
Thanks for the tip. Something else Iāve to dive intoā¦ do you have by any chance a tutorial or info page you can share?
The Proxmox site will inform you on the installation of Proxmox.
To install HA you can check the topic below, but read it carefully. The HassOS version used there is still in beta -> Supervised Install on Proxmox
Cheers, Iāll try first this tutorial: https://medium.com/@dreed10/https-medium-com-installing-home-assistant-on-a-nuc-easier-approach-aac306e48641
which just stays with ubuntu running virtualbox to keep it easy, otherwise iāll try with proxmox.
I need to replicate the install I already have using this method before looking for a new alternative.
I am trying to get the script to install and have the same error. I am trying in vain to do the workaround but have failed. I used wget to copy the file and then edited the āthenā command but I canāt then get the script to run locally. Please can you point me in the right direction?
I support your advice.
Adjusting the installer script is like an entrance test. If you fail it then you probably need to study some more or choose something else.
In the recent blog post, I was quite surprised by the number of people asking what they had installed and were they affected by the deprecation. I wouldnāt think it was possible for someone to not know what they installed, but I was proven wrong.
There is a PR to add additional info to the āInfoā page to show what OS and installation type a user has. It would seem many will still not know, but at least they can be directed to go and check that page.
āIf your info page says X, Y and Z, this will/will not effect youā
6 Likes
is this working fine?
Worked great for me yesterday on OMV/Debian.
Hi
This also work under UBUTU SERVER installed on NUC
I got it working
curl -sL "https://raw.githubusercontent.com/home-assistant/supervised-installer/master/installer.sh" -o installer.sh
nano installer.sh
[remove the following]
if [ "$x" != "not supported" ] then echo "OK, bye!" exit 1 fi
save and close
cat installer.sh | bash -s -- -m raspberrypi4
Granted, Iām a noob, but installing on buster (so I can SSD boot on my pi4) has become a royal pain
Hi!!
Can you post the full script please
I try this curl -sL āhttps://raw.githubusercontent.com/home-assistant/supervised-installer/1f30d124ef7d0ee84b45d1772cb5c1e4a94c67b8/installer.shā | bash -s
This is correct???
user mine
curl -sL āhttps://raw.githubusercontent.com/DEVAXTATOR/supervised-installer/master/installer.shā | bash -s
it works and in debian too
Iāve spent the last few days trying to migrate Home Assistant over the an Intel i7 NUC. Iām new to HA and discovered soon after installing that my Rako lighting was going to be easier to control if HA was not on a Raspberry Pi. I have been following these instructions - https://www.juanmtech.com/set-up-hassio-in-docker-and-in-an-ubuntu-server/
The install was not working and I have just found this thread which seems to explain why.
What is currently the easiest way to get HASS.IO onto a NUC? Should i just wait for the installer.sh to be fixed?
Iām running now HASS.IO with Proxmox. Itās a virtualization software and it is running great and easy to setup.
Iāve followed this tutorial:
1 Like
Except itās no longer called hassio. Its name was changed to Home Assistant OS in June. All of the official documentation has been updated. Only third-party tutorials, created before the name change, still use the deprecated name (and users who havenāt kept up to date with Home Assistantās evolution since June).