SLZB-06 Review 2026 | Best Zigbee PoE Coordinator for Home Assistant

The SMLIGHT SLZB-06 is the most capable network-attached Zigbee coordinator available for Home Assistant users today. Its PoE support, tri-mode connectivity, and powerful local web interface make it a major step up from any USB dongle. For Zigbee2MQTT users, get the SLZB-06 (CC2652P). For ZHA users or anyone eyeing Matter, get the SLZB-06M (EFR32MG21). Both are excellent.

What Is the SMLIGHT SLZB-06?

The SMLIGHT SLZB-06 is a Zigbee 3.0 to Ethernet, USB, and WiFi gateway coordinator built specifically for open-source smart home platforms — Home Assistant, Zigbee2MQTT, and ZHA.

Unlike a USB Zigbee dongle that has to sit next to your server, the SLZB-06 connects over your local network. That means you place it wherever your Zigbee signal is strongest, not wherever your server happens to live. This single change makes a bigger difference to mesh quality than almost any other hardware decision you can make.

The device comes pre-flashed and ready to use. It supports Power over Ethernet (IEEE 802.3af), runs a custom operating system called SLZB-OS, and includes a built-in WireGuard VPN client for remote deployments. For anyone building a serious Zigbee network, it is the strongest hardware foundation currently available.

SLZB-06 vs SLZB-06M: Which Model Should You Actually Buy?

This is the question that brings most people here, and it deserves a direct answer before anything else.

The short answer:

• Use Zigbee2MQTT? → Buy the SLZB-06 (CC2652P)
• Use ZHA or planning for Matter/Thread? → Buy the SLZB-06M (EFR32MG21)
• Running 200+ devices or want the absolute latest? → Consider SLZB-06MG24 (EFR32MG24)

Here is the full model comparison:

Key decision insight: SMLIGHT themselves note that the CC2652P chip rarely exceeds 30% memory utilization even under full load with 200 paired devices. The higher-RAM P7 and P10 variants are largely a marketing distinction for typical home use. Spend your money on the standard model and invest in placement instead.

What are the Hardware Specifications of SLZB-06?

The SLZB-06's performance advantage over USB dongles comes from two things: high-quality internal components and the fact that both primary chips sit on a single unified PCB. That integration eliminates the stability issues common in module-on-board designs.

The Zigbee Radio: Texas Instruments CC2652P

The CC2652P is the most battle-tested Zigbee SoC for Zigbee2MQTT. It includes an integrated +20dBm RF amplifier, which is roughly four times the transmit power of a standard USB dongle. Paired with the included +5dB external SMA antenna, this gives the SLZB-06 significantly better range and Link Quality Indicator (LQI) scores than anything plugged directly into a server.

The CC2652P has been running at scale in community installations for several years. Its firmware support in Zigbee2MQTT is mature, well-documented, and receives regular updates.

The Control Chip: Espressif ESP32

Network management, the web interface, and protocol logic are handled by the ESP32-DOWDQ5-V3, a dual-core processor running at 240MHz. It manages Ethernet, WiFi, Bluetooth (via ESPHome), and coordinates the routing between the network layer and the Zigbee radio. At 240MHz dual-core, it handles all of this without introducing meaningful latency.

See more: What is Zigbee?

Full Specifications Table

PoE Setup: What Switch or Injector Do You Actually Need?

The SLZB-06 requires active PoE (IEEE 802.3af), the standard 15.4W PoE found on most managed and semi-managed switches. It will not work reliably with passive PoE unless the injector outputs the correct voltage range.

Any 802.3af or 802.3at PoE switch works. Popular choices in the Home Assistant community include the TP-Link TL-SG1005P, UniFi switches, and the Netgear GS305P. A standalone 48V 802.3af PoE injector also works if your switch does not support PoE natively.

No PoE switch at all? Power the device via its USB Type-C port and use a standard Ethernet cable for data. The SLZB-06 features optoelectronic isolation between the USB and Ethernet circuits, so connecting both simultaneously is fully supported and safe.

Common mistake to avoid: Passive PoE injectors output 12 to 24V, not the 48V that IEEE 802.3af requires. Using an incompatible passive injector can damage the device. Always verify the PoE standard before connecting.

What are the Three Connectivity Modes?

The SLZB-06 supports three operating modes, switchable via the web dashboard or a physical mode button on the device.

Mode 1: Zigbee-to-Ethernet (Recommended)

The device connects to your network via RJ45 and communicates with Home Assistant over TCP/IP. This is the recommended mode for all permanent installations. Ethernet eliminates WiFi interference, provides lower and more consistent latency, and is dramatically more stable for a coordinator that is always-on.

Use this mode if: You can run an Ethernet cable to the optimal coordinator location.

Mode 2: Zigbee-to-WiFi

