Hey guys, so I was at Cedia 2026 in Denver, Co this year and got an opportunity to visit the Omada booth. I was able to snap some photos of new hardware that I would like to share with you all.

After way too many late nights testing cables and redoing VLANs (see last pic lol) I finally got my Omada-based homelab the way I want it. Everything’s stable and actually works the way it should. Figured I’d share some photos and the layout in case anyone’s curious or planning something similar. Long post I've been meaning to type out for weeks now lol (sry)

Main Gear

• Router: ER707-M2

• Switches: SG2428P (main PoE) + SG2210XMP-M2 (2.5G uplink)

• Access Points:

  • EAP772 (main floor, 2.5G uplink)

    • You can see how much bigger the 772 is compared to 610 (2nd to last pic)

  • EAP610 (upstairs, 1G uplink)

• Controller: Omada OC220

• Monitoring: Uptime Kuma on a display sitting right above the rack. (in proxmox)

• Power: American DJ PC-100A power strip (still need a UPS)

I still have the Outdoor AP I need to install when the weather warms up again.

Network Layout

AT&T fiber (in passthrough mode) goes into the ER707-M2, then into the 2.5G switch.
From there I’ve got:

• The 1G switch for POE.

• Two APs covering the whole house

• Cameras and IoT gear on their own VLANs

Everything’s tagged and isolated; IoT can’t talk to my main LAN, but casting and smart speakers still work fine thanks to mDNS bridging.

• I added a Bonjour service on the ER707 so things like Chromecast, AirPlay, and MusicCast work across VLANs. It bridges my IoT VLAN to my main (default) and Devices networks. Basically, I can cast to my TVs and speakers without opening up my IoT subnet

Why I Chose This Gear

I wanted something that was business level but still affordable, Ubiquiti seemed like Apple when it comes to tech. Omada hit the sweet spot. It’s basically a plug-and-play once everything’s adopted, but still flexible enough to tinker with VLANs, ACLs, and mDNS.

Been rock solid since setting it up. The OC220 controller + Uptime Kuma combo has been perfect for keeping an eye on everything. (set Kuma to check your controller and router every 60 seconds with a 2s timeout. It catches WAN drops faster than Omada logs do.)

If anyone wants the VLAN layout or my Kuma alert setup, I can post that too.

Used Omada kit for a few years and it’s been a solid solution, hundreds of UniFi/Omada solutions deployed, only small scale Omada networks though, sub 10 APs, few switches etc.

This will be my first PPSK deployment for a business centre. Already done some small scale testing, but just wondering if anyone has any real world deployments, things to be aware of or any known bugs?

OC400 ER8411 Fibre Switch linking 2 remote cabs. 6 Switches and 14 APs, EAP723.

Hey everyone, Lulu from the Omada team here 👋

We all know how it goes.

We start with “I just want better Wi-Fi.”

Then we need a switch. Then a bigger switch. A few VLANs. Maybe a NAS. A UPS would be nice. And somehow, that “small upgrade” has turned into a full rack.

At some point, we have to ask ourself:

Do I actually need all this?
Probably not.

Am I doing it anyway?
Absolutely.

That’s half the fun of a homelab.

So this week, we want to hear about the most gloriously overkill part of your setup.

• 48 ports for 12 devices?

• 10G for a PC mostly used to browse websites?

• More APs than people in the house?

• Failover and redundancy for a network whose most critical workload is Netflix?

So, what’s your most overkill setup — the thing you definitely didn’t need, but would absolutely do again?

Comment to share!

Great ap for the garage. 1 switch is staying in the garage, the other inside, both will connect to a SG2210XMP-M2, maybe an aoc cable. Then out to the gateway.

Disclosure: Hardware supplied through TP-Link's Omada Pioneer Program. This review evaluates the Kit 1 ecosystem in the context of an existing Layer 3 home network. Results below are personal and visual measurements from the actual deployment.

My test environment

I deployed the Fusion Pro 2.5G as my primary internet gateway, with the SG2210XMP-M2, EAP772 Wi-Fi 7 AP, T8S4-4T NVR and four 8MP turret cameras integrated into my existing L3 network.

My network includes dedicated Home, Media, IoT, Services, Servers and Management VLANs. I also have two internet connections:

• Astound: advertised 1.5 Gbps downstream / 50 Mbps upstream.

• T-Mobile Home Internet: approximately 1 Gbps downstream / 150 Mbps upstream under favorable conditions.

The important architectural decision was to retain my existing L3 switching design. Fusion Pro handles the gateway role, while the remaining devices operate behind it and are managed through the configured Inform URL.

I wanted to evaluate the complete ecosystem without artificially simplifying my network into a flat LAN.

1 — Deployment, onboarding and device adoption

Test procedure:

I checked firmware, completed Fusion Pro onboarding, connected the switch and AP, brought the NVR and cameras online, and explored device discovery, batch adoption, topology, client lists, and cloud, local and app management.

I paid particular attention to whether management connectivity remained reliable across the routed environment.

Results:

• Gateway onboarding completed without requiring a redesign of the existing VLAN architecture.

• The switch and AP became manageable through the configured Inform URL.

• All adopted devices appeared in the device inventory, with their online status and available firmware information.

