Skip to content

Comparison: Smart Home Server Architectures

This overview compares the three most common operating concepts for a private smart home server (e.g., based on an AMD64 Mini PC or ARM64 Raspberry Pi).

1. Quick Overview (Comparison Table)

Criterion ei23 Raw (Debian Bare Metal) HAOS Raw (Home Assistant OS) Proxmox VE (HAOS VM + ei23 LXC)
Resource Overhead Minimal (~0%) Minimal (~0%) Low to Medium (hardware-dependent)
System Isolation Manual: Without a configured watchdog, errors in a service can freeze the host. Good: Isolated Docker add-ons, but only within the HA universe. Excellent: Full encapsulation of VMs and LXCs.
Backups & Rollbacks Manual / script-based. No system snapshots. HA backups (partial backups via the UI). Excellent: Instant snapshots and automated full backups.
Hardware Access (USB) Direct & straightforward without configuration. Direct & straightforward. Requires passthrough (USB passthrough) in the hypervisor.
HA Add-on Store No (services must be maintained manually via Docker Compose). Yes (fully integrated supervisor store). Yes (by running HAOS in its own VM).
Learning Curve / Complexity Medium (basic Linux & Docker knowledge required). Very low (plug-and-play, console is hardly needed). High (understanding of virtualization, bridges, and storage required).
Hardware Utilization Very good (perfect for weaker hardware). Moderate (powerful hardware often lies idle, as third-party systems are not allowed). Excellent (powerful hardware can be optimally allocated).

2. Detailed Pro & Con Analysis

Concept 1: ei23 Raw (Debian Bare Metal)

Debian is installed directly on the hardware. The ei23 script sets up Docker, Portainer, and the smart home services as a container environment.

Pro

  • Maximum Efficiency: No virtualization layer. Almost 100% of CPU performance and RAM are available to applications (ideal for systems with $\le$ 8 GB RAM).
  • Easy Hardware Access: USB sticks (Zigbee, Z-Wave), Bluetooth modules, or physical watchdogs (/dev/watchdog) work directly out-of-the-box without routing.
  • Full Linux Freedom: Since standard Debian is running, any custom background scripts, crontabs, or system tools can be installed directly on the host.
  • Useful Docker Compose: Perfect for developers and tinkerers who love YAML files and want to test new Docker services quickly.

Con

  • Lack of Isolation: If a service has a memory leak, it can drain the RAM of the entire server. The system enters a "swapping coma" and becomes completely unresponsive.
  • No HA Supervisor: Home Assistant runs as a core container. There is no integrated "Add-on Store" in the HA interface; all additional services must be maintained manually in the docker-compose.yml.

Concept 2: HAOS Raw (Home Assistant OS Directly on Hardware)

The official, minimal operating system from Home Assistant is flashed directly onto the PC's hard drive or the Pi's SD card.

Pro

  • The "Carefree Black Box": Extremely simple installation and absolutely low maintenance. Updates to the OS, HA Core, and add-ons are done with a single click in the UI.
  • Integrated Supervisor: Full access to the Add-on Store (install Node-RED, Mosquitto, InfluxDB, etc. with one click and use them pre-configured).
  • Built-in Watchdogs: Excellent automated error handling. If an add-on or Core crashes, the supervisor restarts the container immediately.
  • High Security: The underlying Linux is minimal and read-only, which minimizes attack surfaces.

Con

  • Complete Lock-in: It is a closed system. It is extremely difficult or impossible to run applications that do not exist as an HA add-on (e.g., a full Nextcloud instance, custom web servers, or custom Docker Compose stacks).
  • Wasted Resources on Powerful Hardware: If HAOS runs on a Mini PC with an i5 processor and 16 GB RAM, the hardware sits idle 90% of the time but cannot be used for other server services.
  • Inflexible for Tinkerers: No standard SSH access to the host system, no package manager of its own (apt), no possibility for deep system customizations.

Concept 3: Proxmox VE (HAOS VM + ei23 LXC)

The bare-metal hypervisor Proxmox VE runs on the hardware. Home Assistant OS is operated in an isolated VM (including Supervisor), while ei23 and other services run in a lightweight LX container (with Docker nesting).

Pro

  • Perfect Crash Safety: If the RAM in the ei23 LXC runs full (e.g., due to InfluxDB), only this LXC crashes. Proxmox itself and your HAOS VM continue running completely unaffected and without downtime.
  • Snapshots & Painless Upgrades: A snapshot is created before any risky update (whether a Debian upgrade in the LXC or an HA Core update in the VM). In case of errors, a rollback takes 5 seconds.
  • The Best of Both Worlds: You get the convenience of HAOS add-ons in the VM and the full flexibility of Docker Compose in the ei23 LXC.
  • Superior Disaster Recovery: Full backups of entire VMs/LXCs can be backed up automatically during operation to a NAS or external drive. In the event of a hardware failure, the system can be restored on any other Proxmox PC within minutes.

Con

  • Virtualization Overhead: Proxmox and the VMs permanently require CPU cycles and RAM. Often too heavy for systems with $\le$ 8 GB RAM. Recommended from 16 GB RAM upwards.
  • Additional Layer of Complexity: The user must maintain another operating system (Proxmox VE) and understand concepts such as virtual bridges, LXCs, VMs, and storage types.
  • Hardware Passthrough Required: USB devices must be manually passed through to the respective VM or LXC in the Proxmox interface.