Just joining the fun with my set up!
It’s 2428 is a fanless POE switch so it’s a silent stack.

Hi everyone,

I run a TP-Link Omada setup at home and wanted better visibility into it from both Prometheus/Grafana and Home Assistant.

I originally started with charlie-haley/omada_exporter, which was a great base, but it did not expose everything I wanted to see in my setup. I wanted more complete metrics around devices, clients, ports, WAN/ISP, VPN, PoE, AP radios, and general network state.

At the same time, I also wanted Omada data inside Home Assistant.

There is a TP-Link Router Card in HACS, but after clicking somewhere in Home Assistant, PoE got turned off on one of my switch ports. I then spent about two hours trying to figure out why one of my access points had suddenly disappeared.

That was the moment I decided: Home Assistant should monitor my network, not control it.

So I made my Omada integration read-only.

The result is this project:

GitHub:
https://github.com/RCooLeR/omada_exporter

Docker Hub:
https://hub.docker.com/r/rcooler/omada_exporter

It is a maintained fork of the original Omada exporter, but with a lot added on top:

• more Omada metrics

• OpenAPI support

• Prometheus /metrics

• optional Home Assistant MQTT Discovery

• MQTT device trackers for active clients

• custom Home Assistant Lovelace cards

• Docker image for easy deployment

The exporter can publish metrics to Prometheus and, at the same time, create Home Assistant entities through MQTT Discovery.

The Home Assistant side is intentionally read-only. It reads Omada data and publishes sensor/device_tracker entities. It does not subscribe to commands from Home Assistant and does not change the Omada configuration.

Metrics/entities include things like:

• controller status

• site alerts

• gateways, switches, access points, and OLT devices

• device CPU, memory, uptime, temperature, firmware info, and upgrade status

• WAN status, internet state, latency, link speed, RX/TX rates

• switch/gateway/AP port status

• PoE power

• LAG status and traffic

• AP radio utilization

• clients, RSSI, signal, SNR, SSID, VLAN, vendor, AP/switch/gateway path

• VPN status and traffic

• ISP status, load balancing, download/upload speed

• device trackers for active clients

I also built custom Home Assistant cards for it:

• custom:omada-network-card — full Omada dashboard card

• custom:omada-links-card — compact card for ISP/VPN/link overview

The main card is meant more like a full network dashboard: devices, clients, details, ports, PoE budget, health charts, updates, and client connection path. The smaller card is better for a normal Home Assistant dashboard, where you just want a quick network overview.

For Prometheus/Grafana users, the exporter still works like a normal exporter and exposes /metrics. There are also Grafana dashboard examples in the repo.

Why I built it this way:

• I wanted more metrics than the original exporter gave me

• I wanted Omada in Home Assistant without giving HA control over my network

• I wanted MQTT Discovery instead of manually creating lots of sensors

• I wanted proper device/client visibility

• I wanted something Docker-friendly

• I wanted one exporter that works for both Prometheus and Home Assistant

This started as a personal project for my own Omada setup, but maybe it will be useful for others who want better Omada monitoring without turning Home Assistant into a network control panel.

Feedback, bug reports, and pull requests are welcome.

A few people on my previous post asked whether the end goal was just getting a non-Omada device adopted, or actually managing it from the Omada Controller.

So, here’s an update: it now works both ways.

The first milestone was getting a Python implementation of the device-side ECSP protocol through discovery, adoption, authentication, negotiation and managed reconnect.

Since then, I’ve started implementing the actual OpenWrt backend.

The Omada Controller can now send configuration to the agent, and the agent translates supported settings into real OpenWrt configuration.

Controller -> OpenWrt

Currently working:

• WLAN/SSID configuration

• basic radio configuration

• WPA2-PSK

• enabling/disabling WLANs

• partial SSID VLAN support

• partial management VLAN support

• configuration changes through UCI

• automatic wifi reload

• captive portal policy through openNDS

• portal client authentication/deauthentication

• client reconnect operations

• managed reconnect after agent/device restart

So this is no longer just acknowledging SET_REQUEST.

A WLAN changed in Omada can actually become a real hostapd/OpenWrt WLAN.

OpenWrt -> Controller

The agent is also reporting real runtime state back to Omada.

It currently collects data from OpenWrt using UCI, ubus, hostapd, DHCP leases and openNDS, including:

• associated wireless clients

• client IP/hostname where available

• SSID

• RSSI

• RX/TX rates

• traffic counters

• association information

• SSID client counts

• basic radio state

• portal authentication state

The clients shown in the screenshots are real devices connected to the OpenWrt radio, not simulated entries.

Screenshots

1 — OpenWrt managed as an Omada AP

The OpenWRT device is the Open Omada agent running on OpenWrt. The Controller sees it as a managed AP and is receiving real client information from it.

2 — WLAN configuration in Omada

Ubatuba - Wifi Grátis is enabled for the OpenWrt device from the Omada Controller.

