-
Hey, thanks for this :), really appreciate it, I no longer have to use local script :)
I have a question, any plans on implementing API V2 ?
So we could switch from using account to using client/s…
-
### The problem
Implemented the required Omada 2FA Authentication using MS Authenticator. Integration error states Two-factor authentication required for local user (-30165). I have functional local …
-
The plugin currently allows associating a single hostname with an IP address assigned by Omada. I would like to expand this functionality to either:
Support Multiple CNAMEs: Allow configuration o…
-
Have been using beta for several months with no issues, very grateful for the hard work of maintaining this addon. Hoping someone could advise on why the addon will no longer start for me. Here's a sa…
-
### The problem
Upgrading the TP-Link Omada controller to version 5.12.7 seem to break the integration?
### What version of Home Assistant Core has the issue?
core-2023.9.3
### What was the last w…
-
would it be possible to make the order consistent between switches and access points in the output of the "omada clients"?
the output of omada client seems to be:
for physical switches: MAC, IP, Na…
-
There is a simple API example here:
https://github.com/ghaberek/omada-api
awlx updated
4 months ago
-
### Brand Name
Omada
### Website
www.tp-link.com
### Popularity Metric
I don't have access to SimilarWeb
### Official Resources for Icon and Color
https://static.tp-link.com/upload/menu/omada_2…
-
### The problem
As stated in #97393, devices that have been removed from the Omada controller still show in Home Assistant.
### What version of Home Assistant Core has the issue?
core-2024.7.4
###…
-
Add support for the Omada Open API: https://use1-omada-northbound.tplinkcloud.com/doc.html#/home
Mentioned in https://github.com/dougbw/coredns_omada/issues/28