Yes—Proxmox Is Not the Problem by Itself

Matter and Thread can work reliably with Home Assistant in Proxmox. Home Assistant officially provides a KVM/Proxmox image for Home Assistant OS, often shortened to HAOS. A virtual machine, or VM, simply lets Home Assistant run as a complete computer inside the Proxmox host. The important part is making that virtual computer look like an ordinary device on your home network.

Use a bridged network connection so the HAOS VM gets its own local address and can exchange IPv6 and the device-finding traffic used on the home network. For Matter-over-Thread, also give Home Assistant a dependable path to a Thread border router—the hub that links the Thread mesh to the normal home network. Either pass a dedicated USB Thread radio into the VM and run Home Assistant's OpenThread Border Router app, or use a compatible border router that already lives on that network.

Matter control remains local. Proxmox does not turn it into a cloud system. The first things to check are an extra network layer that stops devices seeing one another, disabled local IPv6, missing Thread network details on the setup phone, and an unstable USB-radio path—not virtualization alone.

Four Pieces That Are Easy to Mix Up

  • Proxmox host: the physical mini PC or server that runs the VM. Its network bridge and USB hardware sit underneath Home Assistant.
  • Home Assistant OS VM: the supported Home Assistant appliance. It runs Home Assistant Core plus managed apps such as Matter Server and OpenThread Border Router.
  • Matter controller: Home Assistant plus Matter Server. It commissions devices and sends local Matter commands over IPv6.
  • Thread border router: the bridge between the low-power Thread mesh and the normal Ethernet or Wi-Fi home network. It is needed only for Matter-over-Thread devices.

A Thread border router is not the same thing as a Matter controller. A HomePod mini can provide the Thread radio path while Home Assistant controls the device. A Home Assistant Connect ZBT-2 can also provide that path without adding Apple, Google, or SmartThings as a controller, but it ships in Zigbee mode. Dedicate the radio to Thread and follow Home Assistant's official enable-Thread steps before using the OpenThread Border Router app.

Which Proxmox Setup Should You Choose?

Setup path and current examples Official support Local control and cloud dependency Matter, Apple Home, and other platforms Community caveat
HAOS VM plus a passed-through Thread radio
Home Assistant Connect ZBT-2, or ZBT-1 for existing owners, with the official OpenThread Border Router app		 Home Assistant's recommended OS path supports the official Matter Server and OpenThread Border Router apps. Its Thread documentation lists ZBT-2 and ZBT-1, while describing the Home Assistant border-router integration with Matter as work in progress. Matter commands and Thread routing stay local. No Apple, Google, or Samsung account is required. Remote Home Assistant access is a separate, optional choice. Pair devices to Home Assistant directly. Share them later through Matter multi-admin, or expose selected Home Assistant entities to Apple Home with HomeKit Bridge. ZBT-2 and ZBT-1 start in Zigbee mode. Follow the official enable-Thread flow and dedicate this radio to Thread rather than trying to run Zigbee and Thread on it here. USB passthrough also binds the VM to that physical host.
HAOS VM plus an external Thread border router
Apple HomePod mini, HomePod (2nd gen), or Apple TV 4K (3rd gen, Wi-Fi + Ethernet); Google Nest Hub (2nd gen), Nest Wifi Pro, or Google TV Streamer (4K)		 Home Assistant supports compatible third-party Thread border routers. Apple and Google document these models as Thread border routers for their own platforms. Home Assistant's Matter commands remain local. The external platform may require an account for setup, credential sharing, remote control, updates, or its own automations. The border-router role does not force Apple Home or Google Home to control the device. Add those platforms separately through Matter multi-admin or use HomeKit Bridge for Apple. The setup phone must hold the right Thread network details, and all pieces need local IPv6 reachability. Several border routers can help only when they belong to the intended Thread network.
HAOS VM plus SmartThings infrastructure
SmartThings 2018 Hub or Aeotec Smart Home Hub, with a compatible Thread border router where required		 SmartThings documents both hubs as Matter controllers. Its support page says older models without Thread need a separate compatible border router. Home Assistant Matter control stays local. SmartThings setup, remote features, and its own automations use the SmartThings app and services. Share the same Matter device between Home Assistant and SmartThings with a new multi-admin code. Do not reuse the printed factory code after first pairing. Model capabilities differ: being a Matter controller does not guarantee a built-in Thread radio. Check the exact hub before relying on it as the border router.
Matter-over-Wi-Fi or Ethernet only
No Thread radio or Thread border router		 The official Matter Server app supports Matter devices on the regular IP network. Thread is not required for Wi-Fi or Ethernet Matter devices. Routine control is local. A vendor account may still be needed for firmware, optional features, or first-party remote access. Matter multi-admin and HomeKit Bridge choices are the same as above. The transport is Wi-Fi or Ethernet instead of Thread. Local IPv6 and device-discovery traffic still matter. Skipping Thread hardware does not make a VM hidden behind a second virtual router or an isolated network a safe design.
Home Assistant Container plus separate Matter or OTBR containers Home Assistant calls a separately managed Matter Server an unsupported path. Container installs also lack the out-of-box app experience of HAOS. It can remain local, but every container network, IPv6 route, multicast boundary, permission, and update becomes the homeowner's responsibility. Standard Matter sharing can still work after a correct build. HomeKit Bridge remains a separate Home Assistant integration. Choose only when you already operate IPv6-aware containers and accept manual recovery. It is a poor first fix for a VM that merely needs a bridge or working IPv6.
  1. Start with Home Assistant OS. Download the official KVM/Proxmox-compatible disk image. Home Assistant lists 2 GB RAM and two virtual CPUs as the minimum; give a busy installation more headroom.
  2. Use the wired Proxmox bridge. Connect the host by Ethernet and attach the VM to the normal LAN bridge, commonly named vmbr0. The goal is for Home Assistant to appear directly on the same home network as the phone and border router.
  3. Finish HAOS and take a backup. Confirm ordinary integrations and local access work before adding Matter. Keep the Proxmox console available in case a network change removes browser access.
  4. Install the official Matter Server app. Add the Matter integration through Home Assistant and follow its supported app flow. Do not substitute an arbitrary Docker image just because Proxmox can run one.
  5. Set local IPv6 to Automatic. In Settings > System > Network, select the active adapter and use Automatic for IPv6. This does not require your internet provider to offer IPv6.
  6. Add Thread only if the device needs it. For a local Home Assistant border router, pass a dedicated USB radio to the HAOS VM, follow Home Assistant's official procedure to enable Thread on that exact adapter, and install the OpenThread Border Router app. Do not reuse that radio for Zigbee in this design. For an existing external border router, confirm it is on the same home network and import or use the correct Thread network details during setup.
  7. Pair one non-critical device first. A plug, lamp, or contact sensor is a safer test than a lock, alarm, garage door, or thermostat. Save its Matter setup code before doing anything else.