The SLZB-06 connects to your 2.4GHz WiFi network and communicates over the air. Signal quality can vary with network congestion and distance.

Use this mode if: Running Ethernet is not feasible. Expect occasional reconnections in WiFi-congested environments. Not recommended as a permanent setup for networks larger than 50 devices.

Mode 3: Zigbee-to-USB (Serial)

A standard Type-C cable connects the device to your server and it behaves like a conventional USB Zigbee dongle. In this mode, all network features of the device are dormant — it acts purely as a radio.

Use this mode if: You want to try the device before committing to a network setup, or you need a fallback option during Ethernet troubleshooting.

How to Set Up the SLZB-06 with Zigbee2MQTT (Step-by-Step)

This is the most common integration path and the one for which the SLZB-06 is most optimized.

Prerequisites: Home Assistant running, Zigbee2MQTT add-on installed, SLZB-06 powered and connected to your network.

Step 1: Find Your Device's IP Address

After plugging in the SLZB-06, it will appear on your network via DHCP. Find the assigned IP by:

• Checking your router's DHCP client list
• Navigating to http://slzb-06.local in a browser (if mDNS is enabled on your router)
• Checking the SLZB-OS web dashboard at the device's IP

Step 2: Open the SLZB-OS Dashboard

Access the local web interface by entering the device IP in your browser. Confirm the device is running correctly and note the assigned port — by default, the Zigbee serial service runs on port 6638.

Step 3: Update the Zigbee2MQTT Configuration

In your Zigbee2MQTT configuration.yaml, update the serial section:

serial:
  port: 'tcp://192.168.1.XXX:6638'
  adapter: zstack

Replace 192.168.1.XXX with your device's actual IP address. For stability, assign a static IP or DHCP reservation to the SLZB-06 in your router settings — this prevents the IP from changing after a router reboot.

Step 4: Restart Zigbee2MQTT

Restart the add-on from the Home Assistant add-on page. Within a few seconds, Zigbee2MQTT will connect to the coordinator over TCP and begin operating normally. Existing paired devices carry over without re-pairing.

Step 5: Verify Connection

In the Zigbee2MQTT logs, look for:

Connected to the adapter successfully

If you see this line, setup is complete.

How to Set Up the SLZB-06 with ZHA?

Home Assistant version 2023.1 and later includes LAN autodiscovery for the SLZB-06. If your router passes mDNS traffic, Home Assistant may detect the device automatically and prompt you to configure it.

For manual ZHA setup:

1. Go to Settings → Devices & Services → Add Integration
2. Search for Zigbee Home Automation
3. Select Enter Manually when prompted for the serial port
4. Set Radio Type to:
   • ZNP for the standard SLZB-06 (CC2652P)
   • EZSP for the SLZB-06M (EFR32MG21)
5. Set the Serial Device Path to: socket://[YOUR_DEVICE_IP]:6638
6. Leave the baud rate at default and click Submit

ZHA will initialize the coordinator and you can begin pairing devices immediately.

Note for SLZB-06M users: The EFR32MG21 chip is the same silicon used in official Home Assistant SkyConnect and Yellow adapters. This means ZHA has native, deeply tested support for the M variant — often resulting in higher LQI readings than the CC2652P equivalent.

How to Migrate from a USB Dongle to the SLZB-06

Migrating your existing Zigbee network to the SLZB-06 without re-pairing all your devices is possible — and in most cases, straightforward.

Migrating in Zigbee2MQTT

Zigbee2MQTT stores your network key and device database in its configuration.yaml and database.db files. As long as you preserve these files, your devices will reconnect automatically.

Steps:

1. Back up your Zigbee2MQTT data folder (especially configuration.yaml, database.db, and the coordinator_backup.json if present)
2. Stop Zigbee2MQTT
3. Connect the SLZB-06 and update the serial.port value in configuration.yaml to your new TCP address
4. Restore your network backup via the Z2M backup/restore feature or by manually flashing the coordinator backup to the new hardware (available in the SLZB-OS web dashboard under Zigbee → Backup)
5. Start Zigbee2MQTT — devices should reconnect within a few minutes as the mesh reforms

Migrating in ZHA

ZHA supports full coordinator migration via its built-in backup and restore tool:

1. Go to Settings → Devices & Services → Zigbee Home Automation → Configure → Migrate Radio
2. Follow the migration wizard — it will back up your network key and topology
3. When prompted, select your new coordinator (SLZB-06 via socket)
4. ZHA restores the network key to the new hardware
5. Devices reconnect automatically — no re-pairing required

Key tip: If you are migrating from a Sonoff Dongle E (EFR32MG21) to an SLZB-06M (also EFR32MG21), you can often skip the migration wizard entirely. The SLZB-06M supports IEEE address spoofing — you can set the new coordinator's address to match your old dongle's address exactly, making the transition invisible to your device network.