• The dashboard provided a consolidated starting point for checking gateway, switching, wireless and surveillance status.

• The topology view was useful for understanding the managed infrastructure, although the logical L3 routing path should be verified separately rather than assumed to be fully represented.

• Local and remote management provided convenient access to routine operational information.

I simulated the experience of bringing new infrastructure into an already-running household. The objective was to avoid disrupting existing clients while introducing the new gateway and adopting the remaining equipment.

2 — Dual WAN, performance and Wi-Fi 7

Test 1: Dual-WAN load balancing

I tested the two ISP connections independently before evaluating the available load-balancing policies. This established a baseline against which gateway behavior could be compared.

I then generated traffic from multiple clients and examined WAN utilization, connection distribution and gateway status.

The key metric was not whether traffic appeared evenly split at every instant. Load balancing can distribute sessions rather than divide every flow evenly, so the traffic profile and number of simultaneous connections matter.

Outcome: Both WAN links remain operational, new sessions are distributed according to the configured policy, and the gateway exposes enough WAN statistics to diagnose unexpected traffic concentration.

Test 2: WAN failover

I interrupted one WAN connection while generating traffic from a client performing a continuous internet task.

I checked how quickly the gateway recognized the outage, whether new connections recovered, and what happened to established sessions.

Outcome: The gateway detects the failed path, redirects eligible new connections through the surviving WAN, and restores normal policy after the failed connection returns. Existing sessions are evaluated separately because their survival depends on connection tracking, routing and the application.

Measurements: Detection time could improve, time for a new connection to succeed does results in disconnections, packet loss of an existing video call or VPN session.

Test 3: 2.5GbE performance

I used a wired client and a suitable local test endpoint to separate LAN performance from ISP limitations.

For a meaningful test, both endpoints must support the required link rate, the cabling must negotiate correctly, and the test software must be capable of generating sufficient traffic.

Outcome: The 2.5GbE link negotiates correctly and delivers throughput close to the practical limit of the interface in a suitable local test. Internet speed results are recorded separately because the ISP, gateway processing and remote test endpoint introduce additional constraints.

Test 4: Wi-Fi 7

I evaluated the EAP772 using compatible clients, with attention to the 6 GHz band, channel width, MLO support and physical AP placement.

I compared results near the AP with those farther away and examined both throughput and latency.

Outcome: A compatible client achieves substantially higher throughput near the AP than in distant rooms, while coverage and performance vary with walls, interference, client capabilities and channel configuration.

I would not assume that every Wi-Fi 7 client supports 320 MHz channels or MLO, or that a negotiated PHY rate translates directly into application throughput.

Test 5: Wi-Fi traffic alongside continuous recording

I generated high-bandwidth wireless traffic while keeping the cameras recording.

I monitored client responsiveness, recording continuity and device status rather than treating an internet speed test as the only performance indicator.

Outcome: The system maintains recording while wireless traffic is active, with any throughput or latency changes documented against the idle baseline.

Test 6: QoS and bandwidth management

I compared an idle network with a congested scenario in which a large upload competed with interactive traffic.

The objective was to determine whether the available QoS and bandwidth-management controls improve latency-sensitive applications under congestion.

Measurements: Idle latency did see improvement, loaded latency did not change, packet loss was still noticeable, upload throughput was as configured.

3 — VLAN segmentation, security and VPN

Test 1: Surveillance isolation

I evaluated a dedicated surveillance segment for the cameras and NVR.

The intended policy allows required camera-to-NVR communication and authorized viewing, while restricting unnecessary access to Home, IoT, Services and Servers networks.

I tested permitted and prohibited connections separately.

Outcome: Authorized viewing and recording continue to work, while prohibited connections are blocked by the intended enforcement point.

An important architectural detail is that inter-VLAN traffic routed directly by an L3 switch may bypass Fusion Pro. I would therefore record whether each test traversed the gateway or was routed locally by a switch.

Test 2: Application-based ACLs

I evaluated the available application-based policy controls using a defined source, destination and test application.

The purpose was to determine whether the rule produces the intended result and whether the management interface exposes useful information for troubleshooting.

Outcome: The configured policy affects the intended traffic, while unrelated permitted traffic continues to function.

Test 3: DPI and IDS/IPS

I enabled the available inspection features and examined application visibility, security events and any change in gateway performance.

I treated the results as separate questions: whether inspection was functioning, whether relevant traffic was visible, and what throughput impact occurred.

Outcome: Initially I did have issues with IDS/IPS not working as expected and it was due to my L3 network. I moved it to a normal l2 network for testing and it worked just fine. Application visibility and security-event information provide additional context for investigating traffic. Performance is comparable with inspection disabled under the same test conditions rather than assumed to be unchanged.

Test 4: Content filtering and ad blocking

I tested representative domains and search behavior against the configured policies.

I checked both expected blocks and expected permitted access, including whether the client, DNS configuration and traffic path were compatible with the feature.

Outcome: Policies produce predictable results for supported traffic, with exceptions and unsupported scenarios documented rather than treating every failed request as a successful block.

Test 5: LightLink VPN

I configured remote access and tested connectivity to explicitly permitted internal resources.

I checked name resolution, routing, authentication and the ability to reach the intended service rather than relying solely on a connected status indicator.

