Home Assistant on NAS - Australian Setup Guide

A NAS with an Intel or AMD x86 CPU running Docker is the most reliable way to host Home Assistant in an Australian home, and it consolidates your smart home controller, file server, and backup system into a single always-on device. Running Home Assistant on a dedicated Raspberry Pi works, but a NAS gives you proper storage redundancy, scheduled backups, and the processing headroom to run additional containers alongside it, including MQTT brokers, Node-RED, Zigbee2MQTT, and media servers. If you already own a NAS with an x86 CPU or are considering buying one, Home Assistant is one of the best reasons to put that hardware to work. This guide covers everything Australian buyers need to know: which NAS models to choose, how to install Home Assistant via Docker or a VM, how to pass through Zigbee and Z-Wave USB sticks, and how to solve the CGNAT remote access problem that affects most NBN connections.

Why Run Home Assistant on a NAS Instead of a Raspberry Pi

The Raspberry Pi has been the default Home Assistant platform for years, and it works fine for small setups. But a NAS solves three problems that Pi users constantly hit: storage reliability, processing power, and SD card corruption. A NAS runs on proper hard drives or SSDs with RAID redundancy, has a real CPU that won't choke when compiling automations or running machine learning integrations, and doesn't rely on a fragile SD card that fails without warning.

More importantly, a NAS is already designed to run 24/7. It has a proper power supply and thermal management. Pair it with a UPS for graceful shutdown during power outages. Your Home Assistant instance gets the same always-on reliability as your file shares, Plex server, or backup system. One box, one power draw, one set of maintenance tasks.

The trade-off is cost. The TerraMaster F2-425 starts at $499 from MSY, Scorptec or UMart before drives, while a Raspberry Pi generally costs less. But if you already need a NAS for storage, running Home Assistant on it is essentially free. It uses minimal resources and doesn't require any additional hardware beyond a Zigbee or Z-Wave USB coordinator if you're using those protocols.

Minimum Hardware Requirements

Home Assistant Container (the Docker version) is not resource-hungry, but it does have firm requirements that rule out some NAS models entirely.

The CPU architecture matters most. Home Assistant supports both amd64 and aarch64 (64-bit ARM, which covers Realtek RTD1296/RTD1619B-based NAS units). Compatibility for specific third-party integrations and add-ons should still be checked individually rather than assumed. If you plan to run Home Assistant with a full integration ecosystem, an Intel Celeron or AMD Ryzen-based NAS is the safest choice. The budget ARM models, including the Synology DS124 (about $255), QNAP TS-233 (about $402), and Asustor Drivestor 2 Lite AS1102TL (about $299), can technically run it but may struggle with anything beyond a basic setup.

Best NAS Models for Home Assistant in Australia

The ideal Home Assistant NAS has an x86 CPU, at least 4 GB of RAM, Docker support, and USB 3.0 ports for Zigbee/Z-Wave coordinators. Here are the models that tick every box, with current Australian pricing from the major retailers.

The Synology DS225+ (about $599) suits most Australian smart home setups because Synology's Container Manager is the most polished Docker interface on any NAS, and the community documentation for running Home Assistant on Synology is extensive. The 2 GB base RAM is tight. Upgrade to at least 4 GB if running additional containers alongside HA. For more storage capacity and room to grow, the DS425+ (about $899) provides four bays at a moderate price increase.

The QNAP TS-264 (about $1,014) ships with 8 GB of RAM, making it the best value for running Docker and virtualisation workloads without upgrades. QNAP's Container Station and Virtualisation Station both support Home Assistant installation. If you want four bays, the TS-464 (about $1,129) is the go-to choice and has enough headroom for Home Assistant plus a full container stack.

The Asustor AS5402T (about $545) and AS5404T (about $749) are strong alternatives, especially for buyers who want Portainer-based Docker management and a gaming-inspired design. Asustor's ADM supports Docker natively and USB passthrough works without extra configuration. See our best NAS for Docker and home automation guide for a deeper comparison.

The TerraMaster F2-425 ($499 at UMart) deserves a mention as the budget x86 option. It has an Intel Celeron N5095 and runs Docker, but TerraMaster's TOS software is less mature than Synology's DSM or QNAP's QTS, and community documentation for Home Assistant on TerraMaster is sparse. It works, but expect to spend more time troubleshooting.

