Option 1: Home Assistant OS as an appliance guest
Home Assistant OS runs in its own virtual machine on a Proxmox VE node you already own. Techstack creates the VM, and StackKits is never installed inside Home Assistant OS. A mixed homelab can have an Ubuntu guest for the core services and a separate Home Assistant OS guest.
The wizard offers this guest when you select Smart Home and choose Home
Assistant OS, and the instance is new. Updating the pinned version in a
release never changes a guest that already exists.
Read Run kombify on Proxmox VE first. It covers the
connection, authorization and what is not verified yet.
Option 2: Home Assistant as a container
The StackKits catalog has an optionalhome-assistant module. It runs Home
Assistant Container, without Supervisor or apps, next to the other services of
your kit. The catalog pins Home Assistant 2026.9.4 and the auth_oidc
extension 1.2.1 for sign-in. Apply installs no extension from the network.
This path runs on a host you operate, with or without Techstack. A USB radio
for Zigbee or Z-Wave can be passed through to the workload.
What works and what is pending
- Implemented: sign-in through Pocket ID, restricted to the owner, admin and household groups. Local Home Assistant login stays available. The owner account is bound to its Pocket ID identity, and no account is created silently.
- Implemented: adoption of an existing supported Home Assistant container, without recreating it or changing its accounts. An existing instance is registered as observed first.
- Not yet completed: a real Home Assistant start-up with browser and native app sign-in, trust of a private certificate authority, and restore qualification.
- Not yet completed: a full live run of the appliance guest on a current release.