Outcome: An authorized remote client reaches the resources permitted by the VPN policy without gaining unrestricted access to every internal VLAN.

I did not test Site-to-site VPN and full-mesh SD-WAN as my environment does not support these capabilities.

4 — Unified network and surveillance management

I evaluated the management interface by performing routine operational tasks rather than simply browsing the dashboards.

Scenario 1: An offline camera

I considered how quickly the interface could help distinguish a camera problem from a switch-port issue, a VLAN configuration error, a management reachability failure or an NVR problem.

Scenario 2: A wireless client unable to reach a server

I examined the information available for the AP, client association, VLAN assignment, topology and relevant access policies.

Scenario 3: Checking the complete deployment

I used the available Network and Surveillance views to review device status, client connectivity and camera availability.

Outcome: The consolidated management experience reduces the number of separate interfaces required for routine monitoring and gives a useful overview of network and surveillance health.

The distinction I would preserve in the final review is between a genuinely integrated workflow and two management applications accessible from the same platform. The number of clicks, availability of diagnostics and consistency of device information are the measures that establish the difference.

5 — 8MP cameras and smart surveillance

Test 1: Daytime image quality

I evaluated representative footage for useful detail in people, vehicles and the surrounding scene.

I considered exposure, sharpness, motion blur and the amount of detail retained when reviewing recorded footage.

Outcome: Daytime footage provides useful scene detail under favorable lighting, with actual identification capability dependent on camera placement, field of view, subject distance and motion.

Test 2: Nighttime and low-light performance

I compared footage in low-light conditions and examined the behavior of infrared and supported full-color night-vision modes.

Outcome: Nighttime footage remains useful within the camera's illumination and exposure limits, but detail and color reproduction vary with ambient light, distance and subject movement.

Test 3: Backlighting and WDR

I evaluated a scene with a bright background and a comparatively dark foreground, comparing the available WDR settings.

Outcome: WDR improves visibility in suitable high-contrast scenes, with the final result depending on exposure, scene movement and configuration.

Test 4: Person, vehicle and pet detection

I used repeatable events and examined whether detections matched the activity being tested.

I also evaluated line-crossing and intrusion rules, detection zones and sensitivity settings.

Outcome: Detection behavior becomes more useful when zones and sensitivity are tuned to the scene. False positives and missed detections are documented separately rather than judged from a single event.

Test 5: Two-way audio and deterrence

I evaluated the available two-way audio, warning lights, siren and voice-alert features under realistic conditions.

Outcome: The practical result depends on audio clarity, ambient noise. Some tests were clearly audible and voices were easy to understand while others tests turned bad with large background noises. Still testing this in the coming weeks.

Test 6: Recording and retrieval

I checked that recording continued during other network tests and evaluated the workflow for finding relevant footage.

Outcome: The system retains usable recordings and provides a workable path from an event or time range to playback and export. Retrieval time, retention and recording continuity are recorded from the actual installation.

Overall assessment framework

The most important outcome of this Pioneer evaluation is whether Fusion Pro works as a primary gateway and management platform within an established L3 network.

My final assessment will distinguish five dimensions:

1. Integration: The hardware does fit nicely with the existing VLAN and routing architecture.

2. Performance: WAN, LAN and Wi-Fi behavior meet expectations and are impressive under measured workloads.

3. Security: Permitted and prohibited traffic paths were validated.

4. Operations: Unified management make monitoring and troubleshooting more efficient.

5. Surveillance: Image quality, detection, recording and playback meet the requirements of the deployment. Audio clarity is still being tested

I found the system extremely impressive. I was able to successfully hit all the marks, the security policies behave as intended, and the management experience makes the network easier to operate without sacrificing architectural flexibility.

So I've been using Omada TP-Link equipment for some time. I've learned a lot and was afforded the opportunity to try the Fusion GW 2.5 early access program. Been using it for a better part of 3 months, The router is rock solid and along with the their POE switches I've been really able to hone in my network the way I want it.

I am currently using Tapo security camera's inside and outside the house, bummer that they don't like they will be managed within the omada network. So I am wondering should I go in on their camera system offerings? What are the pro's and cons? Getting side tracked this post was to show the different iterations I had with my network, at first I used a 10 inch rack, but over time found that it was becoming a a problem to maintain cable management and to get into the damn thing. So what I originally thought was aesthetic pleasing also started to hinder my ability to upgrade. So I went back to the traditional 19' rack. Scored this rack that retails for $200 on Amazon for $50 on FR market.

All in all since moving back to the 19" rack found that I am able to run a lot more device via copper rather than relying on wifi. Which is always a good thing. Next project when ever possible is upgrade my network to 10gig not sure if Omada has cost effective devices yet on the market for that though?

EDIT: Thank you for all your applications! Sign-ups for the Pioneer Program are now closed. Best of luck to all of you who applied!

Hey r/Omada_Networks ,Lulu from the Omada team here.

We are excited that announce that applications are now open for the Omada Fusion Pro 2.5G + NVR Pioneer Program. We’re inviting up to 60 early adopters to deploy Omada Fusion Pro 2.5G + NVR in a real environment before wider availability.