Docker vs VM. Two Ways to Install Home Assistant

There are two practical ways to run Home Assistant on a NAS, and the right choice depends on whether you need the full add-on ecosystem or just the core platform.

Option 1: Home Assistant Container (Docker)

This is the simplest and most resource-efficient method. You run the official Home Assistant Container image inside Docker, which is available on Synology (Container Manager), QNAP (Container Station), and Asustor (Portainer/Docker CE). The container runs alongside your other NAS services without a hypervisor layer, so overhead is minimal.

Option 2: Home Assistant OS (VM)

For the full Home Assistant experience including the Add-on Store, automatic backups, and the Supervisor management layer, you need to run Home Assistant OS inside a virtual machine. Synology offers Virtual Machine Manager (VMM), QNAP offers Virtualisation Station, and both support the HAOS VM image. This gives you the same experience as running Home Assistant on dedicated hardware like Home Assistant Green or Yellow.

Step-by-Step: Installing Home Assistant via Docker

This walkthrough covers the Docker method, which works on Synology, QNAP, and Asustor. The process varies slightly by NAS brand, but the core steps are the same.

Step 1. Enable Docker on Your NAS

Synology: Open Package Center, search for "Container Manager" (it replaced the old "Docker" package in DSM 7.2), and install it. QNAP: Open App Center, search for "Container Station", and install it. Asustor: Open App Central, install "Docker CE" and optionally "Portainer" for a web GUI. All three platforms pull Docker images from Docker Hub.

Step 2. Create a Configuration Directory

Create a shared folder or directory on your NAS to store the Home Assistant configuration. This keeps your configuration persistent across container restarts. On Synology, create a shared folder called homeassistant (or use an existing docker shared folder). On QNAP, create a folder under /share/Container/homeassistant. On Asustor, use /volume1/docker/homeassistant or similar.

Step 3. Deploy the Container via Docker Compose

The cleanest method is a Docker Compose file. SSH into your NAS (or use the Container Manager/Station GUI to create a new project) and use this configuration:

version: '3'
services:
  homeassistant:
    container_name: homeassistant
    image: ghcr.io/home-assistant/home-assistant:stable
    volumes:
      - /volume1/docker/homeassistant:/config
      - /etc/localtime:/etc/localtime:ro
    devices:
      - /dev/ttyUSB0:/dev/ttyUSB0  # Zigbee/Z-Wave USB stick
    restart: unless-stopped
    privileged: true
    network_mode: host

Adjust the volume path to match your NAS directory structure. The network_mode: host setting is important. It allows Home Assistant to discover devices on your local network via mDNS and SSDP, which is essential for finding Chromecast, Sonos, and other smart home devices. The devices line maps your Zigbee or Z-Wave USB coordinator into the container. If you don't use USB devices yet, you can omit that line and add it later.

Step 4. Access the Home Assistant Dashboard

Once the container is running, open a web browser and navigate to http://[your-nas-ip]:8123. The Home Assistant onboarding wizard will walk you through creating your admin account, setting your home location (which enables Australian time zone and weather data), and discovering devices on your network. The first boot takes 2-5 minutes as HA initialises its database and downloads core components.

Zigbee and Z-Wave USB Passthrough

If you're using Zigbee devices (Aqara sensors, IKEA TRADFRI, Hue bulbs without the bridge) or Z-Wave devices, you'll need a USB coordinator plugged into your NAS. The most popular options in Australia include the Sonoff ZBDongle-P and SONOFF ZBDongle-E for Zigbee, plus the Aeotec Z-Stick 7 for Z-Wave. Check current retailer prices before buying.

USB passthrough maps the physical USB device on the NAS to the Home Assistant container or VM, so Home Assistant can communicate directly with the coordinator. Without it, HA cannot see the USB stick at all.

How to Pass Through USB on Each NAS Brand

Synology (Docker): SSH into the NAS and run ls /dev/ttyUSB* or ls /dev/ttyACM* to find your USB device. Add it to the Docker Compose file under devices: as shown above. On Synology DSM 7.2+, you can also map devices through the Container Manager GUI under the container's settings. Map the USB device explicitly with --device in the Docker configuration; Home Assistant's own Synology guidance describes this as the least-privileged way to grant USB access, not privileged mode.

