Dear @sp9239,

So, I successfully managed EAP 245 from Discovery Tool but can't see it in the controller.  I am able to login to EAP 245 with IP address. 

 

It's suggested to disable firewall or anti-virus software on the Controller host PC to have a check.

Here is the troubleshooting guide for your reference.

What should I do when the controller fails to discover the EAP?

Hope this information is helpful. Best Regards.

Dear @sp9239,

I followed your steps and installed the Controller v 415 and it detected the EAP 245.

However, I didn't see three EAP 225. 

 

With the discovery tool, can you see the three EAP225? If not, please reset one of EAP225 to have a check:

With it powered on, press and hold the reset hole for about 8 seconds until the LED flashes green-red-yellow.

Besides, verify the EAP225 shows up in your router's DHCP client list, ensure the EAP225 is connected to the same subnet network with the Controller.

Please use the Ping command to ping the EAP225 on the Controller host to check the connectivity between the EAP225 and Controller.

Check your network topology, do you have VLAN configured in your network?

Is there a issue with compatibility version of Controller?

 

Omada Controller 4.1.5 can configure and manage only the devices with supported firmware. If you read the Controller Upgrade Guide, it is compatible with the EAP225 V3 but not for EAP245 V1. However, it should be able to discover the EAP in the same subnet network even if the EAP is not using SDN firmware.