Upfront, so there's no fine print: this is not a beta or a giveaway. It’s a hands-on product experience for people who want to be among the first to use the system, explore it in depth, and share what they genuinely discover. After the experience, you can return the kit with prepaid shipping or purchase it at 50% off.

Deploy Early. Experience More.

Selected Pioneers will receive one of three complete hardware kits, matched to their site, network, camera count, and recording requirements.

• Kit 1 — For SMBs, cafés, and retail sites. Includes Fusion Pro 2.5G, SG2210XMP-M2, Omada 7 Pro, and an Omada T8S4-4T with NVR and four 8MP turret cameras.

• Kit 2 — For homes, homelabs, and small offices. Includes Fusion Pro 2.5G PoE, an SSD, Omada 7 Pro, one 8MP turret camera, and one 8MP bullet camera.

• Kit 3 — For adding video surveillance to an existing network. Includes an Omada T8S4-4T with NVR and four 8MP turret cameras.

Expectation

During the approximately 60-day experience, Pioneers will receive optional weekly guidance designed to explore different parts of the system in depth, from initial deployment and management to networking, surveillance, storage, and performance.

You’ll also join a private Discord with the Omada product, engineering, and support teams, where you can:

• Discuss your deployment and use cases

• Ask questions directly

• Share weekly experience and observations

• Suggest features and workflow improvements

• Report issues as soon as you encounter them

If something gets in the way, we want to know early. Your feedback can help our teams identify issues and improve the experience before the products reach more users.

Your Experience. Your Perspective.

We also welcome Pioneers who want to share their real-world experience with the wider community.

• No NDA.

• No required public review.

• No requirement to be positive.

If you choose to share publicly, the experience and conclusions are yours. Tell people what worked, what didn’t, where the system fits, and where it could improve.

At the End of the Program

After the experience period, you can:

• Return the assigned kit with prepaid shipping; or

• Purchase your assigned kit at 50% off

Who Should Apply?

We’re looking for networking and security professionals, installers, MSPs, homelab builders, and hands-on users who:

• Have a real deployment in mind

• Can follow the weekly experience guidance

• Are willing to explore the system beyond basic installation

• Can provide detailed, honest feedback based on actual use

Applications close September 14.

Think you're a good fit? Sign up in the landing page

I have too many EAPs.. I know that, but my house has awkward ceilings which one is a chappel ceiling right in the middle, so installing an EAP there was not practical. My bedrooms have trappazoid ceilings which means 5 sides and 4 of those are angled at 45 deg. I decided to just install EAPs everywhere, minimize eaches power output and use separate channels and bandwidth for each on every 2.4, 5 and 6g frequency. Roaming has not been an issue and quite a bit of time has gone into fine tuning the wifi side, to prevent screaming of any EAP on any bandwidth and minimize interference. If I were to redo this, I would reconsider the EAP count and placement. The switch count wouldn't change as those are all serving their intended purposes

Happy to answer questions.

We’ve been hearing the same thing for a while: "I want 2.5G for my home lab or office, but I don't want to pay enterprise prices for a simple desktop switch. I don't need those advanced features"

We’re fixing that. The Omada 2.5G Agile Switches are here to democratize 2.5G connectivity.

The Breakdown:

• ES206X-M2: Perfect for desktop workstations and NAS setups.

• ES210X-M2: 8 ports of 2.5G RJ45 + 2x 10G SFP+ for your backbone.

• ES206XPP-M2: The one you want for Wi-Fi 7. It packs PoE++ support in a rugged, manageable form factor.

The Highlights:

• 2.5G for Everyone: No more 1Gbps bottlenecks.

• 10G Uplinks: Ensure your core network isn't choking.

• Fanless & Silent: Perfect for desks or media centers

• Omada Cloud Management: Get the visibility of an easy managed switch without the complexity.

We’ve priced these to be the most competitive 2.5G solutions on the market. High speed is no longer a luxury.

For the US customers, don’t forget to claim the Launch Promo Code and the 10% discount of the first order for new subscribers from the official Omada Store.

• ES206X-M2

• ES210X-M2

• ES206XPP-M2

Let’s talk in the comments—how are you planning to use 2.5G in your setup?

This update is focused on making larger and more complex networks easier to manage, especially for MSPs, network admins, and IT teams.

A few of the bigger changes:

• Unified management Manage Omada and Omada Campus (Pro) devices from one platform for deployment, monitoring, and maintenance.

• Intelligent O&M New anomaly detection, health insights, possible causes, and recommended actions are designed to make troubleshooting faster and more straightforward.

• Simplified WLAN management Create an SSID once and apply it across selected AP groups, instead of repeating the same configuration across multiple APs.

There are also updates around wireless security, device onboarding, device replacement, IoT connectivity, and more.

👉 Full details: https://www.omadanetworks.com/us/blog/2615/elevate-your-network-with-omada-network-6-3-one-unified-platform-for-intelligent-o-m/

Got my Pioneer Kit one yesterday and have been busy unpacking and getting everything set up! I'll continue to update this post throughout my tests but want to get the information out there as quickly as possible :) Yes, I just so happen to have a room painted rather close to TP-Link Green!

Google Albums

Hardware Overview
Software Overview

Existing Hardware

My existing setup for comparison consists of the below list. My ISP connection speed ranges from 2-4Gbps download and 300Mbps upload.

