Quick Summary (TL;DR): For a single Proxmox mini PCPriceAliExpress price running Home Assistant OS, a dedicated USB Zigbee coordinatorPriceAliExpress price passed through to the VM is usually the simplest, least expensive architecture. Choose a wired Ethernet/PoE Zigbee coordinatorPriceAliExpress price when radio placement is poor, the server lives in a metal rack, or you intend to move the Home Assistant VM between Proxmox hosts. Keep the network connection local, stable and preferably wired: Zigbee serial-over-IP is not tolerant of Wi-Fi, WAN or VPN dropouts. Thread is different: a genuine Ethernet/Wi-Fi Thread border router is an IP router for the Thread mesh; it is not interchangeable with a Zigbee serial-to-TCP adapter. If you already have a compatible Apple or Google Thread border router, you may not need a separate Thread USB radio at all. For a new USB installation, Home Assistant Connect ZBT-2 is a well-supported option, but each unit runs either Zigbee or Thread, not both simultaneously. Buy the architecture that meets your placement, recovery and networking needs, not whichever device claims the longest range.
The decision in one table
| Your setup | Better starting point | Reason / caveat |
|---|---|---|
| One Proxmox host, HAOS VM, radio can sit near the server | USB coordinator + extension cable | Direct serial connection, straightforward firmware and backup workflow; ties the VM to that host. |
| Proxmox server in garage, loft or metal cabinet | Wired Ethernet/PoE Zigbee coordinator | Place the antenna centrally without relocating the compute host; allow a stable local TCP path. |
| Several Proxmox nodes with VM recovery or planned migration | Wired network Zigbee coordinator | No host USB mapping to recreate, but coordinator state, LAN access and service startup still matter. |
| Already own a working Apple/Google Thread border router | Use existing Thread infrastructure first | Check Home Assistant discovery, credentials and Matter IPv6 requirements before buying another radio. |
| Need Zigbee and Home Assistant-managed Thread | Two dedicated radios or verified two-radio appliance | A single ZBT-2 cannot do both at once; dual-radio products must actually contain two independent 802.15.4 radios. |
| Home network frequently loses power or has unreliable Wi-Fi | USB or wired Ethernet with backed-up power | Do not run a coordinator through unreliable wireless serial forwarding. |
This is a buying and architecture guide, not a second USB mapping tutorial. If you have already chosen a USB adapter, follow our existing Home Assistant on Proxmox: Zigbee and Thread USB Passthrough guide for the Proxmox Hardware → Add → USB Device workflow, persistent paths and OpenThread setup.
First separate three very different pieces of hardware
1. A USB Zigbee coordinator
A USB Zigbee coordinator is a radio with coordinator firmware that presents a local serial interface. Home Assistant ZHA or Zigbee2MQTT communicates with that interface. With Home Assistant OS running in a Proxmox VM, Proxmox must give the guest access to the physical USB device. Once configured, the Zigbee mesh itself is independent of the VM: battery devices and mains-powered Zigbee routers communicate over 2.4 GHz, while the coordinator provides the gateway into your automation stack.
A USB extension lead is not a cosmetic accessory. It can move the antenna away from USB 3.x electrical noise, metal enclosures and crowded ports. The extension does not make the radio magically more powerful; it improves placement. If the server is in a rack at one end of the property, a short lead may still leave the coordinator in a poor RF location.
2. A network-attached Zigbee coordinator
Many Ethernet/PoE Zigbee adapters still expose the same serial coordinator protocol, but transport it across the LAN using a TCP socket. In other words, they are not automatically a full Zigbee hub with its own device automation engine. Your ZHA or Zigbee2MQTT instance remains the controller, and it still needs a continuous connection to the radio. The benefit is physical separation: a Cat6 cable can place the coordinator in a hallway or upstairs without moving the Proxmox machine.
For example, the SMLIGHT SLZB-06 family includes wired Ethernet, USB and IEEE 802.3af PoE options. The SLZB-06 uses a Texas Instruments CC2652P radio, while the SLZB-06M uses a Silicon Labs EFR32MG21. Those are not identical firmware families; the correct Zigbee2MQTT driver depends on the radio firmware, not on the fact that both boxes have Ethernet. Manufacturer descriptions of Zigbee, Thread and multiprotocol support must be checked against the exact model and current firmware.
3. A Thread border router
Thread is not Zigbee over TCP. Thread is an IPv6-based mesh network. A Thread border router joins that mesh to the normal IP LAN; Matter is one application protocol that can use Thread. Home Assistant can use a compatible third-party border router on the LAN, or it can run its own OpenThread Border Router service with a suitable dedicated radio. A product labelled “Thread-capable Ethernet coordinator” is not automatically a working, independently managed Thread border router: verify its border-router software, commissioning method, firmware mode and Home Assistant integration.
The distinction matters most on Proxmox. An Apple HomePod mini or supported Apple TV / Google Nest device can provide Thread border routing over the home network without passing a USB Thread radio into the VM. A bare network serial radio configured for Thread RCP mode may still need a separate OpenThread Border Router host process and a specifically supported connection method. Never assume that entering a Zigbee tcp:// endpoint into Home Assistant makes it a Thread border router.
USB passthrough versus Ethernet/PoE: what actually changes?
| Criterion | USB radio passed to HAOS VM | Wired Ethernet/PoE coordinator |
|---|---|---|
| Physical placement | Limited by USB cable and host position | Can be installed wherever there is a suitable LAN/PoE drop |
| Proxmox host dependence | Device bound to physical node or mapped USB port | VM can reach same radio from another node if network/routing remain available |
| Zigbee serial path | Local USB virtual device | TCP socket over LAN; extra switch, IP and cabling dependencies |
| Power | Usually powered by host USB | PoE switch/injector or compatible USB supply; verify included accessories |
| Firmware management | USB flash/update method depends on device | Often web UI or vendor updater, but check model and firmware |
| RF interference | Extension cable and placement needed | Remote mounting can reduce proximity to server electronics |
| Network security | No radio management service exposed on LAN | Protect web admin, serial TCP port and update mechanism |
| Failure modes | USB disconnects, host reboot, VM mapping | LAN/PoE outage, IP changes, serial socket drops |
| Thread suitability | Dedicated USB RCP with HAOS OpenThread Border Router | Only if product really implements or supports a Thread border-router architecture |
| Typical buying priority | Simplicity and low initial cost | Location flexibility and VM mobility |
A network coordinator is not inherently more reliable or faster. A short, stable USB connection can be excellent. Ethernet adds freedom of placement but also adds a switch, power and TCP dependency. The main reason to choose network-attached hardware is architecture, not a claim of superior Zigbee packet throughput.
Specific hardware worth evaluating in 2026
| Device / family | Verified radio and connection | Best reason to shortlist | Important limitation |
|---|---|---|---|
| Home Assistant Connect ZBT-2 | Silicon Labs MG24 radio; ESP32-S3 USB bridge; USB-C; Zigbee or Thread | Official HA setup, ZHA/OTBR support and a physically separated antenna base | USB only; one protocol at a time; not a stand-alone Ethernet Thread border router |
| SMLIGHT SLZB-06 | TI CC2652P; Ethernet / USB / PoE (802.3af) | Network Zigbee with TI Z-Stack firmware; flexible placement | Check exact firmware, LAN mode and supported stack; Thread features need separate validation |
| SMLIGHT SLZB-06M | Silicon Labs EFR32MG21; Ethernet / USB / PoE (802.3af) | Network Zigbee using Silicon Labs Ember firmware | Different driver/firmware from SLZB-06; wired LAN preferred to Wi-Fi serial forwarding |
| SMLIGHT SLZB-MR series | Selected models contain two independent Zigbee/Thread-capable radio SoCs plus Ethernet/PoE | Potentially one enclosure for distinct Zigbee and Thread radios | Confirm exact MR model, independent firmware modes and supported OTBR integration before purchase |
| Existing Apple / Google Thread border router | Vendor-managed Thread border router over home LAN | No extra HA USB radio required for compatible Matter-over-Thread deployments | Credential sharing, mDNS, IPv6 and supported device combinations still matter |
The SMLIGHT model names are easy to confuse. In particular, “06” and “06M” do not share the same radio chip; “MR” denotes a different, multi-radio family. The manufacturer publishes a model comparison, and Zigbee2MQTT maintains separate Z-Stack and Ember adapter guidance. Use the exact model and firmware revision, not a retailer’s generic “Zigbee/Thread/PoE” badge.
The official ZBT-2 product page lists a recommended MSRP of €45 in the EU, with regional variation. This is an official reference price, not a live retailer quote. Its USB-C power/data specification is 5 V, 500 mA, which is a supply requirement, not a measured 24/7 energy-consumption figure. The manufacturer explicitly rules out simultaneous Zigbee and Thread on one ZBT-2.
ZHA or Zigbee2MQTT: does the software change the purchase?
Yes. Choose the Zigbee application before ordering hardware. ZHA is built into Home Assistant and supports compatible serial Zigbee coordinators, including documented socket-based devices. Zigbee2MQTT runs as a separate service and talks to Home Assistant through MQTT; its adapter list, driver selection and firmware expectations are specific. An adapter that works with one stack or firmware version is not automatically the best choice for the other.
| Software / mode | USB option | Network option | Check before ordering |
|---|---|---|---|
| ZHA | Supported serial USB coordinator | Supported local socket coordinator, for example compatible socket:// radio | Zigpy radio family, firmware, supported socket transport, stable LAN |
| Zigbee2MQTT | USB serial path, preferably /dev/serial/by-id/… | Documented tcp://host:port adapter | Adapter type zstack or ember, coordinator firmware and TCP endpoint |
| Home Assistant-managed Thread | Dedicated USB Thread RCP + OTBR app | Only a supported remote RCP/OTBR design, not a Zigbee TCP socket | Firmware mode, OTBR service, HAOS app support and network credentials |
| Third-party Thread border router | No HA USB radio necessary | Supported Apple/Google/other TBR on LAN | IPv6, mDNS, preferred Thread network and credential sharing |
Zigbee2MQTT documents serial.port: tcp://192.168.1.12:6638 as an example format, not a universal port for every product. Confirm the actual TCP port from the adapter’s management interface. Its current Silicon Labs guidance uses adapter: ember; the older ezsp setting is deprecated. The TI family uses adapter: zstack. A device may be shipped with router firmware rather than coordinator firmware, so check that too.
# Example Zigbee2MQTT serial configuration for a compatible
# wired Silicon Labs Ember coordinator. Illustrative values only.
serial:
port: tcp://192.168.10.25:6638
adapter: ember
# For a compatible TI Z-Stack coordinator, use:
# serial:
# port: tcp://192.168.10.25:6638
# adapter: zstack
Do not paste both configurations into one file. The IP address and port above are examples, not a discovered device or a recommended exposed service. Zigbee2MQTT also advises giving a network adapter a stable address. A DHCP reservation is normally easier to maintain than an undocumented static address, provided your DHCP service is dependable.
Why Proxmox VM mobility is the strongest argument for network Zigbee
Proxmox USB passthrough gives a guest direct access to hardware on a particular node. That is excellent for a one-host home lab but creates a portability constraint. If you migrate or restore the Home Assistant VM onto a different Proxmox node, its configured USB radio may not be physically present. You must move the adapter, provide an equivalent mapped device or change the design. Live migration of a guest that relies on local host USB passthrough is not a general-purpose solution.
A wired Ethernet coordinator has a fixed network identity independent of which Proxmox node runs HAOS. This makes planned maintenance and VM recovery easier, assuming the new node’s network can reach the coordinator. It does not make Zigbee2MQTT or ZHA active-active, and it does not make two Home Assistant instances safe to connect to the same coordinator simultaneously. Only one controller should own a given coordinator and its Zigbee network at a time.
The reliability chain also changes. With USB, the radio generally reboots with the host. With PoE, the radio may remain powered while the VM restarts, which can be convenient. But a switch reboot, DHCP change, network isolation rule or TCP timeout can still interrupt the Zigbee controller. Build and test your recovery procedure rather than assuming “Ethernet” automatically means “high availability”.
Thread over the network: the easy path and the trap
For Thread, the easiest network design is often to use a complete Thread border router that already participates in your home LAN. Home Assistant discovers Thread border routers via local service announcements and can use compatible existing Thread networks. The Thread integration manages network information and credentials; Matter-over-Thread commissioning also needs a functioning Matter controller and correct IPv6 connectivity.
This is different from buying a single-radio Ethernet Zigbee coordinator and flashing “Thread” firmware. Such hardware may become a Thread radio co-processor rather than a self-contained border router. Whether it can be used remotely depends on where OpenThread Border Router runs, how it connects to the RCP, whether the manufacturer provides a working OTBR service and how that service integrates with Home Assistant. A web page listing “Thread support” is insufficient evidence of plug-and-play compatibility.
If you already own a HomePod mini, compatible Apple TV 4K, Nest Hub or Nest Wifi Pro, first open Home Assistant → Settings → Devices & services → Thread and inspect discovered networks. The presence of a border router does not guarantee that Home Assistant has the network credentials or that your phone will commission devices onto the intended mesh. Home Assistant’s documentation describes importing credentials and selecting a preferred network; follow those instructions rather than resetting a functioning Thread network unnecessarily.
For a Home Assistant-managed Thread network using ZBT-2, the normal supported route is to dedicate the USB radio to Thread and run the OpenThread Border Router app inside HAOS. This can work in a Proxmox VM with USB passthrough, but it remains physically tied to the host. A third-party Thread border router avoids that particular USB dependency; it introduces the usual LAN discovery and IPv6 requirements instead.
Network placement, PoE and interference: where the real gains are
Zigbee and Thread use IEEE 802.15.4 in the 2.4 GHz band. Moving a coordinator from the rear USB port of a metal mini PC to a clear central location may help more than upgrading the radio chip. Use the shortest practical reliable USB extension for a USB adapter, or a wired PoE drop for a network coordinator. Keep the antenna away from a metal rack, Wi-Fi access point and high-speed USB peripherals. Do not hide a PoE adapter inside a metal structured-wiring box just because Ethernet reaches it.
PoE is particularly attractive when the ideal radio location has an Ethernet socket but no convenient mains supply. Confirm IEEE 802.3af compatibility for the chosen device, the PoE switch’s available per-port and total budget, and whether a power injector is needed. “PoE compatible” does not necessarily mean the retail box contains an injector. If your switch already has spare compatible PoE ports, the extra infrastructure cost may be small; otherwise include the cost of the injector or switch upgrade.
More transmit power is not automatically better. End devices have their own transmit power and antenna limitations, and a mesh depends heavily on reliable mains-powered Zigbee routers. For an existing weak mesh, diagnose coordinator placement, 2.4 GHz Wi-Fi overlap, router distribution and problem devices before assuming a higher-gain network coordinator will cure every dropout.
Keep network Zigbee on a reliable local LAN
- Prefer wired Ethernet. Both ZHA and Zigbee2MQTT warn against Zigbee serial forwarding over unreliable Wi-Fi, VPN or WAN links because the serial protocol is sensitive to latency and packet loss.
- Use a stable address. Reserve the coordinator IP in DHCP or follow the manufacturer’s supported static-IP method. Record the actual TCP port.
- Limit access. A serial TCP port is an administrative path to the coordinator, not a public service. Block access from guest networks and the internet. Change default management passwords and update firmware carefully.
- Plan for VLANs. A Zigbee serial TCP connection may work across routed local subnets with explicit firewall rules; Matter/Thread discovery is more demanding because it uses IPv6 and mDNS/multicast.
- Protect power. If Home Assistant, the PoE switch and the coordinator must survive short outages together, put the relevant network equipment on the UPS as well as the server.
- Avoid two controllers. Never point ZHA and Zigbee2MQTT, or two active HA instances, at the same coordinator simultaneously.
A common trap is assuming that because a Zigbee TCP socket works across a VLAN, Matter-over-Thread will also work across the same segmentation. Home Assistant’s Matter documentation warns that local IPv6 and multicast discovery must reach the Home Assistant host and that VLANs or multicast filtering can break commissioning. For the first deployment, put the Matter controller and Thread border router on the same trusted LAN, verify basic operation, and only then add carefully tested segmentation.
Five-year ownership cost: calculate the complete system
Comparing a €45 USB radio with a more expensive-looking PoE box is misleading unless you account for everything required to make the architecture work. Likewise, a USB dongle that forces you to relocate a server, add long USB cabling or manually move hardware after every VM migration has operational costs that are not captured by the purchase price. Use the following checklist to compare actual local quotes, including VAT and delivery.
| Cost element | USB passthrough design | Ethernet / PoE design |
|---|---|---|
| Radio hardware | USB coordinator, or two dedicated radios for Zigbee + Thread | One network Zigbee coordinator; separate Thread border router/radio if required |
| Power and connectivity | USB extension lead; powered hub only if necessary | Ethernet cable; existing PoE port or new injector/switch; possibly UPS port |
| Firmware and software | Usually no separate radio subscription; maintain HA/ZHA/Z2M | Usually no separate Zigbee licence; verify vendor firmware update policy |
| Backup / recovery | HA backup and radio migration plan; physical device move on node failure | HA backup plus IP, credentials and radio firmware backup; test alternate-node reachability |
| Five-year energy | Measure marginal USB draw at the wall if possible | Measure PoE switch/injector incremental wall draw; include conversion losses |
| Operational cost | Time spent on USB mapping and VM moves | Time spent on switch, IP, security and network troubleshooting |
Use a five-year cost formula: total cost = radio(s) + cabling + any PoE injector/switch upgrade + any incremental UPS provision + delivery/tax + (measured additional wall watts ÷ 1,000 × 24 × 365.25 × 5 × electricity price per kWh) + any replacement or support cost you reasonably expect. This formula is not a claim about either product’s actual power consumption.
For a worked energy sensitivity calculation only, assume an additional continuous 1 W at the wall and an illustrative electricity rate of €0.30/kWh. Over five years that is 43.83 kWh, or €13.15. At an assumed additional 3 W, it is 131.49 kWh, or €39.45. Neither figure is a measurement or specification for ZBT-2 or SMLIGHT; it shows how to translate your own meter readings into a comparable five-year figure. A PoE switch’s idle power may be shared across many devices, so measure the incremental load rather than charging the whole switch to one radio.
The official EU ZBT-2 reference MSRP is €45 per unit, so two ZBT-2 units have a reference radio-only subtotal of €90 before regional retail pricing, shipping and any accessories. That is useful when you require one Zigbee radio and a separate Home Assistant-managed Thread radio. For Ethernet devices, use a current quote for the exact SLZB model, then add the real price of your PoE arrangement. Prices for the SLZB variants, PoE injectors and network switches were not verified as live retail offers for this article, so they are intentionally not invented.
There is no universal break-even point. A buyer with a spare PoE switch port and Ethernet socket may value central placement enough to justify the network radio immediately. Someone with a single Proxmox box next to a good RF location may gain almost nothing from spending extra on Ethernet. Use your actual environment, not a generic “network is always better” recommendation.
Four sensible deployment designs
A. One mini PC and a small Zigbee network
Choose a supported USB coordinator, ideally an official ZBT-2 if you use ZHA and value the guided setup. Pass it into the HAOS VM, place the antenna away from the computer and back up the Zigbee network. This is the simplest design with the fewest dependencies. If you do not need Thread, do not buy a second radio just because the marketing mentions Matter.
B. Proxmox host in a rack, smart-home devices throughout the house
Use a wired Ethernet/PoE Zigbee coordinator in a better RF position. Run ZHA or Zigbee2MQTT in the HAOS environment, point it at the documented socket endpoint, reserve its IP and protect the management interface. Keep the Proxmox host in the rack and the radio in the house. A centrally placed coordinator is especially valuable if the server room has metalwork, dense cabling or nearby Wi-Fi equipment.
C. Two Proxmox nodes and a recovery plan
Prefer a wired network coordinator for Zigbee so the radio is not tied to one host USB controller. Test stopping the primary HAOS instance, restoring or starting it on the other node and reconnecting to the same coordinator. Never run two active controllers against the same radio. Keep Zigbee network and Home Assistant backups off the failed host. If you also use a USB Thread RCP, recognise that Thread remains tied to that physical host unless you redesign that part separately.
D. Zigbee devices plus Matter-over-Thread
Use one supported Zigbee coordinator (USB or wired network) and assess your existing Thread border routers before buying anything else. If you already have a suitable Apple or Google border router, it may cover Thread. If you want a Home Assistant-managed Thread network, add a dedicated compatible Thread radio and OTBR service. A verified dual-radio appliance may consolidate hardware, but check that its Thread side truly runs a supported border-router architecture and that the two radios can operate independently.
Pre-purchase checklist: twelve questions that prevent expensive mistakes
- Which software owns Zigbee: ZHA or Zigbee2MQTT? Confirm the exact radio family and firmware version against its current compatibility list.
- Are you buying a Zigbee coordinator, Zigbee router/repeater, Thread radio co-processor or complete Thread border router? The roles are not interchangeable.
- Does the device support wired Ethernet, or is it really only Wi-Fi serial forwarding? Prefer wired for network Zigbee.
- Is PoE genuine 802.3af/at compatibility, passive PoE, or merely USB power with an optional splitter? Match the actual standard.
- If buying SMLIGHT, is the SKU SLZB-06, SLZB-06M, SLZB-06MG24 or an MR multi-radio model? Read the exact specification.
- Is the Zigbee coordinator firmware already installed, and can you back up and restore the network during future migration?
- For Thread, does the manufacturer document a working border-router service, network commissioning and Home Assistant integration?
- Can the coordinator be placed clear of the metal rack, Wi-Fi access point and USB 3.x devices?
- Will the radio be on the same reliable power/UPS arrangement as the server and essential network switch?
- Will a Proxmox VM need to move between nodes, or is this genuinely a single-host setup?
- Are the TCP management and serial ports restricted to trusted devices, and is firmware update support credible?
- Have you added cables, injectors, switch ports, VAT, delivery and five-year incremental electricity to the price comparison?
Failure symptoms: diagnose the right layer
| Symptom | Likely layer to check | First useful action |
|---|---|---|
| USB coordinator vanishes after reboot | Proxmox mapping / guest USB device | Check physical connection and guest hardware; use stable mapping, then inspect HAOS hardware |
| Zigbee2MQTT reports serial connection refused | LAN socket / port / coordinator mode | Check IP, TCP port, Ethernet mode and that another controller is not connected |
| Network coordinator drops intermittently | LAN, PoE, Wi-Fi serial proxy, switch | Use wired LAN; inspect PoE logs, link status and controller logs at the same timestamps |
| ZHA can reach radio but devices are slow | Zigbee mesh and RF interference | Review channel overlap, placement and mains-powered routers before replacing hardware |
| Thread network visible but Matter pairing fails | Credentials, IPv6, mDNS, commissioning | Check preferred Thread network, phone credentials, IPv6 and same-LAN discovery |
| VM moved to second Proxmox node; USB gone | Host-bound passthrough | Move/remap USB or use a network radio; do not assume automatic live migration |
| Two Zigbee services fight over one adapter | Exclusive coordinator ownership | Stop one service and confirm the intended controller has exclusive access |
| “Multiprotocol” adapter unstable | Unsupported simultaneous radio operation | Dedicate separate radios; follow vendor-supported firmware and migration procedure |
Avoid “fixes” that destroy network state. Reflashing a coordinator, replacing its IEEE identity or rebuilding a Zigbee network can require device re-pairing. Before any firmware switch or migration, export the supported coordinator/network backup, create a full Home Assistant backup and record firmware version, network channel and serial endpoint. For Thread, also verify how your border router and controller preserve the existing Thread credentials.
Frequently asked questions
Can I run ZHA with an Ethernet Zigbee coordinator?
Yes, when the exact coordinator and serial socket transport are supported by ZHA/zigpy. Home Assistant documents compatible socket-based radio configurations. A stable wired LAN is important; not every Ethernet box or firmware mode is automatically supported.
Can one ZBT-2 handle Zigbee and Matter-over-Thread together?
No. Home Assistant states that one ZBT-2 runs Zigbee or Thread, not both simultaneously. You need another Thread border router or a second dedicated radio if you want both networks.
Is a network Zigbee coordinator a Thread border router?
Not by default. Zigbee serial-over-IP forwards coordinator communication; a Thread border router routes IPv6 traffic between Thread and the LAN. Some multi-mode devices can be reconfigured or include independent radios and software, but you must verify the actual Thread border-router implementation.
Will Ethernet make my Zigbee devices respond faster?
Not necessarily. Zigbee latency usually depends more on radio quality, mesh routing, interference and controller processing than whether the coordinator is reached over USB or a healthy local Ethernet link. Ethernet mainly improves placement and reduces host USB dependence.
Do I need to buy Thread hardware for every Matter device?
No. Matter can run over Wi-Fi/Ethernet or Thread. Only Matter-over-Thread devices require a Thread mesh and border router. A compatible border router you already own may be sufficient; verify Home Assistant discovery and credentials.
Verdict: which should you buy?
Choose USB for a single Proxmox host, a good radio location and minimum complexity. The current official ZBT-2 is a sensible Home Assistant-first choice, provided you dedicate it to Zigbee or Thread. Choose wired Ethernet/PoE Zigbee when radio placement or moving the HAOS VM between Proxmox nodes matters enough to justify the extra network infrastructure and administration. For Zigbee2MQTT, shortlist the exact TI or Silicon Labs adapter family only after confirming its driver and firmware. For Thread, first check existing border routers; a supported Apple/Google border router may be a better solution than buying another USB stick. If you want both Zigbee and Thread in one enclosure, investigate a genuine dual-radio design rather than relying on unstable single-radio multiprotocol claims.
The most robust setup is not the one with the most features printed on the box. It is the one whose radio role, firmware, host software, LAN dependencies and recovery procedure are all understood before you start pairing devices.
Related ESP32 and Home Assistant guides
- Home Assistant on Proxmox: Zigbee and Thread USB Passthrough — practical Proxmox host USB mapping and HAOS radio setup.
- Home Assistant OS vs Docker vs Proxmox — select the right hosting architecture before buying radios.
- Home Assistant Connect ZBT-2: Zigbee — official USB radio capabilities and limitations.
- ZBT-2 vs ZBT-1 — whether an existing USB radio needs replacing.
Official sources and documentation
- Home Assistant — Zigbee Home Automation (ZHA): compatible radios, socket transports, stability cautions and migration.
- Home Assistant — Thread integration: border routers, credentials, preferred network and OTBR.
- Home Assistant — Matter integration: IPv6, mDNS, Thread and supported network arrangements.
- Home Assistant — Connect ZBT-2: official MG24/ESP32-S3 hardware, USB specification, one-protocol rule and reference MSRP.
- Zigbee2MQTT — Adapter settings: USB and TCP serial endpoints, adapter selection and stable IP guidance.
- Zigbee2MQTT — EmberZNet adapters: Silicon Labs firmware and driver compatibility.
- Zigbee2MQTT — Z-Stack adapters: Texas Instruments coordinator guidance.
- Zigbee2MQTT — Remote adapters: warning against unstable Wi-Fi, VPN and WAN serial forwarding.
- SMLIGHT — SLZB model overview: exact model, radio family and PoE comparison.
- Proxmox VE — Administration Guide 9.x: USB passthrough and virtual-machine hardware constraints.
Research note (10 October 2026): Hardware and software claims above were checked against the linked manufacturer and project documentation. No hands-on testing or measured RF benchmarks are claimed. Prices other than the cited ZBT-2 manufacturer MSRP have not been asserted; electricity examples are labelled assumptions. Confirm exact model, firmware, regional stock and support before purchasing.
