Smart Home Assistant
Hubs & dongles
Beelink ME mini N150

Beelink

Beelink ME mini N150

Native integrationLocal control
  • Wi-Fi
  • Bluetooth
See more hubs & dongles picks on our Amazon storefront →

Verified September 2026

Overkill for Home Assistant alone, but genuinely useful if you also want Frigate, Zigbee2MQTT and a Plex library on the same box — an Intel N150 with dual 2.5G LAN and six M.2 NVMe slots gives you server-grade headroom for a fraction of NAS-brand pricing. It's a 99mm cube, small enough to tuck behind a monitor, and idles low enough for genuine 24/7 duty without a leftover desktop's running costs. Against a Raspberry Pi 5: the Pi is simpler and cheaper for HAOS alone, but this trades that simplicity for real multi-VM headroom and six drive bays. Install HAOS as a VM under Proxmox rather than dedicating the whole box to it.

In Home Assistant

ControlTypeWhat it does
CPU usageSensorUtilisation inside the HAOS VM, scoped to the vCPU cores Proxmox allocated to the guest, not the host's full core count.
Memory usageSensor (%)RAM usage against the VM's assigned memory allocation, independent of total physical RAM on the box.
Disk usageSensor (%)Usage of the VM's virtual disk on the Proxmox storage backend, separate from free space on the underlying NVMe pool shared with other guests.
Coordinator connectivityBinary sensorWhether the passed-through USB Zigbee/Z-Wave adapter is present as a serial device inside the VM; goes unavailable if Proxmox drops the USB mapping across a reboot.
GPU loadSensoriGPU utilisation for hardware-accelerated detection, only populated when Frigate runs in a sibling container with the GPU device passed through rather than inside the HAOS VM.

Pass the USB Zigbee/Z-Wave coordinator into the HAOS VM as a discrete USB device by vendor/product ID rather than mapping by physical port or bus number — mapping by port is the most common failure mode, since it silently breaks after a host reboot re-enumerates the bus or the stick gets unplugged and replugged. The N150's integrated GPU has no hardware virtualisation splitting, so it can't be shared between host and guest; running Frigate in a sibling Proxmox container with the GPU device passed straight through gets hardware-accelerated detection without dedicating the whole GPU to one VM, which is the more common setup than passthrough into HAOS itself. Some Beelink units ship with virtualisation extensions disabled and buried outside the obvious BIOS menu, occasionally requiring a firmware update before the option even appears — worth checking before assuming passthrough is unsupported.

Specs

cpu
Intel N150 (4C/4T, up to 3.6GHz)
ram
12GB or 16GB LPDDR5 4800MHz (soldered)
power
100-240V 50/60Hz external adapter, 1.5A max input; N150-class idle draw, well under a repurposed desktop
storage
64GB eMMC system disk + 5x M.2 2280 PCIe 3.0 slots, up to 24TB total
dimensions
99 x 99 x 99mm
networking
dual 2.5G LAN (Intel i226-V), Wi-Fi 6, Bluetooth 5.2
Affiliate disclosure: Some links in this article are affiliate links. If you buy via one of these links, we may earn a small commission at no extra cost to you. This never affects our editorial decisions — see our affiliate policy.