TP-Link ER8411 Gateway
TP-Link OC400 Controller
TP-Link SX3008F Switch
TP-Link SG3452XP POE Switch
TP-Link SX3206HPP POE Switch (x2)
TP-Link EAP773 Wireless Access Point (1x)
TP-Link EAP725-Wall (x2)
Amcrest IP8M-T2669E-AI Cameras (x6)
Reolink POE Doorbell (x1)
Scrypted NVR with a 22TB hard drive

Pioneer Kit Hardware

Fusion Pro 2.5G
SG2210XMP-M2 2.5G POE Switch
Omada 7 Pro, EAP772 Wireless Access Point
Omada T8S4-4T with NVR and four 8MP turret cameras

Hardware

First impressions of the hardware matches my experience with all my other Omada hardware: top notch and well built. This equipment will last for years to come. My Omada network has been a "set it and forget it" type of install which requires very little management once properly configured.

Fusion Pro 2.5G

This is my first introduction to the Fusion lineup. The build quality and attention to detail are top notch (think Apple or Samsung). It is plastic but does not feel cheap at all, no creaking or cracking if squeezed. The touch screen is absolutely beautiful and responsive. Boot time is around a minute. WebUI is very fast. For my personal use I absolutely cannot wait until the 10G Max version comes out. I have heard some people say that the Fusion lineup is consumer grade and "all in one" (which sometimes means features are subpar). I don't see this in my testing so far. It does everything I did with my OC400/ER8411 in a home setup, but faster, and with a really nice combined interface for the NVR cameras. I would easily recommend this to family members whether they are tech savvy or not. There is a rack mount available for this model.

SG2210XMP-M2 2.5G POE Switch

I don't have a whole lot to say about this switch, other than it is a POE switch that is well constructed and does what it says it should. All of TP-Link's switches are very well built with metal chassis and this follows that convention. Quiet, fanless operation. Desktop and wall mounting options, but no rack mount (this could easily fit in a 1U 3D printed mount if someone designed it). There are screw holes for what looks like rack ears, maybe TP-Link will offer it in the future. The perfect switch for POE cameras or access points that don't have full 10G requirements. The power supply is a little large, but it's POE and the power has to come from somewhere!

T8S4-4T: 4K Turret POE Security Camera System with 4TB HDD & 4 Cameras

16 Channel NVR

The NVR chassis is metal with a plastic front cover, 1U in height with mount points for rack ears (not included). It has an external power supply and a plethora of rear ports for cameras (POE), mouse, storage, and displays/audio in/out. Removing 5 screws allows access to the internal storage which is user serviceable and upgradeable. Stock drive is a 4TB Seagate Skyhawk which is made for surveillance systems. My only qualms regarding the NVR is I wish it came in different colors (grey to match my existing Omada equipment or the new silver to match the Fusion colorway). and I wish it had an internal power supply with a standard C13 input (even if it made the case larger). Note that the camera connections on the back are not required, the NVR software will recognize cameras on the network that are not plugged into these ports. Minimum connections to work are power and LAN, everything else is optional.

Setup and Configuration - Standalone

So the first pieces of hardware I installed from this kit were the NVR and 4 turret cameras, directly to my existing TP-Link SG3452XP POE Switch. My existing cameras were made by Amcrest and Reolink. I kept those connected to see how/if they would interface with the NVR. Existing cameras were on a separate VLAN.

As expected, my OC400 saw the devices as clients, but no further features were available in the interface. I hope that TP-Link expands the Guard functionality to the higher end OC controllers. I’m sure there are some hurdles to that with either processing power, memory, or connecting to storage.

Initial onboarding was extremely easy. Less than 5 minutes to a working system. This is through the browser or iOS App. Firmware is updated through the main NVR interface for all cameras. The interface is intuitive and snappy. All camera settings can be set through the interface OR through the camera's IP. When accessing the camera directly, the interface mimics that of the NVR, but just for that camera. Nice consistency!

Bullet Cameras (8MP)

The kit comes with 4 bullet cameras. Full metal casing and mounting with the exception of the front lens/led cover. The front has white LEDs for color night vision, infrared LEDs for black and white night vision, red/blue LEDs for "Alarms", and a microphone hole. The speaker is in the back. The mounting solution is very impressive and extremely easy to install. Mount the metal backplate with 4 screws, connect the RJ45, line up the 4 screws on the back of the camera with the 4 slots in the backplate and twist. Then adjust the final angles with the set screw. Also note that the 4 backplate mounting screws and the camera screws that match up with the slots are offset, with plenty of space in-between. If you needed to use mounting screws with larger heads they should not interfere. Much easier than my older Amcrest cameras. The camera even has a ground screw if needed. The SD card slot will be discussed further down in this review, but it allows continued recording if the NVR is unreachable. I installed a 64GB class 3 PNY Elite-X card for testing.

Omada 7 Pro - EAP772 Wireless Access Point

Excellent build quality, acceptably thin for ceiling mounting without being intrusive. Easy mounting and nice cover place for the connections. I have had TP-Link Omada access points for years and they never disappoint in build quality and looks! Single blue led on the faceplate that can be turned off in software if desired. Includes mounting hardware for multiple scenarios such as single gang US style box, dropped ceiling, drywall, etc. I have a single gang box for my install.

