@Fae 

Why would you advertise the product can do the following, if you aren't able to get full functionality when its being managed by OC200?

https://www.tp-link.com/us/business-networking/poe-switch/tl-sg2008p/

• Integrated into Omada SDN: Zero-Touch Provisioning (ZTP)^**, Centralized Cloud Management, and Intelligent Monitoring.
• Centralized Management: Cloud access and Omada app for ultra convenience and easy management.

Do you have any switches that are 8 port with POE that can be fully managed by OC200?  If i knew that the TL-SG2008P couldn't be fully managed I wouldn't have bought it.  I don't want to use the product in standalone mode, that is why i bought the OC200.

This is not cool.

@Fae Same here, all of the features are expected.
If not then advertice as an Cloud compatible device when it's not.

Hi @HA4g3n @rspinell 

I don't know if @Fae can or can not confirm my point of view, but if I'm wrong someway, please correct me.

Long story short:

TP-Link has very mature and reliable hardware network products. Each single one alone (usually) do exactly what's someone expect it to do and I believe that everything is exhaustively tested for standards compliance. And they are not expensive.

Nowadays, in most of private and public organizations, the IT/networking needs and requirements to keep organization operations running, makes any sysadmin life miserable and a pain in the ass if one has to setup every single device in each site, building, floor... etc. Also, any switch, router, AP, ... whatever device/product is a simple "consumable" like a ink cartridge or toner.

So, in a network/internet perspective, how to maintain everything working in a organization, whose managers and decision makers usually don't understand nothing about networking but require to mix departments, workers, services, spaces, building management and utilities, just "because"? One solution is SDN. Assuming that most of hardware has more or less same networking capabilities/features. Only the load/performance of the devices may vary.

On top of this mesh of devices, one specify a virtual/logic/abstract network of components of the organization. The switches, routers, AP, controllers just behave in order to comply with that logical networks. QoS? There's no QoS here... because network requirements are all the same withn logic applications.

So why TP-Link advertise a lot of features same time they refer "centralized controller" or "omada"? Because it's true.

"Omada" product it's a "SDN solution", not a centralized proxy for every single webpages for all TP-link products. For those (like me) that would like to have some way to manage our few tp-link devices, "Omada" might not be exactly what we expect.

There's hope! Omada SDN is a java solution, under development right now, and we can only complain and complain to TP-Link to implement more features on controller side, or even better, provide omada services API.

Dear @Fae,

Thank you very much for the fast reply.

When I mention an API to omada was simply to make a little pression here in the foruns. I'm very pleased to know about the API.

I would love to be Devil's Advocate and check current draft of controller 5.1 API :)

I already check API 3.0 and 4.1.5 drafts. The only thing that I didn't found anywhere but that I think is essential in all APIs is some kind of push messages. The API 3.0 and 4.1.5 only use REST (request/response) and that's not efficient to react and get most accurate/fresh system/platform status overview.

For some time that I design this kind of "stuff" and some pub/sub channel is now a MUST.

Once again, thank you and greetings to all involved on omada initiative for the omada momentum.

BR,

João Pedro Taveira