Mini PC for Home Assistant and Plex: What Actually Matters

Two jobs that want different things

Home Assistant and Plex both run all day on a small box in a cupboard, and they want nearly opposite things from it. Home Assistant is a tiny workload: its own installation guide puts it on a Raspberry Pi 4 or 5 with as little as 2GB of memory. It needs a machine that stays up for months, boots from a proper drive, has a spare USB port for a radio dongle and sits on Ethernet.

Plex is easy until something needs converting. A file the television can play as it stands (direct play) costs the server almost nothing. When a phone on mobile data or a burnt-in subtitle track needs the video re-encoded on the fly, that is transcoding, and that is the whole question. Plex's hardware acceleration is built on Intel Quick Sync Video, so for Plex the processor brand is the decision.

Idle power is the running cost

A server runs around the clock, so what it draws doing nothing matters more than its peak. Intel rates the N100 at 6W and the Core i5-12600H in the NiPoGi CK10 at a 45W processor base power, rising to 95W in turbo. Those are sustained-load ratings, not idle figures, but the gap is the point: a box built around a low-power laptop chip costs little to leave on all year at British electricity prices, and an old desktop tower doing the same job costs a good deal more. The U-series Ryzen parts on our shelf (7730U, 7330U, 3500U) are the low-power chips; the H-series parts (Ryzen 7 6800H, Core i5-12600H) are hungrier.

Quick Sync: the one thing Plex asks for

Plex's support page is explicit: hardware-accelerated streaming uses Intel Quick Sync Video, which is in all recent Intel Core processors, and it needs an active Plex Pass. With it, more streams at once and, in Plex's words, less power. Without it every transcode is software on the CPU cores, and 4K HEVC is exactly the work the hardware exists for.

AMD is the awkward part. Plex describes its support for dedicated AMD cards as untested and provided as is, and the engines it lists for Linux are Intel, NVIDIA and software. So plan on software transcoding on every Ryzen machine here: fine for a 1080p stream or two on an eight-core Ryzen 7 6800H, and 4K files should be direct play.

One of the seven on our shelf is Intel: the NiPoGi CK10, whose Core i5-12600H Intel lists with Quick Sync Video, Iris Xe-class graphics, twelve cores and 16 threads. The Radeon 680M in the GEEKOM A6 and BOSGAME P3 Lite is the strongest integrated graphics on the page, and for Plex transcoding it is beside the point.

Gigabit is enough, 2.5GbE is for one job

Every pick here has a gigabit socket except the GMKtec mini PC, which has 2.5GbE, per the listing. For playback it changes nothing: a Plex stream to a television is a small slice of a gigabit link. It matters when the library lives on a NAS with its own 2.5GbE port and you are copying rips across, or when the box shares a full-fibre line above a gigabit. Either way, use a cable: Home Assistant's guides list an Ethernet connection as a requirement for every hardware route.

Memory, storage and the second slot

Neither job needs much memory on its own. It matters when one box runs both plus a Proxmox host and a few containers, which is where 32GB in the box (the BOSGAME P3 Lite and the CK10) or a high ceiling (96GB on the GEEKOM A6, 64GB on the A5) earns its keep.

Mini PCs hold one or two drives, not a NAS's worth. Only the CK10 lists a second M.2 slot free. A Plex library lives on a NAS or a USB drive while the box holds the operating system and the metadata, and Home Assistant needs so little space that the 256GB drive counted against the GEEKOM A5 as a desktop is no problem here.

Installing Home Assistant OS on bare metal writes the image over the internal drive, on a PC the guide assumes is dedicated to it, booting UEFI with Secure Boot disabled, so the Windows 11 Pro licence on the CK10, P1, Kron K1 and GMKtec is gone the moment you do it.

Fan noise

None of the seven is described as fanless. The quietest, per the listings, are the low-power machines: the GEEKOM A5 is the quietest combination on the page, and the NiPoGi P1, the ACEMAGICIAN Kron K1 and the GMKtec run quiet in normal use. The H-series machines (A6, P3 Lite and CK10) will use their fans under load, which is what an H-series part in a small case does, and NiPoGi publishes no noise figure for the CK10. A Home Assistant box idles nearly all the time; a Plex transcode is sustained load for the length of a film, so if silence in the room is the point, the box goes in a cupboard and the media comes down an Ethernet cable.

