---
title: "Home Assistant OS — Installation on Proxmox via Community Scripts"
aliases: [haos-proxmox, home-assistant-proxmox, tteck-scripts, proxmoxve-scripts]
tags: [home-assistant, proxmox, haos, vm, homelab, automation]
sources:
  - "daily/2026-04-19.md"
created: 2026-04-19
updated: 2026-04-19
---

# Home Assistant OS — Installation on Proxmox via Community Scripts

The recommended way to install Home Assistant OS (HAOS) on Proxmox is via the community script from `community-scripts/ProxmoxVE`. This script creates a VM, downloads the official HAOS image, imports the disk, and configures UEFI/q35 — all automatically. It takes 3–5 minutes and requires no manual disk import or config editing.

## Key Points

- **HAOS in a VM** is the official and most feature-complete deployment method — full add-on support, supervisor, OS updates
- **Community scripts** (`community-scripts/ProxmoxVE`, formerly tteck's scripts) are the standard homelab approach: one command in Proxmox Shell
- **Default Settings is the right choice** for most home installs — 4GB RAM, 32GB disk, 2 CPU cores; Advanced only needed for custom storage or VM IDs
- Home Assistant is accessible at `http://<VM_IP>:8123` after installation
- The script automatically selects the latest HAOS release — no need to find download URLs manually

## Details

### Installation Command

Run in Proxmox Shell (not inside any container):

```bash
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/vm/haos-vm.sh)"
```

The script prompts:
- **"Install Home Assistant OS - Default Settings or Advanced Settings?"**
  - Choose **Default Settings** — creates VM with 4096 MB RAM, 32 GB disk, 2 CPU cores
  - Advanced: customize VM ID, storage location, CPU type, machine type

After completion, the script outputs the VM's IP address. Open `http://<IP>:8123` in a browser to start the onboarding wizard.

### VM Specs (Default)

| Resource | Default |
|----------|---------|
| RAM | 4096 MB |
| Disk | 32 GB |
| CPU | 2 cores |
| BIOS | OVMF (UEFI) |
| Machine | q35 |
| Network | VirtIO |

These are adequate for a home automation setup with 20-50 devices and a moderate number of automations. Increase RAM to 6–8 GB if running heavy integrations or many add-ons.

### Why VM Over LXC

Home Assistant officially supports LXC (Container) as a deployment option but with significant limitations:
- Some integrations require direct hardware access (USB, Bluetooth, Z-Wave dongle)
- The Home Assistant Supervisor (which manages add-ons and OS updates) works best with full VM isolation
- HAOS in a VM provides supervised installation — the fully supported experience

An LXC deployment of Home Assistant Core (without Supervisor) is possible but loses add-on support and automatic OS management.

### Post-Install Onboarding

1. Browser opens `http://<IP>:8123` — "Preparing Home Assistant" (takes 5–10 min on first boot)
2. Create admin account
3. Set home name, location, timezone
4. Home Assistant auto-discovers devices on the local network
5. Add integrations (Philips Hue, Google Home, Apple HomeKit, etc.)

### Set a Static IP

After installation, fix the VM's IP in the router's DHCP reservation or configure a static IP in Home Assistant → Settings → System → Network to prevent the dashboard URL from changing.

## Related Concepts

- [[wiki/concepts/proxmox-vm-management-methods]] — all approaches for creating VMs on Proxmox
- [[wiki/concepts/proxmox-mcp-server]] — Proxmox MCP for managing VMs from Claude Code
- [[wiki/homelab/_index]] — homelab infrastructure context

## Sources

- [[daily/2026-04-19.md]] — User asked about Home Assistant installation on a fresh Proxmox setup; community script approach chosen over manual disk import; Default Settings selected for home use
