[APP][Pro] TP-Link Omada

I see you tried 192.168.3.1, did you also try it with 192.168.6.15? Also, which controller do you have (OC200/OC300/OC400 box or Omada software controller)?

when I fill in my email up and password got the message something went wrong try again what do I wrong ? 0c200

Can you share a diagnostics report (More->Apps->TP-Link Omada->Settings (top right corner)->Create diagnostics report)?

Yep, I tried with both 192.168.6.15 as well as 192.168.3.1. I use the self hosted Docker variant of the controller.

Version 1.0.10

  • Added port number setting

Version 1.0.11

  • Added more logging

Version 1.0.12

  • Fixed client list for Omada v6.2

Version 1.0.13

  • Update dependencies

It all works now. Thanks again for the awesome app!

Hi smarthomesven!

Thanks for creating this app :slight_smile:
When I try to login I get the message ‘Something went wrong, please try again’. I’ve tried with port number 8043, but also with 80, this should just be the port of the web interface right? I have a OC200 controller. My diagnostics report: f2cf3601-51d8-44d0-bdb1-fc31c984f353.

Yes, it’s the port of the web interface. Is your Omada controller at port 8043? Note that 80 is not a valid port here (Omada uses HTTPS, so that would be port 443)

Ah, the app is trying to connect via https of course, so I should use 433! My controller also runs on http port 80.

Now it unfortunately says ‘Er zijn geen nieuwe apparaten gevonden’.

Diagnostic report: 6d95c4ed-d5e4-4d16-8d9d-d2a5ae11f104

Is your Omada controller at the latest version (6.2)? Omada recently changed the method for retrieving the client list, so I had to change it in my app as well.

Version 1.0.14

  • Fixed Flow cards
  • Removed reconnect capability and Flow card from wired clients (reconnect is only available on wireless clients)

Version 1.0.15

  • Fixed wireless type detection

Hi @Mark1541 , is the issue fixed in the latest version of the app?

Version 1.0.16

  • Added debug page

Hi @RLucassen , is the issue fixed in the latest version?

Hi @smarthomesven, yes, the issue was indeed an older version of the firmware on my controller, now works great!! Thanks again :smiley:

Version 1.0.17

  • Update dependencies