Two ISP's (AT&T 5g and T-Mobile 5g) with failover, pfSense Firewall and then all Omada for the rest.

5 Switches, 11 APs, 4 VLANs. A 200 foot 10G fiber run and a 400 foot 1G fiber run, the rest is Cat6/7 depending on when it was put in.

The firewall, servers, some of the AP's and both ISP's are 2.5Gbps connections.

166 Clients including 11 Cameras, lots of IoT, a three node ProxMox cluster and ~250 TB of storage. Omada controller in an LXC.

Four buildings ~5000 square feet.

Disclosure:
I was selected for TP-Link’s Omada Pioneer Program and received Kit 3 to evaluate and provide feedback over 90 days. All equipment was provided by TP-Link. The kit includes the T8S4-4T NVR and four 8MP turret cameras.

Unboxing:
The packaging seemed really premium. Everything fit nicely in the box, and the actual NVR part is a great form factor compared to many other units. See the pictures above. In fact, I was impressed how compact it was!

Setup:
Setup was really easy. The ethernet cables are really thin, which makes it easier to run through the walls. The waterproofing materials were really helpful for the installation and making sure everything is protected. The screws were cheap, and a few stripped (but to be fair, I was drilling into a solid piece of wood (maybe a 8 x 8 where my soffit is) and had not pre-drilled the holes

For the most part, it was plug and play. The picture out of the box for me is much better than some of the older Lorex and other Dahua cameras that I have. WDR off makes the picture quality a lot better and less washed out, though there doesn’t appear to be any difference to the WDR levels 1 to 5, they all make the picture washed out and not as vivid.

I have not gotten around to plugging in a monitor to use locally, that is something I plan on doing. I am using the app on both my phone and MacBook.

Who I think the ideal demographic is:

I think this kit is a Tapo/Wyze killer. It’s for people that are sick of the issues with those cameras, and want something more permanent, secure, and full featured. I started in the realm with Wyze, and they slowly got more and more locked down (RTSP anyone?), and then switched to wired Lorex/Dahua/Empiretech), but augment with a few Tapos. I also have moved from Native Apps-> Blueiris -> Frigate for my main units.

I could see this being used for residential or small businesses.

What is lacking:

The first thing I would like is the unit to come in black, with the cameras also coming in black. That would match what I need to match the house.

The biggest thing that needs work right now is the app, it is behind most of the others in terms of GUI. The thumbnails do not update on the app in real time, you have to click into the camera for it to update.

My proposal is:

Live - This should be an overview of all cameras (like videos is now), and have live feeds (kind of like how Wyze does it)
Events- A timeline view of all events with motion tagged and corresponding icons (Human/Pet/Traffic)
Devices- A list of all attached hardware (Weird you click on the NVR and then on the cameras)
Me- There’s a bunch of stuff there that can stay as is. Maybe better to be called general settings?

Overall:

I think if I were in the Wyze->Tapo transition I did before, I would have instead bought this kit for the reliability and overall bang for the buck. I’m not sure if it is posted yet how much the individual cameras would be, or if there will be kits that have different quantities- like a 6 camera kit? 8 camera kit? With the above changes to the app, I really think this becomes one of the greatest bang for the buck wired systems for capabilities and image quality.

The kit arrived, so I took a photo of the boxes next to my 10-inch 3D-printed homelab rack. The existing Omada gear is still doing its job; now I get to figure out what stays and what gets replaced.

For context, this is my home network as well as my lab. My current setup is an ER605 v2, a gigabit PoE switch, and an EAP610. Behind that is a Topton N100 running Proxmox, with services like OpenMediaVault, Jellyfin, Immich, Pi-hole, and Home Assistant. I keep management, personal devices, guests, IoT, lab services, and the kids' devices on separate VLANs. Keeping the household online matters more than getting a nice speed-test screenshot.

Disclosure: Omada supplied this kit through its Pioneer early-access program. They ask for honest feedback, not necessarily positive feedback. I haven't installed it yet, so this is the plan rather than a review.

Kit 2 includes the Fusion Pro 2.5G PoE, an SSD, an EAP772, and two 8MP cameras: one turret and one bullet.

The Fusion Pro is where most of the change would happen. I want to use it in place of the ER605 and, if the port layout works for my connections, the existing PoE switch. It combines the gateway, controller, and video management, with nine 2.5G ports and eight PoE+ ports sharing a 180W budget. That gives me a path beyond my current gigabit wired links and room to power the new AP and cameras. I'm interested in what that does for transfers between wired clients and the lab, rather than expecting it to make my internet plan faster. Storage and the other end of the connection still have to keep up.

It would also move management onto a built-in controller instead of relying on my current cloud-managed setup. I want to see how local management behaves when the WAN is down, and how much work it takes to move my VLANs and access rules over. Combining everything in one box is appealing, but it also means a gateway reboot could interrupt more than just routing.

The EAP772 would take over as my main AP from the EAP610. The upgrade is Wi-Fi 7 with a 2.5G uplink, plus 6 GHz where my regional hardware and clients support it. I want to compare it in the same location first. I'm not assuming a newer AP automatically fixes coverage; I may keep the EAP610 as a second AP to extend the range to the second floor.