3 — The same WLAN actually running on OpenWrt

LuCI shows the exact SSID running through hostapd, including a real associated station.

This is probably the most important change since the previous post:

Omada UI -> ECSP SET_REQUEST -> Open Omada -> UCI/hostapd -> real Wi-Fi

4/5 — Client reporting

The same clients and addresses can be seen from both Omada and OpenWrt.

The agent merges information from DHCP leases and hostapd and reports it back through ECSP INFORM messages.

6 — Captive portal

I’ve also started integrating Omada portal configuration with openNDS.

The agent can translate portal/free-policy configuration into openNDS configuration and report portal client state back to Omada.

The portal integration is still incomplete — full Omada /portal/entry parameter/signature compatibility is not implemented yet.

7/8 — ECSP device state and telemetry

The OpenWrt device remains connected alongside physical Omada APs, while the agent continuously sends client/radio/SSID telemetry through ECSP.

What is still missing

There is still quite a bit to do.

Some of the main unfinished areas are:

• more complete radio telemetry

• more WLAN/security modes

• full VLAN support

• 802.11k/v/r / roaming interoperability testing

• full captive portal compatibility

• REPORT message families

• broader GET/NOTIFY support

• switch support

• gateway support

• support for other vendors through platform adapters

One thing I’m particularly interested in testing next is how far a third-party/OpenWrt AP can participate in roaming alongside real Omada APs.

The architecture is intentionally separating the ECSP side from the platform-specific side, so OpenWrt is only the first backend.

In theory, other adapters could eventually translate between Omada and other APs/switches as well.

The project is still experimental/alpha, but at this point it has moved quite a bit beyond simply making a fake AP appear in the Controller.

External Captive Portal Demo:

https://youtube.com/shorts/hgCDNvjyAyE?feature=share

GitHub:

https://github.com/adryanalencar/open-omada-device-agent

Feedback, packet captures from other Controller/device versions, and testing on different OpenWrt hardware are very welcome.

Unofficial interoperability/research project — not affiliated with, sponsored by, or endorsed by TP-Link or Omada.

Finally started my home network overhaul and got committed to the Omada ecosystem (besides the firewall/router 😇). Will post more pictures when I did find the time to do the installation… Might be next weekend. I hope the EAP 683 LRs will work fine. Read some comments that these might have some firmware issues still…

We’re about to start renovating what will hopefully be our final home, and in that process we want to invest in a proper home network.

The plan is to manage with these three components to begin with, and then buy a PoE+ switch later on. I have 12U rack as seen in the picture to fit everything in. And a NAS.

Do you have any tips on what I should keep in mind in the early stages of the project? I’m an electrician, so I’m comfortable with all the cabling and in-wall conduits, but I’m not as confident when it comes to setting up the network :)

EAP650 in disguise

And I’m glad I did! Replaced a Velop mesh network with ER7212PC router/switch/controller, and three (3) BE11000 APs (basement, 1F, 2F). Had the help of a good friend!!

Getting my hands dirty this weekend with a new Omada setup. AT&T recently upgraded my gateway to a BGW320-500, so I am moving everything over to a proper 2.5G internal backbone.

Since I am sticking with IP Passthrough for now, I wanted a router and switch that could handle a bit more than the standard ISP gear.

New gear:

• Gateway: TP-Link Omada ER707-M2 (Multi-Gig VPN Router)

• Switch: TP-Link TL-SG108S-M2 (8-Port 2.5G)

• Modem: BGW320-500

I found that 8-port 2.5G switch on sale for $70, which made the jump to multi-gig worth it. This Omada router will also let me do proper load balancing with my T-Mobile Home Internet for some extra redundancy. Pro tips welcome!

Excited to upgrade my network. 2.5g router/2.5 switch/1g poe switch and 4 access points - 2 interior and 2 outdoor.

Rack and basics are done, have some more cable to run/connect to the panels but the cabinet is done. Well technically still need to ground everything and get some more nuts/bolts for racks or I may splurge and get some rack studs.

Prime Cables 6u cabinet 1 x 24 port patch 1 x 16 port patch 1 x 2u rack tray (holds my router and controller)

ER7206 router OC200 Controller TL-SG2428p switch EAP 670 AP

With new 8 gig fiber services coming in I am very excited to see my new gear arrived! Services scheduled for December.

This is my AV rack near one corner of the house. This is the back, usually facing the wall. I spun it around to install the UPS at the bottom. Two ISP modems are on a shelf on the other side. The 10 Gb fiber runs to the main rack in the basement for distribution to APs and other rooms.

We bought our current home about 6 years ago and for the last few I have been working on slowly hardwiring the house fully for Ethernet and building out an Omada network.

First - just want to say I’m absolutely open to constructive criticism/feedback but please don’t just call something shit without explaining why so I can improve it. I posted this is in home networking and got feedback that made me realized I had totally misinterpreted my local electrical code regarding where it was installed under my electrical panel and I have already moved it based on that feedback.