Proxmox or bare metal

Home Assistant OS on its own PC is the recommended installation type for most users, and the simplest. A plain Docker container costs you the add-ons (which Home Assistant now calls apps), and that is how Z-Wave and Thread are provided, so if you virtualise, run the full OS image as a virtual machine, which Home Assistant documents.

Plex is the constraint. Its documentation says hardware-accelerated streaming is not possible inside a virtual machine, because the host does not expose the video hardware to the guest, while a Docker container given the kernel device works normally. So on one box the layout is Proxmox on the metal, Home Assistant OS in a VM and Plex in a container that can see the graphics device. It also means a Zigbee stick passed through to the VM and three things to keep updated. Two small boxes is not a silly answer.

The dongle and the extension lead

This is the part a mini PC gets wrong out of the box. Home Assistant's Zigbee documentation says all computers and their peripherals generate the interference that degrades a 2.4GHz radio, and names USB 3.x ports and devices as the real-world culprits. Its advice: use a USB extension cable, plug the adapter into a USB 2.0 port or a powered USB 2.0 hub, and keep it away from USB 3.0 devices, Wi-Fi access points, power supplies and electrical cables. So the Zigbee stick never goes straight into the back of the box: put it on a long shielded extension lead, out in the open and well away from the case, and treat a Z-Wave stick the same way.

A used OptiPlex Micro, a new N100 box or a Raspberry Pi

Three things a forum will tell you to buy instead. A used Dell OptiPlex Micro (or Lenovo Tiny or HP Mini) with an Intel Core chip gives you Quick Sync, and Plex's generation advice is what to check: fifth generation or newer for the best results, seventh or newer for HEVC encoding. Most systems from the last ten years boot UEFI, per Home Assistant's guide. What you give up is the warranty and the low power draw.

A new N100 box is the other forum answer, and Intel's numbers explain why: a 6W rating, four cores, Quick Sync included, up to 16GB of memory on a single channel, and the N150 that followed keeps the same four cores and 6W rating. That is a Plex transcoder and a Home Assistant host in one; the single memory channel and the 16GB ceiling rule it out as the Proxmox box that does everything. None of the seven on our shelf uses one.

And the Raspberry Pi: Home Assistant runs happily on a Pi 4 or 5 with 2GB or more, from a microSD card, and for that job alone it is fine. For Plex it is direct play only, because the hardware engines Plex lists for Linux are Intel and NVIDIA, so every transcode on a Pi is software.

Where the seven picks fit

For Plex, or both jobs on one box, the NiPoGi CK10: Quick Sync, twelve cores, 32GB and a second M.2 slot, with gigabit Ethernet and an H-series fan as the costs. For Home Assistant alone, the GEEKOM A5 is the quiet eight-core answer, and the NiPoGi P1 (the deepest owner record on the shelf) and the Kron K1 (the highest owner rating of the seven) do the job for less with four cores. The GMKtec is the 2.5GbE box, for that socket alone; its processor is the oldest on the page. The GEEKOM A6 and BOSGAME P3 Lite are the strongest desktops on the page and the wrong tool for a headless server: you pay for Radeon graphics Plex cannot use and a memory ceiling a Home Assistant box will never approach. If the machine is also your desktop, that changes. The full comparison is on the mini PCs page.

Sources

• Home Assistant: Generic x86-64 installation guide (UEFI and Secure Boot, boot medium, dedicated PC, recommended installation type)
• Home Assistant: installation overview and hardware options (Raspberry Pi 4 or 5 with 2GB, Ethernet, virtual machines, Container without apps)
• Home Assistant: Zigbee Home Automation integration, interference avoidance
• Plex Support: Using Hardware-Accelerated Streaming
• Intel: Core i5-12600H product specifications
• Intel: Processor N100 product specifications