There are only the deactivated ones from the mobile apps. None from any other integrations.
I go into integrations, then the tp-link integration (from hacs) and then choose devices and pick a device.
Anyone with a Omada enabled switch use one or both of these integrations?
Iâm wanting to be able to toggle the status of an ethernet port on the switch. Both being able to toggle off/on POE power to reboot a camera, phone or access point and just to cut network access.
Wondering if we can get this done currently or not yet.
Thanks
Great!
If you turn off one of those switches does it turn off POE only or it is like you pulled the cable from the switch port and there is no network access for whatever device is plugged in when switch is off?
Thanks for the reply.
Cutting the POE power normally causes whatever is attached (like a camera or access point) to become unpowered and therefore non-operational. Is there a scenario where youâd want/expect the power to be cut but the device to continue working? Or is the question: can you cut internet access for the device while not cutting POE power? I donât think you can currently do that via either of the integrations.
Although I would like to be able to power cycle POE devices I would also like to be able to cut off network access to that port. Iâm wondering about something like a desktop pc that isnât powered by POE.
What Iâd like to be able to do is flip one of these switches in HA for a given port and cut network access like I can with wireless already.
I just wanted to make sure that the switch provided by this integration didnât turn off POE, but left network active if the device doesnât use POE.
Thanks
I only see the device_tracker entity. The entity has a few attributes, but I donât see any other sensors.
Do I need to change any settings for this to work?
Does anyone know why I do not see the Tx, Rx and many more, attributes?
Look at the info on your wireless devices, not on the router itself. For example this is what I see on one of my Shelly switches.
If you donât see the Omada integration listed in the Device Info section (the upper circle in the image), you probably donât have the integration set up properly.
I was going to say, I saw nothing showing up from this, then I reread the installation ionstructions, fixed that properly, and BOOM! Wow, this is FANTASTIC, keep up the great work!
I deleted the integration and installed everything again, but I still get only the Device tracker information.
Remember there are multiple integrations being talked about in this thread. You may need the 2nd one installed to see what youâre looking for.
Ah I didnât catch that either. Using the built-in Omada integration no usage details huh, looks like GitHub - zachcheatham/ha-omada: Home Assistant TP-Link Omada Integration is whatâs needed.
I have both the built-in and the HACS one installed.
Ditto. Bookoo information form both that do not overlap!
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.
I also tried the other Omada integration (GitHub - zachcheatham/ha-omada: Home Assistant TP-Link Omada Integration) and could connect instantly without issues ! 
Could it be because my site is not called âDefaultâ ?
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.
It resolved itself on itâs own for me too