Two ZimaBoards, Household Services and Local AI: u/mrt01010101’s Homelab

Eva Wong is the Technical Writer and resident tinkerer at ZimaSpace. A lifelong geek with a passion for homelabs and open-source software, she specializes in translating complex technical concepts into accessible, hands-on guides. Eva believes that self-hosting should be fun, not intimidating. Through her tutorials, she empowers the community to demystify hardware setups, from building their first NAS to mastering Docker containers.

Thank you to u/mrt01010101 for sharing a two-node ZimaBoard homelab that keeps household infrastructure separate from a more demanding data-and-AI machine. Its most useful lessons come from real interruptions: media playback competing with inference, cascading alerts and a GPU that did not recover cleanly after a warm reboot.

The original contribution supplies the hardware photograph and describes the builder’s working arrangement. This account preserves those reported experiences while distinguishing them from general guidance. The external GPU connection and any model-performance figures remain contributor reports, not an independently reproduced hardware test.

Separate the Services That Should Stay Predictable

A two-machine design can express a priority: some services should remain predictable while another computer is used for demanding work. That distinction is useful in a household where losing name resolution feels different from pausing an experiment.

For a similar setup, list the services that ordinary devices need before an administrator signs in. Then identify the host, network and power dependencies beneath them. Putting a service on a smaller machine does not make those dependencies disappear, but it makes the intended responsibility easier to explain.

The contributor’s original photograph of the two-node homelab and external GPU hardware.
The contributor’s original photograph of the two-node homelab and external GPU hardware. Source: u/mrt01010101.
Component or service Role in the story
zima1: ZimaBoard, Debian 13 Core services including DNS filtering, reverse proxy and home automation
zima2: ZimaBoard 2, Ubuntu 24.04 HWE Media, files, observability and local AI
External Radeon GPU The contributor reports an OCuLink-connected RX 9060 XT 16 GB
Separate OS, application and media storage Capacity is assigned by workload in the original account

For readers exploring the automation role, our Home Assistant setup guide for ZimaBoard covers that application separately from the AI workload. The silent ZimaBoard 2 build with dual NVMe storage offers a contrasting physical design focused on keeping everyday services unobtrusive.

For the core node’s access layer, Caddy’s automatic HTTPS documentation explains certificate handling and HTTPS behaviour. A valid certificate and a working proxy do not establish which services are reachable outside the home; the network and access rules need to be checked separately.

A Playback Problem Revealed a Shared Resource

Workload interference is easiest to understand through the experience affected by it. When two services share compute resources, a problem in one configuration can become visible in another application. A movie stuttering during an AI conversation is a more useful symptom than a generally busy dashboard.

The contributor traced this particular interruption to hardware transcoding being disabled. The broader diagnostic lesson is to inspect what the playback session is actually doing before assuming a larger model or faster processor is the answer. Jellyfin’s Intel GPU guide explains the supported acceleration methods and configuration considerations.

For another deployment, verify acceleration through a representative playback session. Then repeat the check after changes to containers, device access or drivers. A selected interface option is useful configuration information; the running session shows whether the expected processing path is being used.

External GPU Recovery Is Part of Operating the System

Expansion changes the boundaries of a compact computer. The host, adapter, graphics card, power and software all participate in the resulting system. A successful startup is useful evidence, but it is only one state an installation needs to handle.

The warm-reboot issue in this account is a contributor-specific troubleshooting experience. It should not become a blanket instruction to power-cycle arbitrary hardware or a promise that every ZimaBoard accepts the same adapter. Anyone attempting a similar arrangement needs the exact connection, power and software details for their own equipment.

A maintenance record should distinguish restart, shutdown and loss-of-power behaviour. That makes an interruption easier to investigate without treating every recovery attempt as a new experiment. It also helps explain why an otherwise useful system may still need hands-on attention after a particular kind of restart.

Useful Alerts Need to Identify the Failed Dependency

The creator also describes using Home Assistant and Prometheus to investigate repeated overnight hot-water heating that depleted a home battery. Moving that heating to solar hours gave the monitoring work a concrete household purpose. It is a reported control change, rather than an independently measured energy-saving result.

Monitoring many applications can produce many symptoms from one failure. If a host disappears, a list of unavailable services is accurate but may still leave the operator reconstructing the common cause. The contributor’s alert experience makes that limitation tangible.

For readers designing monitoring, start with the question an alert should answer. Is the machine unreachable, is a process stopped, or is the application answering incorrectly? Keep those meanings distinct. An independent host check can provide context for several application checks without claiming that every service failure has the same cause.

Home Automation Also Needs Recovery Outside the Main Workload

A home automation system can influence ordinary routines even when its interface looks like another application dashboard. Preserve the configuration and the information required to restore it before changing the surrounding infrastructure. Home Assistant backup documentation explains backup destinations and recovery material.

The official screenshot below illustrates those choices. It is not the contributor’s configuration. The relevant household principle is that the material needed to recover a service should remain accessible when the machine normally providing it is unavailable.

When checking a change, follow the path a household user actually takes:

  1. Confirm the core host and required network services are reachable.
  2. Open the application through its ordinary client.
  3. Exercise the workload and inspect the expected processing path.
Official Home Assistant backup-settings example; this is not the contributor’s installation.
Official Home Assistant backup-settings example; this is not the contributor’s installation. Source: Home Assistant.

When choosing how to deploy automation, the official Home Assistant installation options distinguish running the system on dedicated hardware from using a container or virtual machine. Those choices affect which host and data need to be included in the recovery record.

Keep the Boundary Between Reported Experience and a Build Guide

The original post is a rich account of a working personal system, but it does not publish a reproducible bill of materials and complete deployment procedure. Its value lies in the decisions and failures the owner can explain, rather than in an assumed guarantee for another installation.

That perspective connects with IKEA cabinet mini-rack with ZimaBoard 2 and small-homelab service roles in u/jc-21’s build. The form differs, but knowing which machine owns a service, which resources it shares and how an interruption is handled remains useful at either scale.

FAQ

Which machine carries the everyday core services?

The contributor assigns them to zima1, the original ZimaBoard running Debian 13.

Is the external GPU arrangement independently validated here?

No. It is reported by the contributor. This story does not establish compatibility for other adapters, power supplies or software versions.

Does a busy AI service always explain buffering?

No. Check the playback mode and actual processing path. In this account, the creator identified disabled hardware transcoding as part of the problem.

Is the backup image from the contributor?

No. The hardware photo is original; the backup-settings image is an explicitly credited Home Assistant documentation example.

Conclusion

This homelab makes the responsibilities of a small infrastructure node and a demanding application node visible. The practical depth comes from understanding how workloads, restart behaviour and monitoring interact.

A useful next step for readers is to document one dependency and test one ordinary household task after a change. That turns a collection of applications into a system whose behaviour can be explained.

Welcome to the ZimaSpace community! Share your setup, ask questions, and explore practical build guides, real user stories, and product updates with fellow self-hosters.

Zima Campaign Hub

More to Read

Get More Builds Like This

Stay in the Loop

Get updates from Zima - new products, exclusive deals, and real builds from the community.

Stay in the Loop preferences

We respect your inbox. Unsubscribe anytime.