I’ve spent a few hours trying to get the ConBee II working to no avail - At this point, I don’t think the issue is TrueNAS-related but something either with the ConBee II itself or a bug in KVM.
Here’s some reference to this issue reported on both Ubuntu and Debian host here and here
I also installed virt-manager with QEMU/KVM on my desktop (running Arch Linux), created a VM with HAOS, and tried adding the ConBee II - I’m getting the same error as on Scale.
Also of note - I dug up my old NORTEK HUSBZB-1 to test as well. I’m happy to say it shows up / works in my HAOS VM as expected (no module blacklist required)
EDIT: I just pre-ordered (3rd batch) a sky connect to test as well.
EDIT 2: I tried HAOS in VirtualBox on my desktop and the ConBee II is working there. So this seems to be something with KVM. But only with certain devices?!
I don’t think it’s a general problem. I had ha vm on a proxmox server. There it works.
Have a skyconnect and give it a try, but the skyconnect work’s in the past not so fine with zigbee2mqtt
I’m not sure how useable this will be on TrueNAS but it does work. I don’t use ZigBee myself but I can write a little script someone can use if they want to try it.
your script is really, really cool. i’m really new to TNS (and kinda new to HA now that i think about it)…
anyway, i i kinda stumbled on a way to do it without having to use a script. disclaimer: i don’t really know how i would’ve even gotten a script to run in TrueNAS Scale…i barely understand SSH to begin with
select: Type: PCI Passthrough Device
From the PCI Passthrough Device, pick the one you noted earlier (will probably be something different for you, but here’s what it looked like for me)
This next part is really important:
Power Off the VM (don’t just Restart it via HA, actually shut it down from TrueNAS Scale’s VM management portal).
Then Start it.
profit
edit:
i pulled a graphics card out of the machine that i wasn’t going to be using on there anymore and the ConBee passthrough broke. fortunately, i documented what i had to do to get it working
unfortunately, when i was running the ls /dev/serial* command through TNS’s Shell, it wasn’t outputting anything anymore for some reason.
super annoying.
so, if for some reason you’re seeing something like that (e.g., nothing?), then do this:
ls /dev/serial/by-id
ls /dev/serial/by-path
ta-da! now I (& maybe one of you?) will know what to passthrough again!
Thank you for sharing! This is way better (correctness and convenience) than using a script. The only thing I would change is to recommend using the Stop button instead of Power Off.
My understanding is that Stop should issue a proper shutdown of the VM, while Power Off is like ripping the plug from wall.
Hi everyone, sorry if my message comes out of this thread but it very close.
I trying configure Wi-Fi onboard wi-fi inside HAOS. Inside TrueNas i make PCI Passthru with Wi-Fi mobo but HAOS doesn’t found it. What possible to do with it?
Hi @NAGL95 - I’m not sure if what your trying to do will be supported, and it will undoubtedly be an edge case if it is. The usual response for any server setup is, don’t use WiFi. I don’t want to discourage you, but finding someone successfully using WiFi as the primary connection to Home Assistant may be challenging.
I noticed you made s separate post several days ago, but still no response. I would also try asking on Discord if you’re a member there. First, you should confirm if what you want to do is possible in HAOS.
Thank you so much for this writeup, this really helped me solve an issue with my VM on Truenas.
In case anyone else is having similar issues to me I will describe the issues I was having. I created my Home Assistant VM on Truenas and moved my Home Assistant instance without understanding all of the settings. My VM seemed to be working fine but I was having some trouble with some add ons and the HomeKit integration. My AirSonos add on would stop working after someone tried to play music on a speaker. I have several HomeKit bridges configured and when I reconfigured one of them I was no longer able to add it to the Home app. This was really driving me crazy and all signs seemed to be pointing to some type of network issue. After reading this post I created a test installation and by turning on “Trust Guest Filters” I was able to use AirSonos and connect to HomeKit bridges. I did not create a bridge NIC but did use the VirtIO adapter type.
After recreating my VM using this posts guidelines everything seems to be working so far. Hopefully someone else having issues similar to me can benefit from this great post.
Thanks
I’m running into an issue with DNS. My router is configured to use pihole, which is running as a docker app on TrueNAS. I’m guessing the issue is that HOAS can’t roundtrip to PiHole out of the same network interface.
I’ve tried updating the DNS nameserver using this guide, but none of the options stuck. “resolution info” still shows DNS errors and “network info” still shows the pihole is being used as the nameserver.
I followed the multiple backup restore process from @fedot on this page and that appears to have worked for me.
It appears my add-ons are installed (including the ones I didn’t install manually, or that were from third-party repositories, like Shortumation and Google Drive Backup), configured, and successfully start up.
Please see the next post for another solution
