Long recorder retention, many frequently changing entities and external analytics databases increase writes and database work. Move toward durable SSD storage and additional memory when history and analytics become the workload, rather than upgrading simply because the device count is larger.
For users retaining long history, adding InfluxDB/Grafana or building data-heavy dashboards.Hardwarevereisten voor Home Assistant: CPU, RAM, opslag en smart-homeworkloads
Lees meer over de hardwarevereisten van Home Assistant voor HAOS, containers, Zigbee, Thread, Z-Wave, lokale spraak, Frigate en Zima-serverkeuzes.
Home Assistant hardware requirements at a glance
Choose the installation type before the hardware. Home Assistant OS is the recommended option for most users; Home Assistant Container fits ZimaOS well but requires you to manage the host, companion containers and device access yourself.
- CPU
- Home Assistant does not publish one universal bare-metal CPU minimum. Its current HAOS virtual-machine guide uses 2 vCPUs as the minimum, while Home Assistant Green uses a 1.8 GHz quad-core processor. Cameras, local voice, databases and other companion services determine additional compute demand.
- RAM
- Official HAOS reference points start at 2 GB RAM for Raspberry Pi 4/5 and 2 GB for a HAOS virtual machine; Home Assistant Green uses 4 GB. More memory is mainly for virtualization, local voice, databases, cameras and other services rather than normal automations alone.
- Storage
- Home Assistant Green uses 32 GB eMMC, and the official HAOS VM guide also uses a 32 GB default virtual disk example. That is a reference point, not a universal capacity rule. SSD storage is a practical upgrade for larger recorder history, backups, databases and companion services.
- Network and radios
- Use reliable wired Ethernet when possible. ZimaBoard 2 and ZimaCube 2 do not list built-in Zigbee, Thread or Z-Wave coordinators, so those protocols require compatible USB or network radio hardware.
- HAOS vs Container
- Home Assistant OS is the recommended installation type and supports Home Assistant apps and managed updates. Home Assistant Container runs on ZimaOS/Docker but has no Home Assistant apps; Zigbee USB devices can be mapped into the container manually, while Thread and Z-Wave lack the out-of-the-box app support available on HAOS.
- Best Zima starting point
- ZimaBoard 2 832 is already far above Home Assistant's basic official reference hardware and is the natural Zima starting point for a dedicated HAOS appliance or normal Container host. Choose 1664 for additional services or local voice headroom, and ZimaCube 2 only when NAS, cameras, AI or broader home-server workloads justify it.
From official requirements to the right setup
Home Assistant sizing starts with HAOS versus Container, then grows with device access, recorder history, local voice, cameras, databases, virtualization and other services running on the same Zima system.
-
Official requirements
Choose Home Assistant OS when you want the recommended appliance-style installation with Supervisor-managed apps, backups and updates. Choose Home Assistant Container when you intentionally want to keep ZimaOS and manage Home Assistant plus companion services as separate Docker applications.
-
Confirm your needs
Use official reference hardware rather than a made-up universal minimum: Raspberry Pi HAOS requires at least 2 GB RAM; the current HAOS virtual-machine guide specifies at least 2 GB RAM and 2 vCPUs; Home Assistant Green uses a 1.8 GHz quad-core CPU, 4 GB RAM and 32 GB eMMC.
-
Leave room to grow
List the workloads beyond core automation: recorder retention, InfluxDB/Grafana, Zigbee/Thread/Z-Wave services, local Whisper/Piper, Ollama, Frigate, NVR recording and virtual machines can each create separate CPU, RAM, storage, USB-device or GPU requirements.
-
Run it on ZimaOS
Install Home Assistant using the chosen path, map or pass through the required radio devices, restore or create the configuration, then observe CPU, memory, database growth and automation latency during normal use before adding heavier voice, camera or AI workloads.
Check every playback client
- Installation type: Home Assistant OS or Home Assistant Container
- Approximate device, entity and automation count
- Zigbee, Thread, Z-Wave or Bluetooth radio requirements
- Recorder history, database retention and analytics needs
- Local voice: Speech-to-Phrase, Whisper, Piper or LLM workloads
- Camera, Frigate or object-detection workloads
- USB coordinator mapping or passthrough and physical radio placement
- Other ZimaOS apps, VMs, storage and backup jobs running concurrently
Official minimum requirements
Home Assistant does not publish one universal CPU, RAM and storage minimum for every supported platform. The official installation guide instead publishes installation-specific requirements and official hardware reference points.
Use 2 GB RAM as the current official floor for the Raspberry Pi HAOS path and for HAOS virtual machines, with 2 vCPUs required for the VM path. Home Assistant Green's 4 GB RAM and 32 GB eMMC provide an official appliance reference. For x86 Zima hardware, installation type and companion workloads matter more than matching a single generic minimum.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Raspberry Pi HAOS reference | Raspberry Pi 4 or 5 with at least 2 GB RAM | This is the current requirement on Home Assistant's Raspberry Pi installation path; it is not a universal minimum for every platform. |
| HAOS virtual-machine minimum | At least 2 GB RAM and 2 vCPUs | Home Assistant's current Linux virtual-machine instructions specify these minimum resources and require UEFI boot. |
| Official appliance reference | Home Assistant Green: 1.8 GHz quad-core, 4 GB RAM, 32 GB eMMC | Home Assistant positions Green as its easiest entry appliance and says it provides a fast and smooth Home Assistant experience. |
| Storage planning | No single universal capacity requirement | Home Assistant Green uses 32 GB eMMC, while DIY systems may need more for recorder history, backups, databases, media and apps. SSD storage is practical for write-heavy growth. |
| Recommended installation type | Home Assistant Operating System | Home Assistant OS includes the Supervisor, supports Home Assistant apps and managed updates, and is the recommended installation type for most users. |
| Home Assistant Container | Supported on Docker, but without Home Assistant apps | Container users manage the host and updates themselves. USB devices such as Zigbee coordinators can be mapped manually, while Thread and Z-Wave do not have the out-of-the-box app support provided by HAOS. |
When to upgrade your hardware
Upgrade when Home Assistant expands beyond ordinary automation into heavier database, voice, camera, AI or virtualization workloads. Device count alone is usually a weaker sizing signal than what those devices make the server process.
Recorder history and analytics keep growing
Local voice becomes part of the smart home
Cameras, Frigate or local AI join the server
For focused local control, Speech-to-Phrase can run on modest Home Assistant hardware. For open-ended local speech with Whisper Base, Home Assistant currently recommends at least an Intel N100 or equivalent. N150-class hardware therefore provides a sensible CPU starting point, while larger Whisper models, concurrency or local LLMs can justify more.
For users moving from cloud voice or fixed-command speech to fully local Whisper, Piper or LLM-assisted voice pipelines.Camera decoding, recording and object detection can dwarf ordinary automation workloads. Treat Frigate, NVR storage and AI acceleration as separate services and size CPU, RAM, disk throughput and accelerator hardware around the camera plan.
For smart homes adding multiple cameras, continuous recording or local object detection.Plan hardware growth with confidence
Home Assistant grows most reliably when the automation core, radio layer, database, backups and compute-heavy companion services are planned as separate resources.
Move write-heavy data to durable storage
Home Assistant Green demonstrates that eMMC can be suitable for a dedicated appliance, while larger DIY installations benefit from SSD storage when recorder history, logs, databases, backups or companion applications create sustained writes.
Use SATA or NVMe SSD storage when the data workload grows; do not upgrade storage solely because ordinary automations are present.Plan radios independently from the server
Zigbee, Thread and Z-Wave depend on coordinator hardware and radio placement, not CPU or RAM. With Container installs, USB devices may also need explicit mapping into the Home Assistant container.
Choose a compatible USB or network coordinator and place it away from interference; the server itself does not replace the radio.Keep recoverable backups outside the Home Assistant host
Keep recovery copies away from the same system disk. Home Assistant OS provides managed backup functionality, while Container deployments require you to protect the configuration and companion-service data through your own host-level backup plan.
A Zima NAS or another independent destination can hold Home Assistant backups even when Home Assistant itself runs on a dedicated device.Separate core automation from heavy AI workloads
A stable automation core does not need to become an AI workstation. Speech-to-Phrase can stay lightweight, while Whisper, Ollama and Frigate can be separated or given reserved resources so lighting, alarms and automations remain responsive.
Choose additional CPU, RAM or GPU capacity only for the companion workloads that you actually plan to run.Can it run on ZimaOS?
Home Assistant can use Zima hardware in two distinct ways. ZimaOS App Store applications are Docker-based, so the ZimaOS Home Assistant path is a Container deployment. A direct Home Assistant OS installation instead turns the Zima device into the Home Assistant appliance.
Install Home Assistant Container from ZimaOS
Install Home Assistant from the ZimaOS App Store when you want to keep ZimaOS as the host and run Home Assistant beside NAS, media, backup and other Docker applications. Treat this as Home Assistant Container, not Home Assistant OS.
Open Home Assistant in the ZimaOS App StoreUnderstand the Container feature boundary
Home Assistant Container has no Home Assistant apps. The official Container guide shows that USB devices such as Zigbee coordinators can be mapped into the container manually; Thread and Z-Wave do not have the out-of-the-box app support available on HAOS.
Compare Home Assistant installation typesInstall Home Assistant OS for the full appliance experience
ZimaBoard 2 lists Home Assistant OS as a compatible operating system. Use direct HAOS when the device should primarily be a Home Assistant appliance. Installing another operating system on the same target system disk replaces the ZimaOS installation there.
Read the ZimaBoard Home Assistant guideChoose Zima hardware for your Home Assistant workload
Choose HAOS versus ZimaOS Container first, then size for the workloads Home Assistant will coordinate. Ordinary automations need little hardware; local Whisper, cameras, databases, virtualization and companion containers are what justify larger Zima configurations.
Do you want Home Assistant OS with Supervisor-managed apps and appliance-style updates?
Yes — Home Assistant should be the primary appliance
Install Home Assistant OS directly on ZimaBoard 2 when Home Assistant should own the device. ZimaBoard 2 is far above the official entry reference in CPU and memory, so choose between 832 and 1664 based on companion voice/data workloads rather than basic automation.
- Dedicated HAOS appliance for normal automation, radios and dashboardsZimaBoard 2 832
- Dedicated HAOS with more memory for local Whisper, databases or future appsZimaBoard 2 1664
No — keep ZimaOS and run Home Assistant Container
Keep ZimaOS when Home Assistant is one Docker service in a broader home server. Deploy services that HAOS would provide as apps as separate containers, and handle device mapping and backups at the ZimaOS/container layer.
- Home Assistant Container plus NAS, backups and normal self-hosted servicesZimaCube 2 Standard
- More containers, databases, cameras and faster storage/network workflowsZimaCube 2 Pro
- Dedicated GPU or 64 GB memory for Frigate, local AI, LLMs or heavy VMsZimaCube 2 Creator Pack
This is a workload guide, not a guaranteed device-count or automation-latency benchmark. Results depend on installation type, integration behavior, recorder retention, radio hardware, databases, cameras, voice pipelines, virtual machines and other services.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A dedicated Home Assistant OS appliance or compact ZimaOS Home Assistant Container host with substantial CPU and memory headroom over Home Assistant's official entry reference systems. | Core automations, dashboards, common integrations, USB radio coordinators, normal recorder history and light additional services. |
|
No built-in Zigbee, Thread or Z-Wave coordinator is listed. Direct HAOS replaces ZimaOS on the target system disk; the ZimaOS Container path has no Home Assistant apps and requires manual management of companion services. | Get Now |
| ZimaBoard 2 1664 | A Home Assistant build with additional memory for local Whisper, databases, multiple containers or future experimentation. | Home Assistant plus MQTT, automation companions, databases, local speech services or a broader compact homelab workload. |
|
Choose 16 GB for companion workloads and memory headroom, not because normal Home Assistant requires it. Smart-home radios still require separate hardware. | Get Now |
| ZimaCube 2 Standard | A ZimaOS home server where Home Assistant Container shares the system with multi-drive storage, backups, media and other normal self-hosted applications. | Home Assistant Container, NAS duties, several always-on apps, larger backup storage and moderate smart-home data workloads. |
|
This is usually more hardware than Home Assistant alone needs. Choose ZimaCube 2 Standard because Home Assistant is part of a broader NAS/home-server workload, not simply because the smart home has many devices. | Get Now |
| ZimaCube 2 Pro | Home Assistant Container combined with heavier databases, cameras, many containers, large local storage and faster network workflows. | Smart-home automation beside NVR workloads, analytics, backups, media servers and multiple always-on self-hosted applications. |
|
10GbE, six drive bays and the stronger CPU are not normal Home Assistant requirements; they are justified by the companion server workload. | Get Now |
| ZimaCube 2 Creator Pack | A smart-home server that also has a genuine dedicated-GPU or 64 GB memory requirement for Frigate, local LLMs, AI inference or heavy VMs. | Home Assistant as the automation layer while separate GPU-accelerated services handle computer vision, local AI or other heavy compute. |
|
Usually excessive for Home Assistant alone. Choose it only when a real GPU, large-memory, AI or VM workload is part of the system design. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
★★★★★
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
★★★★★
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
★★★★★
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
★★★★★
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
These answers cover installation type, hardware sizing, radios, storage and local voice questions that are not fully addressed in the sections above.
How much RAM does Home Assistant need?
Home Assistant does not publish one universal RAM minimum for every platform. Current official reference points include at least 2 GB RAM for Raspberry Pi 4/5 HAOS and 2 GB for a HAOS virtual machine, while Home Assistant Green uses 4 GB. More memory is mainly useful for voice, databases, virtualization, cameras and other companion services.
Is 8 GB RAM enough for Home Assistant?
Yes. Eight gigabytes is already above Home Assistant's official entry reference hardware and is ample for ordinary automation. The reason to move beyond 8 GB is usually local voice, databases, Frigate, virtualization, many containers or other services sharing the same machine.
Should I run Home Assistant OS or Home Assistant Container on Zima hardware?
Choose Home Assistant OS when the device is primarily a smart-home appliance and you want the officially recommended installation with Supervisor-managed apps and updates. Choose Home Assistant Container when you want to keep ZimaOS and run Home Assistant beside NAS and other Docker services, accepting that Home Assistant apps are unavailable and companion services are managed separately.
Can ZimaBoard 2 run Home Assistant OS?
Yes. ZimaBoard 2 officially lists Home Assistant OS as a compatible operating system. Its Intel N150 and 8 GB or 16 GB RAM provide much more compute and memory than Home Assistant's entry reference hardware. A direct HAOS installation uses the device as the Home Assistant appliance rather than keeping ZimaOS on the same target system disk.
Does ZimaBoard 2 include Zigbee, Thread or Z-Wave?
No built-in Zigbee, Thread or Z-Wave coordinator is listed for ZimaBoard 2. Add a compatible USB or network coordinator. With Home Assistant Container, USB devices such as Zigbee coordinators can be mapped manually, while Home Assistant notes that Thread and Z-Wave do not have the out-of-the-box app support available on HAOS.
Do I need an SSD for Home Assistant?
Not for every installation. Home Assistant Green uses 32 GB eMMC successfully as an official appliance. SSD storage becomes more attractive when a DIY system keeps longer recorder history, external databases, more backups or other write-heavy services.
How much hardware do I need for a local Home Assistant voice assistant?
It depends on the speech path. Speech-to-Phrase is designed to run on modest hardware. For fully local open-ended speech with Whisper Base, Home Assistant currently recommends at least an Intel N100 or equivalent; the N150 in ZimaBoard 2 is therefore a reasonable CPU class. More memory or GPU compute becomes relevant mainly for larger Whisper models, concurrency or local LLMs.
When should I choose ZimaCube 2 instead of ZimaBoard 2 for Home Assistant?
Choose ZimaBoard 2 for a dedicated HAOS appliance or compact Container host. Choose ZimaCube 2 when Home Assistant is one part of a larger system that also needs multi-drive storage, backups, several services, NVR workloads or local AI. Pro and Creator Pack are justified by those companion workloads, not by ordinary Home Assistant automation.
What sources and further reading informed this Home Assistant hardware guide?
Home Assistant's official installation page is the authority for the current installation model: HAOS is recommended, Container has no Home Assistant apps, the Raspberry Pi HAOS path requires at least 2 GB RAM, and Container users manage the host themselves. The InfluxData, Home Assistant Community and Smart Home Shop UK articles provide practical hardware and storage opinions rather than a universal official minimum. CloudZat is useful specifically for heavier local-voice planning; where any third-party number conflicts with current Home Assistant documentation, the current official Home Assistant source takes precedence.