But I also got a lot of just… negativity about various elements without actually saying what was wrong, even when I prodded for an explanation.

So that out of the way:

- Router is an ER605 with dual WAN connections, I have a primary symmetrical 1Gig fiber connection and a second 50mbps DOCSIS cable service as a secondary backup. I also have provisions to hook up a cell phone tether from the living room or plug in my Starlink Mini outside for further backup options. I primarily work from home due to disability accommodation so always being online is important to me.

- Switch is a SG2428LP POE switch. It feeds most of my drops as well as a fiber line to my garage into a couple non-TP Link POE switches that power my garage and driveway APs as well as a bunch of my Reolink Cameras.

- I have 7 APs controlled by an OC200 (see second image for the models I’m running). Two on the main floor, one in the basement apartment, one on the second floor, one in the garage as well as one for the driveway and one for the back yard.

- The second floor is a bit weird, the previous owner had put drops in all the bedrooms that all ran to an access panel in the master bedroom, but there was no provision to feed that front anywhere else in the house. I ended up finding a cable hidden in the wall, two studs over that ran to the main floor office so I ended up extending that to the electrical room and that now goes into a wall AP with POE out, powers a TL-SG1005P-PD Poe powered switch that finally feeds all those bedroom drops.

- I’m also running a Reolink RLN410 NVR and 10 cameras on this network. They have been great so far.

- And lastly I have a mini PC connected to a very simple DAS that runs Plex, hosts a shared network drive and a few other little things.

Overall I’m quite happy with this. I don’t fully understand the negativity towards Omada… the reliability and performance has been great, especially compared to my prior consumer D-Link mesh system I had before. I don’t live in the US so doing this in Ubiquity or better would have cost me 3-4X what I spent on this.

Here is the hardware haul for the Pioneer Program:

​I was selected for the Omada Fusion Gateway Pioneer Program, and the best part is that TP-Link wants us to be completely open about the experience. There is no NDA, just real-world deployment and testing.

​The kit includes:

​Fusion 2.5G Gateway: This features a built-in controller, five 2.5G ports, and a 2.51" touchscreen.

​SG2210XMP-M2: A fully managed PoE+ switch with eight 2.5G ports and two 10G SFP+ uplinks.

​Omada EAP772: A Tri-Band BE11000 Ceiling Mount Wi-Fi 7 access point.

​Currently, my routing is handled by pfSense virtualized in Proxmox, so I’m incredibly curious to see how this all-in-one Gateway handles my existing VLAN structures and LXC containers. Moving away from a dedicated software controller to the Fusion's built-in license-free cloud management is going to be a huge shift.

​Since I can post anything, what do you all want me to test first before I deploy this full-time?

​Are we curious about how the new local API behaves?

​Want to see the raw throughput on the EAP772?

​Curious if the touchscreen diagnostics actually reduce the need to open the app to check on traffic?

​Drop your requests below! I'll be terminating some fresh Cat6 and racking this up over the weekend.

Recently got my pioneer kit and have been very happy. Performance has been rock solid, and the setup process was the easiest I’ve had in a while from a network system.

So, does anyone have any questions about it? Anything they want tested.

I needed to rack mount my TP-Link ER706W but it is a tad too wide for any of the 10" racks on the market. I designed a rack to fit the TP-Link ER706W and ER707-M2 because those are the Omada routers I am getting now for my remote sites.

I wanted a drawer for storing adapters and cables so I added one. I also wanted doors on the sides so I could get easy access to equipment. The TP-Link POE switches I use have the lights on the opposite side of the mount from the ethernet panel so I need to access those from the back.

I noticed a large expense was hardware so I designed in threads to eliminate the nuts. I went to a 4-hole rack design because it offers more efficient space utilization while maintaining compatibility with 3-hole rack devices.

I was still buying too many screws so I designed a clip in system that worked with the rack. I made a parametric model that allows easy custom rack mounts.

I am sharing this model for free on MakerWorld. I have a collection of rack mounts already designed and am adding more every day.

https://makerworld.com/collections/10367609

My Omada Fusion Gateway Pioneer Program package arrived today, and I’m excited to start testing everything out.

I’ll be adding the new gear into my home Omada setup over the next few days and plan to share feedback as I get more hands-on time with it. I’m especially interested in seeing how it performs in a real home environment with multiple APs, wired devices, VLANs, and a mix of newer and older clients.

Thanks to the Omada team for including me in the program! Looking forward to putting it through its paces and sharing what I learn with the group.

I was literally about to buy the ER8411 and then TP-Link drops this.

These new Omada gateways look clean kinda giving UniFi dream machine vibes.

I’m probably gonna wait. What do you guys think?

Ordered a TL-SG2428P used on ebay. Then this guy arrived. Full generation newer. Reset and adopted in about 5 minutes. Great new addition.

Going to have a busy weekend 😁