@alfsbhfr, please can you post a screenshot of the AP status in Pending mode just before you adopt them? What's the IP of the system running Omada Controller?

@alfsbhfr, what still puzzles me is how you set the IP of the EAP initially. Do you set it through the built-in web UI?

If so, the issue is that after adopting Omada Controller sets the IP back to DHCP with a fallback IP of 192.168.0.254 during the following configuration phase.

In Omada Controller 3.2.6 a static IP set in older EAP firmwares (not newer ones!) is retained and the EAP reaches (and will stay) in »Connected« state.

The only way I could reproduce the behavior of your EAP 220/Controller combination was to set up Omada Controller 2.7.0 with an old EAP110 (I have no EAP220, but EAP110 HW V1 was very similar in behavior). Don't let you fool by the EAP's HW version the controller shows for the EAP110, it changed with firmware v1.2.0, but still is HW V1.

As you see here the EAP with IP 192.168.1.250 set through the built-in web UI can be adopted and then the controller starts configuring it:

After configuration, it changes to state »Connected«, but now has overwritten the IP with the DHCP fall-back IP:

No communication is possible anymore, so the EAP will reach state »Disconnected« after a while:

Now there is a nasty trick you can try:

Set the EAP's fall-back IP to the IP you want to use. Leave it at DHCP for now, apply it:

In Omada controller adopt the EAP and while the controller is provisioning the EAP, quickly set the EAP's »IP Setting« in the controller to the fall-back IP and apply. I use DHCP fall-back because it's easier to just have to change one digit. If you type as fast as I do, you can set up the static IP in this step already, but then you would have to type in subnet mask and gateway IP also. So maybe you want try with the DHCP fall-back IP first.

You must be really quick in doing so, since the setting needs to be applied before Omada controller starts configuring the EAP:

The controller will then configure the EAP and it finally connects:

At this point you can relax and set a static IP permanently.

This trick even has a »fall-back« itself:

Let's assume you have not been fast enough and the EAP was configured to use the factory default IP 192.168.0.254 again:

All bets are NOT off! Just configure the static IP of the EAP in Omada controller now. It's still in »Disconnected« state, but at least you can open the configuration menu in Omada controller:

Note the IP .250 I just used to show what happens next.

Now hard-reset the EAP to factory defaults by pressing the RESET button. Do not forget the EAP in the controller! Then again log into the EAP's built-in web UI and change static IP (or DHCP fall-back IP if you want). Again note here the IP .254 just for demonstration purposes:

Omada controller will provision and re-configure the EAP it already knows to the new IP setting defined in the config menu.

As you can see, during provisioning it still uses the IP set in the web UI (.254):

But after configuration it will use Omada controller's idea of what the IP should be (.250):

Tricky, but works.

Adoption of EAPs would be MUCH easier if the developers of Omada controller would let the user set the MAC and IP addresses for an EAP not yet adopted. It would require a field to enter the MAC and the IP addresses. An EAP pre-configured in this way could become adopted fully automatically, no further manual adoption would be necessary. That's how I have implemented the registration process in our own controller for gateway routers of our hotspot systems.

@forrest, I fully agree that it is the best solution to use a DHCP server for initial setup, even if it only runs temporarily until the EAPs have been configured.

Just forgot to mention this in the post above, so thank you for adding this info!