Could you check what the IP is from your router / your DHCP server? I suppose the IP of the VM would be different from the IP of your QNAP box.
Alternatively,
go to Virtualization Station 3, find your HassOS VM, open a console from there,
login using the default password (link)
EDIT: Not needed these days (Aug 2021). Opening a console will get you directly to the ha > prompt… no need for any default password… maybe since HAOS 6.0
and do login to go into the prompt for the host OS
and then do nmcli
What’s the IP you see?
Edit: to be clear, the IP you see on Virtual Switch 3 is not the IP of your HassOS VM.
Unless something has changed recently, I’m pretty sure the ova from the official github would work just fine.
… and someone has confirmed ova would work:
(Looks like the install guide above has got some nice updates / rewrites since July 2020. Check the HAOS section under the “alternative” route)
… and here’s the guy who said he got things up and running w/in minutes (or was it seconds?):
= = = =
Yes there’s also docker container install option via QNAP Container Station. But assuming your QNAP could do VM, I’d recommend we just do Home Assistant OS via QNAP Virtualization Station 3 using the ova image.
Just wanted to say thanks for this. Been wanting to get HAOS off my PC and onto my NAS, surprised it was this easy. I wonder why this option isn’t described in the HA install documentation.
In case anybody comes here confused, follow the directions exactly but at the end before you start the VM, go into the VM settings > boot options and change ‘firmware type’ to UEFI. Even if you check EFI in VirtualBox before exporting, it will not work until you set it for the VM. I saw several people say they were hung on ‘booting from hard disk’ and this is why that happens.
I recently moved from my Pi to my Qnap nas, but was surprised to see that it says I’m running an "Unsupported version"and that I need an OS agent. I don’t see how I can install an OS agent when I’m directly running Hass.io on the VM
Go to Configuration → Settings → Info… could you share what you have under System Health?
For me, I got this when I was running portainer as one of my add-on, and I used Portainer to manage a docker under HAOS. That practice however is not OK these days, so I’m told. Quoting this:
so I had to move that docker out of HAOS to somewhere else, and then clean its footprint from HAOS using Portainer, and then remove the portainer add-on.
I have also HA in Qnap Virtualization station. Im running Deconz (Conbee2). How do you access those files from Qnap that are inside running VM? I need to donwload/edit DDF files for Deconz…
I cant find the configuration.yaml file on my qnap or the folder where its located. I can edit in the file in HA but cant find the physical location is it imbedded in the image file?
Hello all
and thanks for all the useful information here. @keyelle I want to report that it is possible to avoid the initial conversion step in Virtual Box on another machine :
Download haos ova file place it on either your NAS or your local machine.
In QNAP Virtualization Station, click the Import button, “Import VM”. Select where you downloaded to NAS or PC, and select the file.
Options I selected later under ‘Advanced Settings’ were to use the VirtIo network and HDD drivers - may have worked with other options.
Embarrassingly simple.
Attaching USB drives devices to the VM also seems simple.
I’m running QTS 5.0.1.2194 on a x86 based NAS.
I had been running with using docker instances with QTS Container Station, but wanted a simpler setup (albeit a little less efficient) using a VM.and the Addon store.
Hi,
Please @mbartosik0 which version of Virtualization Station have you been using? Is it 4 beta? I’m just curious because I do not found the option to import .ova in the 3.6. Thanks