Do not change Proxmox host networking from a remote-only session without a recovery path. A bridge or IPv6 mistake can disconnect every VM and the host itself. Keep a local console, a current backup, and the original configuration before making one change at a time.

What to Check on the Proxmox Network

Proxmox's Linux bridge acts like a virtual Ethernet switch. That is what you want: the HAOS VM should sit on the household LAN, not behind a second NAT router created only for the VM. A wired host connection is the simplest choice because bridging through Wi-Fi clients can add platform and access-point limits.

Matter uses IPv6 locally even when the rest of the household thinks in IPv4. Home Assistant explicitly says DHCPv6 and public internet IPv6 are not required. Matter devices still need local IPv6 addresses that work across the Proxmox bridge between Matter Server, the border router, and the device.

Recent Proxmox community cases have traced failed commissioning to IPv6 being disabled on the host or bridge. Treat that as a diagnostic clue, not as a universal command to paste. Inspect the Proxmox host, the bridge, any VLAN firewall, and HAOS together. If one layer drops IPv6 or multicast discovery, changing a setting only inside Home Assistant will not repair the full path.

A safe network checklist

  • Does the HAOS VM have its own LAN address on the same ordinary network as the setup phone and border router?
  • Is IPv6 set to Automatic on the active Home Assistant adapter?
  • Has IPv6 been disabled globally on the Proxmox host or on the bridge?
  • Do VLAN, guest-network, or firewall rules block IPv6, multicast DNS, or traffic between the VM and border router?
  • Can the phone remain on the intended home Wi-Fi during commissioning, with Bluetooth enabled for the first setup exchange?

If a Matter Server log line says Network is unreachable while trying to send to an IPv6 address, that attempt had no working IPv6 route. A user-filed Matter Server issue shows this exact symptom, but other messages and pairing failures can have different causes. Save diagnostics before changing the network.

Make USB Passthrough Boring and Stable

When Home Assistant runs its own Thread border router, the clean arrangement is a dedicated Thread radio physically connected to the Proxmox host and passed through to the HAOS VM. Bind it by a stable physical port when identical USB devices share the same vendor and product ID. A short extension cable also moves the radio away from the computer's metal case and USB 3 interference.

Proxmox documents an important tradeoff: USB passthrough prevents online migration because the hardware belongs to one host. That is acceptable for many homes, but write it into the recovery plan. Shut down the VM, reconnect or reassign the radio on the destination host, and verify Thread before moving critical automations.

Do not confuse an external Thread border router with a raw radio sent over TCP/IP. Home Assistant's OpenThread Border Router documentation warns that running the radio coprocessor across a network is timing-sensitive and can leave stale routes after a failure. Put the OTBR service beside the physical radio. If the radio needs to live elsewhere, use a complete, supported border router on the LAN.

