I'm mainly interested in monitoring, rather than controlling anything.
I have some rough code to Login get the Site list and Device and Client details per site.
I think that's probably about all I need from the API really.
If I were to create a custom node what features might you like to see ?
Thats a good start and in a home environment enough i guess.
I would also like to see management rather than reporting - but if you start the heavy lifting i might then jump on board with feature requests for V2 !!
From a reporting point of view and single pain of glass (i.e. just using NR) it would be nice to see the online status of all devices in the plant/site, last reboot time and FW version. Click on a node and be able to get reporting on VLAN membership and SSID matchup
At the switch port level - click on a switch and show to top 10 busiest ports and the names they have been assigned, click on a port and show VLAN membership
I have an ER7212PC v1. Iāll never buy junk from TP-Link again.
There are slow and no new features, and the additional antenna barely delivers 15% of the performance itās supposed to.
I donāt even feel like connecting it to Node-RED.
I can imagine that its not super responsive as it doesn't have much processing grunt.
I run omada on my Pi5 using the mbentley docker image and it is very responsive both in the browser gui and via the API.
I don't really have any complaints myself, considering that TP-Link omada kit is orders of magnitude cheaper than Cisco and the like, while still providing professional-grade features.
So after some head scratching about which of the APIs and methods to use I have settled on the Omada Open API, there is documentation available for this hosted on your local Omada server at https://xxx.xxx.xxx.xxx:8043/doc.html#/home
Still very much a WIP, but if you have any useful feedback let me know.
To access the Open API, first create an application at Settings > Platform Integration in Global view.
My function uses Client mode: You can define the Application name and access permissions. When calling the interface in this mode, the rights are the same as the login Application.
2ćAfter the creation is successful, each Application will have a corresponding client ID and client secret, which will be used for subsequent access to the Open API.
Edit the function "On Start" tab to add your server IP, port and credentials.
There are a few inject nodes to call some different endpoints, utilising different supported options.
AI generated help guide ?
Message Properties Overview
Property
Type
Required
Default
Description
endpoint
string
Yes
"devices"
API endpoint path
method
string
No
"GET"
HTTP method
params
object
No
{}
Query parameters
body
object
No
null
Request body for POST/PUT
siteId
string
No*
-
Specific site ID
siteName
string
No*
-
Site name (resolved to ID)
apiVersion
string/number
No
"v1"
API version override
pagination
boolean
No
false
Enable pagination
page
number
No
1
Page number**
pageSize
number
No
100
Items per page**
forceLogin
boolean
No
false
Force re-authentication
*Either siteId or siteName can be used. If neither, default site is used.
** Only used when pagination: true
Have fun, I can think of many possible uses for this in home automation already
Is the EAP670 wired to router or wifi. You will probably find the bottle neck is the wifi or cable it is connected to.
I have Installed EAP650's that over mesh (connected to wifi 6 capable router) deliver 500Mbps, but when wired on POE and 100mbps 75m cable only give 70mbps due to cable Bottle neck.