TP-Link Omada Controller as device_tracker?

No, unfortunately not.

That’s a bummer. Was thinking more on it and maybe not a priority to HA, given it can only track wifi devices and no LAN devices. For my purposes, that’s all I really care about for presence detection. Wish I was a better programmer…

Did you try snmp? https://www.home-assistant.io/integrations/snmp/

I could enable snmp on my TP-Link AP, and query it, but the device lacked a client list… A more professional (expensive) device could/should work imho

EDIT: ps I think the ‘removed’ functionality you mention is still available as a custom component, see the thread here TPLink Router Device Tracker

1 Like

Unfortunately, it looks like I can only enable snmp on the individual APs if I disable the controller, which is not going to happen.

I’ll look into the custom component, thanks!

I have two EAP245’s and am running omada so I’m interested in this as well. I believe that you can turn off omada (disconnect the AP’s), then log in to each one and turn on SNMP support, then turn omada back on and re-add the AP’s. Even though you can’t get to the AP individual setups anymore, the SNMP mode is still active. I haven’t done this yet, but I remember reading about somewhere. Here are the EAP MIB’s: http://static.tp-link.com/EAP_Private_Mibs_1.0.zip.

1 Like

This may have changed since you guys looked, but you can enable snmp site wide under the omada settings and then services menu.

2 Likes

Thanks for the tip Chris.
I have SNMP enabled across both my EAP-225 V3 now by selecting it in the Omada SDN controller software under “Services” I have created a couple of sensors and they work fine as indicators of whether the AP is up or not. (unknown means its down!)

image

I have the MIB for v1 and v2 of the EAPs and that helped, but there is no v3 MIB for download as far as I can see. I think I can identify the OID for REBOOT from the MIB I have, but I cant figure out if I can switch off a particular SSID from SNMP without fuller MIB info. - Is that even possible?

Sorry about reviving an old thread, but I recently setup 3x EAP265 HDs and a TR7206 at home and have the Omada Software Controller running using mbentley’s Docker image.

I have found that I can connect to the controller’s MongoDB instance and query the collections for client information, speedtest results, and Omada device info.

I am now deciding on which route to take to get this working in HA - should I create a bash script or golang program that can I can run periodically to publish the data to MQTT, or go down the route of (learning python and HA’s Dev process and) creating a custom component that can be configured to be poll the MongoDB collections for the data I want?

I am considering the MQTT solution as an interim step while I get the custom component built, but I am aware that if I get the MQTT system working, the incentive to build the component is lost.

1 Like

A custom component for this would be fantastic, but I agree that it would be a lot more work to create and maintain it.

See https://github.com/zachcheatham/ha-omada. Needs to be installed via HACS and is a work in progress.

2 Likes

I briefly used omada’s controller with ha. With nodered I was able to log in and get a realtime print from the syslog. It seemed like everything was being reported but I didn’t use it long enough to parse what was actually coming through.

That is awesome, thanks for the information. I will see what I can do to contribute to this then.

Just found out bout this, which is great news ! I’m not a programmer but can test / contribute to the project.
Another thing might be if we can create an add-on for Omada controller to run in HA as container.

1 Like

I don’t own Omada hardware yet, but I’m looking into what kind of access point I would be interested in buying. Isn’t this addon what you are looking for GeertV? Hassio-Addons/README.md at 1dd68aef12cfd7fdbe2dd2ee98258ec487315006 · MattFryer/Hassio-Addons · GitHub

Absolutely :slight_smile: Many thanks, I was reading into creating an add-on myself…

So would an addon like this enable Home Assistant to be able to block clients attached to the APs?
I’m looking for a way to block my kids from getting online at certain times. Also looking into the omada ecosystem for a network rebuild so I would be very interested if this were possible.

I can see 2 different Omada controller addons for HA.

Did anyone managed to make any of these work?

This one does for device tracker:

Bad thing is that it automatically adds every client as an entity. I would rather it brought them in as disabled and let you choose which ones you want to track instead.

I’m hoping they can get to the point where you can turn a certain wireless acces point and switch ports on and off.

@Mikefila fyi the devices are the one sending the logs, not omada-controller. This might have work for you but … not all devices are made identical. I had made a report to tp-link thinking it was an issue with the controller.

I have a EAP660HD, it works great. It was their top of the line when I bought it ~a year ago… and whatever they use to syslog, it doesn’t work.

I stumble on your message cuz I’m digging around to find a better solution… the device tracker don’t get updated fast enough. It takes at times 10-20m for the update to arrive. If a company requires to follow who’s on the network and who isn’t in case of a “bad actor” and have proper “timestamps” , then tp-link isn’t for corporate.

Sorry about reviving an old thread, 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?