QNAP (Docker): Similar process. SSH in, identify the device path, and map it in Container Station. QNAP's Container Station GUI allows adding devices directly when creating or editing a container. USB pass-through also works in Virtualisation Station if running the VM method. Attach the USB device to the VM from the hypervisor settings.

Asustor (Docker): Asustor's Docker implementation supports USB passthrough via the --device flag in the Docker run command or the equivalent Compose setting. Portainer also lets you add devices through the GUI. Asustor generally has fewer restrictions on USB access than Synology, so passthrough tends to be more straightforward.

Remote Access on Australian NBN. The CGNAT Problem

Carrier-Grade NAT (CGNAT) means your provider shares one public IPv4 address between many customers. On a CGNAT connection you cannot open ports on your router to reach Home Assistant from outside your home, because you do not have a dedicated public IPv4 address.

How do you know if you're on CGNAT? Log into your NBN router and check its WAN IP address. If it falls between 100.64.0.0 and 100.127.255.255, you're behind CGNAT: that block is set aside for exactly this use by RFC 6598. You can also compare your router's WAN IP with what whatismyip.com shows; if they differ, something upstream is translating your address. Check the router itself, not a device running Tailscale, because Tailscale hands out addresses from the same 100.x range.

Our Home Assistant remote access guide compares Home Assistant Link, Tailscale, Cloudflare Tunnel and port forwarding, with the first steps and the security checklist for each. For remote access to the NAS itself, see our NAS remote access and VPN guide. The three options that work behind CGNAT, in brief:

Solution 1: Home Assistant Link (Easiest)

Home Assistant Link (formerly Home Assistant Cloud), the official subscription run by Nabu Casa, gives you remote access without opening any ports on your router, so it works behind CGNAT. Setup is a single toggle in the Home Assistant interface, and there is a 31-day free trial. The remote access guide covers the current price and the name change.

Solution 2: Tailscale (Private VPN)

Tailscale is a VPN (an encrypted tunnel to your home network) that works behind CGNAT: connections start through a relay server, then Tailscale tries to connect your devices directly. Install the Tailscale client on your NAS (available as a Synology package, QNAP QPKG, or Docker container) and on your phone. Tailscale's free Personal plan covers unlimited user devices for up to 6 users. Your phone's sensors only update in Home Assistant while the VPN is connected.

Solution 3: Cloudflare Tunnel (Your Own Domain)

Cloudflare Tunnel makes an outbound-only connection from the cloudflared container on your NAS to Cloudflare, so it needs no open ports and works behind CGNAT. You need a domain name that uses Cloudflare for DNS, which has a yearly fee from your registrar. In return you get a normal HTTPS address on your own domain (e.g., ha.yourdomain.com.au).

Power Consumption Considerations

A NAS running Home Assistant draws power 24/7, so electricity cost matters. Running cost depends on your electricity rate, which varies by state and retailer. The good news is that modern NAS units are surprisingly efficient.

A 2-bay NAS like the Synology DS225+ draws roughly 15-20 watts under typical Home Assistant load with two hard drives. A 4-bay model draws more again, and a Raspberry Pi 4 draws far less than either. Estimate annual running cost by multiplying measured power draw by hours of use and your electricity rate, or use our power calculator. The NAS costs more to run, but you're getting vastly more capability. For detailed measurements, see our NAS power consumption guide.

If power consumption is a primary concern, consider running your NAS drives in hibernate mode during off-peak hours. Home Assistant's Recorder writes state and event data to its database continuously (every 5 seconds by default), so hard drives won't fully hibernate unless the database itself is moved to SSD-backed storage and Recorder's commit interval is tuned. Some users install an M.2 NVMe SSD for the Home Assistant database and let the hard drives sleep most of the time.

Additional Containers to Run Alongside Home Assistant

One of the biggest advantages of running Home Assistant on a NAS via Docker is the ability to run complementary containers on the same hardware. These are the most common additions for Australian smart home setups:

Zigbee2MQTT. Bridges Zigbee devices to Home Assistant via MQTT without vendor-specific hubs. Supports hundreds of devices from Aqara, IKEA, Sonoff, Tuya, and others. Runs as a lightweight Docker container and requires a Zigbee USB coordinator.

Mosquitto (MQTT Broker). The message broker that Zigbee2MQTT and many other integrations communicate through. Essential if you're using any MQTT-based devices or services. Uses minimal resources.

Node-RED. A visual flow-based automation tool that integrates with Home Assistant. Many users prefer Node-RED's drag-and-drop interface for complex automations over Home Assistant's native YAML-based system. Runs comfortably alongside HA on any x86 NAS.

ESPHome. Lets you flash and manage custom firmware on ESP32/ESP8266 devices. Compiles firmware directly on the NAS. ESPHome's official container supports amd64, ARM, and ARM64 (aarch64), so this is not strictly an x86-only capability.

Tailscale or Cloudflared. Running either as a container on the NAS gives you remote access behind CGNAT without any configuration on your router; our Home Assistant remote access guide explains which one fits.

Backup and Recovery

Running Home Assistant on a NAS gives you proper backup infrastructure that a Raspberry Pi setup simply cannot match. Your Home Assistant configuration directory sits on a RAID-protected volume, and the NAS can snapshot or back it up to external storage, another NAS, or a cloud service automatically.

Recommended backup approach: Schedule a daily cron job or NAS task that copies the Home Assistant configuration directory to a separate shared folder. On Synology, use Hyper Backup to back up the docker/homeassistant folder to Backblaze B2 or an external USB drive. On QNAP, use Hybrid Backup Sync. Keep at least 7 days of snapshots. Backup size depends heavily on the Recorder database, which can grow to several gigabytes without purge settings configured, so check your actual backup size rather than assuming it stays small.

If you're running the VM method with Home Assistant OS, the built-in Supervisor handles snapshots natively. You can schedule full snapshots from within the Home Assistant UI and store them on the NAS shared folder, which then gets backed up through your normal 3-2-1 backup strategy.

Common Issues and Troubleshooting

Container won't start after NAS update: NAS firmware updates (DSM, QTS, ADM) occasionally break Docker networking or change kernel modules. After a major NAS update, check that the Docker service is running and recreate the container if needed. Keep your Docker Compose file stored outside the container so you can redeploy quickly.

Zigbee devices stop responding: Almost always a USB device path change after reboot. Use /dev/serial/by-id/ paths instead of /dev/ttyUSB0. If using Zigbee2MQTT, update the serial port path in its configuration.yaml.

Home Assistant is slow to load: Check if your NAS is running low on RAM. Home Assistant's database (home-assistant_v2.db) grows over time and can become several gigabytes if you haven't configured recorder settings. Add purge_keep_days: 7 to your recorder configuration to limit database size. Also ensure you're not running the HA database on a hard drive. Move it to an M.2 SSD cache if your NAS supports it.

mDNS discovery not working: If Home Assistant can't find Chromecast, Sonos, or other network devices, confirm the container is running in network_mode: host. Bridge mode networking blocks multicast traffic, which breaks mDNS/SSDP discovery. On QNAP, also check that the "Network & Virtual Switch" settings aren't filtering multicast.

Australian Consumer Law and NAS Purchases

Where you buy matters for a NAS because it is an always-on device storing irreplaceable data. Your first step for a faulty product is usually the retailer that sold it. The ACCC explains your rights under the Australian Consumer Law at accc.gov.au. Grey imports from overseas marketplaces are cheaper, but the manufacturer's Australian warranty may not cover them, and dealing with an overseas seller can be harder in practice. NAS warranty and returns in Australia lists each maker's published warranty length and who to contact first.

Related reading: our NAS buyer's guide and our NAS explainer.

Use our free NAS Sizing Wizard to work out how many bays and what size drives you need.

Related reading: our Home Assistant Docker NAS setup guide, our Portainer and Docker Compose on NAS, and our Vaultwarden password manager on NAS.

Related reading: our self-hosted note sync guide 2026.

Related reading: our self-hosted note sync guide 2026.

See also: our complete Synology NAS Australia guide.

See also: our complete QNAP NAS Australia guide.

See also: our complete Asustor NAS Australia guide.

