openHAB community discussions frequently report around 800 MB–1.2 GB typical process memory and note Docker/64-bit Java adds overhead. Host swap/OOM pressure is a better signal than the nominal 1 GB free-memory floor.
Containerized openHAB and low-memory hosts.openHAB Hardware Requirements: RAM, Java 21, 64-bit & Server Load
Learn openHAB 5 hardware requirements for 64-bit OS, Java 21, RAM, storage and Docker, then choose suitable ZimaOS hardware.
openHAB requirements at a glance
openHAB 5 requires a 64-bit operating system and a 64-bit Java 21 JVM. The openHABian documentation says an old x86 server or desktop can run openHAB with about 1 GB of free RAM, while its current Raspberry Pi recommendation is a Pi 4 or 5 with 2 or 4 GB RAM. That makes 1 GB free RAM a low-end floor and 2–4 GB a more useful dedicated-system reference before adding MQTT, persistence, databases or other services.
- CPU / architecture
- openHAB 5 requires a 64-bit OS and Java 21. No official CPU core-count or clock-speed minimum is published.
- RAM
- openHABian says old x86 systems need about 1 GB free RAM; current Pi recommendation is Pi 4/5 with 2 or 4 GB. Java heap and co-hosted services can require more.
- Java
- Current openHAB 5 prerequisite: 64-bit Java 21 JVM. 32-bit OS installations are no longer supported for openHAB 5.
- Storage
- Use reliable persistent storage for configuration, userdata, caches, logs and persistence databases. openHABian recommends endurance-class SD storage on Raspberry Pi because 24/7 automation writes matter.
- Network
- openHAB installation guidance prefers a dedicated, continuously running system connected by Ethernet for reliable 24/7 automation.
- Best Zima starting point
- ZimaBoard 2 832's 8 GB RAM and modern 64-bit Intel CPU provide generous headroom for openHAB 5. The 1664 is useful when MQTT, databases, dashboards and other services share the same ZimaOS host.
From official requirements to the right setup
openHAB 5 sizing starts with the 64-bit Java 21 platform gate, then scales by bindings, persistence and co-hosted services.
-
Official requirements
Confirm a 64-bit host/runtime first. openHAB 5 documentation requires an up-to-date 64-bit OS and Java 21; running openHAB 5 on a 32-bit OS is no longer supported.
-
Confirm your needs
Use 1 GB free RAM as a low-end openHABian reference, not a complete ZimaOS-server recommendation. The current openHABian hardware recommendation is Raspberry Pi 4 or 5 with 2 or 4 GB RAM for a dedicated system.
-
Leave room to grow
Add memory/storage for bindings, persistence, databases, MQTT, rules and scripting. Java heap behavior means reserved memory can look high, and Docker plus other services adds system overhead.
-
Run it on ZimaOS
Install openHAB from the ZimaOS App Store, restore representative configuration, enable the real bindings/persistence stack and monitor Java heap, host memory and storage writes over several normal automation cycles.
Check every playback client
- 64-bit OS and host architecture
- Java 21 runtime
- At least ~1 GB free RAM for low-end openHABian reference
- Bindings and Things count
- Rules, JavaScript/Python scripting and transformations
- Persistence/database choice and retention
- MQTT, Grafana, InfluxDB and other co-hosted services
- Reliable persistent storage and Ethernet
Official minimum requirements
openHAB publishes a clear software/architecture prerequisite and useful hardware guidance, though not a universal CPU-core table.
For current openHAB 5, the non-negotiable requirement is 64-bit OS + Java 21. A dedicated system with 2–4 GB is a practical official Raspberry Pi reference, while a ZimaOS host should leave additional headroom for Docker and other applications.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Operating system | 64-bit OS required for openHAB 5 | 32-bit OS images are no longer supported for openHAB 5. |
| Java | 64-bit Java 21 JVM | Current official prerequisite. |
| Low-end x86 RAM guidance | About 1 GB free RAM | openHABian says any old x86 server/desktop can work with this free-memory level. |
| Current Raspberry Pi recommendation | Pi 4 or 5 with 2 or 4 GB RAM | Current openHABian recommended dedicated hardware. |
| Availability/network | 24/7 dedicated system; Ethernet preferred | openHAB installation overview emphasizes continuous availability and wired networking. |
| Persistent storage | No fixed capacity minimum published | Configuration is small, but logs, persistence data and write endurance matter over long-term use. |
When to upgrade your hardware
Upgrade openHAB when Java memory pressure, persistence or the wider automation stack—not basic item count—requires it.
Java heap plus Docker/host memory leaves too little headroom
Persistence, graphing and databases run on the same machine
Rules, scripting and large binding stacks become slow
openHAB's installation guidance expects users may add MQTT, persistence and graphing software. Those companion services can dominate RAM and storage requirements.
Users consolidating InfluxDB/Grafana/MQTT and openHAB.Automation logic, scripting runtimes and many active integrations add event-processing and memory load even though openHAB remains event-driven.
Large smart homes with many rules, bindings and external systems.Plan hardware growth with confidence
Scale openHAB by giving Java predictable headroom and keeping persistence on reliable storage.
Use a 64-bit platform with comfortable free memory
openHAB 5's Java 21 requirement makes current 64-bit hardware the stable path. ZimaBoard 2 avoids the old 32-bit Pi transition problem entirely.
8 GB host RAM leaves substantial room beyond a dedicated openHAB installation.Tune Java heap only from real usage
openHAB users can adjust `-Xms`/`-Xmx`, but Java may reserve memory differently from actual working use.
Watch heap, host free memory and OOM behavior rather than copying someone else's heap value.Use reliable SSD/eMMC/NVMe storage for userdata
openHABian recommends endurance storage on Pi because automation logs, caches and persistence create long-term writes.
Keep appdata and databases on durable persistent storage with backups.Separate heavy databases when the stack grows
InfluxDB, PostgreSQL, Grafana and other services can be split or given dedicated resources when they become larger than openHAB itself.
Upgrade for the whole observability/automation platform rather than the openHAB process alone.Can it run on ZimaOS?
openHAB is currently available in the ZimaOS App Store and the current Zima x86-64 platform cleanly matches openHAB 5's 64-bit direction.
Install openHAB from the ZimaOS App Store
The current ZimaOS listing provides openHAB as a Home/Developer application.
Open openHAB in the ZimaOS App StoreStay on the 64-bit Java 21 path
openHAB 5 requires a 64-bit OS and Java 21. Container packaging should provide the compatible runtime, but migration from old 32-bit installations still needs attention.
Read openHAB installation prerequisitesTreat 2–4 GB as dedicated-system guidance, not a ZimaOS cap
The openHABian recommendation assumes a relatively dedicated automation host. ZimaOS users should leave memory for Docker and additional services.
Read openHABian hardware guidanceChoose Zima hardware for openHAB
openHAB 5's official dedicated-system guidance is modest. Choose more Zima hardware for databases, dashboards and other automation services sharing the server.
Is openHAB mostly a dedicated controller, or part of a larger automation/data stack?
Normal home automation controller
ZimaBoard 2 832 provides far more memory than openHABian's current 2–4 GB Raspberry Pi recommendation.
- Normal openHAB 5 serverZimaBoard 2 832
- openHAB plus MQTT/databases/monitoringZimaBoard 2 1664
Large all-in-one home automation and storage platform
Move to ZimaCube for integrated storage and broader service headroom.
- Integrated automation/storage hostZimaCube 2 Standard
- Heavier automation/database/service stackZimaCube 2 Pro
The 1 GB free-RAM and 2–4 GB Raspberry Pi guidance does not guarantee a fixed Thing/item/rule count. Java heap, bindings, scripting, persistence and co-hosted applications can change real requirements.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | A normal openHAB 5 home-automation server. | Bindings, rules, persistence and several lightweight companion services. |
|
Large databases or many additional containers can matter more than openHAB itself. | Get Now |
| ZimaBoard 2 1664 | openHAB plus MQTT, databases, Grafana and other smart-home services. | A larger automation/observability stack. |
|
16 GB is whole-server headroom; openHAB's dedicated-system guidance is much lower. | Get Now |
| ZimaCube 2 Standard | An all-in-one automation and multi-drive home server. | openHAB plus backups, persistence and storage-heavy services. |
|
Choose it for platform consolidation rather than a core openHAB requirement. | Get Now |
| ZimaCube 2 Pro | A heavier home server with large databases and many services. | Automation, monitoring, storage and high local data workflows. |
|
10GbE and Core i5 capacity primarily benefit the wider server stack. | 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 FAQ topics are query-fan-out driven around openHAB 5 RAM, Java 21, 64-bit support, Docker memory, Raspberry Pi sizing and persistence, with openHAB community/Reddit discussions used to identify recurring confusion.
How much RAM does openHAB 5 need?
openHABian says an old x86 system can work with about 1 GB of free RAM, while the current Raspberry Pi recommendation is 2 or 4 GB. For ZimaOS, 8 GB gives comfortable headroom for openHAB plus the container host.
Does openHAB 5 require a 64-bit system?
Yes. Current openHAB documentation requires a 64-bit OS and Java 21 for openHAB 5. Running openHAB 5 on a 32-bit OS is not supported.
Why does openHAB appear to use around 1 GB or more RAM?
openHAB runs on the JVM, which manages heap and can reserve memory differently from what the operating system shows as active use. Community discussions commonly report roughly 800 MB–1.2 GB for typical systems, but configurations vary.
Is 2 GB RAM enough for openHAB?
For a dedicated, normal openHAB installation it often is, and openHABian officially recommends Pi 4/5 with 2 or 4 GB. Docker plus databases and other apps reduce the available headroom.
Why can Docker need more memory for openHAB?
The container host, 64-bit JVM and other containers all consume memory in addition to openHAB's Java heap. Low-memory Pi users frequently report that co-hosted Docker services create pressure even when openHAB itself is healthy.
Can ZimaBoard 2 832 run openHAB 5?
Yes. It is a modern 64-bit x86 system with 8 GB RAM, comfortably above openHABian's current 2–4 GB Raspberry Pi recommendation.
Should openHAB run from an SD card, eMMC or SSD?
openHABian recommends endurance-grade SD media on Raspberry Pi because 24/7 automation writes matter. On ZimaOS, reliable eMMC/SSD/NVMe appdata storage with backups is preferable for long-term logs and persistence.
Do more smart-home devices automatically require much more RAM?
Not linearly. Bindings, rules, persistence, scripting and database retention often matter more than raw device count. Very large deployments should be sized from actual Java heap and event-processing behavior.
What sources and further reading informed this openHAB hardware guide?
openHAB's current Installation Overview establishes the 64-bit OS and Java 21 prerequisite. openHABian provides the 1 GB free-RAM low-end guidance and 2–4 GB Raspberry Pi recommendation. Community and Reddit discussions were used for fan-out around Docker/JVM memory and Pi sizing, but their observed memory figures are not treated as official minimums. The ZimaOS App Store confirms the current openHAB package.
