DumbMonit
IntegrationenNetzwerk und Firewalls
TP-Link Omada überwachen mit DumbMonit
BetaA TP-Link Omada controller through its OpenAPI: devices disconnected, CPU and memory saturated, firmware updates offered, clients per site.
DokumentationOffizielle Website: TP-Link Omada
Die Produktbeschreibungen sind englisch, wie im Produkt. Die Beschriftungen der Seite folgen Ihrer Sprache.
Was DumbMonit überwacht
A TP-Link Omada controller through its OpenAPI: access points, switches and gateways that lost the controller, devices waiting to be adopted, devices whose CPU or memory is saturated, firmware updates the controller offers, and the number of clients per site. This integration is written from TP-Link's Omada OpenAPI documentation and has not been tested on a real controller. Every call is a read (apart from the login that obtains the access token). Tell us what breaks.
Typischer Einsatz. Beta. Omada controller: devices disconnected or pending, CPU and memory, firmware updates, clients per site
Beispiele
- Omada software controller
- OC200 / OC300 hardware controller
- EAP access points, TL-SG switches, ER gateways
Wie die Verbindung läuft
Was Sie brauchen
- OpenAPI clientThe client created for DumbMonit under Open API, in Client mode with the Viewer role.
Zu öffnende Netzwerk-Ports
8043/TCPController HTTPS and OpenAPI (software controller, default)443/TCPOnly for hardware controllers (OC200, OC300) and installs behind a reverse proxy
Einrichtungsschritte: Create a read-only OpenAPI client for DumbMonit
In the Omada controller, open Global View → Settings → Platform Integration → Open API and click Add New App.
Name the app as follows, choose the Client access mode and give it the Viewer role on the sites to read.
dumbmonitClick Apply: the controller shows the Omada ID, the Client ID and the Client Secret. Copy them: the secret is shown once.
In DumbMonit, enter the controller address (omada.lan) and the port (8043, or 443 for a hardware controller), then paste the Client ID and the Client secret.
Hinweis. The Omada controller ships a self-signed certificate: tick "Accept an unverifiable certificate" unless you installed your own. The OpenAPI exists from controller version 5.9.