Related reading: our Home Assistant Docker NAS setup guide and our self-hosted note sync guide 2026.

Related reading: our UGREEN HomeAgent Matter hub launch and our self-hosted note sync guide 2026.

Home Assistant will happily keep talking to a device long after its manufacturer stops updating it. Australia's smart device security rules require in-scope products to publish the date security updates end, which is worth recording for each device you pair to this installation rather than discovering later.

Related reading: our self-hosted note sync guide 2026.

Related reading: our self-hosted note sync guide 2026.

Can I run Home Assistant on a Synology NAS with an ARM processor?

Technically yes, but it's not recommended. ARM-based Synology models (DS124, DS223, DS423) use 64-bit ARM (aarch64) Realtek chips, which Home Assistant officially supports alongside amd64. Compatibility issues, where they exist, come down to specific third-party integrations rather than the CPU architecture itself. The DS225+ (about $599) is the entry point for a trouble-free Home Assistant experience on Synology.

How much RAM does Home Assistant need on a NAS?

Home Assistant Container uses roughly 256-512 MB of RAM in typical operation. However, if you're running additional containers (Zigbee2MQTT, Mosquitto, Node-RED, Plex), total RAM usage climbs quickly. A NAS with 2 GB of RAM can technically run HA alone, but 4 GB is the practical minimum for a comfortable smart home stack, and 8 GB gives you room to grow. The QNAP TS-264 (about $1,014) ships with 8 GB, making it a strong choice without requiring a RAM upgrade.

Does Home Assistant work behind NBN CGNAT?

Home Assistant works fine on your local network regardless of CGNAT. The problem is remote access when controlling your home from outside your network. CGNAT blocks inbound connections, so standard port forwarding does not work. Use Home Assistant Link (formerly Home Assistant Cloud, a paid subscription from Nabu Casa), Tailscale (free VPN), or Cloudflare Tunnel (requires a domain) to access Home Assistant remotely on CGNAT connections; our Home Assistant remote access guide compares them. Some RSPs, such as Aussie Broadband, offer static IP add-ons that eliminate CGNAT entirely; check the provider's current pricing.

Can I use a Zigbee USB stick with a NAS running Home Assistant?

Yes. Plug a Zigbee coordinator, such as the Sonoff ZBDongle-P or ZBDongle-E, into a USB port on the NAS and map the device path into the Home Assistant container. Use /dev/serial/by-id/ paths for reliability rather than /dev/ttyUSB0, which can change on reboot. USB passthrough works on Synology, QNAP, and Asustor by mapping the device explicitly into the container; Synology's own Home Assistant guidance uses --device mapping as the least-privileged method, not privileged container mode.

Is it better to use Docker or a VM for Home Assistant on a NAS?

Docker (Home Assistant Container) is lighter, faster, and simpler for experienced users. It uses less RAM and starts in seconds. The VM method (Home Assistant OS) gives you the full add-on store and Supervisor for automatic backups and updates, but requires at least 2 GB of dedicated RAM and a NAS that supports virtualisation. For most NAS users, Docker is the better fit because it leaves more resources for other NAS tasks. Choose the VM if you specifically need the add-on store or prefer the guided Home Assistant experience.

How much does it cost to run a NAS with Home Assistant 24/7 in Australia?

A 2-bay NAS like the Synology DS225+ draws 15-20 watts under typical load. A 4-bay model draws more again, and a Raspberry Pi 4 draws far less than either. A NAS costs more to run than a Raspberry Pi, but you get file storage, backups, media serving, and Docker hosting on the same hardware. Estimate annual running cost by multiplying measured power draw by hours of use and your electricity rate, or use our power calculator. The incremental cost of running Home Assistant on an existing NAS is essentially zero. It adds minimal load to hardware that's already running.

Which is the cheapest x86 NAS that runs Home Assistant in Australia?

Among the models compared above, the TerraMaster F2-425 starts at $499 from MSY, Scorptec or UMart and supports Docker for Home Assistant. It has an Intel Celeron N5095 and 4 GB of RAM. However, TerraMaster's software ecosystem is less mature than Synology or QNAP, and community support for Home Assistant on TerraMaster is limited. A step up is the Synology DS225+ (about $599), which costs more but has far better software, community documentation, and long-term update support.