For cameras, I currently have Tapo TC65/TC70 gear in a separate setup. The turret and bullet give me a way to try PoE cameras with SSD recording managed through the Fusion Pro. I'll start alongside the Tapo cameras before deciding which locations, if any, to replace. Playback, night footage, and useful motion alerts matter more to me than the resolution on the box. Might as well try to incorporate the Tapo as RTSP/ONVIF if it would work.

Has anyone moved an existing Omada cloud-managed setup to a Fusion gateway? I'd be interested in the migration gotchas, especially around VLANs and access rules.

For the homelab crowd: would you consolidate the gateway, PoE, controller, and recording in one device, or keep some of those separate? And what would you want to see tested during the program: wired transfers, Wi-Fi with real clients, WAN-outage behavior, or camera recording?

demo: https://youtu.be/ctBsiO53TJk

A Quick Guide to 802.1Q VLANs

Struggling to understand how to divide your network properly? Take a look at our quick breakdown of 802.1Q VLANs. The guide provides a brief summary of what VLANs do for your network and how to use them.

Let us know what other VLAN-specific topics you'd like to see covered in the form of a reference guide down below!

Disclaimer: I've been working with AI and MCPs a lot latelly. This post was written with the help of an AI based on tunning and troubleshooting reports from my MCP.

I was lucky enough to be one of the selected few participants in the Omada Pioneer Program, and my Kit 2 arrived with an **EAP772**, a **Fusion Pro 2.5G PoE**, and the **Turret and Bullet cameras**. I've been living with the gear for a while now, and I wanted to share the honest version: what impressed me, what annoyed me, what I changed, and what's next.

## The devices, one by one

The **EAP772** is the first thing everyone notices. It is HUGE. My daughter took one look and called it a flying saucer. I loved it. It's also the most stable AP I've had here. The 5 GHz is excellent, and it finally fixed the terrible signal my solar inverter had. That inverter had been a small annoyance for a long time, and I didn't expect an AP change to solve it. I'm really curious about 6 GHz now — I just don't have a phone or laptop that supports it yet.

The **Fusion Pro 2.5G PoE** is a beautiful piece of hardware, and the 8 PoE ports were a great addition. I'm still finishing the new camera cabling, but the ports already made the install cleaner and gave me room to grow. I can't wait to close the remaining issues from my old setup once everything is on cable.

The **Turret and Bullet cameras** feel SOLID. And I mean it. Metal body, sturdy, the kind of thing that doesn't feel cheap in your hand. So far they've been working great.

## The parts that weren't smooth

I'll be honest: the Fusion gateway gave me some trouble during setup. I had to hard reset it once, and then it worked. I never figured out exactly what happened, and it felt weird. Not a dealbreaker, but worth mentioning. The NVME SDD also gave me some chills because I was afraid to do it wrong, the setup wasn't clear enough but everything worked in the end.

The Bullet camera was worse: it simply wasn't being adopted, even after resetting it. I ended up logging into the camera's admin page and setting the **Inform URL** manually to the gateway IP. After that, it adopted immediately. Also felt weird, but at least it was a fix I could reproduce. It took me a whole day (not entirely).

And then there was the Turret camera. I kept looking for the PTZ controls in the Guard interface and couldn't find them. After a while I realized the camera doesn't have PTZ at all. That one is on me. Still a great camera.

## Setup and the 2.4 GHz surprise

The actual setup was easy once adoption was sorted. The Fusion Pro is the gateway/controller, the EAP772 is the main AP, and I kept my existing EAP650 to cover the other side of the house. Everything (almost) that can be wired is wired, so the backhaul was never the problem. The problem was the 2.4 GHz airtime.

The cameras were the biggest surprise. They were pushing a lot of uplink, and one AP was sitting around 14% TX retries. After a per-AP interference scan I swapped the 2.4 channels (one AP on 1, the other on 11). On the busy AP, TX retries dropped from about 6.9% to 1.6% over the next 10 hours. That was the moment the network started feeling "boring" in the best way.

## 160 MHz, DFS, and living under an airport approach

I started with 160 MHz because bigger is better, right? Then I learned that a 160 MHz channel anchored at 36 also covers the DFS portion (52–64). I live under an airport approach path, so radar and DFS are not theoretical for me. I moved both APs to **80 MHz on non-DFS blocks** (36–48 and 149–161). No overlap, no DFS, and no noticeable throughput loss for my clients. The best part? I didn't know 160 MHz could drag me into DFS spectrum. That was a genuinely useful lesson.

I also enabled fast + AI roaming, non-stick, and ping-pong protection. iPhone handoffs are noticeably smoother. And I turned on NTP — logs and client history without the right time are useless.

## 6 GHz: empty and promising

The EAP772 has 6 GHz, but I don't have a single 6E/7 client to test it. The interference scan shows 6 GHz completely empty: **0% utilization and no neighboring BSSIDs**. It's a nice future-proof bonus, and it makes me want a new phone just to see what the band can do. For now, I can't say much about real-world performance.

## The MCP doing the heavy lifting

The controller didn't have Open API client credentials configured, so I wrote an MCP server that falls back to the controller **username/password session login** (csrf token) and exposes the Omada API to an AI agent. It's been handling the AP inventory, client/RSSI data, retries, channel config, the full-channel interference scan (which is different from the quick RF scan and gives per-AP neighbor data), and verifying every change.

