@Edoardo.a. 

Hi, here is how you do what you asked (ie Settings->Controller), but I'd advise against this approach:

Instead I suggest you create a Reserved IP on your router for the OC200 so it is always provisioned with the same IP via DHCP.

  @Edoardo.a. 

Try factory resetting one of the APs and re-adopting it from scratch.

If that doesn't work, check the Devices tab on your OC200 web interface, and forget all the AP devices you find there (previously adopted)...then re-adopt.

Since you're using a 3rd party router to hand out IP's you need to make sure you only define IP's in the 192.168.1.x/24 subnet on your controller.  Do not enable VLANs.

For the best possible solution, it would be ideal if you could add an ER605 and some managed switches (ie SG2xxx or SG3xxx not the SG1xxx)...because right now, you have no control over subnets or VLANs with the OC200.  Really the only benefit you would get is seamless roaming support.

  @Tescophil 

Your feedback is appreciated, however, I think you misunderstood the point of having a 'fall back IP' as built into all Omada devices.  Those IP/netmasks are used by the device (router/switch/AP) in exactly the case you describe.  So, if my router goes La-La and I lose DHCP, I can power cycle my OC200 and reach it at the Fallback IP by setting my laptop on the same subnet.  So there's really no harm/no difference in using a reserved DHCP (vs statically configuring) IP address for any system device, well, except the router itself :)

In fact, you could probably configure the Fallback IP to be the same IP/subnet as you have reserved in your router's DHCP table.  Best of both worlds then.