SLZB-OS Web Dashboard: What are the Features That Actually Matter

The SLZB-OS web interface is more capable than most users realize. Here are the features worth knowing:

Remote Firmware Updates (OTA)

Both the Zigbee SoC firmware and the ESP32 firmware can be updated directly from the web dashboard — no physical access required. This is critical for long-term maintenance, especially if the coordinator is installed in a ceiling, wall cabinet, or remote building.

Network Mode Switching

Switch between Ethernet, WiFi, and USB modes without touching the device. The dashboard also shows live network statistics including uptime, connection status, and Zigbee coordinator state.

Zigbee Network Backup

Create and restore a full backup of your Zigbee network directly from the dashboard. This includes the network key, pan ID, and coordinator firmware state — everything needed to recover or migrate your network.

WireGuard VPN Client

One of SLZB-06's most underutilized features. The built-in WireGuard client allows you to run a coordinator in a physically remote location — a detached garage, summer house, or office — and tunnel it securely back to your main Home Assistant instance over the internet. This enables a genuine multi-site Zigbee deployment without any additional hardware.

ESPHome Integration

The ESP32 inside the SLZB-06 is accessible via ESPHome. This unlocks the device's temperature sensor, LED control, and other internal telemetry directly within Home Assistant — useful for monitoring coordinator health in your dashboards.

Real-World Performance: Signal, Stability, and Device Limits

Signal Range

The +20dBm CC2652P with a +5dB external antenna represents approximately 4× the effective transmit power of a standard USB Zigbee stick (+5dBm). In practice, this means:

• Wall penetration is noticeably better in multi-story homes
• Problematic edge-device locations (far corners, outbuildings) become reliably pairable
• LQI scores for borderline devices improve significantly — often turning unreliable end-devices into stable ones

Placing the coordinator at the geometric center of your device cluster (rather than in a basement near the server) typically delivers the largest single improvement in mesh stability.

Stability

The Ethernet mode of the SLZB-06 is fundamentally more stable than WiFi-based coordinators because it removes the 2.4GHz interference variable entirely. Zigbee itself operates on 2.4GHz, meaning a WiFi-connected coordinator is competing for airtime on the same frequency band it is trying to coordinate. Ethernet eliminates this entirely.

In community deployments running 80–150 devices over months of operation, the Ethernet-connected SLZB-06 is consistently described as a "set it and forget it" device with no coordinator crashes or disconnections between firmware update cycles.

Device Limits

The standard SLZB-06 (CC2652P) supports up to 200 end devices in Zigbee firmware. SMLIGHT confirms that under maximum load, the chip's processor utilization remains well below capacity — meaning 200 is a firmware-imposed limit, not a hardware one. For networks requiring more than 200 devices, the recommended approach is running a second coordinator instance on a separate SLZB-06, each managing its own Zigbee2MQTT instance in Home Assistant.

What are the Common Problems and How to Fix Them

Device shows as unavailable after switching from USB to Ethernet

The device IP likely changed after a router reboot. Assign a static DHCP lease to your SLZB-06 in your router settings. Then confirm the port in configuration.yaml matches what the SLZB-OS dashboard shows (default 6638).

Zigbee2MQTT fails to connect after setup

This is almost always an adapter type mismatch. Set adapter: zstack for the CC2652P (SLZB-06) or adapter: ember for the EFR32MG21 (SLZB-06M). An incorrect adapter type causes a silent connection failure with no obvious error message in the logs.

WiFi mode drops frequently

2.4GHz channel overlap between your WiFi network and Zigbee is the most common cause. Switch to Ethernet wherever possible. If Ethernet is not an option, set your router to a fixed WiFi channel (1, 6, or 11) and configure Zigbee2MQTT to use Zigbee channel 25 or 26 to minimize frequency conflict.

PoE is not powering the device

Your switch is likely using passive PoE rather than IEEE 802.3af active PoE. Purchase a dedicated 802.3af injector or switch to USB Type-C power instead.

Devices not reconnecting after coordinator migration

The network key was not restored correctly to the new coordinator. Use the SLZB-OS backup restore feature to flash the original network backup, then confirm the network key in configuration.yaml matches the backup file exactly.

Running Multiple SLZB-06 Coordinators in Home Assistant

One of the most powerful architectural advantages of the SLZB-06's network-based design is the ability to run multiple independent Zigbee networks from a single Home Assistant instance.

How it works:

• Each SLZB-06 unit has its own IP and port
• Each unit runs as a separate coordinator in its own Zigbee2MQTT or ZHA instance
• Home Assistant sees all devices from all instances in a unified interface

Common multi-coordinator setups:

• One per floor in a large home
• One for stable production devices, one for unstable or experimental devices (isolating problem devices from your main mesh)
• One per building in a property with a detached garage or workshop