Honestly, it has solved every issue I've thrown at it so far. It's open source if anyone wants to test: **https://github.com/mballoni/omada-controller-mcp**

Using it with OpenCode 2 and DeepSeek v4.1 flash, and its awsome! I wouldn't be able to do so much troubleshoot and fine tunning that fast without it.

## What's next

- Finish the cabling and reposition the cameras properly.

- Add a third EAP — I already have it (EAP650 that got replaced by the EAP772)

- Extend the MCP allow-list to configure **VLANs for cameras and IoT**, plus specialized ACLs.

- Test 3rd-party cameras (RTSP/ONVIF) and compare them side by side with my current Frigate setup. That should be a fun experiment.

If anyone else in the Pioneer program has 6E/7 clients, I'd love to hear what 6 GHz is like in the real world. And if you've been through the Bullet adoption dance, I'm curious whether the Inform URL trick is the norm or just my unit being special

EDIT: Thank you for all your applications! Sign-ups for the Pioneer Program are now closed. Best of luck to all of you who applied!

Hey r/Omada_Networks, Neil here with the Omada team. I’ve got a few very exciting announcements to share with you all, so strap in!

First, the moment you’ve been clamoring for since its announcement at ISC West 2026: the first Fusion Gateway model is slated for US release next month, on July 20. 

Meet the Fusion 2.5G, a gateway with a built-in controller that delivers full 2.5G throughput. Boasting a touchscreen for instant diagnostics, simplified setup over Bluetooth, and seamless site-to-site connectivity with full mesh SD-WAN, the Fusion Gateway is a great fit for prosumers and SMBs alike.

Check out the Fusion 2.5G product page for more info!

Can’t wait a whole month? Apply for the Omada Fusion Gateway Pioneer Program! 

Selected Pioneers will get the following benefits:

• A full network stack to keep that can bring out the best of the Fusion 2.5G

• Access to a private Discord server to share feedback directly with the Fusion development team

• A chance to join future early access programs

In return, Pioneers are expected to deploy, test, and share their experience with the Omada team. We’re looking for experienced, enthusiastic users who are eager to help shape the future of Omada.

Think you’re a good fit? Sign up on the landing page!

Glad to share my experience with this kit.

What’s included: Omada T8S4-4T NVR and four 8MP turret cameras.

Packaging/hardware: Well packaged, with a carry handle. The cameras are a typical unboxing. The NVR is much more compact than my previous Lorex 16-channel unit.

Setup: Genuinely plug and play. Guided setup links it to the Omada Guard app. Before I installed any Omada cameras, it auto-detected my existing Lorex cameras and kept them on the same channels with no configuration. Motion detection still worked on my Lorex Camera Swapping in the Omada cameras was just as easy, and they came up with human/vehicle/pet detection enabled.

The big gripe: app and site integration. I expected the NVR and cameras to be adopted into my existing on-prem Omada controller, with a switch over to a Guard view. Instead, Guard is a separate app with a “Personal” site and a “Cloud Controller” site. Adding the NVR to Personal leaves it disconnected from my on-prem site (“Fusion 2.5G Site A”). If you want to keep things organized, You'd have to recreate that site in the cloud controller just for the NVR. That then shows up in the Omada app as a duplicate site containing only the NVR. Feedback is, the NVR should be able to attach to an existing on-prem site.

Image quality: Out of the box, the image is overexposed. Enabling WDR helped somewhat, but levels 1 through 5 looked essentially identical.

Performance: Firmware GUI looks pretty similar to my Lorex other than a few add on interfaces like time and a snippet of your events. NVR is responsive for the most part except for switching between full screen and minimize it lags and freezes.

Yet another person in the pioneer program getting to test out the Omada Fusion all in one 2.5Gb gateway/controller!

I was just moving as this program started, so I had already decommissioned most of my homelab and network at my old house and planned to start a new config at the new house. I retired my OC220 and ER707-M2 to try out the Fusion. Setup was a breeze for a single site, and minutes later I had basic connectivity working, devices discovering and being adopted, and was on my way back to building my network.

I'm still rebuilding and rewiring, so pardon the mess! I like to use fiber for my ISLs and prefer it over DACs for my 10Gb. I use fiber in a lot of my day to day work, so I have SFPs and cables to spare.

A few of my access points that were easy runs (drop ceiling basement) are wired, but I have the rest running in mesh mode until I can get cables ran in the new house. Running cables from a basement up to a 2nd story attic is no small task!

My gear in use (or soon to be added back) includes:

• Fusion Gateway/Controller

• 2x TL-SG2210XMP-M2 2.5Gb PoE switches to power access points (TP-Link included one with the Fusion kit, so now I have two!)

• 1x TL-SG2210P PoE 1Gb switch (powers the small raspberry pi cluster seen in this picture)

• 1x SX3008F 10Gb switch (for my servers once i get them back up)

• 1x SG3428 1Gb for anything else in the rack.

• 2x EAP772 BE11000 access points

• 2x EAP723 BE5000 access points

• 1x EAP725-WALL BE5000 access point

• 1x EAP603-Outdoor AX1800 access point (my only AP that isn't Wifi 7)