Note that I also have IP-MAC Binding enabled for all my DHCP Static reservations. The MAC addresses are correct (obviously, they haven´t changed.)

The reservations are also not in use. Rebooting or reconnecting the devices still does not give them the correct IP address.

And it's not just my cameras either. Every single device on my network that has a DHCP Static address is hapily ignoring it and getting an entirely different address. My home PC should have 192.168.10.30, but instead receives 192.168.10.13. Same for my printer, same for my AV receiver,... Everything. Which makes managing my network almost impossible if everything keeps changing.

So it looks like the latest firmware has downright broken DHCP reservations.

Looking at the CLI configuration:

(config)#show dhcp server
---------------------------------------------------------------------    
client name:TXXXX    
    bind:0    
    interface:lan    
    macaddr:10-2C-B1-XX-XX-XX    
    ipaddr:192.168.50.17    
    leasetime:Permanent    
---------------------------------------------------------------------   

It's showing a Permanent leastime for the wrong IP address. It should be .15 but it's permanently leased .17 for some reason. This is probably why a reboot doesn´t fix the issue.

  @Clive_A 

I had rebooted the devices themselves, the controller, and the access points to no avail.

Rebooting the router seems to have resolved the issue for now.

I can't be 100% certain what could be the trigger for this, but I can pinpoint the exact moment it started going wrong:

The DHCP server suddenly rejected the .14 address that the devices had always had and started handing out .16. From this point onwards, all other DHCP Reservations were ignored and everything that had a DHCP Reservation received a different IP address. This particular device does seem to be pretty agressive with the DHCP requests though... Once every 10 minutes. Could it have caused a memory leak or something?

The hardware is set to auto-update on Sundays, and none of my other systems are set to auto-update or reboot around that time.

I have the same issue as the above. 

I have ER707 with firmware 1.2.3 with Omada controller version 5.14.32.3. 

All wired reservations are being completely ignored. Rebooting the ER707 does nothing. Rebooting Omada Controller does nothing. Rebooting the devices does nothing.

At a broader macro level, there seems to be ongoing problems with Omada DHCP servers doing this for several years now across different versions of gateways etc. Is there a systemic bug that is not being addressed properly? 

As a note, I'm only seeing this to be an issue on wired devices, not wireless devices. 

Edit: I just downgraded to 1.2.2 in the hope it fixes the problem. 

Ok so no response which means this thing is getting returned to Amazon.