Hi @rockin,

I agree with you, but, I'm trying to keep an open mind given that the SDN interface is a brand new product (unlike the older Omada SW) and the current release is the first initial public offering.  I know R1D2 and others are working hard to provide good feedback to TP-Link to improve the product, and let's not forget that it is free.

But I totally agree with you.  The interface is horribly cluttered with features and capabilities that are unusable unless you have the full suite of SDN compatible equipment (much of which isn't available yet, or is only just becoming available).  And even if you do, the functionality exposed in the SDN interface is significantly less than what can be done from the Web GUI's of unmanaged devices.

I'm torn, because I like being able to see what is possible, for example, if I purchased a managed switch or gateway (I actually did actually buy a switch because of this) -- like in a demo mode or similar.  But I would also like to be able to hide all of the stuff I cannot do so that I can actually find the relevant functionality for the hardware I have.  This could be accomplished with a setup wizard or various user profiles which hide / only display "opted in" equipment or feature sets.

I would also like to be able to add unmanaged / non-TP-Link network components to the connectivity tree for documentation purposes and potentially basic health checks (e.g. ping, perhaps SNMP).  Reporting and notification options for both Omada and the SDN still seem woefully inadequate.

I do miss the older Omada software mainly because I was comfortable with it, and because it was "simpler."  That is to say, it only managed the EAP aspect of the puzzle.  The new SDN software is a much more ambitious offering.

There should be a new SDN version out any day now.  I see the stand alone software on the update page, but the version for the OC-200 hasn't been released yet.  I'm sure the SDN will continue to improve, but TP-Link is generally "more methodical" with their software updates -- typically every 4 to 6 months.

So, in summary, I would say that I applaud TP-Link's effort.  I think the value they offer for the price is incredible.  And their software is still a lot better than Cisco (-:

-Jonathan

I should add,

That as a SOHO user myself (2xEAP245, 2xEAP225-OD, T1500G-8T v2.0, OC-200), the SDN is not really for "us" per se.  It's really targeting much larger deployments.

Even Omada, at first, was a little overwhelming -- compared to the simplicity of one or two web management pages.

But as more and more SOHO / Home Power Users / Enthusiasts upgrade, TP-Link might need to consider an "SDN/Omada Light" type application.

I'm also not sure it makes sense to bundle the device firmwares with the management software the way they do.  I'd rather see firmwares be completed separate (but still upgradeable through Omada/SDN) and then update Omada to be compatible with the same "SDN API" that the SDN SW uses so that one could use either management product with the newer firmware.

But, I'm sure they don't want to support both platforms, long term, going forward.

-Jonathan

Hi @rockin 

The new OC-200 firmware 1.7.1 just came out.  It incorporates the new Omada SDN version 2.4.2.  TP-Link has definitely made a number of improvements to de-clutter the interface.

I'm still finding my way around, but it does seem like the UI is more dynamic now based on the device hardware you actually have.

I see some new? settings as well:

Settings => Maintenance => User Interface => Fixed Menu

Settings=> Site => Application Scenario (Mine defaulted to "Home" -- not sure what effect these have)

And my email forwarding through Amazon AWS SES is working now!  Yea!

-Jonathan