I confirm that it works when I set a new address, but not an old address. So for example, this equipment has an desired IP of 10.10.10.102, and is set to DHCP. Before the last update, it was correctly at 10.10.10.102. I then did the upgrade (19 days ago, If I'm to believe my uptime), and yesterday, had to unplug the equipment (was installing new equipment).

After re-starting the device, it was on 10.10.10.106 - see screenshot.

Now, if I decide to change the 10.10.10.102 to something else - let's say 10.10.10.108 and reboot the device, it indeed has the 10.10.10.108. Again, see screenshot.

If I then decide to switch back to 10.10.10.102, it stays at 10.10.10.108.

I've did a ping on the old address, I confirm that it is free. Also, I can set the equipment with a fixed address of 10.10.10.102, and it works as it should.

I've tried to reboot something else (it this case, the Omada OC200 Controller itself) which was on 10.10.10.10 and it got the ip 10.10.10.26 instead.

Soo ... yeah, I'm a bit at a loss here.

@Fae 

I also have the problem with that the fixed ip is not working anytime....

  @Koboldo Did a follow-up with the customer service team, they indeed found something fishy, and are working on it. @Fae thanks for the ticket creation, the answer was prompt.

Hello Team, 

I have updated my SDN to the latest available version 5.3.1 today also upgraded my ER7206 to v1.2.1. 

Unfortunately, i'm hitting exactly the same error. I tried forgetting device, removing static ip reservation, setting it again, forcing it to reconnect. Nothing helped me, now i see all this other replies, i think there is something wrong with this version of firmware or SDN controller. 

Can you please help?

  @tansuk Hi. Just to let you know that they should have a beta software next week (I've been in contact with support for the last few weeks). Hope it fixes the bug.

This situation has become unbearable. Just moments ago, my server went completely out of access just because Omada decided to assign a random IP address to it. I could live with losing access to my security cameras due to this bug, but the server with all my services on it behind the DMZ configuration, including the Omada Controller software itself is really a ridiculous situation and down right not acceptable. A $10 old used router with DHCP works better than this Omada cr** I wasted money on for several hundreds of dollars.

I have been waiting for this "beta" fix to make it's way to a final release to no avail. A good solid Amazon review on all the bugs and headaches I've been using very basic features is surely on the way. 18 months of absolute headache.

  @PapyPom Please post when the beta is ready and works....and where can i get it.....

Im also having the same issue, is there a way to downgrade my firmware?

  @Fae 

Hello, do we have any update on the fix?

Thank you