Installing HAOS (Home Assistant OS) in a VM

Hey, I actually didn’t. I ended up using a Cloudflare tunnel and the cloudflared addon in HA.
I can’t find the exact guide i used but there are a few around. It was pretty easy since I was already using Cloudflare as my nameserver.

I managed to fix it, thanks to @ctag !!! The solution was to go into the Kubernetes “Advanced Settings” on the Apps tab in the Truenas GUI, and set

  • the v4 Interface to empty (or rather select “–”) instead of the network bridge br0 you probably created since you are using a VM
  • v4 gateway: leave empty, instead of e.g. putting your router IP there.

See @ctan’s post (and link) in this topic: Apps can’t reach VM on same bridge

It’s been mentioned that the nginx proxy manager can’t access IP’s on your local network because official Truenas app just get redirected to the network gateway (see Truenas apps can’t access physical devices on local network. I have tried implementing a rule on my router to then pass on that traffic to the right IP but couldn’t get that working.

1 Like

so what you suggested is to install Deconz as a truenas app and not install it in HomeAssistant (I run it as VM) ?

I’ve been jumping between foruns, and looks the community is identical between here and the home assistant one :slight_smile:

My doubt is if anyone running HA in TrueNas Core with a ZigBee USB dongle connected?

Struggling to make it work, and I was trying to avoid to keep using a Rpi just for zigbee :frowning:

I just got HA installed as a VM on EE. Worked like a charm.

My question now is what controller type do I pick for my zwave usb stick?

Glad you were finally able to get something working… I use qemu-xhci

1 Like

Thanks Tony, I am struggling to get a couple HA Addons to load they are just not starting.

Ive tried Node-Red and Terminal

Really great job. I just installed without a hitch.

But why did you use a thick volume instead of sparse provisioning?

It uses 2.38GiB after it boots,

I solved the NPM forwarding problem by enabling websockets.

I also set the URL in the System>Networking screen to the external URL so it would confirm external access is enabled.

There is an IP ban file that gets deleted on reboot so check that.

I got the ssh working by not enabling sftp. No password. Just my ed25519 public key. works great.

Hi All,

Glad i found this topic, maybe someone can help me with a little problem i have. And thank you in advance !
I have HA OS installed in a VM on TrueNAS Core for 2 years now and eveything is running ok.
Lately i installed Frigate and saw the disk used jump.
Went into TrueNAS and increased the size of the VM to 192 Gb from 128 Gb.
But for the life of me i have no idea what is needed to expand HA onto the full new size. Or maybe it did expand and i just simply dont understand it.
Here are some pics from various places showing the disk utilization:

HA / Storage shows 61% used - 62.2 GB free
This is from HA Settings/System/Storage - according to those numbers it doesnt seem it expanded.

This is from Glances addon - it shows 115G but a total of 188G. No idea what to make from this.

and this is from Frigate which shows the 188 Total.

I did delete all the HA snapshots in Truenas and restarted the VM, still the same.
So if i have 188 Gb in total, why is HA system reporting 61% used and 65 GB free ?!

many thanks !!

PS i’ll come with the pics as soon as i get the rating to post them :slight_smile:

I could not find in the forum rules what it takes to be able to post pics, but i guess more then one post is needed :upside_down_face:

Hmmm scratch my question, running df -h from the Terminal addon shows Size: 188.3G and used 115.6G. So it did expand to the entire volume.

Still , du -sh /* shows only 30G or so used.

Is there a way to find out what is eating up the rest of 80G please ?
I know the terminal addon will shows only whats in the container, but is there a way to ssh into the VM on truenas core ?

Cheers