@Virgo Hello

Thank for replying.

I used the devices onboard webpage to adopt it, pointing to either the FQDN our self-hosted server is using, or it's wan ip address.

Since the onboard webpage is disabled after adopting, I can no longer enter a different FQDN or ip.

It was never needed to enter a port number.

The problem still remains that I need to check which devices are adopted uning ip address.

I can ssh into some of the ER605's using another (non-omada) device, but I need to know the command to get the inform address.

I will install a new server at the new location and perform a controller migration, but I like to know before hand which devices might experience problems.

Factory resetting/forgetting and readopting devices is not an option considering some of our customers are more than a few hours travel away.

  @Virgo Still apreciate you trying to help me

The adopt screen in the local web of a non-managed EAP225 looks like this:

Here either the wan ip address or fqdn of the remote server was entered.
I only need to check on each device which address (wan or fqdn) was enter when they were adopted.

If it was the fqdn, then I have nothing to worry about.
If it was the wan ip however.....

Related question:

When doing a controller migration, there is a field for the new controller address.
Does anyone know if the new ip/fqdn is pushed to the managed devices?
If so it will save me a large headache.

  @MR.S

Sounds promising.

I'm going to migrate the controller during this week

Thanks

  @MR.S