BTW, I do have one AP "TOOLING" in OMADA network but under 192.168.0.X network. Not sure whether this relate to why the client connected to "P1-PRODUCTION" AP but IP is from 192.168.0.X ?

  @ClassA  my i ask what kind of controller did u use?, cause i had some problem when i tried to add an AP to the controller :(

Hi  @Vincent-TP ,

Thanks for your advise.I have 2 VLAN ( .0.X and 10.X ) and each with DHCP server. All my APs are connected under 10.X and last week I added one new AP ( TOOLING is 0.X ). After sometime, just noticed P1-PRODUCTION also obtain 0.X IP.

What I need is when computer connected to "TOOLING", then will obtain 0.X IP and the rest will be under 10.X IP.

  @ClassA 

Thank you so much for taking the time to post the issue on TP-Link community!
To better assist you, I've created a support ticket via your registered email address, and escalated it to our support engineer to look into the issue. The ticket ID is TKID241157092, please check your email box and ensure the support email is well received. Thanks!
Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.
Many thanks for your great cooperation and patience!

  @UniFly 

I'm using TP-link OMADA controller. First of all, do you able to discover your new AP in the controller or you can use Advanced IP Scanner to check whether is discoverable within the current network.. Hope this help.

  @ClassA  thanks for the reply, the AP can be adopted on the controller that i used..., but the problem is when i exit the controller or restarting my pc, the controller is unable to opened on the browser, it just downloaded the .jar file... did the omada controller work like this or theres something wrong with my controller?, thanks in advance.