Here is what i get when i try to download HACS
So the supervisor comes installed with HAOS; there is nothing to do there. As for HACS, I see in the first screenshot (I assume thatās the VM display) you can ping google
And I assume this second screenshot is using the ssh add-on. Can you ping google while using this addon? Iām not sure how helpful I can be in resolving DNS issues, but we can certainly give it a try.
Another way to get HACS installed is by using the Samba add-on. Which you could use to access the Home Assistant config directory from another computer. Installing HACS is simply a matter of unzipping the folder and coping to /config/custom_components/hacs (You may need to create the custom_components directory if it does not already exist)
The latest release of HACS can be downloaded from GitHub - Look for hacs.zip
i donāt know if there is some connection with networking but i donāt see the problem because i can ping google.com.
Thanks Troy. VM has 2 vCPUs, 1 core, 2 threads, 6GB RAM. ZPOOL and ZVOL are both under 20%. I am running the bridge via a lagg interface. I might try with a single interface to rule out network issues.
Just wanted to say thanks for this guide!
New to TrueNAS and this was super useful. I have a Conbee II and wasnāt able to pass through my PCI ports to the VM as my CPU / Mobo doesnāt allow virtualisation so I ended up pulling Mosquito and Zigbee2MQTT into their own container, and creating a network bridge (so the VM and containers could talk).
Great learning experience and will considering pulling HASS out of a VM into a container in the future too 
1 Like
Hi allā¦ new hereā¦ Imalso very new to Y
VMs and himeassistant as wellā¦ Iāve gotten to the long where I see the homeassistant command-line. But when I try and log in from the web address nothing happenes. I tried the ping command and when I hit enter ping is written twice and says thereās no such command. I typing ping only once
From this screenshot, you need to login first, then you should be able to run ping google.com
So Iāve been at this whole thing for about 6 hours troy and Iām throwing in the towel without your help 
Iāve read through this entire page and cannot find my solution. I get the UEFI Interactive Shell screen for my display. Iāve tried to convert the image to the /dev/zvol/Main\ Data/localhomeos and it says incorrect file directory it doesnāt exist, as well as just /dev/Main\ Data/localhomeos and the only one that actually works in a sense of not bringing back an directory doesnāt exists is when the path is /mnt/Main\ Data/localhomeos the other variable in my situation is the fact my overally pools name is Main Data and i messed up when I created my TrueNas installation. But Iāve learned through the shell that the \ inbetween solves that issue when doing cd /mnt/Main\ Data/localhomeos so I donāt think thats the issue
Hi @officialxndr, sorry to hear youāre having trouble.
Are you sure you created a ZVOL for HAOS - I wonder if you created a dataset by mistake. Please share screenshots of the Zvol Details and Zvol Space Management for localhomeos.
I think you made a dataset. It is not possible to cd into a ZVOL
Off topic here, but it is possible to rename your zpool without destroying it.
You can also use quotes " like this: cd "/mnt/Main Data/localhomeos"
UPDATE
I started completely from scratch with a new zVol and VM and it seems to have worked. The only variable that was different was using " " and a + inbetween my dataset that has a space in it lmao so leaving this here for future seekers of knowledge
Thank you Troy! for all youāre doing and the shout with the tip about the " " saved my life haha
2 Likes
Hello! One issue I am running into is after having the VM running with Home Assistant correctly, I canāt access the url as I would be expecting to
Not sure if this is something you have seen before, but unsure as to why this would be a problem if I am able to ping the website from inside the VM, any help in the right direction would be appreciated. Thank you in advance for your time!
Only able to put one embedded image as a new user, but here is the image showing I canāt connect locally from outside the CLI
Hi @CraigSau - Iām guessing you may need a local DNS server - I use Pi-Hole for .local name resolution. But you should also be able to access Home Assistant using the IP address. From your screenshot, please try - http://192.168.50.54:8123
Thanks for the quick reply! While trying the local IP address didnāt work via my PC, both urls, the .local and the local IP worked from my macbook, not sure yet what the reason is for that, but maybe there is something odd with how my network is configured that my PC is unable to make the connection to the VM, yet my macbook is. Not sure if that would be helpful info for anyone else, but figured I would mention it regardless.
@troy Iām currently running TrueNAS-13.0-U2 with home assistant installed in a debian vm. It works ok, but I am considering moving my TrueNAS from CORE over to SCALE for the ease of the apps. I see above in a post that passthrough for USB will work in TrueNAS SCALE ver 22.12 and higher. Are there any reported issues that youāve heard of getting the Aeotec Z-Stick Gen 5+ to work? Iām considering just scrapping my entire server, starting fresh with SCALE, and installing HAOS like youāve shown here, but I have to be able to make it work since I will have hosed my current working install. 
I use the same Z-Wave stick but with Z-Wave JS version 12 I hit the following issue, and the only way I could resolve it was to disable soft reset, which is mentioned in the link as a last resort.
These days Iām so busy at work I donāt have time to troubleshoot things like I used to. There are some links in the issue that say how to configure proper pass through for a USB device to a VM but there are no instructions for KVM and I donāt have time to figure this out on my own.
It might be as simple as passing through the entire USB controller, but that was not an option for me unless I purchased an additional PCIe USB card. I imagine youāre already using PCIe pass through to get your Z-Wave stick working on CORE so maybe the same setup will work for you in SCALE.
I ended up moving Home Assistant to a dedicated device because I need it to be reliable, and I got really frustrated when my Z-Wave broke and I did not have time to figure out how to properly fix it on SCALE.
I donāt want to discourage you from giving SCALE a try, but I understand your concern for scrapping a working install. Rather than a complete reset with SCALE, you could just switch to the SCALE train on your TrueNAS upgrade page. As long as you do not upgrade your zpool, you should be able to still boot back into CORE if you find that SCALE does not work for you.
My mistake was not paying attention to this step (ā/dev/zvol/ā is the path that the image must go to, the rest needs to be replaced according to your VM folder structure):
qemu-img convert -O raw haos_ova-11.2.qcow2 **/dev/zvol/**tank/vm/haos
1 Like
I think I have some DNS issue, I disabled pi-hole thinking that may be the issue but still getting this error. Anyone have a direction they can point me in?
EDIT: restarted everything now its working with pi-hole disabled and router settings back to default(just pi hole dns redirects).