Each Zigbee2MQTT instance runs as a separate add-on or Docker container with its own configuration.yaml. This approach scales without hardware limitations beyond the cost of additional SLZB-06 units.

Matter-over-Thread: Is the SLZB-06 Ready?

The SLZB-06 family supports Matter-over-Thread in varying degrees depending on the model:

Important limitation: No SLZB-06 model currently supports simultaneous Zigbee and Thread operation. You choose one protocol per device. If you run a mixed Zigbee + Matter network, you need two separate coordinators.

For most users in 2026, Zigbee remains the better choice for existing device ecosystems. Thread is worth considering only if you are starting a new installation predominantly with Matter-certified devices.

Is the SLZB-06 Worth It? Final Verdict

Yes — with one caveat.

The SLZB-06 is the right foundation for anyone building a stable, long-lived Zigbee network on Home Assistant. The PoE support, Ethernet connectivity, and remote management are genuine operational advantages. Placing the coordinator where your devices are, rather than where your server is, is the single biggest practical improvement available to a Zigbee network.

The caveat is simple: if you run fewer than 20 devices in a small apartment, a USB dongle is perfectly fine. The SLZB-06 is built for networks that will grow, span multiple rooms, and need to operate reliably without intervention for years at a time.

Choose the SLZB-06 (CC2652P) for Zigbee2MQTT with maximum firmware maturity and community support.

Choose the SLZB-06M (EFR32MG21) for ZHA or a planned transition toward Matter.

Choose the SLZB-06MG24 for new large-scale builds with Thread and Matter as the primary target.

FAQ about the SLZB-06

What is the SMLIGHT SLZB-06 used for?

The SMLIGHT SLZB-06 is a Zigbee coordinator that connects Zigbee 3.0 smart home devices to Home Assistant over your local network via Ethernet, WiFi, or USB. It replaces USB Zigbee dongles by allowing placement anywhere in your home where Zigbee signal is strongest, rather than being restricted to the server location.

What is the difference between the SLZB-06 and SLZB-06M?

The SLZB-06 uses the Texas Instruments CC2652P chip and is best for Zigbee2MQTT users. The SLZB-06M uses the Silicon Labs EFR32MG21 chip, which is the same chip used in official Home Assistant hardware and is better suited for ZHA users. Both support up to 200 devices and both work with PoE.

Can I use the SLZB-06 without a PoE switch?

Yes. The SLZB-06 can be powered via its USB Type-C port while using a standard Ethernet cable for network connectivity. It can also connect over WiFi if Ethernet is unavailable. PoE is the most convenient option but not a requirement.

Does the SLZB-06 work with Zigbee2MQTT?

Yes. The standard SLZB-06 (CC2652P) has full, stable support in Zigbee2MQTT using the ZNP adapter stack. Configure it in your configuration.yaml by setting the port to tcp://[device-ip]:6638 and adapter: zstack. The SLZB-06M uses the Ember stack (adapter: ember).

How many Zigbee devices can the SLZB-06 handle?

The standard SLZB-06 (CC2652P) supports up to 200 end devices. For networks requiring more than 200 devices, SMLIGHT recommends running a second coordinator unit as a separate Zigbee2MQTT instance. The SLZB-06MG24 model supports up to 350 devices.

Can I migrate from a Sonoff Zigbee Dongle to the SLZB-06 without re-pairing?

Yes. In Zigbee2MQTT, use the backup and restore feature to transfer your network key to the new coordinator. In ZHA, use the built-in Migrate Radio wizard. If migrating from a Sonoff Dongle E (EFR32MG21) to an SLZB-06M (same chip), you can also spoof the IEEE address to make the transition seamless.

Is WiFi mode stable enough for a large Zigbee network?

WiFi mode is functional but not recommended for permanent setups with 50+ devices. Zigbee and 2.4GHz WiFi operate on overlapping frequencies, which can cause interference in congested environments. Ethernet mode is always preferred for stability.

Does the SLZB-06 support Matter?

The SLZB-06 family supports Thread (the network layer for Matter) but requires a firmware switch to enable it. You cannot run Zigbee and Thread simultaneously on a single unit. The SLZB-06M and SLZB-06MG24 are the recommended models for Thread/Matter setups.

Can I update the SLZB-06 firmware remotely?

Yes. Both the Zigbee SoC firmware and the ESP32 firmware can be updated over-the-air through the SLZB-OS web dashboard. No physical access to the device is required, making it practical to mount in hard-to-reach locations.

Can I run two SLZB-06 units in one Home Assistant instance?

Yes. Each unit has a unique IP address and port. You can run a separate Zigbee2MQTT or ZHA instance for each coordinator within Home Assistant, and all devices appear in a unified Home Assistant interface. This is the recommended approach for multi-floor homes or networks with more than 200 devices.