Enter Omada: Buying the Whole Ecosystem to Solve One Problem

By the end of Part 2, I’d proven two things conclusively. One: I could build a router from spare parts. Two: I absolutely should not have.

What I had was a pile of mismatched components held together by stubbornness — a single-NIC mini PC, a USB dongle with trust issues, and a vague plan to bolt on a managed switch and an access point from whatever brand happened to be on offer. Each piece would need its own login, its own quirks, its own firmware update at the worst possible moment.

So I did what a lot of homelabbers do at exactly this stage of the journey: I stopped trying to assemble an orchestra out of buskers and went looking for something that was designed to play together. That something was TP-Link Omada.

What Omada actually is

Here’s the bit that confused me at first, so let me save you the head-scratching.

Omada isn’t a single product. It’s an ecosystem — a family of routers (they call them gateways), switches, and access points that are all managed from one place: the Omada Controller.

The controller is the whole point. Instead of logging into your router, then your switch, then each access point separately, you log into one dashboard that manages all of them together. Create a Wi-Fi network once and it appears on every access point. Push a firewall rule once and it applies network-wide. TP-Link calls this approach SDN — Software-Defined Networking — which is a fancy way of saying “the brains are separate from the boxes.”

You can run that controller a few ways: as a physical “hardware controller” appliance, as a cloud-based controller, or — the homelabber’s favourite — as software on a machine you already run. In my eventual setup it lives in a container on my Proxmox server, quietly managing the whole network from a corner of the rack. (More on that build in a later guide.)

After the spare-parts saga, the appeal was overwhelming. One brand. One dashboard. One pane of glass to rule them all. Everything I’d been trying to duct-tape together — routing, switching, Wi-Fi, VLANs, guest networks — sitting inside a single coherent system that the manufacturer actually tested together.

What I was buying it to solve

I went into Omada with a clear shopping list of problems I wanted gone:

The two-NIC nightmare. A purpose-built gateway has the right ports out of the box. No dongles, no router-on-a-stick gymnastics, no 11pm reboots wondering which port was now the WAN.
One management plane. I wanted to stop collecting logins like Pokémon.
Proper VLANs and Wi-Fi together. Create a network, assign it a VLAN, broadcast it from the access points — all in one place, all consistent.
Room to grow. Add an access point, the controller adopts it. Add a switch, same story. The system was supposed to scale with me instead of fighting me.

And to be fair to Omada — it delivered on most of that. The day I migrated over and watched a single dashboard show me every device, every client, and every network at once, after months of janky improvisation, was genuinely one of the most satisfying moments of the whole project.

”Or so I thought”

Here’s where I have to be honest, because the brochure version of this story ends with the satisfying dashboard and a sunset.

The real version has a second act. Omada integrated everything I was looking for — and then revealed a category of problem I hadn’t even thought to shop for. Two of them, specifically:

It’s business gear, and business gear has different priorities than I assumed. I was about to make my network kid-safe — bedtime schedules, content filtering, the works — and I’d quietly assumed a system this capable would handle that as easily as a consumer router does. That assumption did not survive contact with reality.
My budget brain hadn’t left the building. I’d bought into Omada to escape mismatched parts — and then promptly tried to save money on one component, picking a switch that turned out to be missing exactly the feature I’d need. Which is how I ended up with the network’s most creative field fix.

The honest verdict on going Omada

If you’re standing where I was — staring at a Frankenstein router and wondering whether to commit to an ecosystem — here’s my straight take.

Going Omada was the right call, and I’d do it again. Consolidating onto one managed system was the moment my network stopped being a hobby project that occasionally took down the house and started being actual infrastructure. The controller is powerful, the hardware is reasonably priced, and the “buy more, it just adopts” growth path is real.

But “buys you out of your problems” it is not. An ecosystem gives you a coherent set of tools; it does not give you the knowledge of which tool you actually need. I bought Omada to stop making hardware mistakes, and then — because I hadn’t done my homework on two specific features — I made two more.

The difference is that this time, the mistakes were interesting. And the workarounds, as you’ll see, were honestly the most fun part of the whole build.

The next instalment—making the LAN safer for the kids—is still being edited and will be published when it is ready.

Previous: ← The Cheap Dongle That Cost Me a Weekend · Back to: The Network Journey hub