@Tshukela 

A 10.100.xx.xx address is a internal DHCP address (Private Class A) so can only really come from a DHCP server, unless manually set

As the OC200 and the EAP225 are neither DHCP servers, it must be coming from a 3rd party device.   My gut feeling is you have a 2nd DHCP on your network.

Check out what Default Gateway and DHCP server is allocating the addresses to you, you may find something like wireshark useful for this.  

  @Philbert 

The OC200 and the TP link outdoor are connected to a router, the gateway is 192.168...... please advice,what must I do?

I also get the IP address 169.254.104.240


Please help me

  @Tshukela you need to post a topology diagram that shows your network and the role of each device. Local IP addresses, which devices are DHCP Server and what range they are set to assign. You could post screen shots of the DHCP page for router and modem and that would be a starting point. You can blur out any external IP address that may be visible.

  @Tshukela 

Hey

An address starting 169.x.x.x is what is known as a APIPA address (Automatic Private IP Addressing), in short it indicates your devices are not getting a DHCP address from a DHCP server.   You therefore have either a DHCP server issue, or some networking issue stopping the DHCP working

Without knowing what your setup is (models, connections, etc) then sadly I cant help you much more than that.

This is my network Topology

@RickJamesBish 

  @Tshukela still need more info. If you take a screenshot of your Archer C5 DHCP page that would be a good start. For example here is mine. If you at least start with that we can work from there.  

Another good screenshot would be of the Omada Controller Devices page and a screenshot of your EAP225 IP Settings. Both of mine are below for an example.

I have 2 static addresses, for the controller and for the EAP Outdoor

@RickJamesBish 

  @Tshukela  can you take a screenshot of your DEVICES list? I see you put a shot of the client list.

I have a suspicion that the 1 minute lease time under DHCP settings of your router is a potential issue and might even be the root of your problem. I would set it to default or at least 120 minutes.

If you have time, post a screenshot of your DEVICE list in Omada that shows your Access Point(s) you have adopted.

  @RickJamesBish 

Yes my DHCP Address Lease Time is 1 minute, the reason being that Ip address allocation becomes full very fast if I leave the default Address Lease Time. What is your advice in case I need my DHCP to broadcast more than 200 ip addresses?

Below is a screenshot of the adopted device

  @Tshukela 

I cannot see your subnet mask. Look on your TPlink Router status page for the LAN Subnet Mask, it should look like 255.255.255.0.

This is what I would do.

1. Make sure subnet mask is 255.255.255.0

2. Change start / end IP range to 192.168.0.1 - 192.168.0.254

3. Least time 360 or greater

I think the odd IP addressed you are seeing are likely set by the device when it fails to get an address from DHCP.