Troubleshoot in This Order

  1. Name the transport. Check whether the device is Matter-over-Wi-Fi, Matter-over-Ethernet, or Matter-over-Thread. A Thread fix cannot help a Wi-Fi device.
  2. Confirm the supported services are healthy. Update Home Assistant, Matter Server, and OpenThread Border Router where used. Check their logs and download Matter diagnostics before a reset.
  3. Verify the VM bridge. Make sure HAOS is directly reachable on the home LAN and not hidden behind a container-only bridge, NAT layer, or isolated guest network.
  4. Verify local IPv6 end to end. Check HAOS, the Proxmox bridge and host, and any VLAN firewall. Do not stop after seeing one IPv6 address on one screen.
  5. Check the Thread network details and border routers. The setup phone must know the intended Thread network. Confirm the border router is online and that Home Assistant is not steering the device toward a second accidental Thread network.
  6. Check the physical radio path. Confirm USB passthrough still points to the correct VM and that the OTBR app sees the radio. Avoid hubs, network-forwarded serial links, and loose ports while testing.
  7. Remove network isolation for one controlled test. Temporarily place the phone, HAOS VM, and border router on one trusted LAN only if you understand the firewall change and can restore it. This is a diagnosis, not a permanent reason to abandon segmentation.
  8. Reset last. Reboot the relevant service or device after saving evidence. Factory-reset only when the network path is proven and the permanent Matter code is safely stored.

A device working in Apple Home, Google Home, or its vendor app does not prove that the HAOS VM can reach it. That other controller may have a different IPv6 path, different Thread network details, or its own Matter pairing. Test each role separately.

What Stays Local, and What Can Still Use the Cloud?

Home Assistant's routine Matter commands are local. Matter Server talks to devices over the LAN, and a Thread border router routes packets locally between Thread and that LAN. Neither Proxmox nor Thread requires a cloud relay for a light switch or sensor update.

Cloud services can still appear around that local core. A vendor may require its app or account for firmware and device-only features. Apple Home, Google Home, Alexa, and SmartThings use their own accounts for household sharing, voice processing, remote access, or platform automations. Home Assistant remote access is also a separate choice, whether through Home Assistant Cloud or a user-managed VPN.

For Apple Home, choose one of two clear paths. Matter multi-admin gives Apple and Home Assistant separate direct Matter control of the same device. HomeKit Bridge publishes the Home Assistant entity to Apple, so Apple sends control through Home Assistant. Neither choice determines which Thread border router carries the packets, and automations do not copy between platforms.

What to Avoid

  • Do not assume the VM needs its own Thread radio. Matter-over-Wi-Fi does not use Thread, and an existing compatible border router can serve Matter-over-Thread.
  • Do not disable IPv6 because your internet service is IPv4-only. Matter still needs local IPv6.
  • Do not build the first installation from separate Matter, OTBR, and Home Assistant containers. It creates more IPv6 and multicast boundaries than a supported HAOS VM.
  • Do not forward a raw Thread radio over an unreliable network. Pass it directly to HAOS or use a full external border router.
  • Do not create the same automation in Home Assistant, Apple Home, Google Home, Alexa, and SmartThings. Multi-admin shares device control, not one shared automation brain.
  • Do not test the design first on a lock, alarm, garage door, or essential thermostat. Keep a physical fallback and prove the network with a non-critical device.

Tara's Practical Recommendation

For most Proxmox homes, use Home Assistant OS as one bridged VM and keep Matter Server inside that supported appliance. If the home already has a healthy Apple or Google Thread network, try that compatible external border-router path before adding another radio. If Home Assistant should own the Thread network, pass a dedicated Connect ZBT-2 or ZBT-1 directly into the VM, follow the official enable-Thread procedure for that adapter, and run the official OTBR app. Home Assistant still describes this border-router integration with Matter as work in progress.

Whichever route you choose, document four things: the VM bridge, the local IPv6 setting, where the Thread network details live, and whether a USB radio ties the VM to one host. That small diagram is far more useful than factory-resetting devices whenever commissioning hangs.

Frequently Asked Questions

Can Home Assistant Matter work in a Proxmox VM?

Yes. Home Assistant OS in a Proxmox VM is a supported installation path. Use the official Matter Server app, give the VM a bridged LAN connection, and keep local IPv6 working between Home Assistant, the Matter device, and any Thread border router.

Does Matter need internet IPv6?

No. Home Assistant says internet IPv6 and DHCPv6 are not required. Matter does require IPv6 on the local network, so disabling it on the HAOS VM, Proxmox bridge, or host can break commissioning and control.

Does the Home Assistant VM need a USB Thread radio?

Only if Home Assistant will run its own OpenThread Border Router. Matter-over-Wi-Fi needs no Thread radio, and Matter-over-Thread can instead use a compatible external Thread border router on the same local network.

Can Home Assistant use an Apple or Google Thread border router from a VM?

Yes. A compatible Apple or Google Thread border router can provide the radio path while Home Assistant remains the Matter controller. The VM must reach it over the local IPv6 network, and the phone used for setup must have the correct Thread network details.

Can a VM with USB passthrough move to another Proxmox host?

Not while it is running with that physical radio attached. Proxmox documents that USB passthrough prevents online migration. Shut down the VM, reconnect or reassign the radio on the new host, and verify Thread before relying on it again.