Skip to content
Home Assistant TestFlight
Blinds & curtains

TP-Link Omada Open API

bullitt186/ha-omada-open-api · vv1.11.1

HACSCloud polling

TP-Link Omada SDN integration for Home Assistant, monitor APs, switches, gateways, and clients with sensors, device trackers, PoE control, firmware updates, and more via the Omada Open API.

In Apple Home through HomeKit Bridge

What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.

EntityShows up asNote
switchSwitch or outlet
binary_sensorSensor (motion, contact, leak, smoke…)
sensorSensor (temperature, humidity, air quality…)
buttonButton (as a switch)
device_trackerPresence (as an occupancy sensor)

How it connects

Cloud polling

Goes through the maker’s cloud, asking it for updates every so often. Needs the internet and an account.

Details

Installs (analytics)187 (0.03%)
GitHub stars41
Latest versionv1.11.1 (2026-10-20)
Set up in the UIYes
Maintainers@bullitt186
LicenseMIT

Devices listed in its README

  • Controllers: OC300, software controllers, cloud-managed controllers, and OC200 controllers running firmware that exposes Open API (confirmed on 6.2.10.18)
  • Fusion Gateways: TP-Link Omada Fusion series (built-in controller, no separate hardware controller required)
  • Access Points: EAP series (WiFi 5/6/6E/7, indoor & outdoor)
  • Switches: JetStream and Smart Managed switches (PoE and non-PoE)
  • Gateways: ER and SafeStream series
  • Clients: Any device connected to the Omada network (wireless and wired)

Limitations from the README

  • Cloud dependency: Cloud controllers require internet connectivity
  • DPI required: Application traffic monitoring needs DPI enabled on the gateway
  • Local controller: Requires Open API enabled (not available on all firmware versions)
  • Fusion Gateway: Single-site only; no Open API app creation UI (uses web-session auth instead)
  • API rate limits: Respected automatically; rarely an issue with default polling intervals
  • Viewer-only credentials: Monitoring remains available, but controls require the matching endpoint permissions; only the site-wide LED switch has a setup-time permission probe

In ReReHome

Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.

Bridges get their own settings page listing the accessories behind them.