TALK / HOME ASSISTANT
If Home Assistant is the only job, install Home Assistant OS on the mini PC. Add Proxmox only when the same box must host other services.
Short answer
If Home Assistant is the only thing this mini PC will do, install Home Assistant OS (HAOS) directly. If the same box must also run other services, such as a media server, DNS or a test VM, then Proxmox plus a HAOS virtual machine is a documented and reasonable route, but it adds a layer you have to maintain.
What the official documentation says
Home Assistant calls Home Assistant Operating System the recommended installation type for most people. Its generic x86-64 guide assumes a dedicated PC that runs only HAOS, booting in UEFI mode with Secure Boot disabled. The boot drive must use 512-byte logical sectors; some NVMe SSDs use native 4K sectors only and cannot boot HAOS. A USB-attached boot drive is described as not recommended.
The project also publishes a KVM/Proxmox image (.qcow2) for running HAOS in a virtual machine, so the VM route is a supported method, not a workaround. The Container install is a third option, but it does not include apps (add-ons), and integrations that depend on them, such as Thread and Z-Wave, have no out-of-the-box support there.
What the VM layer adds
Our reading, not a measurement: a hypervisor means one more system to update and back up, and a host reboot takes Home Assistant down with it. Proxmox can start guests automatically at boot (the onboot flag), so that part is configurable.
The Zigbee or Z-Wave stick must be passed through to the VM. Proxmox documents two ways: by vendor and product ID, or by physical port. The port method means the stick keeps working only while it stays in that port. Whichever route you take, Home Assistant’s Zigbee documentation advises a USB extension cable, a USB 2.0 port or powered USB 2.0 hub, and keeping the adapter away from USB 3.0 devices. Mini PCs often crowd USB 3 ports together, so plan the cable.
If you choose the VM route
Create the VM from the published image, give it memory and CPU that match your expected workload (Home Assistant says you can increase them later), pass the USB adapter through, enable start at boot, and then test a cold boot before you rely on it. Run one backup and restore test too, so you know the recovery path works before you need it.
Decision rule
Install HAOS directly when the machine is dedicated, you want the fewest moving parts, and you are happy to use one internal SSD for it. Use a Proxmox VM when other workloads share the hardware, or you want snapshots of the whole guest before risky changes. Check that the CPU lists virtualization support and that it is enabled in the BIOS. If you are unsure, start with the simple route and keep Home Assistant’s own backups current.
This answer is about setup choice. It does not claim any performance difference between the two routes; we have not tested one.
Other perspectives
Adding to “the Decision rule”
Budget for the small extras that make either route work: a short USB extension cable, a separate Zigbee or Z-Wave adapter, and an internal SSD rather than a USB boot drive. If you do not need the mini PC for anything else, Home Assistant also sells its own ready-to-run box, Home Assistant Green, which is a different purchase to weigh. Barebone units add the cost of RAM, SSD and an operating system choice; see our barebone vs pre-installed comparison. Whichever route you choose, check the manufacturer’s return terms, since we did not verify any brand’s policy.
Adding to “What the official documentation says”
Before ordering, read the BIOS options on the manufacturer’s page or manual: UEFI boot and a Secure Boot switch are required for the direct route. For the VM route, look for a CPU with virtualization support on its Intel ARK or AMD page, and for enough RAM to leave room after the VM’s share. Count USB ports and check whether any are USB 2.0. Do not infer these from a spec headline. For hardware that fits this job, see our Home Assistant hardware guide and, for the container route, our Docker tutorial (both are being revised).
Adding to “What the VM layer adds”
Whichever route you choose, keep backups outside the mini PC, and shut down cleanly instead of pulling power. On Proxmox, back up the VM and also use Home Assistant’s own backups, because they protect different failures. A battery backup helps both setups; see whether a 24/7 mini PC needs a UPS. Also compare the number of USB ports against what you plan to plug in: adapter, backup drive and any other device compete for space. For a Proxmox-based layout see our Proxmox all-in-one guide (being revised).
Quick questions
- Can I use Docker instead of HAOS?
- Yes. Home Assistant lists Container as an install type, but apps (add-ons) are not available there, and Thread and Z-Wave are controlled by apps, so they have no out-of-the-box support.
- Does USB passthrough work with every Zigbee stick?
- Proxmox documents the passthrough method. We did not test specific adapters, so check your adapter's notes and the Home Assistant ZHA page before buying.
Hardware mentioned
Plain links to manufacturer or project pages. They are not affiliate links, and we show no prices here because prices change; see our price and data policy.
- Beelink EQ14 (Intel N150) (manufacturer or project page, read 2026-10-24)
- GMKtec NucBox G3 Plus (Intel N150) (manufacturer or project page, read 2026-10-24)
- Home Assistant Green (project-made alternative) (manufacturer or project page, read 2026-10-24)
What we checked
We separate documented facts from our own advice and from what we could not confirm. We did not run tests for this answer. See how we test and our editorial policy.
Facts from sources
- HAOS is the recommended installation type for most users (HA installation page).
- x86-64 guide: dedicated PC, UEFI, Secure Boot off, 512-byte sectors; USB boot not recommended (HA x86-64 page).
- A KVM/Proxmox .qcow2 image is offered (HA alternative page).
- Container installs lack apps; Thread/Z-Wave have no out-of-box support there (HA installation page).
- ZHA advice: USB extension cable, USB 2.0 port/hub, away from USB 3.0 (HA ZHA page).
- Proxmox documents USB passthrough by ID or by port (PVE wiki); guests with the onboot flag start at boot (PVE cluster chapter).
Our advice
- Choose direct HAOS for a dedicated box; VM only if the box is shared.
- Budget a USB extension cable and internal SSD.
Not confirmed
- No performance comparison between the two routes was made or is claimed.
- Specific Zigbee adapters were not tested with passthrough.
Sources (read 2026-10-24)
- Home Assistant — Installation — read 2026-10-24
- Home Assistant — Generic x86-64 — read 2026-10-24
- Home Assistant — Alternative (virtual machine) installation — read 2026-10-24
- Home Assistant — Zigbee Home Automation (ZHA) — read 2026-10-24
- Proxmox VE wiki — USB Devices in Virtual Machines — read 2026-10-24
- Proxmox VE documentation — Cluster Manager — read 2026-10-24