The Device Bridge Switch is one of those products that solves a problem you assumed was too niche for anyone to build a dedicated device for: bridging a small cluster of ethernet devices to a wireless network. It’s a managed desktop switch with a built-in wireless client—plug in your devices, and they talk to each other locally via ethernet while connecting wirelessly to the rest of your network. Adoption into the UniFi controller is the same single-click experience as any other UniFi device, and the switch ports are fully managed with per-port VLAN support, all configured seamlessly over the wireless link. If you need ethernet connectivity where you can’t run cable and you’re already in the UniFi ecosystem, this is the clean, purpose-built solution.

The Problem

Sometimes you have a cluster of devices that need network access in a location where running ethernet cable isn’t practical. Maybe it’s a temporary setup, maybe the building doesn’t allow new cable runs, maybe you just don’t want to tear open a wall for three devices. The usual options are ugly: a wireless bridge feeding a dumb switch, a mesh node with ethernet backhaul configured in reverse, or some other cobbled-together arrangement that works but feels fragile and inelegant.

The Device Bridge (Prequel)

A few months before the Device Bridge Switch appeared, Ubiquiti released the single-port Device Bridge. I experimented with it and it worked well—a clean, purpose-built solution for connecting a single wired device to a wireless network. It adopted into the UniFi controller without drama, and the device it bridged appeared on the network as if it were wired.

But one port meant one device. If you needed to bridge several devices, you were back to chaining in a separate switch, which defeated the elegance.

Enter the Device Bridge Switch

Then Ubiquiti released the Device Bridge Switch, and I bought one immediately. Same concept, but with integrated switch ports. Exactly the product the single-port version should have been from the start.
Well, for me anyway; I completely understand the single device use case too, it’s just that the integrated switch matches my use cases much better.

Setup

Adoption is straightforward, consistent with the rest of the UniFi ecosystem. Power it on, click adopt in the controller, and it autoconfigures. No manual SSID entry, no fiddling with wireless credentials. It pulls its configuration from the controller like any other UniFi device.

If you’ve adopted any UniFi device before, this is the same experience. If you’ve used the single-port Device Bridge, it’s identical.

Early Impressions

I’m still in the early stages of testing to see how well it handles the role long-term. Initial results are promising—devices connected to the switch ports appear on the network and communicate without issues.

The real questions are about reliability over time: does the wireless bridge stay stable under sustained use? How does it handle network transitions or controller restarts? What kind of throughput can you realistically expect through the wireless link? These are the things that only show up after weeks of use, not during initial setup.

One thing worth highlighting: the switch ports are fully managed through the UniFi controller, just like any other UniFi switch. You can assign per-port VLANs to different values, and all of that configuration happens seamlessly over the wireless connection. So if you have a couple of devices at a remote location that need to live on different VLANs—say an IoT device on an isolated network alongside a workstation on your main network—you can handle that from the controller without any extra hardware or awkward workarounds. It behaves exactly like a wired managed switch that happens to have a wireless uplink.

Who This Is For

If you need to extend ethernet connectivity to a location where you can’t or won’t run cable, and you’re already in the UniFi ecosystem, this is the clean solution. It replaces a wireless bridge plus a switch with a single managed device that shows up in your controller and behaves like a first-class citizen on your network.

It’s not for high-bandwidth applications—you’re still going through a wireless link. But for the use case it targets, it’s exactly right.