Integration for TP-Link Omada system

Feature Requests
96

I have both the built-in and the HACS one installed.

97

Ditto. Bookoo information form both that do not overlap!

98

Hello, I am trying to connect to https://10.0.0.89:18043 with verify SSL unchecked but all I get is an immediate “Failed to connect” red message in the dialog box.

With the HA Terminal integration I can ping 10.0.0.89 successfully and I can even telnet 10.0.0.89 18043 successfully (It says “Connected to 10.0.0.89”).

For username and password I use the same as when I connect to omada controller through the browser.

I tried to go to home assistant’s Settings > System > Logs but there is nothing logged from the integration.

Is there any other place where I can get a more detailed error than “Failed to connect” ?

Thank you.

99

I also tried the other Omada integration (GitHub - zachcheatham/ha-omada: Home Assistant TP-Link Omada Integration) and could connect instantly without issues ! :hushed:

Could it be because my site is not called “Default” ?

100

Hey,

Did you try it again? I also couldn’t connect it on Tuesday, but it worked on the first try yesterday.

Edit: After I updated HA yesterday.

101

It resolved itself on it’s own for me too

102

I liked the GitHub - zachcheatham/ha-omada: Home Assistant TP-Link Omada Integration integration, The only problem is it adds all the devices as the device tracker.

Instead, If we get the clientList as JSON would be helpful so that we can show that in the UI. I tried forking it and getting the client JSON, but creating a sensor does not work as the sensor state cannot be more than 255 chars and my JSON goes above 10000 chars.
Any suggestion on how to store that big JSON somewhere, so that we can use it for templating or creating a table out of it?

103

Is this not available for the software controller yet? I have mine running in docker and it’s not connecting sadly.
On Unraid. Unless the firewall on the unraid is blocking the port

104

I use both of the Omada integrations (at the same time) and run my software controller in a VM on proxmox.
No issues here. Never used unraid so can’t help there, but it does work with the software controller.

105

migrated my controller over from unraid to proxmox and set up perfectly.
Must be an unraid thing

although very few entities on the integration

106

I use both integrations because they each have different thing they offer. Maybe try both to see if you could get more of what you are looking for.

1 Like
107

I’m not sure why this post made it this far. WTHs asking for integrations is against one of the rules for WTH.

109

Unfortunately, I cannot move this to Feature Requests, I tried. The system does not let me. Therefore you’ll need to recreate the Feature Requests and continue voting there.

Sorry for the inconvenience.

111

https://media1.tenor.com/m/5TpiaukNx80AAAAC/he-man.gif(image larger than 3 MB)

I have the power :wink:

1 Like
112

Noice, and it transferred the votes.

113

If you just want to have all connected clients available in Home Assistant you could create a client sensor with all clients as a single attribute or each client as an individual attribute. The sensor state could be the number of clients or something else

114

The TP-Link router integration is superior to TP-Link Omada integration. Why?
Like, i can´t enable/disable different WIFIs , I can´t click my clients to see any statistics etc. Did I miss some configurations in the omada controller itself? I will download the latest beta and try to contribute a bit.

Edit: I used the wrong integration - zachcheatham/ha-omada is the way to go :smiley:

115

I use zachcheatham/ha-omada and the official one, best of both worlds